Jeremy,

Thanks for trying to reproduce this for me.  I cleaned
up the log and restarted the server, and reran the
client:

I got the same error on the client side, and I
verified that I have "DEBUG:     STATELESS   Hello" in
my openejb.log.   But I got the following exception
after the server is ready:

INFO :  OpenEJB ready.

ERROR:  Service webadmin.properties failed to load.
Cannot load properties: System resource
webadmin.properties cannot be found

ERROR:  Unexpected error

java.net.SocketException: Software caused connection
abort: socket write error

        at java.net.SocketOutputStream.socketWrite0(Native
Method)

        at java.net.SocketOutputStream.socketWrite(Unknown
Source)

        at java.net.SocketOutputStream.write(Unknown Source)

        at
java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown
Source)

        at
java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown
Source)

        at
java.io.ObjectOutputStream.writeNonProxyDesc(Unknown
Source)

        at java.io.ObjectOutputStream.writeClassDesc(Unknown
Source)

        at
java.io.ObjectOutputStream.writeOrdinaryObject(Unknown
Source)

        at java.io.ObjectOutputStream.writeObject0(Unknown
Source)

        at
java.io.ObjectOutputStream.writeFatalException(Unknown
Source)

        at java.io.ObjectOutputStream.writeObject(Unknown
Source)

        at
org.openejb.client.EJBMetaDataImpl.writeExternal(EJBMetaDataImpl.java:209)

        at
org.openejb.client.JNDIResponse.writeExternal(JNDIResponse.java:150)

        at
org.openejb.server.ejbd.JndiRequestHandler.processRequest(JndiRequestHandler.java:114)

        at
org.openejb.server.ejbd.EjbDaemon.processJndiRequest(EjbDaemon.java:186)

        at
org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:141)

        at
org.openejb.server.ejbd.EjbServer.service(EjbServer.java:77)

        at
org.openejb.server.ServiceLogger.service(ServiceLogger.java:142)

        at
org.openejb.server.ServiceAccessController.service(ServiceAccessController.java:109)

        at
org.openejb.server.ServiceDaemon$1.run(ServiceDaemon.java:152)

        at java.lang.Thread.run(Unknown Source)

ERROR:  Encountered problem while closing connection
with client: Software caused connection abort: socket
write error



--- Jeremy Whitlock <[EMAIL PROTECTED]> wrote:

> Lin,
> I just rebuilt an OpenEJB install from CVS and also
> recreated the Hello
> World EJB documented on the OpenEJB site. I was
> unable to reproduce your
> situation. In the client, I was able to look up the
> EJB by it's JNDI name,
> "/Hello". Can you look at your openejb.log to see if
> you see a line like
> this:
> 
> DEBUG: STATELESS Hello
> 
> While in there, check to see if you see any OpenEJB
> errors. If you'd like,
> paste your log here:
> 
> http://www.rafb.net/paste/
> 
> and email me the link. Sorry about this. Take care,
> Jeremy
> 
> On 9/21/05, Jeremy Whitlock <[EMAIL PROTECTED]>
> wrote:
> >
> > Lin,
> > I'll try and replicate your issue. I'll be back to
> you in a bit. Take
> > care, Jeremy
> >
> > On 9/20/05, lin sun < [EMAIL PROTECTED]> wrote:
> > >
> > > I was able to get further... You are right the
> > > classpath isn't setup correctly. My openejb_home
> is
> > > set to 0916's openejb home directory, but the
> jar file
> > > is named as openejb-core-1.0-beta1.jar.
> > >
> > > Here's the new error I am getting:
> > >
> > > E:\try\app>c:\j2sdk1.4.2_09\bin\java -cp
> > > c:\j2sdk1.4.2_09\lib\tools.jar;E:\try\o
> > >
> > >
>
penejb-1.0-20050916\openejb-1.0-20050916\lib\openejb-core-1.0-20050916.jar
> > > ;E:\tr
> > > y\openejb-
> > >
>
1.0-20050916\openejb-1.0-20050916\lib\openejb-loader-1.0-20050916.jar;
> > > E:\try\openejb-
> > >
>
1.0-20050916\openejb-1.0-20050916\beans\openejb-webadmin-clientto
> > > ols.jar;E:\try\openejb-
> > >
>
1.0-20050916\openejb-1.0-20050916\beans\openejb-webadmin-
> > > ejbgen.jar;E:\try\openejb-
> > >
>
1.0-20050916\openejb-1.0-20050916\beans\openejb-webadm
> > > in-main.jar;.
> > >
>
-Dopenejb.home=E:\try\openejb-1.0-20050916\openejb-1.0-20050916
> > > or
> > > g.acme.HelloWorld
> > > javax.naming.NamingException: Cannot lookup
> /Hello:
> > > Received error: Error while
> > > communicating with server: ; nested exception
> is:
> > > java.rmi.RemoteException: Error reading
> > > response from server: ; nested e
> > > xception is:
> > > java.lang.NoClassDefFoundError:
> > > javax/ejb/EJBMetaData
> > > at
> > > org.openejb.client.JNDIContext.lookup
> (JNDIContext.java:260)
> > > at
> > >
>
javax.naming.InitialContext.lookup(InitialContext.java:347)
> > > at
> > > org.acme.HelloWorld.main(HelloWorld.java:18)
> > >
> > >
> > >
> > > --- David Blevins < [EMAIL PROTECTED]>
> wrote:
> > >
> > > > Hmm, what command are you using to run the
> client?
> > > > Seems that the
> > > > classpath isn't getting setup correctly.
> > > >
> > > > -David
> > > >
> > > > On Sep 20, 2005, at 10:58 AM, lin sun wrote:
> > > >
> > > > > This worked fine for me. Thanks!
> > > > >
> > > > > I was able to see "DEBUG: STATELESS Hello"
> > > > in
> > > > > the openejb.log.
> > > > >
> > > > > But I still cannot run the HelloWorld client
> > > > > successfully... kept getting the following
> after I
> > > > > made sure I've included the
> > > > > openejb-core-1.0-20050916.jar to the
> classpath.
> > > > >
> > > > > javax.naming.NoInitialContextException :
> Cannot
> > > > > instantiate class: org.openejb.cl
> <http://org.openejb.cl>
> > > > > ient.RemoteInitialContextFactory [Root
> exception
> > > > is
> > > > > java.lang.ClassNotFoundExcep
> > > > > tion:
> > > >
> org.openejb.client.RemoteInitialContextFactory]
> > > > > at
> > > > >
> > > >
> > >
>
javax.naming.spi.NamingManager.getInitialContext(Unknown
> > > > > Source)
> > > > > at
> > > > >
> > > >
> > >
>
javax.naming.InitialContext.getDefaultInitCtx(Unknown
> > > > > Source)
> > > > > at
> > > > javax.naming.InitialContext.init(Unknown
> > > > > Source)
> > > > > at
> > > > javax.naming.InitialContext .<init>(Unknown
> > > > > Source)
> > > > > at
> > > > > org.acme.HelloWorld.main(HelloWorld.java:16)
> > > > > Caused by: java.lang.ClassNotFoundException:
> > > > > org.openejb.client.RemoteInitialCon
> > > > > textFactory
> > > > > at java.net.URLClassLoader$1.run(Unknown
> > > > > Source)
> > > > > at
> > > > >
> java.security.AccessController.doPrivileged(Native
> > > > > Method)
> > > > > at
> > > > java.net.URLClassLoader.findClass(Unknown
> > > > > Source)
> > > > > at java.lang.ClassLoader.loadClass(Unknown
> > > > > Source)
> > > > > at
> > > > > sun.misc.Launcher$AppClassLoader.loadClass
> (Unknown
> > > > > Source)
> > > > > at java.lang.ClassLoader.loadClass(Unknown
> > > > > Source)
> > > > > at
> > > > >
> java.lang.ClassLoader.loadClassInternal(Unknown
> > > > > Source)
> > > > > at java.lang.Class.forName0(Native Method)
> > > > > at java.lang.Class.forName(Unknown Source)
> > > > > at
> > > > >
> > > >
> > >
> com.sun.naming.internal.VersionHelper12.loadClass
> (Unknown
> > > > > Source)
> > > > > ... 5 more
> > > > > --- David Blevins <[EMAIL PROTECTED]>
> wrote:
> > > > >
> > > > >
> > > > >> Hi Lin,
> > > > >>
> > > > >> That's a hard bug to keep out of the
> system.
> > > > >> Basically the windows
> > > > >> VM holds a lock on the files when they are
> > > > accessed
> > > > >> by a classloader
> > > > >> and they become un-removable while the VM
> is
> > > > still
> > > > >> running.
> > > > >>
> > > > >> Try just copying for now and we'll see if
> we
> > > > can't
> > > > >> re-fix that code.
> > > > >> The command for copying is:
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> 
=== message truncated ===


thanks, 

Lin


        
                
______________________________________________________ 
Yahoo! for Good 
Donate to the Hurricane Katrina relief effort. 
http://store.yahoo.com/redcross-donate3/ 

Reply via email to