I get this too, it doesn't seem to matter fwiw and I put it down to a build environment issue on my part (the wrong version of buildr or some such!) - cj.
On Wed, May 13, 2009 at 11:28 AM, Nowakowski, Mateusz < mateusz.nowakow...@sabre-holdings.com> wrote: > I'll make a build today as fast as possible. > > > > However, yesterday I put manually ode-agents jar into JBI bundle and it > started successfully, but I saw some strange logs on standard output > > > > 2009-05-12 17:02:39 java.util.jar.Attributes read > > WARNING: Duplicate name in Manifest: Manifest-Version. > > Ensure that the manifest does not have duplicate entries, and > > that blank lines separate individual sections in both your > > manifest and in the META-INF/MANIFEST.MF entry in the jar file. > > 2009-05-12 17:02:40 java.util.jar.Attributes read > > WARNING: Duplicate name in Manifest: Manifest-Version. > > Ensure that the manifest does not have duplicate entries, and > > that blank lines separate individual sections in both your > > manifest and in the META-INF/MANIFEST.MF entry in the jar file. > > > > It comes from ... ode-agents-1.3.2.jar manifest: > > > > Manifest-Version: 1.0 > > Created-By: Buildr > > Manifest-Version: 1.0 > > Premain-Class: org.apache.ode.agents.memory.SizingAgent > > > > I'm getting scared, because it seems this version hasn't been even run > on JBI platform before release. > > > > What is more I've got some strange logs during startup: > > > > 2009-05-12 17:02:39,248 [ProcessStoreImpl-1] INFO openjpa.Query - This > query on type "class org.apache.ode.store.jpa.VersionTrackerDAOImpl" > must load the entire candidate class extent and evaluate the query > in-memory. This may be very slow. The query must be executed in memory > because OpenJPA is configured with IgnoreCache=false and > FlushBeforeQueries=false and there are dirty instances that may affect > the query's outcome in the cache. > > > > for each process. > > > > We have only in-memory processes; does it have any impact on these > processes? > > ODE is deployed with EMBEDDED db. > > > > -- > > Regards > > Mateusz Nowakowski > > ________________________________ > > From: Karthick Sankarachary [mailto:sankarach...@intalio.com] > Sent: Tuesday, May 12, 2009 7:30 PM > To: Nowakowski, Mateusz > Subject: Re: [VOTE] ODE 1.3.2 release > > > > Please checkout revision 773992 and see whether the JBI package includes > the required agents module. If so, then that should resolve your issue. > If not, please get back to me at this email. > > Best Regards, > Karthick Sankarachary > > > > On Tue, May 12, 2009 at 8:34 AM, Nowakowski, Mateusz > <mateusz.nowakow...@sabre-holdings.com> wrote: > > Hi, > > > > I've tried JBI version of this release and I've got while startup: > > > > Exception in thread "Timer-2" java.lang.NoClassDefFoundError: > org/apache/ode/agents/memory/SizingAgent > > at > org.apache.ode.bpel.engine.BpelProcess.sizeOf(BpelProcess.java:1046) > > at > org.apache.ode.bpel.engine.BpelEngineImpl.setProcessSize(BpelEngineImpl. > java:638) > > at > org.apache.ode.bpel.engine.BpelProcess$HydrationLatch.doHydrate(BpelProc > ess.java:881) > > at > org.apache.ode.bpel.engine.BpelProcess$HydrationLatch.access$100(BpelPro > cess.java:777) > > at > org.apache.ode.bpel.engine.BpelProcess$HydrationLatch$2.run(BpelProcess. > java:787) > > at > org.apache.ode.bpel.engine.NStateLatch.latch(NStateLatch.java:89) > > at > org.apache.ode.bpel.engine.BpelProcess.hydrate(BpelProcess.java:688) > > at > org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:3 > 14) > > at > org.apache.ode.jbi.OdeServiceUnit.start(OdeServiceUnit.java:104) > > at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:115) > > at > org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUn > itLifeCycle.java:103) > > at > org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Servi > ceAssemblyLifeCycle.java:154) > > at > org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentSe > rvice.java:390) > > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceA > ssembly(AutoDeploymentService.java:351) > > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive( > AutoDeploymentService.java:255) > > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirecto > ry(AutoDeploymentService.java:658) > > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(Aut > oDeploymentService.java:63) > > at > org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDepl > oymentService.java:622) > > at java.util.TimerThread.mainLoop(Timer.java:512) > > at java.util.TimerThread.run(Timer.java:462) > > Caused by: java.lang.ClassNotFoundException: > org.apache.ode.agents.memory.SizingAgent in classloader > org.apache.ode.agents.memory.SizingAgent > > at > org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParen > tClassLoader.java:206) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > > ... 20 more > > > > It seems JBI version doesn't contain ode-agents-1.3.2.jar > > > > -- > > Regards > > Mateusz Nowakowski > > > > > -----Original Message----- > From: Tammo van Lessen [mailto:tvanles...@gmail.com] > Sent: Thursday, April 30, 2009 5:03 PM > To: dev@ode.apache.org > Subject: Re: [VOTE] ODE 1.3.2 release > > > > Matthieu Riou wrote: > > > > > > +1 > > > > > > If we find another annoying bug we can roll out a quick bugfix release > but > > > we've already delayed too much and I'm pretty convinced this release > will > > > greatly benefit the majority of the community. > > > > > > > +1 (for both, release and comment :) > > > > Cheers, > > Tammo > > > > -- > > Tammo van Lessen - http://www.taval.de > > > >
