Thanks Rob,
From the log I read that the server sent End{} and this caused client to close
the connection. Do I read it correctly? So it seems like Service Bus issue then.
Kind regards, Jan
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3184,deliveryTag=p3\xa76Sx\xb6I\xa2\x04\x85\x09\x1b\x072\xbc,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3185,deliveryTag=z\xce\xceB\x10\xe2\xd3E\xb2\x9fg\xabn\xa3\x1a\xba,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: SEND[:5671|0] :
Disposition{role=receiver,first=3160,last=3169,settled=true,state=Accepted{}}
[15:50:08] FINE: SEND[:5671|0] :
Flow{nextIncomingId=3187,incomingWindow=2048,nextOutgoingId=0,outgoingWindow=2048,handle=0,deliveryCount=3186,linkCredit=94,drain=false,echo=false}
[15:50:08] FINE: SEND[:5671|0] :
Disposition{role=receiver,first=3170,last=3179,settled=true,state=Accepted{}}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3186,deliveryTag=\xc5\x1c#\xf9\x94\xfa\x05O\xb0\xcf\x93@\xb3\xbf-\x80,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3187,deliveryTag=\xf7\xf5\xc50\x16\x849B\xa2E\x8bG\xd6\xfcR\x84,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3188,deliveryTag=|\x7f*\x02\xde\xc7{O\x8e\xee\x03\xd1\xa9\xe3>7,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3189,deliveryTag=\xb1\xc84\x183\xac\xfbE\xa9\x991\xe3'\x10\x00\x87,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3190,deliveryTag=<E\x5c\xba\xc6\xb7\x99H\xa4\x99\x9d\xe8A\x15\xe1\xba,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3191,deliveryTag=\xb9J\x92\xd8\x91\xe6\x1cO\x89\x14\xb7)\x9dd
|,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3192,deliveryTag=\xb0.oD\xb9\x95\xe6L\xa9)r\x13\xd0)\x1c\xc6,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3193,deliveryTag=z\x9a\xc7\xa6G\x7f\xa8M\xb7/\x8d:\xb25\xad\xc8,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3194,deliveryTag=D!\xfa'W\xcd\xe3M\xa2\x0a\xbeX\xec\xbc.m,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3195,deliveryTag=1\x0f-\xa0i\xc0\xbfA\x91\xd2\xac#\xee8`\xa7,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3196,deliveryTag=\xbb\x1c2\xe8\x11\xa2YF\xa5/X8\xe5Nq\xfe,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: SEND[:5671|0] :
Disposition{role=receiver,first=3180,last=3189,settled=true,state=Accepted{}}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3197,deliveryTag=\xa5f\xdcm\xcf\x07\xe9O\xa3\xa3\x94.[\x09>I,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3198,deliveryTag=\x0a#*\x93\xf5\x8e\x89@\xa1_\xca\x15\xc6\xfbv\xb4,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3199,deliveryTag=l\xdb\xeb\xd2\x8e\xaf\xa3A\x9f0!\x8d\xfd\x1b\x1bQ,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3200,deliveryTag=a\x17C=\x12W\x08I\xbb\x146\x16\x9e\xb6~i,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: RECV[:5671|0] :
Transfer{handle=0,deliveryId=3201,deliveryTag=F}U\xdfT\xc6YJ\xa4\x19\x94\x90\xb9\xb1\xdf\x8d,messageFormat=0,more=false,batchable=true}
[15:50:08] FINE: SEND[:5671|0] :
Disposition{role=receiver,first=3190,last=3199,settled=true,state=Accepted{}}
[15:50:08] FINE: RECV[:5671|0] : End{}
[15:50:08] FINE: SEND[:5671|0] : Detach{handle=0}
[15:50:08] FINE: SEND[:5671|0] : End{}
[15:50:08] FINE: SEND[:5671|0] : End{}
[15:50:08] FINE: SEND[:5671|0] : Close{}
[15:50:08] FINE: RECV[:5671|0] : 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 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 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=java.util.logging.FileHandler
> FRM.level=ALL
>
> java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
> java.util.logging.SimpleFormatter.format=[%1$tc] %4$s: %5$s%n
>
> java.util.logging.FileHandler.level=ALL
>
> # (The output file is placed in the directory
> # defined by the "user.home" System property.)
> java.util.logging.FileHandler.pattern=%h/qpid-jms-%u.log
>
>
> When you run the client it should then generate a file called
> qpid-jms-0.log in your home directory, with output that looks something
> like:
>
> [Mon Feb 24 18:45:58 CET 2014] FINE: RECV[/127.0.0.1:5672|0] :
> SaslMechanisms{saslServerMechanisms=[ANONYMOUS]}
>
> Given that the mailing list strips off attachments, if the logs themselves
> don;t provide an immediate answer then raising a JIRA and attaching the
> logs to them is probaly the easiest way of sharing them.
>
> Hope this helps,
> Rob
>
>
> On 24 February 2014 18:04, Jan Bares <jan.ba...@wood.cz> wrote:
>
> > Hi,
> >
> > JMS 0.26 with AMQP 1.0 and Service Bus. I have concurrent producer and
> > receiver. The receiver.receive(70000) 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
> > close the consumer, it must be QPID itself. With the same code I also
> > sometimes see IllegalStateException: Closed when I call
> > message.acknowledge. Does it mean that server closed the connection?
> The
> > server is up and running all the time. Where should I look for more
> > details? The very same code works fine with MRG 2.3. I did found anything
> > usefull on the server side, I can run tcpdump on client if it helps.
> >
> > Kind regards, Jan
> >
> > javax.jms.IllegalStateException: Closed
> > at
> >
> org.apache.qpid.amqp_1_0.jms.impl.SessionImpl.checkClosed(SessionImpl.j
> ava:305)
> > at
> >
> org.apache.qpid.amqp_1_0.jms.impl.SessionImpl.acknowledgeAll(SessionIm
> pl.java:679)
> > at
> >
> org.apache.qpid.amqp_1_0.jms.impl.MessageImpl.acknowledge(MessageI
> mpl.java:1136)
> > at cz.baresovi.qpid.Qpid.consumeFromQueue(Qpid.java:411)
> > at cz.baresovi.qpid.Qpid.testConsumerMessagesBug(Qpid.java:180)
> > at cz.baresovi.qpid.Qpid$2.run(Qpid.java:128)
> >
> >
> > Jan Bareš
> > Calypso Lead Developer
> >
> > In association with
> > WOOD & Company Financial Services, a.s.
> > Palladium, Náměstí Republiky 1079/1a
> > 110 00 Prague, Czech Republic
> > Tel. +420 222 096 111
> > Direct +420 222 096 457
> > Fax. +420 222 096 222
> >
> >
> >
> >
> >
> > DISCLAIMER
> > ________________________________
> > WOOD & Company Financial Services, a.s. and its branches are
> > authorized and regulated by the CNB as Home State regulator and in
> Poland
> > by the KNF, in Slovakia by the NBS and in the UK by the FCA as Host State
> > regulators. For further information about WOOD & Co., its investment
> > services, financial instruments and associated risks, safeguard client
> > assets (incl. compensation schemes) and contractual relationship please
> see
> > our website at www.wood.com<http://www.wood.com/> under section
> Corporate
> > Governance.
> > Unless otherwise stated, this transmission is neither an offer
> > nor the solicitation of an offer to sell or purchase any investment. All
> > estimates, opinions and other information contained herein are subject to
> > change without notice and are provided in good faith but without legal
> > responsibility or liability. Opinion may be personal to the author and may
> > not reflect the opinions of WOOD & Co. Communications from sales
> persons,
> > sales traders or traders should not be regarded as investment research and
> > may contain opinions or trading ideas which are different from WOOD &
> Co.
> > investment research opinions.
> > This e-mail and any attachments are confidential and may be
> > privileged or otherwise protected from disclosure. If you are not a named
> > addressee you must not use, disclose, distribute, copy, print or rely on
> > this e-mail and any of its attachments. Please notify the sender that you
> > have received this email by mistake by replying to the email, and then
> > delete the email and any copies of it. Although WOOD & Co. routinely
> > screens e-mails for viruses, addressees should scan this e-mail and any
> > attachments for viruses. WOOD & Co. makes no representation or
> warranty as
> > to the absence of viruses in this e-mail or any attachments. Please note
> > that to ensure regulatory compliance and for the protection of our clients
> > and business, we may monitor and read e-mails sent to and from our
> > server(s).
> > ________________________________
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> >
DISCLAIMER
________________________________
WOOD & Company Financial Services, a.s. and its branches are
authorized and regulated by the CNB as Home State regulator and in Poland by
the KNF, in Slovakia by the NBS and in the UK by the FCA as Host State
regulators. For further information about WOOD & Co., its investment services,
financial instruments and associated risks, safeguard client assets (incl.
compensation schemes) and contractual relationship please see our website at
www.wood.com<http://www.wood.com/> under section Corporate Governance.
Unless otherwise stated, this transmission is neither an offer nor the
solicitation of an offer to sell or purchase any investment. All estimates,
opinions and other information contained herein are subject to change without
notice and are provided in good faith but without legal responsibility or
liability. Opinion may be personal to the author and may not reflect the
opinions of WOOD & Co. Communications from sales persons, sales traders or
traders should not be regarded as investment research and may contain opinions
or trading ideas which are different from WOOD & Co. investment research
opinions.
This e-mail and any attachments are confidential and may be privileged
or otherwise protected from disclosure. If you are not a named addressee you
must not use, disclose, distribute, copy, print or rely on this e-mail and any
of its attachments. Please notify the sender that you have received this email
by mistake by replying to the email, and then delete the email and any copies
of it. Although WOOD & Co. routinely screens e-mails for viruses, addressees
should scan this e-mail and any attachments for viruses. WOOD & Co. makes no
representation or warranty as to the absence of viruses in this e-mail or any
attachments. Please note that to ensure regulatory compliance and for the
protection of our clients and business, we may monitor and read e-mails sent to
and from our server(s).
________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
