Hi Justin...
Yes, What I see is an attempt to deploy that ends in a
nullPointerException, over and over again. I'll have a look at my XML, now
that I know what to look for.
Of course, even if it is my error in the XML, jBoss should handle it a bit
more robustly.
Thanks!
--On Wednesday, May 17, 2000 10:32 PM +0100 Justin Forder
<[EMAIL PROTECTED]> wrote:
> Jim
>
> Thanks - you've prodded my thinking, and I remember that someone else
> reported having this problem very recently (probably while you were away
> at the trade show), and found that it was due to having the wrong JRMP
> version configured in his XML.
>
> That must be what has happened to me: I've just moved up to JDK1.3, and
> haven't reconfigured or recompiled my bean.
>
> I found your resubmitted bug (bug 23), which mentions a null pointer
> exception. I haven't seen any exceptions, but the overall behaviour is
> the same.
>
> Great!
>
> Justin
>
>> Hi Justin...
>>
>> I wrote this up in Bugzilla a while ago. Originally, it was bug 17 and
>> was lost. I resubmitted it already.
>>
>> Jim
>>
>> --On Wednesday, May 17, 2000 9:11 PM +0100 Justin Forder
>> <[EMAIL PROTECTED]> wrote:
>>
>>> Just got JDK1.3 set up, and building jBoss2.0 is working very well.
>>>
>>> BUT when I run, with one JAR in the deploy directory, jBoss is going
>>> into an infinite loop of deploying the bean and then immediately
>>> undeploying it.
>>>
>>> I'm sure someone else posted about this (I've looked in the archives,
>>> but not found any relevant Subject lines).
>>>
>>> What's the answer?
>>> --
>>> Justin Forder
>
> --
> Justin Forder
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
