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
>
: 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
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
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=
Hi,
JMS 0.26 with AMQP 1.0 and Service Bus. I have concurrent producer and
receiver. The receiver.receive(7) returns null after ~17 seconds(the
timeout did not expired). The javadoc says that null should be returned when
timeout expires or message consumer is concurrently closed. I do not c