There are some commented out lines in ApplicationComposer which preload the 
classes I have problem with.
But that looks pretty much like a hack and I think the underlying problem is 
much deeper.

And again: those lines are commented out...


LieGrue,
strub



----- Original Message -----
> From: Romain Manni-Bucau <[email protected]>
> To: Mark Struberg <[email protected]>; [email protected]
> Cc: 
> Sent: Monday, July 30, 2012 11:30 AM
> Subject: Re: stochastic test errors
> 
> I think it was simply preloading this class in Core.
> 
> - Romain
> Le 30 juil. 2012 11:20, "Mark Struberg" <[email protected]> a 
> écrit :
> 
>>  Do you know what David fixed? I didn't find any corresponding JIRA 
> entry.
>> 
>>  LieGrue,
>>  strub
>> 
>> 
>> 
>>  ----- Original Message -----
>>  > From: Romain Manni-Bucau <[email protected]>
>>  > To: [email protected]; Mark Struberg <[email protected]>
>>  > Cc:
>>  > Sent: Monday, July 30, 2012 10:52 AM
>>  > Subject: Re: stochastic test errors
>>  >
>>  > yep but seems you are the only once getting it since David and JL ran 
> it
>>  on
>>  > mac os too i think
>>  >
>>  > I'm not familiar with macos jdk but any idea what could be the 
> diff with
>>  > win or linux jdk? both works
>>  >
>>  > - Romain
>>  >
>>  >
>>  > 2012/7/30 Mark Struberg <[email protected]>
>>  >
>>  >>  nope, clean 7up on openejb svn trunk...
>>  >>
>>  >>  I'm using OSX-10.7 with jdk-1.6. It seems to be a classloader 
> issue.
>>  >>  It doesn't happen if I debug it in idea, but breaks if I 
> start mvn test
>>  >>  -Dtest=..
>>  >>
>>  >>
>>  >>  Is there some temp-classloader or other classloader magic 
> involved?
>>  >>
>>  >>
>>  >>  LieGrue,
>>  >>  strub
>>  >>
>>  >>  >________________________________
>>  >>  > From: Romain Manni-Bucau <[email protected]>
>>  >>  >To: [email protected]; Mark Struberg 
> <[email protected]>
>>  >>  >Sent: Monday, July 30, 2012 9:56 AM
>>  >>  >Subject: Re: stochastic test errors
>>  >>  >
>>  >>  >
>>  >>  >Hey Mark,
>>  >>  >
>>  >>  >JL got this error too but David fixed it weeks ago...is it 
> possible
>>  > your
>>  >>  are not sync? (do you use github proxy?)
>>  >>  >
>>  >>  >- Romain
>>  >>  >
>>  >>  >
>>  >>  >
>>  >>  >2012/7/28 Mark Struberg <[email protected]>
>>  >>  >
>>  >>  >I digged a bit deeper:
>>  >>  >>
>>  >>  >>Caused by: java.lang.LinkageError: loader (instance of
>>  >>  sun/misc/Launcher$ExtClassLoader): attempted  duplicate class
>>  definition
>>  >>  for name: &quot;sun/security/pkcs11/SunPKCS11&quot;
>>  >>  >>        at java.lang.ClassLoader.defineClass1(Native 
> Method)
>>  >>  >>        at
>>  > java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
>>  >>  >>        at 
> java.lang.ClassLoader.defineClass(ClassLoader.java:615)
>>  >>  >>...
>>  >>  >>        at 
> org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown Source)
>>  >>  >>        at org.hsqldb.jdbc.JDBCDriver.connect(Unknown 
> Source)
>>  >>  >>        at
>>  >>
>>  >
>> 
> org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
>>  >>  >>...
>>  >>  >>        at
>>  >>
>>  >
>> 
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156)
>>  >>  >>        at
>>  >>
>>  >
>> 
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227)
>>  >>  >>        at
>>  >>
>>  >
>> 
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:154)
>>  >>  >>        at
>>  >>
>>  >
>> 
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60)
>>  >>  >>        at
>>  >>
>>  >
>> 
> org.apache.openejb.assembler.classic.ReloadableEntityManagerFactory.createEntityManager(ReloadableEntityManagerFactory.java:114)
>>  >>  >>        at
>>  >>
>>  >
>> 
> org.apache.openejb.persistence.ResourceLocalCdiEmTest$EMFProducer.em(ResourceLocalCdiEmTest.java:97)
>>  >>  >>
>>  >>  >>
>>  >>  >>LieGrue,
>>  >>  >>strub
>>  >>  >>
>>  >>  >>
>>  >>  >>
>>  >>  >>
>>  >>  >>
>>  >>  >>----- Original Message -----
>>  >>  >>> From: Mark Struberg <[email protected]>
>>  >>  >>> To: openejb-dev <[email protected]>
>>  >>  >>> Cc:
>>  >>  >>> Sent: Saturday, July 28, 2012 7:48 PM
>>  >>  >>> Subject: stochastic test errors
>>  >>  >>>
>>  >>  >>> Hi folks!
>>  >>  >>>
>>  >>  >>> When doing a full build of the container module, I 
> get the
>>  > following
>>  >>  Exception:
>>  >>  >>>
>>  >>  >>> Test set:
>>  > org.apache.openejb.persistence.ResourceLocalCdiEmTest
>>  >>  >>>
>>  >>
>>  >
>> 
> -------------------------------------------------------------------------------
>>  >>  >>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, 
> Time
>>  > elapsed: 2.192
>>  >>  sec
>>  >>  >>> <<< FAILURE!
>>  >>  >>>
>>  > injection(org.apache.openejb.persistence.ResourceLocalCdiEmTest)  Time
>>  >>  elapsed:
>>  >>  >>> 2.097 sec  <<< FAILURE!
>>  >>  >>> junit.framework.AssertionFailedError
>>  >>  >>>         at 
> junit.framework.Assert.fail(Assert.java:48)
>>  >>  >>>         at 
> junit.framework.Assert.assertTrue(Assert.java:20)
>>  >>  >>>         at
>>  > junit.framework.Assert.assertNotNull(Assert.java:218)
>>  >>  >>>         at
>>  > junit.framework.Assert.assertNotNull(Assert.java:211)
>>  >>  >>>         at
>>  >>  >>>
>>  >>
>>  >
>> 
> org.apache.openejb.persistence.ResourceLocalCdiEmTest.injection(ResourceLocalCdiEmTest.java:50)
>>  >>  >>>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>  > Method)
>>  >>  >>>         at
>>  >>  >>>
>>  >>
>>  >
>> 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>  >>  >>>         at
>>  >>  >>>
>>  >>
>>  >
>> 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>  >>  >>>
>>  >>  >>>
>>  >>  >>> If I start the test in the debugger, all works fine!
>>  >>  >>>
>>  >>  >>> It seems the injection doesn't work.
>>  >>  >>>
>>  >>  >>> Any tips?
>>  >>  >>>
>>  >>  >>> LieGrue,
>>  >>  >>> strub
>>  >>  >>>
>>  >>  >>
>>  >>  >
>>  >>  >
>>  >>  >
>>  >>
>>  >
>> 
>

Reply via email to