July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1771) NotSerializableException is thrown from DayCounter class

by Tyronne Wickramarathne (JIRA)

NotSerializableException is thrown from DayCounter class -------------------------------------------------------- Key: JBMESSAGING-1771 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1771 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Affects Versions: 1.4.0.SP3.CP08 Environment: JBoss-SOA-4.3_CP2, JBM-1.4.0.SP3-CP08.patch01 Reporter: Tyronne Wickramarathne Even though the MessageCounter class implements Serializable interface as per JBMESSAGING-1430; the NotSerializableException is still thrown when accessing MessageCounter via JMX console. The root cause seems to be the DayCounter class. -- 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, 10 months

4
7
0 / 0

[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

14 years, 10 months

4
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1795) HTTPS transport support for JBM

by Tyronne Wickramarathne (JIRA)

HTTPS transport support for JBM ------------------------------- Key: JBMESSAGING-1795 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1795 Project: JBoss Messaging Issue Type: Task Components: JMS Remoting Affects Versions: 1.4.0.SP3.CP10 Environment: JBoss-EAP-4.3_CP7 Reporter: Tyronne Wickramarathne Priority: Minor Fix For: 1.4.0.SP3.CP11 At present HTTPS transport support isn't available by default for JBM. However, as per Remoting manual, it is possible to configure HTTPS transport for JBM -- 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, 10 months

2
4
0 / 0

[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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (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 updated AS7-1344: ------------------------------ Description: 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} was: 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} > 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 > > 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1289) Unnecessary URL reconstruction in management console

by Takayoshi Kimura (JIRA)

Unnecessary URL reconstruction in management console ----------------------------------------------------- Key: AS7-1289 URL: https://issues.jboss.org/browse/AS7-1289 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.0.0.Final Reporter: Takayoshi Kimura Assignee: Heiko Braun Priority: Minor Management console redirects "/console" to "/console/index.html"and it reconstructs URL from management interface definition. ext.example.com:9990/console -> local.example.com:9990/console/index.html This URL reconstruction is not necessary and it's better to keep current URL server/port values. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1152) Support Deployment introspection using ProtocolMetadata in the Arquillian Containers

by Aslak Knutsen (JIRA)

Support Deployment introspection using ProtocolMetadata in the Arquillian Containers ------------------------------------------------------------------------------------ Key: AS7-1152 URL: https://issues.jboss.org/browse/AS7-1152 Project: Application Server 7 Issue Type: Feature Request Components: Test Suite Affects Versions: 7.0.0.CR1 Reporter: Aslak Knutsen on deploy, the Arquillian Containers should return a ProtocolMetadata object that describes the content of the Deployment. e.g. Which HTTP contexts (ip/port) are there, which Servlets etc. This can be used for injection of URL's to the Deployed context, e.g. @ArquillianResource(MyServlet.class) URL url; The same is used by the ServletProtocol to discover the correct web context to call to invoke the test (this does not currently work at all with AS7) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Commented: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.... ] Remy Maucherat commented on JBAS-8297: -------------------------------------- Ok, assuming this works ok in AS 7, I have no intention to fix this for AS 6. > 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2253) Do not expose any AOP dependency from jboss-ejb3-cache

by Carlo de Wolf (JIRA)

Do not expose any AOP dependency from jboss-ejb3-cache ------------------------------------------------------ Key: EJBTHREE-2253 URL: https://issues.jboss.org/browse/EJBTHREE-2253 Project: EJB 3.0 Issue Type: Task Components: cache Reporter: Carlo de Wolf Priority: Critical Fix For: 2.0.0-alpha-4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2230) Create an EJB 3 implementation for AS 7

by Carlo de Wolf (JIRA)

Create an EJB 3 implementation for AS 7 --------------------------------------- Key: EJBTHREE-2230 URL: https://issues.jboss.org/browse/EJBTHREE-2230 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: 2.0.0-alpha-1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011