Initialization issue with Tomcat [solved]

[emil]

After having installed the Development Toolsuite for Windows and having completed the initialization, I figured the following issue with tomcat:

=============================================
Start Tomcat
=============================================

Buildfile: C:\SOPERA\Devbox\tomcat.xml

init:

check-tomcat:
[echo] Check is Tomcat already running ...
[java] Failed network interaction with: https://localhost:18342/mbean?objectname=sbb:*
[java] TSP Status: STOPPED

BUILD SUCCESSFUL
Total time: 1 second
Buildfile: C:\SOPERA\Devbox\tomcat.xml

init:

start-tomcat:

BUILD SUCCESSFUL
Total time: 1 second
Buildfile: C:\SOPERA\Devbox\tomcat.xml

init:

wait-tomcat:
[java] Failed network interaction with: https://localhost:18342/mbean?objectname=sbb:*
[java] Failed network interaction with: https://localhost:18342/mbean?objectname=sbb:*
[java] Failed network interaction with: https://localhost:18342/mbean?objectname=sbb:*
[java] Failed network interaction with: https://localhost:18342/mbean?objectname=sbb:*
[java] 07.04.2009 10:12:21 org.sopware.mss.accessor.https.ReasonableHostnameV erifier verify
[java] INFO: Connecting to host with non-matching ip address. Host localhost Cert: sopsolutions
[java] 07.04.2009 10:12:21 org.sopware.mss.accessor.https.ReasonableHostnameV erifier verify
[java] INFO: Connecting to host with non-matching ip address. Host localhost Cert: sopsolutions
[java] 07.04.2009 10:12:26 org.sopware.mss.accessor.https.ReasonableHostnameV erifier verify
[java] INFO: Connecting to host with non-matching ip address. Host localhost Cert: sopsolutions
[java] 07.04.2009 10:12:32 org.sopware.mss.accessor.https.ReasonableHostnameV erifier verify
[java] INFO: Connecting to host with non-matching ip address. Host localhost Cert: sopsolutions
[java] 07.04.2009 10:12:37 org.sopware.mss.accessor.https.ReasonableHostnameV erifier verify
[java] INFO: Connecting to host with non-matching ip address. Host localhost Cert: sopsolutions
[java] 07.04.2009 10:12:42 org.sopware.mss.accessor.https.ReasonableHostnameV erifier verify
[java] INFO: Connecting to host with non-matching ip address. Host localhost Cert: sopsolutions
[java] 07.04.2009 10:12:48 org.sopware.mss.accessor.https.ReasonableHostnameV erifier verify
[java] INFO: Connecting to host with non-matching ip address. Host localhost Cert: sopsolutions
[java] TSP Status: RUNNING

BUILD SUCCESSFUL
Total time: 52 seconds


Does anyone knows why this behavior appears?

Greets,

-emil

[yshamin]

Hi,

this is not issue. This is expected behavior:
- we are waiting while Tomcat will be started and all TSP's also will be started. And ping 'address:port' each 5 seconds. While TSP's not started yet, you are getting info messages about trying to connect. When all TSP's has been started you will get: [java] TSP Status: RUNNING

Regards,
Yuri

[Jerry]

Hi Emil,

the behaviour you describe is nothing to worry about. What happens is this:

The initialization process starts up the tomcat that hosts the DevBox infrastructure (Service Registry, Configuration and Security providers) and needs to wait until startup is complete before it can fill the TSPs with their initial data. To check whether the startup is completed the initialization process tries to connect to the management port of the infrastructure's core library (see the management guide for details on the management port). Until this port is available, you will get the "Failed network interaction" messages.
The management port is acting as an https server, which means that it requires a certificate. The DevBox uses a generic certificate that does not match the actual host address, therefore you see the info messages about connecting to a host with non-matching ip addresses.

hth

Jerry