Well, that's the wierd part, what I gave you is all the server spit out.
That's the whole thing. I actually sent this email yesterday and it hit the
list today?? Anyhow, since then I did a little poking around on the jboss
site, saved the link to pr4 and then changed the link to pr_3 and was able
to still get the zip for pr3. I installed it, ran it, and depoyed the
_exact_ bean(in fact I pulled if from the pr4 deploy dir.) and redployed the
bean in pr3. It ran flawlessly the first time. The bean, in case the server
snippet didn't give it away, is the Cabin CMP bean from chapter 4 of Richard
Monson-Haefel's EJB book. It works outstanding in pr3, but refuses to work
in pr4. All I get is this NPE. No other data. Weird.

I still have to say though, that even with these petty gripes that I have,
jboss is still the easiest(and becoming the most powerful) ejb server on the
market; free or otherwise. Jboss simply f'n rocks.

Any help on the above problem would be appreciated. I can send the jar and
the client if you don't already have it.

Thanks,

-jdm

-----Original Message-----
From: marc fleury <[EMAIL PROTECTED]>
To: jBoss <[EMAIL PROTECTED]>
Date: Sunday, August 20, 2000 9:51 PM
Subject: RE: [jBoss-User] PR_4 doesn't work..


>we need the server trace
>
>marc
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of John D. McDonald
>> Sent: Saturday, August 19, 2000 6:08 PM
>> To: jboss list
>> Subject: [jBoss-User] PR_4 doesn't work..
>>
>>
>> Now that I have your attention..
>>
>> Could someone help me out with this? I'm deploying a bean that I used
just
>> earlier today on pr_3. I uninstalled pr_3 and upgraded to pr_4. Now I'm
>> getting this exception from jboss. Has anyone seen this excepption? The
>> client that I'm using simply gets a reference to the CabinBean
>> and attempts
>> to set some of its' values. The line that actually throws the exception
in
>> the client is as follows:(line 4)
>>
>> Context jndiContext = getInitialContext();
>> Object obj = jndiContext.lookup("java:CabinBean");
>> CabinHome home = (CabinHome) javax.rmi.PortableRemoteObject.narrow(obj,
>> CabinHome.class);
>> Cabin cabin_1 = home.create(1); <-- Exception Thrown here
>>
>> Now, If I run the client again, it will tell me "Entity with key 1
already
>> exists".
>>
>> Any ideas would by gleefully appreciated!
>>
>>
>> --- jboss exception ---
>> [Default] JRMPCI:invokeHome public abstract strictfp
com.titan.cabin.Cabin
>> com.titan.cabin.CabinHome.create(int) throws
>> java.rmi.RemoteException,javax.ejb.CreateException
>> [CabinBean] Found metadata for bean 'CabinBean' method is create
>> [JAWS] Create, id is 4
>> [JAWS] Exists command executing: SELECT COUNT(*) AS Total FROM CabinBean
>> WHERE id=?
>> [JAWS] Set parameter: idx=1, jdbcType=INTEGER, value=4
>> [JAWS] Create command executing: INSERT INTO CabinBean
>> (bedCount,id,deckLevel,ship,name) VALUES (?,?,?,?,?)
>> [JAWS] Set parameter: idx=1, jdbcType=INTEGER, value=0
>> [JAWS] Set parameter: idx=2, jdbcType=INTEGER, value=4
>> [JAWS] Set parameter: idx=3, jdbcType=INTEGER, value=0
>> [JAWS] Set parameter: idx=4, jdbcType=INTEGER, value=0
>> [JAWS] Set parameter: idx=5, jdbcType=VARCHAR, value=NULL
>> [JAWS] Rows affected = 1
>> [CabinBean] null
>>
>> -=-- client  exception -  ---
>> Exception in thread "main" java.lang.NullPointerException
>>         at
>> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown
>> Source)
>>         at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
>>         at sun.rmi.server.UnicastRef.invoke(Unknown Source)
>>         at
>> org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker_Stub.invoke
>> Home(Unkno
>> wn Source)
>>         at
>>
org.jboss.ejb.plugins.jrmp.interfaces.HomeProxy.invoke(HomeProxy.java:221)
>>         at $Proxy0.create(Unknown Source)
>>         at com.titan.cabin.Client_1.main(Client_1.java:21)
>>
>>
>>
>> --
>> --------------------------------------------------------------
>> To subscribe:        [EMAIL PROTECTED]
>> To unsubscribe:      [EMAIL PROTECTED]
>> Problems?:           [EMAIL PROTECTED]
>>
>>
>
>
>
>--
>--------------------------------------------------------------
>To subscribe:        [EMAIL PROTECTED]
>To unsubscribe:      [EMAIL PROTECTED]
>Problems?:           [EMAIL PROTECTED]
>
>



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to