[JBoss JIRA] (AS7-3016) Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it
by Jiri Pechanec (Created) (JIRA)
Lazy enlistment of JMS Session does not work - UserTransaction implementation does not support it
-------------------------------------------------------------------------------------------------
Key: AS7-3016
URL: https://issues.jboss.org/browse/AS7-3016
Project: Application Server 7
Issue Type: Bug
Components: Transactions
Affects Versions: 7.1.0.Beta1b
Reporter: Jiri Pechanec
Assignee: Jonathan Halliday
Priority: Critical
This test case was identified in TCK6. There is a MDB with CMT configured - com/sun/ts/tests/jms/ee/mdb/xa
The testsuite sends a message to MDB
MDB
1) creates a QueueSession
2) Start UT
3) Send a message
4) Rollback UT
5) Start UT
6) Send a message
7) commit UT
Unfortunately the semantics is broken as QueueSession is not enlisted into transactions.
The enlistment is done when UserTransaction emits a notification org/jboss/tm/usertx/UserTransactionRegistry. The enlistment is done by JCA component which receives the notification and enlists all active XAResources.
Unfortunately the notification is emitted by org/jboss/tm/usertx/client/ServerVMClientUserTransaction. Unfortunately org/jboss/as/txn/service/ArjunaTransactionManagerService hard-codes com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple which does not have this capability.
It is necessary to support this scenario as it is tested in TCKs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (AS7-1268) Can't update subhandler on async handler
by Stan Silvert (JIRA)
Can't update subhandler on async handler
----------------------------------------
Key: AS7-1268
URL: https://issues.jboss.org/browse/AS7-1268
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.1.0.Alpha1
Reporter: Stan Silvert
Assignee: David Lloyd
David, sorry if I'm assigning to the wrong person. I guess this could be a CLI bug.
[standalone@localhost:9999 /] cd subsystem=logging/async-handler=ASYNC
[standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"level" => "INFO",
"overflow-action" => "BLOCK",
"queue-length" => 1024,
"subhandlers" => ["FILE"]
}
}
[standalone@localhost:9999 async-handler=ASYNC] :update-properties(subhandlers=["CONSOLE"])
{"outcome" => "success"}
[standalone@localhost:9999 async-handler=ASYNC] :read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"level" => "INFO",
"overflow-action" => "BLOCK",
"queue-length" => 1024,
"subhandlers" => ["FILE"]
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-4274) Remoting deadlock after deserialization exception of a large object graph returned from EJB.
by Daniel Bevenius (JIRA)
Daniel Bevenius created AS7-4274:
------------------------------------
Summary: Remoting deadlock after deserialization exception of a large object graph returned from EJB.
Key: AS7-4274
URL: https://issues.jboss.org/browse/AS7-4274
Project: Application Server 7
Issue Type: Bug
Components: EJB, Remoting
Affects Versions: 7.1.1.Final
Environment: JBoss AS 7.1.1.Final
Reporter: Daniel Bevenius
Assignee: jaikiran pai
The use case is a remote EJB client that calls an EJB which returns a large object graph. Due to a configuration error on our part a class that is part of this object graph is not available in the clients classpath. This causes a ClassNotFoundException to be thrown when deserializing, and after this exception is thrown the client "freezes" but can be interrupted by CTRL+C, but the server will deadlock and will not respond and has to be shutdown by killing the server process.
Below is part of the thread dump (the complete thread dump will be attached to this jira)
{noformat}
"Remoting "beve-7719" read-1" prio=5 tid=00000000028cc800 nid=0xb56ab000 waiting for monitor entry [00000000b56aa000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:156)
- waiting to lock <0000000005697300> (a org.xnio.streams.BufferPipeOutputStream)
at org.xnio.IoUtils.safeClose(IoUtils.java:137)
at org.jboss.remoting3.remote.OutboundMessage.closeAsync(OutboundMessage.java:158)
at org.jboss.remoting3.remote.RemoteConnectionChannel.handleAsyncClose(RemoteConnectionChannel.java:502)
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:259)
at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
Locked ownable synchronizers:
- None
"EJB default - 4" prio=5 tid=0000000002a10c00 nid=0xb3971000 in Object.wait() [00000000b3970000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <00000000056972d0> (a org.jboss.remoting3.remote.OutboundMessage)
at java.lang.Object.wait(Object.java:485)
at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:91)
- locked <00000000056972d0> (a org.jboss.remoting3.remote.OutboundMessage)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:125)
at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:113)
at org.xnio.streams.BufferPipeOutputStream.getBuffer(BufferPipeOutputStream.java:77)
at org.xnio.streams.BufferPipeOutputStream.write(BufferPipeOutputStream.java:86)
- locked <0000000005697300> (a org.xnio.streams.BufferPipeOutputStream)
at org.jboss.remoting3.remote.OutboundMessage.write(OutboundMessage.java:168)
at java.io.DataOutputStream.write(DataOutputStream.java:71)
- locked <00000000056972b8> (a java.io.DataOutputStream)
at org.jboss.as.ejb3.remote.protocol.versionone.AbstractMessageHandler$1.write(AbstractMessageHandler.java:188)
at java.io.OutputStream.write(OutputStream.java:99)
at org.jboss.marshalling.OutputStreamByteOutput.write(OutputStreamByteOutput.java:56)
at org.jboss.marshalling.SimpleDataOutput.flush(SimpleDataOutput.java:311)
at org.jboss.marshalling.SimpleDataOutput.write(SimpleDataOutput.java:82)
at org.jboss.marshalling.river.BlockMarshaller.flush(BlockMarshaller.java:306)
at org.jboss.marshalling.river.RiverMarshaller.writeEndBlock(RiverMarshaller.java:961)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1008)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:825)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.writeMethodInvocationResponse(MethodInvocationMessageHandler.java:338)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$500(MethodInvocationMessageHandler.java:64)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:226)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Locked ownable synchronizers:
- <0000000008350f48> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-3975) EJB client invocations sometimes hang indefinitely
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3975:
-----------------------------------
Summary: EJB client invocations sometimes hang indefinitely
Key: AS7-3975
URL: https://issues.jboss.org/browse/AS7-3975
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Priority: Critical
Fix For: 7.1.1.Final
When running a EJB stress test when the test is over some clients hang indefinitely.
This is a positive test, there are no failures being injected in the test.
{noformat}
"Runner - 16" daemon prio=10 tid=0x00007fb7a0025000 nid=0x4d7a in Object.wait() [0x00007fb78b3f2000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:330)
- locked <0x00000006c013ae50> (a java.lang.Object)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:140)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy0.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
at java.lang.Thread.run(Thread.java:662)
{noformat}
I originally filed a feature request to implement a timeout AS7-3811, needless to say this needs to get fixed first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBAS-8201) Patching system
by Brian Stansberry (JIRA)
Patching system
---------------
Key: JBAS-8201
URL: https://jira.jboss.org/browse/JBAS-8201
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Emanuel Muckenhuber
Fix For: 7.0.0.M2
"Server" side of the patching system. Server not in the sense of the domain model Server, but rather client-server where the client is whatever tool (JON) determines there are patches available and asks the server to apply them.
This does not need to implemented until M2 but thinking about it during the design of the InstalledImage is good.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-2411) servergroup view
by Rich Sharples (Created) (JIRA)
servergroup view
----------------
Key: AS7-2411
URL: https://issues.jboss.org/browse/AS7-2411
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Heiko Braun
Fix For: 7.1.0.Beta1
In the console when working with a large cluster or server-group it would be *really* useful to have a single view of all servers (local and remote) within the group. In thatview I'd expect to see the server name as well as the host IP / name and status. I think the natural place for this view would be unde Server Groups.
The alterative today is to go to each host and view the server-group on each - that is a real pain in a production environment with a large number of machines / servers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (AS7-887) Support legacy ServiceMBeans in SAR deployments
by Matt Drees (JIRA)
Support legacy ServiceMBeans in SAR deployments
-----------------------------------------------
Key: AS7-887
URL: https://issues.jboss.org/browse/AS7-887
Project: Application Server 7
Issue Type: Enhancement
Reporter: Matt Drees
It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore.
Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months