December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1099) Potential deadlock in shutting down server

by Tim Fox (JIRA)

Potential deadlock in shutting down server ------------------------------------------ Key: JBMESSAGING-1099 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.GA Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.SP1 Need to investigate -- 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

18 years, 5 months

3
22
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1095) ServerPeer won't survive a stop/start of the service

by Clebert Suconic (JIRA)

ServerPeer won't survive a stop/start of the service ---------------------------------------------------- Key: JBMESSAGING-1095 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095 Project: JBoss Messaging Issue Type: Bug Reporter: Clebert Suconic Assigned To: Clebert Suconic Few NullPointerExceptions would happen.. This won't affect any production system... It would affect the JBossAS testsuite only... so this is not a critical production bug. -- 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

18 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1147) NullPointerException in ServerConsumerEndpoint.localClose

by Carlo de Wolf (JIRA)

NullPointerException in ServerConsumerEndpoint.localClose --------------------------------------------------------- Key: JBMESSAGING-1147 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1147 Project: JBoss Messaging Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Tim Fox Something I snatched from the console. Can't reproduce it. 12:22:30,426 ERROR [ExceptionUtil] SessionEndpoint[861-adw6ls8f-1-65ltks8f-axkhkk-110j3] close [a81-uvedms8f-1-65ltks8f-axkhkk-110j3] java.lang.NullPointerException at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:526) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:1166) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.close(ServerSessionEndpoint.java:329) at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$close$aop(SessionAdvised.java:72) at org.jboss.jms.server.endpoint.advised.SessionAdvised$close_N4742752445160157748.invokeNext(SessionAdvised$close_N4742752445160157748.java) at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) at org.jboss.jms.server.endpoint.advised.SessionAdvised$close_N4742752445160157748.invokeNext(SessionAdvised$close_N4742752445160157748.java) at org.jboss.jms.server.endpoint.advised.SessionAdvised.close(SessionAdvised.java) at org.jboss.jms.wireformat.CloseRequest.serverInvoke(CloseRequest.java:66) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101) at org.jboss.remoting.Client.invoke(Client.java:1634) at org.jboss.remoting.Client.invoke(Client.java:548) at org.jboss.remoting.Client.invoke(Client.java:536) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:187) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:158) at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$close$aop(ClientSessionDelegate.java:152) at org.jboss.jms.client.delegate.ClientSessionDelegate$close_N4742752445160157748.invokeNext(ClientSessionDelegate$close_N4742752445160157748.java) at org.jboss.jms.client.container.SessionAspect.handleClose(SessionAspect.java:204) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect25.invoke(SessionAspect25.java) at org.jboss.jms.client.delegate.ClientSessionDelegate$close_N4742752445160157748.invokeNext(ClientSessionDelegate$close_N4742752445160157748.java) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$close_N4742752445160157748.invokeNext(ClientSessionDelegate$close_N4742752445160157748.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$close_N4742752445160157748.invokeNext(ClientSessionDelegate$close_N4742752445160157748.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.close(ClientSessionDelegate.java) at org.jboss.jms.client.JBossConnectionConsumer.doClose(JBossConnectionConsumer.java:338) at org.jboss.jms.client.JBossConnectionConsumer.close(JBossConnectionConsumer.java:163) at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.teardownConsumer(JmsServerSessionPool.java:277) at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.stop(JmsServerSessionPool.java:99) at org.jboss.resource.adapter.jms.inflow.JmsActivation.teardownSessionPool(JmsActivation.java:567) at org.jboss.resource.adapter.jms.inflow.JmsActivation.teardown(JmsActivation.java:321) at org.jboss.resource.adapter.jms.inflow.JmsActivation.stop(JmsActivation.java:223) at org.jboss.resource.adapter.jms.JmsResourceAdapter.endpointDeactivation(JmsResourceAdapter.java:80) at org.jboss.resource.deployment.RARDeployment.endpointDeactivation(RARDeployment.java:287) at org.jboss.resource.deployment.RARDeployment.internalInvoke(RARDeployment.java:235) at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.deactivate(JBossMessageEndpointFactory.java:323) at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.stop(JBossMessageEndpointFactory.java:200) at org.jboss.ejb3.mdb.MessagingContainer.stopProxies(MessagingContainer.java:297) at org.jboss.ejb3.mdb.MessagingContainer.stop(MessagingContainer.java:290) 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:585) at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119) at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.stop(Unknown Source) at org.jboss.system.ServiceController.stop(ServiceController.java:508) at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy119.stop(Unknown Source) at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175) at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202) at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:661) at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107) at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.stop(Unknown Source) at org.jboss.system.ServiceController.stop(ServiceController.java:508) at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy33.stop(Unknown Source) at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:538) 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:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy34.stop(Unknown Source) at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638) at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:516) 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:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:1058) at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:1033) at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:996) -- 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

18 years, 5 months

3
14
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-979) Servlet transport for JBoss Messaging

by Daniel Weeks (JIRA)

Servlet transport for JBoss Messaging ------------------------------------- Key: JBMESSAGING-979 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-979 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Remoting Affects Versions: 1.2.0.SP1 Environment: Windows 2003 with IIS as front-end web server. Reporter: Daniel Weeks Assigned To: Tim Fox Although there is an https transport for JBoss Messaging, it does not support going over the same port that Tomcat is using like the JBoss MQ jbossmq-httpil.sar does. This capability is required for environments in which port 443 is the only port that is open for communication. Although url proxying/forwarding could be used under Apache to work around this issue, there is not a good solution for doing this with IIS (or for applications that don't use a front-end web server and are limited to port 443). Many enterprise PKI solutions (such as DoD) favor the use of IIS over Apache due to cost of COTS products, so this is a show stopper for JBoss Messaging in those environments. This issue is preventing us from migrating an enterprise application that runs in the DoD environment to to JBoss Messaging. The application makes heavy use of JMS and would benefit greatly from the improved performance that JBoss Messaging provides. This feature request is originating from a JBoss Customer Support Portal case at the following URL: https://network.jboss.com/jbossnetwork/restricted/caseDetail.html?caseId=... -- 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

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1185) Add a configuration option to turn off any JMS Spec compliance checks when dealing with message from foreign providers

by Aaron Walker (JIRA)

Add a configuration option to turn off any JMS Spec compliance checks when dealing with message from foreign providers ---------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1185 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1185 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Facade, Messaging Core Affects Versions: 1.4.0.SP2 Reporter: Aaron Walker Assigned To: Aaron Walker Certain message providers, which will remain nameless are not JMS complaint by default. They add JMSX properties in the message header that are not part of the JMS Spec. If often not possible to able to control whats been put in the headers and in order to support foreign messages in JBM a JMS complaince a flag needs to be added to allow this type of checking to be relaxed -- 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

18 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1107) Less noisy client-side failover

by Ovidiu Feodorov (JIRA)

Less noisy client-side failover ------------------------------- Key: JBMESSAGING-1107 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Clustering Affects Versions: 1.4.0.GA Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear. If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails. Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked. The logging information should be naturally still available, but at DEBUG level. -- 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

18 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1144) Routing problem on Browsing when using mixed deliveries..

by Clebert Suconic (JIRA)

Routing problem on Browsing when using mixed deliveries.. --------------------------------------------------------- Key: JBMESSAGING-1144 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1144 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP1 Reporter: Clebert Suconic Assigned To: Tim Fox Fix For: Stable branch I believe the error is due to mixed delivery modes... but that's just a guess as I didn't have time to look at logs. I'm committing a testcase on BrowserTest for this. This testcase was reported by Carlo.. I just converted this testcase from his original test on EJB3. -- 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

18 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1189) JBossMessaging_1_4_0_SP1 patch for JBossAS5

by Scott M Stark (JIRA)

JBossMessaging_1_4_0_SP1 patch for JBossAS5 ------------------------------------------- Key: JBMESSAGING-1189 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1189 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.SP1 Reporter: Scott M Stark Assigned To: Tim Fox We need a patch to JBossMessaging_1_4_0_SP1 to better integrate into the jbossas5 beta3 server. This patch addresses the issues raised in the forum: - externalize the name of the aop-messaging-server.xml so these aspects can be overriden in the server integration project. - externalize the SecurityStore implementation so this can be overriden by the server integration project. The messaging-service.xml is the corresponding update to the messaging integration version. -- 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

18 years, 5 months

3
15
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1215) Closing connection does not delete associated TemporaryQueues

by Mike Clark (JIRA)

Closing connection does not delete associated TemporaryQueues ------------------------------------------------------------- Key: JBMESSAGING-1215 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1215 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Environment: N/A Reporter: Mike Clark Assigned To: Tim Fox When a temporary queue is created, it is not deleted on Connection.close(). This leaves the queue on the system, but unusable since only consumers that are created from the same Connection are allowed to consume from a TemporaryQueue (i.e., it is a resource leak). To reproduce, simply create a Connection, Session, and TemporaryQueue. Close the Connection and examine the Destinations attribute of the jboss.messaging:service=ServerPeer MBean. See attached code. -- 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

18 years, 5 months

3
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1205) Add SecurityBlocks on JBMExecutor

by Clebert Suconic (JIRA)

Add SecurityBlocks on JBMExecutor --------------------------------- Key: JBMESSAGING-1205 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1205 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: Stable branch JBMExecutor is doing set/get ClassLoaderOperations without a SecurityPriviledgeBlock. We should add that to avoid problems under a SecurityManager. -- 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

18 years, 5 months

2
7
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 December 2007