On a previously working BO XI system, I now get “Page Cannot be Displayed” error when trying to go to the Launchpad URL.
I then tried navigating to http://:8080/ to see if Tomcat is OK, and I still get a Page Cannot be Displayed error.
On the server, I went into CCM and checked that all services are started. They were all started (including Tomcat).
Tried restarting all services (including Tomcat). Still the same problem.
Restarted server. Still no joy.
OK, confession time, here’s what I did a few hours prior to discovering the problem (and I suspect this could be what broke the system).
I edited the 3 /WEB-INF/web.xml files in order to change the session-config from 20 to 240 (to increase the timeout).
However, I backed-up each of these files. I have now reinstated the backed-up files but Tomcat still will not start.
Or rather, the service appears to start, according to the CCM, but it clearly is not working properly.
Looking in the stdout.log in the /logs folder I see the following:
05-Dec-2007 15:24:04 org.apache.coyote.http11.Http11Protocol init
SEVERE: Error initializing endpoint
java.net.BindException: Cannot assign requested address: JVM_Bind:8080
at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:264)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:137)
at org.apache.coyote.tomcat5.CoyoteConnector.initialize(CoyoteConnector.java:1429)
at org.apache.catalina.core.StandardService.initialize(StandardService.java:609)
at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2384)
at org.apache.catalina.startup.Catalina.load(Catalina.java:507)
at org.apache.catalina.startup.Catalina.load(Catalina.java:528)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:247)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:421) .....
Has anybody encountered anything like this before?
Any advice on Uninstalling/Reinstalling Tomcat.
(Looking at other posts on this forum, there seem to be quiet a few problems doing this)
For some reason when you edit the xml this happens and there is no trend in my experience as to what causes this.
The only solution is to re-deploy the desktop.war file.
Before you make any changes in future back up the xml file and should you corrupt it, stop tomcat, remove the work folder (temp stuff) replace the file and re-start tomcat.
If you have windows, try re-starting Tomcat through the CCM. If you have unix try re-starting Tomcat through the tomcatstartup.sh command.
If you have further problems with Tomcat and someone else in your organisation looks after this then get them to do the restart.
If you have edited the web.xml for Tomcat you may need to re-install. If you have edited the web.xml inside Infoview folder you need to re-deploy desktop.war
The only thing that I had changed in teach of these files was altering the from 20 to 240
I have backed out all of the changes, by copying back in the backups of these 3 files that I took before I made the changes, so the files should now be exactly as they were before I started. But still I cannot access any pages via Tomcat.
What puzzles me is that I would not expect the changes I made to have stopped Tomcat from working altogether. I cannot even get the Tomcat homepage to display!
There is, of course, the possibility that this is all unrelated to the changes htat I made, but that would seem too much of a coincidence. webnew1.txt (14.0 KB) webnew3.txt (59.0 KB) webnew2.txt (11.0 KB)
Those look odd, maybe the upload process stripped all the XML tags off - what is on the site (here) now is not valid looking XML, but maybe what you have on your servers is?
If you feel like reposting with a zip file, maybe that would give a better picture - in the mean time, I’ll post my desktoplaunch web.xml file here.
I am having a similar problem, but we have not edited any .xml files. The only variable that I’ve noticed that is different is that the IIS update was pushed onto our server.
infoview page/cms page/localhost:8080 is not pulling up. There was an error saying the port was blocked, but our system admins say that no ports are blocked.
Are you also unable to manage servers in the SIA from the CCM? It simply will not connect. Anyone find a solution to the problem?
(BOB member since 2003-01-07)
(BOB member since 2002-08-29)
(BOB member since 2003-01-07)
(BOB member since 2002-08-29)