Deploying admin application causes hang on Tomcat
I'm trying to install JTS and CCM, I just want to make a few tests, so I download the zip and ran the server.startup.bat script, but it takes too long to deploy the admin.war, it stays open but it left the console open for 1 day! and there's no new messages on the console, the log have the same info from the console, I tried on 3 different machines, 2 with win 7 and 1 with win server 2008, all with 8GB of memory and core i5, so, I don't think is a performance issue, can anybody help me with this?
This are all the messages in the console:
Feb 12, 2014 1:47:44 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\JTS5_32bits\server\jre\bin;C:\windows\SysWOW64;C:\windows;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\IBM\Infoprint Select;C:\Program Files (x86)\IBM\Personal Communications\;C:\Program Files (x86)\IBM\Trace Facility\;C:\RAD\SDP\jdk\bin;.
Feb 12, 2014 1:47:44 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9080"]
Feb 12, 2014 1:47:44 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9443"]
Feb 12, 2014 1:47:44 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-9009"]
Feb 12, 2014 1:47:44 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 766 ms
Feb 12, 2014 1:47:44 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Feb 12, 2014 1:47:44 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.25
Feb 12, 2014 1:47:44 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\JTS5_32bits\server\tomcat\webapps\admin.war
The catalina.log file have the same info
Thanks.
3 answers
You can try the following:
1. Turn off the antivirus and firewall applications on the machine.
2. Open a command prompt with Administrator privilege (right-click on the shortcut and choose Run as administrator).
3. Run the command servers.startup.bat.
Comments
The problem is that Tomcat is not starting, if I run the startup.bat I got this errors:
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-9443"]
The weird thing is that if I change the port on the server.xml I get the same error but now pointing to the new port, i.e. if I set this port 9995, I got this error:
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-9445"]
Every time I change it it shows the new port on the error,
Tomcat needs to open several ports when starting up. Make sure that the ports defined in server.xml are all available. To check whether port 9443 is already opened, run command
netstat -aon | findstr 9443
If it is already occupied, the PID can lead you to the process that uses the port.
Another possibility is antivirus/firewall which I mentioned before, and it is at times difficult to check. Some antivirus/firewall will just silently block it if a threat is suspected. In my experience, if the error comes straightaway, the port may be used already; and if the error comes after a few (say 5) seconds, the process may be blocked.
Hi Cesar,
If the hints from Donald do not help, please contact Tomcat support or open new PMR for that.
After several configurations I'm still getting this error:
org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9088"]
org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9488"]
org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9018"]
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-9448"]
I check the 3 ports using the command netstat -aon | findstr xxxx, and all of them is used by java.exe but only when the Tomcat console is opened, after closing it and recheck the ports with the same command, the ports are free, I'm really confused, because if I change the ports I get the same error but now with the new ports.
Maybe I'm missing something, not sure if I need to perform some other steps before trying to start the server, because I just download the zip and run the server.startup.bat script.
1. Download JTS-CCM-keys-Win64_4.0.5.zip.
2. Unzip it.
3. Open a command prompt on my Win7 64 bit machine.
4. Run server.startup.bat.
Here is the log:
18/02/2014 11:23:50 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9080"]
18/02/2014 11:23:50 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9443"]
18/02/2014 11:23:51 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-9009"]
18/02/2014 11:23:51 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 823 ms
18/02/2014 11:23:51 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
18/02/2014 11:23:51 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.32
18/02/2014 11:23:51 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Users\IBM_ADMIN\Downloads\JTS-CCM-keys-Win64_4.0.5\server\tomcat\webapps\admin.war
18/02/2014 11:24:02 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Users\IBM_ADMIN\Downloads\JTS-CCM-keys-Win64_4.0.5\server\tomcat\webapps\ccm.war
18/02/2014 11:25:29 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Users\IBM_ADMIN\Downloads\JTS-CCM-keys-Win64_4.0.5\server\tomcat\webapps\clmhelp.war
18/02/2014 11:25:49 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Users\IBM_ADMIN\Downloads\JTS-CCM-keys-Win64_4.0.5\server\tomcat\webapps\jts.war
18/02/2014 11:26:58 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Users\IBM_ADMIN\Downloads\JTS-CCM-keys-Win64_4.0.5\server\tomcat\webapps\ROOT
18/02/2014 11:26:58 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9080"]
18/02/2014 11:26:58 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9443"]
18/02/2014 11:26:58 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-9009"]
18/02/2014 11:26:58 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 187286 ms
We had in the past issues that users started clm server couple of times. Please kill all java.exe applications from task manager and run server.startup.bat.
Please provide error message which you see then.
Comments
Hi,
I already killed all java process, reboot the computer, etc... the problem is that the Tomcat console is a java process, so when the console is closed the ports are free, but when I run the startup script the console is opened and it still show this messages:
org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9088"]
org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9488"]
org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9018"]
SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-9448"]
I scan the port 9448 using the command netstat -aon | findstr 9448, and the Tomcat console is using it, I guess is because it's trying to do something on that port, but it is only used by the Tomcat console, so, I'm not sure why it is failing
The second port in the list is the secure port. It's possible that the configuration for it is not correct. You can try the following.
In the server.xml file, replace
sslProtocol="${jazz.connector.sslProtocol}"
algorithm="${jazz.connector.algorithm}"
with
sslProtocol="TLS"
algorithm="IbmX509"
These two parameters are supposed to be set in the server.startup script.
Or, use the default Tomcat configuration (commented out, just above the <Connector port="9443"> section in the server.xml file - you just comment out the IBM one and un-comment the Tomcat one.