The Qpid Java Broker has a web ui for configuration:
https://qpid.apache.org/releases/qpid-0.32/java-broker/book/Java-Broker-Management-Channel-Web-Console.html
Or which applications of Qpid do you mean?
--
View this message in context:
Hi Robbie,
thanks for the hint. I just asked my QA who found this issue and he told me
that he changed the windows system time for another test case.
Regards,
Erik
--
View this message in context:
Unfortunately logging was only enabled for the frame and byte logger when
this error happend. I will enable all other loggers too and try to reproduce
this error...
--
View this message in context:
As I can see in the Qpid JMS frame log, the empty frames are send when no
other messages are send for some time:
The interval of the hearbeat messages seems to be something around 7 seconds
in my case when looking in the log file. I guess that is the interval that
is defined by the broker? But
Dear Qpid-Users,
I'm using the Qpid JMS (0.6.0). The provider of the service my client
application connects to has informed me that it has changed it's message
plattform from JBoss A-AMQ 6.1 to A-MQ 6.2:
/Please note AMQ 6.2 comes with an automatic heartbeat / connectivity
monitoring built in
Ok, so sending heartbeats from the client is working automatically when the
broker requested it.
Thanks,
Erik
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Qpid-JMS-Idle-timeout-inactivity-handling-tp7632838p7632840.html
Sent from the Apache Qpid users mailing list
Dear Qpid users,
I'm having a client application which uses the Qpid JMS API to connect to an
AMQP broker.
Is it possibe that messages which were sent successfully (without any
errors) by the Qpid JMS API did not arrive at the brokers queue? I thought
that should not happen when using the AMQP
Do you know what version of AMQP it is? e.g. is it AMQP 1.0?
Yes, it is AMQP 1.0.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Lost-of-messages-possible-in-AMQP-tp7627251p7627254.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
+1
I tested it with my client application and found nothing suspicious so far.
Just one little thing: the logging for the received bytes uses Recieved:
instead of Received: as prefix ;-)
Regards,
Erik
--
View this message in context:
Hi Robbie,
yes we are using the logs from the Qpid client API. We need them currently
the most of the time if something is wrong in the data we received from the
broker. Then we send the log files as evidence to the provider of the
service we are connecting to with our client application.
Is
Dear Qpid users,
the Qpid JMS 0.2.0 release contains the library
qpid-jms-discovery-0.2.0.jar. What is it good for?
Regards,
Erik
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Qpid-JMS-discorvery-tp7625966.html
Sent from the Apache Qpid users mailing list archive at
Dear Qpid users,
the old Qpid client API used the loggers FRM and RAW. These were
replaced by the loggers org.apache.qpid.jms.provider.amqp.FRAMES and
org.apache.qpid.jms.provider.amqp.BYTES. The byte logger only logs sent
data. Why doesn't it log the received data also? This would be interesting
Dear Qpid users,
if have tried the new proton based client and there seems to be no problems
with decoding the received messages until now.
Regards,
Erik
--
View this message in context:
Dear Qpid users,
here is another difference I noticed between the old and the new client API:
The correlation ID of a received message which can be obtained via (JMS)
Message.getJMSCorrelationID() now has the prefix ID:. So I had to change
my code because my application uses this ID to map
Dear Qpid users,
I'm using the Qpid Java JMS client 0.32 to connect to an AMQP broker.
My applications uses 3 broadcast topic listeners listening to different
topics. When my application starts it receives a lot of data from the AMQP
broker. Since some time I notice the following AMQP exception
Hi Rob,
yes, the connection is SSL encrypted.
Regards,
Erik
--
View this message in context:
http://qpid.2158936.n2.nabble.com/AmqpErrorException-when-receiving-broadcast-data-tp7625647p7625649.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Dear Qpid users.
I'm using the QPID JMS AMQP 1.0 Java Client (v0.30).
Do you know and/or use any tools that could help analyzing the log files
created by the JMS client?
For example it would be nice to have something that creates something more
human readable out of from the RAW log:
Hi Rob,
thanks for making this clear. Yes I have turned the FRM logging on also but
I'm logging FRM and RAW to different files.
Regards,
Erik
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Tools-to-analyze-QPID-JMS-client-log-files-tp7623982p7623990.html
Sent from the
Hi Rob,
thank you again for your answer. I requested the server logs from the
service provider who runs the broker. I keep you posted ;-)
Regards,
Erik
--
View this message in context:
PS: Here is the FRM-Log (in an anonymised form ;-)):
Qpid-API-frm.log
http://qpid.2158936.n2.nabble.com/file/n7620481/Qpid-API-frm.log
Maybe it would be needed to use heartbeats to keep the session alive?
Nevertheless why dos the exception listener of the connection don´t get a
exception if
Dear Qpid users,
I'm using the Qpid AMQP 1.0 JMS client to connect to a ActiveMQ message
broker.
Sometimes I'm getting a MessageProducerException (Force detach the link
because the session is remotely ended.) when I'm trying to send a message to
the broker.
As for as I understand the error
Hi Rob,
thanks for the answer.
But the problem is that im trying to send a message at 2015-02-18
12:36:18.925 and after that, the detaches are logged. So the detaches are
triggered by the client and not the broker? Why?
Here are the last to lines from the RAW log:
2015-02-18 11:50:43.696:
Hi Rob,
thanks for this information.
Is there a plan when the proton based JMS AMQP 1.0 client will be available?
Do you think, that the workaround suggested by Keith (using a dedicated
connetion for each message listener) would work?
Regards,
Erik
--
View this message in context:
Hi Keith,
thanks for your answer. I changed my application code so that messages
listeners are not blocking anymore and delegating the message processing as
fast as possible to other threads.
Maybe I raise a Jira ticket if I notice still problems with this issue.
Regards,
Erik
--
View this
Ok, here are the missing details:
I'm using the Java Qpid JMS client for AMQP 1.0 (version 0.30).
The broker I'm connecting to also uses AMQP 1.0 and is from Red Hat (as far
as I know). Actually I don't have other informations about the broker than
the AMQP version.
To make the problem clearer
Dear Qpid Users,
I have an application where I'm using different message listeners to process
data from different topics.
For example I have a message listener which processes reference data
received via a broadcast topic and another message listener which processes
market data like trades and
Hi Qpid-Devs,
when can we expect the release of Qpid 0.30?
Thanks in advance!
Erik
--
View this message in context:
http://qpid.2158936.n2.nabble.com/0-30-release-update-Release-notes-preview-tp7612791p7613743.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Dear Qpid users,
so nobody has experiences with Qpid AMQP 1.0 JMS client in production so
far?
Regards,
Erik
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Experiences-with-Qpid-AMQP-1-0-JMS-client-in-production-tp7611393p7612537.html
Sent from the Apache Qpid users
Hi Rob,
thank you for your answers.
I will share my experiences when I'm able to test against the AMQP 1.0
broker to which I have to connect.
Do you have a plan when the proton based JMS client will be ready?
Kind Regards,
Erik
--
View this message in context:
Hi there,
does anyone have experiences with the Qpid AMQP 1.0 JMS client (v.0.28) in
production? Is it reliable to use or is it in an experimental state?
I have to build an application that is connected to a server application
that uses an AMQP 1.0 broker for its messaging API. I could not test
+1 for this post. This information should actually be provided in the Qpid
JMS client documenation.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Connection-URI-query-string-parameters-AMQP-1-0-JMS-client-tp7610959p7610981.html
Sent from the Apache Qpid users mailing list
that logging on.
Is this the sort of logging you were looking for, or something else?
-- Rob
On 20 July 2014 15:56, Erik Aschenbrenner erika@gmail.com
erikaschenbren...@gmail.com
wrote:
Hi there,
in Qpid JMS AMQP 0.9 and 0.10 there was slf4j which could be used to get
logging
Hi there,
in Qpid JMS AMQP 0.9 and 0.10 there was slf4j which could be used to get
logging information from the JMS client.
In 1.0 there is no logging at all. Will it be included again?
Regards,
Erik
33 matches
Mail list logo
