RE: JMS AMQP 1.0 - can the receiver.receive(timeout) return null even when timeout not expired?

2014-02-26 Thread Jan Bares
d.apache.org > Subject: Re: JMS AMQP 1.0 - can the receiver.receive(timeout) return null > even when timeout not expired? > > Yes - it looks like servicebus send an unsolicited end... so that is the > the place to investigate (unfortunately it doesn't seem like it provides >

Re: JMS AMQP 1.0 - can the receiver.receive(timeout) return null even when timeout not expired?

2014-02-25 Thread Rob Godfrey
: Close{} > > > -Original Message- > > From: Rob Godfrey [mailto:rob.j.godf...@gmail.com] > > Sent: Monday, February 24, 2014 6:50 PM > > To: users@qpid.apache.org > > Subject: Re: JMS AMQP 1.0 - can the receiver.receive(timeout) return null > > even when

RE: JMS AMQP 1.0 - can the receiver.receive(timeout) return null even when timeout not expired?

2014-02-25 Thread Jan Bares
JMS AMQP 1.0 - can the receiver.receive(timeout) return null > even when timeout not expired? > > Hi Jan, > > I think the easiest thing to help diagnose what is going on is to run with > logging turned on in the client... > > The client uses java logging and you can t

Re: JMS AMQP 1.0 - can the receiver.receive(timeout) return null even when timeout not expired?

2014-02-24 Thread Rob Godfrey
Hi Jan, I think the easiest thing to help diagnose what is going on is to run with logging turned on in the client... The client uses java logging and you can turn it on by setting the Java system property java.util.logging.config.file to point to a file that looks something like this: handlers=