[JBossWS] - JBossWS 3.0.3 memory leak
by Marlboro
Hi,
We are running an EJB3/JBossWS aplication on JBoss 4.2.2 with JBossWS - native 3.0.3. Our application causes JBoss to crash with "out of memory error" under load, and we have memory dump from Java 1.6. After analyze of this dump we suspect JBossWS to cause the memory leak. There are 22942513 instances of class java.util.HashMap$Entry with 367080208 bytes and 58967 instances of class [Ljava.util.HashMap$Entry; with 231301484 bytes. Both HashMap entries contain some data from data type's definitions of our endpoints.
For better understating: our application has two parts. At this moment, both parts are deployed on one server but in the future it will be possible to deploy them on two distinct servers. One part is web service client, second one is web service endpoint. We tested our application with Java 1.5 and also 1.6 but we are able to obtain memory dump only with Java 1.6 . Nevertheless both JVMs have the same behavior - they crash approximately after 48 hours.
Any help will be greatly appreciated. If you will need more data/infos please feel free to contact me.
Thanks,
Vratislav Kuzela
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187660#4187660
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187660
16 years, 1 month
[JBossWS] - Upgrade jbossws on JBoss EAP 4.2
by bschmoll1
Hi,
I'm trying to upgrade the JBossws stack on a JBoss EAP 4.2 server instance. I run the upgrade process and it all seems to work fine until I attempt to invoke a web service on the server. I get th following
| 2008-11-06 08:52:11,288 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/OnDemandReport].[OnDemandReportBean]] Servlet.service() for servlet OnDem
| andReportBean threw exception
| java.lang.NoSuchMethodError: org.jboss.ejb3.stateless.StatelessBeanContext.setWebServiceContext(Ljavax/xml/ws/WebServiceContext;)V
| at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3$CallbackImpl.attached(InvocationHandlerEJB3.java:134)
| at org.jboss.ejb3.EJBContainerInvocation.setBeanContext(EJBContainerInvocation.java:77)
| at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:56)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
| at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:108)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
| at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:103)
| at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:476)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
| at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:81)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:619)
|
This all works fine on a JBoss 4.2.2 instance, so I'm thinking it's that the EAP version isn't compatible with the new jbossws stacks. Can anyone confirm this?
Thanks,
-Brett
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187556#4187556
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187556
16 years, 1 month