9 a.m.
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Fix For: 4.2.1 CP2, 4.3
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Mark Little updated JBESB-1555:
-------------------------------
Component/s: Rosetta
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Fix For: 4.2.1 CP2, 4.3
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:55 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Tom Cunningham reassigned JBESB-1555:
-------------------------------------
Assignee: Tom Cunningham
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Assigned To: Tom Cunningham
Fix For: 4.3, 4.2.1 CP2
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:09 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Work on JBESB-1555 started by Tom Cunningham.
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Assigned To: Tom Cunningham
Fix For: 4.3, 4.2.1 CP2
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:45 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Noel Rocher updated JBESB-1555:
-------------------------------
Attachment: ServiceInvoker-loadbalance.tar.gz
Attached a simple testcase.
jbossall-client.jar should be added in injector/lib directory
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Assigned To: Tom Cunningham
Fix For: 4.2.1 CP2, 4.3
Attachments: ServiceInvoker-loadbalance.tar.gz
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:21 a.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Work on JBESB-1555 stopped by Tom Cunningham.
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Assigned To: Tom Cunningham
Fix For: 4.2.1 CP2, 4.3
Attachments: ServiceInvoker-loadbalance.tar.gz
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:21 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Tom Cunningham reassigned JBESB-1555:
-------------------------------------
Assignee: (was: Tom Cunningham)
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Fix For: 4.2.1 CP2, 4.3
Attachments: ServiceInvoker-loadbalance.tar.gz
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:24 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=comments#action_12401765 ]
Tom Cunningham commented on JBESB-1555:
---------------------------------------
Noel found that using jnp://${jboss.bind.address}:1099 for his for his JNDI url fixed this
problem. You also have to bind to an IP other than 127.0.0.1 (./run.sh -b
192.168.1.100 for example). Unassigning this issue for further investigation.
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Fix For: 4.2.1 CP2, 4.3
Attachments: ServiceInvoker-loadbalance.tar.gz
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:29 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=comments#action_12401825 ]
Kevin Conner commented on JBESB-1555:
-------------------------------------
Noel's analysis is spot on, as is his workaround.
The value in the address will reflect the server configuration if the JNDI properties are
not set but, unfortunately, it is only the JNDI properties which dictate where to look for
the queue. If the properties have not been specified then the client reading the EPR will
default to its own settings.
The simple fix will be to modify ListenerUtil to populate the default values although this
will not help those EPRs which are already registered in the repository.
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Fix For: 4.2.1 CP2, 4.3
Attachments: ServiceInvoker-loadbalance.tar.gz
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Kevin Conner reassigned JBESB-1555:
-----------------------------------
Assignee: Kevin Conner
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.3, 4.2.1 CP2
Attachments: ServiceInvoker-loadbalance.tar.gz
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Work on JBESB-1555 started by Kevin Conner.
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.3, 4.2.1 CP2
Attachments: ServiceInvoker-loadbalance.tar.gz
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:16 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1555) Investigate ServiceInvoker/policy behaviour
[ http://jira.jboss.com/jira/browse/JBESB-1555?page=all ]
Kevin Conner closed JBESB-1555.
-------------------------------
Resolution: Done
CP fixed in revision 18831.
trunk fixed in revision 18832.
Investigate ServiceInvoker/policy behaviour
-------------------------------------------
Key: JBESB-1555
URL: http://jira.jboss.com/jira/browse/JBESB-1555
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.1 CP2, 4.3
Attachments: ServiceInvoker-loadbalance.tar.gz
From Noel.
Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in
the load balancing behaviour.
I've got a very simple use case with a service deployed into 2 nodes
and sending 2 messages only.
With a debugger, I can see that the two EPR are used by the
ServiceInvoker and that the RoundRobin Policy that I've set is used to
choose alternatively each one.
However, I can see that the same JMS connection properties are reused
(by JMSCourier) instead of having the properties extracted from the
second EPR.
Is there a way for you to check this ?
------------------------------------------------
I forgot to mention that I'm sending messages to esb services from a standalone JSE
java application with the ServiceInvoker.
Going further, I can see that the EPR's <wsa:address .../> value is not used to
initialise the JMS connection. <ReferenceProperties /> are used instead. This
problem happens when the jndi-url is not setup for your esb service (because you want to
use the default value defined for your esb node in the
jbossesb.sar/jbossesb-properties.xml).
Then you have two ways to fix this :
- when declaring the EPR, reuse the wsa:address values when nothing is defined for the
provider (JMS)
- when the service invoker is creating the JMS connection to send the message, use the
<wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6131
days inactive
6149
days old
11 comments
4 participants
participants (4)
-
Kevin Conner (JIRA) -
Mark Little (JIRA)
-
Noel Rocher (JIRA)
-
Tom Cunningham (JIRA)