[JBoss JIRA] Created: (JBAS-7654) Add methods to ServerInfo to format thread dumps to be read by analysis tools
by Mike Clark (JIRA)
Add methods to ServerInfo to format thread dumps to be read by analysis tools
-----------------------------------------------------------------------------
Key: JBAS-7654
URL: https://jira.jboss.org/jira/browse/JBAS-7654
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA, JBossAS-6.0.0.GA
Reporter: Mike Clark
Assignee: Darran Lofthouse
This is a follow-up to JBAS-5163. The listThreadDump operation of org.jboss.system.server.ServerInfo outputs the thread stack in a JBoss speicifc format. It would be quite useful to be able to output the thread stack formatted so that it could be read by tools such as TDA and Samurai for analysis. This could be accomplished by adding appropriate methods to the ServerInfo/ServerInfoMBean.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-7060) Unable to set attributes for MBeans with quoted object name
by Jeff Mesnil (JIRA)
Unable to set attributes for MBeans with quoted object name
-----------------------------------------------------------
Key: JBAS-7060
URL: https://jira.jboss.org/jira/browse/JBAS-7060
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.1.0.GA
Reporter: Jeff Mesnil
Assignee: Darran Lofthouse
While integration JBoss Messaging 2.0.0.Beta3 to AS 5.1.0.GA, I found an issue when I want to update attributes for one of our MBeans which has a quoted ObjectName. The ObjectName is not properly encoded by the Servlet and an exception is thrown by the MBean registry which claims the mbean is not registered.
The ObjectName is: module=JMS,name="DLQ",type=Queue
- the *name* value is quoted
When I display this mbean in the jmx console, the corresponding form to update the attributes has a field:
<input type="hidden" name="name" value="org.jboss.messaging:module=JMS,type=Queue,name="DLQ"" />
The quotes of the ObjectNames are not properly encoded which results in a bogus object name when applying changes:
0:57:16,082 ERROR [[HtmlAdaptor]] "Servlet.service()" pour la servlet HtmlAdaptor a genere une exception
javax.management.InstanceNotFoundException: org.jboss.messaging:module=JMS,type=Queue,name= is not registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:526)
at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:675)
at org.jboss.jmx.adaptor.control.Server.setAttributes(Server.java:172)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$5.run(HtmlAdaptorServlet.java:403)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$5.run(HtmlAdaptorServlet.java:401)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.setAttributes(HtmlAdaptorServlet.java:399)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.updateAttributes(HtmlAdaptorServlet.java:259)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:102)
at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:86)
This bug prevents to update many MBeans required to managed properly JBoss Messaging when it is integrated in the AS.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-7006) Error starting JMS Destination service via AS admin console
by Howard Gao (JIRA)
Error starting JMS Destination service via AS admin console
-----------------------------------------------------------
Key: JBAS-7006
URL: https://jira.jboss.org/jira/browse/JBAS-7006
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.1.0.GA
Reporter: Howard Gao
Assignee: Darran Lofthouse
To reproduce:
1. deploy a queue service in AS_home/server/all/deploy/messaging/destinations-service.xml
2. start AS : run.sh -c all
3. log in to JBoss AS Administration Console, click 'JMS Destinations' then 'Queues'.
4. Then click the queue on the right pane. Client the 'Control' tab.
5. first click 'stop' operation, it will result in success. Then click 'start', it will fail with the following log message:
java.lang.reflect.UndeclaredThrowableException: Failed to invoke method 'start' on component 'jboss.messaging.destination:name=123456789012345,service=Queue' with parameters [].
at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:201)
at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$0.invoke(AOPProxy$0.java)
at org.jboss.profileservice.management.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:64)
at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:159)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
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:619)
Caused by: java.lang.IllegalArgumentException: No such context: jboss.messaging.destination:name=123456789012345,service=Queue
at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:51)
at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.invoke(BasicKernelBus.java:92)
at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:186)
at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aop.generatedproxies.AOPProxy$0.invoke(AOPProxy$0.java)
at org.jboss.profileservice.management.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:64)
at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:159)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482)
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:619)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
... 18 more
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-7207) JMX web console causes 500 error when MBeans throw exceptions
by Russ Hayward (JIRA)
JMX web console causes 500 error when MBeans throw exceptions
-------------------------------------------------------------
Key: JBAS-7207
URL: https://jira.jboss.org/jira/browse/JBAS-7207
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX/Web Console
Affects Versions: JBossAS-5.1.0.GA, JBossAS-5.1.0.CR1, JBossAS-5.1.0.Beta1, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA, JBossAS-5.0.0.CR2, JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.Beta3
Environment: Tested on Windows XP SP3 with all JBoss versions. Some versions tested on RedHat EL4 with same results.
Reporter: Russ Hayward
Assignee: Darran Lofthouse
When using the JMX web console an exception thrown when invoking any MBean method causes a 500 server error rather than a stack trace to be displayed. To reproduce follow these steps:
. Run JBoss with everything set to the default.
. Go to "http://localhost:8080/jmx-console/".
. Click on "jboss.ws" in the left frame.
. Choose "service=ServerConfig"
. Enter "wibble" in the "WebServicePort" field and click the Apply button.
This seems to be the same for all exceptions generated by MBeans - whether generated by operations or attributes. The correct exception and stack trace appears in the log file.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-7371) admin-console Seam initialization issues with "default" configuration
by Darryl Miles (JIRA)
admin-console Seam initialization issues with "default" configuration
---------------------------------------------------------------------
Key: JBAS-7371
URL: https://jira.jboss.org/jira/browse/JBAS-7371
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX/Web Console, Management services
Affects Versions: JBossAS-5.1.0.GA
Environment: JDK6
Reporter: Darryl Miles
Assignee: Darran Lofthouse
something is wrong with the JBoss AS 5.1.0.GA distribution, using "default" configuration, and trying to access: http://127.0.0.1:8080/admin-console/ when I have my own application EAR that uses a newer version of Seam (2.1.2).
I am using JBoss Tooling (JBIDE) to start the AS instance in debug mode on JDK6. It starts up fine enough, but the first access to the /admin-console/ yields the following stack trace. The web-app that is the admin-console seems to continue to remain deployed. So it is a lazy-Seam-initialization issue. The /admin-console/ web-app has not been modified in the distribution, but I do have an EAR project I am trying to develop which is using a different (newer) version of Seam than the one JBoss AS distributes within admin-console.war.
But all the libraries my EAR uses are contained inside my EAR so this should make no difference (FWIW I am using Seam 2.1.2 in my app). It looks like admin-console.war uses Seam 2.1.0.SP1 this is inside the admin-console.war/WEB-INF/lib so should be isolated.
If I remove my EAR from being deployed and restart the AS then /admin-console/ works.
My EAR (that appears to break on JBoss AS) is really simple:
./jboss-seam-2.1.2.jar
./lib/
./lib/commons-beanutils-1.8.0-BETA.jar
./lib/commons-collections-3.2.1.jar
./lib/commons-digester-1.8.jar
./lib/commons-logging-1.1.1.jar
./lib/drools-api-5.0.1.jar
./lib/drools-core-5.0.1.jar
./lib/jboss-el-1.0_02.CR2.jar
./lib/joda-time-1.6.jar
./lib/richfaces-api-3.3.1.GA.jar
./lib/spring-2.5.6.SEC01.jar
./lib/spring-aspects-2.5.6.SEC01.jar
./META-INF
./META-INF/MANIFEST.MF
./mvel2-2.0.10.jar
Here are the last few lines of the server startup (maybe they are of some use ?) They show the deployment of the /admin-console web-app and the lack of any exception during deployment to indicate a failure at that time.
00:21:24,600 INFO [TomcatDeployment] deploy, ctxPath=/admin-console
00:21:24,713 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'
00:21:28,397 INFO [TomcatDeployment] deploy, ctxPath=/
00:21:28,543 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
00:21:28,748 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
00:21:28,811 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
00:21:28,835 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 1m:12s:424ms
Then upon first access of the webapp the URL http://127.0.0.1:8080/admin-console/ I get:
.....START.....
java.lang.RuntimeException: error while reading /WEB-INF/components.xml
org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:221)
org.jboss.seam.init.Initialization.create(Initialization.java:124)
org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
org.jboss.on.embedded.LazyStartupListener.initialize(LazyStartupListener.java:182)
org.jboss.on.embedded.LazyStartupListener.requestInitialized(LazyStartupListener.java:240)
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:619)
root cause
java.lang.RuntimeException: Error loading element Identity with component name null and component class null
org.jboss.seam.init.Initialization.installComponentsFromXmlElements(Initialization.java:342)
org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:217)
org.jboss.seam.init.Initialization.create(Initialization.java:124)
org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
org.jboss.on.embedded.LazyStartupListener.initialize(LazyStartupListener.java:182)
org.jboss.on.embedded.LazyStartupListener.requestInitialized(LazyStartupListener.java:240)
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:619)
....END....
Then upon subsequent access of the webapp the URL http://127.0.0.1:8080/admin-console/ I get:
....START....
java.lang.NullPointerException
org.jboss.seam.servlet.SeamFilter.getSortedFilters(SeamFilter.java:112)
org.jboss.seam.servlet.SeamFilter.init(SeamFilter.java:93)
org.jboss.on.embedded.LazyStartupFilter.init(LazyStartupFilter.java:104)
org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:85)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
....END....
This problem is simply the filter assuming a something has been correctly/fully initialized when it hasn't. So this points at:
* The first exception has failed to initialize something relating to global Seam configuration, but the global initialization status was not rolled back (since the subsequent HTTP request should have resulted in a repeat of the same error) or
* The second exception should be checking for null on something that is allowed to remain unconfigured
Those matters would be for Seam team to investigate?
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-3630) JMSTransportSupport is not portable across different JMS providers.
by Darran Lofthouse (JIRA)
JMSTransportSupport is not portable across different JMS providers.
-------------------------------------------------------------------
Key: JBAS-3630
URL: http://jira.jboss.com/jira/browse/JBAS-3630
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: JBossAS-4.0.4.GA
Reporter: Darran Lofthouse
Assigned To: Thomas Diesler
Fix For: JBossAS-4.0.6.CR1
JMSTransportSupport is not portable across different JMS providers, the queue name is retrieved using the following code: -
String fromName = null;
Destination destination = message.getJMSDestination();
if (destination instanceof Queue)
fromName = "queue/" + ((Queue)destination).getQueueName();
if (destination instanceof Topic)
fromName = "topic/" + ((Topic)destination).getTopicName();
For JBossMQ this is fine and it results in a name that matches the JNDI name of the queue, for WebSphereMQ this returns the name of the queue as configured on WebSphere not the JNDI name the queue is bound to in JBoss.
The Javadoc for Queue describes the getQueueName as not being suitable for portable clients: -
http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Queue.html
A more portable solution could be to lookup a variable in the ENC that contains the name of the web service, this could either be provided by the user deploying the MDB or the web service deployer could bind a value to the ENC of the message driven bean as the web service is deployed.
--
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
15 years, 7 months
[JBoss JIRA] Resolved: (JBAS-2773) LRUEnterpriseContextCachePolicy should be updated to use org.jboss.util.TimerQueue instead of java.util.Timer
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/JBAS-2773?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse resolved JBAS-2773.
------------------------------------
Resolution: Out of Date
> LRUEnterpriseContextCachePolicy should be updated to use org.jboss.util.TimerQueue instead of java.util.Timer
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-2773
> URL: https://issues.jboss.org/browse/JBAS-2773
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-4.0.3 SP1
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
>
> LRUEnterpriseContextCachePolicy should be updated to use org.jboss.util.TimerQueue instead of java.util.Timer.
> The java.util.Timer implementation does not handle runtime exceptions thrown from the tasks, if any task throws a runtime exception when it executes the timer thread is killed and no further timers will fire.
> The classes EntitySynchronizationInterceptor, LRUEnterpriseContextCachePolicy and LRUStatefulContextCachePolicy all set tasks on the static timer referenced from LRUEnterpriseContextCachePolicy, if any one of these tasks fail all of the timers are affected.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months