I would like to know what solution exists to correct the errors when deploying several applications when using wmq.jmsra.rar, it happens that in several environments with JBoss EAP 7 when deploying or restarting jboss the applications fail and it is only possible to deploy them if it is deployed first wmq.jmsra.rar, is there any way to guarantee that whenever an application is deployed or jboss is restarted, wmq.jmsra.rar is deployed first?
Related
I am developing an application on .NET6 using Microsoft Blazor. I have containerized this application to be able to deploy with more flexibility and to avoid Azure Web Apps problems.
Azure Web Apps is an Azure service which can host web applications like .NET 6 applications but while running on this service, several things can happen:
Server Swap, service is changing the underlying infrastructure, this can be avoided by using the ARR AFFINITY switch form the Azure Portal
Server Upgrades, framework or storage upgrades causes application to be restarted at any time
Application Pool recycle with periodic recycle intervals
So when we have an application which has a stateful mechanism such as a thread pool, all the treads will be cleared after the application is restarted.
Here is an example of a random restart:
One cool way that I found to overcome these issues, is by using Docker Containers which they can implement the .NET 6.
FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
I have already tested this and my application is running without any problem or restart for a week by now while in Azure I had at least two restarts inside a week.
My concern now is more about Application Pool recycle, I was familiar in the past with IIS but now I am sure how this is handled in docker container, if there is an IIS behind with settings and if there is, how I can check the 'DisableOverlappedRecycle', 'DisableRecyclingConfigChange' and 'Idle Time-out' options.
Any ideas?
Looking inside the running Docker container which build by the Dockerfile to understand the deployment, found the project files but also the Web.config file.
That means that an IIS is running, which can accept several settings there like DisableOverlappedRecycle', 'DisableRecyclingConfigChange' and 'Idle Time-out' options.
There is something that I cannot really understand during the AWS CodeStar development flow. Let's say I am developing a web app (MVC) locally, it works and now I want to test it remotely before deploying to the final production environment.
CodeStar has created a Git repository for pushing the changes and it automatically starts the building, testing and deployment tasks. I have few questions:
How can I deploy a change to verify that it works BEFORE doing any sort of commit (avoiding to put dirty commits in the case there are some errors) to the remote environment?
How can I DEBUG a remotely ASP.NET application (breakpoints, etc...)?
How can I tell the application to use a different development database (or any other AWS service) while it is in the development "status" ?
Thank you for your delucidations.
I am deploying 2 different projects in an azure web app service. The service is configured to be running dotnet 5. I am using virtual directory to deploy 3 applications in this app service. The default app, a dotnet 5 app, runs fine. On the first subsites if I deploy a dotnet 2.1 app, that works perfectly. But when I try to deploy a dotnet 5 app on the second subsite it shows the mentioned error in question - added an image of it
As far as I understood this is probably happening because they share same application pool. I tried the following stuffs:
Deployed as a self-contained app
Added AspNetCoreModuleV2 and out of process tags in csproj files of all projects as per this answer (and a few more answers from that link)
Frankly speaking I couldnt find much help in the net and not really sure how to proceed with this.
I've got an ASP.NET 5 project that I'd like to deploy to a remote server. I don't have remote desktop access to this machine, otherwise I could follow the same method most people use when deploying to IIS.
I'm able to deploy to my IIS 8.5 just fine on the same machine as my development. First I package my project to get the approot and wwwroot directories. Then, I point IIS to my wwwroot, and all works fine.
The problem is trying to deploy remotely. Normally I would zip up my MVC 5 project and use the IIS gui to 'import' an application.
That doesn't work for my MVC 6 project. Either I'm zipping it up incorrectly or MVC 6 projects can't be deployed this way.
How do you publish a vNext application to a remote IIS server?
Edit:
Just FYI, I am using Microsoft's Web Deploy Remote Agent to deploy this to the server. http://www.asp.net/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-(remote-agent)
It works perfectly for MVC 5 apps, because developers can easily deploy web apps and IT can restrict access to the machines, but the problem is trying to deploy MVC 6 apps using this agent.
I'm not questioning how to deploy MVC 6 projects to IIS, because that's already answered Here, this is concerning how to remotely deploy to IIS.
I solved this by updating to Web Deploy 3.6. The newest version includes a specialized provider for deploying ASP.NET 5 applications.
Details on how to use it can be found with this blog post:
http://azure.microsoft.com/blog/2014/08/11/web-deploy-3-6-beta-released/
The download link is as follows:
http://www.microsoft.com/en-us/download/details.aspx?id=43717
Use the contentPathLib provider or enable contentlibextension.
Example usage:
C:\Program Files (x86)\IIS\Microsoft Web Deploy V3> msdeploy
-verb:sync -source:iisapp=C:\release\Publish\wwwroot -dest:iisapp="Default Web Site/ExampleApp",computerName=machinename -enablelink:contentlibextension
To my knowledge, there isn't a GUI supporting these deployment methods yet. I assume this is because vNext is in Beta, and is expected to have breaking changes.
How to deploy an asp.net webApp to multiple servers?
Deploy Web Applications Using the Copy Web Tool
also check thread
What method do you use to deploy ASP.Net applications to the wild?
It depends how many servers you're talking about.
For less than about 4 or 5 servers, I just zip the application, copy to each server, unzip into a new folder, and tell IIS to look at the new folder, using IIS Manager. In a load-balanced environment, it also means taking all servers except one offline, and then updating them one at a time, and bringing them back online afterwards.
For more servers than that, I prefer to use Windows Deployment Services (WDS).