Thanks, I have updated the source but still get the same error.
javax.jms.InvalidDestinationException: The messaging entity
'my-namespace:topic:test.topic~15|test1' could not be found.
TrackingId:12ecc2a3-f8f3-42a3-8bd5-ad5d9823c367_B20,
SystemTracker:my-namespace:topic:test.topic~15|test1, Timest
Hi Robbie,
I just started testing the Qpid JMS 0.24.0 RC.
While compiling the src bundle and running the tests I got a test failure.
In the root project folder I ran:
mvn verify
The test in question is:
Tests run: 3, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 31.944 sec <<<
FAILURE!
On 08/08/17 02:05, Pankaj Bhagra wrote:
I am trying to extract bulk messages from azure SB.
As per their documentation the azure SDK doesn't support bulk read message
and recommends using the native amqp for the Azure Service Bus. White
trying to negotiate a session with the azure SB, i noticed
Does a non-durable subscription work?
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
Tested to change but the same error.
//subscriber = subscriberSession.createDurableSubscriber(topic,
"DurableSubscriber1");
subscriber = subscriberSession.createConsumer(topic);
In the exception - what is "~15" characters?
javax.jms.InvalidDestinationException: The messaging ent
Hi,
Using Qpid JMS 0.23 with Azure Service Bus.
When using the URI:
amqps://my-namespace.servicebus.windows.net:5671"
I get:
javax.jms.JMSException: Idle timeout value specified in connection OPEN
('3 ms') is not supported. Minimum idle timeout is '6' ms.
When setting
amqps://my-namespa
On 8 August 2017 at 11:09, 4 Integration <4integrat...@gmail.com> wrote:
> Hi,
>
> Using Qpid JMS 0.23 with Azure Service Bus.
> When using the URI:
>
> amqps://my-namespace.servicebus.windows.net:5671"
>
> I get:
> javax.jms.JMSException: Idle timeout value specified in connection OPEN
> ('3
Thanks for explanation.
/ Joacim
On Tue, Aug 8, 2017 at 11:25 AM, Rob Godfrey
wrote:
> On 8 August 2017 at 11:09, 4 Integration <4integrat...@gmail.com> wrote:
>
> > Hi,
> >
> > Using Qpid JMS 0.23 with Azure Service Bus.
> > When using the URI:
> >
> > amqps://my-namespace.servicebus.windows.n
>From the logs an issue occurred on the broker side during the test.
The client might need work to better handle such a scenario (though
might not, will look further when I'm not on vacation) but I don't see
anything suggesting a client regression here, and it seems to be rare
given you are the fir
Hi,
tests performed:
* verify checksums and signatures
* mvn apache-rat:check
* build from source
* run tests from source (mvn verify)
1 test failure.
-> Robbies analysis indicates no client issue
* run tests of bin release examples
* run HelloWorld from bin release against qpid-broker
There were 5 binding +1 votes, 1 non-binding +1 community vote, and no
other votes received. The vote has passed.
I will add the archives to the dist release repo and release the maven
staging repo shortly. The website will be updated once the artifacts
have had time to sync to the mirrors and mav
+1
* ran qpid system tests with jms-client 0.24 against qpid-broker-j
* built jms-client from source distribution
On 4 August 2017 at 22:42, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a spin for a 0.24.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
As suggested by Gordon => Running with env var PN_TRACE_FRM=1 and post the
protocol trace you see.
Configured a proper logger and got more details:
2017-08-08T12:27:31.202 TRACE [org.apache.qpid.jms.transports.TransportSupport]
- Getting SSLContext instance using protocol: TLS
2017-08-08T12:27:3
On 08/08/17 12:27, 4 Integration wrote:
As suggested by Gordon => Running with env var PN_TRACE_FRM=1 and post the
protocol trace you see.
Configured a proper logger and got more details:
This looks like either there is no source called test.topic configured
on the service bus, or it doesn't
Additional input from Gordon: "
*This looks like either there is no source called test.topic configured on
the service bus, or it doesn't like the 'topic' capability. (You could try
a further experiment with another see if we can rule out one or other of
these).The ~15 seems to be coming from some
On 08/08/17 12:46, 4 Integration wrote:
/(Also, service bus appears to be sending the detach *before* echoing
the attach, which is a protocol error)./
Just for clarification, that part was from a different run where the
detach was before the attach. That is not the case on the latest trace.
On 08/08/17 12:37, Gordon Sim wrote:
You could try a further experiment with another see if we can rule out
one or other of these
E.g. if it is easy to get proton python client, you could use the
simple_recv.py example with -a
my-namespace.servicebus.windows.net:5671/test.topic and see what t
On the topic defined in Azure Service Bus "test.topic" I have a static
subscription defined named "sub1".
When publishing I use:
env.put("topic.TOPIC", "test.topic");
When subscribing to "sub1" I have
env.put("topic.TOPIC", "test.topic/Subscriptions/sub1");
The naming here seems required i.e.
<>
18 matches
Mail list logo
