Hi Jeff, sorry wasn't available for the last two days. I know now how I can prevent an empty byte-array on a redelivered bytemessage (redelivered by session.recover() on a non-transacted client_acknowledge-session) which I get by invoking the previous mentioned standardoperations. The problem 'at our site' seems to be based on the configuration attributes: . DefaultRedeliveryDelay (messaging-service.xml) & . RedeliveryDelay (destinations-service.xml) (overwrites ServerPeer default) My testresults for readBytes(...) on a redelivered bytesmessage with payloadAsByteArray=[72, 73, 95, 74, 69, 70, 70, 10]: using the standard non clustered destination: testQueue. with 0 or 1 msec as DefaultRedeliveryDelay & RedeliveryDelay or no entry (RedeliveryDelay only of course) are: ServerPeer (DefaultRedeliveryDelay) --- Destination (RedeliveryDelay) --- Result (Content of byte[] after .readBytes(...)) ------------------------------------- 0 --- 0 --- [0, 0, 0, 0, 0, 0, 0, 0] 1 --- 0 --- [0, 0, 0, 0, 0, 0, 0, 0] 0 --- 1 --- [72, 73, 95, 74, 69, 70, 70, 10] 1 --- 1 --- [72, 73, 95, 74, 69, 70, 70, 10] 0 --- / --- [0, 0, 0, 0, 0, 0, 0, 0] 1 --- / --- [72, 73, 95, 74, 69, 70, 70, 10] The weird thing is that case #5 can be found as part of the default configuration. Well it's hard to believe that 'our' problem is based only on these two attributes (many others would have the same problem then) but I can live with it knowning that in the end the final saying delayattribute must have an value greater or equal one msec. lesse View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145613#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...