[JBoss JIRA] Created: (JBAS-9060) SFSB isn't disassociated from a transaction
by Carlo de Wolf (JIRA)
SFSB isn't disassociated from a transaction
-------------------------------------------
Key: JBAS-9060
URL: https://issues.jboss.org/browse/JBAS-9060
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: 7.0.0.Beta1
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: 7.0.0.Beta2
{noformat}
javax.ejb.EJBException: EJB 3.1 FR 4.6 Stateful instance Mock for StatefulSessionComponentInstance, hashCode: 1035719231 is already associated with tx TX1 (current tx TX2)
at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:60)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBAS-8781) Can't parse JSF TLD
by Stan Silvert (JIRA)
Can't parse JSF TLD
-------------------
Key: JBAS-8781
URL: https://issues.jboss.org/browse/JBAS-8781
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: 7.0.0.Alpha1
Reporter: Stan Silvert
Assignee: Remy Maucherat
WAR to reproduce is attached.
15:32:07,764 ERROR [org.jboss.as.server.deployment] (pool-3-thread-1) Caught exc
eption handling update (param is 10cd5140-b773-49da-97ab-0fb055b56141): java.lan
g.RuntimeException: Failed to process deployment chain.
at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDe
ploymentStartStopHandler.java:203)
at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDepl
oymentStartStopHandler.java:87)
at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDepl
oymentStartStopHandler.java:71)
at org.jboss.as.model.ServerDeploymentStartStopHandler.redeploy(ServerDe
ploymentStartStopHandler.java:117)
at org.jboss.as.model.ServerModelDeploymentFullReplaceUpdate.applyUpdate
(ServerModelDeploymentFullReplaceUpdate.java:68)
at org.jboss.as.server.mgmt.ServerUpdateController$ServerModelUpdateTupl
e.applyUpdate(ServerUpdateController.java:430)
at org.jboss.as.server.mgmt.ServerUpdateController$ServerModelUpdateTupl
e.access$200(ServerUpdateController.java:400)
at org.jboss.as.server.mgmt.ServerUpdateController.applyUpdates(ServerUp
dateController.java:189)
at org.jboss.as.server.mgmt.ServerUpdateController.executeUpdates(Server
UpdateController.java:142)
at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl$2.run
(ServerDeploymentManagerImpl.java:218)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886) [:1.6.0_18]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908) [:1.6.0_18]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_18]
Caused by: org.jboss.as.deployment.unit.DeploymentUnitProcessingException: Faile
d to parse "/C:/projects/as7trunk/jboss-as/build/target/jboss-7.0.0.Alpha2/bin/c
ontent/mojarra2.0-bundled.war/WEB-INF/lib/jsf-impl-2.0.3-b05.jar/META-INF/html_b
asic.tld"
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(Tl
dParsingDeploymentProcessor.java:118)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds
(TldParsingDeploymentProcessor.java:97)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processDepl
oyment(TldParsingDeploymentProcessor.java:77)
at org.jboss.as.deployment.chain.DeploymentChainImpl.processDeployment(D
eploymentChainImpl.java:50)
at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDe
ploymentStartStopHandler.java:201)
... 12 more
Caused by: java.lang.IllegalArgumentException: No enum const class org.jboss.met
adata.web.spec.BodyContentType.
JSP
at java.lang.Enum.valueOf(Enum.java:196) [:1.6.0_18]
at org.jboss.metadata.web.spec.BodyContentType.valueOf(BodyContentType.j
ava:32)
at org.jboss.as.metadata.parser.jsp.TagMetaDataParser.parse(TagMetaDataP
arser.java:111)
at org.jboss.as.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataP
arser.java:200)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(Tl
dParsingDeploymentProcessor.java:116)
... 16 more
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBMESSAGING-1456) Messages stuck in being-delivered state in cluster
by Justin Bertram (JIRA)
Messages stuck in being-delivered state in cluster
--------------------------------------------------
Key: JBMESSAGING-1456
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1456
Project: JBoss Messaging
Issue Type: Bug
Reporter: Justin Bertram
Assignee: Tim Fox
Priority: Critical
Messages become "stuck" in being-delivered state when clients use a clustered XA connection factory in a cluster of at least 2 nodes.
JBoss setup:
-2 nodes of JBoss EAP 4.3 CP02
-commented out "ClusterPullConnectionFactory" in messaging-service.xml to prevent message redistribution and eliminate the "message suckers" as the potential culprit
-MySQL backend using the default mysql-persistence-service.xml (from <JBOSS_HOME>/docs/examples/jms)
Client setup:
-both nodes have a client which is a separate process (i.e. not inside JBoss)
-clients are Spring based
-one client produces and consumes, the other client just consumes
-both clients use the ClusteredXAConnectionFactory from the default connection-factories-service.xml
-both clients publish to and consume from "queue/testDistributedQueue"
-clients are configured to send persistent messages, use AUTO_ACKNOWLEDGE, and transacted sessions
Symptoms of the issue:
-when running the clients I watch the JMX-Console for the "queue/testDistributedQueue"
-as the consumers pull messages off the queue I can see the MessageCount and DeliveringCount go to 0 every so often
-after a period of time (usually a few hours) the MessageCount and DeliveringCount never go back to 0
-I "kill" the clients and wait for the DeliveringCount to go to 0, but it never does
-after the clients are killed the ConsumerCount for the queue will drop, but never to 0 when messages are "stuck"
-a thread dump reveals at least one JBM server session that is apparently stuck (it never goes away) - ostensibly this is the consumer that is showing in the JMX-Console for "queue/testDistributedQueue"
-a "killall -3 java" doesn't produce anything from the clients so I know their dead
-nothing is in any DLQ or expiry queue
-the database contains as many rows in the JBM_MSG and JBM_MSG_REF tables as the DeliveringCount in the JMX-Console
-rebooting the node with the stuck messages frees the messages to be consumed (i.e. un-sticks them)
Other notes:
-nothing else is happening on either node but running the client and running JBoss
-this only appears to happen when a clustered connection factory is used. I tested using a normal connection factory and after 24 hours couldn't reproduce a stuck message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months