ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: ODE out of memory problem.
Date Fri, 04 Jul 2008 16:05:17 GMT
Blind shot:  Is it possible that you have a circular dependency between your
WSDL or XSD imports?

alex


On Fri, Jul 4, 2008 at 3:54 AM, Ophir <bar9001@yahoo.com> wrote:

>
> Hi Mathew,
> Im still getting OOM error , heap space when deploying many processes
> using the deployment API .
>
> Initializing properties
> Jul 4, 2008 1:36:46 PM org.apache.coyote.http11.Http11BaseProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-8080
> Jul 4, 2008 1:36:50 PM org.apache.jk.common.ChannelSocket init
> INFO: JK: ajp13 listening on /0.0.0.0:8009
> Jul 4, 2008 1:36:50 PM org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=0/1141  config=null
> Jul 4, 2008 1:36:52 PM org.apache.catalina.storeconfig.StoreLoader load
> INFO: Find registry server-registry.xml at classpath resource
> Exception in thread "Thread-6" java.lang.OutOfMemoryError: Java heap space
> java.lang.reflect.InvocationTargetException
> Jul 4, 2008 1:37:10 PM
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor
> processChildren
> SEVERE: Exception invoking periodic operation:
> java.lang.OutOfMemoryError: Java heap space
>        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:585)
>        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
>        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
> Caused by: java.lang.OutOfMemoryError: Java heap space
>        at java.lang.String.<init>(String.java:208)
>        at
>
> com.sun.org.apache.xerces.internal.xni.XMLString.toString(XMLString.java:226)
>        at
>
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1037)
>        at
>
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:851)
>        at
>
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:16
> 93)
>        at
>
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
>        at
>
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
>        at
>
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
>        at
>
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
>        at
>
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
>        at
>
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
>        at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:98)
>        at org.apache.commons.modeler.util.DomUtil.readXml(DomUtil.java:257)
>        at
>
> org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.execute(MbeansDescriptorsDOMSource.java:88)
>        at
>
> org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.loadDescriptors(MbeansDescriptorsDOMSource.java:78)
>        at org.apache.commons.modeler.Registry.load(Registry.java:792)
>        at
> org.apache.commons.modeler.Registry.loadDescriptors(Registry.java:901)
>        at
> org.apache.commons.modeler.Registry.loadMetadata(Registry.java:268)
>        at
>
> org.apache.catalina.storeconfig.StoreConfigLifecycleListener.createMBean(StoreConfigLifecycleListener.java:93)
>        at
>
> org.apache.catalina.storeconfig.StoreConfigLifecycleListener.lifecycleEvent(StoreConfigLifecycleListener.java:58)
>        at
>
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
>        at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:705)
>        at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
>        ... 6 more
>
>
>
>
>
>
>
>
>
> Matthieu Riou-5 wrote:
> >
> > On Tue, Jul 1, 2008 at 9:43 AM, Ophir <bar9001@yahoo.com> wrote:
> >
> >>
> >> Hi ,
> >> Im runing ODE under linux. when i have many processes deployed ( around
> >> 30
> >> )
> >> and the ODE restarts ,
> >> all the deployed processes are starting to get activated , but after ~20
> >> processes there is memory heap
> >> exception.
> >> I have allocated -Xmx1024m for the ODE server but it still happens after
> >> a
> >> while.
> >> 1. is this a known issue ? and how is it solved .
> >
> >
> > I've never seen OOM problems with persistent processes. Even with
> > thousands
> > of processes.
> >
> >
> >>
> >> 2. i wonder if using a standalone derby db ( not running on same jvm)
> >> would
> >> help it. and if yes
> >> how do i config the server to run with standalone derby db .
> >>
> >
> > If you ask me, Derby sucks :) So you could go with a MySQL for example.
> > See
> > "Configuring ODE in Tomcat with a MySQL Database" here:
> >
> > http://ode.apache.org/user-guide.html#UserGuide-InaWebApplication
> >
> > That being said, the database you're running shouldn't impact the VM that
> > much, AFAIK even embedded, Derby doesn't leak so that's rather
> surprising.
> > It would be interesting to see what the heap looks like.
> >
> > Cheers,
> > Matthieu
> >
> >
> >>
> >> Thanks ,
> >> Ophir.
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/ODE-out-of-memory-problem.-tp18220393p18220393.html
> >> Sent from the Apache Ode User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/ODE-out-of-memory-problem.-tp18220393p18277252.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message