[JBoss JIRA] Created: (JBAS-4017) failing org.jboss.test.jca.test.XAExceptionUnitTestCase
by Dimitris Andreadis (JIRA)
failing org.jboss.test.jca.test.XAExceptionUnitTestCase
-------------------------------------------------------
Key: JBAS-4017
URL: http://jira.jboss.com/jira/browse/JBAS-4017
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Environment: Java Version 1.5.0_10
Java Vendor Sun Microsystems Inc.
Java VM Name Java HotSpot(TM) Server VM
Java VM Version 1.5.0_10-b03
Java VM Info mixed mode
OS Name Linux
OS Version 2.6.9-42.0.2.ELsmp
OS Arch i386
Reporter: Dimitris Andreadis
Assigned To: Weston Price
Weston can you please qualify is this is a JCA or JBossTS issue?
testMatchManagedConnectionResourceError Error RuntimeException; nested exception is: java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] Ending suspended RMs failed when rolling back the transaction, but transaction rolled back.
java.rmi.ServerException: RuntimeException; nested exception is:
java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] Ending suspended RMs failed when rolling back the transaction, but transaction rolled back.
at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:421)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:954)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:231)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
at $Proxy15.invoke(Unknown Source)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:541)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261)
Caused by: java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] Ending suspended RMs failed when rolling back the transaction, but transaction rolled back.
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:307)
at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:493)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:361)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:954)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:231)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
at $Proxy15.invoke(Unknown Source)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:541)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:612)
at org.jboss.remoting.Client.invoke(Client.java:604)
at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:175)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:112)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy2.simulateFactoryError(Unknown Source)
at org.jboss.test.jca.test.XAExceptionUnitTestCase.testMatchManagedConnectionResourceError(XAExceptionUnitTestCase.java:193)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
0.095
testMatchManagedConnectionRuntimeError Error RuntimeException; nested exception is: java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] Ending suspended RMs failed when rolling back the transaction, but transaction rolled back.
java.rmi.ServerException: RuntimeException; nested exception is:
java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] Ending suspended RMs failed when rolling back the transaction, but transaction rolled back.
at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:421)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:954)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:231)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
at $Proxy15.invoke(Unknown Source)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:541)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261)
Caused by: java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] [com.arjuna.ats.internal.jta.transaction.arjunacore.endsuspendfailed2] Ending suspended RMs failed when rolling back the transaction, but transaction rolled back.
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:307)
at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:493)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:361)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:954)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:231)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
at $Proxy15.invoke(Unknown Source)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:541)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:612)
at org.jboss.remoting.Client.invoke(Client.java:604)
at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:175)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:112)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy2.simulateFactoryError(Unknown Source)
at org.jboss.test.jca.test.XAExceptionUnitTestCase.testMatchManagedConnectionRuntimeError(XAExceptionUnitTestCase.java:207)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Resolved: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs
by Weston Price (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3321?page=all ]
Weston Price resolved JBAS-3321.
--------------------------------
Fix Version/s: JBossAS-4.2.0.CR1
Resolution: Done
Added transaction timeout to org.jboss.resource.adapter.jms.inflow.JmsActivationSpec and associated code to set the transaction timeout in XATransactionDemarcationStrategy on the TM prior to XAResource being enlisted in the global transaction.
> Support for "method-attributes" including "transaction-timeout" for MDBs
> ------------------------------------------------------------------------
>
> Key: JBAS-3321
> URL: http://jira.jboss.com/jira/browse/JBAS-3321
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-4.0.4.GA
> Reporter: Galder Zamarreno
> Assigned To: Weston Price
> Fix For: JBossAS-4.2.0.CR1
>
>
> Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes",
> particularly "transaction-timeout", why is this?
> I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact
> Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss?
> I guess it is either an error or a deliberate design decision not to support it, if it's the latter I
> would be interested to hear what the rational is?
> Adrian Brock wrote:
> Because the MDB transaction is not started by the EJB container
> like the other EJB types.
> Raise a feature request. There is no reason why the ServerSessionPool
> cannot ask the EJB container for this information.
> _________________
> Adrian Brock
> Chief Scientist
> JBoss, Inc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBCACHE-970) With JGroups 2.2.7.1, callRemoteMethodsViaReflection fails
by Brian Stansberry (JIRA)
With JGroups 2.2.7.1, callRemoteMethodsViaReflection fails
----------------------------------------------------------
Key: JBCACHE-970
URL: http://jira.jboss.com/jira/browse/JBCACHE-970
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Replication
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 1.4.1.SP1
TreeCache.callRemoteMethodsViaReflection uses the JGroups version short to decide whether to call the 2.4.1 method that supports anycast. This fails with JG 2.2.7.1 since the non-canonical JGroups version short 2271 is greater than 241.
Solution is to one time only try to resolve and store a ref to the new anycast method, ignoring any exception. Then callRemoteMethodsViaReflection can use a null check of the ref to the method to decide whether to use anycast.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Commented: (JBADMCON-135) MBean attribute type java.util.Properties improperly handled when applying changes on page JMX MBean View
by Geert Pante (JIRA)
[ http://jira.jboss.com/jira/browse/JBADMCON-135?page=comments#action_12352554 ]
Geert Pante commented on JBADMCON-135:
--------------------------------------
org.jboss.util.propertyeditor.PropertiesEditor does override the getValue to parse the input properties file format using java.util.Properties.load(InputStream is). It inherits setAsText(String text) from TextPropertyEditorSupport.
In the end, the default java.util.Properties.toString() method will be used in the getAsText() method, which results in "{name1=value1,name2=value2}".
It should use java.util.Properties.store(OutputStream os).
> MBean attribute type java.util.Properties improperly handled when applying changes on page JMX MBean View
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBADMCON-135
> URL: http://jira.jboss.com/jira/browse/JBADMCON-135
> Project: JBoss Admin Console
> Issue Type: Bug
> Environment: JBoss 4.0.3, Windows XP Browser IE 6 and Firefox 1.5
> Reporter: Ben Hurwitz
>
> If you have an MBean attribute whose type is java.util.Properties (there is a built-in property editor for setting these in jboss-service.xml), applying changes to any attribute of that MBean is perilous. Its value is shown on the JMX MBean View form as {name1=value1, name2=value2, name3=value3} in an input field. That's not a bug for viewing the values, but the bug is that the style used for rendering values cannot be submitted to retain the attribute's value. If you don't change the Properties but simply click the "Apply Changes" button, the property values are now shown as {{name1=value1, name2=value2, name3=value3}}, and in fact what happened is that now there is a single property named "{name1" whose value is "value1, name2=value2, name3=value3}". Similarly, it is difficult to actively edit the field to obtain the property list you want.
> Workaround: It is possible to create the desired properly list by submitting the form twice: First set the property value to include "\r\n" and click "Apply Changes". This produces a new form showing an incorrect value for the properties, but with a multi-line text field for the Properties value. Now the correct properties values can be entered, one per line, like this:
> name1=value1
> name2=value2
> name3=value3
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months