[jira] Updated: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client
[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated CXF-2760: - Fix Version/s: 2.1.10 2.2.8 (was: 2.3) Affects Version/s: 2.2.7 2.1.9 I have looked into the current releases. The issue went into 2.2.8 and 2.1.10. So I updated the Fix Versions. @Willem: is there some work open for this issue or can we close it? > implement useMessageIDAsCorrelationID for JMS Client > > > Key: CXF-2760 > URL: https://issues.apache.org/jira/browse/CXF-2760 > Project: CXF > Issue Type: New Feature > Components: Transports >Affects Versions: 2.1.4, 2.1.9, 2.2.7 >Reporter: Seumas Soltysik >Assignee: Willem Jiang > Fix For: 2.2.8, 2.1.10 > > Attachments: cxf-2760.patch > > > MQSeries servers often use the message ID of and incoming message as the > correlation ID for an outgoing message. In order for a CXF client to > communicate with an MQSeries server it needs to correlate the outgoing > message with the incoming message using the message ID of the sent message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2760) implement useMessageIDAsCorrelationID for JMS Client
[ https://issues.apache.org/jira/browse/CXF-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-2760. --- Resolution: Fixed It's should be closed, as we have some different implementation in CXF 2.3.0. > implement useMessageIDAsCorrelationID for JMS Client > > > Key: CXF-2760 > URL: https://issues.apache.org/jira/browse/CXF-2760 > Project: CXF > Issue Type: New Feature > Components: Transports >Affects Versions: 2.1.4, 2.1.9, 2.2.7 >Reporter: Seumas Soltysik >Assignee: Willem Jiang > Fix For: 2.1.10, 2.2.8 > > Attachments: cxf-2760.patch > > > MQSeries servers often use the message ID of and incoming message as the > correlation ID for an outgoing message. In order for a CXF client to > communicate with an MQSeries server it needs to correlate the outgoing > message with the incoming message using the message ID of the sent message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2936) NullPointerException in ServerImpl combining JAX-RS and Simple Frontend
[
https://issues.apache.org/jira/browse/CXF-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901363#action_12901363
]
Dennis Kieselhorst commented on CXF-2936:
-
Thanks!
> NullPointerException in ServerImpl combining JAX-RS and Simple Frontend
> ---
>
> Key: CXF-2936
> URL: https://issues.apache.org/jira/browse/CXF-2936
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.2.9
> Environment: Windows 7 64-Bit, Java 1.6.0_17, Jetty 7.0.0.pre5
>Reporter: Dennis Kieselhorst
>Assignee: Daniel Kulp
>Priority: Critical
> Fix For: 2.2.10
>
> Attachments: cxf-testserver.zip
>
>
> After adding JAXRS to an existing CXF webservice application (using simple
> frontend) the startup fails with a NPE in ServerImpl:
> {noformat}
> 2010-08-11 10:07:26.980::WARN: Failed startup of context
> org.mortbay.jetty.plugin.jetty6pluginwebappcont...@608925b0
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name
> 'org.apache.cxf.jaxrs.spring.JAXRSServerFactoryBeanDefinitionParser$SpringJAXRSServerFactoryBean---47367291':
> Invocation of init method failed;
> nested exception is
> org.apache.cxf.service.factory.ServiceConstructionException
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1412)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:574)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
> at
> org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
> at
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
> at
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:579)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:156)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1215)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:548)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:348)
> at
> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:107)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:151)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:222)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132)
> at
> org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:384)
> at
> org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:320)
> at
> org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:205)
> at
> org.mortbay.jetty.plugin.Je
[jira] Resolved: (CXF-2953) CXF-2915 causes regression against Interopfest WS-Trust 1.0 scenarios 9 & 10
[ https://issues.apache.org/jira/browse/CXF-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Valeri resolved CXF-2953. --- Resolution: Fixed > CXF-2915 causes regression against Interopfest WS-Trust 1.0 scenarios 9 & 10 > > > Key: CXF-2953 > URL: https://issues.apache.org/jira/browse/CXF-2953 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 2.2.10 >Reporter: David Valeri >Assignee: David Valeri > Fix For: 2.3, 2.2.11 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-2954) Occur ConcurrentModificationException when creating mutiple WebService client in mutiple thread
[
https://issues.apache.org/jira/browse/CXF-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp reassigned CXF-2954:
Assignee: Daniel Kulp
> Occur ConcurrentModificationException when creating mutiple WebService client
> in mutiple thread
> ---
>
> Key: CXF-2954
> URL: https://issues.apache.org/jira/browse/CXF-2954
> Project: CXF
> Issue Type: Bug
> Components: Bus
>Affects Versions: 2.2.10
> Environment: CXF2.2.10, JDK1.5, Tomcat 5.5
>Reporter: Jammy chen
>Assignee: Daniel Kulp
>
> The cxf application will throw ConcurrentModificationException when creating
> mutiple WebService client in mutiple thread in the same time.
> Here is to create WebService client source code:
>JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
> factory.setServiceClass(SystemPortType.class);
> factory.setAddress(wsdlPort);
> SystemPortType isspt = (SystemPortType) factory.create();
> ((BindingProvider)
> isspt).getRequestContext().put(BindingProvider.SESSION_MAINTAIN_PROPERTY,
> true);
> Here is the ConcurrentModificationException stack track, notice only to
> create mutiple WebService client in the same time will throw this exception:
> Caused by: java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
> at java.util.AbstractList$Itr.remove(Unknown Source)
> at
> org.apache.cxf.bus.extension.ExtensionManagerImpl.activateAllByType(ExtensionManagerImpl.java:115)
> at org.apache.cxf.bus.extension.DeferredMap.undefer(DeferredMap.java:36)
> at
> org.apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFactoryForUri(DestinationFactoryManagerImpl.java:140)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:239)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:145)
> at
> org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:51)
> at
> org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactoryBean.java:102)
> at
> org.apache.cxf.jaxws.JaxWsProxyFactoryBean.create(JaxWsProxyFactoryBean.java:121)
> I did some research and found this couses that different thread try to
> operate the map in class ExtensionManagerImpl, the map was defined
> by ConcurrentHashMap> deferred, although
> ConcurrentHashMap is Multithread-Safe but ArrayList is not, Here is a piece
> of cxf code will trigger the exception,
> public void activateAllByType(Class type) {
> for (Map.Entry> e :
> deferred.entrySet()) {
> Iterator it = e.getValue().iterator();
> while (it.hasNext()) {
> Extension ex = it.next();
> if (type.isAssignableFrom(ex.getClassObject(loader))) {
> loadAndRegister(ex);
> it.remove();
> }
> }
> }
> }
> why you didn't declare this method as synchronized? I found some else methods
> both declare as synchronized such as activateAll(), activateViaNS(). so I
> tried to did some changes which declare activateAllByType() as synchronized
> everything work fine.
> This maybe your bug I hope you fix it asap, This is very important for our
> current project. really thank you
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2954) Occur ConcurrentModificationException when creating mutiple WebService client in mutiple thread
[
https://issues.apache.org/jira/browse/CXF-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-2954.
--
Fix Version/s: 2.2.11
Resolution: Fixed
> Occur ConcurrentModificationException when creating mutiple WebService client
> in mutiple thread
> ---
>
> Key: CXF-2954
> URL: https://issues.apache.org/jira/browse/CXF-2954
> Project: CXF
> Issue Type: Bug
> Components: Bus
>Affects Versions: 2.2.10
> Environment: CXF2.2.10, JDK1.5, Tomcat 5.5
>Reporter: Jammy chen
>Assignee: Daniel Kulp
> Fix For: 2.2.11
>
>
> The cxf application will throw ConcurrentModificationException when creating
> mutiple WebService client in mutiple thread in the same time.
> Here is to create WebService client source code:
>JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
> factory.setServiceClass(SystemPortType.class);
> factory.setAddress(wsdlPort);
> SystemPortType isspt = (SystemPortType) factory.create();
> ((BindingProvider)
> isspt).getRequestContext().put(BindingProvider.SESSION_MAINTAIN_PROPERTY,
> true);
> Here is the ConcurrentModificationException stack track, notice only to
> create mutiple WebService client in the same time will throw this exception:
> Caused by: java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
> at java.util.AbstractList$Itr.remove(Unknown Source)
> at
> org.apache.cxf.bus.extension.ExtensionManagerImpl.activateAllByType(ExtensionManagerImpl.java:115)
> at org.apache.cxf.bus.extension.DeferredMap.undefer(DeferredMap.java:36)
> at
> org.apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFactoryForUri(DestinationFactoryManagerImpl.java:140)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:239)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:145)
> at
> org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:51)
> at
> org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactoryBean.java:102)
> at
> org.apache.cxf.jaxws.JaxWsProxyFactoryBean.create(JaxWsProxyFactoryBean.java:121)
> I did some research and found this couses that different thread try to
> operate the map in class ExtensionManagerImpl, the map was defined
> by ConcurrentHashMap> deferred, although
> ConcurrentHashMap is Multithread-Safe but ArrayList is not, Here is a piece
> of cxf code will trigger the exception,
> public void activateAllByType(Class type) {
> for (Map.Entry> e :
> deferred.entrySet()) {
> Iterator it = e.getValue().iterator();
> while (it.hasNext()) {
> Extension ex = it.next();
> if (type.isAssignableFrom(ex.getClassObject(loader))) {
> loadAndRegister(ex);
> it.remove();
> }
> }
> }
> }
> why you didn't declare this method as synchronized? I found some else methods
> both declare as synchronized such as activateAll(), activateViaNS(). so I
> tried to did some changes which declare activateAllByType() as synchronized
> everything work fine.
> This maybe your bug I hope you fix it asap, This is very important for our
> current project. really thank you
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-2922) JAX-RS runtime configuration (Spring) warns with Spring 3.0.3
[
https://issues.apache.org/jira/browse/CXF-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp reassigned CXF-2922:
Assignee: Daniel Kulp
> JAX-RS runtime configuration (Spring) warns with Spring 3.0.3
> -
>
> Key: CXF-2922
> URL: https://issues.apache.org/jira/browse/CXF-2922
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
>Affects Versions: 2.2.9
>Reporter: Benson Margulies
>Assignee: Daniel Kulp
>
> The error is:
> {noformat}
> org.apache.cxf.endpoint.ServerImpl - Setting the server's publish address to
> be /Extraction
> Jul 31, 2010 7:54:31 AM
> org.springframework.beans.GenericTypeAwarePropertyDescriptor
> getWriteMethodForActualAccess
> WARNING: Invalid JavaBean property 'serviceBeans' being accessed! Ambiguous
> write methods found next to actually used [public void
> org.apache.cxf.jaxrs.JAXRSServerFactoryBean.setServiceBeans(java.lang.Object[])]:
> [public void
> org.apache.cxf.jaxrs.JAXRSServerFactoryBean.setServiceBeans(java.util.List)]
> {noformat}
> For:
> {code}
>
>
>
>
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
