App hangs on --> 'Initializing Spring root WebApplicationContext' on websphere - websphere

When I try to deploy the app ear through RSA on websphere, the deployment hangs on the following line:
Initializing Spring root WebApplicationContext.
Initialization successful.
And then server times out.
How can I troubleshoot this problem?
Which log should I see? The logs folder is rather confusing with too many files.
When I deploy the app through the admin console by building .ear first, it deploys fine.

I assume you are referring to publish the application within RSA/RAD. The logs are the same whether you deploy through this or via the admin console.
SystemOut, SystemErr and trace.logs would be my first points of check.
I am assuming your application spits out this info line:
Initializing Spring root WebApplicationContext. Initialization successful
When does it do this? This would likely occur after the application has been deployed and the application is in its starting phase.
I would check this location
/profiles//installedApps/
Replace all the <...> with the respective values in your environment.
Once deployment is successful you should see a directory with the name of your application eg.
This tells you that the application is installed in your Test environment server.
Publishing effectively does two activities - Install and Start the application.
Once you see the EAR here you know that your problem lies in your application start up activities.
Try and see if you can narrow down from there.
HTH
Manglu

Related

Time-out w/ Gradle deploy of Spring-based web application to WAS Liberty

I am trying to write a simple Spring-based web service to run on WAS Liberty 8.5.5.9. The application is a Gradle project, and I build and deploy the application with the command gradle clean build deploy. However, this fails with the following message:
[ant:deploy] CWWKM2006I: Deploying application .../userSetting.war to the dropins folder.
[ant:deploy] CWWKM2010I: Searching for CWWKZ0001I.*userSetting in
/home/lavin/WASLiberty/usr/servers/defaultServer/logs/messages.log.
This search will timeout after 30 seconds.
[ant:deploy] CWWKM2011E: Timed out searching for CWWKZ0001I.*userSetting in
/home/lavin/WASLiberty/usr/servers/defaultServer/logs/messages.log.
:deploy FAILED
I do see userSetting.war in the dropins/ folder, but I run into problems trying to start the application, so I assume the deployment is broken.
Can someone please explain what the problem is and how to fix?
The tooling here is waiting for up to 30 seconds to see the CWWKZ0001I message, which is the "application XYZ started" message ID. Since the build script did not find this message in 30 seconds, there are 2 possibilities:
The application failed to start (probably the case)
The application is taking longer than 30s to start (probably not the case, unless your .war application is massive)
I'll assume that the application simply failed to start, in which case you will want to check the server logs to figure out why the application failed to start. As the console indicates, the message.log can be found at /home/lavin/WASLiberty/usr/servers/defaultServer/logs/messages.log
On a side-note, Liberty 8.5.5.9 is rather old, and the Liberty team has made specific efforts to better support Spring applications since then. In particular, check out this blog post:
Open Liberty Spring Boot Starter
In case you haven't heard of OpenLiberty before, its an open-source subset of WAS Liberty (meaning anything that works on OpenLiberty will work on WAS Liberty).

Tomcat immediately undeploys .war after a successful deploy to webapps directory

I have an Octopus deployment plan using the Tomcat Manager step to deploy a .war to a linux box's instance of Tomcat. The deployment seems to succeed, but Tomcat will immediately undeploy it, causing a cycle of deployment attempts until Octopus gives up and fails the deployment.
In my catalina.out log on the target linux box, I see this:
07-Mar-2018 21:16:46.084 INFO [http-nio-8080-exec-120] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive /var/lib/tomcat8/webapps/myWebApp.war has finished in 118,532 ms
07-Mar-2018 21:16:56.355 INFO [http-nio-8080-exec-123] org.apache.catalina.startup.HostConfig.undeploy Undeploying context [/myWebApp]
There's 10 seconds in between deploying and undeploying. There's nothing in between these log lines to suggest why Tomcat decided to undeploy the webapps/myWebApp directory. What's strange is, after the final deployment attempt, the /myWebApp directory remains even though Octopus gives up and fails the deployment plan.
I'm wondering if anyone else has seen similar behavior while deploying .war files to Tomcat Manager, or if this behavior suggests a wonky config somewhere I don't know to look for.
Today I had the same problem. I tried to deploy a third application on Tomcat and got the same log output as above (yes, even with a ten to twelve second delay).
After hours I finally found the solution: My new application was developed with Java 11 but Tomcat still runs on Java 8.
I'm sure there must be any exception during deployment but it was not logged to catalina.out. Even in other log files I didn't find any clues.

IBM Worklight 6.0 - Deployed application is available in all Worklight Consoles

I have installed IBM Worklight Server 6.0 in WAS 8.0.
I have deployed a projectA.war & projectB.war via ant script and I can access both the console with the different context root.
The problem I am facing here is, I have deployed the appA.wlapp in projectA.war via the Worklight console, the same application is available when I access the projectB.war console.
Can anyone help me to find the solution?
My only guess right now is that there is a mutual database for both projects so you see the same app in both consoles (and that too only happens w/out an error because maybe the different .war files have identical authenticationConfig.xml settings).
That is, the same database configuration is used for both projects; This configuration is either:
Part of the .war files that you deploy (in worklight.properties), or
Something that you configure in the Ant task script used to deploy the .war files, or
Some configuration in the application server hosting the .war files.
See documentation: http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_clustering.html

Jboss deploying a ear and war file in the same server instance

Is it possible in Jboss deploying a ear and war file in the same server instance? If so any good source to get started? Any suggestion.
I have two applications deployed under my default deploy folder of jboss. I am running one application from which i have to call the other application to get some data. Is this possible? If so how to get started??
It is actually recommended that you only put 1 application in a server instance as a time. That said, I have had multiple ears and wars running in the same instance while I am developing. But for production it is better to separate them out. Since there is no extra cost involved this makes it easier to observe and debug apps.
Do you have a specific reason for wanting them to run side by side?
What version of JBoss are you running.

Exception sending context initialized

When i am running my application it give me this exception:-
Exception sending context initialized event to listener instance of class
org.springframework.web.util.Log4jConfigListener
java.lang.ExceptionInInitializerError
But this problem is not permanent. If i remove the log4j entries from web.xml and restart p.c and then again add log4j entries and start the server, then the application works fine.
I noticed that when the application is deployed and when i undeploy and again deploy the same application, this problem emerge.
Please help me ........ i am facing this problem from 3 months...
I just investigated it a little and have found the similar issue:
It causes when multiple jar file for log4j is available to application.
From web/application server and from build path(Included from other
path rather than web/application server)
You can see the entire thread here:
http://www.coderanch.com/t/551933/Spring/Exception-sending-context-initialized-event
looks like this is your problem.

Resources