[JBoss JIRA] Created: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
5:06 p.m.
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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
5:14 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=comments#action_12359331 ]
Burr Sutter commented on JBESB-507:
-----------------------------------
Steps to recreate issue:
1) Copy the sample-bindings.xml from the JBoss Application Server to a known location
2) Copy bindingservice-plugin.jar to the ESB Server's default\lib directory
3) Modify the ESB Server's conf\jboss-service.xml by finding the
ServiceBindingManager, uncomment it and tweak the settings like so:
<mbean code="org.jboss.services.binding.ServiceBindingManager"
name="jboss.system:service=ServiceBindingManager">
<attribute name="ServerName">ports-01</attribute>
<attribute
name="StoreURL">/labs/binding_manager/jboss-bindings.xml</attribute>
<attribute name="StoreFactoryClassName">
org.jboss.services.binding.XMLServicesStoreFactory
</attribute>
</mbean>
Edit the "StoreURL" to point to where you dropped and how you names the
sample-bindings.xml file. I renamed my sample-bindings.xml to jboss-bindings.xml.
Perhaps we'll ship with an esb-bindings.xml when this issue is resolved.
4) Modify the esb.juddi.properties in server\default\deploy\jbossesb.sar\ to point to the
new JNDI portjava.naming.provider.url=jnp://localhost:1099
To
java.naming.provider.url=jnp://localhost:1199
5) Start the server and you'll see the error:
16:42:41,953 INFO [JuddiRMIService] starting juddi RMI service
16:42:47,984 ERROR [STDERR] javax.naming.CommunicationException: Could not obtai
n connection to any of these urls: localhost:1099 and discovery failed with erro
r: javax.naming.CommunicationException: Receive timed out [Root exception is jav
a.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming
.CommunicationException: Failed to connect to server localhost:1099 [Root except
ion is javax.naming.ServiceUnavailableException: Failed to connect to server loc
alhost:1099 [Root exception is java.net.ConnectException: Connection refused: co
nnect]]]
Note: this might be user error as well. However, we need to include the bindings.xml and
the plugin.jar in the default download for ESB 4.2 M2. Plus we'll need to document
how this feature is enabled.
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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:42 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=all ]
Mark Little reassigned JBESB-507:
---------------------------------
Assignee: Kurt Stam (was: Mark Little)
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Kurt Stam
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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:44 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=all ]
Mark Little updated JBESB-507:
------------------------------
Priority: Critical (was: Major)
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Kurt Stam
Priority: Critical
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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
4:19 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=all ]
Mark Little reassigned JBESB-507:
---------------------------------
Assignee: Tom Cunningham (was: Kurt Stam)
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Tom Cunningham
Priority: Critical
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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
3:53 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=all ]
Work on JBESB-507 started by Tom Cunningham.
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Tom Cunningham
Priority: Critical
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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
6:22 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=comments#action_12361101 ]
Tom Cunningham commented on JBESB-507:
--------------------------------------
The juddi part of this is fixed. Need to find out where to package the plugin.jar.
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Tom Cunningham
Priority: Critical
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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
5:22 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=comments#action_12361166 ]
Tom Cunningham commented on JBESB-507:
--------------------------------------
Added bindings jar to esbserver zip. Now writing up something which explains the
process of using multiple servers and the jboss-messaging/juddi steps.
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Tom Cunningham
Priority: Critical
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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:37 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=all ]
Tom Cunningham resolved JBESB-507.
----------------------------------
Resolution: Done
Added text noting jboss-messaging remoting.xml/ServiceBinding manager issue to
Administrator Guide.
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Tom Cunningham
Priority: Critical
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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
10:02 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-507) Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
[ http://jira.jboss.com/jira/browse/JBESB-507?page=all ]
Mark Little closed JBESB-507.
-----------------------------
Federated: Multiple ESB Servers on same machine - jboss-bindings.xml
--------------------------------------------------------------------
Key: JBESB-507
URL: http://jira.jboss.com/jira/browse/JBESB-507
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Tom Cunningham
Priority: Critical
Fix For: 4.2 Milestone Release 2
In 4.0 it was possible to bring up multiple JVMs hosting an instance of the ESB each with
unique services. A single message flow could be routed throughout all the different
ESB/JVMs. The aggregator quickstart demonstrated this concept.
In the 4.2 M1 (head), the new ESB Server uses several new ports (JNDI, HTTP, etc) that
conflict with other running ESB Servers. You can now basically only run a single ESB
Server per machine.
The traditional approach to resolve this issue involves using the ServiceBindingManager
MBean identified in jboss-service.xml. However, it does not seem to work. jUDDI
complains (upon ESB Server boot up).
More details in the comments
--
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
6269
days inactive
6288
days old
9 comments
3 participants
participants (3)
-
Burr Sutter (JIRA) -
Mark Little (JIRA)
-
Tom Cunningham (JIRA)