Thank you Daniela. I will read through the details and try it. Peter
-----Original Message----- From: Daniela Mercadante [mailto:[EMAIL PROTECTED] Sent: Monday, August 25, 2003 3:02 AM To: Jetspeed Users List Subject: Re: Monitoring Jetspeed Hi Peter, I have not so much experience in Jetspeed, but I know that this error can be generated in different ways. I can share with you one of the causes: I have jetspeed 1.4 b3, MySQL on Windows 2000. Our website has different services that use DB connection, so not managing properly these connections after sometimes the system reached the maximum of connection, jetspeed crashed and it gave the mentioned error at each login. So the problem was the incorrect handling of DB connection and the only solution was to stop Tomcat and to restart it in order to release connections. The solution that works perfectly is to enable in Tomcat the DBCP for each services implemented and the connection number doesn't grow anymore. You can find details at the following address: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-how to.html Hope this will help you. Daniela ----- Original Message ----- From: "Peter Kapakos" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 13, 2003 5:27 PM Subject: Monitoring Jetspeed > Does anyone know of a way to monitor Jetspeed to ensure that it is running? > Users of our jetspeed portal are sometimes confronted with the following > java error: > > Horrible Exception: org.apache.jetspeed.om.profile.ProfileException: > java.lang.NullPointerException at > org.apache.jetspeed.services.profiler.JetspeedProfilerService.fallbackProfil > e (JetspeedProfilerService.java:414) at > org.apache.jetspeed.services.profiler.JetspeedProfilerService.getProfile(Jet > speedProfilerService.java:287) at > org.apache.jetspeed.services.profiler.JetspeedProfilerService.getProfile(Jet > speedProfilerService.java:440) at > org.apache.jetspeed.services.Profiler.getProfile(Profiler.java:123) at > org.apache.jetspeed.modules.actions.JetspeedAccessController.doPerform(Jetsp > eedAccessController.java:99) at > org.apache.turbine.modules.Action.perform(Action.java:87) at > org.apache.turbine.modules.ActionLoader.exec(ActionLoader.java:122) at > org.apache.turbine.Turbine.doGet(Turbine.java:476) at > org.apache.turbine.Turbine.doPost(Turbine.java:616) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application > FilterChain.java:247) at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh > ain.java:193) at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja > va:260) at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja > va:191) at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 > ) at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. > java:170) at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:641) at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 > ) at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:641) at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java > :174) at > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at > org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java: > 1040) at > org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151 > ) at java.lang.Thread.run(Thread.java:536) > > We are not entirely sure what causes this error, but we need a way to know > that it has occured before a user logs on and sees it. Currently we only > know about it when a user encounters it upon logging in and then notifies > us...at which point we restart Tomcat and the error goes away. > > If anyone can shed any light on: > > 1) the cause of this error > 2) how it can be avoided > 3) monitoring jetspeed for availability > > Thanks in advance everyone. > > Peter Kapakos > Web Developer > Teleias Inc. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
