Recently I have deployed couple of applications in Jboss 7.1.0 EAP. Whenever I shutdown or restarts the Jboss server, application undeploys and again starts deploying, because of this, we have to wait for longer time to access the deployed applications, which is not acceptable.
Currently I am deploying applications via JBOSS CLI command interface.
Can we stop this undeployment of applications on shutting down or restart of jboss EAP?
Related
I have just started working with jboss eap 7 application servers, so I would like to have an environment where I can carry out various tests, I have created a small laboratory with standalone and cluster included, but I would like to have some applications where I can test deployments, status monitoring and the server logs and the applications, I have a graylog for that purpose of the logs, but I just need the ear war applications etc... where could I download some sample applications to deploy in my laboratory?
Thanks in advance
You should use JBoss EAP QuickStarts https://github.com/jboss-developer/jboss-eap-quickstarts
JBoss startup and Server logs are not getting updated completely like started in XXXX ms. But all the services are being deployed successfully. Is there any way to debug why the logs are not printing?
Thanks,
Kusuma
Just check on your the logging subsystem configuration in your standalone.xml.
If that's not the issue, this is probably a problem with your application configuration and not JBoss, probably you just have to exclude some logging libraries in your jboss-deployment-structure.xml, to use the provided and not the jboss instance libs.
On our development server there are half dozen or so successfully deployed apps.
Every Sunday night, the server (not sure if it is JBoss or the actual server) is restarted. As JBoss tries to redeploy all the apps, one fails and then all are rolled back.
I think what is happening is that one application depends on ojdb6.jar, which is also deployed as an app, but the application is trying to be deployed before JBoss tries to deploy the oracle driver.
I followed this article http://middlewaremagic.com/jboss/?p=350 for installing the driver and followed the "Install as a deployment"
Should I have the server guys as the driver as a module?
Or does the error lye within how my application depends on the db driver?
I have disabled the HDScanner bean (by removing JBOSS_HOME/deploy/hdscanner-jboss-beans.xml) in JBoss 5.1.0 so that I must do all deployments to running instances through Twiddle (applications found in the deployment directory are automatically deployed on startup).
After I have done this I can deploy and undeploy a war by using the following commands:
twiddle.sh -s localhost invoke "jboss.system:service=MainDeployer" deploy "file:/path/to/my.war"
twiddle.sh -s localhost invoke "jboss.system:service=MainDeployer" undeploy "file:/path/to/my.war"
This works fine.
However, if I restart JBoss between the deploy and the undeploy, when I try to undeploy the app using twiddle, the app remains deployed and the JBoss logs display :
2011-04-18 14:30:41,318 WARN [org.jboss.deployment.MainDeployer] (WorkerThread#0[10.21.4.61:43700]) undeploy 'file:/path/to/my.war' : package not deployed
Am I doing something wrong, expecting something that's not possible, or is this a bug in JBoss?
If I am doing something wrong, what is the correct way to undeploy an app that has been deployed using twiddle on an instance of JBoss that has been subsequently restarted?
Edit
Without looking at the source code of JBoss, it seems to me that apps that are deployed on startup are managed in a different place from those deployed through Twiddle. Ie if an app is deployed at startup it is not known of by the mechanism accessed through Twiddle, hence the "package not deployed" error.
So, is there a way to access this other deployment manager through Twiddle such that apps that are present at startup can still be undeployed?
I have done a lot of testing on this, and basically apps that are found at startup are (rightly) considered to be part of the JBoss 'core' and are therefore deployed automatically as part of the startup process. This applies for things such as the jmx-console, and therefore applies for other .wars too. Whether through design or through consequence, these resources that have been automatically deployed during startup cannot be managed by twiddle invokations.
A strange problem occurred yesterday on a production system which has been running fine for weeks on a JBoss 4.2.3 application server: the JAR file containing the web application was no longer in the deployment folder (so the clients could no longer access the application). The server is running on a Windows box.
There was no indication of undeployment in the server logs. Normally JBoss detects if somebody deletes (or moves) a deployed web application file and executes the standard undeployment procedure, so there would be a log entry in this case.
Other web applications on the same system continued to run fine, so it was only this JAR file which simply disappeared.
Has somebody seen a similar problem with web applications on JBoss?
I'd bet my shoes that's not possible to happen spontaneously.
Check your security settings - didn't you leave JMX console accessible? Etc.