[JBoss JIRA] (JBESB-3932) JmsConnectionPool reverts to non-xa when transaction has expired
by Kevin Conner (JIRA)
[ https://issues.jboss.org/browse/JBESB-3932?page=com.atlassian.jira.plugin... ]
Kevin Conner reassigned JBESB-3932:
-----------------------------------
Assignee: Tom Cunningham
> JmsConnectionPool reverts to non-xa when transaction has expired
> ----------------------------------------------------------------
>
> Key: JBESB-3932
> URL: https://issues.jboss.org/browse/JBESB-3932
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.10 CP1
> Reporter: Kevin Conner
> Assignee: Tom Cunningham
> Attachments: JBESB-3932.diff
>
>
> The JmsConnectionPool test for whether to create a non-XA session or XA session does not take into account an expired transaction. The test checks for active transactions and, it not found, falls back to the non-XA API.
> The test should only check for an existing transaction, whether active or not, and allow the TransactionManager to fail when invoked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBESB-3932) JmsConnectionPool reverts to non-xa when transaction has expired
by Kevin Conner (JIRA)
[ https://issues.jboss.org/browse/JBESB-3932?page=com.atlassian.jira.plugin... ]
Kevin Conner updated JBESB-3932:
--------------------------------
Attachment: JBESB-3932.diff
Fix based on 4_10_CP codebase
> JmsConnectionPool reverts to non-xa when transaction has expired
> ----------------------------------------------------------------
>
> Key: JBESB-3932
> URL: https://issues.jboss.org/browse/JBESB-3932
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.10 CP1
> Reporter: Kevin Conner
> Attachments: JBESB-3932.diff
>
>
> The JmsConnectionPool test for whether to create a non-XA session or XA session does not take into account an expired transaction. The test checks for active transactions and, it not found, falls back to the non-XA API.
> The test should only check for an existing transaction, whether active or not, and allow the TransactionManager to fail when invoked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBESB-3932) JmsConnectionPool reverts to non-xa when transaction has expired
by Kevin Conner (JIRA)
Kevin Conner created JBESB-3932:
-----------------------------------
Summary: JmsConnectionPool reverts to non-xa when transaction has expired
Key: JBESB-3932
URL: https://issues.jboss.org/browse/JBESB-3932
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.10 CP1
Reporter: Kevin Conner
The JmsConnectionPool test for whether to create a non-XA session or XA session does not take into account an expired transaction. The test checks for active transactions and, it not found, falls back to the non-XA API.
The test should only check for an existing transaction, whether active or not, and allow the TransactionManager to fail when invoked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBESB-3931) java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions when running webservice_consumer_wise QS
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-3931?page=com.atlassian.jira.plugin... ]
Tom Cunningham updated JBESB-3931:
----------------------------------
Fix Version/s: 4.13
> java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions when running webservice_consumer_wise QS
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBESB-3931
> URL: https://issues.jboss.org/browse/JBESB-3931
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server
> Affects Versions: 4.12
> Reporter: Tom Cunningham
> Fix For: 4.13
>
>
> When running the webservice_consumer_wise QS, seeing the following on the ESB server (AS 4.2.3.GA). Looks like AOP JAR mismatch/missing JARs
> java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions
> at it.javalinux.wise.core.client.WSDynamicClient$WSDynamicClientAdvisor.
> <init>(WSDynamicClient$WSDynamicClientAdvisor.java)
> at it.javalinux.wise.core.client.WSDynamicClient.<clinit>(WSDynamicClien
> t.java)
> at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.create(WSD
> ynamicClientFactory.java:74)
> at org.jboss.soa.esb.actions.soap.wise.SOAPClient.createClient(SOAPClien
> t.java:330)
> at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.jav
> a:263)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
> ipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
> ipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(
> ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$Transactiona
> lRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jbos
> s.aop.advice.SecurityActions
> at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
> at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryCl
> assLoader.java:521)
> at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassL
> oader.java:415)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 12 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBESB-3931) java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions when running webservice_consumer_wise QS
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-3931?page=com.atlassian.jira.plugin... ]
Tom Cunningham updated JBESB-3931:
----------------------------------
Component/s: Application Server
> java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions when running webservice_consumer_wise QS
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBESB-3931
> URL: https://issues.jboss.org/browse/JBESB-3931
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server
> Affects Versions: 4.12
> Reporter: Tom Cunningham
>
> When running the webservice_consumer_wise QS, seeing the following on the ESB server (AS 4.2.3.GA). Looks like AOP JAR mismatch/missing JARs
> java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions
> at it.javalinux.wise.core.client.WSDynamicClient$WSDynamicClientAdvisor.
> <init>(WSDynamicClient$WSDynamicClientAdvisor.java)
> at it.javalinux.wise.core.client.WSDynamicClient.<clinit>(WSDynamicClien
> t.java)
> at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.create(WSD
> ynamicClientFactory.java:74)
> at org.jboss.soa.esb.actions.soap.wise.SOAPClient.createClient(SOAPClien
> t.java:330)
> at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.jav
> a:263)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
> ipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
> ipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(
> ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$Transactiona
> lRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jbos
> s.aop.advice.SecurityActions
> at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
> at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryCl
> assLoader.java:521)
> at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassL
> oader.java:415)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 12 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBESB-3931) java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions when running webservice_consumer_wise QS
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-3931?page=com.atlassian.jira.plugin... ]
Tom Cunningham updated JBESB-3931:
----------------------------------
Affects Version/s: 4.12
> java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions when running webservice_consumer_wise QS
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBESB-3931
> URL: https://issues.jboss.org/browse/JBESB-3931
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.12
> Reporter: Tom Cunningham
>
> When running the webservice_consumer_wise QS, seeing the following on the ESB server (AS 4.2.3.GA). Looks like AOP JAR mismatch/missing JARs
> java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions
> at it.javalinux.wise.core.client.WSDynamicClient$WSDynamicClientAdvisor.
> <init>(WSDynamicClient$WSDynamicClientAdvisor.java)
> at it.javalinux.wise.core.client.WSDynamicClient.<clinit>(WSDynamicClien
> t.java)
> at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.create(WSD
> ynamicClientFactory.java:74)
> at org.jboss.soa.esb.actions.soap.wise.SOAPClient.createClient(SOAPClien
> t.java:330)
> at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.jav
> a:263)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
> ipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
> ipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(
> ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$Transactiona
> lRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jbos
> s.aop.advice.SecurityActions
> at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
> at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryCl
> assLoader.java:521)
> at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassL
> oader.java:415)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 12 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBESB-3931) java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions when running webservice_consumer_wise QS
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-3931?page=com.atlassian.jira.plugin... ]
Tom Cunningham updated JBESB-3931:
----------------------------------
Description:
When running the webservice_consumer_wise QS, seeing the following on the ESB server (AS 4.2.3.GA). Looks like AOP JAR mismatch/missing JARs
java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions
at it.javalinux.wise.core.client.WSDynamicClient$WSDynamicClientAdvisor.
<init>(WSDynamicClient$WSDynamicClientAdvisor.java)
at it.javalinux.wise.core.client.WSDynamicClient.<clinit>(WSDynamicClien
t.java)
at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.create(WSD
ynamicClientFactory.java:74)
at org.jboss.soa.esb.actions.soap.wise.SOAPClient.createClient(SOAPClien
t.java:330)
at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.jav
a:263)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
ipeline(ActionProcessingPipeline.java:667)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
ipeline(ActionProcessingPipeline.java:614)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(
ActionProcessingPipeline.java:442)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$Transactiona
lRunner.run(MessageAwareListener.java:587)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jbos
s.aop.advice.SecurityActions
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryCl
assLoader.java:521)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassL
oader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 12 more
> java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions when running webservice_consumer_wise QS
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBESB-3931
> URL: https://issues.jboss.org/browse/JBESB-3931
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Tom Cunningham
>
> When running the webservice_consumer_wise QS, seeing the following on the ESB server (AS 4.2.3.GA). Looks like AOP JAR mismatch/missing JARs
> java.lang.NoClassDefFoundError: org/jboss/aop/advice/SecurityActions
> at it.javalinux.wise.core.client.WSDynamicClient$WSDynamicClientAdvisor.
> <init>(WSDynamicClient$WSDynamicClientAdvisor.java)
> at it.javalinux.wise.core.client.WSDynamicClient.<clinit>(WSDynamicClien
> t.java)
> at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.create(WSD
> ynamicClientFactory.java:74)
> at org.jboss.soa.esb.actions.soap.wise.SOAPClient.createClient(SOAPClien
> t.java:330)
> at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.jav
> a:263)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
> ipeline(ActionProcessingPipeline.java:667)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processP
> ipeline(ActionProcessingPipeline.java:614)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(
> ActionProcessingPipeline.java:442)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$Transactiona
> lRunner.run(MessageAwareListener.java:587)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jbos
> s.aop.advice.SecurityActions
> at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
> at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryCl
> assLoader.java:521)
> at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassL
> oader.java:415)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 12 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBESB-3930) NPE during deployment when Action in xsd is missing leading slash and validate option is true
by Richard Vachula (JIRA)
Richard Vachula created JBESB-3930:
--------------------------------------
Summary: NPE during deployment when Action in xsd is missing leading slash and validate option is true
Key: JBESB-3930
URL: https://issues.jboss.org/browse/JBESB-3930
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.12
Environment: jboss-5.1.0.GA, jbossesb 4.12
Reporter: Richard Vachula
<actions inXsd="schemas/getUserInfo_in.xsd" mep="RequestResponse"
outXsd="schemas/getUserInfo_out.xsd" validate="true" webservice="true">
When inXsd or outXsd is missing leading slash / ("schemas/getUserInfo_in.xsd" instead of "/schemas/getUserInfo_in.xsd" deploy will result in NPE:
Caused by: java.lang.NullPointerException
at org.jboss.internal.soa.esb.util.XMLHelper.getSchema(XMLHelper.java:465)
at org.jboss.internal.soa.esb.util.XMLHelper.getSchema(XMLHelper.java:418)
at org.jboss.internal.soa.esb.util.XMLHelper.getSchema(XMLHelper.java:381)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.<init>(ActionProcessingPipeline.java:197)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:199)
at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBESB-3929) Wise SOAPClient throws String index out of range when wrong wsdl in configuration
by Richard Vachula (JIRA)
Richard Vachula created JBESB-3929:
--------------------------------------
Summary: Wise SOAPClient throws String index out of range when wrong wsdl in configuration
Key: JBESB-3929
URL: https://issues.jboss.org/browse/JBESB-3929
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.12
Environment: jboss-5.1.0.GA, jbossesb 4.12
Reporter: Richard Vachula
When wise SOAPClient action contains invalid wsdl like http://some/service.wsdl instead of http://some/service?wsdl (missing ? character), deployment will raise following exception:
Caused by: org.jboss.soa.esb.ConfigurationException: Unexpected exception while instantiating action instance
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:359)
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:340)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.<init>(ActionProcessingPipeline.java:279)
at org.jboss.soa.esb.listeners.message.MessageAwareListener.doInitialise(MessageAwareListener.java:199)
... 61 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:355)
... 64 more
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -67
at java.lang.String.substring(String.java:1937)
at org.jboss.soa.esb.actions.soap.wise.SOAPClient.<init>(SOAPClient.java:214)
... 69 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months