Hi again,

this will be the last one for today ;-).

I figured out, that __Proxy0.class gets generated by the client. The
__Proxy0.class is always involved in this problem, regardless of where the
server or the client runs or what version of jdk or orion i use (meanwhile i
tried out 1.0.3, since it's the last "official" release), as if there was an
old copy of this class somewhere in my classpath which gets used. But on
neither of my machines i can find any instance of this class, except for the
directory where i start the client - and this one i have removed a hundred
times by now...

Can someone please explain, where, by whom and under which circumstances
this class gets generated (is it true, that the client must have write
access for the current directory to write this class? Or somewhere else?)?
Are there any other generated classes (so that i can search for old
instances of these) apart from those under "application-deployments" on the
server or clientside? Where are they placed if running the client within an
IDE (forte)?

Regards,

Jens

> -----Urspr�ngliche Nachricht-----
> Von: Jens Stutte [mailto:[EMAIL PROTECTED]]
> Gesendet am: Donnerstag, 6. Juli 2000 14:03
> An: Orion-Interest
> Cc: '[EMAIL PROTECTED]'
> Betreff: AW: Strange exception - further details
> 
> 
> Hi, 
> some further deatils:
> 
> The exception reported in the last mail was generated, if the 
> server is
> running on linux, 
> java version "1.2.2", Classic VM (build 1.2.2-L, green 
> threads, javacomp)
> and the client on a windows box, java version "1.3.0", 
> Java(TM) 2 Runtime
> Environment, Standard Edition (build 1.3.0-C), Java 
> HotSpot(TM) Client VM
> (build 1.3.0-C, mixed mode) - both using the same classes via a shared
> network directory. Because i did not know, what to do, i switched the
> situation - client on linux jdk 1.2.2, server on windows jdk 1.3.
> Now the exception changes to:
> 
> java.lang.VerifyError: (class: __Proxy0, method: <clinit> 
> signature: ()V)
> Accessing value from uninitialized register 0
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java, Compiled Code)
>         at com.evermind.reflect.Proxy.ama(JAX)
>         at com.evermind.reflect.Proxy.al9(JAX)
>         at com.evermind.reflect.Proxy.al7(JAX)
>         at com.evermind.server.rmi.a8.f4(JAX)
>         at com.evermind.server.rmi.a5.resolveObject(JAX)
>         at 
> java.io.ObjectInputStream.readObject(ObjectInputStream.java,
> Compiled Code)
>         at 
> java.io.ObjectInputStream.readObject(ObjectInputStream.java,
> Compiled Code)
>         at com.evermind.server.rmi.a8.gj(JAX)
>         at com.evermind.server.rmi.a8.run(JAX)
>         at java.lang.Thread.run(Thread.java:475)
> java.lang.NullPointerException:
>         at com.evermind.reflect.Proxy.al9(JAX)
>         at com.evermind.reflect.Proxy.al7(JAX)
>         at com.evermind.server.rmi.a8.f4(JAX)
>         at com.evermind.server.rmi.a5.resolveObject(JAX)
>         at 
> java.io.ObjectInputStream.readObject(ObjectInputStream.java,
> Compiled Code)
>         at 
> java.io.ObjectInputStream.readObject(ObjectInputStream.java,
> Compiled Code)
>         at com.evermind.server.rmi.a8.gj(JAX)
>         at com.evermind.server.rmi.a8.run(JAX)
>         at java.lang.Thread.run(Thread.java:475)
> de.netmedia.ejb.interfaces.exceptions$NMBeanHomeNotFoundException
>         at
> de.netmedia.ejb.interfaces.NMejbConnection.getHome(NMejbConnec
> tion.java:176)
>         at
> de.netmedia.ejb.interfaces.NMejbConnection.getHome(NMejbConnec
> tion.java:186)
>         at
> de.netmedia.ejb.interfaces.NMejbAccess.<init>(NMejbAccess.java:47)
>         at
> de.netmedia.ejb.base.binarybean.NMejbBinaryAccess.<init>(NMejb
> BinaryAccess.j
> ava:47)
>         at 
> de.netmedia.ejb.test.clienttest.addWords(clienttest.java:92)
>         at de.netmedia.ejb.test.clienttest.main(clienttest.java:246)
> de.netmedia.ejb.interfaces.exceptions$NMBeanHomeNotFoundException
>         at
> de.netmedia.ejb.interfaces.NMejbConnection.getHome(NMejbConnec
> tion.java:176)
>         at
> de.netmedia.ejb.interfaces.NMejbConnection.getHome(NMejbConnec
> tion.java:186)
>         at
> de.netmedia.ejb.interfaces.NMejbAccess.<init>(NMejbAccess.java:47)
>         at
> de.netmedia.ejb.base.binarybean.NMejbBinaryAccess.<init>(NMejb
> BinaryAccess.j
> ava:47)
>         at 
> de.netmedia.ejb.test.clienttest.addWords(clienttest.java:92)
>         at de.netmedia.ejb.test.clienttest.main(clienttest.java:246)
> 
> 
> and gets thrown already on bean home retrieval (which worked 
> the other way
> round, the first _access_ to the home failed).
> 
> Ran i into some incompatibility between jdk 1.2.2 and jdk 1.3 
> ? My next test
> will be trying to use the same jdks, unfortunately i cannot 
> run client and
> server on the same machine...
> 
> Very weird...
> 
> > -----Urspr�ngliche Nachricht-----
> > Von: Jens Stutte [mailto:[EMAIL PROTECTED]]
> > Gesendet am: Donnerstag, 6. Juli 2000 12:44
> > An: Orion-Interest
> > Cc: '[EMAIL PROTECTED]'
> > Betreff: Strange exception
> > 
> > Hi,
> > 
> > i ran into a real showstopper. My EJBs deploy all correct, 
> > and some of them
> > can be accessed. But accessing one particular Bean generates 
> > the following
> > exception on the client side:
> > 
> > javax.ejb.CreateException
> >         at com.evermind.server.rmi.a8.invokeMethod(JAX)
> >         at com.evermind.server.rmi.a_.invoke(JAX)
> >         at com.evermind.server.rmi.a0.invoke(JAX)
> >         at __Proxy0.create(Unknown Source)
> >         at
> > de.netmedia.ejb.base.binarybean.NMejbBinaryAccess.create(NMejb
> > BinaryAccess.j
> > ava:89)
> >         at 
> > de.netmedia.ejb.test.clienttest.addWords(clienttest.java:100)
> >         at de.netmedia.ejb.test.clienttest.main(clienttest.java:246)
> > 
> > The client is using the physical identical classes as the 
> > server, so that
> > there can be no discrepances. The server does not report 
> > anything, it gets
> > not even touched it seems... What's more, i cannot locate a 
> > __Proxy0.class
> > in any of the orion directories, is it part of some jar? The 
> > name looks like
> > it was generated.
> > What may cause this exception? This happens both with orion 
> > 1.1.8 and 1.1.9.
> > Yesterday (nearly) the same bean worked well, so i fear that 
> > something in my
> > settings/classes screw up - but i cant figure out the 
> reason (and the
> > exception is not very descriptive).
> > 
> > Any help would be very appriciated, thanx
> > 
> > Jens Stutte
> > 
> > 
> > ____________________________________________
> > [EMAIL PROTECTED], http://www.netmedia.de
> > 
> > NetMedia GmbH
> > Neugrabenweg 5-7
> > 66123 Saarbruecken
> > Germany
> > 
> > fon: +49 (0) 681 - 3 79 88 - 0
> > fax: +49 (0) 681 -�3 79 88 - 99
> > 
> > 
> > 
> 

Reply via email to