Donald; For TBL 3.4.2, we support Apache Tomcat 6.0 or higher - see http://www.topquadrant.com/products/supportedPlatforms3.4.html. We'd suggest 6.0.28 or higher versions of Tomcat 6.
Our testing shows that this behavior does not occur on Reset when using Tomcat 6, but if the behavior continues after upgrading Tomcat, we'd be interested in hearing more about that. The assumption here is that upgrading to Tomcat 6 is OK. If that's not the case, we can look into whether we can reproduce with a similar setup and maybe offer insights on potential fixes. -- Scott On Mar 24, 7:17 pm, Dilphat <[email protected]> wrote: > Hi Scott, > > Turning off the nighly reset took care of the crash, but now we are > trying to figure out why TBL crashes when attempting the reset. The > full stack trace is given below. TBL seems to try the restart several > times without success before the ultimate OutOfMemoryError occurs. > > Our Tomcat support group (not suprisingly) blames TBL for the problem, > and sites that the error did not exist before the upgrade to 3.4.2. My > bet is that we are runing a very old version of Tomcat (5.5.X) and TBL > 3.4.2 is using newer Tomcat functionality. > > Could you please provide some insight on what might be causing the > behavior below, or confirm that our outdated version of Tomcat is a > fault? We just upgraded Java to 1.6.0_24, so the JVM should not be an > issue. > > [TopBraid Info] org.topbraidlive.server: Requesting reset service at > "Tue Mar 22 01:00:26 EDT 2011" > [TopBraid Error] org.topbraid.eclipsex: Mar 22, 2011 1:00:27 AM > org.apache.catalina.core.ApplicationContext log > SEVERE: Error while stopping Framework > java.lang.reflect.InvocationTargetException > 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:597) > at > org.eclipse.equinox.servletbridge.FrameworkLauncher.stop(FrameworkLauncher.java: > 719) > at > org.topbraidlive.servletbridge.webapplicationserver.FrameworkLauncher.stop(FrameworkLauncher.java: > 185) > at > org.topbraidlive.servletbridge.webapplicationserver.FrameworkLauncher.restart(FrameworkLauncher.java: > 175) > at > org.topbraidlive.servletbridge.osgi.TBLPersonality.tblRestart(TBLPersonality.java: > 160) > at org.topbraidlive.server.PeriodicRestarter > $1.run(PeriodicRestarter.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: java.lang.IllegalStateException: The service has been > unregistered > at > org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java: > 209) > at > org.eclipse.osgi.framework.internal.core.ConsoleManager.stopConsole(ConsoleManager.java: > 162) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java: > 412) > ... 11 more > (null) > java.lang.reflect.InvocationTargetException > 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:597) > at > org.eclipse.equinox.servletbridge.FrameworkLauncher.stop(FrameworkLauncher.java: > 719) > at > org.topbraidlive.servletbridge.webapplicationserver.FrameworkLauncher.stop(FrameworkLauncher.java: > 185) > at > org.topbraidlive.servletbridge.webapplicationserver.FrameworkLauncher.restart(FrameworkLauncher.java: > 175) > at > org.topbraidlive.servletbridge.osgi.TBLPersonality.tblRestart(TBLPersonality.java: > 160) > at org.topbraidlive.server.PeriodicRestarter > $1.run(PeriodicRestarter.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: java.lang.IllegalStateException: The service has been > unregistered > at > org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java: > 209) > at > org.eclipse.osgi.framework.internal.core.ConsoleManager.stopConsole(ConsoleManager.java: > 162) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java: > 412) > ... 11 more > ^M > osgi> java.lang.OutOfMemoryError: PermGen space > > On Mar 23, 9:19 pm, Dilphat <[email protected]> wrote: > > > Thanks for the quick response Scott! I'll make the change to the > > config. > > > On Mar 23, 7:00 pm, Scott Henninger <[email protected]> > > wrote: > > > > ...also set Nightly Restart ON to false. > > > > -- Scott > > > > On Mar 23, 5:40 pm, Scott Henninger <[email protected]> > > > wrote: > > > > > Donald; This is a TBL setting to reset nightly. It is a safeguard for > > > > long-running sessions that is rarely needed. You can safely turn it > > > > off by going to the Admin Console and selecting Server Configuration > > > > Parameters. Delete the value for Nightly Restart Time and Save Data. > > > > Then re-start the server. > > > > > ...and let your Tomcat people know they are off the hook ;-) > > > > > -- Scott > > > > > On Mar 23, 5:28 pm, Dilphat <[email protected]> wrote: > > > > > > Hi all, > > > > > > we just recently upgraded to tobraid live 3.4.2 under Linux 64 bit OS. > > > > > All three of our environments, development, QA and production, crash > > > > > at 1am and issue the same error message: > > > > > > [TopBraid Info] org.topbraidlive.server: Requesting reset service at > > > > > "Wed Mar 23 01:00:05 EDT 2011" > > > > > [TopBraid Error] org.topbraid.eclipsex: Mar 23, 2011 1:00:06 AM > > > > > org.apache.catalina.core.ApplicationContext log > > > > > SEVERE: Error while stopping Framework > > > > > java.lang.reflect.InvocationTargetException > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > > > > Note that the DEV and QA environments run under different tomcat > > > > > instances on the same physical server, and the PRD instance runs under > > > > > a tomcat instance on a different server. > > > > > > The request for reset behavior had been seen when we upgraded to 3.4.1 > > > > > as well, but it rarely genereated an exception. > > > > > > Our tomcat application support group states (swears) that they are > > > > > doing nothing to cause the 1am shutdown, and from the looks of the log > > > > > messages topbraid is itself requesting the reset at 1am. > > > > > > Do you know if the above behavior is expected from TBL 3.4.2? If so is > > > > > there a way we can turn off the reset requests?- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text - -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
