Bug 780756 (SOA-3210)
Summary: | Conflicting Spring jars in the server | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Pechanec <jpechane> |
Component: | JBossESB | Assignee: | Martin Vecera <mvecera> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 5.2.0 ER1 | CC: | dpalmer, jpechane, kevin.conner |
Target Milestone: | --- | ||
Target Release: | 5.2.0 GA, 5.2.0.ER3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/SOA-3210 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-10-07 07:16:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jiri Pechanec
2011-07-26 06:30:40 UTC
It seems that Camel gateway is also affected Affects Testing: Added: [Blocks Testing] Blocked Tests: Added: Blocks WS tests Affects Testing: Removed: [Blocks Testing] Blocked Tests: Removed: Blocks WS tests Link: Added: This issue relates to SOA-2743 Link: Removed: This issue relates to SOA-2743 I updated the cxf-2.2.12-patch-01 tag to use 3.0.3.RELEASE and ran through the CXF testsuite, no issues were discovered. I tried to run the 'testsuite' in the jbossws-cxf project but this does not appear to work, even before updating spring. I updated the spring jars, in the CXF installer, to 3.0.3.RELEASE and brought up SOA 5.2 without issues, the spring_jpetstore works as expected. I also did a bytecode comparison of the CXF jars, compiled against each spring release, and found no differences other than some classes associated with xmlbeans had the order of their methods changed. One option would be to update the spring jars within CXF; whether this is acceptable really needs input from QE. I have tried replacing the spring jars in ER2 (in both client and jbossws.deployer) but I get exceptions when I run the spring_jpetstore quickstart. -- Posted from Bugbox for iPhone If you are seeing exceptions, assuming that they are the same as before, then you are likely to be still using the old version of the spring jars. Please double check which spring jars are included in the server, I'll chase up in the morning. The exceptions are different with the new spring jars. Here is the relevant log section: 09:23:17,488 INFO [QueueService] Queue[/queue/quickstart_spring_jpetstore_Request] started, fullSize=200000, pageSize=2000, downCacheSize=2000 09:23:17,502 INFO [QueueService] Queue[/queue/quickstart_spring_jpetstore_Response] started, fullSize=200000, pageSize=2000, downCacheSize=2000 09:23:17,531 INFO [QueueService] Queue[/queue/quickstart_spring_jpetstore_esb] started, fullSize=200000, pageSize=2000, downCacheSize=2000 09:23:17,607 INFO [EsbDeployment] Starting ESB Deployment 'spring_jpetstore.esb' 09:23:17,657 INFO [ClassPathXmlApplicationContext] Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@3fec95d7: startup date [Thu Aug 18 09:23:17 BST 2011]; root of context hierarchy 09:23:17,657 INFO [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [applicationContext.xml] 09:23:17,918 INFO [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [dataAccessContext-local.xml] 09:23:18,028 INFO [PropertyPlaceholderConfigurer] Loading properties file from class path resource [jdbc.properties] 09:23:18,062 INFO [DefaultListableBeanFactory] Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@5e1c3a97: defining beans [propertyConfigurer,accountValidator,orderValidator,petStore,org.springframework.aop.config.internalAutoProxyCreator,org.springframework.aop.support.DefaultBeanFactoryPointcutAdvisor#0,txAdvice,dataSource,transactionManager,sqlMapClient,accountDao,categoryDao,productDao,itemDao,orderDao,sequenceDao]; root of factory hierarchy 09:23:19,140 INFO [InquiryHelper] uddi:juddi.apache.org:a1d73b22-8310-4a86-95e8-02787aaeaf54 is modified Wed Aug 17 23:11:16 BST 2011 1313619076462 09:23:19,169 INFO [InquiryHelper] uddi:juddi.apache.org:a1d73b22-8310-4a86-95e8-02787aaeaf54 is modified Thu Aug 18 09:23:19 BST 2011 1313655799154 09:23:40,126 ERROR [AbstractSpringAction] Exception Root Cause is: Cannot create PoolableConnectionFactory (socket creation error) Full Stack Trace is: org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225) org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) org.springframework.jdbc.datasource.DataSourceTransactionManager.doBegin(DataSourceTransactionManager.java:202) org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371) org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:316) org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:105) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) $Proxy519.insertOrder(Unknown Source) org.jboss.soa.esb.samples.quickstart.spring_jpetstore.InsertOrderAction.insertOrder(InsertOrderAction.java:61) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649) org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603) org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433) org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:550) java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) java.lang.Thread.run(Thread.java:680) 09:23:40,136 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms:127.0.0.1:1099#queue/quickstart_spring_jpetstore_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_spring_jpetstore_esb/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: da8d2e95-da2d-482e-824a-29d33a094c9e RelatesTo: jms:correlationID#da8d2e95-da2d-482e-824a-29d33a094c9e 09:23:40,142 INFO [InquiryHelper] uddi:juddi.apache.org:86134d82-c91f-438e-9e9d-61d3c6b7b4b3 is modified Thu Aug 18 09:19:20 BST 2011 1313655560349 Looks like you have not run up the database. Replaced cxf spring jars with version 3.0.3.RELEASE. Assigned to QE to verify the fix and close the JIRA Release Notes Docs Status: Added: Not Required Writer: Added: dlesage Verified in ER4 |