March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4272) failing org.jboss.test.classloader.leak.test.Ejb3ClassloaderLeakUnitTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.classloader.leak.test.Ejb3ClassloaderLeakUnitTestCase ---------------------------------------------------------------------------- Key: JBAS-4272 URL: http://jira.jboss.com/jira/browse/JBAS-4272 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_10-b03 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-42.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Priority: Critical Fix For: JBossAS-4.2.0.GA All the tests in the testcase fail with something like: Name Status Type Time(s) testSimpleEjb Failure Classloaders unregistered: EJB3_SLSB junit.framework.AssertionFailedError: Classloaders unregistered: EJB3_SLSB at org.jboss.test.classloader.leak.test.ClassloaderLeakTestBase.ejbTest(ClassloaderLeakTestBase.java:191) at org.jboss.test.classloader.leak.test.Ejb3ClassloaderLeakUnitTestCase.testSimpleEjb(Ejb3ClassloaderLeakUnitTestCase.java:74) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) Brian, if you can't handle this, give it the EJB3 guys. -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3611) Get the jboss-4.0-testsuite-sun-1.5 passing

by Dimitris Andreadis (JIRA)

Get the jboss-4.0-testsuite-sun-1.5 passing ------------------------------------------- Key: JBAS-3611 URL: http://jira.jboss.com/jira/browse/JBAS-3611 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA Container task for sun jdk1.5 test run failures -- 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

19 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-3906) 4.2 testsuite on RHEL4 (JRockit jdk5)

by Dimitris Andreadis (JIRA)

4.2 testsuite on RHEL4 (JRockit jdk5) ------------------------------------- Key: JBAS-3906 URL: http://jira.jboss.com/jira/browse/JBAS-3906 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4243) build.bat does not process command line arguments correctly

by Richard Achmatowicz (JIRA)

build.bat does not process command line arguments correctly ----------------------------------------------------------- Key: JBAS-4243 URL: http://jira.jboss.com/jira/browse/JBAS-4243 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.2.0.CR1 Environment: Windows 2003 Reporter: Richard Achmatowicz Fix For: JBossAS-4.2.0.GA The batch script build.bat in the testsuite diredctory does not correctly deal long command lines, such as this required for testing: > build.bat -Djboss.dist=<dist location> -Dnode0=%MYTESTIP_1% -Dnode1=%MYTESTIP_2% -DudpGroup=239.11.12.13 tests Windows batch files throw out '=' signs when processing command line arguments. This the command line arguments above are: %1=-Djboss.dist %2=<dist location> %3=-Dnode0 %4=%MYTESTIP_1% %5=-Dnode1 %6=%MYTESTIP_2% %7=-DudpGroup %8=239.11.12.13 %9=tests However, build.bat is written in such a way that it processes a maximum of 6 command line arguments. Thus, I can't run the testsuite with the command line above using build.bat. The same problem presumably applies to build.bat in the build directory. I have written a modification of build.bat which will handle command lines of any length, mimicking what the ant batch file does using the shift command. Will post this when JBoss Labs is available again. -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4260) JBossMQ table schema can not be created within a transaction when using MS SQL Server jdbc driver

by Luc Texier (JIRA)

JBossMQ table schema can not be created within a transaction when using MS SQL Server jdbc driver ------------------------------------------------------------------------------------------------- Key: JBAS-4260 URL: http://jira.jboss.com/jira/browse/JBAS-4260 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Environment: MS SQL Server jdbd driver 1.1 MS SQL Server 2005 database Reporter: Luc Texier Assigned To: Luc Texier Fix For: JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1 At startup, when creating the table schema for JBossMQ, the following error is thrown 11:19:15,468 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=JmsXA,service=ConnectionFactoryBinding' to JNDI name 'java:JmsXA' 11:19:15,539 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=KANA/jdbc/realm1,service=DataSourceBinding' to JNDI name 'java:KANA/jdbc/realm1' 11:19:15,870 WARN [TransactionImpl] XAException: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=mht-vani/1, BranchQual=, localId=1] errorCode=XA_RBROLLBACK org.jboss.resource.connectionmanager.JBossLocalXAException: could not commit local tx; - nested throwable: (org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: New request is not allowed to start because it should come with valid transaction descriptor.)) at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.commit(TxConnectionManager.java:912) at org.jboss.tm.TransactionImpl$Resource.commit(TransactionImpl.java:2253) at org.jboss.tm.TransactionImpl.commitResources(TransactionImpl.java:1784) at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:340) at org.jboss.tm.TxManager.commit(TxManager.java:240) at org.jboss.mq.sm.jdbc.JDBCStateManager$JDBCSession.close(JDBCStateManager.java:613) at org.jboss.mq.sm.jdbc.JDBCStateManager.initDB(JDBCStateManager.java:465) at org.jboss.mq.sm.jdbc.JDBCStateManager.startService(JDBCStateManager.java:378) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) 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) The MS jdbc driver does not support table schema creation in the scope of a transaction -- 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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4163) Interation between custom jboss trace and log4j trace levels

by Scott M Stark (JIRA)

Interation between custom jboss trace and log4j trace levels ------------------------------------------------------------ Key: JBAS-4163 URL: http://jira.jboss.com/jira/browse/JBAS-4163 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System, Logging Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.0.GA I believe the following type of configuration should work with the current log4j version as it now supports trace natively: <category name="org.jboss.profileservice"> <priority value="TRACE"/> <appender-ref ref="PROFILESERVICE"/> </category> While messages do appear in the PROFILESERVICE appender, no trace level messages are there. Most likely the jboss Logger is getting in the way of mapping this priority and an update to the common logging spi is needed. -- 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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4263) Remove JBoss version of StandardService

by Anil Saldhana (JIRA)

Remove JBoss version of StandardService --------------------------------------- Key: JBAS-4263 URL: http://jira.jboss.com/jira/browse/JBAS-4263 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Anil Saldhana Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.Beta2 The tomcat module contains a version of StandardService that was forked to basically not start the tomcat connectors as part of the service startup, but rather the connectors are started after the JBoss server starts. Since the addition of Executors to the Catalina service interface, as of this morning, this StandardService class has gone stale. We will need to update this class to incorporate the new changes to the Service interface. Since we are using JBossWeb, I am wondering if we can make the start of the connectors configurable in StandardService of JBossWeb such that we can discard this fork of StandardService sitting in the tomcat module. -- 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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Commented: (JBAS-3162) Testcase to validate set up of a root context web app

by Stan Silvert (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3162?page=comments#action_12357782 ] Stan Silvert commented on JBAS-3162: ------------------------------------ I'm going to try to get it done, but I'm not sure if I can finish it by Friday. > Testcase to validate set up of a root context web app > ----------------------------------------------------- > > Key: JBAS-3162 > URL: http://jira.jboss.com/jira/browse/JBAS-3162 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Anil Saldhana > Assigned To: Stan Silvert > Priority: Minor > Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.0.GA > > > Need to have a testcase that validates > http://wiki.jboss.org/wiki/Wiki.jsp?page=SetupARootContextApp -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-3071) MemoryLeak (redeployment) on EJB3

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3071?page=all ] Carlo de Wolf resolved JBAS-3071. --------------------------------- Fix Version/s: JBossAS-5.0.0.Beta2 (was: JBossAS-5.0.0.Beta3) Resolution: Done > MemoryLeak (redeployment) on EJB3 > --------------------------------- > > Key: JBAS-3071 > URL: http://jira.jboss.com/jira/browse/JBAS-3071 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB3 > Affects Versions: JBossAS-4.0.4.CR2 > Reporter: Clebert Suconic > Assigned To: Carlo de Wolf > Priority: Critical > Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA > > Attachments: leaks.txt > > > This might be caused by JBAS-3016: > But I'm seeing this strong reference: > org.jboss.mx.loading.UnifiedClassLoader3@33411906 > !--- org.jboss.ejb3.stateless.StatelessContainer@29610827 > We should make sure EJB3 packages are not leaking. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3582) Get the ejb3-4.0 testsuite passing

by Dimitris Andreadis (JIRA)

Get the ejb3-4.0 testsuite passing ---------------------------------- Key: JBAS-3582 URL: http://jira.jboss.com/jira/browse/JBAS-3582 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Bill Burke Fix For: JBossAS-4.0.5.CR1 There are currenlty 28 failures -- 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

19 years, 3 months

3
10
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 March 2007