12:12 a.m.
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Priority: Critical
Attachments: soapproxy-breaker.zip
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
12:12 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3021) SOAPProxies on different services shares configuration
[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
Jiri Pechanec updated JBESB-3021:
---------------------------------
Attachment: soapproxy-breaker.zip
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Priority: Critical
Attachments: soapproxy-breaker.zip
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
3:16 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3021) SOAPProxies on different services shares configuration
[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3021:
-------------------------------------
Can you add a log file for this please, pointing out the part you believe to be in error?
Thanks
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Priority: Critical
Attachments: soapproxy-breaker.zip
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
4:10 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3021) SOAPProxies on different services shares configuration
[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
Jiri Pechanec updated JBESB-3021:
---------------------------------
Attachment: two_proxies.log.gz
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Priority: Critical
Attachments: soapproxy-breaker.zip, two_proxies.log.gz
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
4:38 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3021) SOAPProxies on different services shares configuration
[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-3021:
--------------------------------
Fix Version/s: 4.7 CP1
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Priority: Critical
Fix For: 4.7 CP1
Attachments: soapproxy-breaker.zip, two_proxies.log.gz
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
2:51 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3021) SOAPProxies on different services shares configuration
[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
David Ward reassigned JBESB-3021:
---------------------------------
Assignee: David Ward
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Assignee: David Ward
Priority: Critical
Fix For: 4.7 CP1
Attachments: soapproxy-breaker.zip, two_proxies.log.gz
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
3:18 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3021) SOAPProxies on different services shares configuration
[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3021:
-----------------------------------
Hmmm... I wonder if HttpClient is statically "sharing" configuration data per
endpointUrl. Both your services have the same endpointUrl, and they are in the same
classloader, so it's possible that the 2nd set of http-client-properties are
overwriting the 1st. I'll have to investigate. There's nothing in
HttpSOAPProxyTransport that's jumping out at me at being the culprit. I'll also
look at HttpRouter, as HttpSOAPProxyTransport uses it under the covers. I'll let you
know what I find.
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Assignee: David Ward
Priority: Critical
Fix For: 4.7 CP1
Attachments: soapproxy-breaker.zip, two_proxies.log.gz
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
1:41 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-3021) SOAPProxies on different services shares configuration
[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-3021.
-----------------------------
Resolution: Done
My initial guess was close. There was nothing wrong with SOAPProxy. It was static
caching done by HttpClient (used by our HttpRouter/HttpProtocol). I blame HttpClient.
Thank goodness for open source, otherwise I wouldn't have figured out what the heck it
was doing, or how to fix it. Basically, HttpClient's "Protocol" class has a
static map where it caches Protocol instances. Inside a protocol instance is a
SocketFactory. So what was happening was that every time a new HttpRouter is created - IN
THE SAME CLASSLOADER - the SocketFactory would get clobbered. Last one wins. The fix was
to use one of the overloaded methods of executeMethod, where I could pass in an
action-scoped HttpConfiguration with the proper Protocol. I also had to change the
MethodFactories so that they only constructed non-absolute URI's (otherwise
SocketFactory would get clobbered again, believe it or not). This bug would have hit any
use of HttpRouter (not just SOAPProxy) where one configures different
protocol-socket-factory(ies). OMG, what spaghetti code HttpClient 3.0.1 is. I wonder if
4.0.x is any better...
[dward@dwardlinux JBESB_4_7_CP]$ svn commit
product/rosetta/src/org/jboss/soa/esb/http/configurators/HttpProtocol.java
product/rosetta/src/org/jboss/soa/esb/actions/routing/http/HttpRouter.java
product/rosetta/src/org/jboss/soa/esb/actions/routing/http/GETHttpMethodFactory.java
product/rosetta/src/org/jboss/soa/esb/actions/routing/http/AbstractHttpMethodFactory.java
product/rosetta/src/org/jboss/soa/esb/actions/routing/http/POSTHttpMethodFactory.java
Adding
product/rosetta/src/org/jboss/soa/esb/actions/routing/http/AbstractHttpMethodFactory.java
Sending
product/rosetta/src/org/jboss/soa/esb/actions/routing/http/GETHttpMethodFactory.java
Sending product/rosetta/src/org/jboss/soa/esb/actions/routing/http/HttpRouter.java
Sending
product/rosetta/src/org/jboss/soa/esb/actions/routing/http/POSTHttpMethodFactory.java
Sending product/rosetta/src/org/jboss/soa/esb/http/configurators/HttpProtocol.java
Transmitting file data .....
Committed revision 30590.
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Assignee: David Ward
Priority: Critical
Fix For: 4.7 CP1
Attachments: soapproxy-breaker.zip, two_proxies.log.gz
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
3:17 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3021) SOAPProxies on different services shares configuration
[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3021:
-------------------------------------
The mapping in HttpClient is the default expected for each protocol, our problem is that
we were overwriting that on each invocation. More a misunderstanding in the original
implementation of the HttpClientFactory etc, than any issue with HttpClient.
The fix you have added is what we should really have been doing in the first place,
creating our own version and using that explicitly.
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL: https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Assignee: David Ward
Priority: Critical
Fix For: 4.7 CP1
Attachments: soapproxy-breaker.zip, two_proxies.log.gz
If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then
the configuration is shared between them.
Check the attached example
1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The
execution is performed correctly and target service is invoked.
2) Enable Proxy-breaker service but disable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. Although
you are invoking the first service the invocation will fail due to strict SSL setting.
3) Enable Proxy-breaker service and enable <http-client-property
name="protocol-socket-factory"... in it, deploy and do ant run test. The
execution is performed correctly and target service is invoked.
It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy
settings of Proxy service.
--
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
5448
days inactive
5511
days old
8 comments
3 participants
participants (3)
-
David Ward (JIRA) -
Jiri Pechanec (JIRA)
-
Kevin Conner (JIRA)