You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Howard W. Smith, Jr." <sm...@gmail.com> on 2013/01/29 23:26:47 UTC
Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me,
nothing in server logs
Sending this to tomee/openejb and tomcat user mailing lists.
Late last night (around 11 PM), I decided to download the latest TomEE
1.5.2-SNAPSHOT available in the repository
(apache-tomee-1.5.2-20130128.041133-52-plus.zip) and start running that on
the production and development servers. After some hours and heavy lifting
(this afternoon), TomEE/tomcat just died with no 'cause' recorded in
stderr, catalina, localhost... logs. I undeployed/deleted host manager and
manager apps (weeks ago and never install/use it), for security reasons, so
there is nothing in those log files (of course).
Prior to last night, the development and production servers have been
running apache-tomee-1.5.2-20130114.041209-37-plus.zip for the last 2
weeks. With that version, i did not experience this issue at all.
What is the best way for me to find out the cause of this issue? Another
question, is 1.5.2-SNAPSHOT using Tomcat 7.0.34, still, or 7.0.35 (yet)?
I will add that, this afternoon (between 1:30 PM and 2:00 PM), I also
upgraded from Atmosphere 1.0.8 to 1.0.9 (and learned today that Atmosphere
1.0.10 may be more applicable/appropriate for me to use). With that said, I
did see the following, while using
apache-tomee-1.5.2-20130128.041133-52-plus.zip and Atmosphere 1.0.8 between
10:30 AM and 11:00 AM. The exception below just started occurring today
Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:114)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 29, 2013 10:39:48 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:117)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 29, 2013 10:40:15 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:117)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 29, 2013 10:40:35 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:117)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 29, 2013 10:40:55 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:117)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 29, 2013 10:41:20 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:117)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 29, 2013 10:41:41 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:117)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 29, 2013 10:42:05 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:117)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Jan 29, 2013 10:42:39 AM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:117)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Tue, Jan 29, 2013 at 6:00 PM, Caldarale, Charles R <
Chuck.Caldarale@unisys.com> wrote:
> > From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
> > Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just
> died on me, nothing in server logs
>
> > I was hoping to get a response from tomcat committers/users, and I
> > was assuming the same, an Atmosphere issue.
>
> The other possibility is that TomEE (not supported on this mailing list)
> has set some value to a non-numeric string, whereas a true Tomcat only uses
> numeric values in that location. Without looking at the Atmosphere code,
> it's really impossible to tell.
>
>
>
Understood about TomEE not supported on this list. Prior to using latest
Atmosphere version (1.0.9) along with latest version of TomEE, I reached
out to Jeanfrancois, and he confirmed that Atmosphere 1.0.10 is targeted
for PrimeFaces Push users (like myself), and from what I understand, 1.0.9
fixed a simple software/typo mistake in 1.0.8, and I'm assuming that 1.0.9
should not be used to replace 1.0.8 by PrimeFaces Push users like myself.
for now, i have reverted to Atmosphere 1.0.6, which was the recommended
(and most applicable/appropriate version), weeks ago, to use with my
PrimeFaces web app. I informed the tomee list that I will monitor this
behavior for the meanwhile, and I'm looking forward to using/testing
Atmosphere 1.0.10 when it is released.
RE: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
on me, nothing in server logs
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
> Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
> I was hoping to get a response from tomcat committers/users, and I
> was assuming the same, an Atmosphere issue.
The other possibility is that TomEE (not supported on this mailing list) has set some value to a non-numeric string, whereas a true Tomcat only uses numeric values in that location. Without looking at the Atmosphere code, it's really impossible to tell.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
> > Sending this to tomee/openejb and tomcat user mailing lists.
>
> Cross-posting is really frowned upon.
>
> > Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
> event
> > SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
> > [/mcmsweb] threw exception
> > java.lang.NumberFormatException: For input string: "(TomEE)/7"
> > at java.lang.NumberFormatException.forInputString(Unknown Source)
> > at java.lang.Integer.parseInt(Unknown Source)
> > at java.lang.Integer.valueOf(Unknown Source)
> > at
> org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
>
> Sure looks like an Atmosphere problem from here...
>
> - Chuck
>
>
Thanks Chuck for the response, my apologies for cross-posting, and that
part of the question, I was hoping to get a response from tomcat
committers/users, and I was assuming the same, an Atmosphere issue.
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Thu, Jan 31, 2013 at 6:10 AM, Mark Thomas <ma...@apache.org> wrote:
> On 31/01/2013 03:14, Howard W. Smith, Jr. wrote:
> > 5. from what I can see, there is an atmosphere thread that is (possibly)
> > causing this issue; please see below and let me know if I should open a
> > tomcat7.0.35 JIRA/issue or atmosphere issue on atmosphere github,
> because I
> > want to upload and/or share/provide the heap dump files; i'm assuming
> that
> > I should 'not' attach the files via email, and it might not be readable
> to
> > copy/paste the content here; please advise.
>
> That looks like a problem with the APR/native connector. Was there any
> more text (like a full stack trace) in the error message you quote below?
>
> I can't see any relevant changes between 7.0.34 and 7.0.35 that might
> have triggered this.
>
> Mark
>
> > #
> > # A fatal error has been detected by the Java Runtime Environment:
> > #
> > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180005310,
> > pid=2396, tid=3724
> > #
> > # JRE version: 7.0_11-b21
> > # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode
> > windows-amd64 compressed oops)
> > # Problematic frame:
> > # C [tcnative-1.dll+0x5310] Java_org_apache_tomcat_jni_Socket_send+0xa0
> > #
> > # Core dump written. Default location:
> > D:\apache-tomcat-7.0.35\bin\hs_err_pid2396.mdmp
> > #
> > # If you would like to submit a bug report, please visit:
> > # http://bugreport.sun.com/bugreport/crash.jsp
> > # The crash happened outside the Java Virtual Machine in native code.
> > # See problematic frame for where to report the bug.
> > #
> >
> > --------------- T H R E A D ---------------
> >
> > Current thread (0x0000000014f08000): JavaThread
> "Atmosphere-AsyncWrite-60"
> > daemon [_thread_in_native, id=3724,
> > stack(0x000000001f130000,0x000000001f230000)]
>
>
Please see https://gist.github.com/4680412
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
on me, nothing in server logs
Posted by Mark Thomas <ma...@apache.org>.
On 31/01/2013 03:14, Howard W. Smith, Jr. wrote:
> 5. from what I can see, there is an atmosphere thread that is (possibly)
> causing this issue; please see below and let me know if I should open a
> tomcat7.0.35 JIRA/issue or atmosphere issue on atmosphere github, because I
> want to upload and/or share/provide the heap dump files; i'm assuming that
> I should 'not' attach the files via email, and it might not be readable to
> copy/paste the content here; please advise.
That looks like a problem with the APR/native connector. Was there any
more text (like a full stack trace) in the error message you quote below?
I can't see any relevant changes between 7.0.34 and 7.0.35 that might
have triggered this.
Mark
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180005310,
> pid=2396, tid=3724
> #
> # JRE version: 7.0_11-b21
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode
> windows-amd64 compressed oops)
> # Problematic frame:
> # C [tcnative-1.dll+0x5310] Java_org_apache_tomcat_jni_Socket_send+0xa0
> #
> # Core dump written. Default location:
> D:\apache-tomcat-7.0.35\bin\hs_err_pid2396.mdmp
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.sun.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
>
> --------------- T H R E A D ---------------
>
> Current thread (0x0000000014f08000): JavaThread "Atmosphere-AsyncWrite-60"
> daemon [_thread_in_native, id=3724,
> stack(0x000000001f130000,0x000000001f230000)]
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
David, my apologies. below is my last/latest response to tomcat user list;
this should answer your question and provide a bit more on the 2 different
issues in OP. please see below and let me know your thoughts.
On Wed, Jan 30, 2013 at 10:14 PM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko <
> knst.kolinko@gmail.com> wrote:
>
>> 2013/1/30 Caldarale, Charles R <Ch...@unisys.com>:
>> >> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
>> >> Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just
>> died on me, nothing in server logs
>> >
>> >> Sending this to tomee/openejb and tomcat user mailing lists.
>> >
>> > Cross-posting is really frowned upon.
>> >
>> >> Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
>> event
>> >> SEVERE: Servlet.service() for servlet [Push Servlet] in context with
>> path
>> >> [/mcmsweb] threw exception
>> >> java.lang.NumberFormatException: For input string: "(TomEE)/7"
>> >> at java.lang.NumberFormatException.forInputString(Unknown Source)
>> >> at java.lang.Integer.parseInt(Unknown Source)
>> >> at java.lang.Integer.valueOf(Unknown Source)
>> >> at
>> org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
>> >
>> > Sure looks like an Atmosphere problem from here...
>> >
>>
>> +1.
>>
>>
>> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
>>
>> That "bz51881" method... an example of what you should never do...
>>
>> It tries to parse a version string to "workaround" a bug that was
>> properly fixed more than a year ago, and fails horribly.
>>
>> It is a normal practice to modify the "server info" value, e.g. [1].
>> It is useless to rely on it. It is no wonder that the one used by
>> TomEE is different from Tomcat.
>>
>> [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves
>>
>>
>>
> UPDATE:
>
> 1. Atmosphere issue 869[1] was opened, fixed, and closed on atmosphere
> github
>
> 2. This issue has been occurring on my Windows Server 2008 64bit 32GB RAM
> production server ever since I started using a new(er) version of TomEE
> 1.5.2-SNAPSHOT (which now has Tomcat 7.0.35 dependency)
>
> 3. So, I reverted to an earlier (2013-01-14) version of TomEE
> 1.5.2-SNAPSHOT (which has tomcat 7.0.34 dependency), in the meanwhile, to
> avoid this issue on the production server.
>
> 4. Within the last 30 minutes, I recognized that I have heap dump files
> for the times that TomEE 1.5.2-SNAPSHOT (with Tomcat 7.0.35 dependency)
> stopped running as windows service.
>
> 5. from what I can see, there is an atmosphere thread that is (possibly)
> causing this issue; please see below and let me know if I should open a
> tomcat7.0.35 JIRA/issue or atmosphere issue on atmosphere github, because I
> want to upload and/or share/provide the heap dump files; i'm assuming that
> I should 'not' attach the files via email, and it might not be readable to
> copy/paste the content here; please advise.
>
>
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180005310,
> pid=2396, tid=3724
> #
> # JRE version: 7.0_11-b21
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode
> windows-amd64 compressed oops)
> # Problematic frame:
> # C [tcnative-1.dll+0x5310] Java_org_apache_tomcat_jni_Socket_send+0xa0
> #
> # Core dump written. Default location:
> D:\apache-tomcat-7.0.35\bin\hs_err_pid2396.mdmp
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.sun.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
>
> --------------- T H R E A D ---------------
>
> Current thread (0x0000000014f08000): JavaThread
> "Atmosphere-AsyncWrite-60" daemon [_thread_in_native, id=3724,
> stack(0x000000001f130000,0x000000001f230000)]
>
>
>
>
> [1] https://github.com/Atmosphere/atmosphere/issues/869
>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko
<kn...@gmail.com>wrote:
> 2013/1/30 Caldarale, Charles R <Ch...@unisys.com>:
> >> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
> >> Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
> on me, nothing in server logs
> >
> >> Sending this to tomee/openejb and tomcat user mailing lists.
> >
> > Cross-posting is really frowned upon.
> >
> >> Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
> event
> >> SEVERE: Servlet.service() for servlet [Push Servlet] in context with
> path
> >> [/mcmsweb] threw exception
> >> java.lang.NumberFormatException: For input string: "(TomEE)/7"
> >> at java.lang.NumberFormatException.forInputString(Unknown Source)
> >> at java.lang.Integer.parseInt(Unknown Source)
> >> at java.lang.Integer.valueOf(Unknown Source)
> >> at
> org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
> >
> > Sure looks like an Atmosphere problem from here...
> >
>
> +1.
>
>
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
>
> That "bz51881" method... an example of what you should never do...
>
> It tries to parse a version string to "workaround" a bug that was
> properly fixed more than a year ago, and fails horribly.
>
> It is a normal practice to modify the "server info" value, e.g. [1].
> It is useless to rely on it. It is no wonder that the one used by
> TomEE is different from Tomcat.
>
> [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves
>
>
>
UPDATE:
1. Atmosphere issue 869[1] was opened, fixed, and closed on atmosphere
github
2. This issue has been occurring on my Windows Server 2008 64bit 32GB RAM
production server ever since I started using a new(er) version of TomEE
1.5.2-SNAPSHOT (which now has Tomcat 7.0.35 dependency)
3. So, I reverted to an earlier (2013-01-14) version of TomEE
1.5.2-SNAPSHOT (which has tomcat 7.0.34 dependency), in the meanwhile, to
avoid this issue on the production server.
4. Within the last 30 minutes, I recognized that I have heap dump files for
the times that TomEE 1.5.2-SNAPSHOT (with Tomcat 7.0.35 dependency) stopped
running as windows service.
5. from what I can see, there is an atmosphere thread that is (possibly)
causing this issue; please see below and let me know if I should open a
tomcat7.0.35 JIRA/issue or atmosphere issue on atmosphere github, because I
want to upload and/or share/provide the heap dump files; i'm assuming that
I should 'not' attach the files via email, and it might not be readable to
copy/paste the content here; please advise.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000180005310,
pid=2396, tid=3724
#
# JRE version: 7.0_11-b21
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode
windows-amd64 compressed oops)
# Problematic frame:
# C [tcnative-1.dll+0x5310] Java_org_apache_tomcat_jni_Socket_send+0xa0
#
# Core dump written. Default location:
D:\apache-tomcat-7.0.35\bin\hs_err_pid2396.mdmp
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- T H R E A D ---------------
Current thread (0x0000000014f08000): JavaThread "Atmosphere-AsyncWrite-60"
daemon [_thread_in_native, id=3724,
stack(0x000000001f130000,0x000000001f230000)]
[1] https://github.com/Atmosphere/atmosphere/issues/869
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
FYI, I just approached tomcat user list about this issue. waiting for a
response. IMHO, i really don't think this is a tomee 1.5.2-snapshot issue.
On Wed, Jan 30, 2013 at 10:00 PM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> Since these issues started when I started using Atmosphere 1.0.8 and 1.0.9
> with TomEE 1.5.2-SNAPSHOT (2013-01-28), I assuming that this is either a
> tomcat7.0.35 or Atmosphere issue.
>
> Please let me know if I should create a tomcat issue/jira or atmosphere
> issue on atmosphere github.
>
> Again/FYI, earlier this afternoon (around 12pm EST or EDT), I reverted to
> TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34) and
> Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was working well
> with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
>
> thanks,
> Howard
>
>
> On Wed, Jan 30, 2013 at 9:53 PM, Howard W. Smith, Jr. <
> smithh032772@gmail.com> wrote:
>
>> UPDATE:
>>
>> My apologies, I have core dumps and seemingly-to-be heap dump files as
>> well in my tomcat7.0.35/bin folder at 3 different times that I experienced
>> this problem. I am seeing atmosphere in these files.
>>
>> what is the best way for me to share heap dump text files? should I
>> create an TOMEE JIRA and then attach the files, or should I copy/paste the
>> content of the files here?
>>
>>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
used 512 some few times on TomEE but that's already a lot and was and a
buggy version regarding classloading ;)
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> thanks, i will adjust as per your recommendation. I had 384m at first, but
> with the new upgrade to new hardware, i thought that would be necessary
> since I increased -Xmx4096m.
>
>
> On Thu, Jan 31, 2013 at 8:55 AM, Mark Struberg <st...@yahoo.de> wrote:
>
> > wow -XX:MaxPermSize=4096m
> > that might be a bit huge ^^
> >
> > Permanent Generation Space is used for loaded classes and stuff. Usually
> > 256m is plenty!
> > In our production with 16 fat webapps we have 384m or so...
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> > ----- Original Message -----
> > > From: "Howard W. Smith, Jr." <sm...@gmail.com>
> > > To: users@tomee.apache.org
> > > Cc:
> > > Sent: Thursday, January 31, 2013 2:14 PM
> > > Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just
> > died on me, nothing in server logs
> > >
> > > Interesting, I ran tomcat7w.exe from d:\tomcat7.0.35\bin folder, and I
> > > am
> > > accessing the 'tomee' windows service config. So, I can use
> tomcat7w.exe
> > > to
> > > configure tomee's window service's java options. Below, is what is
> > > populated (most likely, by default) on Java options tab of tomee
> windows
> > > service. :)
> > >
> > > -Dcatalina.base=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> > > -Dcatalina.home=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> > > -Djava.endorsed.dirs=D:\apache-tomee-plus-1.5.2-SNAPSHOT\endorsed
> > > -Djava.io.tmpdir=D:\apache-tomee-plus-1.5.2-SNAPSHOT\temp
> > > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> > >
> >
> -Djava.util.logging.config.file=D:\apache-tomee-plus-1.5.2-SNAPSHOT\conf\logging.properties
> > > -Djava.awt.headless=true
> > > -XX:+UseParallelGC
> > > -XX:MaxPermSize=256M
> > > -Xss2048k
> > > -Xmx1024m
> > >
> > > I don't usually use the following, but maybe I can start using them,
> now.
> > > please advise.
> > >
> > > -XX:+UseParallelGC
> > > -Xss2048k
> > >
> > > some time has passed since I wrote, all that I mentioned above, so I
> > > configured the following on production server via tomcat7w.exe:
> > >
> > > Java Options (final):
> > > -Dcatalina.base=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> > > -Dcatalina.home=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> > > -Djava.endorsed.dirs=D:\apache-tomee-plus-1.5.2-SNAPSHOT\endorsed
> > > -Djava.io.tmpdir=D:\apache-tomee-plus-1.5.2-SNAPSHOT\temp
> > > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> > >
> >
> -Djava.util.logging.config.file=D:\apache-tomee-plus-1.5.2-SNAPSHOT\conf\logging.properties
> > > -Djava.awt.headless=true
> > > -Dtomee.keep-server-info=true
> > > -Xmx4096m
> > > -XX:MaxPermSize=4096m
> > > -XX:+UseTLAB
> > > -XX:+UseConcMarkSweepGC
> > > -XX:+CMSClassUnloadingEnabled
> > >
> > > On Java tab of tomcat7w.exe, have the following specified:
> > >
> > > Initial memory pool = 512
> > > Maximum memory pool = 4096
> > > Thread stack size =
> > >
> > > The web app via TomEE windows service is running. will continue to keep
> > you
> > > posted on this issue related to atmosphere and tcnative.
> > >
> > >
> > > On Thu, Jan 31, 2013 at 7:43 AM, Howard W. Smith, Jr. <
> > > smithh032772@gmail.com> wrote:
> > >
> > >> I'm attempting to use tomee service exe. It installed correctly.
> > >>
> > >> what is tomee's equivalent to tomcat7w.exe? I'm trying to figure
> > > out how
> > >> to configure the service, populate java options like java options are
> > >> populated on the Java tab of the tomcat7w.exe dialog?
> > >>
> > >>
> > >> On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau
> > > <rmannibucau@gmail.com
> > >> > wrote:
> > >>
> > >>>
> > >>> maybe try using tomee service exe instead of tomcat ones too
> > >>>
> > >>
> > >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
thanks, i will adjust as per your recommendation. I had 384m at first, but
with the new upgrade to new hardware, i thought that would be necessary
since I increased -Xmx4096m.
On Thu, Jan 31, 2013 at 8:55 AM, Mark Struberg <st...@yahoo.de> wrote:
> wow -XX:MaxPermSize=4096m
> that might be a bit huge ^^
>
> Permanent Generation Space is used for loaded classes and stuff. Usually
> 256m is plenty!
> In our production with 16 fat webapps we have 384m or so...
>
> LieGrue,
> strub
>
>
>
>
> ----- Original Message -----
> > From: "Howard W. Smith, Jr." <sm...@gmail.com>
> > To: users@tomee.apache.org
> > Cc:
> > Sent: Thursday, January 31, 2013 2:14 PM
> > Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just
> died on me, nothing in server logs
> >
> > Interesting, I ran tomcat7w.exe from d:\tomcat7.0.35\bin folder, and I
> > am
> > accessing the 'tomee' windows service config. So, I can use tomcat7w.exe
> > to
> > configure tomee's window service's java options. Below, is what is
> > populated (most likely, by default) on Java options tab of tomee windows
> > service. :)
> >
> > -Dcatalina.base=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> > -Dcatalina.home=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> > -Djava.endorsed.dirs=D:\apache-tomee-plus-1.5.2-SNAPSHOT\endorsed
> > -Djava.io.tmpdir=D:\apache-tomee-plus-1.5.2-SNAPSHOT\temp
> > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> >
> -Djava.util.logging.config.file=D:\apache-tomee-plus-1.5.2-SNAPSHOT\conf\logging.properties
> > -Djava.awt.headless=true
> > -XX:+UseParallelGC
> > -XX:MaxPermSize=256M
> > -Xss2048k
> > -Xmx1024m
> >
> > I don't usually use the following, but maybe I can start using them, now.
> > please advise.
> >
> > -XX:+UseParallelGC
> > -Xss2048k
> >
> > some time has passed since I wrote, all that I mentioned above, so I
> > configured the following on production server via tomcat7w.exe:
> >
> > Java Options (final):
> > -Dcatalina.base=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> > -Dcatalina.home=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> > -Djava.endorsed.dirs=D:\apache-tomee-plus-1.5.2-SNAPSHOT\endorsed
> > -Djava.io.tmpdir=D:\apache-tomee-plus-1.5.2-SNAPSHOT\temp
> > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> >
> -Djava.util.logging.config.file=D:\apache-tomee-plus-1.5.2-SNAPSHOT\conf\logging.properties
> > -Djava.awt.headless=true
> > -Dtomee.keep-server-info=true
> > -Xmx4096m
> > -XX:MaxPermSize=4096m
> > -XX:+UseTLAB
> > -XX:+UseConcMarkSweepGC
> > -XX:+CMSClassUnloadingEnabled
> >
> > On Java tab of tomcat7w.exe, have the following specified:
> >
> > Initial memory pool = 512
> > Maximum memory pool = 4096
> > Thread stack size =
> >
> > The web app via TomEE windows service is running. will continue to keep
> you
> > posted on this issue related to atmosphere and tcnative.
> >
> >
> > On Thu, Jan 31, 2013 at 7:43 AM, Howard W. Smith, Jr. <
> > smithh032772@gmail.com> wrote:
> >
> >> I'm attempting to use tomee service exe. It installed correctly.
> >>
> >> what is tomee's equivalent to tomcat7w.exe? I'm trying to figure
> > out how
> >> to configure the service, populate java options like java options are
> >> populated on the Java tab of the tomcat7w.exe dialog?
> >>
> >>
> >> On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau
> > <rmannibucau@gmail.com
> >> > wrote:
> >>
> >>>
> >>> maybe try using tomee service exe instead of tomcat ones too
> >>>
> >>
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
Posted by Mark Struberg <st...@yahoo.de>.
wow -XX:MaxPermSize=4096m
that might be a bit huge ^^
Permanent Generation Space is used for loaded classes and stuff. Usually 256m is plenty!
In our production with 16 fat webapps we have 384m or so...
LieGrue,
strub
----- Original Message -----
> From: "Howard W. Smith, Jr." <sm...@gmail.com>
> To: users@tomee.apache.org
> Cc:
> Sent: Thursday, January 31, 2013 2:14 PM
> Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
>
> Interesting, I ran tomcat7w.exe from d:\tomcat7.0.35\bin folder, and I
> am
> accessing the 'tomee' windows service config. So, I can use tomcat7w.exe
> to
> configure tomee's window service's java options. Below, is what is
> populated (most likely, by default) on Java options tab of tomee windows
> service. :)
>
> -Dcatalina.base=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> -Dcatalina.home=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> -Djava.endorsed.dirs=D:\apache-tomee-plus-1.5.2-SNAPSHOT\endorsed
> -Djava.io.tmpdir=D:\apache-tomee-plus-1.5.2-SNAPSHOT\temp
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> -Djava.util.logging.config.file=D:\apache-tomee-plus-1.5.2-SNAPSHOT\conf\logging.properties
> -Djava.awt.headless=true
> -XX:+UseParallelGC
> -XX:MaxPermSize=256M
> -Xss2048k
> -Xmx1024m
>
> I don't usually use the following, but maybe I can start using them, now.
> please advise.
>
> -XX:+UseParallelGC
> -Xss2048k
>
> some time has passed since I wrote, all that I mentioned above, so I
> configured the following on production server via tomcat7w.exe:
>
> Java Options (final):
> -Dcatalina.base=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> -Dcatalina.home=D:\apache-tomee-plus-1.5.2-SNAPSHOT
> -Djava.endorsed.dirs=D:\apache-tomee-plus-1.5.2-SNAPSHOT\endorsed
> -Djava.io.tmpdir=D:\apache-tomee-plus-1.5.2-SNAPSHOT\temp
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> -Djava.util.logging.config.file=D:\apache-tomee-plus-1.5.2-SNAPSHOT\conf\logging.properties
> -Djava.awt.headless=true
> -Dtomee.keep-server-info=true
> -Xmx4096m
> -XX:MaxPermSize=4096m
> -XX:+UseTLAB
> -XX:+UseConcMarkSweepGC
> -XX:+CMSClassUnloadingEnabled
>
> On Java tab of tomcat7w.exe, have the following specified:
>
> Initial memory pool = 512
> Maximum memory pool = 4096
> Thread stack size =
>
> The web app via TomEE windows service is running. will continue to keep you
> posted on this issue related to atmosphere and tcnative.
>
>
> On Thu, Jan 31, 2013 at 7:43 AM, Howard W. Smith, Jr. <
> smithh032772@gmail.com> wrote:
>
>> I'm attempting to use tomee service exe. It installed correctly.
>>
>> what is tomee's equivalent to tomcat7w.exe? I'm trying to figure
> out how
>> to configure the service, populate java options like java options are
>> populated on the Java tab of the tomcat7w.exe dialog?
>>
>>
>> On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau
> <rmannibucau@gmail.com
>> > wrote:
>>
>>>
>>> maybe try using tomee service exe instead of tomcat ones too
>>>
>>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Interesting, I ran tomcat7w.exe from d:\tomcat7.0.35\bin folder, and I am
accessing the 'tomee' windows service config. So, I can use tomcat7w.exe to
configure tomee's window service's java options. Below, is what is
populated (most likely, by default) on Java options tab of tomee windows
service. :)
-Dcatalina.base=D:\apache-tomee-plus-1.5.2-SNAPSHOT
-Dcatalina.home=D:\apache-tomee-plus-1.5.2-SNAPSHOT
-Djava.endorsed.dirs=D:\apache-tomee-plus-1.5.2-SNAPSHOT\endorsed
-Djava.io.tmpdir=D:\apache-tomee-plus-1.5.2-SNAPSHOT\temp
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=D:\apache-tomee-plus-1.5.2-SNAPSHOT\conf\logging.properties
-Djava.awt.headless=true
-XX:+UseParallelGC
-XX:MaxPermSize=256M
-Xss2048k
-Xmx1024m
I don't usually use the following, but maybe I can start using them, now.
please advise.
-XX:+UseParallelGC
-Xss2048k
some time has passed since I wrote, all that I mentioned above, so I
configured the following on production server via tomcat7w.exe:
Java Options (final):
-Dcatalina.base=D:\apache-tomee-plus-1.5.2-SNAPSHOT
-Dcatalina.home=D:\apache-tomee-plus-1.5.2-SNAPSHOT
-Djava.endorsed.dirs=D:\apache-tomee-plus-1.5.2-SNAPSHOT\endorsed
-Djava.io.tmpdir=D:\apache-tomee-plus-1.5.2-SNAPSHOT\temp
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=D:\apache-tomee-plus-1.5.2-SNAPSHOT\conf\logging.properties
-Djava.awt.headless=true
-Dtomee.keep-server-info=true
-Xmx4096m
-XX:MaxPermSize=4096m
-XX:+UseTLAB
-XX:+UseConcMarkSweepGC
-XX:+CMSClassUnloadingEnabled
On Java tab of tomcat7w.exe, have the following specified:
Initial memory pool = 512
Maximum memory pool = 4096
Thread stack size =
The web app via TomEE windows service is running. will continue to keep you
posted on this issue related to atmosphere and tcnative.
On Thu, Jan 31, 2013 at 7:43 AM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> I'm attempting to use tomee service exe. It installed correctly.
>
> what is tomee's equivalent to tomcat7w.exe? I'm trying to figure out how
> to configure the service, populate java options like java options are
> populated on the Java tab of the tomcat7w.exe dialog?
>
>
> On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <rmannibucau@gmail.com
> > wrote:
>
>>
>> maybe try using tomee service exe instead of tomcat ones too
>>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
think it doesn't exist today but you can simply fork service.bat, that's
the most efficient way to do so.
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> I'm attempting to use tomee service exe. It installed correctly.
>
> what is tomee's equivalent to tomcat7w.exe? I'm trying to figure out how to
> configure the service, populate java options like java options are
> populated on the Java tab of the tomcat7w.exe dialog?
>
>
> On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau
> <rm...@gmail.com>wrote:
>
> >
> > maybe try using tomee service exe instead of tomcat ones too
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
I'm attempting to use tomee service exe. It installed correctly.
what is tomee's equivalent to tomcat7w.exe? I'm trying to figure out how to
configure the service, populate java options like java options are
populated on the Java tab of the tomcat7w.exe dialog?
On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
>
> maybe try using tomee service exe instead of tomcat ones too
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
I will definitely have to try tomee service exe, again, as I have not tried
since I first tried deploying tomee 1.5.1-SNAPSHOT to production server.
tomcat7 (service) exe worked immediately, so I went with that, and all I
have been doing on production server, ever since, is updating tomee
1.5.1-SNAPSHOT, tomee 1.5.1, and tomee 1.5.2-SNAPSHOT folders. :)
The recent change in tomee 1.5.2-snapshot from tomcat7.0.34 dependency to
tomcat7.0.35 dependency is when this issue started occurring.
Mark Thomas (tomcat) just mentioned the following in a separate thread:
That looks like a problem with the APR/native connector. Was there any
more text (like a full stack trace) in the error message you quote below?
I can't see any relevant changes between 7.0.34 and 7.0.35 that might
have triggered this.
On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> tomcat supports websockets but no link with atmosphere (maybe classloader
> issue in your app, check deps)
>
> maybe try using tomee service exe instead of tomcat ones too
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>
> > Are you saying, does it work without tomee 1.5.2 SNAPSHOT integrated? I
> > have not tested that, but atmosphere does work with recent builds of
> TomEE
> > 1.5.2 SNAPSHOT, but it core dumps unexpectedly, under load or after some
> > time has passed. I'm waiting to see if it core dumps unexpectedly again
> > after adding the system property that you recommended earlier.
> >
> > By the way, I did see websockets in tomcat 7.0.35 change log. I don't
> know
> > if that could possibly be the cause. :-)
> >
> > One question. Windows service dialog has properties to restart service if
> > service fails but tomcat7w.exe does not. I set those properties yesterday
> > via window's Services dialog but I think tomcat7w.exe overwrites those
> > properties, since I generally use tomcat7w.exe to start stop service on
> > production server.
> > On Jan 31, 2013 1:12 AM, "Romain Manni-Bucau" <rm...@gmail.com>
> > wrote:
> >
> > > Do you know if atmo works with last tomcat?
> > > Le 31 janv. 2013 06:36, "Howard W. Smith, Jr." <smithh032772@gmail.com
> >
> > a
> > > écrit :
> > >
> > > > Atmosphere issue 875 added[1]
> > > >
> > > > [1] https://github.com/Atmosphere/atmosphere/issues/875
> > > >
> > > >
> > > > On Wed, Jan 30, 2013 at 10:43 PM, Howard W. Smith, Jr. <
> > > > smithh032772@gmail.com> wrote:
> > > >
> > > > > On Wed, Jan 30, 2013 at 10:34 PM, David Blevins <
> > > david.blevins@gmail.com
> > > > >wrote:
> > > > >
> > > > >> On Jan 30, 2013, at 7:00 PM, "Howard W. Smith, Jr." <
> > > > >> smithh032772@gmail.com> wrote:
> > > > >>
> > > > >> > Again/FYI, earlier this afternoon (around 12pm EST or EDT), I
> > > reverted
> > > > >> to
> > > > >> > TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34)
> and
> > > > >> > Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was
> > working
> > > > >> well
> > > > >> > with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
> > > > >>
> > > > >> Just to make sure it wasn't lost in the cracks, we did identify an
> > > issue
> > > > >> with Atomosphere/TomEE. In this file in the Atomosphere:
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
> > > > >>
> > > > >> It has the following code:
> > > > >>
> > > > >> String[] tomcatVersion =
> > > > >>
> > > config.getServletContext().getServerInfo().substring(14).split("\\.");
> > > > >>
> > > > >> This won't work because of recent updates in TomEE 1.5.2-SNAPSHOT
> > > which
> > > > >> append "(TomEE)" onto the ServerInfo string -- only skipping 14
> > > > characters
> > > > >> is not enough. Romain gave the workaround of reverting to the
> old,
> > > > >> unmodified, ServerInfo string via the System property
> > > > >> "tomee.keep-server-info=true"
> > > > >>
> > > > >> Note that if the "tomee.keep-server-info" was successfully set to
> > > true,
> > > > >> it will be logged on INFO level. If the default of false is used,
> > the
> > > > >> checking of the 'tomee.keep-server-info' is still logged, but on
> > DEBUG
> > > > >> level.
> > > > >>
> > > > >> Is it possible you can confirm that you have tried the system
> > > property,
> > > > >> see the expected log output, and the issue still exists?
> > > > >>
> > > > >>
> > > > >> -David
> > > > >>
> > > > >>
> > > > > sometime earlier, i added the system property to tomcat7w.exe java
> > > > > options, and it is currently running against earlier version of
> TomEE
> > > > > 1.5.2-SNAPSHOT (that has tomcat 7.0.34 dependency).
> > > > >
> > > > > Next/now, I will download latest version of TomEE 1.5.2-SNAPSHOT,
> and
> > > > > install to production server, and leave it running, and see what
> > > happens.
> > > > > honestly, I don't think the 'atmosphere issue' is causing the
> > > > tomee/tomcat7
> > > > > service to 'stop' running. that is possibly caused by
> > another/separate
> > > > > issue (either atmosphere or tomcat7.0.35 issue); that's my opinion.
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
WARNING: Failed using comet support:
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket, error: Tomcat
failed to detect this is a Comet application because context.xml is missing
or the Http11NioProtocol Connector is not enabled.
If that's not the case, you can also remove META-INF/context.xml and
WEB-INF/lib/atmosphere-compat-tomcat.jar Is the Nio or Apr Connector
enabled?
To answer the questions mentioned above or to respond to the above,
1. i have not configured a context.xml
2. I do have atmosphere-compat-tomcat.jar in tomee/libs (as I always have)
3. with tomee windows service, I do not have APR connector enabled (or
configured)
On Thu, Jan 31, 2013 at 1:21 PM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> Wow, interesting, now I am getting the following error in my server log
> (first time ever)
>
> Jan 31, 2013 10:49:07 AM org.atmosphere.cpr.AtmosphereFramework
> doCometSupport
> WARNING: Failed using comet support:
> org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket, error: Tomcat
> failed to detect this is a Comet application because context.xml is missing
> or the Http11NioProtocol Connector is not enabled.
> If that's not the case, you can also remove META-INF/context.xml and
> WEB-INF/lib/atmosphere-compat-tomcat.jar Is the Nio or Apr Connector
> enabled?
> Jan 31, 2013 10:49:07 AM org.atmosphere.cpr.AtmosphereFramework
> doCometSupport
> WARNING: Using org.atmosphere.container.Tomcat7BIOSupportWithWebSocket
>
> and many many attempts/occurrences of the following:
>
> Jan 31, 2013 10:51:13 AM org.atmosphere.container.BlockingIOCometSupport
> action
> SEVERE: Unable to resume the suspended connection
> Jan 31, 2013 10:51:13 AM org.atmosphere.container.BlockingIOCometSupport
> action
> SEVERE: Unable to resume the suspended connection
> Jan 31, 2013 10:51:25 AM org.atmosphere.container.BlockingIOCometSupport
> action
> SEVERE: Unable to resume the suspended connection
>
> someone else reported this/similar at URL below
>
>
> https://groups.google.com/forum/?fromgroups=#!topic/atmosphere-framework/wx9HC2Xef0o
>
> Since I didn't see this while running tomcat7 APR, I wonder if I need to
> configure APR.
>
>
>
> On Thu, Jan 31, 2013 at 10:09 AM, Howard W. Smith, Jr. <
> smithh032772@gmail.com> wrote:
>
>> Smiling... not tomee related but tomcat. I like that response! :)
>>
>> I'll have to research that. I was waiting for your response to let you
>> know that I'm going to run 'without' APR, and 'maybe' do some research to
>> see if I really need or could benefit from APR/tcnative, because as I see
>> it, this issue was due to the fact that I was using tomcat APR, and tomcat
>> APR and atmosphere was not 'jelling' together well under my 'previous'
>> config of tomcat7exe (windows service) running tomee.
>>
>> since I'm waiting patiently for Atmosphere 1.0.10, I'm going to continue
>> to use the 'stable' Atmosphere 1.0.6 version that works well with my other
>> dependencies, unless i get tempted and look at issues fixed by Atmosphere
>> 1.0.7/8/9. :)
>>
>> i will keep you all posted. as always, thank you TomEE committers!
>>
>>
>> On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau <
>> rmannibucau@gmail.com> wrote:
>>
>>> %PATH% -> apr
>>>
>>> then regarding perf it is not tomee related but tomcat
>>>
>>> it enhances perf in some cases and degrades them in some others...depends
>>> the app
>>>
>>> *Romain Manni-Bucau*
>>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>>> *Blog: **http://rmannibucau.wordpress.com/*<
>>> http://rmannibucau.wordpress.com/>
>>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>>> *Github: https://github.com/rmannibucau*
>>>
>>>
>>>
>>> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>>>
>>> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH% ?
>>> >
>>> > will not make app faster in all cases? so, tomee (committers) does not
>>> > recommend use of APR for faster performance? please let me know,
>>> because if
>>> > I remove APR, then I'm assuming APR = tomcat native, and that already
>>> > (along with other changes made today or this morning) resolves the
>>> issue
>>> > where tomee (or tomcat7 service) does not 'stop' unexpectedly because
>>> of
>>> > some conflict between atmosphere and tcnative.
>>> >
>>> >
>>> >
>>> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
>>> > <rm...@gmail.com>wrote:
>>> >
>>> > > add it to your win %PATH%
>>> > >
>>> > > but you know it will not make your app faster in all cases?
>>> > >
>>> > > the message is a bit wrong on that point
>>> > >
>>> > > *Romain Manni-Bucau*
>>> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>>> > > *Blog: **http://rmannibucau.wordpress.com/*<
>>> > > http://rmannibucau.wordpress.com/>
>>> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>>> > > *Github: https://github.com/rmannibucau*
>>> > >
>>> > >
>>> > >
>>> > > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>>> > >
>>> > > > Okay, this has always concerned me, even when I see this in the
>>> log on
>>> > my
>>> > > > development machine, which uses tomee startup scripts, when I start
>>> > tomee
>>> > > > via Netbeans - Servers - right-click TomEE, and select Start or
>>> Stop.
>>> > > >
>>> > > >
>>> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default
>>> windows
>>> > > > service, I see the following in the log (APR is loaded
>>> successfully,
>>> > > > always)
>>> > > >
>>> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
>>> > > > Jan 31, 2013 1:57:17 AM
>>> org.apache.catalina.core.AprLifecycleListener
>>> > > init
>>> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using
>>> APR
>>> > > > version 1.4.6.
>>> > > > Jan 31, 2013 1:57:17 AM
>>> org.apache.catalina.core.AprLifecycleListener
>>> > > init
>>> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept
>>> filters
>>> > > > [false], random [true].
>>> > > > Jan 31, 2013 1:57:19 AM
>>> org.apache.catalina.core.AprLifecycleListener
>>> > > > initializeSSL
>>> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
>>> > > >
>>> > > >
>>> > > > But when I use tomee/bin service.bat to install tomee windows
>>> service
>>> > > (and
>>> > > > when I start tomee server via Netbeans/tomee mgr scripts), I see
>>> the
>>> > > > following on development server (and now on production server)
>>> > > >
>>> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
>>> > > > Jan 31, 2013 9:01:43 AM
>>> org.apache.catalina.core.AprLifecycleListener
>>> > > init
>>> > > > INFO: The APR based Apache Tomcat Native library which allows
>>> optimal
>>> > > > performance in production environments was not found on the
>>> > > > java.library.path:
>>> > > >
>>> > > >
>>> > >
>>> >
>>> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
>>> > > >
>>> > > > Please advise how i can get APR loaded successfully using tomee
>>> > > > scripts/service/etc...
>>> > > >
>>> > > >
>>> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
>>> > > > smithh032772@gmail.com> wrote:
>>> > > >
>>> > > > > Okay, now that I'm using tomee service exe, as per Romain's
>>> > suggestion,
>>> > > > > and already updated max perm size as per Mark's suggestion and
>>> > > restarted
>>> > > > > server on production server... a quick update:
>>> > > > >
>>> > > > > 1. Downloaded, installed, and
>>> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on
>>> production
>>> > > > server
>>> > > > > (Windows Server 2008 64bit 32GB RAM)
>>> > > > >
>>> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested
>>> > > earlier
>>> > > > >
>>> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from
>>> what I
>>> > > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly
>>> with
>>> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
>>> > > > > -Dtomee.keep-server-info=true, when running with tomee
>>> 1.5.2-SNAPSHOT
>>> > > > build
>>> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
>>> > > > >
>>> > > > > 4. Even though the web app (and tomee) has not been under load
>>> (yet,
>>> > > > > today) like it was yesterday morning and afternoon, I have not
>>> seen
>>> > > > issue #
>>> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2
>>> (atmosphere
>>> > > > "(TomEE)/7"
>>> > > > > numberFormatException), as mentioned/discussed in OP and
>>> throughout
>>> > > this
>>> > > > > thread, ever since I added -Dtomee.keep-server-info=true
>>> > > > >
>>> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or
>>> 1.0.9 to
>>> > > the
>>> > > > > mix, just to see/confirm if tomee will stop, unexpectedly, with a
>>> > > > > resulting-core-dump in tomee/bin like it did (at least) 3 times
>>> in
>>> > > > > tomcat7/bin, when this issue occurred in the last 3 days.
>>> > > > >
>>> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be released,
>>> > which
>>> > > > > includes fix for atmosphere "(TomEE)/7" numberFormatException,
>>> along
>>> > > with
>>> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
>>> > > 3.5-SNAPSHOT)
>>> > > > > and non-PrimeFaces-Push users (I assume).
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
>>> > > > rmannibucau@gmail.com
>>> > > > > > wrote:
>>> > > > >
>>> > > > >> tomcat supports websockets but no link with atmosphere (maybe
>>> > > > classloader
>>> > > > >> issue in your app, check deps)
>>> > > > >>
>>> > > > >> maybe try using tomee service exe instead of tomcat ones too
>>> > > > >>
>>> > > > >> *Romain Manni-Bucau*
>>> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>>> > > > >> *Blog: **http://rmannibucau.wordpress.com/*<
>>> > > > >> http://rmannibucau.wordpress.com/>
>>> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>>> > > > >> *Github: https://github.com/rmannibucau*
>>> > > > >>
>>> > > > >>
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Wow, interesting, now I am getting the following error in my server log
(first time ever)
Jan 31, 2013 10:49:07 AM org.atmosphere.cpr.AtmosphereFramework
doCometSupport
WARNING: Failed using comet support:
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket, error: Tomcat
failed to detect this is a Comet application because context.xml is missing
or the Http11NioProtocol Connector is not enabled.
If that's not the case, you can also remove META-INF/context.xml and
WEB-INF/lib/atmosphere-compat-tomcat.jar Is the Nio or Apr Connector
enabled?
Jan 31, 2013 10:49:07 AM org.atmosphere.cpr.AtmosphereFramework
doCometSupport
WARNING: Using org.atmosphere.container.Tomcat7BIOSupportWithWebSocket
and many many attempts/occurrences of the following:
Jan 31, 2013 10:51:13 AM org.atmosphere.container.BlockingIOCometSupport
action
SEVERE: Unable to resume the suspended connection
Jan 31, 2013 10:51:13 AM org.atmosphere.container.BlockingIOCometSupport
action
SEVERE: Unable to resume the suspended connection
Jan 31, 2013 10:51:25 AM org.atmosphere.container.BlockingIOCometSupport
action
SEVERE: Unable to resume the suspended connection
someone else reported this/similar at URL below
https://groups.google.com/forum/?fromgroups=#!topic/atmosphere-framework/wx9HC2Xef0o
Since I didn't see this while running tomcat7 APR, I wonder if I need to
configure APR.
On Thu, Jan 31, 2013 at 10:09 AM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> Smiling... not tomee related but tomcat. I like that response! :)
>
> I'll have to research that. I was waiting for your response to let you
> know that I'm going to run 'without' APR, and 'maybe' do some research to
> see if I really need or could benefit from APR/tcnative, because as I see
> it, this issue was due to the fact that I was using tomcat APR, and tomcat
> APR and atmosphere was not 'jelling' together well under my 'previous'
> config of tomcat7exe (windows service) running tomee.
>
> since I'm waiting patiently for Atmosphere 1.0.10, I'm going to continue
> to use the 'stable' Atmosphere 1.0.6 version that works well with my other
> dependencies, unless i get tempted and look at issues fixed by Atmosphere
> 1.0.7/8/9. :)
>
> i will keep you all posted. as always, thank you TomEE committers!
>
>
> On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau <rmannibucau@gmail.com
> > wrote:
>
>> %PATH% -> apr
>>
>> then regarding perf it is not tomee related but tomcat
>>
>> it enhances perf in some cases and degrades them in some others...depends
>> the app
>>
>> *Romain Manni-Bucau*
>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> *Blog: **http://rmannibucau.wordpress.com/*<
>> http://rmannibucau.wordpress.com/>
>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> *Github: https://github.com/rmannibucau*
>>
>>
>>
>> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>>
>> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH% ?
>> >
>> > will not make app faster in all cases? so, tomee (committers) does not
>> > recommend use of APR for faster performance? please let me know,
>> because if
>> > I remove APR, then I'm assuming APR = tomcat native, and that already
>> > (along with other changes made today or this morning) resolves the issue
>> > where tomee (or tomcat7 service) does not 'stop' unexpectedly because of
>> > some conflict between atmosphere and tcnative.
>> >
>> >
>> >
>> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
>> > <rm...@gmail.com>wrote:
>> >
>> > > add it to your win %PATH%
>> > >
>> > > but you know it will not make your app faster in all cases?
>> > >
>> > > the message is a bit wrong on that point
>> > >
>> > > *Romain Manni-Bucau*
>> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> > > *Blog: **http://rmannibucau.wordpress.com/*<
>> > > http://rmannibucau.wordpress.com/>
>> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> > > *Github: https://github.com/rmannibucau*
>> > >
>> > >
>> > >
>> > > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>> > >
>> > > > Okay, this has always concerned me, even when I see this in the log
>> on
>> > my
>> > > > development machine, which uses tomee startup scripts, when I start
>> > tomee
>> > > > via Netbeans - Servers - right-click TomEE, and select Start or
>> Stop.
>> > > >
>> > > >
>> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default
>> windows
>> > > > service, I see the following in the log (APR is loaded successfully,
>> > > > always)
>> > > >
>> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
>> > > > Jan 31, 2013 1:57:17 AM
>> org.apache.catalina.core.AprLifecycleListener
>> > > init
>> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR
>> > > > version 1.4.6.
>> > > > Jan 31, 2013 1:57:17 AM
>> org.apache.catalina.core.AprLifecycleListener
>> > > init
>> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
>> > > > [false], random [true].
>> > > > Jan 31, 2013 1:57:19 AM
>> org.apache.catalina.core.AprLifecycleListener
>> > > > initializeSSL
>> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
>> > > >
>> > > >
>> > > > But when I use tomee/bin service.bat to install tomee windows
>> service
>> > > (and
>> > > > when I start tomee server via Netbeans/tomee mgr scripts), I see the
>> > > > following on development server (and now on production server)
>> > > >
>> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
>> > > > Jan 31, 2013 9:01:43 AM
>> org.apache.catalina.core.AprLifecycleListener
>> > > init
>> > > > INFO: The APR based Apache Tomcat Native library which allows
>> optimal
>> > > > performance in production environments was not found on the
>> > > > java.library.path:
>> > > >
>> > > >
>> > >
>> >
>> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
>> > > >
>> > > > Please advise how i can get APR loaded successfully using tomee
>> > > > scripts/service/etc...
>> > > >
>> > > >
>> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
>> > > > smithh032772@gmail.com> wrote:
>> > > >
>> > > > > Okay, now that I'm using tomee service exe, as per Romain's
>> > suggestion,
>> > > > > and already updated max perm size as per Mark's suggestion and
>> > > restarted
>> > > > > server on production server... a quick update:
>> > > > >
>> > > > > 1. Downloaded, installed, and
>> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on
>> production
>> > > > server
>> > > > > (Windows Server 2008 64bit 32GB RAM)
>> > > > >
>> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested
>> > > earlier
>> > > > >
>> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from
>> what I
>> > > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly
>> with
>> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
>> > > > > -Dtomee.keep-server-info=true, when running with tomee
>> 1.5.2-SNAPSHOT
>> > > > build
>> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
>> > > > >
>> > > > > 4. Even though the web app (and tomee) has not been under load
>> (yet,
>> > > > > today) like it was yesterday morning and afternoon, I have not
>> seen
>> > > > issue #
>> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2
>> (atmosphere
>> > > > "(TomEE)/7"
>> > > > > numberFormatException), as mentioned/discussed in OP and
>> throughout
>> > > this
>> > > > > thread, ever since I added -Dtomee.keep-server-info=true
>> > > > >
>> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9
>> to
>> > > the
>> > > > > mix, just to see/confirm if tomee will stop, unexpectedly, with a
>> > > > > resulting-core-dump in tomee/bin like it did (at least) 3 times in
>> > > > > tomcat7/bin, when this issue occurred in the last 3 days.
>> > > > >
>> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be released,
>> > which
>> > > > > includes fix for atmosphere "(TomEE)/7" numberFormatException,
>> along
>> > > with
>> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
>> > > 3.5-SNAPSHOT)
>> > > > > and non-PrimeFaces-Push users (I assume).
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
>> > > > rmannibucau@gmail.com
>> > > > > > wrote:
>> > > > >
>> > > > >> tomcat supports websockets but no link with atmosphere (maybe
>> > > > classloader
>> > > > >> issue in your app, check deps)
>> > > > >>
>> > > > >> maybe try using tomee service exe instead of tomcat ones too
>> > > > >>
>> > > > >> *Romain Manni-Bucau*
>> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> > > > >> *Blog: **http://rmannibucau.wordpress.com/*<
>> > > > >> http://rmannibucau.wordpress.com/>
>> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> > > > >> *Github: https://github.com/rmannibucau*
>> > > > >>
>> > > > >>
>> > > >
>> > >
>> >
>>
>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Smiling... not tomee related but tomcat. I like that response! :)
I'll have to research that. I was waiting for your response to let you know
that I'm going to run 'without' APR, and 'maybe' do some research to see if
I really need or could benefit from APR/tcnative, because as I see it, this
issue was due to the fact that I was using tomcat APR, and tomcat APR and
atmosphere was not 'jelling' together well under my 'previous' config of
tomcat7exe (windows service) running tomee.
since I'm waiting patiently for Atmosphere 1.0.10, I'm going to continue to
use the 'stable' Atmosphere 1.0.6 version that works well with my other
dependencies, unless i get tempted and look at issues fixed by Atmosphere
1.0.7/8/9. :)
i will keep you all posted. as always, thank you TomEE committers!
On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> %PATH% -> apr
>
> then regarding perf it is not tomee related but tomcat
>
> it enhances perf in some cases and degrades them in some others...depends
> the app
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>
> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH% ?
> >
> > will not make app faster in all cases? so, tomee (committers) does not
> > recommend use of APR for faster performance? please let me know, because
> if
> > I remove APR, then I'm assuming APR = tomcat native, and that already
> > (along with other changes made today or this morning) resolves the issue
> > where tomee (or tomcat7 service) does not 'stop' unexpectedly because of
> > some conflict between atmosphere and tcnative.
> >
> >
> >
> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
> > <rm...@gmail.com>wrote:
> >
> > > add it to your win %PATH%
> > >
> > > but you know it will not make your app faster in all cases?
> > >
> > > the message is a bit wrong on that point
> > >
> > > *Romain Manni-Bucau*
> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > http://rmannibucau.wordpress.com/>
> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > *Github: https://github.com/rmannibucau*
> > >
> > >
> > >
> > > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> > >
> > > > Okay, this has always concerned me, even when I see this in the log
> on
> > my
> > > > development machine, which uses tomee startup scripts, when I start
> > tomee
> > > > via Netbeans - Servers - right-click TomEE, and select Start or Stop.
> > > >
> > > >
> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default
> windows
> > > > service, I see the following in the log (APR is loaded successfully,
> > > > always)
> > > >
> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
> > > > Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener
> > > init
> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR
> > > > version 1.4.6.
> > > > Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener
> > > init
> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
> > > > [false], random [true].
> > > > Jan 31, 2013 1:57:19 AM org.apache.catalina.core.AprLifecycleListener
> > > > initializeSSL
> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
> > > >
> > > >
> > > > But when I use tomee/bin service.bat to install tomee windows service
> > > (and
> > > > when I start tomee server via Netbeans/tomee mgr scripts), I see the
> > > > following on development server (and now on production server)
> > > >
> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
> > > > Jan 31, 2013 9:01:43 AM org.apache.catalina.core.AprLifecycleListener
> > > init
> > > > INFO: The APR based Apache Tomcat Native library which allows optimal
> > > > performance in production environments was not found on the
> > > > java.library.path:
> > > >
> > > >
> > >
> >
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
> > > >
> > > > Please advise how i can get APR loaded successfully using tomee
> > > > scripts/service/etc...
> > > >
> > > >
> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
> > > > smithh032772@gmail.com> wrote:
> > > >
> > > > > Okay, now that I'm using tomee service exe, as per Romain's
> > suggestion,
> > > > > and already updated max perm size as per Mark's suggestion and
> > > restarted
> > > > > server on production server... a quick update:
> > > > >
> > > > > 1. Downloaded, installed, and
> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on
> production
> > > > server
> > > > > (Windows Server 2008 64bit 32GB RAM)
> > > > >
> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested
> > > earlier
> > > > >
> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from
> what I
> > > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly with
> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
> > > > > -Dtomee.keep-server-info=true, when running with tomee
> 1.5.2-SNAPSHOT
> > > > build
> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
> > > > >
> > > > > 4. Even though the web app (and tomee) has not been under load
> (yet,
> > > > > today) like it was yesterday morning and afternoon, I have not seen
> > > > issue #
> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2 (atmosphere
> > > > "(TomEE)/7"
> > > > > numberFormatException), as mentioned/discussed in OP and throughout
> > > this
> > > > > thread, ever since I added -Dtomee.keep-server-info=true
> > > > >
> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9
> to
> > > the
> > > > > mix, just to see/confirm if tomee will stop, unexpectedly, with a
> > > > > resulting-core-dump in tomee/bin like it did (at least) 3 times in
> > > > > tomcat7/bin, when this issue occurred in the last 3 days.
> > > > >
> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be released,
> > which
> > > > > includes fix for atmosphere "(TomEE)/7" numberFormatException,
> along
> > > with
> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
> > > 3.5-SNAPSHOT)
> > > > > and non-PrimeFaces-Push users (I assume).
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
> > > > rmannibucau@gmail.com
> > > > > > wrote:
> > > > >
> > > > >> tomcat supports websockets but no link with atmosphere (maybe
> > > > classloader
> > > > >> issue in your app, check deps)
> > > > >>
> > > > >> maybe try using tomee service exe instead of tomcat ones too
> > > > >>
> > > > >> *Romain Manni-Bucau*
> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > > >> *Blog: **http://rmannibucau.wordpress.com/*<
> > > > >> http://rmannibucau.wordpress.com/>
> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > > >> *Github: https://github.com/rmannibucau*
> > > > >>
> > > > >>
> > > >
> > >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
After some researching/reading, I replaced APR connector with NIO
connector. thanks for the recommendation, Romain.
On Thu, Jan 31, 2013 at 3:10 PM, Howard W. Smith, Jr.
<sm...@gmail.com> wrote:
> Reading through old tomcat user list threads. thanks! :)
>
>
> On Thu, Jan 31, 2013 at 2:14 PM, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>>
>> Bench you'll see ;)
>>
>> For me nio connector is often enough
>> Le 31 janv. 2013 19:46, "Howard W. Smith, Jr." <sm...@gmail.com> a
>> écrit :
>>
>> > Never mind...
>> >
>> > I found the following,
>> >
>> >
>> >
>> > http://stackoverflow.com/questions/8716259/what-does-the-apr-based-apache-tomcat-native-library-was-not-found-mean
>> >
>> > and that hinted that I needed to copy 'tcnative-1.dll' from tomcat7/bin
>> > to
>> > tomee/bin, and now APR is loaded. Do you think it is better for me to
>> > configure/use NIO connector instead?
>> >
>> >
>> >
>> > On Thu, Jan 31, 2013 at 1:34 PM, Howard W. Smith, Jr. <
>> > smithh032772@gmail.com> wrote:
>> >
>> > > Hmm, is the tomcat APR included in tomee/bin? I appended tomee/bin to
>> > > windows system %PATH%, and I still get the following error after
>> > > starting
>> > > tomee.
>> > >
>> > >
>> > > 2013-01-31 13:28:17 Commons Daemon procrun stderr initialized
>> > > Jan 31, 2013 1:28:18 PM org.apache.catalina.core.AprLifecycleListener
>> > init
>> > > INFO: The APR based Apache Tomcat Native library which allows optimal
>> > > performance in production environments was not found on the
>> > > java.library.path:
>> > >
>> >
>> > D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;.
>> > >
>> > >
>> > > On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau <
>> > rmannibucau@gmail.com
>> > > > wrote:
>> > >
>> > >> %PATH% -> apr
>> > >>
>> > >> then regarding perf it is not tomee related but tomcat
>> > >>
>> > >> it enhances perf in some cases and degrades them in some
>> > others...depends
>> > >> the app
>> > >>
>> > >> *Romain Manni-Bucau*
>> > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> > >> *Blog: **http://rmannibucau.wordpress.com/*<
>> > >> http://rmannibucau.wordpress.com/>
>> > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> > >> *Github: https://github.com/rmannibucau*
>> > >>
>> > >>
>> > >>
>> > >> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>> > >>
>> > >> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to
>> > >> > %PATH%
>> > ?
>> > >> >
>> > >> > will not make app faster in all cases? so, tomee (committers) does
>> > >> > not
>> > >> > recommend use of APR for faster performance? please let me know,
>> > >> because if
>> > >> > I remove APR, then I'm assuming APR = tomcat native, and that
>> > >> > already
>> > >> > (along with other changes made today or this morning) resolves the
>> > issue
>> > >> > where tomee (or tomcat7 service) does not 'stop' unexpectedly
>> > >> > because
>> > of
>> > >> > some conflict between atmosphere and tcnative.
>> > >> >
>> > >> >
>> > >> >
>> > >> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
>> > >> > <rm...@gmail.com>wrote:
>> > >> >
>> > >> > > add it to your win %PATH%
>> > >> > >
>> > >> > > but you know it will not make your app faster in all cases?
>> > >> > >
>> > >> > > the message is a bit wrong on that point
>> > >> > >
>> > >> > > *Romain Manni-Bucau*
>> > >> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> > >> > > *Blog: **http://rmannibucau.wordpress.com/*<
>> > >> > > http://rmannibucau.wordpress.com/>
>> > >> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> > >> > > *Github: https://github.com/rmannibucau*
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>> > >> > >
>> > >> > > > Okay, this has always concerned me, even when I see this in the
>> > log
>> > >> on
>> > >> > my
>> > >> > > > development machine, which uses tomee startup scripts, when I
>> > start
>> > >> > tomee
>> > >> > > > via Netbeans - Servers - right-click TomEE, and select Start or
>> > >> Stop.
>> > >> > > >
>> > >> > > >
>> > >> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default
>> > >> windows
>> > >> > > > service, I see the following in the log (APR is loaded
>> > successfully,
>> > >> > > > always)
>> > >> > > >
>> > >> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
>> > >> > > > Jan 31, 2013 1:57:17 AM
>> > >> org.apache.catalina.core.AprLifecycleListener
>> > >> > > init
>> > >> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24
>> > >> > > > using
>> > APR
>> > >> > > > version 1.4.6.
>> > >> > > > Jan 31, 2013 1:57:17 AM
>> > >> org.apache.catalina.core.AprLifecycleListener
>> > >> > > init
>> > >> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept
>> > filters
>> > >> > > > [false], random [true].
>> > >> > > > Jan 31, 2013 1:57:19 AM
>> > >> org.apache.catalina.core.AprLifecycleListener
>> > >> > > > initializeSSL
>> > >> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May
>> > 2012)
>> > >> > > >
>> > >> > > >
>> > >> > > > But when I use tomee/bin service.bat to install tomee windows
>> > >> service
>> > >> > > (and
>> > >> > > > when I start tomee server via Netbeans/tomee mgr scripts), I
>> > >> > > > see
>> > the
>> > >> > > > following on development server (and now on production server)
>> > >> > > >
>> > >> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
>> > >> > > > Jan 31, 2013 9:01:43 AM
>> > >> org.apache.catalina.core.AprLifecycleListener
>> > >> > > init
>> > >> > > > INFO: The APR based Apache Tomcat Native library which allows
>> > >> optimal
>> > >> > > > performance in production environments was not found on the
>> > >> > > > java.library.path:
>> > >> > > >
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>> > D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
>> > >> > > >
>> > >> > > > Please advise how i can get APR loaded successfully using tomee
>> > >> > > > scripts/service/etc...
>> > >> > > >
>> > >> > > >
>> > >> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
>> > >> > > > smithh032772@gmail.com> wrote:
>> > >> > > >
>> > >> > > > > Okay, now that I'm using tomee service exe, as per Romain's
>> > >> > suggestion,
>> > >> > > > > and already updated max perm size as per Mark's suggestion
>> > >> > > > > and
>> > >> > > restarted
>> > >> > > > > server on production server... a quick update:
>> > >> > > > >
>> > >> > > > > 1. Downloaded, installed, and
>> > >> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on
>> > >> production
>> > >> > > > server
>> > >> > > > > (Windows Server 2008 64bit 32GB RAM)
>> > >> > > > >
>> > >> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain
>> > >> > > > > suggested
>> > >> > > earlier
>> > >> > > > >
>> > >> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because
>> > >> > > > > from
>> > >> what I
>> > >> > > > > remember/witnessed, tomee/tomcat7 service stopped
>> > >> > > > > unexpectedly
>> > >> with
>> > >> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without
>> > >> > > > > the
>> > >> > > > > -Dtomee.keep-server-info=true, when running with tomee
>> > >> 1.5.2-SNAPSHOT
>> > >> > > > build
>> > >> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
>> > >> > > > >
>> > >> > > > > 4. Even though the web app (and tomee) has not been under
>> > >> > > > > load
>> > >> (yet,
>> > >> > > > > today) like it was yesterday morning and afternoon, I have
>> > >> > > > > not
>> > >> seen
>> > >> > > > issue #
>> > >> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2
>> > >> (atmosphere
>> > >> > > > "(TomEE)/7"
>> > >> > > > > numberFormatException), as mentioned/discussed in OP and
>> > >> throughout
>> > >> > > this
>> > >> > > > > thread, ever since I added -Dtomee.keep-server-info=true
>> > >> > > > >
>> > >> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or
>> > 1.0.9
>> > >> to
>> > >> > > the
>> > >> > > > > mix, just to see/confirm if tomee will stop, unexpectedly,
>> > >> > > > > with
>> > a
>> > >> > > > > resulting-core-dump in tomee/bin like it did (at least) 3
>> > >> > > > > times
>> > in
>> > >> > > > > tomcat7/bin, when this issue occurred in the last 3 days.
>> > >> > > > >
>> > >> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be
>> > >> > > > > released,
>> > >> > which
>> > >> > > > > includes fix for atmosphere "(TomEE)/7"
>> > >> > > > > numberFormatException,
>> > >> along
>> > >> > > with
>> > >> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
>> > >> > > 3.5-SNAPSHOT)
>> > >> > > > > and non-PrimeFaces-Push users (I assume).
>> > >> > > > >
>> > >> > > > >
>> > >> > > > >
>> > >> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
>> > >> > > > rmannibucau@gmail.com
>> > >> > > > > > wrote:
>> > >> > > > >
>> > >> > > > >> tomcat supports websockets but no link with atmosphere
>> > >> > > > >> (maybe
>> > >> > > > classloader
>> > >> > > > >> issue in your app, check deps)
>> > >> > > > >>
>> > >> > > > >> maybe try using tomee service exe instead of tomcat ones too
>> > >> > > > >>
>> > >> > > > >> *Romain Manni-Bucau*
>> > >> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> > >> > > > >> *Blog: **http://rmannibucau.wordpress.com/*<
>> > >> > > > >> http://rmannibucau.wordpress.com/>
>> > >> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> > >> > > > >> *Github: https://github.com/rmannibucau*
>> > >> > > > >>
>> > >> > > > >>
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Reading through old tomcat user list threads. thanks! :)
On Thu, Jan 31, 2013 at 2:14 PM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> Bench you'll see ;)
>
> For me nio connector is often enough
> Le 31 janv. 2013 19:46, "Howard W. Smith, Jr." <sm...@gmail.com> a
> écrit :
>
> > Never mind...
> >
> > I found the following,
> >
> >
> >
> http://stackoverflow.com/questions/8716259/what-does-the-apr-based-apache-tomcat-native-library-was-not-found-mean
> >
> > and that hinted that I needed to copy 'tcnative-1.dll' from tomcat7/bin
> to
> > tomee/bin, and now APR is loaded. Do you think it is better for me to
> > configure/use NIO connector instead?
> >
> >
> >
> > On Thu, Jan 31, 2013 at 1:34 PM, Howard W. Smith, Jr. <
> > smithh032772@gmail.com> wrote:
> >
> > > Hmm, is the tomcat APR included in tomee/bin? I appended tomee/bin to
> > > windows system %PATH%, and I still get the following error after
> starting
> > > tomee.
> > >
> > >
> > > 2013-01-31 13:28:17 Commons Daemon procrun stderr initialized
> > > Jan 31, 2013 1:28:18 PM org.apache.catalina.core.AprLifecycleListener
> > init
> > > INFO: The APR based Apache Tomcat Native library which allows optimal
> > > performance in production environments was not found on the
> > > java.library.path:
> > >
> >
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;.
> > >
> > >
> > > On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > > wrote:
> > >
> > >> %PATH% -> apr
> > >>
> > >> then regarding perf it is not tomee related but tomcat
> > >>
> > >> it enhances perf in some cases and degrades them in some
> > others...depends
> > >> the app
> > >>
> > >> *Romain Manni-Bucau*
> > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > >> *Blog: **http://rmannibucau.wordpress.com/*<
> > >> http://rmannibucau.wordpress.com/>
> > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > >> *Github: https://github.com/rmannibucau*
> > >>
> > >>
> > >>
> > >> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> > >>
> > >> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to
> %PATH%
> > ?
> > >> >
> > >> > will not make app faster in all cases? so, tomee (committers) does
> not
> > >> > recommend use of APR for faster performance? please let me know,
> > >> because if
> > >> > I remove APR, then I'm assuming APR = tomcat native, and that
> already
> > >> > (along with other changes made today or this morning) resolves the
> > issue
> > >> > where tomee (or tomcat7 service) does not 'stop' unexpectedly
> because
> > of
> > >> > some conflict between atmosphere and tcnative.
> > >> >
> > >> >
> > >> >
> > >> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
> > >> > <rm...@gmail.com>wrote:
> > >> >
> > >> > > add it to your win %PATH%
> > >> > >
> > >> > > but you know it will not make your app faster in all cases?
> > >> > >
> > >> > > the message is a bit wrong on that point
> > >> > >
> > >> > > *Romain Manni-Bucau*
> > >> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > >> > > *Blog: **http://rmannibucau.wordpress.com/*<
> > >> > > http://rmannibucau.wordpress.com/>
> > >> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > >> > > *Github: https://github.com/rmannibucau*
> > >> > >
> > >> > >
> > >> > >
> > >> > > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> > >> > >
> > >> > > > Okay, this has always concerned me, even when I see this in the
> > log
> > >> on
> > >> > my
> > >> > > > development machine, which uses tomee startup scripts, when I
> > start
> > >> > tomee
> > >> > > > via Netbeans - Servers - right-click TomEE, and select Start or
> > >> Stop.
> > >> > > >
> > >> > > >
> > >> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default
> > >> windows
> > >> > > > service, I see the following in the log (APR is loaded
> > successfully,
> > >> > > > always)
> > >> > > >
> > >> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
> > >> > > > Jan 31, 2013 1:57:17 AM
> > >> org.apache.catalina.core.AprLifecycleListener
> > >> > > init
> > >> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using
> > APR
> > >> > > > version 1.4.6.
> > >> > > > Jan 31, 2013 1:57:17 AM
> > >> org.apache.catalina.core.AprLifecycleListener
> > >> > > init
> > >> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept
> > filters
> > >> > > > [false], random [true].
> > >> > > > Jan 31, 2013 1:57:19 AM
> > >> org.apache.catalina.core.AprLifecycleListener
> > >> > > > initializeSSL
> > >> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May
> > 2012)
> > >> > > >
> > >> > > >
> > >> > > > But when I use tomee/bin service.bat to install tomee windows
> > >> service
> > >> > > (and
> > >> > > > when I start tomee server via Netbeans/tomee mgr scripts), I see
> > the
> > >> > > > following on development server (and now on production server)
> > >> > > >
> > >> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
> > >> > > > Jan 31, 2013 9:01:43 AM
> > >> org.apache.catalina.core.AprLifecycleListener
> > >> > > init
> > >> > > > INFO: The APR based Apache Tomcat Native library which allows
> > >> optimal
> > >> > > > performance in production environments was not found on the
> > >> > > > java.library.path:
> > >> > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
> > >> > > >
> > >> > > > Please advise how i can get APR loaded successfully using tomee
> > >> > > > scripts/service/etc...
> > >> > > >
> > >> > > >
> > >> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
> > >> > > > smithh032772@gmail.com> wrote:
> > >> > > >
> > >> > > > > Okay, now that I'm using tomee service exe, as per Romain's
> > >> > suggestion,
> > >> > > > > and already updated max perm size as per Mark's suggestion and
> > >> > > restarted
> > >> > > > > server on production server... a quick update:
> > >> > > > >
> > >> > > > > 1. Downloaded, installed, and
> > >> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on
> > >> production
> > >> > > > server
> > >> > > > > (Windows Server 2008 64bit 32GB RAM)
> > >> > > > >
> > >> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain
> suggested
> > >> > > earlier
> > >> > > > >
> > >> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from
> > >> what I
> > >> > > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly
> > >> with
> > >> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
> > >> > > > > -Dtomee.keep-server-info=true, when running with tomee
> > >> 1.5.2-SNAPSHOT
> > >> > > > build
> > >> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
> > >> > > > >
> > >> > > > > 4. Even though the web app (and tomee) has not been under load
> > >> (yet,
> > >> > > > > today) like it was yesterday morning and afternoon, I have not
> > >> seen
> > >> > > > issue #
> > >> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2
> > >> (atmosphere
> > >> > > > "(TomEE)/7"
> > >> > > > > numberFormatException), as mentioned/discussed in OP and
> > >> throughout
> > >> > > this
> > >> > > > > thread, ever since I added -Dtomee.keep-server-info=true
> > >> > > > >
> > >> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or
> > 1.0.9
> > >> to
> > >> > > the
> > >> > > > > mix, just to see/confirm if tomee will stop, unexpectedly,
> with
> > a
> > >> > > > > resulting-core-dump in tomee/bin like it did (at least) 3
> times
> > in
> > >> > > > > tomcat7/bin, when this issue occurred in the last 3 days.
> > >> > > > >
> > >> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be
> released,
> > >> > which
> > >> > > > > includes fix for atmosphere "(TomEE)/7" numberFormatException,
> > >> along
> > >> > > with
> > >> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
> > >> > > 3.5-SNAPSHOT)
> > >> > > > > and non-PrimeFaces-Push users (I assume).
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
> > >> > > > rmannibucau@gmail.com
> > >> > > > > > wrote:
> > >> > > > >
> > >> > > > >> tomcat supports websockets but no link with atmosphere (maybe
> > >> > > > classloader
> > >> > > > >> issue in your app, check deps)
> > >> > > > >>
> > >> > > > >> maybe try using tomee service exe instead of tomcat ones too
> > >> > > > >>
> > >> > > > >> *Romain Manni-Bucau*
> > >> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > >> > > > >> *Blog: **http://rmannibucau.wordpress.com/*<
> > >> > > > >> http://rmannibucau.wordpress.com/>
> > >> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > >> > > > >> *Github: https://github.com/rmannibucau*
> > >> > > > >>
> > >> > > > >>
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Bench you'll see ;)
For me nio connector is often enough
Le 31 janv. 2013 19:46, "Howard W. Smith, Jr." <sm...@gmail.com> a
écrit :
> Never mind...
>
> I found the following,
>
>
> http://stackoverflow.com/questions/8716259/what-does-the-apr-based-apache-tomcat-native-library-was-not-found-mean
>
> and that hinted that I needed to copy 'tcnative-1.dll' from tomcat7/bin to
> tomee/bin, and now APR is loaded. Do you think it is better for me to
> configure/use NIO connector instead?
>
>
>
> On Thu, Jan 31, 2013 at 1:34 PM, Howard W. Smith, Jr. <
> smithh032772@gmail.com> wrote:
>
> > Hmm, is the tomcat APR included in tomee/bin? I appended tomee/bin to
> > windows system %PATH%, and I still get the following error after starting
> > tomee.
> >
> >
> > 2013-01-31 13:28:17 Commons Daemon procrun stderr initialized
> > Jan 31, 2013 1:28:18 PM org.apache.catalina.core.AprLifecycleListener
> init
> > INFO: The APR based Apache Tomcat Native library which allows optimal
> > performance in production environments was not found on the
> > java.library.path:
> >
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;.
> >
> >
> > On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > > wrote:
> >
> >> %PATH% -> apr
> >>
> >> then regarding perf it is not tomee related but tomcat
> >>
> >> it enhances perf in some cases and degrades them in some
> others...depends
> >> the app
> >>
> >> *Romain Manni-Bucau*
> >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> >> *Blog: **http://rmannibucau.wordpress.com/*<
> >> http://rmannibucau.wordpress.com/>
> >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> >> *Github: https://github.com/rmannibucau*
> >>
> >>
> >>
> >> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> >>
> >> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH%
> ?
> >> >
> >> > will not make app faster in all cases? so, tomee (committers) does not
> >> > recommend use of APR for faster performance? please let me know,
> >> because if
> >> > I remove APR, then I'm assuming APR = tomcat native, and that already
> >> > (along with other changes made today or this morning) resolves the
> issue
> >> > where tomee (or tomcat7 service) does not 'stop' unexpectedly because
> of
> >> > some conflict between atmosphere and tcnative.
> >> >
> >> >
> >> >
> >> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
> >> > <rm...@gmail.com>wrote:
> >> >
> >> > > add it to your win %PATH%
> >> > >
> >> > > but you know it will not make your app faster in all cases?
> >> > >
> >> > > the message is a bit wrong on that point
> >> > >
> >> > > *Romain Manni-Bucau*
> >> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> >> > > *Blog: **http://rmannibucau.wordpress.com/*<
> >> > > http://rmannibucau.wordpress.com/>
> >> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> >> > > *Github: https://github.com/rmannibucau*
> >> > >
> >> > >
> >> > >
> >> > > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> >> > >
> >> > > > Okay, this has always concerned me, even when I see this in the
> log
> >> on
> >> > my
> >> > > > development machine, which uses tomee startup scripts, when I
> start
> >> > tomee
> >> > > > via Netbeans - Servers - right-click TomEE, and select Start or
> >> Stop.
> >> > > >
> >> > > >
> >> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default
> >> windows
> >> > > > service, I see the following in the log (APR is loaded
> successfully,
> >> > > > always)
> >> > > >
> >> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
> >> > > > Jan 31, 2013 1:57:17 AM
> >> org.apache.catalina.core.AprLifecycleListener
> >> > > init
> >> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using
> APR
> >> > > > version 1.4.6.
> >> > > > Jan 31, 2013 1:57:17 AM
> >> org.apache.catalina.core.AprLifecycleListener
> >> > > init
> >> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept
> filters
> >> > > > [false], random [true].
> >> > > > Jan 31, 2013 1:57:19 AM
> >> org.apache.catalina.core.AprLifecycleListener
> >> > > > initializeSSL
> >> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May
> 2012)
> >> > > >
> >> > > >
> >> > > > But when I use tomee/bin service.bat to install tomee windows
> >> service
> >> > > (and
> >> > > > when I start tomee server via Netbeans/tomee mgr scripts), I see
> the
> >> > > > following on development server (and now on production server)
> >> > > >
> >> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
> >> > > > Jan 31, 2013 9:01:43 AM
> >> org.apache.catalina.core.AprLifecycleListener
> >> > > init
> >> > > > INFO: The APR based Apache Tomcat Native library which allows
> >> optimal
> >> > > > performance in production environments was not found on the
> >> > > > java.library.path:
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
> >> > > >
> >> > > > Please advise how i can get APR loaded successfully using tomee
> >> > > > scripts/service/etc...
> >> > > >
> >> > > >
> >> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
> >> > > > smithh032772@gmail.com> wrote:
> >> > > >
> >> > > > > Okay, now that I'm using tomee service exe, as per Romain's
> >> > suggestion,
> >> > > > > and already updated max perm size as per Mark's suggestion and
> >> > > restarted
> >> > > > > server on production server... a quick update:
> >> > > > >
> >> > > > > 1. Downloaded, installed, and
> >> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on
> >> production
> >> > > > server
> >> > > > > (Windows Server 2008 64bit 32GB RAM)
> >> > > > >
> >> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested
> >> > > earlier
> >> > > > >
> >> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from
> >> what I
> >> > > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly
> >> with
> >> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
> >> > > > > -Dtomee.keep-server-info=true, when running with tomee
> >> 1.5.2-SNAPSHOT
> >> > > > build
> >> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
> >> > > > >
> >> > > > > 4. Even though the web app (and tomee) has not been under load
> >> (yet,
> >> > > > > today) like it was yesterday morning and afternoon, I have not
> >> seen
> >> > > > issue #
> >> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2
> >> (atmosphere
> >> > > > "(TomEE)/7"
> >> > > > > numberFormatException), as mentioned/discussed in OP and
> >> throughout
> >> > > this
> >> > > > > thread, ever since I added -Dtomee.keep-server-info=true
> >> > > > >
> >> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or
> 1.0.9
> >> to
> >> > > the
> >> > > > > mix, just to see/confirm if tomee will stop, unexpectedly, with
> a
> >> > > > > resulting-core-dump in tomee/bin like it did (at least) 3 times
> in
> >> > > > > tomcat7/bin, when this issue occurred in the last 3 days.
> >> > > > >
> >> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be released,
> >> > which
> >> > > > > includes fix for atmosphere "(TomEE)/7" numberFormatException,
> >> along
> >> > > with
> >> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
> >> > > 3.5-SNAPSHOT)
> >> > > > > and non-PrimeFaces-Push users (I assume).
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
> >> > > > rmannibucau@gmail.com
> >> > > > > > wrote:
> >> > > > >
> >> > > > >> tomcat supports websockets but no link with atmosphere (maybe
> >> > > > classloader
> >> > > > >> issue in your app, check deps)
> >> > > > >>
> >> > > > >> maybe try using tomee service exe instead of tomcat ones too
> >> > > > >>
> >> > > > >> *Romain Manni-Bucau*
> >> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> >> > > > >> *Blog: **http://rmannibucau.wordpress.com/*<
> >> > > > >> http://rmannibucau.wordpress.com/>
> >> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> >> > > > >> *Github: https://github.com/rmannibucau*
> >> > > > >>
> >> > > > >>
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Never mind...
I found the following,
http://stackoverflow.com/questions/8716259/what-does-the-apr-based-apache-tomcat-native-library-was-not-found-mean
and that hinted that I needed to copy 'tcnative-1.dll' from tomcat7/bin to
tomee/bin, and now APR is loaded. Do you think it is better for me to
configure/use NIO connector instead?
On Thu, Jan 31, 2013 at 1:34 PM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> Hmm, is the tomcat APR included in tomee/bin? I appended tomee/bin to
> windows system %PATH%, and I still get the following error after starting
> tomee.
>
>
> 2013-01-31 13:28:17 Commons Daemon procrun stderr initialized
> Jan 31, 2013 1:28:18 PM org.apache.catalina.core.AprLifecycleListener init
> INFO: The APR based Apache Tomcat Native library which allows optimal
> performance in production environments was not found on the
> java.library.path:
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;.
>
>
> On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau <rmannibucau@gmail.com
> > wrote:
>
>> %PATH% -> apr
>>
>> then regarding perf it is not tomee related but tomcat
>>
>> it enhances perf in some cases and degrades them in some others...depends
>> the app
>>
>> *Romain Manni-Bucau*
>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> *Blog: **http://rmannibucau.wordpress.com/*<
>> http://rmannibucau.wordpress.com/>
>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> *Github: https://github.com/rmannibucau*
>>
>>
>>
>> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>>
>> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH% ?
>> >
>> > will not make app faster in all cases? so, tomee (committers) does not
>> > recommend use of APR for faster performance? please let me know,
>> because if
>> > I remove APR, then I'm assuming APR = tomcat native, and that already
>> > (along with other changes made today or this morning) resolves the issue
>> > where tomee (or tomcat7 service) does not 'stop' unexpectedly because of
>> > some conflict between atmosphere and tcnative.
>> >
>> >
>> >
>> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
>> > <rm...@gmail.com>wrote:
>> >
>> > > add it to your win %PATH%
>> > >
>> > > but you know it will not make your app faster in all cases?
>> > >
>> > > the message is a bit wrong on that point
>> > >
>> > > *Romain Manni-Bucau*
>> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> > > *Blog: **http://rmannibucau.wordpress.com/*<
>> > > http://rmannibucau.wordpress.com/>
>> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> > > *Github: https://github.com/rmannibucau*
>> > >
>> > >
>> > >
>> > > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>> > >
>> > > > Okay, this has always concerned me, even when I see this in the log
>> on
>> > my
>> > > > development machine, which uses tomee startup scripts, when I start
>> > tomee
>> > > > via Netbeans - Servers - right-click TomEE, and select Start or
>> Stop.
>> > > >
>> > > >
>> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default
>> windows
>> > > > service, I see the following in the log (APR is loaded successfully,
>> > > > always)
>> > > >
>> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
>> > > > Jan 31, 2013 1:57:17 AM
>> org.apache.catalina.core.AprLifecycleListener
>> > > init
>> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR
>> > > > version 1.4.6.
>> > > > Jan 31, 2013 1:57:17 AM
>> org.apache.catalina.core.AprLifecycleListener
>> > > init
>> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
>> > > > [false], random [true].
>> > > > Jan 31, 2013 1:57:19 AM
>> org.apache.catalina.core.AprLifecycleListener
>> > > > initializeSSL
>> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
>> > > >
>> > > >
>> > > > But when I use tomee/bin service.bat to install tomee windows
>> service
>> > > (and
>> > > > when I start tomee server via Netbeans/tomee mgr scripts), I see the
>> > > > following on development server (and now on production server)
>> > > >
>> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
>> > > > Jan 31, 2013 9:01:43 AM
>> org.apache.catalina.core.AprLifecycleListener
>> > > init
>> > > > INFO: The APR based Apache Tomcat Native library which allows
>> optimal
>> > > > performance in production environments was not found on the
>> > > > java.library.path:
>> > > >
>> > > >
>> > >
>> >
>> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
>> > > >
>> > > > Please advise how i can get APR loaded successfully using tomee
>> > > > scripts/service/etc...
>> > > >
>> > > >
>> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
>> > > > smithh032772@gmail.com> wrote:
>> > > >
>> > > > > Okay, now that I'm using tomee service exe, as per Romain's
>> > suggestion,
>> > > > > and already updated max perm size as per Mark's suggestion and
>> > > restarted
>> > > > > server on production server... a quick update:
>> > > > >
>> > > > > 1. Downloaded, installed, and
>> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on
>> production
>> > > > server
>> > > > > (Windows Server 2008 64bit 32GB RAM)
>> > > > >
>> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested
>> > > earlier
>> > > > >
>> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from
>> what I
>> > > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly
>> with
>> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
>> > > > > -Dtomee.keep-server-info=true, when running with tomee
>> 1.5.2-SNAPSHOT
>> > > > build
>> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
>> > > > >
>> > > > > 4. Even though the web app (and tomee) has not been under load
>> (yet,
>> > > > > today) like it was yesterday morning and afternoon, I have not
>> seen
>> > > > issue #
>> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2
>> (atmosphere
>> > > > "(TomEE)/7"
>> > > > > numberFormatException), as mentioned/discussed in OP and
>> throughout
>> > > this
>> > > > > thread, ever since I added -Dtomee.keep-server-info=true
>> > > > >
>> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9
>> to
>> > > the
>> > > > > mix, just to see/confirm if tomee will stop, unexpectedly, with a
>> > > > > resulting-core-dump in tomee/bin like it did (at least) 3 times in
>> > > > > tomcat7/bin, when this issue occurred in the last 3 days.
>> > > > >
>> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be released,
>> > which
>> > > > > includes fix for atmosphere "(TomEE)/7" numberFormatException,
>> along
>> > > with
>> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
>> > > 3.5-SNAPSHOT)
>> > > > > and non-PrimeFaces-Push users (I assume).
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
>> > > > rmannibucau@gmail.com
>> > > > > > wrote:
>> > > > >
>> > > > >> tomcat supports websockets but no link with atmosphere (maybe
>> > > > classloader
>> > > > >> issue in your app, check deps)
>> > > > >>
>> > > > >> maybe try using tomee service exe instead of tomcat ones too
>> > > > >>
>> > > > >> *Romain Manni-Bucau*
>> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> > > > >> *Blog: **http://rmannibucau.wordpress.com/*<
>> > > > >> http://rmannibucau.wordpress.com/>
>> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> > > > >> *Github: https://github.com/rmannibucau*
>> > > > >>
>> > > > >>
>> > > >
>> > >
>> >
>>
>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Hmm, is the tomcat APR included in tomee/bin? I appended tomee/bin to
windows system %PATH%, and I still get the following error after starting
tomee.
2013-01-31 13:28:17 Commons Daemon procrun stderr initialized
Jan 31, 2013 1:28:18 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;.
On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> %PATH% -> apr
>
> then regarding perf it is not tomee related but tomcat
>
> it enhances perf in some cases and degrades them in some others...depends
> the app
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>
> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH% ?
> >
> > will not make app faster in all cases? so, tomee (committers) does not
> > recommend use of APR for faster performance? please let me know, because
> if
> > I remove APR, then I'm assuming APR = tomcat native, and that already
> > (along with other changes made today or this morning) resolves the issue
> > where tomee (or tomcat7 service) does not 'stop' unexpectedly because of
> > some conflict between atmosphere and tcnative.
> >
> >
> >
> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
> > <rm...@gmail.com>wrote:
> >
> > > add it to your win %PATH%
> > >
> > > but you know it will not make your app faster in all cases?
> > >
> > > the message is a bit wrong on that point
> > >
> > > *Romain Manni-Bucau*
> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > http://rmannibucau.wordpress.com/>
> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > *Github: https://github.com/rmannibucau*
> > >
> > >
> > >
> > > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> > >
> > > > Okay, this has always concerned me, even when I see this in the log
> on
> > my
> > > > development machine, which uses tomee startup scripts, when I start
> > tomee
> > > > via Netbeans - Servers - right-click TomEE, and select Start or Stop.
> > > >
> > > >
> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default
> windows
> > > > service, I see the following in the log (APR is loaded successfully,
> > > > always)
> > > >
> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
> > > > Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener
> > > init
> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR
> > > > version 1.4.6.
> > > > Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener
> > > init
> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
> > > > [false], random [true].
> > > > Jan 31, 2013 1:57:19 AM org.apache.catalina.core.AprLifecycleListener
> > > > initializeSSL
> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
> > > >
> > > >
> > > > But when I use tomee/bin service.bat to install tomee windows service
> > > (and
> > > > when I start tomee server via Netbeans/tomee mgr scripts), I see the
> > > > following on development server (and now on production server)
> > > >
> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
> > > > Jan 31, 2013 9:01:43 AM org.apache.catalina.core.AprLifecycleListener
> > > init
> > > > INFO: The APR based Apache Tomcat Native library which allows optimal
> > > > performance in production environments was not found on the
> > > > java.library.path:
> > > >
> > > >
> > >
> >
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
> > > >
> > > > Please advise how i can get APR loaded successfully using tomee
> > > > scripts/service/etc...
> > > >
> > > >
> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
> > > > smithh032772@gmail.com> wrote:
> > > >
> > > > > Okay, now that I'm using tomee service exe, as per Romain's
> > suggestion,
> > > > > and already updated max perm size as per Mark's suggestion and
> > > restarted
> > > > > server on production server... a quick update:
> > > > >
> > > > > 1. Downloaded, installed, and
> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on
> production
> > > > server
> > > > > (Windows Server 2008 64bit 32GB RAM)
> > > > >
> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested
> > > earlier
> > > > >
> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from
> what I
> > > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly with
> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
> > > > > -Dtomee.keep-server-info=true, when running with tomee
> 1.5.2-SNAPSHOT
> > > > build
> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
> > > > >
> > > > > 4. Even though the web app (and tomee) has not been under load
> (yet,
> > > > > today) like it was yesterday morning and afternoon, I have not seen
> > > > issue #
> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2 (atmosphere
> > > > "(TomEE)/7"
> > > > > numberFormatException), as mentioned/discussed in OP and throughout
> > > this
> > > > > thread, ever since I added -Dtomee.keep-server-info=true
> > > > >
> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9
> to
> > > the
> > > > > mix, just to see/confirm if tomee will stop, unexpectedly, with a
> > > > > resulting-core-dump in tomee/bin like it did (at least) 3 times in
> > > > > tomcat7/bin, when this issue occurred in the last 3 days.
> > > > >
> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be released,
> > which
> > > > > includes fix for atmosphere "(TomEE)/7" numberFormatException,
> along
> > > with
> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
> > > 3.5-SNAPSHOT)
> > > > > and non-PrimeFaces-Push users (I assume).
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
> > > > rmannibucau@gmail.com
> > > > > > wrote:
> > > > >
> > > > >> tomcat supports websockets but no link with atmosphere (maybe
> > > > classloader
> > > > >> issue in your app, check deps)
> > > > >>
> > > > >> maybe try using tomee service exe instead of tomcat ones too
> > > > >>
> > > > >> *Romain Manni-Bucau*
> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > > >> *Blog: **http://rmannibucau.wordpress.com/*<
> > > > >> http://rmannibucau.wordpress.com/>
> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > > >> *Github: https://github.com/rmannibucau*
> > > > >>
> > > > >>
> > > >
> > >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
%PATH% -> apr
then regarding perf it is not tomee related but tomcat
it enhances perf in some cases and degrades them in some others...depends
the app
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH% ?
>
> will not make app faster in all cases? so, tomee (committers) does not
> recommend use of APR for faster performance? please let me know, because if
> I remove APR, then I'm assuming APR = tomcat native, and that already
> (along with other changes made today or this morning) resolves the issue
> where tomee (or tomcat7 service) does not 'stop' unexpectedly because of
> some conflict between atmosphere and tcnative.
>
>
>
> On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
> <rm...@gmail.com>wrote:
>
> > add it to your win %PATH%
> >
> > but you know it will not make your app faster in all cases?
> >
> > the message is a bit wrong on that point
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> >
> > > Okay, this has always concerned me, even when I see this in the log on
> my
> > > development machine, which uses tomee startup scripts, when I start
> tomee
> > > via Netbeans - Servers - right-click TomEE, and select Start or Stop.
> > >
> > >
> > > When I use tomcat7/bin service.bat to install 'tomcat7' default windows
> > > service, I see the following in the log (APR is loaded successfully,
> > > always)
> > >
> > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
> > > Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener
> > init
> > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR
> > > version 1.4.6.
> > > Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener
> > init
> > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
> > > [false], random [true].
> > > Jan 31, 2013 1:57:19 AM org.apache.catalina.core.AprLifecycleListener
> > > initializeSSL
> > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
> > >
> > >
> > > But when I use tomee/bin service.bat to install tomee windows service
> > (and
> > > when I start tomee server via Netbeans/tomee mgr scripts), I see the
> > > following on development server (and now on production server)
> > >
> > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
> > > Jan 31, 2013 9:01:43 AM org.apache.catalina.core.AprLifecycleListener
> > init
> > > INFO: The APR based Apache Tomcat Native library which allows optimal
> > > performance in production environments was not found on the
> > > java.library.path:
> > >
> > >
> >
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
> > >
> > > Please advise how i can get APR loaded successfully using tomee
> > > scripts/service/etc...
> > >
> > >
> > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
> > > smithh032772@gmail.com> wrote:
> > >
> > > > Okay, now that I'm using tomee service exe, as per Romain's
> suggestion,
> > > > and already updated max perm size as per Mark's suggestion and
> > restarted
> > > > server on production server... a quick update:
> > > >
> > > > 1. Downloaded, installed, and
> > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on production
> > > server
> > > > (Windows Server 2008 64bit 32GB RAM)
> > > >
> > > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested
> > earlier
> > > >
> > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from what I
> > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly with
> > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
> > > > -Dtomee.keep-server-info=true, when running with tomee 1.5.2-SNAPSHOT
> > > build
> > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
> > > >
> > > > 4. Even though the web app (and tomee) has not been under load (yet,
> > > > today) like it was yesterday morning and afternoon, I have not seen
> > > issue #
> > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2 (atmosphere
> > > "(TomEE)/7"
> > > > numberFormatException), as mentioned/discussed in OP and throughout
> > this
> > > > thread, ever since I added -Dtomee.keep-server-info=true
> > > >
> > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9 to
> > the
> > > > mix, just to see/confirm if tomee will stop, unexpectedly, with a
> > > > resulting-core-dump in tomee/bin like it did (at least) 3 times in
> > > > tomcat7/bin, when this issue occurred in the last 3 days.
> > > >
> > > > 6. still waiting patiently for Atmosphere 1.0.10 to be released,
> which
> > > > includes fix for atmosphere "(TomEE)/7" numberFormatException, along
> > with
> > > > other fixes that was targeting PrimeFaces Push (PrimeFaces
> > 3.5-SNAPSHOT)
> > > > and non-PrimeFaces-Push users (I assume).
> > > >
> > > >
> > > >
> > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
> > > rmannibucau@gmail.com
> > > > > wrote:
> > > >
> > > >> tomcat supports websockets but no link with atmosphere (maybe
> > > classloader
> > > >> issue in your app, check deps)
> > > >>
> > > >> maybe try using tomee service exe instead of tomcat ones too
> > > >>
> > > >> *Romain Manni-Bucau*
> > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > >> *Blog: **http://rmannibucau.wordpress.com/*<
> > > >> http://rmannibucau.wordpress.com/>
> > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > >> *Github: https://github.com/rmannibucau*
> > > >>
> > > >>
> > >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH% ?
will not make app faster in all cases? so, tomee (committers) does not
recommend use of APR for faster performance? please let me know, because if
I remove APR, then I'm assuming APR = tomcat native, and that already
(along with other changes made today or this morning) resolves the issue
where tomee (or tomcat7 service) does not 'stop' unexpectedly because of
some conflict between atmosphere and tcnative.
On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> add it to your win %PATH%
>
> but you know it will not make your app faster in all cases?
>
> the message is a bit wrong on that point
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
>
> > Okay, this has always concerned me, even when I see this in the log on my
> > development machine, which uses tomee startup scripts, when I start tomee
> > via Netbeans - Servers - right-click TomEE, and select Start or Stop.
> >
> >
> > When I use tomcat7/bin service.bat to install 'tomcat7' default windows
> > service, I see the following in the log (APR is loaded successfully,
> > always)
> >
> > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
> > Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener
> init
> > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR
> > version 1.4.6.
> > Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener
> init
> > INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
> > [false], random [true].
> > Jan 31, 2013 1:57:19 AM org.apache.catalina.core.AprLifecycleListener
> > initializeSSL
> > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
> >
> >
> > But when I use tomee/bin service.bat to install tomee windows service
> (and
> > when I start tomee server via Netbeans/tomee mgr scripts), I see the
> > following on development server (and now on production server)
> >
> > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
> > Jan 31, 2013 9:01:43 AM org.apache.catalina.core.AprLifecycleListener
> init
> > INFO: The APR based Apache Tomcat Native library which allows optimal
> > performance in production environments was not found on the
> > java.library.path:
> >
> >
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
> >
> > Please advise how i can get APR loaded successfully using tomee
> > scripts/service/etc...
> >
> >
> > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
> > smithh032772@gmail.com> wrote:
> >
> > > Okay, now that I'm using tomee service exe, as per Romain's suggestion,
> > > and already updated max perm size as per Mark's suggestion and
> restarted
> > > server on production server... a quick update:
> > >
> > > 1. Downloaded, installed, and
> > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on production
> > server
> > > (Windows Server 2008 64bit 32GB RAM)
> > >
> > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested
> earlier
> > >
> > > 3. Reverted to and running Atmosphere 1.0.6; why? because from what I
> > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly with
> > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
> > > -Dtomee.keep-server-info=true, when running with tomee 1.5.2-SNAPSHOT
> > build
> > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
> > >
> > > 4. Even though the web app (and tomee) has not been under load (yet,
> > > today) like it was yesterday morning and afternoon, I have not seen
> > issue #
> > > 1 (tomee stopping, unexpectedly, with core dump) or # 2 (atmosphere
> > "(TomEE)/7"
> > > numberFormatException), as mentioned/discussed in OP and throughout
> this
> > > thread, ever since I added -Dtomee.keep-server-info=true
> > >
> > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9 to
> the
> > > mix, just to see/confirm if tomee will stop, unexpectedly, with a
> > > resulting-core-dump in tomee/bin like it did (at least) 3 times in
> > > tomcat7/bin, when this issue occurred in the last 3 days.
> > >
> > > 6. still waiting patiently for Atmosphere 1.0.10 to be released, which
> > > includes fix for atmosphere "(TomEE)/7" numberFormatException, along
> with
> > > other fixes that was targeting PrimeFaces Push (PrimeFaces
> 3.5-SNAPSHOT)
> > > and non-PrimeFaces-Push users (I assume).
> > >
> > >
> > >
> > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
> > rmannibucau@gmail.com
> > > > wrote:
> > >
> > >> tomcat supports websockets but no link with atmosphere (maybe
> > classloader
> > >> issue in your app, check deps)
> > >>
> > >> maybe try using tomee service exe instead of tomcat ones too
> > >>
> > >> *Romain Manni-Bucau*
> > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > >> *Blog: **http://rmannibucau.wordpress.com/*<
> > >> http://rmannibucau.wordpress.com/>
> > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > >> *Github: https://github.com/rmannibucau*
> > >>
> > >>
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
add it to your win %PATH%
but you know it will not make your app faster in all cases?
the message is a bit wrong on that point
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> Okay, this has always concerned me, even when I see this in the log on my
> development machine, which uses tomee startup scripts, when I start tomee
> via Netbeans - Servers - right-click TomEE, and select Start or Stop.
>
>
> When I use tomcat7/bin service.bat to install 'tomcat7' default windows
> service, I see the following in the log (APR is loaded successfully,
> always)
>
> 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
> Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR
> version 1.4.6.
> Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
> [false], random [true].
> Jan 31, 2013 1:57:19 AM org.apache.catalina.core.AprLifecycleListener
> initializeSSL
> INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
>
>
> But when I use tomee/bin service.bat to install tomee windows service (and
> when I start tomee server via Netbeans/tomee mgr scripts), I see the
> following on development server (and now on production server)
>
> 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
> Jan 31, 2013 9:01:43 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: The APR based Apache Tomcat Native library which allows optimal
> performance in production environments was not found on the
> java.library.path:
>
> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
>
> Please advise how i can get APR loaded successfully using tomee
> scripts/service/etc...
>
>
> On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
> smithh032772@gmail.com> wrote:
>
> > Okay, now that I'm using tomee service exe, as per Romain's suggestion,
> > and already updated max perm size as per Mark's suggestion and restarted
> > server on production server... a quick update:
> >
> > 1. Downloaded, installed, and
> > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on production
> server
> > (Windows Server 2008 64bit 32GB RAM)
> >
> > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested earlier
> >
> > 3. Reverted to and running Atmosphere 1.0.6; why? because from what I
> > remember/witnessed, tomee/tomcat7 service stopped unexpectedly with
> > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
> > -Dtomee.keep-server-info=true, when running with tomee 1.5.2-SNAPSHOT
> build
> > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
> >
> > 4. Even though the web app (and tomee) has not been under load (yet,
> > today) like it was yesterday morning and afternoon, I have not seen
> issue #
> > 1 (tomee stopping, unexpectedly, with core dump) or # 2 (atmosphere
> "(TomEE)/7"
> > numberFormatException), as mentioned/discussed in OP and throughout this
> > thread, ever since I added -Dtomee.keep-server-info=true
> >
> > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9 to the
> > mix, just to see/confirm if tomee will stop, unexpectedly, with a
> > resulting-core-dump in tomee/bin like it did (at least) 3 times in
> > tomcat7/bin, when this issue occurred in the last 3 days.
> >
> > 6. still waiting patiently for Atmosphere 1.0.10 to be released, which
> > includes fix for atmosphere "(TomEE)/7" numberFormatException, along with
> > other fixes that was targeting PrimeFaces Push (PrimeFaces 3.5-SNAPSHOT)
> > and non-PrimeFaces-Push users (I assume).
> >
> >
> >
> > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > > wrote:
> >
> >> tomcat supports websockets but no link with atmosphere (maybe
> classloader
> >> issue in your app, check deps)
> >>
> >> maybe try using tomee service exe instead of tomcat ones too
> >>
> >> *Romain Manni-Bucau*
> >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> >> *Blog: **http://rmannibucau.wordpress.com/*<
> >> http://rmannibucau.wordpress.com/>
> >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> >> *Github: https://github.com/rmannibucau*
> >>
> >>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Okay, this has always concerned me, even when I see this in the log on my
development machine, which uses tomee startup scripts, when I start tomee
via Netbeans - Servers - right-click TomEE, and select Start or Stop.
When I use tomcat7/bin service.bat to install 'tomcat7' default windows
service, I see the following in the log (APR is loaded successfully, always)
2013-01-31 01:57:12 Commons Daemon procrun stderr initialized
Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR
version 1.4.6.
Jan 31, 2013 1:57:17 AM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
[false], random [true].
Jan 31, 2013 1:57:19 AM org.apache.catalina.core.AprLifecycleListener
initializeSSL
INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012)
But when I use tomee/bin service.bat to install tomee windows service (and
when I start tomee server via Netbeans/tomee mgr scripts), I see the
following on development server (and now on production server)
2013-01-31 09:01:41 Commons Daemon procrun stderr initialized
Jan 31, 2013 9:01:43 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
Please advise how i can get APR loaded successfully using tomee
scripts/service/etc...
On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> Okay, now that I'm using tomee service exe, as per Romain's suggestion,
> and already updated max perm size as per Mark's suggestion and restarted
> server on production server... a quick update:
>
> 1. Downloaded, installed, and
> running apache-tomee-1.5.2-20130130.041108-54-plus.zip on production server
> (Windows Server 2008 64bit 32GB RAM)
>
> 2. Also added -Dtomee.keep-server-info=true, as Romain suggested earlier
>
> 3. Reverted to and running Atmosphere 1.0.6; why? because from what I
> remember/witnessed, tomee/tomcat7 service stopped unexpectedly with
> Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
> -Dtomee.keep-server-info=true, when running with tomee 1.5.2-SNAPSHOT build
> 2013-01-28 between the dates of 2013-01-28 and 2013-01-30
>
> 4. Even though the web app (and tomee) has not been under load (yet,
> today) like it was yesterday morning and afternoon, I have not seen issue #
> 1 (tomee stopping, unexpectedly, with core dump) or # 2 (atmosphere "(TomEE)/7"
> numberFormatException), as mentioned/discussed in OP and throughout this
> thread, ever since I added -Dtomee.keep-server-info=true
>
> 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9 to the
> mix, just to see/confirm if tomee will stop, unexpectedly, with a
> resulting-core-dump in tomee/bin like it did (at least) 3 times in
> tomcat7/bin, when this issue occurred in the last 3 days.
>
> 6. still waiting patiently for Atmosphere 1.0.10 to be released, which
> includes fix for atmosphere "(TomEE)/7" numberFormatException, along with
> other fixes that was targeting PrimeFaces Push (PrimeFaces 3.5-SNAPSHOT)
> and non-PrimeFaces-Push users (I assume).
>
>
>
> On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau <rmannibucau@gmail.com
> > wrote:
>
>> tomcat supports websockets but no link with atmosphere (maybe classloader
>> issue in your app, check deps)
>>
>> maybe try using tomee service exe instead of tomcat ones too
>>
>> *Romain Manni-Bucau*
>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> *Blog: **http://rmannibucau.wordpress.com/*<
>> http://rmannibucau.wordpress.com/>
>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> *Github: https://github.com/rmannibucau*
>>
>>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Okay, now that I'm using tomee service exe, as per Romain's suggestion, and
already updated max perm size as per Mark's suggestion and restarted server
on production server... a quick update:
1. Downloaded, installed, and
running apache-tomee-1.5.2-20130130.041108-54-plus.zip on production server
(Windows Server 2008 64bit 32GB RAM)
2. Also added -Dtomee.keep-server-info=true, as Romain suggested earlier
3. Reverted to and running Atmosphere 1.0.6; why? because from what I
remember/witnessed, tomee/tomcat7 service stopped unexpectedly with
Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the
-Dtomee.keep-server-info=true, when running with tomee 1.5.2-SNAPSHOT build
2013-01-28 between the dates of 2013-01-28 and 2013-01-30
4. Even though the web app (and tomee) has not been under load (yet, today)
like it was yesterday morning and afternoon, I have not seen issue # 1
(tomee stopping, unexpectedly, with core dump) or # 2 (atmosphere "(TomEE)/7"
numberFormatException), as mentioned/discussed in OP and throughout this
thread, ever since I added -Dtomee.keep-server-info=true
5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9 to the
mix, just to see/confirm if tomee will stop, unexpectedly, with a
resulting-core-dump in tomee/bin like it did (at least) 3 times in
tomcat7/bin, when this issue occurred in the last 3 days.
6. still waiting patiently for Atmosphere 1.0.10 to be released, which
includes fix for atmosphere "(TomEE)/7" numberFormatException, along with
other fixes that was targeting PrimeFaces Push (PrimeFaces 3.5-SNAPSHOT)
and non-PrimeFaces-Push users (I assume).
On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> tomcat supports websockets but no link with atmosphere (maybe classloader
> issue in your app, check deps)
>
> maybe try using tomee service exe instead of tomcat ones too
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
tomcat supports websockets but no link with atmosphere (maybe classloader
issue in your app, check deps)
maybe try using tomee service exe instead of tomcat ones too
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/1/31 Howard W. Smith, Jr. <sm...@gmail.com>
> Are you saying, does it work without tomee 1.5.2 SNAPSHOT integrated? I
> have not tested that, but atmosphere does work with recent builds of TomEE
> 1.5.2 SNAPSHOT, but it core dumps unexpectedly, under load or after some
> time has passed. I'm waiting to see if it core dumps unexpectedly again
> after adding the system property that you recommended earlier.
>
> By the way, I did see websockets in tomcat 7.0.35 change log. I don't know
> if that could possibly be the cause. :-)
>
> One question. Windows service dialog has properties to restart service if
> service fails but tomcat7w.exe does not. I set those properties yesterday
> via window's Services dialog but I think tomcat7w.exe overwrites those
> properties, since I generally use tomcat7w.exe to start stop service on
> production server.
> On Jan 31, 2013 1:12 AM, "Romain Manni-Bucau" <rm...@gmail.com>
> wrote:
>
> > Do you know if atmo works with last tomcat?
> > Le 31 janv. 2013 06:36, "Howard W. Smith, Jr." <sm...@gmail.com>
> a
> > écrit :
> >
> > > Atmosphere issue 875 added[1]
> > >
> > > [1] https://github.com/Atmosphere/atmosphere/issues/875
> > >
> > >
> > > On Wed, Jan 30, 2013 at 10:43 PM, Howard W. Smith, Jr. <
> > > smithh032772@gmail.com> wrote:
> > >
> > > > On Wed, Jan 30, 2013 at 10:34 PM, David Blevins <
> > david.blevins@gmail.com
> > > >wrote:
> > > >
> > > >> On Jan 30, 2013, at 7:00 PM, "Howard W. Smith, Jr." <
> > > >> smithh032772@gmail.com> wrote:
> > > >>
> > > >> > Again/FYI, earlier this afternoon (around 12pm EST or EDT), I
> > reverted
> > > >> to
> > > >> > TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34) and
> > > >> > Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was
> working
> > > >> well
> > > >> > with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
> > > >>
> > > >> Just to make sure it wasn't lost in the cracks, we did identify an
> > issue
> > > >> with Atomosphere/TomEE. In this file in the Atomosphere:
> > > >>
> > > >>
> > > >>
> > >
> >
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
> > > >>
> > > >> It has the following code:
> > > >>
> > > >> String[] tomcatVersion =
> > > >>
> > config.getServletContext().getServerInfo().substring(14).split("\\.");
> > > >>
> > > >> This won't work because of recent updates in TomEE 1.5.2-SNAPSHOT
> > which
> > > >> append "(TomEE)" onto the ServerInfo string -- only skipping 14
> > > characters
> > > >> is not enough. Romain gave the workaround of reverting to the old,
> > > >> unmodified, ServerInfo string via the System property
> > > >> "tomee.keep-server-info=true"
> > > >>
> > > >> Note that if the "tomee.keep-server-info" was successfully set to
> > true,
> > > >> it will be logged on INFO level. If the default of false is used,
> the
> > > >> checking of the 'tomee.keep-server-info' is still logged, but on
> DEBUG
> > > >> level.
> > > >>
> > > >> Is it possible you can confirm that you have tried the system
> > property,
> > > >> see the expected log output, and the issue still exists?
> > > >>
> > > >>
> > > >> -David
> > > >>
> > > >>
> > > > sometime earlier, i added the system property to tomcat7w.exe java
> > > > options, and it is currently running against earlier version of TomEE
> > > > 1.5.2-SNAPSHOT (that has tomcat 7.0.34 dependency).
> > > >
> > > > Next/now, I will download latest version of TomEE 1.5.2-SNAPSHOT, and
> > > > install to production server, and leave it running, and see what
> > happens.
> > > > honestly, I don't think the 'atmosphere issue' is causing the
> > > tomee/tomcat7
> > > > service to 'stop' running. that is possibly caused by
> another/separate
> > > > issue (either atmosphere or tomcat7.0.35 issue); that's my opinion.
> > > >
> > > >
> > >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Are you saying, does it work without tomee 1.5.2 SNAPSHOT integrated? I
have not tested that, but atmosphere does work with recent builds of TomEE
1.5.2 SNAPSHOT, but it core dumps unexpectedly, under load or after some
time has passed. I'm waiting to see if it core dumps unexpectedly again
after adding the system property that you recommended earlier.
By the way, I did see websockets in tomcat 7.0.35 change log. I don't know
if that could possibly be the cause. :-)
One question. Windows service dialog has properties to restart service if
service fails but tomcat7w.exe does not. I set those properties yesterday
via window's Services dialog but I think tomcat7w.exe overwrites those
properties, since I generally use tomcat7w.exe to start stop service on
production server.
On Jan 31, 2013 1:12 AM, "Romain Manni-Bucau" <rm...@gmail.com> wrote:
> Do you know if atmo works with last tomcat?
> Le 31 janv. 2013 06:36, "Howard W. Smith, Jr." <sm...@gmail.com> a
> écrit :
>
> > Atmosphere issue 875 added[1]
> >
> > [1] https://github.com/Atmosphere/atmosphere/issues/875
> >
> >
> > On Wed, Jan 30, 2013 at 10:43 PM, Howard W. Smith, Jr. <
> > smithh032772@gmail.com> wrote:
> >
> > > On Wed, Jan 30, 2013 at 10:34 PM, David Blevins <
> david.blevins@gmail.com
> > >wrote:
> > >
> > >> On Jan 30, 2013, at 7:00 PM, "Howard W. Smith, Jr." <
> > >> smithh032772@gmail.com> wrote:
> > >>
> > >> > Again/FYI, earlier this afternoon (around 12pm EST or EDT), I
> reverted
> > >> to
> > >> > TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34) and
> > >> > Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was working
> > >> well
> > >> > with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
> > >>
> > >> Just to make sure it wasn't lost in the cracks, we did identify an
> issue
> > >> with Atomosphere/TomEE. In this file in the Atomosphere:
> > >>
> > >>
> > >>
> >
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
> > >>
> > >> It has the following code:
> > >>
> > >> String[] tomcatVersion =
> > >>
> config.getServletContext().getServerInfo().substring(14).split("\\.");
> > >>
> > >> This won't work because of recent updates in TomEE 1.5.2-SNAPSHOT
> which
> > >> append "(TomEE)" onto the ServerInfo string -- only skipping 14
> > characters
> > >> is not enough. Romain gave the workaround of reverting to the old,
> > >> unmodified, ServerInfo string via the System property
> > >> "tomee.keep-server-info=true"
> > >>
> > >> Note that if the "tomee.keep-server-info" was successfully set to
> true,
> > >> it will be logged on INFO level. If the default of false is used, the
> > >> checking of the 'tomee.keep-server-info' is still logged, but on DEBUG
> > >> level.
> > >>
> > >> Is it possible you can confirm that you have tried the system
> property,
> > >> see the expected log output, and the issue still exists?
> > >>
> > >>
> > >> -David
> > >>
> > >>
> > > sometime earlier, i added the system property to tomcat7w.exe java
> > > options, and it is currently running against earlier version of TomEE
> > > 1.5.2-SNAPSHOT (that has tomcat 7.0.34 dependency).
> > >
> > > Next/now, I will download latest version of TomEE 1.5.2-SNAPSHOT, and
> > > install to production server, and leave it running, and see what
> happens.
> > > honestly, I don't think the 'atmosphere issue' is causing the
> > tomee/tomcat7
> > > service to 'stop' running. that is possibly caused by another/separate
> > > issue (either atmosphere or tomcat7.0.35 issue); that's my opinion.
> > >
> > >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Do you know if atmo works with last tomcat?
Le 31 janv. 2013 06:36, "Howard W. Smith, Jr." <sm...@gmail.com> a
écrit :
> Atmosphere issue 875 added[1]
>
> [1] https://github.com/Atmosphere/atmosphere/issues/875
>
>
> On Wed, Jan 30, 2013 at 10:43 PM, Howard W. Smith, Jr. <
> smithh032772@gmail.com> wrote:
>
> > On Wed, Jan 30, 2013 at 10:34 PM, David Blevins <david.blevins@gmail.com
> >wrote:
> >
> >> On Jan 30, 2013, at 7:00 PM, "Howard W. Smith, Jr." <
> >> smithh032772@gmail.com> wrote:
> >>
> >> > Again/FYI, earlier this afternoon (around 12pm EST or EDT), I reverted
> >> to
> >> > TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34) and
> >> > Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was working
> >> well
> >> > with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
> >>
> >> Just to make sure it wasn't lost in the cracks, we did identify an issue
> >> with Atomosphere/TomEE. In this file in the Atomosphere:
> >>
> >>
> >>
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
> >>
> >> It has the following code:
> >>
> >> String[] tomcatVersion =
> >> config.getServletContext().getServerInfo().substring(14).split("\\.");
> >>
> >> This won't work because of recent updates in TomEE 1.5.2-SNAPSHOT which
> >> append "(TomEE)" onto the ServerInfo string -- only skipping 14
> characters
> >> is not enough. Romain gave the workaround of reverting to the old,
> >> unmodified, ServerInfo string via the System property
> >> "tomee.keep-server-info=true"
> >>
> >> Note that if the "tomee.keep-server-info" was successfully set to true,
> >> it will be logged on INFO level. If the default of false is used, the
> >> checking of the 'tomee.keep-server-info' is still logged, but on DEBUG
> >> level.
> >>
> >> Is it possible you can confirm that you have tried the system property,
> >> see the expected log output, and the issue still exists?
> >>
> >>
> >> -David
> >>
> >>
> > sometime earlier, i added the system property to tomcat7w.exe java
> > options, and it is currently running against earlier version of TomEE
> > 1.5.2-SNAPSHOT (that has tomcat 7.0.34 dependency).
> >
> > Next/now, I will download latest version of TomEE 1.5.2-SNAPSHOT, and
> > install to production server, and leave it running, and see what happens.
> > honestly, I don't think the 'atmosphere issue' is causing the
> tomee/tomcat7
> > service to 'stop' running. that is possibly caused by another/separate
> > issue (either atmosphere or tomcat7.0.35 issue); that's my opinion.
> >
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Atmosphere issue 875 added[1]
[1] https://github.com/Atmosphere/atmosphere/issues/875
On Wed, Jan 30, 2013 at 10:43 PM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> On Wed, Jan 30, 2013 at 10:34 PM, David Blevins <da...@gmail.com>wrote:
>
>> On Jan 30, 2013, at 7:00 PM, "Howard W. Smith, Jr." <
>> smithh032772@gmail.com> wrote:
>>
>> > Again/FYI, earlier this afternoon (around 12pm EST or EDT), I reverted
>> to
>> > TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34) and
>> > Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was working
>> well
>> > with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
>>
>> Just to make sure it wasn't lost in the cracks, we did identify an issue
>> with Atomosphere/TomEE. In this file in the Atomosphere:
>>
>>
>> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
>>
>> It has the following code:
>>
>> String[] tomcatVersion =
>> config.getServletContext().getServerInfo().substring(14).split("\\.");
>>
>> This won't work because of recent updates in TomEE 1.5.2-SNAPSHOT which
>> append "(TomEE)" onto the ServerInfo string -- only skipping 14 characters
>> is not enough. Romain gave the workaround of reverting to the old,
>> unmodified, ServerInfo string via the System property
>> "tomee.keep-server-info=true"
>>
>> Note that if the "tomee.keep-server-info" was successfully set to true,
>> it will be logged on INFO level. If the default of false is used, the
>> checking of the 'tomee.keep-server-info' is still logged, but on DEBUG
>> level.
>>
>> Is it possible you can confirm that you have tried the system property,
>> see the expected log output, and the issue still exists?
>>
>>
>> -David
>>
>>
> sometime earlier, i added the system property to tomcat7w.exe java
> options, and it is currently running against earlier version of TomEE
> 1.5.2-SNAPSHOT (that has tomcat 7.0.34 dependency).
>
> Next/now, I will download latest version of TomEE 1.5.2-SNAPSHOT, and
> install to production server, and leave it running, and see what happens.
> honestly, I don't think the 'atmosphere issue' is causing the tomee/tomcat7
> service to 'stop' running. that is possibly caused by another/separate
> issue (either atmosphere or tomcat7.0.35 issue); that's my opinion.
>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Wed, Jan 30, 2013 at 10:34 PM, David Blevins <da...@gmail.com>wrote:
> On Jan 30, 2013, at 7:00 PM, "Howard W. Smith, Jr." <
> smithh032772@gmail.com> wrote:
>
> > Again/FYI, earlier this afternoon (around 12pm EST or EDT), I reverted to
> > TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34) and
> > Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was working well
> > with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
>
> Just to make sure it wasn't lost in the cracks, we did identify an issue
> with Atomosphere/TomEE. In this file in the Atomosphere:
>
>
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
>
> It has the following code:
>
> String[] tomcatVersion =
> config.getServletContext().getServerInfo().substring(14).split("\\.");
>
> This won't work because of recent updates in TomEE 1.5.2-SNAPSHOT which
> append "(TomEE)" onto the ServerInfo string -- only skipping 14 characters
> is not enough. Romain gave the workaround of reverting to the old,
> unmodified, ServerInfo string via the System property
> "tomee.keep-server-info=true"
>
> Note that if the "tomee.keep-server-info" was successfully set to true, it
> will be logged on INFO level. If the default of false is used, the
> checking of the 'tomee.keep-server-info' is still logged, but on DEBUG
> level.
>
> Is it possible you can confirm that you have tried the system property,
> see the expected log output, and the issue still exists?
>
>
> -David
>
>
sometime earlier, i added the system property to tomcat7w.exe java options,
and it is currently running against earlier version of TomEE 1.5.2-SNAPSHOT
(that has tomcat 7.0.34 dependency).
Next/now, I will download latest version of TomEE 1.5.2-SNAPSHOT, and
install to production server, and leave it running, and see what happens.
honestly, I don't think the 'atmosphere issue' is causing the tomee/tomcat7
service to 'stop' running. that is possibly caused by another/separate
issue (either atmosphere or tomcat7.0.35 issue); that's my opinion.
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
Posted by David Blevins <da...@gmail.com>.
On Jan 30, 2013, at 7:00 PM, "Howard W. Smith, Jr." <sm...@gmail.com> wrote:
> Again/FYI, earlier this afternoon (around 12pm EST or EDT), I reverted to
> TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34) and
> Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was working well
> with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
Just to make sure it wasn't lost in the cracks, we did identify an issue with Atomosphere/TomEE. In this file in the Atomosphere:
https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
It has the following code:
String[] tomcatVersion = config.getServletContext().getServerInfo().substring(14).split("\\.");
This won't work because of recent updates in TomEE 1.5.2-SNAPSHOT which append "(TomEE)" onto the ServerInfo string -- only skipping 14 characters is not enough. Romain gave the workaround of reverting to the old, unmodified, ServerInfo string via the System property "tomee.keep-server-info=true"
Note that if the "tomee.keep-server-info" was successfully set to true, it will be logged on INFO level. If the default of false is used, the checking of the 'tomee.keep-server-info' is still logged, but on DEBUG level.
Is it possible you can confirm that you have tried the system property, see the expected log output, and the issue still exists?
-David
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Since these issues started when I started using Atmosphere 1.0.8 and 1.0.9
with TomEE 1.5.2-SNAPSHOT (2013-01-28), I assuming that this is either a
tomcat7.0.35 or Atmosphere issue.
Please let me know if I should create a tomcat issue/jira or atmosphere
issue on atmosphere github.
Again/FYI, earlier this afternoon (around 12pm EST or EDT), I reverted to
TomEE 1.5.2-SNAPSHOT (2013-01-14, which is using tomcat7.0.34) and
Atmosphere 1.0.6, I don't see an issue. Atmosphere 1.0.8 was working well
with TomEE 1.5.2-SNAPSHOT (2013-01-14), too.
thanks,
Howard
On Wed, Jan 30, 2013 at 9:53 PM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> UPDATE:
>
> My apologies, I have core dumps and seemingly-to-be heap dump files as
> well in my tomcat7.0.35/bin folder at 3 different times that I experienced
> this problem. I am seeing atmosphere in these files.
>
> what is the best way for me to share heap dump text files? should I create
> an TOMEE JIRA and then attach the files, or should I copy/paste the content
> of the files here?
>
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
UPDATE:
My apologies, I have core dumps and seemingly-to-be heap dump files as well
in my tomcat7.0.35/bin folder at 3 different times that I experienced this
problem. I am seeing atmosphere in these files.
what is the best way for me to share heap dump text files? should I create
an TOMEE JIRA and then attach the files, or should I copy/paste the content
of the files here?
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
Interesting, noted, and thanks Mark. I did see jstack on a tomcat wikki
page that I was reading earlier today. I will have to try that.
On Wed, Jan 30, 2013 at 5:54 PM, Mark Struberg <st...@yahoo.de> wrote:
> I think under Windows it's catalina.bat.
>
> And the logs usually go under ./logs/...
>
>
> What I do whenever tomcat or another java process dies is to send a
> SIGINT. Which ich kill -3 [processid] under linux, and there is a special
> command for it under windows I think. Might be the jstack command if I
> remember correctly.
> This dumps all the Thread infos - including full stack traces of each
> Thread - and continues the process normally. Do this a few times in a 1
> second interval and you will get a good picture where it's stuck.
>
> LieGrue,
> strub
>
> >
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
Posted by Mark Struberg <st...@yahoo.de>.
I think under Windows it's catalina.bat.
And the logs usually go under ./logs/...
What I do whenever tomcat or another java process dies is to send a SIGINT. Which ich kill -3 [processid] under linux, and there is a special command for it under windows I think. Might be the jstack command if I remember correctly.
This dumps all the Thread infos - including full stack traces of each Thread - and continues the process normally. Do this a few times in a 1 second interval and you will get a good picture where it's stuck.
LieGrue,
strub
----- Original Message -----
> From: "Howard W. Smith, Jr." <sm...@gmail.com>
> To: users@tomee.apache.org
> Cc:
> Sent: Wednesday, January 30, 2013 11:11 PM
> Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
>
> On Wed, Jan 30, 2013 at 5:04 PM, Romain Manni-Bucau
> <rm...@gmail.com>wrote:
>
>> Catalina.sh run?
>> >
>>
>
> Hmmm, okay, and when I start tomee via Catalina.sh, will the logs tell me
> something when tomee stops?
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Wed, Jan 30, 2013 at 5:04 PM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> Catalina.sh run?
> >
>
Hmmm, okay, and when I start tomee via Catalina.sh, will the logs tell me
something when tomee stops?
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Catalina.sh run?
Le 30 janv. 2013 21:38, "Howard W. Smith, Jr." <sm...@gmail.com> a
écrit :
> On Wed, Jan 30, 2013 at 3:16 PM, Romain Manni-Bucau
> <rm...@gmail.com>wrote:
>
> > Try to start it manually. Using the os when there is an issue never works
> > >
> >
>
> How to start it manually? If I don't start it as a Windows Service, that
> means I need to remain logged into the windows 2008 server as administrator
> (which is not a problem, of course).
>
> I might as well tell you now... when I started using TomEE 1.5.1-SNAPSHOT
> on production server, I was 'not' able to use tomee/bin/service.bat to
> install/create tomee 32bit or 64bit windows service, so I downloaded
> tomcat7.0.32+, and ran tomcat7/bin/service.bat and it worked, immediately,
> without issue. I think I reported this to tomee user list when TomEE 1.5.1
> was in development, but never got that to work, and I think, per my
> understanding, tomee does not have test cases for Windows boxes/servers.
>
> So, i am currently (and have been) using tomcat7 windows service to start
> tomee container, and I do all that via tomcat7w.exe and populate Java
> options with tomee-specific stuff/config.
>
> so, does tomcat7w.exe = 'using the os'?
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Wed, Jan 30, 2013 at 3:16 PM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> Try to start it manually. Using the os when there is an issue never works
> >
>
How to start it manually? If I don't start it as a Windows Service, that
means I need to remain logged into the windows 2008 server as administrator
(which is not a problem, of course).
I might as well tell you now... when I started using TomEE 1.5.1-SNAPSHOT
on production server, I was 'not' able to use tomee/bin/service.bat to
install/create tomee 32bit or 64bit windows service, so I downloaded
tomcat7.0.32+, and ran tomcat7/bin/service.bat and it worked, immediately,
without issue. I think I reported this to tomee user list when TomEE 1.5.1
was in development, but never got that to work, and I think, per my
understanding, tomee does not have test cases for Windows boxes/servers.
So, i am currently (and have been) using tomcat7 windows service to start
tomee container, and I do all that via tomcat7w.exe and populate Java
options with tomee-specific stuff/config.
so, does tomcat7w.exe = 'using the os'?
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Try to start it manually. Using the os when there is an issue never works
Le 30 janv. 2013 20:43, "Howard W. Smith, Jr." <sm...@gmail.com> a
écrit :
> On Wed, Jan 30, 2013 at 12:44 PM, Howard W. Smith, Jr. <
> smithh032772@gmail.com> wrote:
>
> > On Wed, Jan 30, 2013 at 1:14 AM, Romain Manni-Bucau <
> rmannibucau@gmail.com
> > > wrote:
> >
> >> Add -Dtomee.keep-server-info=true ... but that's an atmosphere issue. It
> >> shouldn't rely on this to get the tomcat version.
> >> Le 30 janv. 2013 04:26, "Howard W. Smith, Jr." <sm...@gmail.com>
> a
> >> écrit :
> >>
> >> >
> >>
> >
> > Okay, i need to add that -D-tomee.keep-server-info=true, but the latest
> > version of TomEE 1.5.2-SNAPSHOT (2013-01-28) that I downloaded/installed
> on
> > Windows Server 2008 R2 (32GB RAM) was stopping too much on my endusers,
> so
> > I had to revert to the 2013-01-14 version of TomEE 1.5.2-SNAPSHOT. :)
> >
> >
> >
> Okay, I was wondering if TomEE 1.5.2-SNAPSHOT was now using (and when TomEE
> 1.5.2-SNAPSHOT started using) Tomcat 7.0.35, and I see that TOMEE-740[1]
> was when TomEE 1.5.2-SNAPSHOT upgraded to Tomcat 7.0.35. Since I listen in
> on tomcat user list, I do remember the announcement of tomcat 7.0.35, and I
> do remember a known issue with 7.0.35, and I heard that it was best to wait
> for 7.0.36, which was coming soon/ASAP. I wonder if the upgrade to 7.0.35
> is the cause of the issue that I'm reporting here and in the OP.
>
> I see that Tomcat 7.0.35 dependency was added to TomEE 1.5.2-SNAPSHOT on
> 2013-01-17. As mentioned earlier, I had no issues when TomEE 1.5.2-SNAPSHOT
> was using Tomcat 7.0.34 dependency.
>
> Now, I'm reviewing TomEE 1.5.2-SNAPSHOT issue list (and/or change log) [2]
> and Tomcat 7.0.35 change log[3].
>
> [1] https://issues.apache.org/jira/browse/TOMEE-740
> [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TOMEE
> [3] http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Wed, Jan 30, 2013 at 12:44 PM, Howard W. Smith, Jr. <
smithh032772@gmail.com> wrote:
> On Wed, Jan 30, 2013 at 1:14 AM, Romain Manni-Bucau <rmannibucau@gmail.com
> > wrote:
>
>> Add -Dtomee.keep-server-info=true ... but that's an atmosphere issue. It
>> shouldn't rely on this to get the tomcat version.
>> Le 30 janv. 2013 04:26, "Howard W. Smith, Jr." <sm...@gmail.com> a
>> écrit :
>>
>> >
>>
>
> Okay, i need to add that -D-tomee.keep-server-info=true, but the latest
> version of TomEE 1.5.2-SNAPSHOT (2013-01-28) that I downloaded/installed on
> Windows Server 2008 R2 (32GB RAM) was stopping too much on my endusers, so
> I had to revert to the 2013-01-14 version of TomEE 1.5.2-SNAPSHOT. :)
>
>
>
Okay, I was wondering if TomEE 1.5.2-SNAPSHOT was now using (and when TomEE
1.5.2-SNAPSHOT started using) Tomcat 7.0.35, and I see that TOMEE-740[1]
was when TomEE 1.5.2-SNAPSHOT upgraded to Tomcat 7.0.35. Since I listen in
on tomcat user list, I do remember the announcement of tomcat 7.0.35, and I
do remember a known issue with 7.0.35, and I heard that it was best to wait
for 7.0.36, which was coming soon/ASAP. I wonder if the upgrade to 7.0.35
is the cause of the issue that I'm reporting here and in the OP.
I see that Tomcat 7.0.35 dependency was added to TomEE 1.5.2-SNAPSHOT on
2013-01-17. As mentioned earlier, I had no issues when TomEE 1.5.2-SNAPSHOT
was using Tomcat 7.0.34 dependency.
Now, I'm reviewing TomEE 1.5.2-SNAPSHOT issue list (and/or change log) [2]
and Tomcat 7.0.35 change log[3].
[1] https://issues.apache.org/jira/browse/TOMEE-740
[2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TOMEE
[3] http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Wed, Jan 30, 2013 at 1:14 AM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> Add -Dtomee.keep-server-info=true ... but that's an atmosphere issue. It
> shouldn't rely on this to get the tomcat version.
> Le 30 janv. 2013 04:26, "Howard W. Smith, Jr." <sm...@gmail.com> a
> écrit :
>
> >
>
Okay, i need to add that -D-tomee.keep-server-info=true, but the latest
version of TomEE 1.5.2-SNAPSHOT (2013-01-28) that I downloaded/installed on
Windows Server 2008 R2 (32GB RAM) was stopping too much on my endusers, so
I had to revert to the 2013-01-14 version of TomEE 1.5.2-SNAPSHOT. :)
Honestly, I have no way of debugging/troubleshooting this issue. Reverting
to earlier/stable version is all I know for now.
Of course, I'm quite sure I cannot build or assemble a test case that can
duplicate this issue.
I've noticed that Windows Server 2008 had a Software Protection Service
running and it seemed as though that was the possible cause of TomEE
1.5.2-SNAPSHOT (2013-01-28) windows service 'stopping'... The windows Event
Viewer was the only reliable logging method to track this.
When Atmosphere 1.0.10 is available/released, I will try to reinstall
2013-01-28 (or later) version of TomEE 1.5.2-SNAPSHOT on production server,
and hopefully, TomEE windows service will continue to run.
Again, I wish I knew what changed (if anything) between 2013-01-14 and
2013-01-28 that might be causing TomEE windows service to 'stop' running so
much now. The 2013-01-14 version of TomEE 1.5.2-SNAPSHOT was running very
well and stable between 01-18-2013 and 01-28-2013 (prior to installing
2013-01-28 version).
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Add -Dtomee.keep-server-info=true ... but that's an atmosphere issue. It
shouldn't rely on this to get the tomcat version.
Le 30 janv. 2013 04:26, "Howard W. Smith, Jr." <sm...@gmail.com> a
écrit :
> I didn't experience this issue while running Atmosphere 1.0.9, so i
> recompiled the project with Atmosphere 1.0.9, atmosphere-compat-tomcat.jar
> (tomcat6 jar) is in tomee/lib (as this has been standard procedure for me),
> and restarted tomee.
>
> also, i checked event log on the windows server, and wow, google update
> service was triggered and started to run one hour prior to tomee service
> stopping. i had to login to the server and restart tomee. i just disabled
> google update service and a dns client service running on the windows 2008
> server. i'm quite sure that i have no need of either of those services from
> running.
>
> i'm going to monitor logs in tomee/logs to see if atmosphere 1.0.9 is
> running good/okay with latest TomEE 1.5.2-SNAPSHOT.
>
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
I didn't experience this issue while running Atmosphere 1.0.9, so i
recompiled the project with Atmosphere 1.0.9, atmosphere-compat-tomcat.jar
(tomcat6 jar) is in tomee/lib (as this has been standard procedure for me),
and restarted tomee.
also, i checked event log on the windows server, and wow, google update
service was triggered and started to run one hour prior to tomee service
stopping. i had to login to the server and restart tomee. i just disabled
google update service and a dns client service running on the windows 2008
server. i'm quite sure that i have no need of either of those services from
running.
i'm going to monitor logs in tomee/logs to see if atmosphere 1.0.9 is
running good/okay with latest TomEE 1.5.2-SNAPSHOT.
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Tue, Jan 29, 2013 at 7:42 PM, David Blevins <da...@gmail.com>wrote:
>
> On Jan 29, 2013, at 4:04 PM, "Howard W. Smith, Jr." <
> smithh032772@gmail.com> wrote:
>
> > On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko
> > <kn...@gmail.com>wrote:
> >
> >> 2013/1/30 Caldarale, Charles R <Ch...@unisys.com>:
> >>>> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
> >>>> Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just
> died
> >> on me, nothing in server logs
> >>>
> >>>> Sending this to tomee/openejb and tomcat user mailing lists.
> >>>
> >>> Cross-posting is really frowned upon.
> >>>
> >>>> Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
> >> event
> >>>> SEVERE: Servlet.service() for servlet [Push Servlet] in context with
> >> path
> >>>> [/mcmsweb] threw exception
> >>>> java.lang.NumberFormatException: For input string: "(TomEE)/7"
> >>>> at java.lang.NumberFormatException.forInputString(Unknown Source)
> >>>> at java.lang.Integer.parseInt(Unknown Source)
> >>>> at java.lang.Integer.valueOf(Unknown Source)
> >>>> at
> >>
> org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
> >>>
> >>> Sure looks like an Atmosphere problem from here...
> >>>
> >>
> >> +1.
> >>
> >>
> >>
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
> >>
> >> That "bz51881" method... an example of what you should never do...
> >>
> >> It tries to parse a version string to "workaround" a bug that was
> >> properly fixed more than a year ago, and fails horribly.
> >>
> >> It is a normal practice to modify the "server info" value, e.g. [1].
> >> It is useless to rely on it. It is no wonder that the one used by
> >> TomEE is different from Tomcat.
> >>
> >> [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves
> >>
> >>
> >> Best regards,
> >> Konstantin Kolinko
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> > TomEE committers, per Konstantin's response above, can you let me know,
> if
> > this is TomEE or Atmosphere issue?
>
> Looks like an Atmosphere issue. It's basically doing:
>
> String[] tomcatVersion =
> config.getServletContext().getServerInfo().substring(14).split("\\.");
>
> The getServerInfo() method was updated to add "(TomEE)" in there so people
> can have more info on the flavor of Tomcat they're using.
>
>
> -David
>
>
Has there been any changes with TomEE 1.5.2-SNAPSHOT between 2013-01-14 and
2013-01-28 that might be related to this? I'm asking, because I just
reverted to an earlier version of Atmosphere (1.0.6), and the problem is
still occurring.
I went back in time and looked at the log files in tomee/logs, and this
error really only started happening 'after' I started using the latest
TomEE 1.5.2-SNAPSHOT as I reported in OP. :(
Even though I informed Atmosphere of any/all details (and responses from
tomcat and tomee) [1], I am thinking about reverting to the previous
version of TomEE 1.5.2-SNAPSHOT (2013-01-14) that has been running,
perfectly, without this issue.
After reverting to Atmosphere 1.0.6 (few hours ago) and running latest
TomEE 1.5.2-SNAPSHOT, I saw this exception in localhost log in tomee/logs
(below). :(
Jan 29, 2013 8:52:35 PM org.apache.catalina.core.StandardWrapperValve event
SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
[/mcmsweb] threw exception
java.lang.NumberFormatException: For input string: "(TomEE)/7"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at
org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
at
org.atmosphere.container.Tomcat7CometSupport.service(Tomcat7CometSupport.java:114)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.doService(Tomcat7AsyncSupportWithWebSocket.java:63)
at
org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:84)
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
at
org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1307)
at org.atmosphere.cpr.AtmosphereServlet.event(AtmosphereServlet.java:358)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilterEvent(ApplicationFilterChain.java:484)
at
org.apache.catalina.core.ApplicationFilterChain.doFilterEvent(ApplicationFilterChain.java:377)
at
org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:411)
at
org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:146)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:256)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at org.apache.catalina.valves.ValveBase.event(ValveBase.java:224)
at
org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:138)
at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:209)
at
org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:133)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at
org.apache.tomcat.util.net.AprEndpoint$SocketEventProcessor.run(AprEndpoint.java:1867)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
[1]
https://groups.google.com/forum/?fromgroups=#!topic/atmosphere-framework/RWuFZfeJu5s
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Tue, Jan 29, 2013 at 7:42 PM, David Blevins <da...@gmail.com>wrote:
>
>
> Looks like an Atmosphere issue. It's basically doing:
>
> String[] tomcatVersion =
> config.getServletContext().getServerInfo().substring(14).split("\\.");
>
> The getServerInfo() method was updated to add "(TomEE)" in there so people
> can have more info on the flavor of Tomcat they're using.
>
>
> -David
>
>
That's good to know. I already posted a question on atmosphere
googlegroups. will update that post with your response David. thanks!
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
Posted by David Blevins <da...@gmail.com>.
On Jan 29, 2013, at 4:04 PM, "Howard W. Smith, Jr." <sm...@gmail.com> wrote:
> On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko
> <kn...@gmail.com>wrote:
>
>> 2013/1/30 Caldarale, Charles R <Ch...@unisys.com>:
>>>> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
>>>> Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
>> on me, nothing in server logs
>>>
>>>> Sending this to tomee/openejb and tomcat user mailing lists.
>>>
>>> Cross-posting is really frowned upon.
>>>
>>>> Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
>> event
>>>> SEVERE: Servlet.service() for servlet [Push Servlet] in context with
>> path
>>>> [/mcmsweb] threw exception
>>>> java.lang.NumberFormatException: For input string: "(TomEE)/7"
>>>> at java.lang.NumberFormatException.forInputString(Unknown Source)
>>>> at java.lang.Integer.parseInt(Unknown Source)
>>>> at java.lang.Integer.valueOf(Unknown Source)
>>>> at
>> org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
>>>
>>> Sure looks like an Atmosphere problem from here...
>>>
>>
>> +1.
>>
>>
>> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
>>
>> That "bz51881" method... an example of what you should never do...
>>
>> It tries to parse a version string to "workaround" a bug that was
>> properly fixed more than a year ago, and fails horribly.
>>
>> It is a normal practice to modify the "server info" value, e.g. [1].
>> It is useless to rely on it. It is no wonder that the one used by
>> TomEE is different from Tomcat.
>>
>> [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves
>>
>>
>> Best regards,
>> Konstantin Kolinko
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
> TomEE committers, per Konstantin's response above, can you let me know, if
> this is TomEE or Atmosphere issue?
Looks like an Atmosphere issue. It's basically doing:
String[] tomcatVersion = config.getServletContext().getServerInfo().substring(14).split("\\.");
The getServerInfo() method was updated to add "(TomEE)" in there so people can have more info on the flavor of Tomcat they're using.
-David
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko
<kn...@gmail.com>wrote:
> 2013/1/30 Caldarale, Charles R <Ch...@unisys.com>:
> >> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
> >> Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
> on me, nothing in server logs
> >
> >> Sending this to tomee/openejb and tomcat user mailing lists.
> >
> > Cross-posting is really frowned upon.
> >
> >> Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
> event
> >> SEVERE: Servlet.service() for servlet [Push Servlet] in context with
> path
> >> [/mcmsweb] threw exception
> >> java.lang.NumberFormatException: For input string: "(TomEE)/7"
> >> at java.lang.NumberFormatException.forInputString(Unknown Source)
> >> at java.lang.Integer.parseInt(Unknown Source)
> >> at java.lang.Integer.valueOf(Unknown Source)
> >> at
> org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
> >
> > Sure looks like an Atmosphere problem from here...
> >
>
> +1.
>
>
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
>
> That "bz51881" method... an example of what you should never do...
>
> It tries to parse a version string to "workaround" a bug that was
> properly fixed more than a year ago, and fails horribly.
>
> It is a normal practice to modify the "server info" value, e.g. [1].
> It is useless to rely on it. It is no wonder that the one used by
> TomEE is different from Tomcat.
>
> [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves
>
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
TomEE committers, per Konstantin's response above, can you let me know, if
this is TomEE or Atmosphere issue?
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko
<kn...@gmail.com>wrote:
> 2013/1/30 Caldarale, Charles R <Ch...@unisys.com>:
> >> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
> >> Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
> on me, nothing in server logs
> >
> >> Sending this to tomee/openejb and tomcat user mailing lists.
> >
> > Cross-posting is really frowned upon.
> >
> >> Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
> event
> >> SEVERE: Servlet.service() for servlet [Push Servlet] in context with
> path
> >> [/mcmsweb] threw exception
> >> java.lang.NumberFormatException: For input string: "(TomEE)/7"
> >> at java.lang.NumberFormatException.forInputString(Unknown Source)
> >> at java.lang.Integer.parseInt(Unknown Source)
> >> at java.lang.Integer.valueOf(Unknown Source)
> >> at
> org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
> >
> > Sure looks like an Atmosphere problem from here...
> >
>
> +1.
>
>
> https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
>
> That "bz51881" method... an example of what you should never do...
>
> It tries to parse a version string to "workaround" a bug that was
> properly fixed more than a year ago, and fails horribly.
>
> It is a normal practice to modify the "server info" value, e.g. [1].
> It is useless to rely on it. It is no wonder that the one used by
> TomEE is different from Tomcat.
>
> [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves
>
>
Interesting, thanks for the response, Konstantin.
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by Konstantin Kolinko <kn...@gmail.com>.
2013/1/30 Caldarale, Charles R <Ch...@unisys.com>:
>> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
>> Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
>
>> Sending this to tomee/openejb and tomcat user mailing lists.
>
> Cross-posting is really frowned upon.
>
>> Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve event
>> SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
>> [/mcmsweb] threw exception
>> java.lang.NumberFormatException: For input string: "(TomEE)/7"
>> at java.lang.NumberFormatException.forInputString(Unknown Source)
>> at java.lang.Integer.parseInt(Unknown Source)
>> at java.lang.Integer.valueOf(Unknown Source)
>> at org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
>
> Sure looks like an Atmosphere problem from here...
>
+1.
https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129
That "bz51881" method... an example of what you should never do...
It tries to parse a version string to "workaround" a bug that was
properly fixed more than a year ago, and fails horribly.
It is a normal practice to modify the "server info" value, e.g. [1].
It is useless to rely on it. It is no wonder that the one used by
TomEE is different from Tomcat.
[1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on
me, nothing in server logs
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Tue, Jan 29, 2013 at 5:37 PM, Caldarale, Charles R <
Chuck.Caldarale@unisys.com> wrote:
> > From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
> > Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
> on me, nothing in server logs
>
> > Sending this to tomee/openejb and tomcat user mailing lists.
>
> Cross-posting is really frowned upon.
>
> > Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
> event
> > SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
> > [/mcmsweb] threw exception
> > java.lang.NumberFormatException: For input string: "(TomEE)/7"
> > at java.lang.NumberFormatException.forInputString(Unknown Source)
> > at java.lang.Integer.parseInt(Unknown Source)
> > at java.lang.Integer.valueOf(Unknown Source)
> > at
> org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
>
> Sure looks like an Atmosphere problem from here...
>
> - Chuck
>
>
>
Tomcat user list's response is above. I'll revert to an earlier/stable
version of Atmosphere, and continue to monitor tomee/tomcat, and let you
know if this issue persists.
My apologies for the cross posting; apologized to tomcat list already. :)
RE: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
on me, nothing in server logs
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Howard W. Smith, Jr. [mailto:smithh032772@gmail.com]
> Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
> Sending this to tomee/openejb and tomcat user mailing lists.
Cross-posting is really frowned upon.
> Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve event
> SEVERE: Servlet.service() for servlet [Push Servlet] in context with path
> [/mcmsweb] threw exception
> java.lang.NumberFormatException: For input string: "(TomEE)/7"
> at java.lang.NumberFormatException.forInputString(Unknown Source)
> at java.lang.Integer.parseInt(Unknown Source)
> at java.lang.Integer.valueOf(Unknown Source)
> at org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141)
Sure looks like an Atmosphere problem from here...
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org