1 Reply Latest reply on Dec 13, 2010 5:47 AM by kconner

    OOME on restoring messages

    andreasriedel

      Hello Forum.

       

      I've some problem with a productiv ESB, so therefore I will not experimental. Due some reason we have massiv request to one of ower ESB services. Shutdown the server and restart ended up in following error-message below.

       

      We have tried to clean up the undelivered messages by running Queues MBean removeAllMessages-Method, with no result. My last hope was to find the messages in the database. I looked for some JMS stuff. But i was unable to find them.

      • Has anyone an idea, whats to do.
      • Is it possible, that the problem will be fixed by it selv, only to start up the server once with the -XX:-UseGCOverheadLimit option.

       

      TIA

        Andreas

       

      Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
          at java.util.Arrays.copyOf(Arrays.java:2882)
          at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
          at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:515)
          at java.lang.StringBuffer.append(StringBuffer.java:306)
          at java.io.StringWriter.write(StringWriter.java:77)
          at org.apache.xml.serializer.ToStream.processDirty(ToStream.java:1531)
          at org.apache.xml.serializer.ToStream.characters(ToStream.java:1449)
          at org.apache.xalan.transformer.TransformerIdentityImpl.characters(TransformerIdentityImpl.java:1125)
          at org.apache.xml.serializer.TreeWalker.dispatachChars(TreeWalker.java:244)
          at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:414)
          at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:143)
          at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:389)
          at org.apache.ws.scout.util.XMLUtils.convertNodeToXMLString(XMLUtils.java:38)
          at org.apache.ws.scout.registry.RegistryV3Impl.execute(RegistryV3Impl.java:342)
          at org.apache.ws.scout.registry.RegistryV3Impl.getServiceDetail(RegistryV3Impl.java:1000)
          at org.apache.ws.scout.registry.RegistryV3Impl.getServiceDetail(RegistryV3Impl.java:982)
          at org.apache.ws.scout.registry.BusinessQueryManagerV3Impl.getRegistryObject(BusinessQueryManagerV3Impl.java:708)
          at org.apache.ws.scout.registry.BusinessQueryManagerV3Impl.findServiceBindings(BusinessQueryManagerV3Impl.java:566)
          at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findServiceBindings(JAXRRegistryImpl.java:779)
          at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:316)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at org.jboss.internal.soa.esb.services.registry.RegistryService$1.invoke(RegistryService.java:61)
          at $Proxy24.findEPRs(Unknown Source)
          at org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor.findEPRs(InVMRegistryInterceptor.java:85)
          at org.jboss.soa.esb.services.registry.RegistryFactory$HeadRegistryInterceptor.findEPRs(RegistryFactory.java:229)
          at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226)
          at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:532)
          at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:174)
          at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:155)

       

        • 1. Re: OOME on restoring messages
          kconner

          This is a symptom of another issue.  That particular error message usually means that the GC is very active but unable to release much memory, do you know what is occurring in the VM at this point?  Do you have any log files?