January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8739) org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase ---------------------------------------------------------- Key: JBAS-8739 URL: https://issues.jboss.org/browse/JBAS-8739 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Andrew Rubinger Fix For: 6.0.0.Final All tests failing: testEarManagedComponentNames testMdb testSfsb testSlsb testSlsbLocal with: Component not found; no managed object with name "testEjb3xMetrics.jar/BEAN" in: [] Stacktrace junit.framework.AssertionFailedError: Component not found; no managed object with name "testEjb3xMetrics.jar/SLSB" in: [] at org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase.getAndTestManagedComponent(Ejb3MetricsUnitTestCase.java:453) at org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase.testSlsb(Ejb3MetricsUnitTestCase.java:255) These tests were passing with EJB 3 depchain 1.0.0-alpha-32 and failing with 1.0.0-alpha-34 (do not have results of these tests with 1.0.0-alpha-33) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8245) Fix org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase

by Brian Stansberry (JIRA)

Fix org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase -------------------------------------------------------------- Key: JBAS-8245 URL: https://jira.jboss.org/browse/JBAS-8245 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3, Test Suite Reporter: Brian Stansberry Fix For: 6.0.0.Final http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-8834) org.jboss.test.web.test.Enc*UnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.web.test.Enc*UnitTestCase ---------------------------------------- Key: JBAS-8834 URL: https://issues.jboss.org/browse/JBAS-8834 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Shelly McGowan org.jboss.test.web.test.EncXmlUnitTestCase.testAltRequestInfoServlet org.jboss.test.web.test.EncAnnotationsUnitTestCase.testAltRequestInfoServlet java.io.IOException: Expected reply code:200, actual=500 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8835) org.jboss.test.web.test.NamingServletUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.web.test.NamingServletUnitTestCase ------------------------------------------------- Key: JBAS-8835 URL: https://issues.jboss.org/browse/JBAS-8835 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.1 org.jboss.test.web.test.NamingServletUnitTestCase.testAppContextRoot org.jboss.test.web.test.NamingServletUnitTestCase.testGlobalContextRoot junit.framework.AssertionFailedError: FIXME: don't know what to expect naming!ROOT not bound -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8821) org.jboss.test.ejb3.async.test.AsyncSessionBeanUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.ejb3.async.test.AsyncSessionBeanUnitTestCase ----------------------------------------------------------- Key: JBAS-8821 URL: https://issues.jboss.org/browse/JBAS-8821 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3 Reporter: Shelly McGowan Assignee: Andrew Rubinger Fix For: TBD-6.x testLocalRemote: junit.framework.AssertionFailedError: Remote async call should be able to be cancelled testLocalCancel: junit.framework.AssertionFailedError: Local async call should be able to be cancelled -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8268) Should we add a relax flag for people using out of order content inside elements of their XML files

by Emmanuel Bernard (JIRA)

Should we add a relax flag for people using out of order content inside elements of their XML files --------------------------------------------------------------------------------------------------- Key: JBAS-8268 URL: https://jira.jboss.org/browse/JBAS-8268 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.M4 Reporter: Emmanuel Bernard Assignee: Ales Justin Fix For: 6.0.0.Final It seems that JBoss AS 6 and JBoss XB are stricter than they used to wrt the order of the content in elements https://jira.jboss.org/browse/JBAS-8265?focusedCommentId=12542087#action_... Would it make sense to have a flag to relax this rule? I am thinking of people with existing applications trying to deploy into AS 6 from 5 and seeing such errors (ease of use and less pain in support down the road). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
15
0 / 0

[JBoss JIRA] Created: (JBAS-8623) Update JBoss Threads to resolve unneeded CPU consumption

by Rico Neubauer (JIRA)

Update JBoss Threads to resolve unneeded CPU consumption -------------------------------------------------------- Key: JBAS-8623 URL: https://jira.jboss.org/browse/JBAS-8623 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Affects Versions: 6.0.0.M5 Reporter: Rico Neubauer JBTHR-17 fixes a major issue regarding CPU-usage. JBoss6 should update jboss-threads.jar to include that fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7218) ENC EM injection erroneously happens only once for web modules

by henk de boer (JIRA)

ENC EM injection erroneously happens only once for web modules -------------------------------------------------------------- Key: JBAS-7218 URL: https://jira.jboss.org/jira/browse/JBAS-7218 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: Observed problem on Mac OS X 10.5.7 and Debian Lenny 64 bits using JDK 6 Reporter: henk de boer Using a persistence-context-ref element in the web.xml of a web module, it appears that this causes an EntityManager instance to be injected only once into the ENC of this component. However, the EJB 3.0 spec states in section 16.2.1: "In general, lookups of objects in the JNDI java: namespace are required to return a new instance of the requested object every time." So the observed behavior seems to violate the spec. In addition, this is particularly troublesome since an EntityManager is explicitly not thread-safe. Using the same EM instance for simultaneous requests therefor doesn't work. Of course there are several other methods to obtain an EM reference, for instance binding an EM factory directly to JNDI and using that to obtain the reference. -- 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

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-8800) Can't parse TLD for Trinidad demo application

by Stan Silvert (JIRA)

Can't parse TLD for Trinidad demo application --------------------------------------------- Key: JBAS-8800 URL: https://issues.jboss.org/browse/JBAS-8800 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 6.0.0.Final Reporter: Stan Silvert Assignee: Remy Maucherat You can get the demo app here: https://repository.apache.org/content/repositories/orgapachemyfaces-013/o... You will see the error below on AS6 Final. This works on AS5.1 and it reportedly also works on Tomcat 7. There is a similar issue here: https://issues.apache.org/jira/browse/TOMAHAWK-1560. I assume that one can be worked around by setting in war-deployers-jboss-beans.xml: <bean name="TldParsingDeployer" class="org.jboss.deployment.TldParsingDeployer"> <property name="relativeOrder">2002</property> <property name="useSchemaValidation">false</property> <property name="useValidation">false</property> </bean> But even with no validation, you still get this error for the trinidad demo: 10:27:01,762 WARN [JBossEntityResolver] Trying to resolve systemId as a non-fil e URL: http://java.sun.com/xml/ns/javaee 10:28:02,379 ERROR [AbstractKernelController] Error installing to Parse: name=vf s:///C:/jboss-6.0.0.Final/server/default/deploy/trinidad-demo-1.2.14.war state=P reParse mode=Manual requiredState=Parse: org.jboss.deployers.spi.DeploymentExcep tion: Error creating managed object for vfs:///C:/jboss-6.0.0.Final/server/defau lt/deploy/trinidad-demo-1.2.14.war at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentExcept ion(DeploymentException.java:49) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithO utput.createMetaData(AbstractParsingDeployerWithOutput.java:383) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithO utput.createMetaData(AbstractParsingDeployerWithOutput.java:343) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithO utput.createMetaData(AbstractParsingDeployerWithOutput.java:315) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithO utput.deploy(AbstractParsingDeployerWithOutput.java:255) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(Deployer Wrapper.java:179) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(Deployer sImpl.java:1832) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFi rst(DeployersImpl.java:1550) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(Deployers Impl.java:1491) [:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra ctControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractContr oller.java:2044) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra ctController.java:1083) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementSta teDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr actController.java:1246) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr actController.java:1139) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractContro ller.java:939) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractContro ller.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersI mpl.java:1983) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(Deployers Impl.java:1076) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeploye rImpl.java:679) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.p rocess(MainDeployerPlugin.java:106) [:6.0.0.Final] at org.jboss.profileservice.dependency.ProfileControllerContext$Delegate Deployer.process(ProfileControllerContext.java:143) [:0.2.2] at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(Profil eDeployAction.java:151) [:0.2.2] at org.jboss.profileservice.dependency.ProfileDeployAction.installAction Internal(ProfileDeployAction.java:94) [:0.2.2] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction (InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction (InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.sim pleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2. 2.0.GA] at org.jboss.dependency.plugins.action.AccessControllerContextAction.ins tall(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContextActions.install (AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra ctControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractContr oller.java:2044) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra ctController.java:1083) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementSta teDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr actController.java:1246) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr actController.java:1139) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractContro ller.java:939) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractContro ller.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicPro fileActivation.start(ProfileActivationWrapper.java:190) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(Pr ofileActivationWrapper.java:87) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationService.activate Profile(ProfileActivationService.java:215) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationService.activate (ProfileActivationService.java:159) [:0.2.2] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.ac tivate(AbstractProfileServiceBootstrap.java:112) [:0.2.2] at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolve rFacade.deploy(BasicResolverFactory.java:87) [:0.2.2] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.st art(AbstractProfileServiceBootstrap.java:91) [:0.2.2] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceB ootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.0.0.Final] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceB ootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(A bstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.r un(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at java.lang.Thread.run(Thread.java:619) [:1.6.0_18] Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: vfs:// /C:/jboss-6.0.0.Final/server/default/deploy/trinidad-demo-1.2.14.war/WEB-INF/lib /trinidad-impl-1.2.14.jar/META-INF/tr.tld@1,238 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars er.java:224) [jbossxb.jar:2.0.3.GA] at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java :178) [jbossxb.jar:2.0.3.GA] at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:257) [jbossx b.jar:2.0.3.GA] at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:231) [jbossx b.jar:2.0.3.GA] at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(Sch emaResolverDeployer.java:137) [:2.2.0.GA] at org.jboss.deployment.TldParsingDeployer.parse(TldParsingDeployer.java :64) [:6.0.0.Final] at org.jboss.deployment.TldParsingDeployer.parse(TldParsingDeployer.java :38) [:6.0.0.Final] at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(Sch emaResolverDeployer.java:121) [:2.2.0.GA] at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.handl eMultipleFiles(AbstractVFSParsingDeployer.java:446) [:2.2.0.GA] at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse (AbstractVFSParsingDeployer.java:319) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithO utput.createMetaData(AbstractParsingDeployerWithOutput.java:376) [:2.2.0.GA] ... 47 more Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to parse schema for nsURI=http://java.sun.com/xml/ns/javaee, localName=taglib, schemaLocation=nu ll at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(A bstractMutableSchemaResolver.java:350) [jbossxb.jar:2.0.3.GA] at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startE lement(SundayContentHandler.java:176) [jbossxb.jar:2.0.3.GA] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.startElement(SaxJBos sXBParser.java:401) [jbossxb.jar:2.0.3.GA] at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour ce) [xercesImpl.jar:6.0.0.Final] at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Sou rce) [xercesImpl.jar:6.0.0.Final] at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Sourc e) [xercesImpl.jar:6.0.0.Final] at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unkn own Source) [xercesImpl.jar:6.0.0.Final] at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.s canRootElementHook(Unknown Source) [xercesImpl.jar:6.0.0.Final] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent Dispatcher.dispatch(Unknown Source) [xercesImpl.jar:6.0.0.Final] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un known Source) [xercesImpl.jar:6.0.0.Final] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [x ercesImpl.jar:6.0.0.Final] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [x ercesImpl.jar:6.0.0.Final] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) [xercesImpl .jar:6.0.0.Final] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) [xe rcesImpl.jar:6.0.0.Final] at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Sour ce) [xercesImpl.jar:6.0.0.Final] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars er.java:209) [jbossxb.jar:2.0.3.GA] ... 57 more Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 -1:-1 schema_refe rence.4: Failed to read schema document 'null', because 1) could not find the do cument; 2) the document could not be read; 3) the root element of the document i s not <xsd:schema>. at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHa ndler.handleError(XsdBinderTerminatingErrorHandler.java:40) [jbossxb.jar:2.0.3.G A] at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source) [xercesImpl.jar:6.0.0.Final] at org.apache.xerces.impl.xs.XSLoaderImpl.load(Unknown Source) [xercesIm pl.jar:6.0.0.Final] at org.jboss.xb.binding.Util.loadSchema(Util.java:394) [jbossxb.jar:2.0. 3.GA] at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.ja va:178) [jbossxb.jar:2.0.3.GA] at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.ja va:149) [jbossxb.jar:2.0.3.GA] at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(A bstractMutableSchemaResolver.java:342) [jbossxb.jar:2.0.3.GA] ... 72 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

8
15
0 / 0

[JBoss JIRA] Created: (JBAS-8833) server crash on shutdown with ssl connector enabled

by Marcel Å ebek (JIRA)

server crash on shutdown with ssl connector enabled --------------------------------------------------- Key: JBAS-8833 URL: https://issues.jboss.org/browse/JBAS-8833 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.1.0.GA Environment: Linux - Debian ~testing, libssl0.9.8o, libtcnative-1.1.20 Reporter: Marcel Å ebek Assignee: Remy Maucherat With https connector enabled and using libtcnative, the server segfaults during shutdown. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
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 January 2011