March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBMESSAGING-254) Remove ThreadContextClassLoaderChanger

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-254?page=all ] Clebert Suconic reassigned JBMESSAGING-254: ------------------------------------------- Assignee: Clebert Suconic (was: Ovidiu Feodorov) > Remove ThreadContextClassLoaderChanger > -------------------------------------- > > Key: JBMESSAGING-254 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-254 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Critical > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Kabir has fixed this in AOP so this is no longer necessary. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-254) Remove ThreadContextClassLoaderChanger

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-254?page=comments#action_12... ] Clebert Suconic commented on JBMESSAGING-254: --------------------------------------------- Accordinly to Kabir, all we have to do is change JmsClientAspectXMLLoader::deployXML as follows: public void deployXML(byte[] config) throws Exception { ...... this.deployXML(doc, null, this.getClass().getClassLoader()); ....... } I have tested this as a fix to JBMESSAGING-922 and it worked. > Remove ThreadContextClassLoaderChanger > -------------------------------------- > > Key: JBMESSAGING-254 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-254 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Kabir has fixed this in AOP so this is no longer necessary. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-996) Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-996?page=all ] Manik Surtani closed JBCACHE-996. --------------------------------- Resolution: Cannot Reproduce Bug > Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest > ------------------------------------------------------------------- > > Key: JBCACHE-996 > URL: http://jira.jboss.com/jira/browse/JBCACHE-996 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.BETA1 > Reporter: Rajesh Rajasekaran > Assigned To: Manik Surtani > Fix For: 2.0.0.BETA2 > > > org.jboss.cache.multiplexer.BuddyGroupAssignmentTest fails on the release distribution. > To reproduce: > run ./build.sh dist. > Unzip JBossCache-all-2.0.0.BETA1.zip > Run ant one.test -Dtest=org.jboss.cache.multiplexer.BuddyGroupAssignmentTest > <testcase classname="org.jboss.cache.multiplexer.BuddyGroupAssignmentTest" name="testRemovalFromCluster2Buddies" time="24.523"> > <failure message="10.16.7.254:60612 should be a buddy to 10.16.7.254:60606" type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: 10.16.7.254:60612 should be a buddy to 10.16.7.254:60606 > at org.jboss.cache.buddyreplication.BuddyReplicationTestsBase.assertIsBuddy(BuddyReplicationTestsBase.java:285) > at org.jboss.cache.buddyreplication.BuddyGroupAssignmentTest.testRemovalFromCluster2Buddies(BuddyGroupAssignmentTest.java:131) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > </failure> -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-985) build failed under jboss distribution

by Ben Wang (JIRA)

build failed under jboss distribution ------------------------------------- Key: JBCACHE-985 URL: http://jira.jboss.com/jira/browse/JBCACHE-985 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ben Wang Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 After doing a "build dist" under JBC, do an unzip of the JBossCache-xxx.zip, and then do a "build compile" would fail to compile becuase new dependency on ant and some cacheloader (bdbje) errors. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-993) Test failure - org.jboss.cache.marshall.AsyncReplTest, org.jboss.cache.marshall.SyncReplTest

by Rajesh Rajasekaran (JIRA)

Test failure - org.jboss.cache.marshall.AsyncReplTest, org.jboss.cache.marshall.SyncReplTest -------------------------------------------------------------------------------------------- Key: JBCACHE-993 URL: http://jira.jboss.com/jira/browse/JBCACHE-993 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Manik Surtani Fix For: 2.0.0.BETA1 org.jboss.cache.marshall.AsyncReplTest & org.jboss.cache.marshall.SyncReplTest fail on the release distribution. To reproduce: run ./build.sh dist. Unzip JBossCache-all-2.0.0.BETA1.zip Run ant one.test -Dtest=org.jboss.cache.marshall.AsyncReplTest 1.) org.jboss.cache.marshall.AsyncReplTest testCustomFqn N/A java.lang.NullPointerException at org.jboss.cache.marshall.FooClassLoader.loadFoo(FooClassLoader.java:25) at org.jboss.cache.marshall.AsyncReplTest.testCustomFqn(AsyncReplTest.java:295) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2.) org.jboss.cache.marshall.SyncReplTest testCustomFqn N/A java.lang.NullPointerException at org.jboss.cache.marshall.FooClassLoader.loadFoo(FooClassLoader.java:25) at org.jboss.cache.marshall.SyncReplTest.testCustomFqn(SyncReplTest.java:381) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4190) Add EJB2 SFSB and EJB3 Session bean testing to ClassloaderLeakUnitTestCase

by Brian Stansberry (JIRA)

Add EJB2 SFSB and EJB3 Session bean testing to ClassloaderLeakUnitTestCase -------------------------------------------------------------------------- Key: JBAS-4190 URL: http://jira.jboss.com/jira/browse/JBAS-4190 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Brian Stansberry Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA Expand the EE component types that are tested -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1003) Missing extention attribute when running some test targets

by Aleksandar Kostadinov (JIRA)

Missing extention attribute when running some test targets ---------------------------------------------------------- Key: JBCACHE-1003 URL: http://jira.jboss.com/jira/browse/JBCACHE-1003 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Aleksandar Kostadinov Assigned To: Manik Surtani Priority: Critical In HEAD there is missing extention attribute of junit task's formatter nested element which leads to not including these tests in the final report as files don't get ".xml" extension. As well udp stack maybe overwrites tcp stack tests. Problem is verified for "all-unittests-retro-cc" target. I see other junit tasks without this attribute also. See http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite-jdk1... Cruisecontrol reports testsuite completed without any 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, 1 month

2
1
0 / 0

[JBoss JIRA] Commented: (JBAS-1192) CheckValidConnectionSQL is not Serializable

by Aditya Mishra (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1192?page=comments#action_12356102 ] Aditya Mishra commented on JBAS-1192: ------------------------------------- This issue also exists in the JBoss 4.0. Adding to this we are also not able to get the ResultSet in the other jvm when we are using the DB2 with JBoss. This is handled in weblogic. > CheckValidConnectionSQL is not Serializable > ------------------------------------------- > > Key: JBAS-1192 > URL: http://jira.jboss.com/jira/browse/JBAS-1192 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-3.2.6 Final > Reporter: SourceForge User > Assigned To: Adrian Brock > Fix For: Closed issues from sourceforge > > > SourceForge Submitter: prudrakshala . > WrapperDataSource implements Serializable, but when > serializing a Data Source with <check-valid-connection- > sql> element in -ds.xml fails. > 2004-11-09 19:01:08,866 INFO [STDOUT] > java.io.NotSerializableException: > org.jboss.resource.adapter.jdbc.CheckValidConnectionSQ > L > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.writeObject0 > (ObjectOutputStream.java:1054) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.defaultWriteFields > (ObjectOutputStream.java:1332) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.writeSerialData > (ObjectOutputStream.java:1304) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.writeOrdinaryObject > (ObjectOutputStream.java:1247) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.writeObject0 > (ObjectOutputStream.java:1052) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.defaultWriteFields > (ObjectOutputStream.java:1332) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.writeSerialData > (ObjectOutputStream.java:1304) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.writeOrdinaryObject > (ObjectOutputStream.java:1247) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.writeObject0 > (ObjectOutputStream.java:1052) > 2004-11-09 19:01:08,866 INFO [STDOUT] at > java.io.ObjectOutputStream.writeObject > (ObjectOutputStream.java:278) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-994) Test failure - org.jboss.cache.loader.AdjListJDBCClassLoaderCompatibilityTest

by Rajesh Rajasekaran (JIRA)

Test failure - org.jboss.cache.loader.AdjListJDBCClassLoaderCompatibilityTest ----------------------------------------------------------------------------- Key: JBCACHE-994 URL: http://jira.jboss.com/jira/browse/JBCACHE-994 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Manik Surtani Fix For: 2.0.0.BETA1 org.jboss.cache.loader.AdjListJDBCClassLoaderCompatibilityTest fails on the release distribution. To reproduce: run ./build.sh dist. Unzip JBossCache-all-2.0.0.BETA1.zip Run ant one.test -Dtest=org.jboss.cache.loader.AdjListJDBCClassLoaderCompatibilityTest Error Connectionn factory class could not be loaded java.lang.IllegalStateException: Connectionn factory class could not be loaded at org.jboss.cache.loader.AdjListJDBCClassLoader.setConfig(AdjListJDBCClassLoader.java:49) at org.jboss.cache.loader.AdjListJDBCClassLoaderCompatibilityTest.getOldLoader(AdjListJDBCClassLoaderCompatibilityTest.java:262) at org.jboss.cache.loader.AdjListJDBCClassLoaderCompatibilityTest.setUp(AdjListJDBCClassLoaderCompatibilityTest.java:48)Caused by: java.lang.ClassNotFoundException: org.jboss.cache.manualtests.cacheloader.OneConnectionFactory at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.cache.util.Util.loadClass(Util.java:52) at org.jboss.cache.loader.AdjListJDBCClassLoader.setConfig(AdjListJDBCClassLoader.java:44) ... 12 more -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-437) Util.objectToByteBuffer() throw exception if string argument is > 65K

by Bela Ban (JIRA)

Util.objectToByteBuffer() throw exception if string argument is > 65K --------------------------------------------------------------------- Key: JGRP-437 URL: http://jira.jboss.com/jira/browse/JGRP-437 Project: JGroups Issue Type: Bug Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 java.io.UTFDataFormatException: encoded string too long: 140000 bytes at java.io.DataOutputStream.writeUTF(DataOutputStream.java:347) at java.io.DataOutputStream.writeUTF(DataOutputStream.java:306) at org.jgroups.util.Util.objectToByteBuffer(Util.java:281) at org.jgroups.tests.UtilTest.testObjectToByteArrayWithLargeString(UtilTest.java:229) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) -- 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, 1 month

1
2
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