Running as service issues

pbrad

Hi,
I am having an issue lately with AwareIM on my server when trying to run it as a service. I had this running for a long time and then recently it stopped working. After I run the InstallService.bat file all three services will start up properly and run but I can no longer access the login screen etc... It will only work when I start the Aware Server from the desktop. I am running the app through Port 8088.

My suspicion is that the line in the server.xml file that tells Tomcat to use Port8088 is not being picked up by the service version. Does that make any sense at all?

Anyway, I was wondering if you could suggest a troubleshooting procedure for me to figure out why I cannot use the service version which would be my obvious preference.
Cheers,
Pete

aware_support

Hard to say what the problem is from this description. Most likely it is the port conflict. Port 8088 is not a good choice - it is often used by other apps (maybe even by JBoss). Have you checked the Tomcat log - are you sure it starts up properly? Search the log for 8088 - maybe there is an error message there. Changing the server.xml file should be quite sufficient.

Can you try some other port?

pbrad

Hi,
I just shut down the console version of AwareIM and installed the service. The three services started up fine although the server cpu usage went to 100% until I shut the AwareIM service back down again a minute later. I then removed the services and restarted AwareIM using the console.

I assume that the log that I am inspecting is the wrapper.log in C:\AwareIM\Tomcat\logs? In it, I found the following error lines:

INFO | jvm 1 | 2007/05/17 06:39:35 | INFO: Server startup in 95265 ms
INFO | jvm 1 | 2007/05/17 06:39:37 | Connecting to server localhost at port 9000
INFO | jvm 1 | 2007/05/17 06:39:37 | Connecting to server localhost at port 9000
INFO | jvm 1 | 2007/05/17 06:39:37 | Connecting to server localhost at port 9000
INFO | jvm 1 | 2007/05/17 06:39:38 | ActionErrorException thrown with error key error.basserver.connection and message null for original exception com.bas.connectionserver.server.ConnectionException and original message Unable to open TCP/IP socket for server localhost on port 9000
INFO | jvm 1 | 2007/05/17 06:39:38 | Please make sure that port 9000 is unblocked.
INFO | jvm 1 | 2007/05/17 06:39:38 | Original exception is Connection refused: connect
INFO | jvm 1 | 2007/05/17 06:39:38 | com.bas.connectionserver.server.ConnectionException: Unable to open TCP/IP socket for server localhost on port 9000
INFO | jvm 1 | 2007/05/17 06:39:38 | Please make sure that port 9000 is unblocked.
INFO | jvm 1 | 2007/05/17 06:39:38 | Original exception is Connection refused: connect
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.bas.connectionserver.server.ConnectionFactory.sendSocketLoginRequest(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.bas.connectionserver.server.ConnectionFactory.createLocalSocketConnection(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.bas.webapp.misc.WebAppUtils.logon(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.bas.webapp.actions.LogonAction.aQ(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.bas.webapp.actions.LogonAction.doExecute(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.cc.framework.adapter.struts.ActionUtil.execute(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.cc.framework.adapter.struts.FWAction.execute(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.cc.framework.adapter.struts.FWAction.execute(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.cc.framework.adapter.struts.RequestProcessorUtil.processAction(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at com.cc.framework.adapter.struts.FWRequestProcessor.processActionPerform(Unknown Source)
INFO | jvm 1 | 2007/05/17 06:39:38 | at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)

So, it looks like the problem is actually Port 9000, not Port 8088. It seems strange to me however that Port 9000 offers no problems with the console started version. Any pointers in where to head next to troubleshoot this would be appreciated.
Thanks,
Pete

aware_support

Tomcat connects to the Aware IM server via localhost and port 9000. This connection is for some reason refused. Either localhost is not addressable or there is some problem with port 9000 - it could be blocked.

tford

Other threads have reported that Running as a Service issues were resolved in Build 967.

Tom

aware_support

Yes, build 967 fixed an issue that used to break running Aware IM as a service in 2.3. It is very likely that the issue reported by the current thread was caused by that problem. Please try the latest build.