Start a Conversation

Unsolved

DM

4 Posts

590

January 9th, 2023 14:00

Dell Wyse Upgrade 3.3.0.276 to 3.3.1.29 Tomcat unable to deploy

Hello,

I just upgraded Dell Wyse Management Suite from v3.3.0.276 to v3.3.1.29.
Upgrade completed successfully but now I am unable to access it through the web browser, I receive a 404 Not Found error.

Looking into the log files, Apache Tomcat-9 seems to be having issues deploying the application. Below is the beginning of the errors in the catalina logs for Tomcat-9. Not sure how to resolve this. I don't believe upgrading further will help the situation.

09-Jan-2023 14:37:38.327 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
09-Jan-2023 14:38:34.842 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
09-Jan-2023 14:38:34.858 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/ccm-web] startup failed due to previous errors
09-Jan-2023 14:38:34.967 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ccm-web] registered the JDBC driver [org.mariadb.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
09-Jan-2023 14:38:34.983 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [C:\Program Files\DELL\WMS\Tomcat-9\webapps\ccm-web.war] has finished in [68,966] ms
09-Jan-2023 14:38:34.983 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [C:\Program Files\DELL\WMS\Tomcat-9\webapps\wms-api.war]
09-Jan-2023 14:38:47.296 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
09-Jan-2023 14:39:03.360 SEVERE [main] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [C:\Program Files\DELL\WMS\Tomcat-9\webapps\wms-api.war]
	java.lang.IllegalStateException: Error starting child
		at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:720)
		at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
		at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:706)
		at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:946)
		at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1792)
		at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
		at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
		at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
		at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
		at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:757)
		at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:426)
		at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1520)
		at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
		at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
		at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
		at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
		at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936)
		at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:843)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
		at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
		at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
		at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
		at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
		at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
		at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.core.StandardService.startInternal(StandardService.java:434)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.startup.Catalina.start(Catalina.java:772)
		at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
		at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
		at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
		at java.base/java.lang.reflect.Method.invoke(Method.java:566)
		at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:342)
		at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:473)
	Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/wms-api]]
		at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
		at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717)
		... 37 more

 

 

 

1 Rookie

 • 

678 Posts

January 10th, 2023 12:00

In the past, I have used the following to determine what is causing this.

Review the following logs (May be in a different location now)

  • Tomcat related log files: 
  • C:\Program Files\DELL\WMS\Tomcat-8\logs 
  • Stratus website log file: 
  • C:\Program Files\DELL\WMS\Tomcat-8\stratus.log  
  • Check Logs for error binding to port 8005 
  • SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8005]:  

java.net.BindException: Address already in use: JVM_Bind 

  • Start > run > cmd > Netstat -ano 
  • Provides list of ports in use on the server 
  • Confirm whether port 8005 (default tomcat port) is already in use 
  • Windows Express Updating Service for security updates may conflict 
  • Would appear as system service with low PID such as PID =’4’ 
  • Check PID against Taskmgr if unsure of Process name 
  • Resolve Port Conflict by updating Tomcat config to use different port: 
  • Tomcat Port defined in: 
  • C:\Program Files\DELL\WMS\Tomcat-8\conf\server.xml 
  • Confirm availability of open ports with netstat -ano 
  • Recommend port 8010 to give space for other services and skip over other tomcat port requirements 
  • Restart service (or entire server) 
  • Confirm functionality restored 

346 Posts

May 10th, 2023 22:00


If you are unable to deploy the Dell Wyse upgrade from version 3.3.0.276 to 3.3.1.29 due to a Tomcat error, there are a few things you can try to resolve the issue:

Check the Tomcat logs: Check the Tomcat logs for any errors or warnings that might provide clues to what is causing the issue. The logs are typically located in the "logs" directory of your Tomcat installation.

Restart Tomcat: Try restarting the Tomcat service on your server. Sometimes, this can resolve issues that are preventing the deployment of the upgrade.

Check file permissions: Make sure that the user account running the Tomcat service has the necessary permissions to access and modify the files required for the upgrade. The user account may need to have read and write permissions on the Wyse Management Suite directory.

Disable anti-virus software: Anti-virus software can sometimes interfere with the deployment of software updates. Try temporarily disabling any anti-virus software on the server and see if this resolves the issue.

Contact Dell Support: If none of the above steps resolve the issue, you may need to contact Dell support for further assistance. They can help you troubleshoot the issue and provide guidance on how to resolve it.

No Events found!

Top