JNDI initialization and browsing question.

2005-07-11 Thread Piotr Przybylski

Hi, 
I have a question about JNDI maybe someone
can help me with. Does JNDI require any special initialization and is there
a way to browse it, other than using JNDI API? I am  running into
JNDI lookup problem on M3 driver. I am using a simple resource adapter
RAR file (v 1.5 compliant). When I deploy it to the server, it deploys
fine. The application (with JSP) also deploys fine but when I try to lookup
the connection from the jsp triggered class, the JNDI context seems empty,
the lookup of the following does not find anything:
- java:comp/env/test/j2c/po/dii/order/Order_CF
- test/j2c/po/dii/order/Order_CF
- g2MyTestAdapterCF

The global context seems to contain
only JMXConnector Object. 

Below are the relevant fragmnets of
the configuration files used to deploy connector and application. 

Thank you, any help greatly appreciated.

Regards, 

Piotr Przybylski. 

geronimo-jetty.xml:
        
         
      test/j2c/po/dii/order/Order_CF
         
      g2MyTestAdapter
        


web.xml:
        
         
      test/j2c/po/dii/order/Order_CF
         
      javax.resource.cci.ConnectionFactory
         
      Container
         
      Shareable
        


geronimo-ra.xml

...

   
   
      javax.resource.cci.ConnectionFactory

   
      g2MyTestAdapter

      localhost

      user 
        
           
 
         

           
  10 
           
  5000

           
   
         

    
    TestAdapterCF

  
  
  
  
  





Re: latest build supposed to be working?

2005-07-11 Thread Scott Anderson


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?

2005-07-11 Thread Jacek Laskowski

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: build failure

2005-07-11 Thread Joe Bohn

The Problem is solved!!!   Thank you all.

After I sent my last append I looked with task manager and noticed a 
rouge java.exe and javaw.exe.   Assuming these were Geronimo from an 
earlier failed build I blew them away and then ran the build again but 
without the "no test" options.  The build said it failed but it looked 
like it was only because of the tests ... so I ran one final build with 
no test to ensure that everything fundamental build itself worked and it 
was successful.


Jacek ... it's water under the bridge now, but I did answer your 
questions below just in case you were curious.   Thanks for your help!


Jacek Laskowski wrote:


Joe Bohn wrote:

Now it looks like I'm having problems with OpenEJB and ActiveMQ:   
I'm getting this:


Attempting to download activemq-ra-3.1-SNAPSHOT.rar.
Error retrieving artifact from
[http://www.ibiblio.org/maven/activemq/rars/activ
emq-ra-3.1-SNAPSHOT.rar]: java.net.ConnectException: Connection
timed out: conne
ct



This is because your connection to iBiblio timed out. It doesn't apply 
to Geronimo in any way other than that without it it's impossible to 
build Geronimo. So, open the browser of your choice and visit the 
site. If it works, run maven again. Make sure you don't use any proxy 
server as Maven would be required to be configured with it, too.


I could get to the site and it did work on a subsequent attempt ... it 
must have been some network fluke.  I don't use a proxy server.




I also get the same message for  "openejb-core-2.0-SNAPSHOT.jar" and  
"openejb-builder-2.0-SNAPSHOT.jar."



See above.

So looking thru earlier appends about failed builds and openEJB.
When I ran  "maven m:co"  it says it was successful but the messages 
don't give me a warm fuzzy


m:checkout:
[cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass
for reading:
 No such file or directory
[cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass
for reading:
 No such file or directory
[cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass
for reading:
 No such file or directory
BUILD SUCCESSFUL



It looks as if the cvs error msgs don't make the build fail. Do you 
use cygwin? Can you run cvs in the command line. I may be mistaken, 
but I've  read that the cvspass file needs to be created the first 
time CVS is executed. See a cvs manual.


I do use cygwin and cvs does work directly from the command line.   I 
checked and I don't have a  .cvspass file created.  It looks like this 
is a password file but I don't recall setting up an id/password when 
installing CVS.  Perhaps I'm connecting as a guest so long as I just 
check-out and don't check in code?



I then ran "maven m:rebuild-all" as Aaron recommended



Well, I don't see why it could help having seen the above cvs errors? 
How did you get the sources then?


I was running on desperation and hoping that the cvs messages were a red 
herring and the build really was successful.  :-)  I think I must have 
retrieved the source on a previous failed built that for some reason 
didn't encounter the same error. 




and I received this failure:

BUILD FAILED
File.. C:\cygwin\home\bohn\geronimo\maven.xml
Element... ant:delete
Line.. 132
Column 52
Unable to delete file
C:\cygwin\home\bohn\geronimo\modules\assembly\target\geron
imo-1.0-SNAPSHOT\bin\server.jar

I'm not sure why it can't delete the server jar ... it isn't 
protected.  Is it possible that I have some daemon or service version 
of Geronimo already running?   How would I terminate it?  Any other 
ideas?



The file is probably locked by a running instance of Geronimo. Use 
task manager to kill all of the running java processes.


As I mentioned above I did find these rouge processes and killed them 
resolving this problem.




Jacek





--
Joe Bohn 

[EMAIL PROTECTED] 
"He is no fool who gives what he cannot keep, to gain what he cannot lose."   -- Jim Elliot




Re: latest build supposed to be working?

2005-07-11 Thread Scott Anderson
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: build failure

2005-07-11 Thread Jacek Laskowski

Joe Bohn wrote:

Now it looks like I'm having problems with OpenEJB and ActiveMQ:   I'm 
getting this:


Attempting to download activemq-ra-3.1-SNAPSHOT.rar.
Error retrieving artifact from
[http://www.ibiblio.org/maven/activemq/rars/activ
emq-ra-3.1-SNAPSHOT.rar]: java.net.ConnectException: Connection
timed out: conne
ct


This is because your connection to iBiblio timed out. It doesn't apply 
to Geronimo in any way other than that without it it's impossible to 
build Geronimo. So, open the browser of your choice and visit the site. 
If it works, run maven again. Make sure you don't use any proxy server 
as Maven would be required to be configured with it, too.


I also get the same message for  "openejb-core-2.0-SNAPSHOT.jar" and  
"openejb-builder-2.0-SNAPSHOT.jar."


See above.

So looking thru earlier appends about failed builds and openEJB.When 
I ran  "maven m:co"  it says it was successful but the messages don't 
give me a warm fuzzy


m:checkout:
[cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass
for reading:
 No such file or directory
[cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass
for reading:
 No such file or directory
[cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass
for reading:
 No such file or directory
BUILD SUCCESSFUL


It looks as if the cvs error msgs don't make the build fail. Do you use 
cygwin? Can you run cvs in the command line. I may be mistaken, but I've 
 read that the cvspass file needs to be created the first time CVS is 
executed. See a cvs manual.



I then ran "maven m:rebuild-all" as Aaron recommended


Well, I don't see why it could help having seen the above cvs errors? 
How did you get the sources then?


and I received 
this failure:


BUILD FAILED
File.. C:\cygwin\home\bohn\geronimo\maven.xml
Element... ant:delete
Line.. 132
Column 52
Unable to delete file
C:\cygwin\home\bohn\geronimo\modules\assembly\target\geron
imo-1.0-SNAPSHOT\bin\server.jar

I'm not sure why it can't delete the server jar ... it isn't protected.  
Is it possible that I have some daemon or service version of Geronimo 
already running?   How would I terminate it?  Any other ideas?


The file is probably locked by a running instance of Geronimo. Use task 
manager to kill all of the running java processes.


Jacek



Re: latest build supposed to be working?

2005-07-11 Thread Aaron Mulder
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

latest build supposed to be working?

2005-07-11 Thread Scott Anderson


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.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(Ej

Re: build failure

2005-07-11 Thread Joe Bohn




Thanks for your help.  I've tried this with the offline option and it
seems like things went better ... but it still failed.

Now it looks like I'm having problems with OpenEJB and ActiveMQ:   I'm
getting this: 
Attempting to download activemq-ra-3.1-SNAPSHOT.rar.
Error retrieving artifact from
[http://www.ibiblio.org/maven/activemq/rars/activ
emq-ra-3.1-SNAPSHOT.rar]: java.net.ConnectException: Connection timed
out: conne
ct

I also get the same message for  "openejb-core-2.0-SNAPSHOT.jar" and 
"openejb-builder-2.0-SNAPSHOT.jar."

So looking thru earlier appends about failed builds and openEJB.   
When I ran  "maven m:co"  it says it was successful but the messages
don't give me a warm fuzzy
m:checkout:
    [cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass for
reading:
 No such file or directory
    [cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass for
reading:
 No such file or directory
    [cvs] cvs checkout: warning: failed to open /home/bohn/.cvspass for
reading:
 No such file or directory
BUILD SUCCESSFUL


I then ran "maven m:rebuild-all" as Aaron recommended and I received
this failure:
BUILD FAILED
File.. C:\cygwin\home\bohn\geronimo\maven.xml
Element... ant:delete
Line.. 132
Column 52
Unable to delete file
C:\cygwin\home\bohn\geronimo\modules\assembly\target\geron
imo-1.0-SNAPSHOT\bin\server.jar

I'm not sure why it can't delete the server jar ... it isn't
protected.  Is it possible that I have some daemon or service version
of Geronimo already running?   How would I terminate it?  Any other
ideas?

David Jencks wrote:
I don't know where the IP address comes from, but you
might try adding  -Dgeronimo.assemble.offline=true to your command line
  
  
Normally during assembly we start the server and deploy a bunch of 
packages into the running server, to save time and test that the 
runtime deployer actually works.  This flag makes all deployment
happen  without a running server.
  
  
david jencks
  
  
On Jul 11, 2005, at 10:21 AM, Joe Bohn wrote:
  
  
   That's definitely not the IP address of this
machine. 


 I'm confused as to even why it is attempting to start the server with 
the skip=true values being set.


 Any ideas on why it is starting the server and if I can manually set 
the ip address someplace?


 Thanks, Joe


 Aaron Mulder wrote:    On that machine, does the host name of the 
machine resolve to

10.150.1.3, and if so, is that the correct
IP address?  It looks like  it
  
might be getting a bogus IP and then timing out while trying to 
connect to
  
itself.
  
  
Aaron
  
  
On Mon, 11 Jul 2005, Joe Bohn wrote:
  
  
  I'm trying to get my build working for
Geronimo and I'm running into

some problem.  It looks to be like even though I specified the maven

command with test & itest = true ... it is still trying to run the 
tests

and hitting some error while starting booting the Geronimo kernel 
(which

I didn't think it would do without the test specified).


Here's the command I used:

maven m:build -Dmaven.test.skip=true -Dmaven.itest.skip=true


Here is the output:

target/geronimo-1.0-SNAPSHOT

Booting Geronimo Kernel (in Java 1.4.2_08)...

11:29:23,898 WARN

[server:J2EEApplication=null,J2EEModule=org/apache/geronimo/S

erver,J2EEServer=geronimo,j2eeType=GBean,name=JMXService] Error 
stopping

JMXConn

ector after failure

java.io.IOException: javax.naming.ServiceUnavailableException [Root

exception is

 java.rmi.ConnectException: Connection refused to host: 10.150.1.3;

nested excep

tion is:

    java.net.ConnectException: Connection timed out: connect]

    at 
mx4j.remote.resolver.rmi.Resolver.unbindServer(Resolver.java:279)

    at

javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServe

r.java:172)



11:29:23,898 ERROR [GBeanInstanceState] Error while starting; GBean  is

now in th

e FAILED state:

objectName="geronimo.server:J2EEApplication=null,J2EEModule=org/

apache/geronimo/
Server,J2EEServer=geronimo,j2eeType=GBean,name=JMXService"

java.io.IOException: javax.naming.ServiceUnavailableException [Root

exception is

 java.rmi.ConnectException: Connection refused to host: 10.150.1.3;

nested excep

tion is:

    java.net.ConnectException: Connection timed out: connect]

    at 
mx4j.remote.resolver.rmi.Resolver.bindServer(Resolver.java:199)

    at

javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ

er.java:152)

    at

org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav

a:112)

    at

Re: build failure

2005-07-11 Thread David Jencks
I don't know where the IP address comes from, but you might try adding  
-Dgeronimo.assemble.offline=true to your command line


Normally during assembly we start the server and deploy a bunch of  
packages into the running server, to save time and test that the  
runtime deployer actually works.  This flag makes all deployment happen  
without a running server.


david jencks

On Jul 11, 2005, at 10:21 AM, Joe Bohn wrote:


 That's definitely not the IP address of this machine. 

 I'm confused as to even why it is attempting to start the server with  
the skip=true values being set.


 Any ideas on why it is starting the server and if I can manually set  
the ip address someplace?


 Thanks, Joe

 Aaron Mulder wrote:On that machine, does the host name of the  
machine resolve to
10.150.1.3, and if so, is that the correct IP address?  It looks like  
it
might be getting a bogus IP and then timing out while trying to  
connect to

itself.

Aaron

On Mon, 11 Jul 2005, Joe Bohn wrote:


I'm trying to get my build working for Geronimo and I'm running into
some problem.  It looks to be like even though I specified the maven
command with test & itest = true ... it is still trying to run the  
tests
and hitting some error while starting booting the Geronimo kernel  
(which

I didn't think it would do without the test specified).

Here's the command I used:
maven m:build -Dmaven.test.skip=true -Dmaven.itest.skip=true

Here is the output:
target/geronimo-1.0-SNAPSHOT
Booting Geronimo Kernel (in Java 1.4.2_08)...
11:29:23,898 WARN
[server:J2EEApplication=null,J2EEModule=org/apache/geronimo/S
erver,J2EEServer=geronimo,j2eeType=GBean,name=JMXService] Error  
stopping

JMXConn
ector after failure
java.io.IOException: javax.naming.ServiceUnavailableException [Root
exception is
 java.rmi.ConnectException: Connection refused to host: 10.150.1.3;
nested excep
tion is:
java.net.ConnectException: Connection timed out: connect]
at  
mx4j.remote.resolver.rmi.Resolver.unbindServer(Resolver.java:279)

at
javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServe
r.java:172)

11:29:23,898 ERROR [GBeanInstanceState] Error while starting; GBean  
is

now in th
e FAILED state:
objectName="geronimo.server:J2EEApplication=null,J2EEModule=org/
apache/geronimo/ 
Server,J2EEServer=geronimo,j2eeType=GBean,name=JMXService"

java.io.IOException: javax.naming.ServiceUnavailableException [Root
exception is
 java.rmi.ConnectException: Connection refused to host: 10.150.1.3;
nested excep
tion is:
java.net.ConnectException: Connection timed out: connect]
at  
mx4j.remote.resolver.rmi.Resolver.bindServer(Resolver.java:199)

at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
er.java:152)
at
org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav
a:112)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI
nstance.java:850)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
(GBeanInstanceState.java:328)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta
nceState.java:111)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
BeanInstanceState.java:133)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
nstance.java:503)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
cKernel.java:207)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
BeanInstanceState.java:141)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
nstance.java:503)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
cKernel.java:207)
at  
org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:247)
at  
org.apache.geronimo.system.main.Daemon.(Daemon.java:81)
at  
org.apache.geronimo.system.main.Daemon.main(Daemon.java:320)

Geronimo startup complete

BUILD FAILED
File.. C:\Documents and
Settings\Administrator\.maven\cache\maven-multiproje
ct-plugin-1.3.1\plugin.jelly
Element... maven:reactor
Line.. 217
Column 9
Unable to obtain goal [default] --
C:\cygwin\home\bohn\geronimo\modules\assembly
\maven.xml:395:63:  Could not connect
Total time: 26 minutes 48 seconds
Finished at: Mon Jul 11 11:43:40 EDT 2005

Thank you,
Joe Bohn










Re: build failure

2005-07-11 Thread Joe Bohn




That's definitely not the IP address of this machine.  

I'm confused as to even why it is attempting to start the server with
the skip=true values being set.

Any ideas on why it is starting the server and if I can manually set
the ip address someplace?

Thanks, Joe

Aaron Mulder wrote:

  	On that machine, does the host name of the machine resolve to 
10.150.1.3, and if so, is that the correct IP address?  It looks like it 
might be getting a bogus IP and then timing out while trying to connect to 
itself.

Aaron

On Mon, 11 Jul 2005, Joe Bohn wrote:
  
  
I'm trying to get my build working for Geronimo and I'm running into 
some problem.  It looks to be like even though I specified the maven 
command with test & itest = true ... it is still trying to run the tests 
and hitting some error while starting booting the Geronimo kernel (which 
I didn't think it would do without the test specified).

Here's the command I used:
maven m:build -Dmaven.test.skip=true -Dmaven.itest.skip=true

Here is the output:
target/geronimo-1.0-SNAPSHOT
Booting Geronimo Kernel (in Java 1.4.2_08)...
11:29:23,898 WARN  
[server:J2EEApplication=null,J2EEModule=org/apache/geronimo/S
erver,J2EEServer=geronimo,j2eeType=GBean,name=JMXService] Error stopping 
JMXConn
ector after failure
java.io.IOException: javax.naming.ServiceUnavailableException [Root 
exception is
 java.rmi.ConnectException: Connection refused to host: 10.150.1.3; 
nested excep
tion is:
java.net.ConnectException: Connection timed out: connect]
at mx4j.remote.resolver.rmi.Resolver.unbindServer(Resolver.java:279)
at 
javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServe
r.java:172)

11:29:23,898 ERROR [GBeanInstanceState] Error while starting; GBean is 
now in th
e FAILED state: 
objectName="geronimo.server:J2EEApplication=null,J2EEModule=org/
apache/geronimo/Server,J2EEServer=geronimo,j2eeType=GBean,name=JMXService"
java.io.IOException: javax.naming.ServiceUnavailableException [Root 
exception is
 java.rmi.ConnectException: Connection refused to host: 10.150.1.3; 
nested excep
tion is:
java.net.ConnectException: Connection timed out: connect]
at mx4j.remote.resolver.rmi.Resolver.bindServer(Resolver.java:199)
at 
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
er.java:152)
at 
org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav
a:112)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI
nstance.java:850)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
(GBeanInstanceState.java:328)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta
nceState.java:111)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
BeanInstanceState.java:133)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
nstance.java:503)
at 
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
cKernel.java:207)
at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
BeanInstanceState.java:141)
at 
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
nstance.java:503)
at 
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
cKernel.java:207)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:247)
at org.apache.geronimo.system.main.Daemon.(Daemon.java:81)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:320)
Geronimo startup complete

BUILD FAILED
File.. C:\Documents and 
Settings\Administrator\.maven\cache\maven-multiproje
ct-plugin-1.3.1\plugin.jelly
Element... maven:reactor
Line.. 217
Column 9
Unable to obtain goal [default] -- 
C:\cygwin\home\bohn\geronimo\modules\assembly
\maven.xml:395:63:  Could not connect
Total time: 26 minutes 48 seconds
Finished at: Mon Jul 11 11:43:40 EDT 2005

Thank you,
Joe Bohn



  
  

  





Re: build failure

2005-07-11 Thread Aaron Mulder
On that machine, does the host name of the machine resolve to 
10.150.1.3, and if so, is that the correct IP address?  It looks like it 
might be getting a bogus IP and then timing out while trying to connect to 
itself.

Aaron

On Mon, 11 Jul 2005, Joe Bohn wrote:
> I'm trying to get my build working for Geronimo and I'm running into 
> some problem.  It looks to be like even though I specified the maven 
> command with test & itest = true ... it is still trying to run the tests 
> and hitting some error while starting booting the Geronimo kernel (which 
> I didn't think it would do without the test specified).
> 
> Here's the command I used:
> maven m:build -Dmaven.test.skip=true -Dmaven.itest.skip=true
> 
> Here is the output:
> target/geronimo-1.0-SNAPSHOT
> Booting Geronimo Kernel (in Java 1.4.2_08)...
> 11:29:23,898 WARN  
> [server:J2EEApplication=null,J2EEModule=org/apache/geronimo/S
> erver,J2EEServer=geronimo,j2eeType=GBean,name=JMXService] Error stopping 
> JMXConn
> ector after failure
> java.io.IOException: javax.naming.ServiceUnavailableException [Root 
> exception is
>  java.rmi.ConnectException: Connection refused to host: 10.150.1.3; 
> nested excep
> tion is:
> java.net.ConnectException: Connection timed out: connect]
> at mx4j.remote.resolver.rmi.Resolver.unbindServer(Resolver.java:279)
> at 
> javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServe
> r.java:172)
> 
> 11:29:23,898 ERROR [GBeanInstanceState] Error while starting; GBean is 
> now in th
> e FAILED state: 
> objectName="geronimo.server:J2EEApplication=null,J2EEModule=org/
> apache/geronimo/Server,J2EEServer=geronimo,j2eeType=GBean,name=JMXService"
> java.io.IOException: javax.naming.ServiceUnavailableException [Root 
> exception is
>  java.rmi.ConnectException: Connection refused to host: 10.150.1.3; 
> nested excep
> tion is:
> java.net.ConnectException: Connection timed out: connect]
> at mx4j.remote.resolver.rmi.Resolver.bindServer(Resolver.java:199)
> at 
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
> er.java:152)
> at 
> org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav
> a:112)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI
> nstance.java:850)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
> (GBeanInstanceState.java:328)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta
> nceState.java:111)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
> BeanInstanceState.java:133)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
> nstance.java:503)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
> cKernel.java:207)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
> BeanInstanceState.java:141)
> at 
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
> nstance.java:503)
> at 
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
> cKernel.java:207)
> at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:247)
> at org.apache.geronimo.system.main.Daemon.(Daemon.java:81)
> at org.apache.geronimo.system.main.Daemon.main(Daemon.java:320)
> Geronimo startup complete
> 
> BUILD FAILED
> File.. C:\Documents and 
> Settings\Administrator\.maven\cache\maven-multiproje
> ct-plugin-1.3.1\plugin.jelly
> Element... maven:reactor
> Line.. 217
> Column 9
> Unable to obtain goal [default] -- 
> C:\cygwin\home\bohn\geronimo\modules\assembly
> \maven.xml:395:63:  Could not connect
> Total time: 26 minutes 48 seconds
> Finished at: Mon Jul 11 11:43:40 EDT 2005
> 
> Thank you,
> Joe Bohn
> 
> 


build failure

2005-07-11 Thread Joe Bohn
I'm trying to get my build working for Geronimo and I'm running into 
some problem.  It looks to be like even though I specified the maven 
command with test & itest = true ... it is still trying to run the tests 
and hitting some error while starting booting the Geronimo kernel (which 
I didn't think it would do without the test specified).


Here's the command I used:
maven m:build -Dmaven.test.skip=true -Dmaven.itest.skip=true

Here is the output:
target/geronimo-1.0-SNAPSHOT
Booting Geronimo Kernel (in Java 1.4.2_08)...
11:29:23,898 WARN  
[server:J2EEApplication=null,J2EEModule=org/apache/geronimo/S
erver,J2EEServer=geronimo,j2eeType=GBean,name=JMXService] Error stopping 
JMXConn

ector after failure
java.io.IOException: javax.naming.ServiceUnavailableException [Root 
exception is
java.rmi.ConnectException: Connection refused to host: 10.150.1.3; 
nested excep

tion is:
   java.net.ConnectException: Connection timed out: connect]
   at mx4j.remote.resolver.rmi.Resolver.unbindServer(Resolver.java:279)
   at 
javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServe

r.java:172)

11:29:23,898 ERROR [GBeanInstanceState] Error while starting; GBean is 
now in th
e FAILED state: 
objectName="geronimo.server:J2EEApplication=null,J2EEModule=org/

apache/geronimo/Server,J2EEServer=geronimo,j2eeType=GBean,name=JMXService"
java.io.IOException: javax.naming.ServiceUnavailableException [Root 
exception is
java.rmi.ConnectException: Connection refused to host: 10.150.1.3; 
nested excep

tion is:
   java.net.ConnectException: Connection timed out: connect]
   at mx4j.remote.resolver.rmi.Resolver.bindServer(Resolver.java:199)
   at 
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ

er.java:152)
   at 
org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav

a:112)
   at 
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI

nstance.java:850)
   at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart

(GBeanInstanceState.java:328)
   at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta

nceState.java:111)
   at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G

BeanInstanceState.java:133)
   at 
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI

nstance.java:503)
   at 
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi

cKernel.java:207)
   at 
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G

BeanInstanceState.java:141)
   at 
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI

nstance.java:503)
   at 
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi

cKernel.java:207)
   at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:247)
   at org.apache.geronimo.system.main.Daemon.(Daemon.java:81)
   at org.apache.geronimo.system.main.Daemon.main(Daemon.java:320)
Geronimo startup complete

BUILD FAILED
File.. C:\Documents and 
Settings\Administrator\.maven\cache\maven-multiproje

ct-plugin-1.3.1\plugin.jelly
Element... maven:reactor
Line.. 217
Column 9
Unable to obtain goal [default] -- 
C:\cygwin\home\bohn\geronimo\modules\assembly

\maven.xml:395:63:  Could not connect
Total time: 26 minutes 48 seconds
Finished at: Mon Jul 11 11:43:40 EDT 2005

Thank you,
Joe Bohn