[JBoss JIRA] Updated: (AS7-1344) JGroups subsystem TimerSchedulerAdapter throws UOE when using timer-executor
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/AS7-1344?page=com.atlassian.jira.plugin.s... ]
Paul Ferraro updated AS7-1344:
------------------------------
Summary: JGroups subsystem TimerSchedulerAdapter throws UOE when using timer-executor (was: JGroups subsystem TimerScedulerAdapter throws UOE when using timer-executor)
> JGroups subsystem TimerSchedulerAdapter throws UOE when using timer-executor
> ----------------------------------------------------------------------------
>
> Key: AS7-1344
> URL: https://issues.jboss.org/browse/AS7-1344
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.0.0.Final
> Reporter: Michal Linhard
> Assignee: Trustin Lee
>
> 07:42:39,535 WARNING [org.jgroups.protocols.UDP] (DiagnosticsHandler,default,perf17-37478) Could not retrieve value of attribute (method) getNumTimerTasks: java.lang.reflect.InvocationTargetException
> [JBoss] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
> [JBoss] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
> [JBoss] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
> [JBoss] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
> [JBoss] at org.jgroups.stack.Protocol.dumpStats(Protocol.java:272) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.stack.ProtocolStack.dumpStats(ProtocolStack.java:310) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.JChannel.dumpStats(JChannel.java:687) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.JChannel$MyProbeHandler.handleProbe(JChannel.java:2099) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.protocols.TP$DiagnosticsHandler.handleDiagnosticProbe(TP.java:2165) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.protocols.TP$DiagnosticsHandler.run(TP.java:2137) [jgroups-2.12.1.Final.jar:]
> [JBoss] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
> [JBoss] Caused by: java.lang.UnsupportedOperationException
> [JBoss] at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.getExecutor(TimerSchedulerAdapter.java:168) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT]
> [JBoss] at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.size(TimerSchedulerAdapter.java:153) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT]
> [JBoss] at org.jgroups.protocols.TP.getNumTimerTasks(TP.java:714) [jgroups-2.12.1.Final.jar:]
> [JBoss] ... 11 more
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Commented: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped
by Ales Justin (JIRA)
[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ]
Ales Justin commented on JBAS-8297:
-----------------------------------
>> Ok, assuming this works ok in AS 7, I have no intention to fix this for AS 6.
If this works in AS7, wouldn't this mean we just need to bump the JBossWeb version in AS6?
(or in the worst case patch the one we have, if the new one is incompatible)
> Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped
> ------------------------------------------------------------------------------------------
>
> Key: JBAS-8297
> URL: https://issues.jboss.org/browse/JBAS-8297
> Project: Legacy JBoss Application Server 6
> Issue Type: Bug
> Components: Weld/CDI
> Environment: JBoss 6.0.0.M2, Windows XP SP3
> Reporter: Marcos Antonio
> Assignee: Remy Maucherat
> Fix For: 6.1.0
>
> Attachments: solicitacoes.zip
>
>
> 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBMESSAGING-1791) ConcurrentModificationException at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally
by Tamas Cserveny (JIRA)
ConcurrentModificationException at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally
-----------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1791
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1791
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.0.SP3
Environment: JBoss AS 4.2.3.GA Release (JBossESB 4.7)
jboss.messaging.jmsVersion=1.1
jboss.messaging.jmsMajorVersion=1
jboss.messaging.jmsMinorVersion=1
jboss.messaging.jmsProviderName=JBoss Messaging
jboss.messaging.providerVersion=1.4.0.SP3
jboss.messaging.providerMajorVersion=1
jboss.messaging.providerMinorVersion=4
jboss.messaging.providerIncrementingVersion=21
Reporter: Tamas Cserveny
Hi,
I found a CME in the JBoss-messageing.
Test scenario:
Vanilla JBossESB 4.7 with a simple flow. (file -> queue, bridge queue to another queue, queue -> file)
I kept this server running on a 2 core system with a load of 10 messages / sec. (ca 3kb messages).
I received many of these exception during the test. It caused some messages to stuck into the queue, but eventually they were redelivered. (Not after 5s, but after some other messages). They were counted in the 'DeliveringCount', and stayed like that.
Cheers,
Tamas
2010-02-26 00:00:50,083 ERROR [org.jboss.jms.client.container.ClientConsumer] Failed to deliver message
javax.jms.JMSException: There is no transaction with id LocalTx[m0r-676r546g-1-2tbmq36g-nq5p47-51zk6a]
at org.jboss.jms.tx.ResourceManager.addAck(ResourceManager.java:186)
at org.jboss.jms.client.container.SessionAspect.handlePreDeliver(SessionAspect.java:293)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect19.invoke(SessionAspect19.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate.preDeliver(ClientSessionDelegate.java)
at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:152)
at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:976)
at org.jboss.messaging.util.JBMExecutor$TCLExecutor.run(JBMExecutor.java:78)
at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
at java.lang.Thread.run(Thread.java:619)
2010-02-26 00:03:22,084 ERROR [org.jboss.messaging.util.ExceptionUtil] ConnectionEndpoint[uip-txvw446g-1-2tbmq36g-nq5p47-51zk6a] sendTransaction [f6r-ghfu546g-1-2tbmq36g-nq5p47-5
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.next(AbstractList.java:343)
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally(ServerSessionEndpoint.java:1474)
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:810)
at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:473)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101)
at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java)
at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195)
--
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
13 years, 5 months
[JBoss JIRA] Moved: (AS7-1344) JGroups subsystem TimerScedulerAdapter throws UOE when using timer-executor
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/AS7-1344?page=com.atlassian.jira.plugin.s... ]
Paul Ferraro moved JBPAPP-6863 to AS7-1344:
-------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-1344 (was: JBPAPP-6863)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.0.0.Final
(was: EDG 6.0.0 ALPHA)
Component/s: Clustering
(was: Enterprise Data Grid)
Security: (was: Public)
Docs QE Status: (was: NEW)
> JGroups subsystem TimerScedulerAdapter throws UOE when using timer-executor
> ---------------------------------------------------------------------------
>
> Key: AS7-1344
> URL: https://issues.jboss.org/browse/AS7-1344
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.0.0.Final
> Reporter: Michal Linhard
> Assignee: Trustin Lee
>
> http://hudson.qa.jboss.com/hudson/view/EDG6/job/edg-60-stress-client-hotr...
> {code}
> 07:42:39,535 WARNING [org.jgroups.protocols.UDP] (DiagnosticsHandler,default,perf17-37478) Could not retrieve value of attribute (method) getNumTimerTasks: java.lang.reflect.InvocationTargetException
> [JBoss] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24]
> [JBoss] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24]
> [JBoss] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24]
> [JBoss] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24]
> [JBoss] at org.jgroups.stack.Protocol.dumpStats(Protocol.java:272) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.stack.ProtocolStack.dumpStats(ProtocolStack.java:310) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.JChannel.dumpStats(JChannel.java:687) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.JChannel$MyProbeHandler.handleProbe(JChannel.java:2099) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.protocols.TP$DiagnosticsHandler.handleDiagnosticProbe(TP.java:2165) [jgroups-2.12.1.Final.jar:]
> [JBoss] at org.jgroups.protocols.TP$DiagnosticsHandler.run(TP.java:2137) [jgroups-2.12.1.Final.jar:]
> [JBoss] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
> [JBoss] Caused by: java.lang.UnsupportedOperationException
> [JBoss] at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.getExecutor(TimerSchedulerAdapter.java:168) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT]
> [JBoss] at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.size(TimerSchedulerAdapter.java:153) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT]
> [JBoss] at org.jgroups.protocols.TP.getNumTimerTasks(TP.java:714) [jgroups-2.12.1.Final.jar:]
> [JBoss] ... 11 more
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months