Simon,
Thanks again. I will download the new version.
As it turns out the answer to my riddle is
annoying. I made a mistake in the SQL
command that was executed. A non existing
column name. This caused the Exception. That
is when I corrected it the Exception did not
occur anymore.
I would have expected a SQLException though.
The fact that I didn't may have to do with the
cocurrency issue you rose.
Thanks again.
Cor Hofman.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone
Sent: Thursday, January 18, 2001 12:48
To: 'jBoss'
Subject: RE: [jBoss-User] java.lang.Error id may not be null
Hey,
> Hi Simon,
>
> Thanks for your reaction.
> Yes I am using JBoss 2.0 FINAL.
> I am glad to hear that this bug has been fixed,
> but what keeps bugging me, why didn't I get
> the exception when I ran it with Oracle?
> In other words can you provide me some background to
> the why of this bug?
It was related to concurrency issues on the server between invocation and
passivation :)
So you did not get it in Oracle only by luck...
> I just studied the source code and the impression
> I get is that this Exception implies that I return
> a null key from the beans ejbCreate().
It's not the only case.
> The weird thing
> is, that I have the impression that this ejbCreate() is
> not actually executed. That is I have not been able to
> prove (yet) that the ejbCreate code of that bean has been
> executed.
System.out something in ejbCreate, then you'll see
> So where do I go wrong?
You don't very probably :). Just upgrade JBoss
As for the JMX Bugs messages, don't worry at all :)
Simon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
