For some reason our standalone JBoss 7.1.1 undeploys my war file on shutdown/restart.
Deployment happens with maven from a remote machine (jboss-as-maven-plugin).
Stopping happens with local cli 9999 shutdown command.
Any ideas?
I finally got it why this happens. I did not only restart but also replace/update my config file. But in the updated file the deployment part is missing. And then it seams that jboss does not re-deploy the war file.
Kind of a problem that configuration and deployment information are in the same file, there is no separation of concerns here.
Related
I have a Spring Boot project. I created the following two configurations:
Spring Boot Configuration
JAR Application Configuration
Can someone tell me what is the difference? They both run as expected.
Thank you.
Running via Spring Boot configuration will allow hot swapping of the changes during debugging which is very useful during development as you don't have to rebuild all the files and package the jar on every change.
Jar Application is handy when you want to verify that your production jar works as expected.
Is there any way to disable marking files in JBoss 7.2?
I deploy/undeploy my war using jmx, when undeploying the war is marked with ".undeployed" even if i deploy it it keeps the same marker. The problem is that when i restart the server the undeployed files can not be redeployed.
Any other suggestion is welcome.
Thanks.
You can remove deployment-scanner subsystem, this why deployments folder wont be even consider for deploying.
And you can use CLI/console/mgmt api to do deployments.
you can remove deployment-scanner subsystem by removing it from standalone.xml
or by running
/subsystem=deployment-scanner:remove
reload
in CLI.
We have a Live mule server (Community edition ) 3.3.0 running on a Windows 2008 server.
We have several apps running on it.
We tried to hotdeploy a new app in it. It failed saying some port was already in use/bind - this was a JMX port. However we were unable to undeploy it. It didn't create any anchor file as it had failed deployment so we couldn't do the clean undeploy. When we tried to delete the exploded folder it didn't allow as it said the jars in the lib were in use.
We tried to re-deploy the same file with fix again but it had no effect.
Question is irrespective of what caused out application to fail - how can one undeploy or take out a Mule app (failed) completely? It doesn't have anchor file and trying to delete says jar in use. Only way we could do was to stop mule and then delete the folder and restart Mule - totally unacceptable in production environment.
Any clues?
This is a known bug on 3.3.0 that was fixed on 3.3.1.
Hi guys previously i was deploying my project WAR on JBOSS AS 7 and whenever resources got changed the eclipse Juno auto republished the war file. But since I added my war into a ear and deployed that ear on JBOSS, now eclipse doesn't auto republish. I also tried changing publishing setting but nothing worked for me. Now I republish manually after every single change. Please help me out.
I had this same issue, but got it to work after checking the 'Deploy projects as compressed archives' box (open up the server configuration and go to the Deployments tab)
I'm trying to use IntelliJ to deploy exploded wars to JBoss 4.2.3. I seem to have no problem with doing this with 5.0.1.
But when I switch the server to 4.2.3, IntelliJ tells me that the extension for the exploded war is invalid, which makes very little sense, given that it is an exploded war. It seems to be expecting a .war file extension.
It seems that JBoss 4.2.3 can only take compressed war files, though I haven't found documentation to prove it.
Is there a way to configure JBoss 4.2.3 to accept exploded wars?
JBoss 4.x requires the exploded directory to have .war in the end of its name, adjust IDEA artifact settings and it will work fine.