Re: latest build supposed to be working?
On Jul 11, 2005, at 2:13 PM, Jacek Laskowski wrote: Scott Anderson wrote: Where is it posted? I don't see it on the home page, downloads page, or the wiki. http://cvs.apache.org/dist/geronimo/unstable/1.0-M4-QA/. Would you add a note on wiki? Done. It does appear my problem was due to a memory condition. I also needed to reboot after the build failure. After the "maven m:rebuild- all" failure, the reboot, and a "maven" command at the root of the dist I am back being productive. Scott
Re: latest build supposed to be working?
Scott Anderson wrote: Where is it posted? I don't see it on the home page, downloads page, or the wiki. http://cvs.apache.org/dist/geronimo/unstable/1.0-M4-QA/. Would you add a note on wiki? Scott Jacek
Re: latest build supposed to be working?
On Jul 11, 2005, at 11:55 AM, Aaron Mulder wrote:Well, you might start with the recently posted M4 QA build, and then you don't have to fool with this.Where is it posted? I don't see it on the home page, downloads page, or the wiki.The exceptions toward the bottom of your message are in many casesexpected -- you're in the test cases and some of the tests are tests forerror conditions and bad code and bad deployments and so on.That's what I figured.For the bus error thingy, what happens if you just run another build totake up where you left off? I often see voodoo errors in the middle of abuild (particularly around the time of the assembly module) that go awayif I try again -- I think it may ultimately be an out of memory condition,but I don't really know.I was doing a "maven m:rebuild-all" to resolve a conflict with open-ejb. Should I follow this up with just a "maven" when I suspect a memory condition?I have 2GB RAM. Is there an indicated way to configure Maven and/or Ant to boost the memory that they use?ScottOn Mon, 11 Jul 2005, Scott Anderson wrote: How do I determine if the build is known to be broken?I recently did a new source checkout, found it did not build, and tried to go back to my old working build to then find that I apparently overwrote my old open-ejb binary in my attempts to get the latest build running. My old working build is no longer working with the new open-ejb binary that replaced the old. At least, that is what I guessed happened.So, now I am left with trying to get the latest source to build. Here is the error I am encountering before the build dies... [junit] Running org.openejb.test.stateless.StatelessTestSuite/usr/local/maven-1.0.2/bin/maven: line 162: 322 Bus error "$JAVACMD" $MAVEN_OPTS - Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFact oryImpl - Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.Documen tBuilderFactoryImpl "-Djava.endorsed.dirs=${MAVEN_ENDORSED}" - classpath "${MAVEN_HOME}/lib/forehead-${FOREHEAD_VERSION}.jar" "- Dforehead.conf.file=${MAVEN_HOME}/bin/forehead.conf" "-Dtools.jar= $TOOLS_JAR" "-Dmaven.home=${MAVEN_HOME}" $MAIN_CLASS "$@"The above error was *preceeded* by a slew of repeating Derby serialization expections combined with exceptions related to the "Testing ability to throw System Exceptions"... [junit] Running org.openejb.test.entity.bmp.BmpTestSuite11:13:47,314 FATAL [EjbRequestHandler] Invocation result object is not serializable: org.apache.derby.impl.jdbc.EmbedSQLExceptionjava.io.NotSerializableException: org.apache.derby.impl.sql.compile.TableName at java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1054) at java.io.ObjectOutputStream.writeArray (ObjectOutputStream.java:1224) at java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1050) at java.io.ObjectOutputStream.defaultWriteFields (ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.writeSerialData (ObjectOutputStream.java:1304) at java.io.ObjectOutputStream.writeOrdinaryObject (ObjectOutputStream.java:1247) at java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.writeObject (ObjectOutputStream.java:278) at org.openejb.client.EJBResponse.writeExternal (EJBResponse.java:176) at org.openejb.server.ejbd.EjbRequestHandler.processRequest (EjbRequestHandler.java:260) at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java: 135) at org.openejb.server.ejbd.EjbServer.service(EjbServer.java:84) at org.openejb.server.ejbd.EjbServer$$FastClassByCGLIB$ $d379d2ff.invoke() at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java:118) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java:719) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java:36) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java:94) at org.openejb.server.ServerService$$EnhancerByCGLIB$ $42f62608.service() at org.openejb.server.ServicePool$2.run(ServicePool.java:106) at org.openejb.server.ServicePool$3.run(ServicePool.java:129) at org.apache.geronimo.pool.ThreadPool $ContextClassLoaderRunnable.run(ThreadPool.java:123) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run (Unknown Source) at java.lang.Thread.run(Thread.java:552)11:13:47,358 FATAL [EjbRequestHandler] Invocation result object is not serializable: org.apache.derby.impl.jdbc.EmbedSQLExceptionjava.io.NotSerializableException: org.apache.derby.impl.sq
Re: latest build supposed to be working?
Well, you might start with the recently posted M4 QA build, and then you
don't have to fool with this. Otherwise...
The exceptions toward the bottom of your message are in many cases
expected -- you're in the test cases and some of the tests are tests for
error conditions and bad code and bad deployments and so on.
For the bus error thingy, what happens if you just run another build to
take up where you left off? I often see voodoo errors in the middle of a
build (particularly around the time of the assembly module) that go away
if I try again -- I think it may ultimately be an out of memory condition,
but I don't really know.
Aaron
On Mon, 11 Jul 2005, Scott Anderson wrote:
> How do I determine if the build is known to be broken?
>
> I recently did a new source checkout, found it did not build, and
> tried to go back to my old working build to then find that I
> apparently overwrote my old open-ejb binary in my attempts to get the
> latest build running. My old working build is no longer working with
> the new open-ejb binary that replaced the old. At least, that is what
> I guessed happened.
>
> So, now I am left with trying to get the latest source to build. Here
> is the error I am encountering before the build dies...
>
> [junit] Running org.openejb.test.stateless.StatelessTestSuite
> /usr/local/maven-1.0.2/bin/maven: line 162: 322 Bus
> error "$JAVACMD" $MAVEN_OPTS -
> Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFact
> oryImpl -
> Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.Documen
> tBuilderFactoryImpl "-Djava.endorsed.dirs=${MAVEN_ENDORSED}" -
> classpath "${MAVEN_HOME}/lib/forehead-${FOREHEAD_VERSION}.jar" "-
> Dforehead.conf.file=${MAVEN_HOME}/bin/forehead.conf" "-Dtools.jar=
> $TOOLS_JAR" "-Dmaven.home=${MAVEN_HOME}" $MAIN_CLASS "$@"
>
> The above error was *preceeded* by a slew of repeating Derby
> serialization expections combined with exceptions related to the
> "Testing ability to throw System Exceptions"...
>
> [junit] Running org.openejb.test.entity.bmp.BmpTestSuite
> 11:13:47,314 FATAL [EjbRequestHandler] Invocation result object is
> not serializable: org.apache.derby.impl.jdbc.EmbedSQLException
> java.io.NotSerializableException:
> org.apache.derby.impl.sql.compile.TableName
> at java.io.ObjectOutputStream.writeObject0
> (ObjectOutputStream.java:1054)
> at java.io.ObjectOutputStream.writeArray
> (ObjectOutputStream.java:1224)
> at java.io.ObjectOutputStream.writeObject0
> (ObjectOutputStream.java:1050)
> at java.io.ObjectOutputStream.defaultWriteFields
> (ObjectOutputStream.java:1332)
> at java.io.ObjectOutputStream.writeSerialData
> (ObjectOutputStream.java:1304)
> at java.io.ObjectOutputStream.writeOrdinaryObject
> (ObjectOutputStream.java:1247)
> at java.io.ObjectOutputStream.writeObject0
> (ObjectOutputStream.java:1052)
> at java.io.ObjectOutputStream.writeObject
> (ObjectOutputStream.java:278)
> at org.openejb.client.EJBResponse.writeExternal
> (EJBResponse.java:176)
> at org.openejb.server.ejbd.EjbRequestHandler.processRequest
> (EjbRequestHandler.java:260)
> at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:
> 135)
> at org.openejb.server.ejbd.EjbServer.service(EjbServer.java:84)
> at org.openejb.server.ejbd.EjbServer$$FastClassByCGLIB$
> $d379d2ff.invoke()
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke
> (FastMethodInvoker.java:38)
> at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke
> (GBeanOperation.java:118)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke
> (GBeanInstance.java:719)
> at org.apache.geronimo.gbean.runtime.RawInvoker.invoke
> (RawInvoker.java:57)
> at
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke
> (RawOperationInvoker.java:36)
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept
> (ProxyMethodInterceptor.java:94)
> at org.openejb.server.ServerService$$EnhancerByCGLIB$
> $42f62608.service()
> at org.openejb.server.ServicePool$2.run(ServicePool.java:106)
> at org.openejb.server.ServicePool$3.run(ServicePool.java:129)
> at org.apache.geronimo.pool.ThreadPool
> $ContextClassLoaderRunnable.run(ThreadPool.java:123)
> at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run
> (Unknown Source)
> at java.lang.Thread.run(Thread.java:552)
> 11:13:47,358 FATAL [EjbRequestHandler] Invocation result object is
> not serializable: org.apache.derby.impl.jdbc.EmbedSQLException
> java.io.NotSerializableException:
> org.apache.derby.impl.sql.compile.TableName
> at java.io.ObjectOutputStream.writeObject0
> (ObjectOutputStream.java:1054)
> at java
