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-1f3371ffc847;|[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.