[JBoss JIRA] Created: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
1:04 p.m.
JBossRemotingGateway listener should support multiple listeners for the same host port
combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.3
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to identify
the path that will be used by a ws client that calls the service. Talked to Tom and he
suggested placing the path property on the jbr-bus element so I'll change that. The
attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting forum
if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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
1:06 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[ http://jira.jboss.com/jira/browse/JBESB-1557?page=all ]
Daniel Bevenius updated JBESB-1557:
-----------------------------------
Attachment: webservice_producer.jar
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.3
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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
1:06 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[ http://jira.jboss.com/jira/browse/JBESB-1557?page=all ]
Daniel Bevenius updated JBESB-1557:
-----------------------------------
Attachment: jboss-remoting.jar
jbossesb-config-model-1.0.1.jar
jbossesb-rosetta.jar
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.3
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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
1:10 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[ http://jira.jboss.com/jira/browse/JBESB-1557?page=comments#action_12400418 ]
Daniel Bevenius commented on JBESB-1557:
----------------------------------------
Just a note about how I tested this...
1. Browse to http://localhost:8080/contract/
2. Open soapui and create two projects with the Http Contract URLs for :
MyServiceCategory:MyWSProducerService
and
MyServiceCategory:MyWSProducerService2
3. Run service1 and it will invoke service1 in the ESB and so on.
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.3
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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:24 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[ http://jira.jboss.com/jira/browse/JBESB-1557?page=comments#action_12400470 ]
Daniel Bevenius commented on JBESB-1557:
----------------------------------------
I'll add a ConnectorManager that stores the jbr Connectors in JNDI and that should
take care of the issue with single jvm or classloader issue. I'll make this generic so
other types can be stored and not only jbr connectors.
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.3
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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:52 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[ http://jira.jboss.com/jira/browse/JBESB-1557?page=comments#action_12400478 ]
Kevin Conner commented on JBESB-1557:
-------------------------------------
Hiya Daniel.
Please hold off on committing this at the moment as this area may be about to change.
Thanks,
Kev
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.3
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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
2 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[ http://jira.jboss.com/jira/browse/JBESB-1557?page=comments#action_12400580 ]
Daniel Bevenius commented on JBESB-1557:
----------------------------------------
No problem. I won't commit anything until I hear from you.
I'm a little curious about the change you mentioned :) Any thing you are allowed to
tell me about?
Thanks,
Daniel
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.3
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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:40 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[ http://jira.jboss.com/jira/browse/JBESB-1557?page=all ]
Kevin Conner updated JBESB-1557:
--------------------------------
Fix Version/s: 4.4
(was: 4.3)
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.4
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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:28 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[ http://jira.jboss.com/jira/browse/JBESB-1557?page=all ]
Kevin Conner updated JBESB-1557:
--------------------------------
Fix Version/s: 4.x
(was: 4.4)
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: http://jira.jboss.com/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Fix For: 4.x
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
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:26 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[
https://jira.jboss.org/jira/browse/JBESB-1557?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1557:
-------------------------------------
We will be investigating tomcat/servlets as the HTTP provider in preference to JBR for ESB
4.5 and this should support multiplexing.
I am leaving this issue open until we have made further progress on the servlet work.
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: https://jira.jboss.org/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.x
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[
https://jira.jboss.org/jira/browse/JBESB-1557?page=com.atlassian.jira.plu...
]
Mark Little closed JBESB-1557.
------------------------------
Resolution: Won't Fix
Won't fix in the JBR support. The to be added Tomcat support already addresses this.
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: https://jira.jboss.org/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assignee: Mark Little
Fix For: 4.x
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[
https://jira.jboss.org/jira/browse/JBESB-1557?page=com.atlassian.jira.plu...
]
Mark Little reassigned JBESB-1557:
----------------------------------
Assignee: Mark Little (was: Daniel Bevenius)
Discussed with Daniel and assigning to me.
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: https://jira.jboss.org/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assignee: Mark Little
Fix For: 4.x
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:10 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[
https://jira.jboss.org/jira/browse/JBESB-1557?page=com.atlassian.jira.plu...
]
Mark Little reopened JBESB-1557:
--------------------------------
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: https://jira.jboss.org/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assignee: Mark Little
Fix For: 4.5
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:10 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[
https://jira.jboss.org/jira/browse/JBESB-1557?page=com.atlassian.jira.plu...
]
Mark Little closed JBESB-1557.
------------------------------
Fix Version/s: 4.5
(was: 4.x)
Resolution: Done
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: https://jira.jboss.org/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assignee: Mark Little
Fix For: 4.5
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:13 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[
https://jira.jboss.org/jira/browse/JBESB-1557?page=com.atlassian.jira.plu...
]
Mark Little reopened JBESB-1557:
--------------------------------
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: https://jira.jboss.org/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assignee: Mark Little
Fix For: 4.5
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1557) JBossRemotingGateway listener should support multiple listeners for the same host port combination
[
https://jira.jboss.org/jira/browse/JBESB-1557?page=com.atlassian.jira.plu...
]
Mark Little closed JBESB-1557.
------------------------------
Resolution: Won't Fix
JBossRemotingGateway listener should support multiple listeners for
the same host port combination
--------------------------------------------------------------------------------------------------
Key: JBESB-1557
URL: https://jira.jboss.org/jira/browse/JBESB-1557
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.3
Reporter: Daniel Bevenius
Assignee: Mark Little
Fix For: 4.5
Attachments: jboss-remoting.jar, jbossesb-config-model-1.0.1.jar,
jbossesb-rosetta.jar, webservice_producer.jar
Add support for having multiple jbr listeners listen to the same host port combination:
<jbr-provider name="JBR-Http" protocol="http"
host="localhost" path="service1">
<jbr-bus busid="Http-1" port="8765" />
</jbr-provider>
<jbr-provider name="JBR-Http2" protocol="http"
host="localhost" path="service2">
<jbr-bus busid="Http-2" port="8765"/>
</jbr-provider>
Also notice the addition of the path configuration parameter. This is intended to
identify the path that will be used by a ws client that calls the service. Talked to Tom
and he suggested placing the path property on the jbr-bus element so I'll change that.
The attached example uses this way just as a proof-of-concept (too lazy to change it right
now)
The path is used by the JBossRemoteGatewayListener as the subsystem when adding
InvokationHandlers to a Connector. So we are bascically keeping track of JBoss Remting
Connectors that share the same host/port combination, and adding InvokationHandlers to
them with the above specifed path as their subsystem.
This solution requires that the JBoss Remoting ServerInvoker be modified and adding
something like this:
String subsystem = invocation.getSubsystem();
String clientId = invocation.getSessionId();
Map requestPayload = invocation.getRequestPayload();
if ( subsystem == null && requestPayload != null )
{
String path = (String) requestPayload.get( HTTPMetadataConstants.PATH );
subsystem = path.substring( path.indexOf( '/' ) + 1 );
}
log.info( "subsystem : " + subsystem );
This is needed so it can set the incoming path as the target subsystem.
I'm not sure if this is the best way to do this but I'll ask in the Remoting
forum if they have a better suggestion.
Really, the gain with this is that we can have multiple webservice running in a ESB
instance using the same port. This is important because we it becomes difficult opening a
separate port for every web service. This is the issue we are facing at the moment.
Note that this solution does not work when running multiple ESB instances on the same
machine, as this would still cause a port conflict. The solution is specific to a single
JVM.
Any thought or comments on this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5603
days inactive
5961
days old
15 comments
3 participants
participants (3)
-
Daniel Bevenius (JIRA) -
Kevin Conner (JIRA)
-
Mark Little (JIRA)