August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-408) Queue binds in jndi but cannot be looked up

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-408?page=all ] Ovidiu Feodorov updated JBMESSAGING-408: ---------------------------------------- Fix Version/s: 1.0.1.CR5 > Queue binds in jndi but cannot be looked up > ------------------------------------------- > > Key: JBMESSAGING-408 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-408 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Environment: Windows XP, JBoss 4.0.4GA with EJB3 > Reporter: Paul Smith > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.CR5 > > Attachments: JBoss_queue_binding_issue.zip > > > The issue is described under the following forum entry: > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=82842 > In short the queue is bound in jndi but cannot be looked up from the context. I have traced what messaging I can but can find no errors. I have also attached the relevant configuration xml and test EJB3 session bean. The connection factory can be looked up correctly but the queue cannot for some reason. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-424) Cannot access the first message when starting the JMS subscriber

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-424?page=all ] Ovidiu Feodorov updated JBMESSAGING-424: ---------------------------------------- Fix Version/s: 1.0.1.CR5 > Cannot access the first message when starting the JMS subscriber > ---------------------------------------------------------------- > > Key: JBMESSAGING-424 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-424 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Environment: JBoss jboss-4.0.4.GA & jboss-messaging-1.0.1.CR2 > Reporter: Seung Hyun > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.CR5 > > > Some messages are already published to the specific queue and the queue contains few messages. Starts the subscriber to receive the messages in the queue. It reads all the messages except the first message. Also, the first message is not accessible at all. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-410) java:/JmsXA in no-tx context does not work the same way as JBossMQ

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-410?page=all ] Ovidiu Feodorov updated JBMESSAGING-410: ---------------------------------------- Fix Version/s: 1.0.1.CR5 > java:/JmsXA in no-tx context does not work the same way as JBossMQ > ------------------------------------------------------------------ > > Key: JBMESSAGING-410 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-410 > Project: JBoss Messaging > Issue Type: Bug > Components: Configuration and Management > Affects Versions: 1.0.1.CR2 > Reporter: Elias Ross > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.CR5 > > > The same code I wrote that uses java:/JmsXA in a non-transacted environment with JBossMQ does not work with JBoss Messaging. And actually the same code does work correctly with SonicMQ as well, using the JCA adaptor with the Sonic XA connection factory. > Why allow the use java:/JmsXA without transactions? It makes sense to use a cached connection manager anyway, like you would with a database. And anyway, should be addressed for compatibility. > The following code *should* successfully send a message to a queue running without a transaction. Currently, it doesn't seem to do anything and no usage warnings are produced. > QueueConnectionFactory queueCF = (QueueConnectionFactory)new InitialContext.lookup("java:/JmsXA"); > ... > QueueConnection queueConnection = queueCF.createQueueConnection(); > QueueSession queueSession = > queueConnection.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE); > QueueSender queueSender = queueSession.createSender(queue); > ObjectMessage om = queueSession.createObjectMessage(); > queueSender.send(om); > queueSender.close(); > queueSession.close(); > queueConnection.close(); -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-429) Implement intelligent flow control

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-429?page=all ] Ovidiu Feodorov updated JBMESSAGING-429: ---------------------------------------- Fix Version/s: 1.2.1 > Implement intelligent flow control > ---------------------------------- > > Key: JBMESSAGING-429 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-429 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Fix For: 1.2.1 > > > We should implement an intelligent flow control mechanism so message sending can be automatically throttled when consumers are slow to prevent messages bulding up on queues/subscriptions. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-414) Simplify delivery hierarchy

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-414?page=all ] Ovidiu Feodorov updated JBMESSAGING-414: ---------------------------------------- Fix Version/s: 1.2.1 > Simplify delivery hierarchy > --------------------------- > > Key: JBMESSAGING-414 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-414 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > > The current delivery hierarchy seems over complex. > A delivery only ever comes from one Receiver so the all we need is a: > Delivery interface > and > SimpleDelivery implementation > Methods like acknowledge(), cancel() should be in the Delivery interface. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-425) Naming of Pipe and Distributed Pipe

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-425?page=all ] Ovidiu Feodorov updated JBMESSAGING-425: ---------------------------------------- Fix Version/s: 1.2.1 > Naming of Pipe and Distributed Pipe > ----------------------------------- > > Key: JBMESSAGING-425 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-425 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR3 > Reporter: Tim Fox > Priority: Minor > Fix For: 1.2.1 > > > The "Pipe" instance is basically a reliable channel that forwards from input to output. > However the "DistributedPipe" is not a channel at all and seems to be just an abstraction of a remote connection, so seems to have no relation whatsoever to a "Pipe". > Suggestion is to rename these classes to something that makes a bit more sense and is less confusing. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-432) One connection per unique JMS server leak

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=all ] Ovidiu Feodorov updated JBMESSAGING-432: ---------------------------------------- Fix Version/s: 1.0.1.CR5 > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 1.0.1.CR5 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-428) Stress tests fail

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-428?page=all ] Ovidiu Feodorov updated JBMESSAGING-428: ---------------------------------------- Fix Version/s: 1.0.1.CR5 (was: 1.0.1.GA) > Stress tests fail > ----------------- > > Key: JBMESSAGING-428 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-428 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.CR5 > > > [junit] main 18:46:45,187 INFO [StressTest] ####################################################### Start IN-VM test: testTopicMultipleReceivers > [junit] main 18:46:45,187 INFO [ServerManagement] IN-VM TEST > [junit] main 18:46:45,250 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:name=DefaultDS,service=DataSourceBinding' to JNDI name 'java:/DefaultDS' > [junit] main 18:46:45,281 INFO [ServiceContainer] remoting = "socket", serialization = "jboss", database = "mysql" > [junit] main 18:46:45,593 INFO [ServerPeer] JBoss Messaging 1.0.1.CR3 server [server.0] started > [junit] main 18:46:45,593 INFO [ConnectionFactory] Connector has leasing enabled, lease period 20000 milliseconds > [junit] main 18:46:45,593 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] deployed > [junit] main 18:46:45,609 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=JCAConnectionFactory,service=ConnectionFactoryBinding' to JNDI name 'java:/JCAConnectionFactory' > [junit] main 18:46:45,609 INFO [LocalTestServer] server started > [junit] main 18:46:45,609 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000 > [junit] main 18:46:45,640 INFO [Queue] Queue[/queue/Queue1] started, fullSize=3000, pageSize=1000, downCacheSize=1000 > [junit] main 18:46:45,640 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000 > [junit] main 18:46:45,671 INFO [Queue] Queue[/queue/Queue2] started, fullSize=3000, pageSize=1000, downCacheSize=1000 > [junit] main 18:46:45,671 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000 > [junit] main 18:46:45,687 INFO [Queue] Queue[/queue/Queue3] started, fullSize=3000, pageSize=1000, downCacheSize=1000 > [junit] main 18:46:45,687 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000 > [junit] main 18:46:45,703 INFO [Queue] Queue[/queue/Queue4] started, fullSize=3000, pageSize=1000, downCacheSize=1000 > [junit] main 18:46:45,703 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000 > [junit] main 18:46:45,718 INFO [Topic] Topic[/topic/Topic1] started, fullSize=3000, pageSize=1000, downCacheSize=1000 > [junit] main 18:46:45,718 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000 > [junit] main 18:46:45,734 INFO [Topic] Topic[/topic/Topic2] started, fullSize=3000, pageSize=1000, downCacheSize=1000 > [junit] main 18:46:45,734 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000 > [junit] main 18:46:45,750 INFO [Topic] Topic[/topic/Topic3] started, fullSize=3000, pageSize=1000, downCacheSize=1000 > [junit] main 18:46:45,750 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000 > [junit] main 18:46:45,765 INFO [Topic] Topic[/topic/Topic4] started, fullSize=3000, pageSize=1000, downCacheSize=1000 > [junit] Thread-90 18:49:42,609 ERROR [TransactionalReceiver] Message is null > [junit] Thread-82 18:49:47,765 ERROR [Receiver] Message is null > [junit] Thread-86 18:50:02,140 ERROR [RecoveringReceiver] Message is null > [junit] Thread-96 18:50:09,000 ERROR [Transactional2PCReceiver] Message is null > [junit] Thread-94 18:50:32,015 ERROR [Transactional2PCReceiver] Message is null (rollback) > [junit] Thread-88 18:50:33,937 ERROR [RecoveringReceiver] Message is null > [junit] Thread-92 18:50:37,828 ERROR [TransactionalReceiver] Message is null > [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue1] stopped > [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue2] stopped > [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue3] stopped > [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue4] stopped > [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic1] stopped > [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic2] stopped > [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic3] stopped > [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic4] stopped > [junit] main 18:50:37,828 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=JCAConnectionFactory,service=ConnectionFactoryBinding' from JNDI name 'java:/JCAConnectionFactory' > [junit] main 18:50:37,828 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] undeployed > [junit] main 18:50:37,843 INFO [ServerPeer] JMS ServerPeer [server.0] stopped > [junit] main 18:50:37,843 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=DefaultDS,service=DataSourceBinding' from JNDI name 'java:/DefaultDS' > [junit] main 18:50:37,843 INFO [LocalTestServer] server stopped > [junit] main 18:50:37,843 INFO [StressTest] ####################################################### Stop IN-VM test: testTopicMultipleReceivers > No exception in logs. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-196) jbpm and bpel services do not play together well

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-196?page=all ] Alejandro Guizar updated BPEL-196: ---------------------------------- Workaround Description: 1. Extract the attached patch to BPEL_HOME. - lib/jbpm/jbpm-identity-3.1.1.jar - src/bpel/org/jbpm/bpel/data/exe/varmapping.xml - src/config/jbpm.cfg.xml - src/config/hibernate.cfg.xml - build.xml 2. Rebuild the bpel library and service by calling targets build, build.service.404 in BPEL_HOME/build.xml 3. Build the jBPM web application by calling target build.webapp in JBPM_HOME/build.deploy.xml 4. Deploy BPEL_HOME/build/jbpm-bpel.sar and then JBPM_HOME/build/jbpm.war to JBoss. DO NOT deploy JBPM_HOME/build/jbpm.sar; all required files are already in jbpm-bpel.sar. If you start JBoss at this point, you will no longer see the messaging service error. You will see the web app show up but you won't be able to use it since the users table is empty. You might want to perform the steps below to load some users and the sample websale process into the HSQL database that jBPM BPEL uses by default. EITHER 5. Copy the following files from BPEL_HOME to JBPM_HOME/lib/bpel/: - build/jbpm-bpel-xxx.jar - lib/commons/commons-lang-xxx.jar - lib/wsdl4j/wsdl4j.jar 6. Copy hibernate.cfg.xml from BPEL_HOME/src/config to JBPM_HOME/src/config.files 7. Call target create.db in JBPM_HOME/build.deploy.xml 8. Rename localDB.* in JBPM_HOME/build/db to jbpmBpel.* OR 9. Just grab the attached files. 10. Copy jbpmBpel.* to JBOSS_HOME/server/xxx/data/hypersonic If you use a database other than the aforementioned, you can create the jBPM tables by calling target create-schema in BPEL_HOME/doc/examples/build.xml was: 1. Extract the attached patch to BPEL_HOME. - lib/jbpm/jbpm-identity-3.1.1.jar - src/bpel/org/jbpm/bpel/data/exe/varmapping.xml - src/config/jbpm.cfg.xml - src/config/hibernate.cfg.xml - build.xml 2. Rebuild the bpel library and service by calling targets build, build.service.404 in BPEL_HOME/build.xml 3. Build the jBPM web application by calling target build.webapp in JBPM_HOME/build.deploy.xml 4. Deploy BPEL_HOME/build/jbpm-bpel.sar and then JBPM_HOME/build/jbpm.war to JBoss If you start JBoss at this point, you will no longer see the messaging service error. You will see the web app show up but you won't be able to use it since the users table is empty. You might want to perform the steps below to load some users and the sample websale process into the HSQL database that jBPM BPEL uses by default. EITHER 5. Copy the following files from BPEL_HOME to JBPM_HOME/lib/bpel/: - build/jbpm-bpel-xxx.jar - lib/commons/commons-lang-xxx.jar - lib/wsdl4j/wsdl4j.jar 6. Copy hibernate.cfg.xml from BPEL_HOME/src/config to JBPM_HOME/src/config.files 7. Call target create.db in JBPM_HOME/build.deploy.xml 8. Rename localDB.* in JBPM_HOME/build/db to jbpmBpel.* OR 9. Just grab the attached files. 10. Copy jbpmBpel.* to JBOSS_HOME/server/xxx/data/hypersonic If you use a database other than the aforementioned, you can create the jBPM tables by calling target create-schema in BPEL_HOME/doc/examples/build.xml > jbpm and bpel services do not play together well > ------------------------------------------------ > > Key: BPEL-196 > URL: http://jira.jboss.com/jira/browse/BPEL-196 > Project: JBoss jBPM BPEL > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.1 beta 1 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Priority: Critical > Fix For: jBPM BPEL 1.1 beta 2 > > Attachments: jbpm-bpel-1.1-beta1-bpel-196.zip, jbpmBpel.properties, jbpmBpel.script > > > When deploying a jPDL process or even accessing the jbpm web application, the following exception arises: > java.lang.NullPointerException > at org.jbpm.JbpmContext.setActorId(JbpmContext.java:453) > at org.jbpm.web.JbpmContextFilter.doFilter(JbpmContextFilter.java:81) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:595) -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-177) Server-side message persistence/caching should be done by an AOP interceptor

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-177?page=all ] Ovidiu Feodorov updated JBMESSAGING-177: ---------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.7) > Server-side message persistence/caching should be done by an AOP interceptor > ---------------------------------------------------------------------------- > > Key: JBMESSAGING-177 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-177 > Project: JBoss Messaging > Issue Type: Task > Components: AOP Support > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.2.1 > > -- 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

17 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006