users@glassfish.java.net

Re: GF 2.1.1 IMQReaderChannel WARNING

From: Paulo Reis <casmeiron_at_gmail.com>
Date: Fri, 30 Oct 2009 10:59:22 -0200

Hi Nigel,

I got this message with glassfish running, I didn't restart it, it has been
running for like 24 hours now.

The MQ broker is configured to LOCAL. This exception was raised after the
creation of a timer (8 minutes after, I don't know if they're related):

[#|2009-10-30T08:52:06.757-0200|INFO|sun-appserver2.1] Creating timer using
the interval value '1800000' ...

[#|2009-10-30T08:52:06.758-0200|INFO|sun-appserver2.1] Timer 'Timer
45@@1256818892750@@server@@npe' was created with success! ResetTimer method
ended!
|#]

[#|2009-10-30T09:00:01.692-0200|WARNING|sun-appserver2.1|javax.jms|_ThreadID
=393;_ThreadName=iMQReadChannel-26883;_RequestID=e0d04d1f-c035-4af5-bc9f-1f3
371ffc847;|[I500]: Caught JVM Exception: java.io.EOFException: Trying to
read 72 bytes. Already read 0 bytes.|#]

The creation of timer is simple as:

getTimerService().createTimer(...);

I don't know if you remember me but this is the client that often got the mq
to frozen the consumer calls, still tryin' to find the root cause, no
problem so far with the new release of glassfish (2.1.1).

Thanks.



On 10/30/09 10:35 AM, "Nigel Deakin" <Nigel.Deakin_at_Sun.COM> wrote:

> Paulo,
>
> These messages are typically seen when the application detects that a LOCAL or
> REMOTE MQ broker has terminated.
>
> When did you get these messages? If you got them when shutting down the
> Glassfish instance, this is a known issue:
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=10392
>
> Nigel
>
> Paulo Reis wrote:
>> Hi,
>>
>> I caught this warning in one of our servers that runs glassfish 2.1.1:
>>
>> [#|2009-10-30T09:00:01.692-0200|WARNING|sun-appserver2.1|javax.jms|_ThreadID=
>> 393;_ThreadName=iMQReadChannel-26883;_RequestID=e0d04d1f-c035-4af5-bc9f-1f337
>> 1ffc847;|[I500]:
>> Caught JVM Exception: java.io.EOFException: Trying to read 72 bytes.
>> Already read 0 bytes.|#]
>>
>>
>> What is that means?
>>
>> I often find the EOFException in the server.log.
>>
>> Environment:
>>
>> Redhat Linux 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64
>> x86_64 x86_64 GNU/Linux
>> java version "1.6.0_16"
>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>> Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
>>
>>
>> Thanks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>