I’ve setup InfoView using tomcat 4.x with apache. I’m using the versions installed with BO 6.5.x. I deployed both using the Configuration tool. I first setup the ORB, then created/deployed the web application (tomcat) and then created/deployed the virtual web directory (apache).
When I get redirected to the login jsp under tomcat I get the following:
HTTP Status 503 -
type Status report
message
description The requested service () is not currently available.
Tomcat and my BO server are both running as well as the WebIntelligence Cluster service. When i look at the stderr.log for tomcat, i see the following:
Oct 26, 2004 5:20:43 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Oct 26, 2004 5:20:43 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=231/290 config=D:\Program Files\Business Objects\ThirdParties\tomcat\conf\jk2.properties
Oct 26, 2004 5:22:32 PM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
Oct 26, 2004 5:23:45 PM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
Take a look at your services from the control panel. Make sure you have the server(s) and web intelligence cluster started. You may have to double click on the service and go the ‘recovery’ tab and set your failure attribute to ‘restart the service’ for at least one or two times. Set the service to automatic (if not already set). Then reboot the machine to be on the safe side. See if this helps and let us know.
Thanks for the reply…I solved the problem, see below. I cannot attribute a concrete cause for the problem though…which is frustrating the heck out of me!
For anyone thats interested, here is what i THINK was the problem. I deleted my web app and virtual directory through the configuration tool and recreated them. When I was recreating my web virtual directory I noticed that it was displaying the host name, not the fully qualified url (ex: http://host-name:8085/wijsp and not http://test.development.com:8085/wisjp) according to my ORB configuration. I removed the virtual directory and the web app again, re-updated my orb, re-added the web app, re-added the virtual directory and restarted the server…this fixed the problem.
Is it me or is this software extremely inconsistent? I verified that my services were up and running…I followed the installation and configuration steps exactly…and still ran into this problem. Has anyone else found version 6.5.x to be a bit unstable/inconsistent in behavior?
Well what was going to be my next suggestion was to search for your host file on your server and make sure the host was listed. By doing what you did, you probably re-wrote to the file and it fixed the problem. I can’t say for sure if that was your issue, but I’ve had to fix it many times on customer’s servers.
Well I need to get in on the game here as well. I am having the same issue.
Not new to BO, but I am new to the apache/tomcat platform and the 6.X version so details will help me a whole lot.
Here is the output from the stderr.log:
Oct 28, 2004 6:13:32 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Oct 28, 2004 6:13:32 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=16/47 config=C:\Program Files\Business Objects\ThirdParties\tomcat\conf\jk2.properties
Oct 28, 2004 6:18:23 PM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
Oct 28, 2004 6:33:39 PM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
Oct 28, 2004 6:35:01 PM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
Which is almost the same as the other posting. I did notice that this appears to be listening on 8009 when we are using 8085 as per the ‘typical’ install.
I have checked the host file that I know of (c:/winnt/system32/drivers/etc/host) and it is standard fair with only the local loopback address. Is there someplace else I should be looking (a .conf file somewhere maybe)?
(BOB member since 2003-10-22)
I verified that my services were up and running…I followed the installation and configuration steps exactly…and still ran into this problem. Has anyone else found version 6.5.x to be a bit unstable/inconsistent in behavior?
