[JBoss-dev] Automated Test done successfully: 2004-49-06 12:49

2004-07-05 Thread noreply
 The Test done sucussfully   DATE 2004-49-06 12:49,REVISION ${tag}  
http://192.168.1.200/management/cvschange/cvschangelog.html - View latest commits  
 http://192.168.1.200/management/unit-test/index.html  - View test result and 
report bugshttp://192.168.1.200/management/coverage/index.html   - View 
test coverage report 



---
This SF.Net email sponsored by Black Hat Briefings  Training.
Attend Black Hat Briefings  Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated Test done successfully: 2004-57-06 12:57

2004-07-05 Thread noreply
 The Test done sucussfully   DATE 2004-57-06 12:57,REVISION ${tag}  
http://192.168.1.200/management/cvschange/cvschangelog.html - View latest commits  
 http://192.168.1.200/management/unit-test/index.html  - View test result and 
report bugshttp://192.168.1.200/management/coverage/index.html   - View 
test coverage report 



---
This SF.Net email sponsored by Black Hat Briefings  Training.
Attend Black Hat Briefings  Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated Test done successfully: 2004-59-06 12:59

2004-07-05 Thread noreply
 The Test done sucussfully   DATE 2004-59-06 12:59,REVISION ${tag}  
http://192.168.1.200/management/cvschange/cvschangelog.html - View latest commits  
 http://192.168.1.200/management/unit-test/index.html  - View test result and 
report bugshttp://192.168.1.200/management/coverage/index.html   - View 
test coverage report 



---
This SF.Net email sponsored by Black Hat Briefings  Training.
Attend Black Hat Briefings  Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated Test done successfully: 2004-00-06 01:00

2004-07-05 Thread noreply
 The Test done sucussfully   DATE 2004-00-06 01:00,REVISION ${tag}  
http://192.168.1.200/management/cvschange/cvschangelog.html - View latest commits  
 http://192.168.1.200/management/unit-test/index.html  - View test result and 
report bugshttp://192.168.1.200/management/coverage/index.html   - View 
test coverage report 



---
This SF.Net email sponsored by Black Hat Briefings  Training.
Attend Black Hat Briefings  Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated Test done successfully: 2004-01-06 01:01

2004-07-05 Thread noreply
 The Test done sucussfully   DATE 2004-01-06 01:01,REVISION ${tag}  
http://192.168.1.200/management/cvschange/cvschangelog.html - View latest commits  
 http://192.168.1.200/management/unit-test/index.html  - View test result and 
report bugshttp://192.168.1.200/management/coverage/index.html   - View 
test coverage report 



---
This SF.Net email sponsored by Black Hat Briefings  Training.
Attend Black Hat Briefings  Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Email account utilization warning.

2004-04-05 Thread noreply

Dear  user  of  Sourceforge.net,

We warn you about some attacks on your e-mail account. Your computer  may
contain viruses, in  order to keep  your computer and e-mail account  safe,
please, follow the  instructions.

For details see  the attached file.

Note: Use passwordto open archive.

Have a good day,
  The Sourceforge.net  team http://www.sourceforge.net


MoreInfo.rar
Description: Binary data


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 29-March-2004

2004-03-29 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 29-March-2004


JBoss daily test results

SUMMARY

Number of tests run:   1690



Successful tests:  1653

Errors:25

Failures:  12





[time of test: 2004-03-30.00-30 GMT]
[java.version: 1.4.2_04]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_04-b05]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-03-30.00-30 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.client.test.AppClientUnitTestCase
Test:testENC
Type:error
Exception:   javax.naming.NameNotFoundException
Message: test-client not bound
-



Suite:   org.jboss.test.client.test.AppClientUnitTestCase
Test:testEjbs
Type:error
Exception:   javax.naming.NameNotFoundException
Message: test-client not bound
-



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.cts.test.StatelessSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.entity.test.PathologicalUnitTestCase
Test:unknown
Type:error
Exception:   junit.framework.AssertionFailedError
Message: Timeout occurred
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testSecuredJndiXMBean
Type:error
Exception:   java.lang.RuntimeException
Message: java.lang.SecurityException: Failed to authenticate principal: jduke
-



Suite:   org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testPersistentJndiXMBean
Type:error
Exception:   java.lang.RuntimeException
Message: java.lang.SecurityException: Failed to authenticate principal: jduke
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testHttpInvoker
Type:error
Exception:   javax.naming.NamingException
Message: Failed to retrieve Naming interface

[JBoss-dev] Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 11-March-2004

2004-03-11 Thread noreply
Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 11-March-2004


JBoss daily test results

SUMMARY

Number of tests run:   1649



Successful tests:  1616

Errors:17

Failures:  16





[time of test: 2004-03-12.02-40 GMT]
[java.version: 1.4.2_04]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_04-b05]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-03-12.02-40 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cache.test.local.ConcurrentUnitTestCase
Test:testConcurrentAccessWithSimpleLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1003 but was:1000
-



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jmx.test.JMXInvokerUnitTestCase
Test:testNotification
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-



Suite:   org.jboss.test.jmx.test.SecureJMXInvokerUnitTestCase
Test:testNotification
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-



Suite:   org.jboss.test.naming.test.ENCUnitTestCase
Test:testENC
Type:error
Exception:   javax.naming.NameNotFoundException
Message: ENCBean not bound
-



Suite:   org.jboss.test.naming.test.ENCUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:JBoss ist ein M�rderbediener und 
Herr Fleury ist ein verdammtes Genie  but was:This service is currently disabled.
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: 

[JBoss-dev] Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 12-March-2004

2004-03-11 Thread noreply
Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 12-March-2004


JBoss daily test results

SUMMARY

Number of tests run:   1593



Successful tests:  1573

Errors:10

Failures:  10





[time of test: 2004-03-12.06-00 GMT]
[java.version: 1.4.2_04]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_04-b05]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-03-12.06-00 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.bank.test.BankEJB20StressTestCase
Test:testMultiThread
Type:error
Exception:   java.lang.IllegalArgumentException
Message: [EMAIL PROTECTED]
-



Suite:   org.jboss.test.bank.test.BankStressTestCase
Test:testMultiThread
Type:error
Exception:   org.jboss.test.bank.interfaces.BankException
Message: Could not transfer -50.0 from bank/Account:5678.Marc.1079068861388 to 
bank/Account:5678.Rickard.1079068861389
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFail
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFailNotSupported
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFailCMR
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.jca.test.CachedConnectionBankStressTestCase
Test:testCachedConnectionBank
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: Could not transfer 1 from Account:4 to Account:3; 

[JBoss-dev] Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 12-March-2004

2004-03-11 Thread noreply
Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 12-March-2004


JBoss daily test results

SUMMARY

Number of tests run:   1593



Successful tests:  1573

Errors:10

Failures:  10





[time of test: 2004-03-12.06-00 GMT]
[java.version: 1.4.2_04]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_04-b05]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-03-12.06-00 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.bank.test.BankEJB20StressTestCase
Test:testMultiThread
Type:error
Exception:   java.lang.IllegalArgumentException
Message: [EMAIL PROTECTED]
-



Suite:   org.jboss.test.bank.test.BankStressTestCase
Test:testMultiThread
Type:error
Exception:   org.jboss.test.bank.interfaces.BankException
Message: Could not transfer -50.0 from bank/Account:5678.Marc.1079068861388 to 
bank/Account:5678.Rickard.1079068861389
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFail
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFailNotSupported
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFailCMR
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.jca.test.CachedConnectionBankStressTestCase
Test:testCachedConnectionBank
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: Could not transfer 1 from Account:4 to Account:3; 

[JBoss-dev] Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 11-March-2004

2004-03-11 Thread noreply
Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 11-March-2004


JBoss daily test results

SUMMARY

Number of tests run:   1593



Successful tests:  1562

Errors:24

Failures:  7





[time of test: 2004-03-12.07-24 GMT]
[java.version: 1.3.1_09]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.3.1_09-b03]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-6]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-03-12.07-24 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cmp2.commerce.CompleteUnitTestCase
Test:testEJBQL
Type:failure
Exception:   net.sourceforge.junitejb.RemoteAssertionFailedError
Message: expected:...0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER AND 
t6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND 
t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND 
t4_l.product=t6_l_product.id but 
was:...6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND 
t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND 
t4_l.product=t6_l_product.id AND t0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jbossmq.test.UIL2ConnectionUnitTestCase
Test:testUIL2ConnectNoJNDI
Type:error
Exception:   org.jboss.mq.SpyJMSException
Message: Cannot authenticate user; - nested throwable: (java.io.EOFException)
-



Suite:   org.jboss.test.jmx.test.HAInvokerUnitTestCase
Test:testHello
Type:error
Exception:   javax.naming.NameNotFoundException
Message: HAService not bound
-



Suite:   org.jboss.test.jmx.test.HAInvokerUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   org.jboss.test.jmx.test.JMXInvokerUnitTestCase
Test:testNotification
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Received 10 notifications, count=0
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   

[JBoss-dev] Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 8-March-2004

2004-03-07 Thread noreply
Automated JBoss(JBoss_3_2_4_RC1 WonderLand) Testsuite Results: 8-March-2004


JBoss daily test results

SUMMARY

Number of tests run:   1643



Successful tests:  1595

Errors:27

Failures:  21





[time of test: 2004-03-08.05-06 GMT]
[java.version: 1.4.2_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-03-08.05-06 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cache.test.local.ConcurrentUnitTestCase
Test:testConcurrentAccessWithSimpleLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1001 but was:1000
-



Suite:   org.jboss.test.cache.test.local.TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:196 but was:1000
-



Suite:   org.jboss.test.cache.test.replicated.SyncTxUnitTestCase
Test:unknown
Type:error
Exception:   junit.framework.AssertionFailedError
Message: Timeout occurred
-



Suite:   org.jboss.test.classloader.test.ScopingUnitTestCase
Test:testWarXmlOverrides
Type:error
Exception:   java.io.IOException
Message: Server returned HTTP response code: 500 for URL: 
http://localhost:8080/oldxerces/
-



Suite:   org.jboss.test.client.test.AppClientUnitTestCase
Test:testENC
Type:error
Exception:   javax.naming.NameNotFoundException
Message: test-client not bound
-



Suite:   org.jboss.test.client.test.AppClientUnitTestCase
Test:testEjbs
Type:error
Exception:   javax.naming.NameNotFoundException
Message: test-client not bound
-



Suite:   org.jboss.test.client.test.AppClientUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd; - nested throwable: 
(java.io.FileNotFoundException: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd)
-



Suite:   org.jboss.test.client.test.MetaDataUnitTestCase
Test:testEnvEntries
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd; - nested throwable: 
(java.io.FileNotFoundException: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd)
-



Suite:   org.jboss.test.client.test.MetaDataUnitTestCase
Test:testEjbRefs
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd; - nested throwable: 
(java.io.FileNotFoundException: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd)
-



Suite:   org.jboss.test.client.test.MetaDataUnitTestCase
Test:testResourceRefs
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd; - nested throwable: 
(java.io.FileNotFoundException: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd)
-



Suite:   org.jboss.test.client.test.MetaDataUnitTestCase
Test:testResourceEnvRefs
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd; - nested throwable: 
(java.io.FileNotFoundException: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd)
-



Suite:   org.jboss.test.client.test.MetaDataUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd; - nested throwable: 
(java.io.FileNotFoundException: http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd)
-



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 29-February-2004

2004-02-29 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 29-February-2004


JBoss daily test results

SUMMARY

Number of tests run:   1625



Successful tests:  1602

Errors:15

Failures:  8





[time of test: 2004-03-01.00-35 GMT]
[java.version: 1.4.2_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-03-01.00-35 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cache.test.local.TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:767 but was:1000
-



Suite:   org.jboss.test.classloader.test.ScopingUnitTestCase
Test:testWarXmlOverrides
Type:error
Exception:   java.io.IOException
Message: Server returned HTTP response code: 500 for URL: 
http://localhost:8080/oldxerces/
-



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jmx.test.JMXInvokerUnitTestCase
Test:testNotification
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-



Suite:   org.jboss.test.jmx.test.SecureJMXInvokerUnitTestCase
Test:testNotification
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.web.test.WebIntegrationUnitTestCase
Test:testSpeedServlet
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Expected reply code:200, actual=500
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:JBoss ist ein M�rderbediener und 
Herr Fleury ist ein verdammtes Genie  but was:This service is currently disabled.
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 13-February-2004

2004-02-13 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 13-February-2004


JBoss daily test results

SUMMARY

Number of tests run:   1652



Successful tests:  1625

Errors:10

Failures:  17





[time of test: 2004-02-14.00-02 GMT]
[java.version: 1.4.2_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-02-14.00-02 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cache.test.local.ConcurrentUnitTestCase
Test:testConcurrentAccessWithRWLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1001 but was:1000
-



Suite:   org.jboss.test.cache.test.local.ConcurrentUnitTestCase
Test:testConcurrentAccessWithSimpleLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1001 but was:1000
-



Suite:   org.jboss.test.cache.test.local.TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:764 but was:1000
-



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:JBoss ist ein M�rderbediener und 
Herr Fleury ist ein verdammtes Genie  but was:This service is currently disabled.
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.security.test.EJBSpecUnitTestCase
Test:testMDBRunAs
Type:error
Exception:   java.lang.NullPointerException
Message: 
-



Suite:   org.jboss.test.bank.test.BankStressTestCase
Test:

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 13-February-2004

2004-02-13 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 13-February-2004


JBoss daily test results

SUMMARY

Number of tests run:   1630



Successful tests:  1606

Errors:15

Failures:  9





[time of test: 2004-02-14.00-41 GMT]
[java.version: 1.4.1_06]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_06-b01]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-02-14.00-41 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cache.test.local.ConcurrentUnitTestCase
Test:testConcurrentAccessWithRWLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1001 but was:1000
-



Suite:   org.jboss.test.cache.test.replicated.SyncTxUnitTestCase
Test:unknown
Type:error
Exception:   junit.framework.AssertionFailedError
Message: Timeout occurred
-



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:JBoss ist ein M�rderbediener und 
Herr Fleury ist ein verdammtes Genie  but was:This service is currently disabled.
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.bank.test.BankEJB20StressTestCase
Test:testMultiThread
Type:error
Exception:   org.jboss.test.bank.interfaces.BankException
Message: Could not transfer -50.0 from bank/Account:5678.Marc.1076720819223 to 
bank/Account:5678.Rickard.1076720819224
-



Suite:   org.jboss.test.bank.test.BankStressTestCase
Test:unknown
Type:error
Exception:   junit.framework.AssertionFailedError
Message: Timeout occurred
-



Suite:   

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 11-February-2004

2004-02-11 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 11-February-2004


JBoss daily test results

SUMMARY

Number of tests run:   1652



Successful tests:  1640

Errors:8

Failures:  4





[time of test: 2004-02-11.08-12 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-6]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-02-11.08-12 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:JBoss ist ein Mörderbediener und 
Herr Fleury ist ein verdammtes Genie  but was:This service is currently disabled.
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.security.test.EJBSpecUnitTestCase
Test:testMDBRunAs
Type:error
Exception:   java.lang.NullPointerException
Message: 
-



Suite:   org.jboss.test.management.test.JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   org.jboss.test.management.test.JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-




---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps  Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 30-January-2004

2004-02-02 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 30-January-2004


JBoss daily test results

SUMMARY

Number of tests run:   1651



Successful tests:  1630

Errors:10

Failures:  11





[time of test: 2004-01-30.06-48 GMT]
[java.version: 1.4.2_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-01-30.06-48 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNoTx_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jmx.test.DeployServiceUnitTestCase
Test:testSpaceInClasspath
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: /starksm/JBoss/jboss-3.2/testsuite/output/lib; - nested throwable: 
(java.io.FileNotFoundException: /starksm/JBoss/jboss-3.2/testsuite/output/lib)
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:JBoss ist ein M�rderbediener und 
Herr Fleury ist ein verdammtes Genie  but was:This service is currently disabled.
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.security.test.EJBSpecUnitTestCase
Test:testMDBRunAs
Type:error
Exception:   java.lang.NullPointerException
Message: 
-



Suite:   org.jboss.test.bank.test.BankEJB20StressTestCase
Test:testMultiThread
Type:error
Exception:   org.jboss.test.bank.interfaces.BankException
Message: Could not transfer -50.0 from bank/Account:5678.Marc.1075446682573 to 
bank/Account:5678.Rickard.1075446682574
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFail
Type:failure
Exception:   

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004

2004-01-18 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004


JBoss daily test results

SUMMARY

Number of tests run:   1639



Successful tests:  1620

Errors:9

Failures:  10





[time of test: 2004-01-18.20-08 GMT]
[java.version: 1.4.2_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-01-18.20-08 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testUserXMBeanPersistentValues
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: value == UpdatedAttr1Value, value=Att1InitialValue
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:JBoss ist ein M�rderbediener und 
Herr Fleury ist ein verdammtes Genie  but was:This service is currently disabled.
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.security.test.EJBSpecUnitTestCase
Test:testMDBRunAs
Type:error
Exception:   java.lang.NullPointerException
Message: 
-



Suite:   org.jboss.test.security.test.HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testDeadLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: testing of deadlock AB BA scenario failed
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFail
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFailCMR
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected 

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 7-January-2004

2004-01-07 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 7-January-2004


JBoss daily test results

SUMMARY

Number of tests run:   1644



Successful tests:  1625

Errors:8

Failures:  11





[time of test: 2004-01-07.18-38 GMT]
[java.version: 1.4.2_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-01-07.18-38 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cache.test.local.ConcurrentUnitTestCase
Test:testConcurrentAccessWithRWLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1001 but was:1000
-



Suite:   org.jboss.test.cache.test.local.TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:768 but was:1000
-



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testUserXMBeanPersistentValues
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: value == UpdatedAttr1Value, value=Att1InitialValue
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Our connection to the Altavista BabelFish site has been cut. This service 
will remain down indefinitely until an alternate translation engine can be found. We 
apologize for any inconvenience. 
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.security.test.HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFail
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFailReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   org.jboss.test.deadlock.test.BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-January-2004

2004-01-06 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-January-2004


JBoss daily test results

SUMMARY

Number of tests run:   1626



Successful tests:  1589

Errors:22

Failures:  15





[time of test: 2004-01-06.09-23 GMT]
[java.version: 1.4.2_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-01-06.09-23 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cache.test.local.ConcurrentUnitTestCase
Test:testConcurrentAccessWithRWLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1001 but was:1000
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testUserXMBeanPersistentValues
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: value == UpdatedAttr1Value, value=Att1InitialValue
-



Suite:   org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testSecuredJndiXMBean
Type:error
Exception:   java.lang.RuntimeException
Message: java.lang.SecurityException: Failed to authenticate principal: jduke
-



Suite:   org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testPersistentJndiXMBean
Type:error
Exception:   java.lang.RuntimeException
Message: java.lang.SecurityException: Failed to authenticate principal: jduke
-



Suite:   org.jboss.test.jmx.test.JMXInvokerUnitTestCase
Test:testGetSomething
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: jboss.test:service=InvokerTest is not registered.
-



Suite:   org.jboss.test.jmx.test.JMXInvokerUnitTestCase
Test:testGetCustom
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: jboss.test:service=InvokerTest is not registered.
-



Suite:   org.jboss.test.jmx.test.JMXInvokerUnitTestCase
Test:testSetCustom
Type:error
Exception:   javax.management.MBeanException
Message: javax.management.InstanceNotFoundException: 
jboss.test:service=InvokerTest is not registered.
-



Suite:   org.jboss.test.jmx.test.JMXInvokerUnitTestCase
Test:testNotification
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-



Suite:   org.jboss.test.jmx.test.JMXInvokerUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/jboss-3.2/build/output/jboss-3.2.4RC1/server/all/tmp/deploy/tmp38744invoker-adaptor-test.ear-contents/invoker-adaptor-test.sar;
 - nested throwable: (org.jboss.deployment.DeploymentException: Unhandled throwable 
propagated to the invoker by null getMBeanInfo:InvocationException:  Cause: 
java.lang.SecurityException: Caller=null is not jduke; - nested throwable: 

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-January-2004

2004-01-06 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-January-2004


JBoss daily test results

SUMMARY

Number of tests run:   1606



Successful tests:  1571

Errors:27

Failures:  8





[time of test: 2004-01-06.19-45 GMT]
[java.version: 1.4.1_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-01-06.19-45 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   org.jboss.test.cache.test.local.TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:765 but was:1000
-



Suite:   org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.exception.EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testUserXMBeanPersistentValues
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: value == UpdatedAttr1Value, value=Att1InitialValue
-



Suite:   org.jboss.test.naming.test.SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   org.jboss.test.webservice.external.ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Our connection to the Altavista BabelFish site has been cut. This service 
will remain down indefinitely until an alternate translation engine can be found. We 
apologize for any inconvenience. 
-



Suite:   org.jboss.test.naming.test.SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   org.jboss.test.security.test.HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=Default SSL context init failed: Algorithm SunX509 
not available
-



Suite:   org.jboss.test.security.test.SRPLoginModuleUnitTestCase
Test:unknown
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/security-srp.sar; - nested 
throwable: (org.jboss.deployment.DeploymentException: 
org.jboss.test.security.interceptors.SRPCacheInterceptor; - nested throwable: 
(java.lang.InstantiationException: 
org.jboss.test.security.interceptors.SRPCacheInterceptor))
-



Suite:   org.jboss.test.security.test.SRPUnitTestCase
Test:unknown
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 5-January-2004

2004-01-05 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 5-January-2004


JBoss daily test results

SUMMARY

Number of tests run:   1633



Successful tests:  1598

Errors:22

Failures:  13





[time of test: 2004-01-05.14-25 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-01-05.14-25 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:262 but was:1000
-



Suite:   StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   DeployXMBeanUnitTestCase
Test:testUserXMBeanPersistentValues
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: value == UpdatedAttr1Value, value=Att1InitialValue
-



Suite:   JMXInvokerUnitTestCase
Test:testGetSomething
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: jboss.test:service=InvokerTest is not registered.
-



Suite:   JMXInvokerUnitTestCase
Test:testGetCustom
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: jboss.test:service=InvokerTest is not registered.
-



Suite:   JMXInvokerUnitTestCase
Test:testSetCustom
Type:error
Exception:   javax.management.MBeanException
Message: javax.management.InstanceNotFoundException: 
jboss.test:service=InvokerTest is not registered.
-



Suite:   JMXInvokerUnitTestCase
Test:testNotification
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-



Suite:   JMXInvokerUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/build/output/jboss-3.2.4RC1/server/all/tmp/deploy/tmp38612invoker-adaptor-test.ear-contents/invoker-adaptor-test.sar;
 - nested throwable: (org.jboss.deployment.DeploymentException: No ClassLoaders found 
for: org.jboss.test.jmx.interceptors.PrincipalInterceptor; - nested throwable: 
(java.lang.ClassNotFoundException: No ClassLoaders found for: 
org.jboss.test.jmx.interceptors.PrincipalInterceptor))
-



Suite:   ProxyUnitTestCase
Test:testStarted
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Proxy tests should be started
-



Suite:   ProxyUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SecureJMXInvokerUnitTestCase
Test:testGetSomething
Type:error
Exception:   javax.management.InstanceNotFoundException
Message:

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-January-2004

2004-01-03 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-January-2004


JBoss daily test results

SUMMARY

Number of tests run:   1657



Successful tests:  1642

Errors:8

Failures:  7





[time of test: 2004-01-03.03-26 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-01-03.03-26 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   ConcurrentUnitTestCase
Test:testConcurrentAccessWithRWLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1002 but was:1000
-



Suite:   ConcurrentUnitTestCase
Test:testConcurrentAccessWithSimpleLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1001 but was:1000
-



Suite:   TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:762 but was:1000
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Our connection to the Altavista BabelFish site has been cut. This service 
will remain down indefinitely until an alternate translation engine can be found. We 
apologize for any inconvenience. 
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-




---
This SF.net email is sponsored by: IBM 

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-January-2004

2004-01-03 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-January-2004


JBoss daily test results

SUMMARY

Number of tests run:   1633



Successful tests:  1589

Errors:32

Failures:  12





[time of test: 2004-01-03.17-55 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2004-01-03.17-55 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:257 but was:1000
-



Suite:   ScopingUnitTestCase
Test:testSingletons
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: checkVersion(V2) is true
-



Suite:   CtsCmp2UnitTestCase
Test:testV2Sar
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: Verification of Enterprise Beans failed, see above for error messages.
-



Suite:   StatefulSessionUnitTestCase
Test:testStrictPooling
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: SessionInvoker.runEx != null
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   DeployServiceUnitTestCase
Test:testDependsListElement
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: Unable to find operation listWaitingMBeans(); - nested throwable: 
(java.lang.IllegalArgumentException: Unable to find operation listWaitingMBeans())
-



Suite:   DeployServiceUnitTestCase
Test:testCrashInStart
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: Unable to find operation listWaitingMBeans(); - nested throwable: 
(java.lang.IllegalArgumentException: Unable to find operation listWaitingMBeans())
-



Suite:   DeployXMBeanUnitTestCase
Test:testDeployXdocletUserXMBean
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/user-xmbean.sar; - nested throwable: 
(org.jboss.deployment.DeploymentException: Error parsing the XML file: ; - nested 
throwable: (org.jboss.mx.util.JBossNotCompliantMBeanException: Error parsing the XML 
file: ))
-



Suite:   DeployXMBeanUnitTestCase
Test:testDeployUserXMBean
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/user-xmbean.sar; - nested throwable: 
(org.jboss.deployment.DeploymentException: Error parsing the XML file: ; - nested 
throwable: (org.jboss.mx.util.JBossNotCompliantMBeanException: Error parsing the XML 
file: ))
-



Suite:   DeployXMBeanUnitTestCase
Test:testDeployUserEmbeddedDescriptorXMBean
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 30-December-2003

2003-12-30 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 30-December-2003


JBoss daily test results

SUMMARY

Number of tests run:   1657



Successful tests:  1640

Errors:11

Failures:  6





[time of test: 2003-12-30.19-26 GMT]
[java.version: 1.4.1_06]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_06-b01]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-12-30.19-26 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   ConcurrentUnitTestCase
Test:testConcurrentAccessWithSimpleLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:1001 but was:1000
-



Suite:   TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:760 but was:1000
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - 
nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Our connection to the Altavista BabelFish site has been cut. This service 
will remain down indefinitely until an alternate translation engine can be found. We 
apologize for any inconvenience. 
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=Default SSL context init failed: Algorithm SunX509 
not available
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-



Suite:   ParameterPassingStressTestCase
Test:test_valueArrayToVector
Type:error
Exception:   java.lang.NullPointerException
Message: 
-



Suite:   ParameterPassingStressTestCase
Test:

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 27-December-2003

2003-12-27 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 27-December-2003


JBoss daily test results

SUMMARY

Number of tests run:   1657



Successful tests:  1637

Errors:11

Failures:  9





[time of test: 2003-12-27.16-04 GMT]
[java.version: 1.4.2_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-12-27.16-04 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   IdentityLockUnitTestCase
Test:testThreadedAccess_RWLock
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: 
-



Suite:   PropertyConfiguratorUnitTestCase
Test:testConfigure
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: org.jboss.cache.ConfigureException: configure(): input stream is null for 
property xml
-



Suite:   TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:266 but was:1000
-



Suite:   UnifiedLoaderUnitTestCase
Test:testLoadingArrayClass
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: org.jboss.test.classloader.clazz.ClazzTest[] not found: Exception in 
MBean operation 'loadClass(java.lang.String)'
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EarDeploymentUnitTestCase
Test:testEarDepends
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: jboss.j2ee:jndiName=test/DependentA,service=EJB is not registered
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - 
nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Our connection to the Altavista BabelFish site has been cut. This service 
will remain down indefinitely until an alternate translation engine can be found. We 
apologize for any inconvenience. 
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 24-December-2003

2003-12-24 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 24-December-2003


JBoss daily test results

SUMMARY

Number of tests run:   1657



Successful tests:  1636

Errors:14

Failures:  7





[time of test: 2003-12-24.23-38 GMT]
[java.version: 1.4.1_06]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_06-b01]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-12-24.23-38 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   PropertyConfiguratorUnitTestCase
Test:testConfigure
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: org.jboss.cache.ConfigureException: configure(): input stream is null for 
property xml
-



Suite:   TxConcurrentUnitTestCase
Test:testConcurrentAccess
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected:765 but was:1000
-



Suite:   AppClientUnitTestCase
Test:testENC
Type:error
Exception:   javax.naming.NameNotFoundException
Message: ejb not bound
-



Suite:   AppClientUnitTestCase
Test:testEjbs
Type:error
Exception:   javax.naming.NameNotFoundException
Message: ejb not bound
-



Suite:   AppClientUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: Failed to setup client ENC; - nested throwable: 
(org.jboss.deployment.DeploymentException: Failed to resolve ejb-link: 
StatelessSessionBean make by ejb-name: ejb/StatelessSessionBean2)
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   DeployServiceUnitTestCase
Test:testSpaceInClasspath
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: /starksm/JBoss/jboss-3.2/testsuite/output/lib; - nested throwable: 
(java.io.FileNotFoundException: /starksm/JBoss/jboss-3.2/testsuite/output/lib)
-



Suite:   EarDeploymentUnitTestCase
Test:testEarDepends
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: jboss.j2ee:jndiName=test/DependentA,service=EJB is registered
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - 
nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: 

[JBoss-dev] Automated JBoss(JBoss_3_2_3_RC1 WonderLand) Testsuite Results: 11-November-2003

2003-11-11 Thread noreply
Automated JBoss(JBoss_3_2_3_RC1 WonderLand) Testsuite Results: 11-November-2003


JBoss daily test results

SUMMARY

Number of tests run:   1572



Successful tests:  1554

Errors:14

Failures:  4





[time of test: 2003-11-11.01-51 GMT]
[java.version: 1.4.1_03]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_03-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-11-11.01-51 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/Releases/3.2.3RC1/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - 
nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Our connection to the Altavista BabelFish site has been cut. This service 
will remain down indefinitely until an alternate translation engine can be found. We 
apologize for any inconvenience. 
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=Default SSL context init failed: Algorithm SunX509 
not available
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 9-November-2003

2003-11-09 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 9-November-2003


JBoss daily test results

SUMMARY

Number of tests run:   1572



Successful tests:  1557

Errors:11

Failures:  4





[time of test: 2003-11-09.22-48 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-11-09.22-48 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Our connection to the Altavista BabelFish site has been cut. This service 
will remain down indefinitely until an alternate translation engine can be found. We 
apologize for any inconvenience. 
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-





[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 9-November-2003

2003-11-09 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 9-November-2003


JBoss daily test results

SUMMARY

Number of tests run:   1572



Successful tests:  1554

Errors:14

Failures:  4





[time of test: 2003-11-10.03-14 GMT]
[java.version: 1.3.1_09]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.3.1_09-b03]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-11-10.03-14 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Our connection to the Altavista BabelFish site has been cut. This service 
will remain down indefinitely until an alternate translation engine can be found. We 
apologize for any inconvenience. 
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=Default SSL context init failed: Algorithm SunX509 
not available
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 31-October-2003

2003-10-31 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 31-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1573



Successful tests:  1558

Errors:11

Failures:  4





[time of test: 2003-10-31.16-34 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-31.16-34 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Could not translate. Our connection to the babelfish site is expiencing 
difficulties 
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more 

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 31-October-2003

2003-10-31 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 31-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1551



Successful tests:  1521

Errors:24

Failures:  6





[time of test: 2003-10-31.18-32 GMT]
[java.version: 1.3.1_09]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.3.1_09-b03]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-31.18-32 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   CompleteUnitTestCase
Test:testEJBQL
Type:failure
Exception:   net.sourceforge.junitejb.RemoteAssertionFailedError
Message: expected:...0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER AND 
t6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND 
t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND 
t4_l.product=t6_l_product.id but 
was:...6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND 
t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND 
t4_l.product=t6_l_product.id AND t0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Could not translate. Our connection to the babelfish site is expiencing 
difficulties 
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   SRPLoginModuleUnitTestCase
Test:testSRPLogin
Type:error
Exception:   javax.security.auth.login.LoginException
Message: Failed to complete SRP login, msg=Unknown username: scott
-



Suite:   SRPLoginModuleUnitTestCase
Test:testSRPLoginHTTP
Type:error
Exception:   javax.security.auth.login.LoginException
Message: Failed to complete SRP login, msg=Unknown username: scott

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 25-October-2003

2003-10-25 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 25-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1552



Successful tests:  1525

Errors:23

Failures:  4





[time of test: 2003-10-25.11-51 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-25.11-51 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   BankStressTestCase
Test:unknown
Type:error
Exception:   junit.framework.AssertionFailedError
Message: Timeout occurred
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailNotSupportedReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   BaseConnectionManagerStressTestCase
Test:unknown
Type:error
Exception:   junit.framework.AssertionFailedError
Message: Timeout occurred
-



Suite:   CachedConnectionBankStressTestCase
Test:testCachedConnectionBank
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: null; CausedByException is:  Table not found: CCBMPCUSTOMER in 
statement [DROP TABLE CCBMPCUSTOMER]
-



Suite:   NamingStressTestCase
Test:testENCPerf
Type:error
Exception:   

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 24-October-2003

2003-10-24 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 24-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1541



Successful tests:  1510

Errors:26

Failures:  5





[time of test: 2003-10-24.07-48 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-24.07-48 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EnumUnitTestCase
Test:testColorEnum
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Method is not a known CMP field accessor, CMR field accessor, or 
ejbSelect method: methodName=setAnimal; CausedByException is:  Method is not a known 
CMP field accessor, CMR field accessor, or ejbSelect method: methodName=setAnimal; 
nested exception is:   javax.ejb.TransactionRolledbackLocalException: Method is not a 
known CMP field accessor, CMR field accessor, or ejbSelect method: 
methodName=setAnimal; CausedByException is:  Method is not a known CMP field accessor, 
CMR field accessor, or ejbSelect method: methodName=setAnimal
-



Suite:   EnumUnitTestCase
Test:testAnimalEnum
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Method is not a known CMP field accessor, CMR field accessor, or 
ejbSelect method: methodName=setAnimal; CausedByException is:  Method is not a known 
CMP field accessor, CMR field accessor, or ejbSelect method: methodName=setAnimal; 
nested exception is:   javax.ejb.TransactionRolledbackLocalException: Method is not a 
known CMP field accessor, CMR field accessor, or ejbSelect method: 
methodName=setAnimal; CausedByException is:  Method is not a known CMP field accessor, 
CMR field accessor, or ejbSelect method: methodName=setAnimal
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the 

[JBoss-dev] Automated JBoss(JBoss_3_2_2 WonderLand) Testsuite Results: 16-October-2003

2003-10-16 Thread noreply
Automated JBoss(JBoss_3_2_2 WonderLand) Testsuite Results: 16-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1562



Successful tests:  1548

Errors:10

Failures:  4





[time of test: 2003-10-16.03-53 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-16.03-53 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/Releases/3.2.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - 
nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:... ... but was:... ...
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
JBoss-Development mailing list
[EMAIL PROTECTED]

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 11-October-2003

2003-10-11 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 11-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1562



Successful tests:  1549

Errors:10

Failures:  3





[time of test: 2003-10-11.23-01 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-11.23-01 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 5-October-2003

2003-10-05 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 5-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1577



Successful tests:  1565

Errors:8

Failures:  4





[time of test: 2003-10-05.07-16 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-05.07-16 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:... ... but was:... ...
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 5-October-2003

2003-10-05 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 5-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1577



Successful tests:  1563

Errors:10

Failures:  4





[time of test: 2003-10-06.02-50 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-06.02-50 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   CustomSocketsUnitTestCase
Test:testCustomAccess
Type:error
Exception:   javax.naming.NameNotFoundException
Message: StatelessSession not bound
-



Suite:   CustomSocketsUnitTestCase
Test:testServerFound
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:failure
Exception:   junit.framework.ComparisonFailure
Message: got the translation right expected:... ... but was:... ...
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-October-2003

2003-10-03 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1569



Successful tests:  1556

Errors:10

Failures:  3





[time of test: 2003-10-03.12-50 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-03.12-50 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   CircularityUnitTestCase
Test:testLoading
Type:error
Exception:   javax.management.RuntimeMBeanException
Message: RuntimeException in MBean operation 'testLoading()'
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   JDBCStatementTestsConnectionUnitTestCase
Test:testJDBCStatementTestsConnection
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: RuntimeException; nested exception is:   
java.lang.ArrayIndexOutOfBoundsException: 1
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-October-2003

2003-10-03 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-October-2003


JBoss daily test results

SUMMARY

Number of tests run:   1569



Successful tests:  1556

Errors:10

Failures:  3





[time of test: 2003-10-03.12-50 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-10-03.12-50 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   CircularityUnitTestCase
Test:testLoading
Type:error
Exception:   javax.management.RuntimeMBeanException
Message: RuntimeException in MBean operation 'testLoading()'
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   JDBCStatementTestsConnectionUnitTestCase
Test:testJDBCStatementTestsConnection
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: RuntimeException; nested exception is:   
java.lang.ArrayIndexOutOfBoundsException: 1
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 30-September-2003

2003-09-30 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 30-September-2003


JBoss daily test results

SUMMARY

Number of tests run:   1564



Successful tests:  1549

Errors:12

Failures:  3





[time of test: 2003-09-30.16-59 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-09-30.16-59 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   AddrUnitTestCase
Test:testAddress
Type:error
Exception:   org.apache.axis.AxisFault
Message: The AXIS engine could not find a target service to invoke!  targetService 
is samples/AddressBook
-



Suite:   ExternalUnitTestCase
Test:testFederated
Type:error
Exception:   org.apache.axis.AxisFault
Message: Exception from service object: Invalid authorization key: wrong license
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   CMRStressTestCase
Test:testRelations
Type:error
Exception:   javax.ejb.FinderException
Message: Find failed: java.sql.SQLException: Table not found: STRESSEDPARENT in 
statement [SELECT id FROM STRESSEDPARENT WHERE id='arbitrary pk']
-



Suite:   CMRStressTestCase
Test:testServerFound
Type:error
Exception:   javax.ejb.CreateException
Message: Error checking if entity exists:java.sql.SQLException: Table not found: 
STRESSEDPARENT in statement [SELECT COUNT(*) FROM STRESSEDPARENT WHERE id='arbitrary 
pk']
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 28-September-2003

2003-09-28 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 28-September-2003


JBoss daily test results

SUMMARY

Number of tests run:   1529



Successful tests:  1498

Errors:28

Failures:  3





[time of test: 2003-09-28.05-51 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-09-28.05-51 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   LocalWrapperCleanupUnitTestCase
Test:testAutoCommitInReturnedConnection
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: Untested problem in test: javax.naming.NameNotFoundException: 
SingleConnectionDS not bound
-



Suite:   MBeanDependsOnConnectionManagerUnitTestCase
Test:testMBeanDependsOnConnectionManager
Type:error
Exception:   org.jboss.deployment.IncompleteDeploymentException
Message: 
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   BankStressTestCase
Test:testMultiThread
Type:error
Exception:   org.jboss.test.bank.interfaces.BankException
Message: Could not transfer -50.0 from bank/Account:5678.Marc.1064729434122 to 
bank/Account:5678.Rickard.1064729434123
-



Suite:   BankStressTestCase
Test:testMultiThread2
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: Load failed; CausedByException is:  Wrong data type: type: 
VARCHAR (12) expected: BINARY value: 5678.Rickard.1064729434123
-



Suite:   BankStressTestCase
Test:testTransaction
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in 

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 28-September-2003

2003-09-28 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 28-September-2003


JBoss daily test results

SUMMARY

Number of tests run:   1531



Successful tests:  1520

Errors:8

Failures:  3





[time of test: 2003-09-28.21-10 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-09-28.21-10 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(JBoss_3_2_2_RC4 WonderLand) Testsuite Results: 18-September-2003

2003-09-19 Thread noreply
Automated JBoss(JBoss_3_2_2_RC4 WonderLand) Testsuite Results: 18-September-2003


JBoss daily test results

SUMMARY

Number of tests run:   1506



Successful tests:  1492

Errors:9

Failures:  5





[time of test: 2003-09-19.01-54 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-09-19.01-54 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   DeployServiceUnitTestCase
Test:testSpaceInClasspath
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/Releases/3.2.2RC4/jboss-3.2/testsuite/output/lib/archivestest-service.xml; - 
nested throwable: (java.io.FileNotFoundException: 
/Releases/3.2.2RC4/jboss-3.2/testsuite/output/lib)
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/Releases/3.2.2RC4/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - 
nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFail
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailCMR
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 17-September-2003

2003-09-17 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 17-September-2003


JBoss daily test results

SUMMARY

Number of tests run:   1505



Successful tests:  1491

Errors:8

Failures:  6





[time of test: 2003-09-18.01-30 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-09-18.01-30 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested 
throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   ImplUnitTestCase
Test:testEncPerf
Type:error
Exception:   javax.naming.NameNotFoundException
Message: comp not bound
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL
Type:error
Exception:   java.io.IOException
Message: Failed to readURL, ex=null
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFail
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailCMR
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 10-September-2003

2003-09-10 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 10-September-2003


JBoss daily test results

SUMMARY

Number of tests run:   1501



Successful tests:  1488

Errors:6

Failures:  7





[time of test: 2003-09-10.18-41 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-09-10.18-41 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   CircularityUnitTestCase
Test:testLoading
Type:error
Exception:   javax.management.RuntimeMBeanException
Message: RuntimeException in MBean operation 'testLoading()'
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml;
 - nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFail
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailCMR
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Bad attribute(MessageCache) is not a JSR77 type
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-September-2003

2003-09-06 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-September-2003


JBoss daily test results

SUMMARY

Number of tests run:   1500



Successful tests:  1488

Errors:5

Failures:  7





[time of test: 2003-09-07.03-54 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-09-07.03-54 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   RollBackUnitTestCase
Test:testAsynchDurableTopicReceiveRollBack
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Topic should be full
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml;
 - nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailCMR
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Bad attribute(MessageCache) is not a JSR77 type
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 4-September-2003

2003-09-04 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 4-September-2003


JBoss daily test results

SUMMARY

Number of tests run:   1500



Successful tests:  1488

Errors:6

Failures:  6





[time of test: 2003-09-04.20-26 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-09-04.20-26 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   CircularityUnitTestCase
Test:testLoading
Type:error
Exception:   javax.management.RuntimeMBeanException
Message: RuntimeException in MBean operation 'testLoading()'
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml;
 - nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailReentrant
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   BeanStressTestCase
Test:testAllCompleteOrFailCMR
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Unexpected exception
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Bad attribute(MessageCache) is not a JSR77 type
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(JBoss_3_2_2_RC3 WonderLand) Testsuite Results: 24-August-2003

2003-08-24 Thread noreply
Automated JBoss(JBoss_3_2_2_RC3 WonderLand) Testsuite Results: 24-August-2003


JBoss daily test results

SUMMARY

Number of tests run:   1498



Successful tests:  1488

Errors:5

Failures:  5





[time of test: 2003-08-24.20-45 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-08-24.20-45 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/Releases/3.2.2RC3/jboss-3.2/testsuite/output/lib/missingclass-service.xml;
 - nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   WebIntegrationUnitTestCase
Test:testUnsecureRunAsServlet
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Expected reply code:200, actual=500
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Bad attribute(MessageCache) is not a JSR77 type
-




---
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-August-2003

2003-08-14 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-August-2003


JBoss daily test results

SUMMARY

Number of tests run:   1473



Successful tests:  1462

Errors:7

Failures:  4





[time of test: 2003-08-06.13-51 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-08-06.13-51 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   ScopingUnitTestCase
Test:testWarOverrides
Type:error
Exception:   java.io.FileNotFoundException
Message: http://localhost:8080/log4j113/ENCServlet/
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   RollBackUnitTestCase
Test:testAsynchDurableTopicReceiveRollBack
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Topic should be full
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml;
 - nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 9-August-2003

2003-08-09 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 9-August-2003


JBoss daily test results

SUMMARY

Number of tests run:   1479



Successful tests:  1469

Errors:7

Failures:  3





[time of test: 2003-08-09.20-26 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-08-09.20-26 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   ScopingUnitTestCase
Test:testWarOverrides
Type:error
Exception:   java.io.FileNotFoundException
Message: http://localhost:8080/log4j113/ENCServlet/
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml;
 - nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SimpleUnitTestCase
Test:testNameChanges
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: name.equals(copy), name=jmx
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 4-August-2003

2003-08-04 Thread noreply
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 4-August-2003


JBoss daily test results

SUMMARY

Number of tests run:   1468



Successful tests:  1459

Errors:7

Failures:  2





[time of test: 2003-08-05.00-28 GMT]
[java.version: 1.4.2]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.2-b28]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.20-9smp]

Useful resources:

- http://jboss.sourceforge.net//junit-results/32/2003-08-05.00-28 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   ScopingUnitTestCase
Test:testWarOverrides
Type:error
Exception:   java.io.FileNotFoundException
Message: http://localhost:8080/log4j113/ENCServlet/
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   EntityExceptionUnitTestCase
Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local
Type:error
Exception:   net.sourceforge.junitejb.RemoteTestException
Message: Error, bean instance was discarded!
-



Suite:   MissingClassUnitTestCase
Test:testDeployServiceWithoutClass
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/home/starksm/JBoss/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml;
 - nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   JSR77SpecUnitTestCase
Test:testNotificationDeliver
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Not enough notifications received: 0
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-




---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 8-February-2003

2003-02-08 Thread noreply


JBoss daily test results

SUMMARY

Number of tests run:   1024



Successful tests:  1020

Errors:4

Failures:  0





[time of test: 2003-02-07.23-35 GMT]
[java.version: 1.4.1_01]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_01-b01]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.18-19.8.0]

See http://users.jboss.org/~starksm/Branch_3_0/2003-02-07.23-35
for details of this test. 

NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   UnackedUnitTestCase
Test:testUnackedTopic(org.jboss.test.jbossmq.test.UnackedUnitTestCase)
Type:error
Exception:   java.lang.InternalError
Message: Test timeout
-



Suite:   LocalWrapperCleanupUnitTestCase
Test:
testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase)
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: Row committed, autocommit still on!
-



Suite:   MissingClassUnitTestCase
Test:
testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: 
(javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not 
registered.)
-



Suite:   EJBSpecUnitTestCase
Test:testMDBRunAs(org.jboss.test.security.test.EJBSpecUnitTestCase)
Type:error
Exception:   java.lang.NullPointerException
Message: 
-




---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 4-February-2003

2003-02-04 Thread noreply


JBoss daily test results

SUMMARY

Number of tests run:   1024



Successful tests:  1019

Errors:5

Failures:  0





[time of test: 2003-02-04.09-00 GMT]
[java.version: 1.3.1_07]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.3.1_07-b02]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.18-14]

See http://users.jboss.org/~starksm/Branch_3_0/2003-02-04.09-00
for details of this test. 

NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   UnackedUnitTestCase
Test:testUnackedTopic(org.jboss.test.jbossmq.test.UnackedUnitTestCase)
Type:error
Exception:   java.lang.InternalError
Message: Test timeout
-



Suite:   LocalWrapperCleanupUnitTestCase
Test:
testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase)
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: Row committed, autocommit still on!
-



Suite:   MissingClassUnitTestCase
Test:
testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: 
(javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not 
registered.)
-



Suite:   SimpleUnitTestCase
Test:testHaParitionName(org.jboss.test.naming.test.SimpleUnitTestCase)
Type:error
Exception:   javax.naming.CommunicationException
Message: Receive timed out
-



Suite:   EJBSpecUnitTestCase
Test:testMDBRunAs(org.jboss.test.security.test.EJBSpecUnitTestCase)
Type:error
Exception:   java.lang.NullPointerException
Message: 
-




---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 30-January-2003

2003-01-30 Thread noreply


JBoss daily test results

SUMMARY

Number of tests run:   1024



Successful tests:  1019

Errors:5

Failures:  0





[time of test: 2003-01-30.15-01 GMT]
[java.version: 1.4.1_01]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_01-b01]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.18-14]

See http://users.jboss.org/~starksm/Branch_3_0/2003-01-30.15-01
for details of this test. 

NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   UnackedUnitTestCase
Test:testUnackedTopic(org.jboss.test.jbossmq.test.UnackedUnitTestCase)
Type:error
Exception:   java.lang.InternalError
Message: Test timeout
-



Suite:   LocalWrapperCleanupUnitTestCase
Test:
testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase)
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: Row committed, autocommit still on!
-



Suite:   MissingClassUnitTestCase
Test:
testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: 
(javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not 
registered.)
-



Suite:   SimpleUnitTestCase
Test:testHaParitionName(org.jboss.test.naming.test.SimpleUnitTestCase)
Type:error
Exception:   javax.naming.CommunicationException
Message: Receive timed out
-



Suite:   EJBSpecUnitTestCase
Test:testMDBRunAs(org.jboss.test.security.test.EJBSpecUnitTestCase)
Type:error
Exception:   java.lang.NullPointerException
Message: 
-




---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-661335 ] JBoss links ejbs to tables in wrong tablespace

2003-01-02 Thread noreply
Bugs item #661335, was opened at 2003-01-02 16:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=661335group_id=22866

Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBoss links ejbs to tables in wrong tablespace

Initial Comment:
JBoss 3.0.2
Oracle8.1.7

I have 2 oracle users:
user1 has 3 tables in it's default tablespace called A, B 
and C (which i created with one version of the 
deployment).

ok, so i add another datasource pointing at the same db 
with user2 as the login. It has it's own tablespace and 
cannot write to user1's tablespace.

I then have a deployment (another set of apps) that 
deploys 5 enity beans that point at tables A, B, C, D 
and E. I'm reusing A, B and C.

When I deploy, JBoss creates tables D and E in user2's 
tablespace, but does not create table A, B or C.

Then when i try to use the beans and write to bean/table 
A, JBoss blows up. with this error: 
java.sql.SQLException: ORA-00942: table or view does 
not exist

I'm thinking that something is not quite write with the 
code that creates the tables, in specific the code that 
determines if it should create the table.


If we create public synanins to user1's tables, then 
everything works fine, but this is not what i would like. I 
would like new tables created in user2's tablespace.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=661335group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-661335 ] JBoss links ejbs to tables in wrong tablespace

2003-01-02 Thread noreply
Bugs item #661335, was opened at 2003-01-02 14:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=661335group_id=22866

Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBoss links ejbs to tables in wrong tablespace

Initial Comment:
JBoss 3.0.2
Oracle8.1.7

I have 2 oracle users:
user1 has 3 tables in it's default tablespace called A, B 
and C (which i created with one version of the 
deployment).

ok, so i add another datasource pointing at the same db 
with user2 as the login. It has it's own tablespace and 
cannot write to user1's tablespace.

I then have a deployment (another set of apps) that 
deploys 5 enity beans that point at tables A, B, C, D 
and E. I'm reusing A, B and C.

When I deploy, JBoss creates tables D and E in user2's 
tablespace, but does not create table A, B or C.

Then when i try to use the beans and write to bean/table 
A, JBoss blows up. with this error: 
java.sql.SQLException: ORA-00942: table or view does 
not exist

I'm thinking that something is not quite write with the 
code that creates the tables, in specific the code that 
determines if it should create the table.


If we create public synanins to user1's tables, then 
everything works fine, but this is not what i would like. I 
would like new tables created in user2's tablespace.

--

Comment By: Jeremy Boynes (jboynes)
Date: 2003-01-02 16:21

Message:
Logged In: YES 
user_id=378919

This happens because user2 has access to user1's tables even
though they are in a different schema. This is probably due
to an explicit grant or because user2 has the
select_any_table role (e.g. it is a DBA account). As a
result a row is returned by getTables(catalog, null,
tableName) making JBoss believe the table exists.

JBoss can't handle this conflict without knowledge on how
partial identifiers (e.g. A) are resolved by the
underlying database. Oracle's rules here are quite different
to a database e.g. SQLServer that uses the full
catalog.schema.object convention. This makes a general
solution complex and means resolution probably has to wait
for database pluggability.

In the mean time, I would highly recommend reducing the
roles granted to your user2 account - granting just
connect,resource (or better, more specific rights) will work
around this problem and eliminate a lot of the potential
security risks. Alternatively, creating the tables
explicitly (which a DBA would typically do, especially in
production, right?) and turning off automatic create-table
would work.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=661335group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Patches-660670 ] Fix for wrong constants in Duration

2003-01-01 Thread noreply
Patches item #660670, was opened at 2003-01-01 14:33
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376687aid=660670group_id=22866

Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Frank Langelage (lafr)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix for wrong constants in Duration

Initial Comment:
The duration for startup of jboss-head is calculated
wrong due to wrong values for some time-constants in
Duration.java.
ONE_MINUTE is to big by factor 10.
Others are to small by factor 10.
See the diff attached.



--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376687aid=660670group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Change Notes-660839 ] HTTP URL scanning support

2003-01-01 Thread noreply
Change Notes item #660839, was opened at 2003-01-01 14:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=381174aid=660839group_id=22866

Category: JBoss/System
Group: v3.2
Status: Open
Priority: 5
Submitted By: Jeremy Boynes (jboynes)
Assigned to: Nobody/Anonymous (nobody)
Summary: HTTP URL scanning support

Initial Comment:
Support has been added for scanning HTTP locations
using the WebDAV protocol. This allows locations to be
scanned when the server has been netbooted from a web
server in the same manner as local directories are
scanned. This allows JBoss to be booted from an
unmodified configuration located on a WebDAV capable
server such as Tomcat 4.1.X, Apache 2.0 with mod_dav or
even Microsoft IIS. Alternatively, a trival DAV server
is supplied in docs/examples/netboot that allows JBoss
to be booted from any J2EE WebContainer such as JBossWeb.

DAV scanning is supported for the SARDeployer
classpath element and for the URLDeploymentScanner
urls element. The latter requires locations to be
specified in accordance with RFC2518 - basically URLs
will be scanned if they end with a '/' character and
deployed if they do not. See the standard
conf/jboss-service.xml for examples.

With this change URLDeploymentScanner is now able to
provide the functionality of URLDirectoryScanner and
HttpURLDeploymentScanner and these mbeans should no
longer be used.

A current limitation is that locations to be scanned
via HTTP/DAV must not contain unpacked archives
(especially SAR or WAR archives). This limitation may
be removed in the future.

Also WAR archives should contain in their lib or
classes directories all classes needed to compile JSP
pages. Strictly, the javac compiler invoked during JSP
compilation uses a classpath derived from ClassLoaders
referencing the local filesystem; as a result
dependencies on classes loaded over the network may
result in cannot resolve symbol errors during JSP
compilation.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=381174aid=660839group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-660405 ] ServiceController.create( ObjectName, Collectio

2002-12-31 Thread noreply
Bugs item #660405, was opened at 2002-12-31 15:41
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Corby (corby)
Assigned to: Nobody/Anonymous (nobody)
Summary: ServiceController.create( ObjectName, Collectio

Initial Comment:
 SHORT VERSION: If I set my user MBeans to be 
dependent on the LocalTxConnectionManager, I can no 
longer successfully recycle my connection pool.

LONG VERSION: (I am running JBoss 3.0.4, JDK 
1.4.1_01, Win2K)

I am using an MBean configuration file, sybase-
service.xml, which is laid out almost identically to the 
hsqldb-service.xml file. It contains a LocalTxCM MBean, 
which is dependent on a LocalTxDS MBean and a 
LocalTXPool MBean.

Normally, if I touch sybase-service.xml everything works 
great. ServiceController.install() is called with 
LocalTxCM, LocalTxDS, and LocalTxPool. 
ServiceController.create() is called with LocalTxCM, but 
it waits because the iDependOn beans haven't been 
created yet. After LocalTxPool is created, we iterate 
through the dependsOnMe mbeans and the LocalTxCM 
MBean is created. All is good.

But if I introduce my own MBeans that are dependent on 
the database connection pool, then the 
ServiceController.create() method behaves differently. I 
use the following tag in my user MBeans:

dependsjboss.jca:service=LocalTxCM,name=sybaseD
S/depends

Now I can start the JBoss server just fine. But if I 
recycle the connection pool, here is what happens:

ServiceController.install() is called just as before. The 
ServiceContexts for all three MBeans look fine. In 
particular, the iDependOn and the dependsOnMe lists 
are correct, and my userMBeans have been added to 
the dependsOnMe list for LocalTxCM.

When ServiceController.create() method is called on 
LocalTxCM, it defers again. When 
ServiceController.create() is called on the other two 
MBeans, it seems to succeed. The create() methods 
are successfully executed on these MBeans.

Thanks to dependsOnMe, ServiceController.create() is 
called on LocalTxCM again. But now when we get the 
ServiceContexts in the iDependOn list for LocalTxCM, 
they are all defined as state: NOTYETINSTALLED. So 
LocalTxCM still fails to create because it believes its 
dependent MBeans have not yet been created.

This leads to the predictable log message:

ERROR [URLDeploymentScanner] MBeanException: 
Exception in MBean 
operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
none
Incompletely deployed packages:
none
MBeans waiting for classes:
none
MBeans waiting for other MBeans:
...
ObjectName: 
jboss.jca:service=LocalTxCM,name=sybaseDS
state: CONFIGURED
I Depend On: 
jboss.jca:service=LocalTxDS,name=sybaseDS
jboss.jca:service=LocalTxPool,name=sybaseDS
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
jboss.jca:service=RARDeployer
jboss.jca:service=LocalTxDS,name=sybaseDS
jboss.jca:service=LocalTxPool,name=sybaseDS

Depends On Me: (My User MBeans)


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-660405 ] ServiceController.create( ObjectName, Collectio

2002-12-31 Thread noreply
Bugs item #660405, was opened at 2002-12-31 15:41
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Corby (corby)
Assigned to: David Jencks (d_jencks)
Summary: ServiceController.create( ObjectName, Collectio

Initial Comment:
 SHORT VERSION: If I set my user MBeans to be 
dependent on the LocalTxConnectionManager, I can no 
longer successfully recycle my connection pool.

LONG VERSION: (I am running JBoss 3.0.4, JDK 
1.4.1_01, Win2K)

I am using an MBean configuration file, sybase-
service.xml, which is laid out almost identically to the 
hsqldb-service.xml file. It contains a LocalTxCM MBean, 
which is dependent on a LocalTxDS MBean and a 
LocalTXPool MBean.

Normally, if I touch sybase-service.xml everything works 
great. ServiceController.install() is called with 
LocalTxCM, LocalTxDS, and LocalTxPool. 
ServiceController.create() is called with LocalTxCM, but 
it waits because the iDependOn beans haven't been 
created yet. After LocalTxPool is created, we iterate 
through the dependsOnMe mbeans and the LocalTxCM 
MBean is created. All is good.

But if I introduce my own MBeans that are dependent on 
the database connection pool, then the 
ServiceController.create() method behaves differently. I 
use the following tag in my user MBeans:

dependsjboss.jca:service=LocalTxCM,name=sybaseD
S/depends

Now I can start the JBoss server just fine. But if I 
recycle the connection pool, here is what happens:

ServiceController.install() is called just as before. The 
ServiceContexts for all three MBeans look fine. In 
particular, the iDependOn and the dependsOnMe lists 
are correct, and my userMBeans have been added to 
the dependsOnMe list for LocalTxCM.

When ServiceController.create() method is called on 
LocalTxCM, it defers again. When 
ServiceController.create() is called on the other two 
MBeans, it seems to succeed. The create() methods 
are successfully executed on these MBeans.

Thanks to dependsOnMe, ServiceController.create() is 
called on LocalTxCM again. But now when we get the 
ServiceContexts in the iDependOn list for LocalTxCM, 
they are all defined as state: NOTYETINSTALLED. So 
LocalTxCM still fails to create because it believes its 
dependent MBeans have not yet been created.

This leads to the predictable log message:

ERROR [URLDeploymentScanner] MBeanException: 
Exception in MBean 
operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
none
Incompletely deployed packages:
none
MBeans waiting for classes:
none
MBeans waiting for other MBeans:
...
ObjectName: 
jboss.jca:service=LocalTxCM,name=sybaseDS
state: CONFIGURED
I Depend On: 
jboss.jca:service=LocalTxDS,name=sybaseDS
jboss.jca:service=LocalTxPool,name=sybaseDS
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
jboss.jca:service=RARDeployer
jboss.jca:service=LocalTxDS,name=sybaseDS
jboss.jca:service=LocalTxPool,name=sybaseDS

Depends On Me: (My User MBeans)


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-660405 ] ServiceController.create( ObjectName, Collectio

2002-12-31 Thread noreply
Bugs item #660405, was opened at 2002-12-31 15:41
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Corby (corby)
Assigned to: David Jencks (d_jencks)
Summary: ServiceController.create( ObjectName, Collectio

Initial Comment:
 SHORT VERSION: If I set my user MBeans to be 
dependent on the LocalTxConnectionManager, I can no 
longer successfully recycle my connection pool.

LONG VERSION: (I am running JBoss 3.0.4, JDK 
1.4.1_01, Win2K)

I am using an MBean configuration file, sybase-
service.xml, which is laid out almost identically to the 
hsqldb-service.xml file. It contains a LocalTxCM MBean, 
which is dependent on a LocalTxDS MBean and a 
LocalTXPool MBean.

Normally, if I touch sybase-service.xml everything works 
great. ServiceController.install() is called with 
LocalTxCM, LocalTxDS, and LocalTxPool. 
ServiceController.create() is called with LocalTxCM, but 
it waits because the iDependOn beans haven't been 
created yet. After LocalTxPool is created, we iterate 
through the dependsOnMe mbeans and the LocalTxCM 
MBean is created. All is good.

But if I introduce my own MBeans that are dependent on 
the database connection pool, then the 
ServiceController.create() method behaves differently. I 
use the following tag in my user MBeans:

dependsjboss.jca:service=LocalTxCM,name=sybaseD
S/depends

Now I can start the JBoss server just fine. But if I 
recycle the connection pool, here is what happens:

ServiceController.install() is called just as before. The 
ServiceContexts for all three MBeans look fine. In 
particular, the iDependOn and the dependsOnMe lists 
are correct, and my userMBeans have been added to 
the dependsOnMe list for LocalTxCM.

When ServiceController.create() method is called on 
LocalTxCM, it defers again. When 
ServiceController.create() is called on the other two 
MBeans, it seems to succeed. The create() methods 
are successfully executed on these MBeans.

Thanks to dependsOnMe, ServiceController.create() is 
called on LocalTxCM again. But now when we get the 
ServiceContexts in the iDependOn list for LocalTxCM, 
they are all defined as state: NOTYETINSTALLED. So 
LocalTxCM still fails to create because it believes its 
dependent MBeans have not yet been created.

This leads to the predictable log message:

ERROR [URLDeploymentScanner] MBeanException: 
Exception in MBean 
operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
none
Incompletely deployed packages:
none
MBeans waiting for classes:
none
MBeans waiting for other MBeans:
...
ObjectName: 
jboss.jca:service=LocalTxCM,name=sybaseDS
state: CONFIGURED
I Depend On: 
jboss.jca:service=LocalTxDS,name=sybaseDS
jboss.jca:service=LocalTxPool,name=sybaseDS
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
jboss.jca:service=RARDeployer
jboss.jca:service=LocalTxDS,name=sybaseDS
jboss.jca:service=LocalTxPool,name=sybaseDS

Depends On Me: (My User MBeans)


--

Comment By: Corby (corby)
Date: 2002-12-31 21:03

Message:
Logged In: YES 
user_id=25032

The attached files comprise a test case which illustrates the 
bug

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=660405group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-659897 ] SecurityException not being thrown?

2002-12-29 Thread noreply
Bugs item #659897, was opened at 2002-12-30 01:31
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659897group_id=22866

Category: JBossSX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Brian Topping (topping)
Assigned to: Nobody/Anonymous (nobody)
Summary: SecurityException not being thrown?

Initial Comment:
Environment:

Client is W2K SP3, JDK 1.4.1_01, client libs copied 
from server.

Server is SuSE 8.1, JDK 1.4.1_01, JBoss 3.2.0B3.

Deploying a client on the same VM as the server works 
properly, splitting them across the network does not.  
I'm used to seeing a SecurityException thrown when the 
client is not logged in and tries to access a protected 
resource, it does not seem to throw on 3.2B3.  Instead, I 
get a MarshalException or UnmarshalException 
(changes between them over successive runs) with an 
underlying SocketException.  

I figured this out from looking at the network packet 
traces, it looks like it is pushing the exception over the 
wire, but the client is out of sync or otherwise treating 
the exception data as the object data, which is then 
throwing the UnmarshalException because the stream 
is mismatched.  I can provide whatever additional 
information is necessary on this.

Many thanks, as always...

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659897group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-659152 ] Classloading Problem with JavaMail

2002-12-28 Thread noreply
Bugs item #659152, was opened at 2002-12-27 13:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659152group_id=22866

Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas (hunterhillegas)
Assigned to: Scott M Stark (starksm)
Summary: Classloading Problem with JavaMail

Initial Comment:
MacOS X 10.2.3
Apple Java 1.4.1 DP8

When trying to use JavaMail in a Web application, I got
the following exception:

13:13:58,967 WARN  [jbossweb] WARNING: Error for
/vagrant/vagrantController?action=sendFriendEmail
java.lang.LinkageError: Class javax/mail/Transport
violates loader constraints
at java.lang.ClassLoader.defineClass0(Native
Method)
at
java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at
org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:444)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:250)
at
org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:187)
at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:119)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at
javax.mail.Session.getTransport(Session.java:685)
at
javax.mail.Session.getTransport(Session.java:628)
at
javax.mail.Session.getTransport(Session.java:608)
at
javax.mail.Session.getTransport(Session.java:663)
at javax.mail.Transport.send0(Transport.java:154)
at javax.mail.Transport.send(Transport.java:80)
at
com.liberationmedia.beans.EmailBean.init(Unknown Source)
at vagrantController.sendFriendEmail(Unknown
Source)
at vagrantController.doPost(Unknown Source)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:272)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:550)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1655)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:542)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1605)
at
org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:202)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)


Here is the class loader trace:

[193546,UnifiedClassLoader3,PoolThread-4] released,
holds: 0
[193549,UnifiedClassLoader3,PoolThread-4] attempt(1)
was: true for
:org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server
/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrder=2}
[193549,LoadMgr,PoolThread-4] registerLoaderThread,
ucl=org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/con
f/jboss-service.xml/1.jboss-service.xml ,addedOrder=2},
t=PoolThread-4, prevT=null
[193549,LoadMgr,PoolThread-4] Begin beginLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:
javax.mail.internet.UniqueValue, requestingThread:
PoolThread-4, requestingClassLo
ader: org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrde
r=2}, loadedClass: null, loadOrder: 2147483647,
loadException: null, threadTaskCount: 0, state: 0}
[193551,LoadMgr,PoolThread-4] End beginLoadTask,
loadClassFromClassLoader
[193552,LoadMgr,PoolThread-4] Begin endLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:

[JBoss-dev] [ jboss-Bugs-659152 ] Classloading Problem with JavaMail

2002-12-28 Thread noreply
Bugs item #659152, was opened at 2002-12-27 13:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659152group_id=22866

Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas (hunterhillegas)
Assigned to: Scott M Stark (starksm)
Summary: Classloading Problem with JavaMail

Initial Comment:
MacOS X 10.2.3
Apple Java 1.4.1 DP8

When trying to use JavaMail in a Web application, I got
the following exception:

13:13:58,967 WARN  [jbossweb] WARNING: Error for
/vagrant/vagrantController?action=sendFriendEmail
java.lang.LinkageError: Class javax/mail/Transport
violates loader constraints
at java.lang.ClassLoader.defineClass0(Native
Method)
at
java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at
org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:444)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:250)
at
org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:187)
at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:119)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at
javax.mail.Session.getTransport(Session.java:685)
at
javax.mail.Session.getTransport(Session.java:628)
at
javax.mail.Session.getTransport(Session.java:608)
at
javax.mail.Session.getTransport(Session.java:663)
at javax.mail.Transport.send0(Transport.java:154)
at javax.mail.Transport.send(Transport.java:80)
at
com.liberationmedia.beans.EmailBean.init(Unknown Source)
at vagrantController.sendFriendEmail(Unknown
Source)
at vagrantController.doPost(Unknown Source)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:272)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:550)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1655)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:542)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1605)
at
org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:202)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)


Here is the class loader trace:

[193546,UnifiedClassLoader3,PoolThread-4] released,
holds: 0
[193549,UnifiedClassLoader3,PoolThread-4] attempt(1)
was: true for
:org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server
/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrder=2}
[193549,LoadMgr,PoolThread-4] registerLoaderThread,
ucl=org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/con
f/jboss-service.xml/1.jboss-service.xml ,addedOrder=2},
t=PoolThread-4, prevT=null
[193549,LoadMgr,PoolThread-4] Begin beginLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:
javax.mail.internet.UniqueValue, requestingThread:
PoolThread-4, requestingClassLo
ader: org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrde
r=2}, loadedClass: null, loadOrder: 2147483647,
loadException: null, threadTaskCount: 0, state: 0}
[193551,LoadMgr,PoolThread-4] End beginLoadTask,
loadClassFromClassLoader
[193552,LoadMgr,PoolThread-4] Begin endLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:

[JBoss-dev] [ jboss-Bugs-659152 ] Classloading Problem with JavaMail

2002-12-28 Thread noreply
Bugs item #659152, was opened at 2002-12-27 21:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659152group_id=22866

Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas (hunterhillegas)
Assigned to: Scott M Stark (starksm)
Summary: Classloading Problem with JavaMail

Initial Comment:
MacOS X 10.2.3
Apple Java 1.4.1 DP8

When trying to use JavaMail in a Web application, I got
the following exception:

13:13:58,967 WARN  [jbossweb] WARNING: Error for
/vagrant/vagrantController?action=sendFriendEmail
java.lang.LinkageError: Class javax/mail/Transport
violates loader constraints
at java.lang.ClassLoader.defineClass0(Native
Method)
at
java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at
org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:444)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:250)
at
org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:187)
at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:119)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at
javax.mail.Session.getTransport(Session.java:685)
at
javax.mail.Session.getTransport(Session.java:628)
at
javax.mail.Session.getTransport(Session.java:608)
at
javax.mail.Session.getTransport(Session.java:663)
at javax.mail.Transport.send0(Transport.java:154)
at javax.mail.Transport.send(Transport.java:80)
at
com.liberationmedia.beans.EmailBean.init(Unknown Source)
at vagrantController.sendFriendEmail(Unknown
Source)
at vagrantController.doPost(Unknown Source)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:272)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:550)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1655)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:542)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1605)
at
org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:202)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)


Here is the class loader trace:

[193546,UnifiedClassLoader3,PoolThread-4] released,
holds: 0
[193549,UnifiedClassLoader3,PoolThread-4] attempt(1)
was: true for
:org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server
/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrder=2}
[193549,LoadMgr,PoolThread-4] registerLoaderThread,
ucl=org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/con
f/jboss-service.xml/1.jboss-service.xml ,addedOrder=2},
t=PoolThread-4, prevT=null
[193549,LoadMgr,PoolThread-4] Begin beginLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:
javax.mail.internet.UniqueValue, requestingThread:
PoolThread-4, requestingClassLo
ader: org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrde
r=2}, loadedClass: null, loadOrder: 2147483647,
loadException: null, threadTaskCount: 0, state: 0}
[193551,LoadMgr,PoolThread-4] End beginLoadTask,
loadClassFromClassLoader
[193552,LoadMgr,PoolThread-4] Begin endLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:

[JBoss-dev] [ jboss-Bugs-659152 ] Classloading Problem with JavaMail

2002-12-27 Thread noreply
Bugs item #659152, was opened at 2002-12-27 21:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659152group_id=22866

Category: None
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas (hunterhillegas)
Assigned to: Nobody/Anonymous (nobody)
Summary: Classloading Problem with JavaMail

Initial Comment:
MacOS X 10.2.3
Apple Java 1.4.1 DP8

When trying to use JavaMail in a Web application, I got
the following exception:

13:13:58,967 WARN  [jbossweb] WARNING: Error for
/vagrant/vagrantController?action=sendFriendEmail
java.lang.LinkageError: Class javax/mail/Transport
violates loader constraints
at java.lang.ClassLoader.defineClass0(Native
Method)
at
java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at
org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:444)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:250)
at
org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:187)
at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:119)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at
javax.mail.Session.getTransport(Session.java:685)
at
javax.mail.Session.getTransport(Session.java:628)
at
javax.mail.Session.getTransport(Session.java:608)
at
javax.mail.Session.getTransport(Session.java:663)
at javax.mail.Transport.send0(Transport.java:154)
at javax.mail.Transport.send(Transport.java:80)
at
com.liberationmedia.beans.EmailBean.init(Unknown Source)
at vagrantController.sendFriendEmail(Unknown
Source)
at vagrantController.doPost(Unknown Source)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:272)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:550)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1655)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:542)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1605)
at
org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:202)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)


Here is the class loader trace:

[193546,UnifiedClassLoader3,PoolThread-4] released,
holds: 0
[193549,UnifiedClassLoader3,PoolThread-4] attempt(1)
was: true for
:org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server
/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrder=2}
[193549,LoadMgr,PoolThread-4] registerLoaderThread,
ucl=org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/con
f/jboss-service.xml/1.jboss-service.xml ,addedOrder=2},
t=PoolThread-4, prevT=null
[193549,LoadMgr,PoolThread-4] Begin beginLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:
javax.mail.internet.UniqueValue, requestingThread:
PoolThread-4, requestingClassLo
ader: org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrde
r=2}, loadedClass: null, loadOrder: 2147483647,
loadException: null, threadTaskCount: 0, state: 0}
[193551,LoadMgr,PoolThread-4] End beginLoadTask,
loadClassFromClassLoader
[193552,LoadMgr,PoolThread-4] Begin endLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:

[JBoss-dev] [ jboss-Bugs-659152 ] Classloading Problem with JavaMail

2002-12-27 Thread noreply
Bugs item #659152, was opened at 2002-12-27 13:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659152group_id=22866

Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas (hunterhillegas)
Assigned to: Scott M Stark (starksm)
Summary: Classloading Problem with JavaMail

Initial Comment:
MacOS X 10.2.3
Apple Java 1.4.1 DP8

When trying to use JavaMail in a Web application, I got
the following exception:

13:13:58,967 WARN  [jbossweb] WARNING: Error for
/vagrant/vagrantController?action=sendFriendEmail
java.lang.LinkageError: Class javax/mail/Transport
violates loader constraints
at java.lang.ClassLoader.defineClass0(Native
Method)
at
java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at
org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:444)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:250)
at
org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:187)
at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:119)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at
javax.mail.Session.getTransport(Session.java:685)
at
javax.mail.Session.getTransport(Session.java:628)
at
javax.mail.Session.getTransport(Session.java:608)
at
javax.mail.Session.getTransport(Session.java:663)
at javax.mail.Transport.send0(Transport.java:154)
at javax.mail.Transport.send(Transport.java:80)
at
com.liberationmedia.beans.EmailBean.init(Unknown Source)
at vagrantController.sendFriendEmail(Unknown
Source)
at vagrantController.doPost(Unknown Source)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:272)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:550)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1655)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:542)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1605)
at
org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:202)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)


Here is the class loader trace:

[193546,UnifiedClassLoader3,PoolThread-4] released,
holds: 0
[193549,UnifiedClassLoader3,PoolThread-4] attempt(1)
was: true for
:org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server
/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrder=2}
[193549,LoadMgr,PoolThread-4] registerLoaderThread,
ucl=org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/con
f/jboss-service.xml/1.jboss-service.xml ,addedOrder=2},
t=PoolThread-4, prevT=null
[193549,LoadMgr,PoolThread-4] Begin beginLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:
javax.mail.internet.UniqueValue, requestingThread:
PoolThread-4, requestingClassLo
ader: org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrde
r=2}, loadedClass: null, loadOrder: 2147483647,
loadException: null, threadTaskCount: 0, state: 0}
[193551,LoadMgr,PoolThread-4] End beginLoadTask,
loadClassFromClassLoader
[193552,LoadMgr,PoolThread-4] Begin endLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:

[JBoss-dev] [ jboss-Bugs-626484 ] Incorrect libraries classpath?

2002-12-27 Thread noreply
Bugs item #626484, was opened at 2002-10-21 20:58
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=626484group_id=22866

Category: Build System
Group: CVS HEAD
Status: Closed
Resolution: None
Priority: 5
Submitted By: ycswyw (ycswyw)
Assigned to: Jason Dillon (user57)
Summary: Incorrect libraries classpath?

Initial Comment:
In CVS of jboss4.0.0alpha, thirdparty libraries are
structured as ${project.thirdparty}/vendor/product,
but in
jboss-all/tools/etc/buildfragments/libraries.ent are
referenced as ${project.thirdparty}/vendor-product.

The attached file is a replacement of libraries.ent,
to fix the problem.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=626484group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-659152 ] Classloading Problem with JavaMail

2002-12-27 Thread noreply
Bugs item #659152, was opened at 2002-12-27 21:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659152group_id=22866

Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas (hunterhillegas)
Assigned to: Scott M Stark (starksm)
Summary: Classloading Problem with JavaMail

Initial Comment:
MacOS X 10.2.3
Apple Java 1.4.1 DP8

When trying to use JavaMail in a Web application, I got
the following exception:

13:13:58,967 WARN  [jbossweb] WARNING: Error for
/vagrant/vagrantController?action=sendFriendEmail
java.lang.LinkageError: Class javax/mail/Transport
violates loader constraints
at java.lang.ClassLoader.defineClass0(Native
Method)
at
java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at
org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:444)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:250)
at
org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:187)
at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:119)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at
javax.mail.Session.getTransport(Session.java:685)
at
javax.mail.Session.getTransport(Session.java:628)
at
javax.mail.Session.getTransport(Session.java:608)
at
javax.mail.Session.getTransport(Session.java:663)
at javax.mail.Transport.send0(Transport.java:154)
at javax.mail.Transport.send(Transport.java:80)
at
com.liberationmedia.beans.EmailBean.init(Unknown Source)
at vagrantController.sendFriendEmail(Unknown
Source)
at vagrantController.doPost(Unknown Source)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:272)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:550)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1655)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:542)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1605)
at
org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:202)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)


Here is the class loader trace:

[193546,UnifiedClassLoader3,PoolThread-4] released,
holds: 0
[193549,UnifiedClassLoader3,PoolThread-4] attempt(1)
was: true for
:org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server
/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrder=2}
[193549,LoadMgr,PoolThread-4] registerLoaderThread,
ucl=org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/con
f/jboss-service.xml/1.jboss-service.xml ,addedOrder=2},
t=PoolThread-4, prevT=null
[193549,LoadMgr,PoolThread-4] Begin beginLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:
javax.mail.internet.UniqueValue, requestingThread:
PoolThread-4, requestingClassLo
ader: org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrde
r=2}, loadedClass: null, loadOrder: 2147483647,
loadException: null, threadTaskCount: 0, state: 0}
[193551,LoadMgr,PoolThread-4] End beginLoadTask,
loadClassFromClassLoader
[193552,LoadMgr,PoolThread-4] Begin endLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:

[JBoss-dev] [ jboss-Bugs-659152 ] Classloading Problem with JavaMail

2002-12-27 Thread noreply
Bugs item #659152, was opened at 2002-12-27 13:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659152group_id=22866

Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas (hunterhillegas)
Assigned to: Scott M Stark (starksm)
Summary: Classloading Problem with JavaMail

Initial Comment:
MacOS X 10.2.3
Apple Java 1.4.1 DP8

When trying to use JavaMail in a Web application, I got
the following exception:

13:13:58,967 WARN  [jbossweb] WARNING: Error for
/vagrant/vagrantController?action=sendFriendEmail
java.lang.LinkageError: Class javax/mail/Transport
violates loader constraints
at java.lang.ClassLoader.defineClass0(Native
Method)
at
java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at
org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:444)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:250)
at
org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:187)
at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:119)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at
javax.mail.Session.getTransport(Session.java:685)
at
javax.mail.Session.getTransport(Session.java:628)
at
javax.mail.Session.getTransport(Session.java:608)
at
javax.mail.Session.getTransport(Session.java:663)
at javax.mail.Transport.send0(Transport.java:154)
at javax.mail.Transport.send(Transport.java:80)
at
com.liberationmedia.beans.EmailBean.init(Unknown Source)
at vagrantController.sendFriendEmail(Unknown
Source)
at vagrantController.doPost(Unknown Source)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:272)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:550)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1655)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:542)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1605)
at
org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:202)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)


Here is the class loader trace:

[193546,UnifiedClassLoader3,PoolThread-4] released,
holds: 0
[193549,UnifiedClassLoader3,PoolThread-4] attempt(1)
was: true for
:org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server
/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrder=2}
[193549,LoadMgr,PoolThread-4] registerLoaderThread,
ucl=org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/con
f/jboss-service.xml/1.jboss-service.xml ,addedOrder=2},
t=PoolThread-4, prevT=null
[193549,LoadMgr,PoolThread-4] Begin beginLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:
javax.mail.internet.UniqueValue, requestingThread:
PoolThread-4, requestingClassLo
ader: org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrde
r=2}, loadedClass: null, loadOrder: 2147483647,
loadException: null, threadTaskCount: 0, state: 0}
[193551,LoadMgr,PoolThread-4] End beginLoadTask,
loadClassFromClassLoader
[193552,LoadMgr,PoolThread-4] Begin endLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:

[JBoss-dev] [ jboss-Bugs-659152 ] Classloading Problem with JavaMail

2002-12-27 Thread noreply
Bugs item #659152, was opened at 2002-12-27 21:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=659152group_id=22866

Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Hunter Hillegas (hunterhillegas)
Assigned to: Scott M Stark (starksm)
Summary: Classloading Problem with JavaMail

Initial Comment:
MacOS X 10.2.3
Apple Java 1.4.1 DP8

When trying to use JavaMail in a Web application, I got
the following exception:

13:13:58,967 WARN  [jbossweb] WARNING: Error for
/vagrant/vagrantController?action=sendFriendEmail
java.lang.LinkageError: Class javax/mail/Transport
violates loader constraints
at java.lang.ClassLoader.defineClass0(Native
Method)
at
java.lang.ClassLoader.defineClass(ClassLoader.java:502)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at
java.net.URLClassLoader.defineClass(URLClassLoader.java:250)
at
java.net.URLClassLoader.access$100(URLClassLoader.java:54)
at
java.net.URLClassLoader$1.run(URLClassLoader.java:193)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at
org.jboss.mx.loading.UnifiedClassLoader.findClass(UnifiedClassLoader.java:444)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassLocally(UnifiedClassLoader.java:250)
at
org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:187)
at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:119)
at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:161)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at
javax.mail.Session.getTransport(Session.java:685)
at
javax.mail.Session.getTransport(Session.java:628)
at
javax.mail.Session.getTransport(Session.java:608)
at
javax.mail.Session.getTransport(Session.java:663)
at javax.mail.Transport.send0(Transport.java:154)
at javax.mail.Transport.send(Transport.java:80)
at
com.liberationmedia.beans.EmailBean.init(Unknown Source)
at vagrantController.sendFriendEmail(Unknown
Source)
at vagrantController.doPost(Unknown Source)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:272)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:550)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1655)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:542)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1605)
at
org.mortbay.http.HttpServer.service(HttpServer.java:862)
at org.jboss.jetty.Jetty.service(Jetty.java:497)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:752)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:769)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:202)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)


Here is the class loader trace:

[193546,UnifiedClassLoader3,PoolThread-4] released,
holds: 0
[193549,UnifiedClassLoader3,PoolThread-4] attempt(1)
was: true for
:org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server
/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrder=2}
[193549,LoadMgr,PoolThread-4] registerLoaderThread,
ucl=org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/con
f/jboss-service.xml/1.jboss-service.xml ,addedOrder=2},
t=PoolThread-4, prevT=null
[193549,LoadMgr,PoolThread-4] Begin beginLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:
javax.mail.internet.UniqueValue, requestingThread:
PoolThread-4, requestingClassLo
ader: org.jboss.mx.loading.UnifiedClassLoader3@d61ee4{
url=file:/Users/hunter/Unix/jboss-3.2.0beta3/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml
,addedOrde
r=2}, loadedClass: null, loadOrder: 2147483647,
loadException: null, threadTaskCount: 0, state: 0}
[193551,LoadMgr,PoolThread-4] End beginLoadTask,
loadClassFromClassLoader
[193552,LoadMgr,PoolThread-4] Begin endLoadTask,
task=org.jboss.mx.loading.ClassLoadingTask@7433e7{classname:

[JBoss-dev] [ jboss-Change Notes-658609 ] Optimistic locking support

2002-12-26 Thread noreply
Change Notes item #658609, was opened at 2002-12-26 10:46
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=381174aid=658609group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Priority: 5
Submitted By: Alexey Loubyansky (loubyansky)
Assigned to: Nobody/Anonymous (nobody)
Summary: Optimistic locking support

Initial Comment:
To setup optimistic locking, container configuration 
element locking-policy should be set to
locking-
policyorg.jboss.ejb.plugins.lock.JDBCOptimisticLock/l
ocking-policy
and entity element in jbosscmp-jdbc.xml should have 
optimistic-locking element.

Following are the possible configurations of optimistic-
locking element:
1. Fixed group of fields that will be used for optimistic 
locking.
   optimistic-locking
  group-nameoptimisticLockingGroup/group-
name
   /optimistic-locking
where optimisticLockingGroup is one of the entity's load-
group-name's.

2. Modified strategy. The fields that were modified during 
transaction will be used for optimistic locking.
   optimistic-locking
  modified-strategy/
   /optimistic-locking

3. Read strategy. The fields that were read during 
transaction will be used for optimistic locking.
   optimistic-locking
  read-strategy/
   /optimistic-locking

4. Version (counter) column strategy. Additional version 
(counter) field of type java.lang.Long will be added to 
entity which 

will be used for optimistic locking. Each update of the 
entity will increase the value of its version field by 1.
   optimistic-locking
  version-column/
  field-nameversionField/field-name
  column-nameol_version/column-name
  jdbc-typeINTEGER/jdbc-type
  sql-typeINTEGER(5)/sql-type
   /optimistic-locking

5. Timestamp column strategy. Additional timestamp 
column field of type java.util.Date will be added to entity 
which will be 

used for optimistic locking. Each update of the entity will 
set the value of its timestamp field to the current time.
   optimistic-locking
  timestamp-column/
  field-nametimestampField/field-name
  column-nameol_timestamp/column-name
  jdbc-typeTIMESTAMP/jdbc-type
  sql-typeDATETIME/sql-type
   /optimistic-locking

6. Version column generated by KeyGenerator. 
Additional field will be added to entity that will be used 
for optimistic 

locking. Each update of the entity will update its version 
column with value generated by KeyGenerator.
   optimistic-locking
  key-generator-
factoryUUIDKeyGeneratorFactory/key-generator-
factory
  field-typejava.lang.String/field-type
  field-nameuuidField/field-name
  column-nameol_uuid/column-name
  jdbc-typeVARCHAR/jdbc-type
  sql-typeVARCHAR(32)/sql-type
   /optimistic-locking


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=381174aid=658609group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-658711 ] Error on MDB message receiving

2002-12-26 Thread noreply
Bugs item #658711, was opened at 2002-12-26 17:15
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658711group_id=22866

Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: viccos (viccos)
Assigned to: Nobody/Anonymous (nobody)
Summary: Error on MDB message receiving

Initial Comment:
OS: WINDOWS 2000
JDK 1.3.0

The stack trace is the following:

16:42:10,948 ERROR [STDERR] java.lang.NoSuchMethodError
16:42:10,948 ERROR [STDERR] at
org.jboss.jms.asf.StdServerSession.onMessage(StdServerSessio
n.java:293)
16:42:10,948 ERROR [STDERR] at
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessag
e(SpyMessageConsumer.java:603)
16:42:10,968 ERROR [STDERR] at
org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsume
r.java:417)
16:42:10,978 ERROR [STDERR] at
org.jboss.mq.SpySession.run(SpySession.java:296)
16:42:10,988 ERROR [STDERR] at
org.jboss.jms.asf.StdServerSession.run(StdServerSession.java
:178)
16:42:11,018 ERROR [STDERR] at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(P
ooledExecutor.java:642)
16:42:11,028 ERROR [STDERR] at
java.lang.Thread.run(Thread.java:484)

This error happens when a message is rceiver by the
MDB. The MDB has CMP and has been simplified to show
only a message through standard output.

Comments:
I tried to call the method end of class XAResource
using reflection inside StdServerSession and it doesn´t
work, obtaining the same result. But listing the
methods of this class it is shown

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658711group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-658224 ] ut.rollback may not work after sqlexcept

2002-12-24 Thread noreply
Bugs item #658224, was opened at 2002-12-24 15:03
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658224group_id=22866

Category: JBossCX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: David Jencks (d_jencks)
Assigned to: David Jencks (d_jencks)
Summary: ut.rollback may not work after sqlexcept

Initial Comment:
Problem found with jboss 3.0.2, following code snippet may not 
result in actual rollback even if ut.rollback called.  Reordering code 
to close connection in finally block before commit/rollback 
reported to fix the problem.  See forum thread http://
www.jboss.org/forums/thread.jsp?forum=136thread=26437

public RuleVO insert(RuleVO rule) {
UserTransaction ut = context.getUserTransaction();

DAOFactory daoFactory = DAOFactory.getDAOFactory();
Connection conn = null;

RuleVO savedRule = new RuleVO();
try {
ut.begin();
try {
conn = daoFactory.getConnection();
} catch (IllegalArgumentException ex) {
throw new EJBException(
Could not establish database connection:  + ex.getMessage());
}
savedRule = daoFactory.getRuleDAO().insert(conn, rule);
ut.commit();
} catch (SQLException e) {
try {
ut.rollback();
} catch (SystemException syex) {
throw new EJBException
(Rule insert  rollback failed:  + syex.getMessage());
}
throw new EJBException
(Rule insert failed:  + e.getMessage());
} catch (Exception ex) {
throw new EJBException
(Rule insert begin/commit transaction failed:  + 
ex.getMessage());
} finally {
try {
DAOFactory.closeConnection(conn);
} catch (SQLException ex) {
throw new EJBException(
Could not close database connection:  + ex.getMessage());
}
return savedRule;
}
}


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658224group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Change Notes-658296 ] FK fields mapped to PK fields support

2002-12-24 Thread noreply
Change Notes item #658296, was opened at 2002-12-24 21:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=381174aid=658296group_id=22866

Category: JBossCMP
Group: v3.2
Status: Open
Priority: 5
Submitted By: Alexey Loubyansky (loubyansky)
Assigned to: Nobody/Anonymous (nobody)
Summary: FK fields mapped to PK fields support

Initial Comment:
It's possible to map foreign key fields in one-to-many 
and one-to-one relationships to primary key fields. All is 
needed to assign the same names to the corresponding 
foreign and primary key fields.

Relationships are assigned between ejbCreate and 
ejbPostCreate. This means that relationships are 
accessible in ejbPostCreate and not in ejbCreate.
Relationships are established and removed only with 
creation and removal of entities. Modifications with 
abstract CMR accessors are not allowed as they 
change primary key values.

If ONE side doesn't exist CMR on the MANY side will 
return null value.
If MANY side doesn't exist CMR on the ONE side will 
return empty collection.

If cascade-delete is specified then removal of the ONE 
side will remove the related MANY side. In this case, 
ONE side is removed first breaking the relationship, i.e. 
CMR field on the MANY side in ejbRemove will return 
null.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=381174aid=658296group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-657837 ] IllegalAccessException - after redeploy

2002-12-23 Thread noreply
Bugs item #657837, was opened at 2002-12-23 08:26
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=657837group_id=22866

Category: JBossServer
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Eyal Lupu (eyall)
Assigned to: Nobody/Anonymous (nobody)
Summary: IllegalAccessException - after redeploy

Initial Comment:
OS: W2K
JDK: 1.4.1
JBoss 3.0.4

We have an application build of 1 ear including:
-5 EJB jars
-2 WARs
-1 SAR
- and 10 library jars (/library/xxx.jar)


There are no duplicate classes.

After redeployment we start to get 
IllegalAccessException when accessing package 
protected method. If no redeployment has taken place
everything works fine.

We suspect that classes has more than one instance.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=657837group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-658042 ] High contention in jboss/naming

2002-12-23 Thread noreply
Bugs item #658042, was opened at 2002-12-23 15:42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658042group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Stefan Reich (sreich)
Assigned to: Nobody/Anonymous (nobody)
Summary: High contention in jboss/naming

Initial Comment:
While running ECperf Scott and I discovered high
contention in two classes of the JNDI naming
implementation of JBoss:

1) org.jboss.naming.ENCFactory calls a native method
(Thread.currentThread) while holding a lock, which is
very expensive in most vms. Fix: moved the call out of
the synchronized bloc.

2) org.jnp.interfaces.NamingParser has a static
Properties instance that holds JNDI read-only
properties. In the tests we saw as many as 30% of all
threads waiting to acquire the lock for the Hashtable,
from which java.util.Properties extends. The
synchronization is unnecessary, since the static
instance is read-only after its allocation.
Fix: wrote a custom class that extends
java.util.Properties overriding all methods to get rid
of unwanted locking and ensure read-only semantics.

Both fixes result in an increase of about factor three
in ECperf BBops on a Dual 500MHz PowerMac and have been
tested for a week on Jboss 3.0.5RC1.

Diff attached.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658042group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Change Notes-658052 ] XDoclet built in JBoss

2002-12-23 Thread noreply
Change Notes item #658052, was opened at 2002-12-24 00:22
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=381174aid=658052group_id=22866

Category: Build System
Group: v4.0
Status: Open
Priority: 5
Submitted By: David Jencks (d_jencks)
Assigned to: David Jencks (d_jencks)
Summary: XDoclet built in JBoss

Initial Comment:
I've  addded an xdoclet module to jboss 4 (head) that
builds xdoclet from
source from the xdoclet cvs tree.  To minize
disruption, please read!

You can avoid requiring a fresh jboss checkout by
executing in jboss-head

cvs get _jboss_xdoclet


WARNING you may have to run build/build.sh twice, see
Issues. I am
investigating this.

HOW IT WORkS---

The first time you build jboss, xdoclet source is
checked out into a
directory checkout by the xdoclet/build.xml ant script.
 The cvs properties
are set in the xdoclet.cvs.properties file.  After
successful checkout and
build, flag files are created xdoclet.last.checkout and
xdoclet.last.build.
 As long as the checkout folder remains, and these
files are not touched,
xdoclet will not be rebuilt.  On my machines building
xdoclet takes about
the same amount of time as building jboss.

The xdoclet build is supplied with some properties so
it builds into
xdoclet/output/lib.  The libraries.ent file is modified
to use xdoclet from
here.  If all goes well I will remove the xdoclet copy
from thirdparty in a
day or two.

if you want to modify xdoclet, remove the
xdoclet.last.build file and your
modifications will be compiled the next time you build
jboss.

CHANGES WITH THIS VERSION OF XDOCLET---

--The main change is that xdoclet no longer copies over
all the imports
from your source  class to generated interfaces,
instead fully  qualifying
all class names in the generated interfaces.

WARNING!!!  THIS REQUIRES YOU TO EXPLICITLY IMPORT
EVERY CLASS IN EVERY
JAVA FILE XDOCLET LOOKS AT!!  NO import x.y.x.*;!

If you import a package.*, xdoclet may find a class
referenced in a file in
which it is not explicitly imported and decide the
class is unknown and
therefore to be generated in the current package, and
not fully qualify
the name in ANY file it generates.  This can be
extremely confusing since
the effects are in a file totally unrelated to the file
with the package
import, and there is no obvious warning of where the
problem came from. I'm
looking for a way to at least provide a more obvious
warning for this.


--xmbean operations require you to list the
managed-parameters with  the
correct types.  While a nuisance, this at least
encourages you to comment
them.

--xmbean display-names can be specified, and they
display in the
jmx-console.

-

Issues:

--currently xdoclet head is checked out.  After I make
sure this works a
little more and fix a couple of xdoclet problems I will
tag xdoclet source
so we have a more stable checkout.

--On some machines it appears that the first build will
not be able to find
the just-compiled xdoclet jars.  Running build/build.sh
again seems to find
them.  (I thought it worked on apple 1.4.1, but a fresh
checkout on linux
sun 1.3.1 fails on the first build).  I'm looking at this.

--

Next steps:

put the jboss xdoclet module into jboss cvs and build
it with the rest of
xdoclet.

provide instructions for xdoclet committers to work
with a live copy of
xdoclet in jboss.

Thanks
david jencks


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=381174aid=658052group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-658060 ] Several locking problems in connectors

2002-12-23 Thread noreply
Bugs item #658060, was opened at 2002-12-23 17:03
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658060group_id=22866

Category: JBossCX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Stefan Reich (sreich)
Assigned to: Nobody/Anonymous (nobody)
Summary: Several locking problems in connectors

Initial Comment:
While browsing the 3.0.5RC1 source I discovered several
places with inconsistent locking:

*
org/jboss/resource/adapter/jdbc/local/LocalManagedConnection:
field cels is locked on this in
add/removeConnectionEventListener, but locked on cels
in closeHandle and connectionError.
The field handles is accessed w/o a lock in
getConnection()

*
org/jboss/resource/connectionmanager/BaseConnectionManager2
The fields handleCount and handles are accessed w/o
holding the lock on this in isManagedConnectionFree()
and unregisterConnections()

*
main/org/jboss/resource/connectionmanager/InternalManagedConnectionPool
exception gets logged at the wrong level in
returnConnection()

*
org/jboss/resource/connectionmanager/JBossManagedConnectionPool
All methods iterating over the pools field must lock
to avoid ConcurrentModificationExceptions or otherwise
inconsistent state.

Diffs attached.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658060group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-658042 ] High contention in jboss/naming

2002-12-23 Thread noreply
Bugs item #658042, was opened at 2002-12-23 15:42
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658042group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Stefan Reich (sreich)
Assigned to: Scott M Stark (starksm)
Summary: High contention in jboss/naming

Initial Comment:
While running ECperf Scott and I discovered high
contention in two classes of the JNDI naming
implementation of JBoss:

1) org.jboss.naming.ENCFactory calls a native method
(Thread.currentThread) while holding a lock, which is
very expensive in most vms. Fix: moved the call out of
the synchronized bloc.

2) org.jnp.interfaces.NamingParser has a static
Properties instance that holds JNDI read-only
properties. In the tests we saw as many as 30% of all
threads waiting to acquire the lock for the Hashtable,
from which java.util.Properties extends. The
synchronization is unnecessary, since the static
instance is read-only after its allocation.
Fix: wrote a custom class that extends
java.util.Properties overriding all methods to get rid
of unwanted locking and ensure read-only semantics.

Both fixes result in an increase of about factor three
in ECperf BBops on a Dual 500MHz PowerMac and have been
tested for a week on Jboss 3.0.5RC1.

Diff attached.

--

Comment By: Scott M Stark (starksm)
Date: 2002-12-23 17:07

Message:
Logged In: YES 
user_id=175228

Integrated into 3.0+

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658042group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-658060 ] Several locking problems in connectors

2002-12-23 Thread noreply
Bugs item #658060, was opened at 2002-12-24 01:03
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658060group_id=22866

Category: JBossCX
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Stefan Reich (sreich)
Assigned to: David Jencks (d_jencks)
Summary: Several locking problems in connectors

Initial Comment:
While browsing the 3.0.5RC1 source I discovered several
places with inconsistent locking:

*
org/jboss/resource/adapter/jdbc/local/LocalManagedConnection:
field cels is locked on this in
add/removeConnectionEventListener, but locked on cels
in closeHandle and connectionError.
The field handles is accessed w/o a lock in
getConnection()

*
org/jboss/resource/connectionmanager/BaseConnectionManager2
The fields handleCount and handles are accessed w/o
holding the lock on this in isManagedConnectionFree()
and unregisterConnections()

*
main/org/jboss/resource/connectionmanager/InternalManagedConnectionPool
exception gets logged at the wrong level in
returnConnection()

*
org/jboss/resource/connectionmanager/JBossManagedConnectionPool
All methods iterating over the pools field must lock
to avoid ConcurrentModificationExceptions or otherwise
inconsistent state.

Diffs attached.


--

Comment By: David Jencks (d_jencks)
Date: 2002-12-24 05:05

Message:
Logged In: YES 
user_id=60525

Thanks very much. I've applied these to 3.0, 3.2, and 4 with the 
following exception:

I retained the non-synchronized collections in LocalManagedConnection 
and applied explicit synchronization.  According to the discussion of 
locks and memory in the Java Virtual Machine Specification section 8.6 
(more or less copied from the Java  Language Spec), every lock/unlock 
operation requires synchronizing a threads local memore with main 
memory, not just the outermost lock/unlock.  Using explicit 
synchronization everywhere avoids this double memory synch when 
iterating through the collection.  I also find it clearer to show al the 
synchronization explicitly.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658060group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-658134 ] JaasSecurityDomain NPE

2002-12-23 Thread noreply
Bugs item #658134, was opened at 2002-12-23 23:47
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658134group_id=22866

Category: JBossSX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Scott M Stark (starksm)
Summary: JaasSecurityDomain NPE

Initial Comment:
A bug was introduced in 3.0.4 that disallows a 
JaasSecurityDomain from functioning as an 
AuthenticationManager due to NPEs because the 
authentication cache is not being set. This is due to the 
JaasSecurityManager no longer creating a default 
cache. The JaasSecurityManagerService now will set 
the authentication cache for security managers that 
register via the registerSecurityDomain op.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658134group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-658134 ] JaasSecurityDomain NPE

2002-12-23 Thread noreply
Bugs item #658134, was opened at 2002-12-23 23:47
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658134group_id=22866

Category: JBossSX
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Scott M Stark (starksm)
Summary: JaasSecurityDomain NPE

Initial Comment:
A bug was introduced in 3.0.4 that disallows a 
JaasSecurityDomain from functioning as an 
AuthenticationManager due to NPEs because the 
authentication cache is not being set. This is due to the 
JaasSecurityManager no longer creating a default 
cache. The JaasSecurityManagerService now will set 
the authentication cache for security managers that 
register via the registerSecurityDomain op.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=658134group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-644289 ] ClassLoader issue with protected access and manifest refs

2002-12-23 Thread noreply
Bugs item #644289, was opened at 2002-11-26 11:10
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=644289group_id=22866

Category: JBossMX
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Scott M Stark (starksm)
Summary: ClassLoader issue with protected access and manifest refs

Initial Comment:
When package protected access is used with classes 
that are loaded by more than one classloader via 
manifest Class-Path references you can get 
IllegalAccessErrors when more than one jar references 
the jar containing the classes due to the use of a UCL 
per jar. This has been reported in various forms in bugs 
565701, 606359, 641740 and is consolidated here with 
a trival testcase that demonstrates the problem.

The 
org.jboss.test.classloader.test.CircularityUnitTestCase 
testPackageProtected unit test demonstrates the 
problem with a repository that contains a login.jar and a 
usrmgr.jar, both of which reference a cl-util.jar. The 
contents of the jars is:

login.jar
+- 
org/jboss/test/classloader/circularity/support/UserOfLogi
nInfo.class
+- META-INF/MANIFEST.MF Class-Path: cl-util.jar
usrmgr.jar
+- 
org/jboss/test/classloader/circularity/support/UserOfUsr
Mgr.class
+- META-INF/MANIFEST.MF Class-Path: cl-util.jar
cl-util.jar
+- 
org/jboss/test/classloader/circularity/support/LoginInfo.cl
ass
+- 
org/jboss/test/classloader/circularity/support/UsrMgr.cla
ss
+- META-INF/MANIFEST.MF

The test first loads the UserOfLoginInfo class using the 
UCL associated with login.jar, and then loads the 
UserOfUsrMgr class using the UCL associated with 
usrmgr.jar. A changePassword method is then invoked 
on an instance of UserOfUsrMgr and this results in an 
IllegalAccessError because the LoginInfo class was 
seen to be loaded from the UCL associated with 
login.jar while the UsMgr class was loaded from the 
UCL associated with usrmgr.jar. Although both are in 
the same package and jar, two different class loaders 
are involved and so the access check fails.

The only workaround at the moment requires moving the 
common jar to the server/xxx/lib directory so that the 
UCLs do not see common jar as part of their classes.


--

Comment By: Scott M Stark (starksm)
Date: 2002-12-23 23:48

Message:
Logged In: YES 
user_id=175228

This has been fixed in the 3.0 and 3.2 branches.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=644289group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-634990 ] Problem with MBeans loading by MLET

2002-12-21 Thread noreply
Bugs item #634990, was opened at 2002-11-07 16:24
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=634990group_id=22866

Category: JBossMX
Group: None
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Yuriy Khabarov (thundcat)
Assigned to: Adrian Brock (ejort)
Summary: Problem with MBeans loading by MLET

Initial Comment:
JBoss 3.0.2

java.lang.ClassCastException in:

file \jboss-
all\jmx\src\main\javax\management\loading\MLet.java

   public Class loadClass(String name, boolean resolve) 
throws ClassNotFoundException

Looks like

 UnifiedLoaderRepository ulr = 
(UnifiedLoaderRepository)
LoaderRepository.getDefaultLoaderRepository();
 return ulr.loadClass(name, resolve, 
Thread.currentThread().getContextClassLoader());

should be changed to 

 LoaderRepository ulr = 
LoaderRepository.getDefaultLoaderRepository();
 return ulr.loadClass(name, resolve, 
Thread.currentThread().getContextClassLoader());

Because of 
ServerConstants.UNIFIED_LOADER_REPOSITORY_CL
ASS and System.getProperty
(ServerConstants.LOADER_REPOSITORY_CLASS_PR
OPERTY)
equals
org.jboss.mx.loading.UnifiedLoaderRepository2
not 
org.jboss.mx.loading.UnifiedLoaderRepository

if I'm wrong please reply. Thank you

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=634990group_id=22866


---
This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
Time is running out!  Thinkgeek.com has the coolest gifts for
your favorite geek.   Let your fingers do the typing.   Visit Now.
T H I N K G E E K . C O Mhttp://www.thinkgeek.com/sf/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-657311 ] Resource Contention - Leaking Handles

2002-12-21 Thread noreply
Bugs item #657311, was opened at 2002-12-21 16:16
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=657311group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Dennis Cartier (dcartier)
Assigned to: Nobody/Anonymous (nobody)
Summary: Resource Contention - Leaking Handles

Initial Comment:
I have noticed some odd files appearing in the /tmp
directory of my Linux JBoss machines. They are all
named ddtbX.tmp

Eg.
ddtb48340.tmp ddtb48349.tmp ddtb48358.tmp ddtb48367.tmp ...

When I check the output of lsof, it appears that close
to all of the java processes running each have every
one of the ddtb files open. This quickly adds up to
thousands of open files. Each one of the ddtb files are
0 bytes long, so there is not even anything in them.

I have tried deleting them while JBoss reamins running,
no ill effects were observed, but lsof still shows the
java process having them open even after they are gone.

It appears to be only under load that the files are
created. Idle servers do not seem to generate these files.

I am just worried that over a period of time, this will
cause the JBoss servers to eventually fail. Can anyone
shed any light on this?

Particulars:
JBoss 3.0.4 Tomcat 4.1.12
Debian Stable Linux
Kernel 2.4.19
Sun 1.4.0_02 JVM

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=657311group_id=22866


---
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players,  XBox Games,  Flying Saucers,  WebCams,  Smart Putty.
T H I N K G E E K . C O M   http://www.thinkgeek.com/sf/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-647648 ] IllegalAccessException w/ 3.2 Beta 2

2002-12-20 Thread noreply
Bugs item #647648, was opened at 2002-12-02 23:50
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=647648group_id=22866

Category: JBossMX
Group: v3.2
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Dorothy Gantenbein (dgantenbein)
Assigned to: Scott M Stark (starksm)
Summary: IllegalAccessException w/ 3.2 Beta 2

Initial Comment:
We are working on upgrading from 3.2Beta1 to 
3.2Beta2.  Our automated test suites triggers the 
IllegalAcessException errors which did not occur with 
Beta1.

Our environment is Windows XP, JBoss 3.2Beta2, Sun 
JDK 1.4.0_01-b03.

I cannot give you a small test case but attached is the 
UCL.log. 

If you need me to try any bug fixes or any other info, 
please feel free to contact me at 
[EMAIL PROTECTED]

Thanks...
Dorothy

--

Comment By: Scott M Stark (starksm)
Date: 2002-12-20 13:15

Message:
Logged In: YES 
user_id=175228

The two classes in question are TaskQueueRequestAction 
and TaskItem as TaskQueueRequestAction is calling the 
package private TaskItem.activate. The ucl.log shows that 
TaskQueueRequestAction was loaded by the class loader 
associated with infra.ear/infra.sar while TaskItem was loaded 
by the class loader associated with infra.ear/infra-client.jar. 
I'm putting out a fix for this for testing in a beta3 release of 
3.2.0 today.

--

Comment By: Dorothy Gantenbein (dgantenbein)
Date: 2002-12-16 22:55

Message:
Logged In: YES 
user_id=328249

Ran a new test run to generate a new ucl1.zip.  The main 
class is com.informative.infra.enterprise.event.TaskItem.  The 
test class is 
com.informative.infra.enterprise.event.TaskItemTest.

Here is the top of the error stacktrace.

java.lang.IllegalAccessError: try to access method 
com.informative.infra.enterprise.event.TaskItem.activate()V 
from class 
com.informative.infra.enterprise.event.TaskQueueRequestActi
on
at 
com.informative.infra.enterprise.event.TaskQueueRequestActi
on.run(TaskQueueRequestAction.java:27)
at 
com.informative.infra.enterprise.event.ReplicatedCacheManag
er$SyncAction.run(ReplicatedCacheManager.java:232)
at 
com.informative.infra.enterprise.event.ReplicatedCacheManag
er.runSynchronizedTask(ReplicatedCacheManager.java:177)
at 
com.informative.infra.enterprise.event.TaskQueueData.request
NextTask(TaskQueueData.java:95)
at 
com.informative.infra.enterprise.event.TaskQueue.requestNext
Task(TaskQueue.java:79)
at 
com.informative.infra.enterprise.event.TaskItemTest.testActiva
tedCompleted(TaskItemTest.java:84)

--

Comment By: Scott M Stark (starksm)
Date: 2002-12-16 14:14

Message:
Logged In: YES 
user_id=175228

This looks to be essentially a duplicate of the 3.0 bug 
644289. IllegalAccessExceptions don't show up in the ucl.log 
so what are the two classes in this particular example that 
correspond to Foo and FooTest?

--

Comment By: Dorothy Gantenbein (dgantenbein)
Date: 2002-12-05 16:20

Message:
Logged In: YES 
user_id=328249

After more experimentation, the problem occurs referencing a 
protected method from the same package but from a different 
source directory.

Assume the following directory structure.

src/com/informative/Foo.java
test/com/informative/FooTest.java

Both, Foo and FooTest are in the same package.  The class, 
Foo, has a protected method 'doSomething'.  When FooTest 
invokes 'Foo.doSomething'.  The IllegalAccessException 
occurs.  Changing 'Foo.doSomething' works around the 
problem.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=647648group_id=22866


---
This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
Time is running out!  Thinkgeek.com has the coolest gifts for
your favorite geek.   Let your fingers do the typing.   Visit Now.
T H I N K G E E K . C O Mhttp://www.thinkgeek.com/sf/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Patches-656231 ] BigInteger is recognized as BigDecimal

2002-12-19 Thread noreply
Patches item #656231, was opened at 2002-12-19 11:00
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376687aid=656231group_id=22866

Category: JBossCMP
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Raymond (rpbrandon)
Assigned to: Nobody/Anonymous (nobody)
Summary: BigInteger is recognized as BigDecimal

Initial Comment:
JBoss recognizes a BigInteger as BigDecimal in 
JDBCCommand.java and reports error Got a 
java.math.BigDecimal: '###' while looking 
for a java.math.BigInteger. This has been reproduced 
this with v3.0.3 and v3.0.4 both with EJB1.1 and EJB2.0.

An application stores a row in to a table and then 
retrieves the data. The table looks like this:

CREATE TABLE X (
id VARCHAR (40) NOT NULL,
bigDecimalType DECIMAL (18, 4) NOT NULL,
bigIntegerType DECIMAL (18) NOT NULL,
PRIMARY KEY (id)
);

JBoss debug output:

2002-12-17 14:35:31,543 DEBUG 
[org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand] Create 
command executing: INSERT INTO 
BigNumbersMandatory 
(bigDecimalType,bigIntegerType,id) VALUES (?,?,?)
2002-12-17 14:35:31,543 DEBUG 
[org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand] Set 
parameter: idx=1, jdbcType=DECIMAL, value=10
2002-12-17 14:35:31,543 DEBUG 
[org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand] Set 
parameter: idx=2, jdbcType=DECIMAL, value=100
2002-12-17 14:35:31,543 DEBUG 
[org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand] Set 
parameter: idx=3, jdbcType=VARCHAR, value=Piet
2002-12-17 14:35:31,558 DEBUG 
[org.jboss.ejb.plugins.jaws.jdbc.JDBCUpdateCommand] 
Rows affected = 1
2002-12-17 14:35:31,574 TRACE [EjbTier] 
BigNumbersMandatoryBean.ejbPostCreate
(BigNumbersMandatoryUpdate update)
2002-12-17 14:35:31,590 TRACE [EjbTier] 
BigNumbersMandatoryBean.ejbStore(): key=id(Piet)
2002-12-17 14:35:31,590 DEBUG 
[org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand] Load 
command executing: SELECT 
BigNumbersMandatory.id,BigNumbersMandatory.bigDeci
malType,BigNumbersMandatory.bigIntegerType FROM 
BigNumbersMandatory WHERE id=?
2002-12-17 14:35:31,590 DEBUG 
[org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand] Set 
parameter: idx=1, jdbcType=VARCHAR, value=Piet
2002-12-17 14:35:31,621 DEBUG 
[org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand] Got a 
java.math.BigDecimal: '100' while looking for a 
java.math.BigInteger


Note that in the create table script the difference 
between bigint and bigdecimal is the precision.

I looked at Solid, Informix, Oracle, InstandDB and DB2. 
They all use BigInteger and BigDecimal the same way, 
that is: A BigInteger is a BigDecimal without precision 
(on SQL table creation level). 

Proposal for function protected Object getResultObject
(ResultSet rs, int idx, Class destination) in 
JDBCCommand.java (org.jboss.ejb.plugins.jaws.jdbc)

Upon retrieving a BigDecimal when actually a BigInteger 
is expected, check if the desired type is indeed 
BigInteger. Test if the actual retrieved BigDecimal has a 
scale of zero. If this is the case, convert the BigDecimal 
to BigInteger by calling method toBigInteger() and return 
the converted type.

Attached is a zip file containing the file original 
JDBCCommand.java file and the new file with the 
proposed changes. 


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376687aid=656231group_id=22866


---
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M  http://www.thinkgeek.com/sf/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-648344 ] open-cursors limit reached

2002-12-19 Thread noreply
Bugs item #648344, was opened at 2002-12-04 11:52
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=648344group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bruce Barrow (bruce_b)
Assigned to: Nobody/Anonymous (nobody)
Summary: open-cursors limit reached

Initial Comment:
First 'bug', so bear with me. Some description follows 
the trace.

OS: Windows NT 4.0
JDK: 1.4


10:13:49,671 INFO  [Server] JBoss Release: JBoss-
3.0.3 CVSTag=JBoss_3_0_3
10:13:49,718 INFO  [Server] Home Dir: F:\jboss\jboss-
3.0.3
10:13:49,718 INFO  [Server] Home URL: 
file:/F:/jboss/jboss-3.0.3/
10:13:49,718 INFO  [Server] Library URL: 
file:/F:/jboss/jboss-3.0.3/lib/
10:13:49,718 INFO  [Server] Patch URL: null
10:13:49,718 INFO  [Server] Server Name: efc
10:13:49,718 INFO  [Server] Server Home Dir: 
F:\jboss\jboss-3.0.3\server\efc
10:13:49,718 INFO  [Server] Server Home URL: 
file:/F:/jboss/jboss-3.0.3/server/efc/
10:13:49,718 INFO  [Server] Server Data Dir: 
F:\jboss\jboss-3.0.3\server\efc\db
10:13:49,718 INFO  [Server] Server Temp Dir: 
F:\jboss\jboss-3.0.3\server\efc\tmp
10:13:49,750 INFO  [Server] Server Config URL: 
file:/F:/jboss/jboss-3.0.3/server/efc/conf/
10:13:49,750 INFO  [Server] Server Library URL: 
file:/F:/jboss/jboss-3.0.3/server/efc/lib/
10:13:49,750 INFO  [Server] Root Deployemnt Filename: 
jboss-service.xml
10:13:49,750 INFO  [Server] Starting General Purpose 
Architecture (GPA)...
10:13:50,218 INFO  [ServerInfo] Java version: 
1.4.0_02,Sun Microsystems Inc.
10:13:50,218 INFO  [ServerInfo] Java VM: Java HotSpot
(TM) Client VM 1.4.0_02-b02,Sun Microsystems Inc.
10:13:50,218 INFO  [ServerInfo] OS-System: Windows 
NT 4.0,x86
10:13:50,312 INFO  [ServiceController] Controller MBean 
online
10:13:50,484 INFO  [MainDeployer] Creating
10:13:50,546 INFO  [MainDeployer] Created
10:13:50,546 INFO  [MainDeployer] Starting
10:13:50,546 INFO  [MainDeployer] Started
10:13:50,578 INFO  [JARDeployer] Creating
10:13:50,578 INFO  [JARDeployer] Created
10:13:50,578 INFO  [JARDeployer] Starting
10:13:50,578 INFO  [MainDeployer] Adding deployer: 
org.jboss.deployment.JARDeployer@808199
10:13:50,578 INFO  [JARDeployer] Started
10:13:50,609 INFO  [SARDeployer] Creating
10:13:50,609 INFO  [SARDeployer] Created
10:13:50,609 INFO  [SARDeployer] Starting
10:13:50,609 INFO  [MainDeployer] Adding deployer: 
org.jboss.deployment.SARDeployer@66a22b
10:13:50,703 INFO  [SARDeployer] Started
10:13:50,703 INFO  [Server] Core system initialized
10:13:50,718 INFO  [MainDeployer] Starting deployment 
of package: file:/F:/jboss/jboss-
3.0.3/server/efc/conf/jboss-servi
ce.xml

[...]
10:14:04,562 INFO  [jbossweb] Starting Jetty/4.1
10:14:04,593 INFO  [jbossweb] Started 
org.mortbay.http.NCSARequestLog@8a8ce2
[...]
10:14:31,437 INFO  [EjbModule] Started
10:14:31,437 INFO  [EjbModule] Starting
10:14:31,484 INFO  [EjbModule] Started
10:14:31,484 INFO  [MainDeployer] Deployed package: 
file:/F:/jboss/jboss-3.0.3/server/efc/deploy/efc.ear
10:14:31,484 INFO  [URLDeploymentScanner] Started
10:14:31,500 INFO  [MainDeployer] Deployed package: 
file:/F:/jboss/jboss-3.0.3/server/efc/conf/jboss-service.xml
10:14:31,500 INFO  [Server] JBoss (MX MicroKernel) 
[3.0.3 Date:200209301503] Started in 0m:41s:750ms
10:42:25,890 INFO  [STDOUT] 
CPCBean.registerUserSession
10:42:25,906 INFO  [STDOUT] 
CPCBean.registerUserSession: Registering 
userSession, key=edgar_j:Product Tester [-38522377
2]
[...]
11:08:20,468 ERROR [STDERR] 
{className=WorkspaceDAOOracle 
methodName=readRow 
componentSequenceNumber=203003 severity
=13 errorType=0 errorMessage=An SQL Exception 
occurred while trying to execute statement  SELECT 
cols_list FROMtable WHERE   where . 
The error was 72000
 dynamicContent={ SELECT   cols FROM
table WHERE etc... , 72000
} nestedException.message=ORA-01000: maximum 
open cursors exceeded
 nestedException.stackTrace=java.sql.SQLException: 
ORA-01000: maximum open cursors exceeded


Initially, the open_cursors parameter on the database 
was set to 250. This was raised to 500, but this was just 
putting off the problem - not resolving it.

Querying the database shows that some sessions have 
over 250 cursors - these should really expire or be aged 
out. Is this a known issue? 

Connecting to the JBoss server takes one or two 
seconds, because of the work required to determine 
access rights, therefore sessions are left connected. 
The number of cursors used therefore increases quickly.

Is there a way of configuring JBoss to release cursors 
more quickly?

Thanks in advance,

Bruce

--

Comment By: Bruce Barrow (bruce_b)
Date: 2002-12-19 11:34

Message:
Logged In: YES 
user_id=661946

UPDATE:

We found (okay, so I didn't!) a statement in the 
initialisation/connection opening section which was setting 
the date format. This statement was NOT being closed.

This was done by one of our colleagues (long-since 

[JBoss-dev] [ jboss-Bugs-656613 ] Only local files allowed in JSP classpat

2002-12-19 Thread noreply
Bugs item #656613, was opened at 2002-12-19 19:29
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=656613group_id=22866

Category: JBossWeb
Group: CVS HEAD
Status: Open
Resolution: None
Priority: 5
Submitted By: Jeremy Boynes (jboynes)
Assigned to: Nobody/Anonymous (nobody)
Summary: Only local files allowed in JSP classpat

Initial Comment:
When JBoss is booted from the network, boot libraries
from JBOSS_HOME/lib are loaded using a http: URL. Due
to limitations of the Java compiler used for JSP
compilation, classes in these libraries are not
available when the JSP servlet is being compiled and
may result in compilation errors.

The web integration layer should ensure that all URLs
handled by the context classloader are available
locally for use by the JSP compiler regardless of where
the true location is. This may require downloading
jar/zip files.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=656613group_id=22866


---
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M  http://www.thinkgeek.com/sf/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Patches-655675 ] NamingContext.lookup() loops too often

2002-12-18 Thread noreply
Patches item #655675, was opened at 2002-12-18 12:00
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376687aid=655675group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Jens Deponte (dirkgently)
Assigned to: Nobody/Anonymous (nobody)
Summary: NamingContext.lookup() loops too often

Initial Comment:
In class org.jnp.interfaces.NamingContext:

1) When NamingContext.lookup() is called the lookup is
done in a loop that is *always* executed MAX_REPEAT
(==10) times. The result of naming.lookup(n) is not
checked in the loops condition clause.
The problem leads to no error, but decreases performance.

2) When the lookup fails MAX-REPEAT times, there is no
proper exception handling. IMHO the catched
ConnectException should be thrown.

The bugs were found in JBoss 3.0.4. The second one is
fixed in 3.1beta2, but the first still exists.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376687aid=655675group_id=22866


---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Patches-655700 ] NamingContext.lookup() loops too often

2002-12-18 Thread noreply
Patches item #655700, was opened at 2002-12-18 12:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376687aid=655700group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Jens Deponte (dirkgently)
Assigned to: Nobody/Anonymous (nobody)
Summary: NamingContext.lookup() loops too often

Initial Comment:
In class org.jnp.interfaces.NamingContext:

1) When NamingContext.lookup() is called the lookup is
done in a loop that is *always* executed MAX_REPEAT
(==10) times. The result of naming.lookup(n) is not
checked in the loops condition clause.
The problem leads to no error, but decreases performance.

2) When the lookup fails MAX-REPEAT times, there is no
proper exception handling. IMHO the catched
ConnectException should be thrown.

The bugs were found in JBoss 3.0.4. The second one is
fixed in 3.1beta2, but the first still exists.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376687aid=655700group_id=22866


---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-547831 ] JMS Redelivery doesn't work

2002-12-18 Thread noreply
Bugs item #547831, was opened at 2002-04-23 23:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=547831group_id=22866

Category: JBossMQ
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Randy Dey-Toth (rdeytoth)
Assigned to: Adrian Brock (ejort)
Summary: JMS Redelivery doesn't work

Initial Comment:
According to a posting in the forum, this is an old 
bug, fixed in the 3.0 line.  But it is not fixed.

When using a durable persistent Topic, unacknowledged 
messages are only redelivered when the server is 
restarted.


--

Comment By: Alexander Rabinowitz (raevsky)
Date: 2002-12-18 15:40

Message:
Logged In: YES 
user_id=671073

Yes, I tried creating a new QueueConnection. That is how I 
saw the bug initially. The new QueueConnection works OK on 
JBoss 2.4.4. However, the first message is still lost, even 
when I use new QueueConnection.
All the other messages are delivered OK through new 
QueueConnection.

--

Comment By: Randy Dey-Toth (rdeytoth)
Date: 2002-12-18 04:09

Message:
Logged In: YES 
user_id=524545

raevsky:  the spec can be found at a 
href=http://java.sun.com/products/jms/docs.htmlJMS 1.1 
Spec /a

Did you try just creating a new QueueConnection, if you can't 
close the one you have?

The spec says that, for durable subcribers,  Subsequent 
subscriber objects with the same identity resume the
subscription in the state it was left in by the prior 
subscriber.  If the last subscriber had one message sent to it 
but not acknowledged, this could be interpreted to mean the 
next subscriber with the same client id should immediately 
be delivered the sent but unacknowledged message, so that 
it may be in the same state.  When the JBoss Server was 
restarted, this is how it behaved.  The fix makes the behavior 
consistent.

In any case, when the bug was posted, the session.recover() 
was not an option, it didn't work either.  (see bug 526696  
session.recover() doesn't work ). 


--

Comment By: Adrian Brock (ejort)
Date: 2002-12-17 21:06

Message:
Logged In: YES 
user_id=9459

Hi,

The fixes you want are mainly in 
org.jboss.mq.server.BasicQueue
org.jboss.mq.server.ClientConsumer

there is also a fix for closing a non-transactional session
with unacknowledged messages in 
org.jboss.mq.SpySession

But if you look at org.jboss.mq.server
for 3.0 and 2.4 you will see they are very different.
http://cvs.sourceforge.net/cgi-
bin/viewcvs.cgi/jboss/jbossmq/src/main/org/jboss/mq/server/?
only_with_tag=Branch_2_4
http://cvs.sourceforge.net/cgi-
bin/viewcvs.cgi/jboss/jbossmq/src/main/org/jboss/mq/server/?
only_with_tag=Branch_3_0
The main server classes have changed and
a message cache is introduced for scalability.

The work I did was mainly fixing leaks in the message
cache, dropped connections was just a small part of
it.

Rimmeraj is correct, the spec does not require
this behaviour, but there is small comment in
one of the javadocs that implies it.

Regards,
Adrian

--

Comment By: Alexander Rabinowitz (raevsky)
Date: 2002-12-17 20:33

Message:
Logged In: YES 
user_id=671073

Actually, my problem  is the following (JBoss 2.4.4):
http://www.jboss.org/forums/thread.jsp?forum=48thread=26224

Adrian (ejort) confirmed his fix should have fixed my problem. I just wanted to put 
the fix into JBoss 2.4.4 (which I 
am using) , and Adrian asked me to put the question into the bug description. He will 
hopefully tell us how to fix 
the bug in 2.4.4

--

Comment By: Alexander Rabinowitz (raevsky)
Date: 2002-12-17 20:05

Message:
Logged In: YES 
user_id=671073

Where can I look at that spec?
What does it mean it is not supposed to?
How can I recover the session if I cannot close the QueueConnection, because the 
network connection is lost on 
the client?


--

Comment By: Dave Smith (rimmeraj)
Date: 2002-12-17 19:11

Message:
Logged In: YES 
user_id=486338

Read the spec. It is not supposed to .  If you want the
messages re-delivered then recover the session.




--

Comment By: Alexander Rabinowitz (raevsky)
Date: 2002-12-17 18:18

Message:
Logged In: YES 
user_id=671073

Hi, Adrian:

I'd like to install your change (that you put into JBoss 3.0.4) to Jboss
2.4.4
As I see into source code, you added two files -
ExclusiveQueue.java and
SelectorPersistentQueue.java

Is that how the problem is fixed?

Can you tell me what I need to do to put the changes to 2.4.4?

Thanks very much

--

Comment By: Adrian Brock 

[JBoss-dev] [ jboss-Bugs-655821 ] bug with [ 644394 ] support for cmr+cmp

2002-12-18 Thread noreply
Bugs item #655821, was opened at 2002-12-18 15:48
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=655821group_id=22866

Category: JBossCMP
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jeff Whiteside (jwhiteside)
Assigned to: Nobody/Anonymous (nobody)
Summary: bug with [ 644394 ] support for cmr+cmp 

Initial Comment:
I descovered a potential problem with patch 644394 
described in the following 
forum:http://jboss.org/forums/thread.jsp?
forum=46thread=25017. If this is not the proper place to 
post this, please let me know.

I have successfully applied the patch but am still receiving 
a duplicate column name. After digging through the 
patched code I noticed that the cmpFieldsByName Map on 
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge 
contains field names as keys. When the 
getCMPFieldByName(cnames[ndx]) method is invoked 
within the loadUniqueCMPCMRFieldSet() method of the 
same class, an array containing column names is passed 
in. Since the Map contains field names and the argument 
contains column names, this method always returns null 
causing both the cmp and the cmr field to be added to the 
insert causing the duplicate column name.

I fixed the problem in my case by changing the 
JDBCEntityBridge.loadUniqueCMPCMRFieldSet() code 
from:

String cnames[] = cmrField.getJDBCType
().getColumnNames();
  for (int ndx = 0; ndx  cnames.length; ndx++) {
 if (getCMPFieldByName(cnames[ndx]) == null)   {
uniqueList.add(cmrField);
  }

to:

if (getCMPFieldByName(cmrField.getFieldName()) == null) {
  uniqueList.add(cmrField);
}

Can sombody verify that this is a defect and advise me as 
to how to get the patch updated?



--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=655821group_id=22866


---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-547831 ] JMS Redelivery doesn't work

2002-12-18 Thread noreply
Bugs item #547831, was opened at 2002-04-23 23:17
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=547831group_id=22866

Category: JBossMQ
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Randy Dey-Toth (rdeytoth)
Assigned to: Adrian Brock (ejort)
Summary: JMS Redelivery doesn't work

Initial Comment:
According to a posting in the forum, this is an old 
bug, fixed in the 3.0 line.  But it is not fixed.

When using a durable persistent Topic, unacknowledged 
messages are only redelivered when the server is 
restarted.


--

Comment By: Alexander Rabinowitz (raevsky)
Date: 2002-12-18 16:07

Message:
Logged In: YES 
user_id=671073

The quote you used Subsequent 
subscriber objects with the same identity resume the
subscription in the state it was left in by the prior 
subscriber. is used in the spec in the context of durable 
subscriptions, not queues. So, that does not look like the 
spec requires this behaviour. But nevertheless it makes the 
system unusable. Probably, because it is a problem with the 
soec itself. The spec cannot describe everything.

--

Comment By: Alexander Rabinowitz (raevsky)
Date: 2002-12-18 15:40

Message:
Logged In: YES 
user_id=671073

Yes, I tried creating a new QueueConnection. That is how I 
saw the bug initially. The new QueueConnection works OK on 
JBoss 2.4.4. However, the first message is still lost, even 
when I use new QueueConnection.
All the other messages are delivered OK through new 
QueueConnection.

--

Comment By: Randy Dey-Toth (rdeytoth)
Date: 2002-12-18 04:09

Message:
Logged In: YES 
user_id=524545

raevsky:  the spec can be found at a 
href=http://java.sun.com/products/jms/docs.htmlJMS 1.1 
Spec /a

Did you try just creating a new QueueConnection, if you can't 
close the one you have?

The spec says that, for durable subcribers,  Subsequent 
subscriber objects with the same identity resume the
subscription in the state it was left in by the prior 
subscriber.  If the last subscriber had one message sent to it 
but not acknowledged, this could be interpreted to mean the 
next subscriber with the same client id should immediately 
be delivered the sent but unacknowledged message, so that 
it may be in the same state.  When the JBoss Server was 
restarted, this is how it behaved.  The fix makes the behavior 
consistent.

In any case, when the bug was posted, the session.recover() 
was not an option, it didn't work either.  (see bug 526696  
session.recover() doesn't work ). 


--

Comment By: Adrian Brock (ejort)
Date: 2002-12-17 21:06

Message:
Logged In: YES 
user_id=9459

Hi,

The fixes you want are mainly in 
org.jboss.mq.server.BasicQueue
org.jboss.mq.server.ClientConsumer

there is also a fix for closing a non-transactional session
with unacknowledged messages in 
org.jboss.mq.SpySession

But if you look at org.jboss.mq.server
for 3.0 and 2.4 you will see they are very different.
http://cvs.sourceforge.net/cgi-
bin/viewcvs.cgi/jboss/jbossmq/src/main/org/jboss/mq/server/?
only_with_tag=Branch_2_4
http://cvs.sourceforge.net/cgi-
bin/viewcvs.cgi/jboss/jbossmq/src/main/org/jboss/mq/server/?
only_with_tag=Branch_3_0
The main server classes have changed and
a message cache is introduced for scalability.

The work I did was mainly fixing leaks in the message
cache, dropped connections was just a small part of
it.

Rimmeraj is correct, the spec does not require
this behaviour, but there is small comment in
one of the javadocs that implies it.

Regards,
Adrian

--

Comment By: Alexander Rabinowitz (raevsky)
Date: 2002-12-17 20:33

Message:
Logged In: YES 
user_id=671073

Actually, my problem  is the following (JBoss 2.4.4):
http://www.jboss.org/forums/thread.jsp?forum=48thread=26224

Adrian (ejort) confirmed his fix should have fixed my problem. I just wanted to put 
the fix into JBoss 2.4.4 (which I 
am using) , and Adrian asked me to put the question into the bug description. He will 
hopefully tell us how to fix 
the bug in 2.4.4

--

Comment By: Alexander Rabinowitz (raevsky)
Date: 2002-12-17 20:05

Message:
Logged In: YES 
user_id=671073

Where can I look at that spec?
What does it mean it is not supposed to?
How can I recover the session if I cannot close the QueueConnection, because the 
network connection is lost on 
the client?


--

Comment By: Dave Smith (rimmeraj)
Date: 2002-12-17 19:11

Message:
Logged In: YES 
user_id=486338

Read the spec. It is not supposed to .  If you want the
messages re-delivered then 

[JBoss-dev] [ jboss-Bugs-652520 ] INSERTING AN ALREADY EXISTING BEAN

2002-12-18 Thread noreply
Bugs item #652520, was opened at 2002-12-12 13:04
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=652520group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 9
Submitted By: Artemiy Zinoviev (bedriven)
Assigned to: Adrian Brock (ejort)
Summary: INSERTING AN ALREADY EXISTING BEAN

Initial Comment:
Hello all!

I have a Jboss version 3.0.4 an receive the same error 
when trying to create a EJB.

I have tried use commit option A,B,C but it is not work. 

When I use commit option C this error appears rarely 
but take a place in any case.

I have tried to inspect JBoss source code and I have 
found out next code in AbstractInstanceCache:

...

public void insert(EnterpriseContext ctx)
{
if (ctx == null) throw new IllegalArgumentException
(Can't insert a null object in the cache);

CachePolicy cache = getCache();
synchronized (getCacheLock())
{
// This call must be inside the sync block, otherwise can 
happen that I get the
// key, then the context is passivated and I will insert in 
cache a meaningless
// context.
Object key = getKey(ctx);

if (cache.peek(key) == null)
{
cache.insert(key, ctx);
}
else
{
// Here it is a bug.
// Check for all places where insert is called, and ensure 
that they cannot
// run without having acquired the cache lock via 
getCacheLock()
throw new IllegalStateException(INSERTING AN 
ALREADY EXISTING BEAN, ID =  + key);
}
}
}

...

Could anyone tell me whats going on? My project under 
the risk, please, I need help. Is it bug or something?


Stack trace is :

java.lang.IllegalStateException: INSERTING AN 
ALREADY EXISTING BEAN, ID = [.]
at org.jboss.ejb.plugins.AbstractInstanceCache.insert
(AbstractInstanceCache.java:222)
at 
org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHo
me(EntityInstanceInterceptor.java:103)
at 
org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome
(EntityLockInterceptor.java:79)
at 
org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHo
me(EntityCreationInterceptor.java:44)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext
(AbstractTxInterceptor.java:111)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxInterceptorCMT.java:178)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome
(TxInterceptorCMT.java:52)
at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome
(SecurityInterceptor.java:105)
at org.jboss.ejb.plugins.LogInterceptor.invokeHome
(LogInterceptor.java:129)
at org.jboss.ejb.EntityContainer.invokeHome
(EntityContainer.java:487)
at 
org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.inv
okeHome(BaseLocalContainerInvoker.java:230)
at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke
(LocalHomeProxy.java:110)
at $Proxy22.create(Unknown Source)
at 
com.eurooil.managers.user.basic.DefaultUserManager.cr
eateUser(DefaultUserManager.java:147)
at com.eurooil.web.example.CreateUserAction.perform
(CreateUserAction.java:79)
at 
org.apache.struts.action.ActionServlet.processActionPerf
orm(ActionServlet.java:1787)
at org.apache.struts.action.ActionServlet.process
(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doGet
(ActionServlet.java:492)
at javax.servlet.http.HttpServlet.service
(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service
(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationFilterChain.internalD
oFilter(ApplicationFilterChain.java:247)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:260)
at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.CertificatesValve.invoke
(CertificatesValve.java:246)
at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:180)
at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:643)
at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at 
org.apache.catalina.core.StandardPipeline$StandardPipe
lineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:172)
at 

[JBoss-dev] [ jboss-Bugs-615553 ] Bean Load generates way more SQL

2002-12-18 Thread noreply
Bugs item #615553, was opened at 2002-09-27 12:00
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=615553group_id=22866

Category: JBossCMP
Group: v3.1
Status: Closed
Resolution: Invalid
Priority: 9
Submitted By: Peter Luttrell (objec)
Assigned to: Dain Sundstrom (dsundstrom)
Summary: Bean Load generates way more SQL

Initial Comment:
I'm using most of the default jboss settings. I wasn't able 
to change the read-ahead settings (see other bug, which 
is now fixed).

I have a finder method that returns in this case 1106 
entity beans. Then i iterate through the collection and 
grab most of the data.

This takes an enormous amount of time. Some 
900,000ms in one particular test. I looked at the sql 
jboss generated in the server.log file and beleive that 
there is some looping error because it is generating way 
too much sql.

According to my understanding the default readahead 
settings will cause jboss to construct a sql statement 
with 255 ORs, hense reading the 1106 rows in 5 different 
sql statements.

But JBoss is actually creating 1106 sql statements with 
varring amounts of ORs. Some times JBoss executes 
sql statements with the same large number 255, i think. 
Other times it does a series of 255, 254, 2531. It's 
actually a pretty waterfall effect.

I could post my log file, but it's like 5mbs. Dain, please 
email me if you'd like the log file sent directly to you.

--

Comment By: C. Lamont Gilbert (dnoyeb)
Date: 2002-12-19 01:44

Message:
Logged In: YES 
user_id=280374

I am experiencing the same thing in 3.0.4 but appearantly
you are saying this is correct behavior.

I need the documentation. will purchase...

--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-09-27 12:12

Message:
Logged In: YES 
user_id=251431

Optimized loading is overed in the JBossCMP documentation
chapter 6.  Look for the O(n^2) section.  The problem is you
are not using a transaction.

BTW, changing the priority does not get your bug fixed any
faster.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=615553group_id=22866


---
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players,  XBox Games,  Flying Saucers,  WebCams,  Smart Putty.
T H I N K G E E K . C O M   http://www.thinkgeek.com/sf/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-655101 ] ClassNotFoundException in JSF demo

2002-12-17 Thread noreply
Bugs item #655101, was opened at 2002-12-17 12:29
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=655101group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Vladimir Korenev (vkorenev)
Assigned to: Nobody/Anonymous (nobody)
Summary: ClassNotFoundException in JSF demo

Initial Comment:
When trying to execute examples from JavaServerFaces
ea2 an exception occures:
2002-12-16 17:29:30,470 ERROR [STDERR]
java.lang.ClassNotFoundException: No ClassLoaders found
for: com.sun.faces.context.MessageTemplate
2002-12-16 17:29:30,470 ERROR [STDERR]  at
org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:138)
2002-12-16 17:29:30,470 ERROR [STDERR]  at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:140)
2002-12-16 17:29:30,470 ERROR [STDERR]  at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
2002-12-16 17:29:30,470 ERROR [STDERR]  at
org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java:252)
2002-12-16 17:29:30,470 ERROR [STDERR]  at
org.apache.commons.digester.Digester.startElement(Digester.java:1237)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1488)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
org.apache.commons.digester.Digester.parse(Digester.java:1514)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.context.MessageResourcesImpl.loadMessages(MessageResourcesImpl.java:172)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.context.MessageResourcesImpl.findCatalog(MessageResourcesImpl.java:122)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.context.MessageResourcesImpl.getMessage(MessageResourcesImpl.java:213)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.context.MessageResourcesImpl.getMessage(MessageResourcesImpl.java:208)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.util.Util.getExceptionMessage(Util.java:213)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.util.Util.getExceptionMessage(Util.java:222)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getKeyAndLookupInBundle(HtmlBasicRenderer.java:204)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.renderkit.html_basic.ButtonRenderer.getImageSrc(ButtonRenderer.java:116)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
com.sun.faces.renderkit.html_basic.ButtonRenderer.encodeEnd(ButtonRenderer.java:231)
2002-12-16 17:29:30,480 ERROR [STDERR]  at
javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:1127)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
javax.faces.component.UICommand.encodeEnd(UICommand.java:156)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
javax.faces.webapp.FacesTag.doEndTag(FacesTag.java:278)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.apache.jsp.greeting$jsp._jspService(greeting$jsp.java:158)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:366)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:293)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:216)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:151)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
com.sun.faces.lifecycle.ViewHandlerImpl.renderView(ViewHandlerImpl.java:57)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
com.sun.faces.lifecycle.JspRenderResponsePhase.execute(JspRenderResponsePhase.java:91)
2002-12-16 17:29:30,490 ERROR [STDERR]  at
com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:259)
2002-12-16 17:29:30,490 

[JBoss-dev] [ jboss-Bugs-654652 ] Message-driven bean security error

2002-12-17 Thread noreply
Bugs item #654652, was opened at 2002-12-16 17:41
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=654652group_id=22866

Category: JBossSX
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Remind
Priority: 5
Submitted By: Maxim (kimerinn)
Assigned to: Scott M Stark (starksm)
Summary: Message-driven bean security error

Initial Comment:
Scenario:

1) I created a secured session bean, it can be accessed
under the tester security role. 
2) I created a message-driven bean, which operates
under run-as identity and has tester sequrity role.
3) When MDB tries to access secured session bean, an
error raises:

17:21:21,015 ERROR [LogInterceptor] EJBException, causedBy:

java.lang.SecurityException: Authentication exception,
principal=null

at
org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(SecurityInterceptor.java:173)

at
org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:94)

at
org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:129)

at
org.jboss.ejb.StatelessSessionContainer.invokeHome(StatelessSessionContainer.java:300)

at
org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.invokeHome(BaseLocalContainerInvoker.java:230)

at
org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:110)

at $Proxy25.create(Unknown Source)

at ejbtest.mdbBean.onMessage(mdbBean.java:27)

at java.lang.reflect.Method.invoke(Native Method)

at
org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:391)

at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)

at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:107)

at
org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:144)

at
org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT.invoke(MessageDrivenTxInterceptorBMT.java:33)

at
org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:88)

at
org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:100)

at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203)

at
org.jboss.ejb.MessageDrivenContainer.invoke(MessageDrivenContainer.java:302)

at
org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:962)

at
org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1038)

at
org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:238)

at
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:603)

at
org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:417)

at org.jboss.mq.SpySession.run(SpySession.java:259)

at
org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)

at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:642)

at java.lang.Thread.run(Thread.java:484)

17:21:21,065 ERROR [STDERR] javax.ejb.EJBException:
checkSecurityAssociation; CausedByException is:
Authentication exception, principal=null

17:21:21,065 ERROR [STDERR] at
org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(SecurityInterceptor.java:174)

17:21:21,706 ERROR [STDERR] at
org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:94)

17:21:21,706 ERROR [STDERR] at
org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:129)

17:21:21,706 ERROR [STDERR] at
org.jboss.ejb.StatelessSessionContainer.invokeHome(StatelessSessionContainer.java:300)

17:21:21,706 ERROR [STDERR] at
org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.invokeHome(BaseLocalContainerInvoker.java:230)

17:21:21,716 ERROR [STDERR] at
org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:110)

17:21:21,716 ERROR [STDERR] at $Proxy25.create(Unknown
Source)

17:21:21,716 ERROR [STDERR] at
ejbtest.mdbBean.onMessage(mdbBean.java:27)

17:21:21,716 ERROR [STDERR] at
java.lang.reflect.Method.invoke(Native Method)

17:21:21,716 ERROR [STDERR] at
org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:391)

17:21:21,716 ERROR [STDERR] at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)

17:21:21,726 ERROR [STDERR] at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:107)

17:21:21,746 ERROR [STDERR] at
org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:144)

17:21:21,746 ERROR [STDERR] at

  1   2   3   4   5   6   7   8   9   10   >