You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Vladimir Romaniuk (Created) (JIRA)" <ji...@apache.org> on 2012/03/21 08:33:39 UTC
[jira] [Created] (CXF-4187) New conduit implementation issues
New conduit implementation issues
---------------------------------
Key: CXF-4187
URL: https://issues.apache.org/jira/browse/CXF-4187
Project: CXF
Issue Type: Bug
Environment: 2 Talend ESB containers:
1st Service Locator and 2 deployed dataservices
2nd 2 Corresponded consumers
Reporter: Vladimir Romaniuk
Attachments: DoubleIt-0.1_TIMEOUT.kar, DoubleIt_SL_ON_SSL.kar, consumer2_SL.jar, consumer2_Timeout.jar, org.apache.cxf.http.conduits-common.cfg, org.apache.cxf.http.conduits-timeout.cfg
Hello,
I found a couple of issues in new conduit configuration.
I prepare two dataservices and corresponding consumers with different endpoints. All uses Service Locator functionality. I also prepaired two conduit configs and place it to etc directory.
Issue 1. When I deploying second the consumer after first consumer it not using the corresponding conduit configuration but using latest from previous request.
Issue 2. Sometimes when I redeploying consumer it throwing the exception:
Exception in component tESBConsumer_1
java.lang.RuntimeException: java.security.UnrecoverableKeyException: Password must not be null
at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.applyTlsClientParameters(HTTPTransportActivator.java:368)
at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.apply(HTTPTransportActivator.java:255)
at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.configure(HTTPTransportActivator.java:237)
but sometimes not and works normally.
Regards,
Vladimir
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4187) New conduit implementation issues
Posted by "Vladimir Romaniuk (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Romaniuk updated CXF-4187:
-----------------------------------
Description:
Hello,
I found a couple of issues in new conduit configuration.
I prepare two dataservices and corresponding consumers with different endpoints(in attachment). All uses Service Locator functionality. I also prepaired two conduit configs(in attachment) and place it to etc directory.
Issue 1. When I deploying the timeout consumer (endpoint https://localhost:9001/TimeoutDemoService) after DoubleIt consumer (endpoint https://localhost:9001/DoubleItDemoService) it not using the corresponding conduit configuration but using latest from previous request.
Issue 2. Sometimes when I redeploying consumer it throwing the exception (screen_1) but sometimes not and works normally.
Regards,
Vladimir
was:
Hello,
I found a couple of issues in new conduit configuration.
I prepare two dataservices and corresponding consumers with different endpoints. All uses Service Locator functionality. I also prepaired two conduit configs and place it to etc directory.
Issue 1. When I deploying second the consumer after first consumer it not using the corresponding conduit configuration but using latest from previous request.
Issue 2. Sometimes when I redeploying consumer it throwing the exception:
Exception in component tESBConsumer_1
java.lang.RuntimeException: java.security.UnrecoverableKeyException: Password must not be null
at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.applyTlsClientParameters(HTTPTransportActivator.java:368)
at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.apply(HTTPTransportActivator.java:255)
at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.configure(HTTPTransportActivator.java:237)
but sometimes not and works normally.
Regards,
Vladimir
> New conduit implementation issues
> ---------------------------------
>
> Key: CXF-4187
> URL: https://issues.apache.org/jira/browse/CXF-4187
> Project: CXF
> Issue Type: Bug
> Environment: 2 Talend ESB containers:
> 1st Service Locator and 2 deployed dataservices
> 2nd 2 Corresponded consumers
> Reporter: Vladimir Romaniuk
> Attachments: DoubleIt-0.1_TIMEOUT.kar, DoubleIt_SL_ON_SSL.kar, consumer2_SL.jar, consumer2_Timeout.jar, org.apache.cxf.http.conduits-common.cfg, org.apache.cxf.http.conduits-timeout.cfg, screenshot-1.jpg
>
>
> Hello,
> I found a couple of issues in new conduit configuration.
> I prepare two dataservices and corresponding consumers with different endpoints(in attachment). All uses Service Locator functionality. I also prepaired two conduit configs(in attachment) and place it to etc directory.
> Issue 1. When I deploying the timeout consumer (endpoint https://localhost:9001/TimeoutDemoService) after DoubleIt consumer (endpoint https://localhost:9001/DoubleItDemoService) it not using the corresponding conduit configuration but using latest from previous request.
> Issue 2. Sometimes when I redeploying consumer it throwing the exception (screen_1) but sometimes not and works normally.
> Regards,
> Vladimir
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4187) New conduit implementation issues
Posted by "Vladimir Romaniuk (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Romaniuk updated CXF-4187:
-----------------------------------
Attachment: org.apache.cxf.http.conduits-common.cfg
DoubleIt_SL_ON_SSL.kar
DoubleIt-0.1_TIMEOUT.kar
consumer2_Timeout.jar
consumer2_SL.jar
org.apache.cxf.http.conduits-timeout.cfg
> New conduit implementation issues
> ---------------------------------
>
> Key: CXF-4187
> URL: https://issues.apache.org/jira/browse/CXF-4187
> Project: CXF
> Issue Type: Bug
> Environment: 2 Talend ESB containers:
> 1st Service Locator and 2 deployed dataservices
> 2nd 2 Corresponded consumers
> Reporter: Vladimir Romaniuk
> Attachments: DoubleIt-0.1_TIMEOUT.kar, DoubleIt_SL_ON_SSL.kar, consumer2_SL.jar, consumer2_Timeout.jar, org.apache.cxf.http.conduits-common.cfg, org.apache.cxf.http.conduits-timeout.cfg
>
>
> Hello,
> I found a couple of issues in new conduit configuration.
> I prepare two dataservices and corresponding consumers with different endpoints. All uses Service Locator functionality. I also prepaired two conduit configs and place it to etc directory.
> Issue 1. When I deploying second the consumer after first consumer it not using the corresponding conduit configuration but using latest from previous request.
> Issue 2. Sometimes when I redeploying consumer it throwing the exception:
> Exception in component tESBConsumer_1
> java.lang.RuntimeException: java.security.UnrecoverableKeyException: Password must not be null
> at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.applyTlsClientParameters(HTTPTransportActivator.java:368)
> at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.apply(HTTPTransportActivator.java:255)
> at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.configure(HTTPTransportActivator.java:237)
> but sometimes not and works normally.
> Regards,
> Vladimir
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4187) New conduit implementation issues
Posted by "Daniel Kulp (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-4187.
------------------------------
Resolution: Invalid
Fix Version/s: Invalid
Assignee: Daniel Kulp
This scenario involves a lot more moving parts than just CXF. It would need to be stripped down quite a bit to even determine if it is a CXF issue.
That said, my "gut feeling" is this is working as designed. The conduit configuration is applied when the conduit is first created, not per request, for performance reasons. Thus, changing URL's or similar that would not cause a conduit recreation would not change the settings. You COULD install a custom ConduitSelector into the client proxy that would handle that if really needed.
> New conduit implementation issues
> ---------------------------------
>
> Key: CXF-4187
> URL: https://issues.apache.org/jira/browse/CXF-4187
> Project: CXF
> Issue Type: Bug
> Environment: 2 Talend ESB containers:
> 1st Service Locator and 2 deployed dataservices
> 2nd 2 Corresponded consumers
> Reporter: Vladimir Romaniuk
> Assignee: Daniel Kulp
> Fix For: Invalid
>
> Attachments: DoubleIt-0.1_TIMEOUT.kar, DoubleIt_SL_ON_SSL.kar, consumer2_SL.jar, consumer2_Timeout.jar, org.apache.cxf.http.conduits-common.cfg, org.apache.cxf.http.conduits-timeout.cfg, screenshot-1.jpg
>
>
> Hello,
> I found a couple of issues in new conduit configuration.
> I prepare two dataservices and corresponding consumers with different endpoints(in attachment). All uses Service Locator functionality. I also prepaired two conduit configs(in attachment) and place it to etc directory.
> Issue 1. When I deploying the timeout consumer (endpoint https://localhost:9001/TimeoutDemoService) after DoubleIt consumer (endpoint https://localhost:9001/DoubleItDemoService) it not using the corresponding conduit configuration but using latest from previous request.
> Issue 2. Sometimes when I redeploying consumer it throwing the exception (screen_1) but sometimes not and works normally.
> Regards,
> Vladimir
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4187) New conduit implementation issues
Posted by "Vladimir Romaniuk (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Romaniuk updated CXF-4187:
-----------------------------------
Attachment: screenshot-1.jpg
Talend ESB log screen
> New conduit implementation issues
> ---------------------------------
>
> Key: CXF-4187
> URL: https://issues.apache.org/jira/browse/CXF-4187
> Project: CXF
> Issue Type: Bug
> Environment: 2 Talend ESB containers:
> 1st Service Locator and 2 deployed dataservices
> 2nd 2 Corresponded consumers
> Reporter: Vladimir Romaniuk
> Attachments: DoubleIt-0.1_TIMEOUT.kar, DoubleIt_SL_ON_SSL.kar, consumer2_SL.jar, consumer2_Timeout.jar, org.apache.cxf.http.conduits-common.cfg, org.apache.cxf.http.conduits-timeout.cfg, screenshot-1.jpg
>
>
> Hello,
> I found a couple of issues in new conduit configuration.
> I prepare two dataservices and corresponding consumers with different endpoints. All uses Service Locator functionality. I also prepaired two conduit configs and place it to etc directory.
> Issue 1. When I deploying second the consumer after first consumer it not using the corresponding conduit configuration but using latest from previous request.
> Issue 2. Sometimes when I redeploying consumer it throwing the exception:
> Exception in component tESBConsumer_1
> java.lang.RuntimeException: java.security.UnrecoverableKeyException: Password must not be null
> at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.applyTlsClientParameters(HTTPTransportActivator.java:368)
> at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.apply(HTTPTransportActivator.java:255)
> at org.apache.cxf.transport.http.osgi.HTTPTransportActivator.configure(HTTPTransportActivator.java:237)
> but sometimes not and works normally.
> Regards,
> Vladimir
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira