What is the version of GlassFish or GlassFish ESB you are using ?
I got something similar and it happened that it was a bug in grizzly.
If you want to whether this is the same problem or not, download Grizzly 1.0.30 from
http://download.java.net/maven/2/com/sun/grizzly/grizzly-framework-http/1.0.30-SNAPSHOT/
Store the jar file somewhere on the server file system and reference it using the classpath-prefix attribute (edit domain.xml or use the administration console).
Restart your GlassFish and check whether you can reproduce or not.
Bye
[Message sent by forum member 'vkoniecz' (vkoniecz)]