On 3 June 2015 at 15:54, Erik Aschenbrenner wrote:
> Ok, now I have another problem.
>
> My program now hangs when creating the first jms session
> (Connection.createSession (false, Session.AUTO_ACKNOWLEDGE);
>
> Any ideas?
>
> If I'm changing "amqp" to "amqps" in my connection url
> (amqps://123.
Ok, now I have another problem.
My program now hangs when creating the first jms session
(Connection.createSession (false, Session.AUTO_ACKNOWLEDGE);
Any ideas?
If I'm changing "amqp" to "amqps" in my connection url
(amqps://123.12.12.123:12345?ssl=true&ssl-cert-alias=x&clientid=ConnectionT
Ok, now I have another problem.
My program now hangs when creating the first jms session
(Connection.createSession (false, Session.AUTO_ACKNOWLEDGE);
Any ideas?
If I'm changing "amqp" to "amqps" in my connection url
(amqps://123.12.12.123:12345?ssl=true&ssl-cert-alias=x&clientid=ConnectionT
On 3 June 2015 at 14:50, Timothy Bish wrote:
> On 06/03/2015 09:45 AM, Erik Aschenbrenner wrote:
>> Dear Qpid-Users,
>>
>> I just tried to use the new proton based Qpid JMS 0.2.0 client.
>>
>> I removed the jars of the old client (Qpid JMS 0.32) and added the jars of
>> the new client to my projec
OK, I see: the InitialContextFactory class changed to
org.apache.qpid.jms.jndi.JmsInitialContextFactory.
Regards,
Erik
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Changing-from-old-Qpid-JMS-client-to-Qpid-JMS-0-2-0-tp7625652p7625655.html
Sent from the Apache Qpid users m
Hi Erik,
In the properties, where you configure the connection URI / destinations,
you usually also configure the context factory, which is different for the
new JMS client. So instead of something like this:
java.naming.factory.initial=org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialCo
nt
On 06/03/2015 09:45 AM, Erik Aschenbrenner wrote:
> Dear Qpid-Users,
>
> I just tried to use the new proton based Qpid JMS 0.2.0 client.
>
> I removed the jars of the old client (Qpid JMS 0.32) and added the jars of
> the new client to my project.
>
> When I try to start my application I'm getting
Dear Qpid-Users,
I just tried to use the new proton based Qpid JMS 0.2.0 client.
I removed the jars of the old client (Qpid JMS 0.32) and added the jars of
the new client to my project.
When I try to start my application I'm getting this exception:
javax.naming.NoInitialContextException: Cannot
:-(
So either the message was incorrectly encoded when it was sent, or
there is an error in the client.
Have you tried retrieving the message with a different client (such as
the new Proton based JMS client)?
-- Rob
On 3 June 2015 at 14:29, Erik Aschenbrenner wrote:
> Hi Rob,
>
> yes, the conn
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.
So the error is indicating that the client cannot decode the incoming
message - in particular it seems to believe the data is malformed. It
is trying to decode the message data (section)... it seems to be
interpreting the data as saying the described type has a String which
is encoded as having le
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 o
12 matches
Mail list logo
