On 2/13/07, David Blevins <[EMAIL PROTECTED]> wrote:
On Feb 12, 2007, at 7:29 PM, Prasad Kashyap wrote: > Jenck's patch seeems to have fixed the persistence bugs. However these > are the new exceptions seen when the same 2 test ears are deployed. > > Background Context: > ------------------------------- > The deployment-testsuite/test-deployments deploys the following 2 ears > in succession, hits the context-root URL in a browser and then > undeploys it again. > > org.apache.geronimo.testsupport/test-ear-j2ee_1.3/2.0-SNAPSHOT/ear > org.apache.geronimo.testsupport/test-ear-j2ee_1.4/2.0-SNAPSHOT/ear > > This used to work fine until recently. So for problem #1 I checked in a fix which should at least not result in a null pointer exception. We'll see what it throws next :) For #2 that'll take some debugging, but I think I may have an idea of how to fix. Quick question, how do I run the deployment-testsuite/test-deployments ?
The easiest way is to edit the geronimo/testsuite/pom.xml and comment out all other child modules. Just leave the deployment-testsuite in place. Then run 'mvn". But for you to recreate and test this, just use the CLI deploy tool to deploy your copy of trunk\testsupport\test-deployment-j2ee_1.4\test-ear-j2ee_1.4\target\test-ear-j2ee_1.4-2.0-SNAPSHOT.ear to a standalone running server.
-David
Cheers Prasad
> > > Problem #1: Starting an app with EJBs > -------------------------------------------------------- > Error: Operation failed: start of > org.apache.geronimo.testsupport/test-ear-j2ee_1.4/2.0-SNAPSHOT/ear > failed > Unknown start exception > > Configuration > org.apache.geronimo.testsupport/test-ear-j2ee_1.4/2.0-SNAPSHOT/ear > failed to start due to the following reasons: > The service > EJBModule=ejb.jar,J2EEApplication=org.apache.geronimo.testsupport/ > test-ear-j2ee_1.4/2.0-SNAPSHOT/ > ear,j2eeType=StatefulSessionBean,name=SimpleStatefulSession > did not start because > org.apache.geronimo.testsupport/test-ear-j2ee_1.4/2.0-SNAPSHOT/ear? > J2EEApplication=org.apache.geronimo.testsupport/test-ear- > j2ee_1.4/2.0-SNAPSHOT/ear,j2eeType=EJBModule,name=ejb.jar > did not start. > The service > J2EEApplication=org.apache.geronimo.testsupport/test-ear- > j2ee_1.4/2.0-SNAPSHOT/ear,j2eeType=EJBModule,name=ejb.jar > did not start because the doStart method threw an exception. > > org.apache.openejb.OpenEJBException: Error building bean > 'SimpleCMPEntity'. Exception: class > java.lang.NullPointerException: > null: null > > at org.apache.openejb.assembler.classic.EjbJarBuilder.build > (EjbJarBuilder.java:61) > at > org.apache.openejb.assembler.classic.Assembler.createApplication > (Assembler.java:379) > at org.apache.openejb.assembler.classic.Assembler.createEjbJar > (Assembler.java:303) > at org.apache.geronimo.openejb.OpenEjbSystemGBean.createEjbJar > (OpenEjbSystemGBean.java:184) > > > Full stack traces here - > http://rifers.org/paste/show/3524 > http://rifers.org/paste/show/3525 > > Problem # 2: Undeploy > ----------------------------------- > The apps distribute but fail to start. Undeploying them leaves behind > ejb.jar and ejb-cmp2.jar which are locked by the running server. The > server has to be stopped, these files deleted and only then can the > app be re-installed again. > > Cheers > Prasad > > > On 2/8/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote: >> Dain was referring to this - >> http://www.nabble.com/Persistence-deployer-bugs--tf3189760.html >> >> Will wait on David Jencks to fix this soon :-) >> >> Cheers >> Prasad >> >> On 2/8/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote: >> > On Feb 8, 2007, at 6:17 PM, Prasad Kashyap wrote: >> > >> > > org.apache.geronimo.kernel.GBeanAlreadyExistsException: GBean >> already >> > > registered: geronimo:J2EEServer=geronimo,name=cmp,j2eeType=GBean >> > >> > This the PersistenceUnit naming problem I pointed out >> yesterday. The >> > JPA deployer is not picking a very unique names and we quickly run >> > into conflicts. >> > >> > -dain >> > >> >
