Fantastic - thanks for all your help in identifying and diagnosing the
issue!
-- Rob
On 15 March 2016 at 15:35, Adel Boutros wrote:
> Hello Tim, Rob,
>
> Following Tim's fix, I re-launched my test and everything works fine. Both
> Issues are fixed.
>
> Thank you for your quick reaction.
>
> Reg
Hello Tim, Rob,
Following Tim's fix, I re-launched my test and everything works fine. Both
Issues are fixed.
Thank you for your quick reaction.
Regards,
Adel Boutros
Murex SAS
www.murex.com
On Fri, Mar 11, 2016 at 4:50 PM, Rob Godfrey
wrote:
> Great - thanks!
>
> -- Rob
>
> On 11 March 2016
Great - thanks!
-- Rob
On 11 March 2016 at 15:37, Adel Boutros wrote:
> I have created the Jira issue under
> https://issues.apache.org/jira/browse/QPIDJMS-154
>
> Regards,
> Adel
>
> On Fri, Mar 11, 2016 at 11:25 AM, Rob Godfrey
> wrote:
>
> > Thanks for all the detailed investigation. Sadly
I have created the Jira issue under
https://issues.apache.org/jira/browse/QPIDJMS-154
Regards,
Adel
On Fri, Mar 11, 2016 at 11:25 AM, Rob Godfrey
wrote:
> Thanks for all the detailed investigation. Sadly the Apache mailing lists
> strip off inline images from mails :-(
>
> Probably the best th
Thanks for all the detailed investigation. Sadly the Apache mailing lists
strip off inline images from mails :-(
Probably the best thing to do is to raise a JIRA issue for the JMS client:
https://issues.apache.org/jira/browse/QPIDJMS (if you don't already have an
account you'll need to create one
PS: I am using qpid-jms-client 0.8.0
Regards,
Adel
On Fri, Mar 11, 2016 at 11:07 AM, Adel Boutros wrote:
> Hello guys,
>
> I have debugged a bit and made some progress. The problem is with the
> multi-thread handling. The main thread exits before the Failover trial
> thread has tried the 2nd co
Hello guys,
I have debugged a bit and made some progress. The problem is with the
multi-thread handling. The main thread exits before the Failover trial
thread has tried the 2nd connection URL and is this exiting with a
connection to the unreachable virtual host
You can see in the logs below what
Hello Tim,
Please find below a complete test case:
*Code*
public class ScalabilityTest {
//~
//~ Methods
//~
---
To expand a little further for Tim/Robbie:
After a connection is established with the Java Broker, it needs to route
the connection to the desired virtual host within the broker (which it uses
the host in the open frame to identify). If there is no such virtual host,
or if the virtual host is not
Hello Tim,
The error is happening when trying to create a session with the below
failover URL when the first URL is that of the REPLICATE. I am using the
amqp.vhost option to specify the virtual host, could that be the issue? I
mean the vhost is not present on the REPLICATE machine.
failover:(amq
On 03/10/2016 06:12 PM, Rob Godfrey wrote:
On 10 March 2016 at 23:44, Adel Boutros wrote:
If I compile while skipping tests and deploy the jar then the broker no
longer crashes.
Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
below stack. If I put back the MASTER UR
On 03/10/2016 05:44 PM, Adel Boutros wrote:
If I compile while skipping tests and deploy the jar then the broker no
longer crashes.
Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
below stack. If I put back the MASTER URL before the Replicate URL, then
everything works
On 11 March 2016 at 00:07, Rob Godfrey wrote:
> OK - that's my fault, I need to fix some of the mocking in that test... I
> will do that shortly - you can ignore this issue in the meantime.
>
>
I've merged the fixes for the mocking in the unit tests to the 6.0.x branch
so the test failures should
On 10 March 2016 at 23:44, Adel Boutros wrote:
> If I compile while skipping tests and deploy the jar then the broker no
> longer crashes.
> Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
> below stack. If I put back the MASTER URL before the Replicate URL, then
> eve
OK - that's my fault, I need to fix some of the mocking in that test... I
will do that shortly - you can ignore this issue in the meantime.
-- Rob
On 10 March 2016 at 23:36, Adel Boutros wrote:
> Hello Rob,
>
> I have 3 tests failing under *ProtocolEngine_1_0_0Test* when compiling
> *broker-plu
Hello Rob,
I have 3 tests failing under *ProtocolEngine_1_0_0Test* when compiling
*broker-plugins
6.0.2-SNAPSHOT *in Intellij or maven
- ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslNonTLSandAnon
- ProtocolEngine_1_0_0Test.testProtocolEngineWithNoSaslTLSandExternal
- ProtocolEngi
If I compile while skipping tests and deploy the jar then the broker no
longer crashes.
Nevertheless, the client doesn't try the 2nd URL, instead it fails with the
below stack. If I put back the MASTER URL before the Replicate URL, then
everything works fine.
It seems to me that the order in which
Apologies for this - you have indeed run into bug :-(
I've raised a JIRA - https://issues.apache.org/jira/browse/QPID-7136 .
I've committed a fix both to trunk, and the 6.0.x branch which I hope will
fix this issue... If you want to test it out you can use the 6.0.x branch
which can be found her
Hello,
When we provide a failover URL where the first URL is that of a replicate
broker, the connection will trigger an IllegalStateException which is not
caught anywhere. Thus making the broker crash and the session creation fail
on the client-side.
Shouldn't the "close" method log the exception
19 matches
Mail list logo
