You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jacek Laskowski (JIRA)" <ji...@apache.org> on 2006/12/03 13:31:23 UTC
[jira] Closed: (OPENEJB-394) javax.naming.NameNotFoundException
Name "client/tools/DatabaseHome" not found
[ http://issues.apache.org/jira/browse/OPENEJB-394?page=all ]
Jacek Laskowski closed OPENEJB-394.
-----------------------------------
Transmitting file data .............
Committed revision 481764.
> javax.naming.NameNotFoundException Name "client/tools/DatabaseHome" not found
> -----------------------------------------------------------------------------
>
> Key: OPENEJB-394
> URL: http://issues.apache.org/jira/browse/OPENEJB-394
> Project: OpenEJB
> Issue Type: Bug
> Components: deployment
> Affects Versions: 3.0
> Reporter: Jacek Laskowski
> Assigned To: Jacek Laskowski
> Fix For: 3.0
>
>
> While building OpenEJB I'm getting the following error message. Does anyone know what's broken and why?
> -------------------------------------------------------------------------------
> Test set: org.apache.openejb.ApplicationTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.953
> sec <<< FAILURE!
> org.apache.openejb.iTest@c1a0eb Time elapsed: 1,164,841,511.015 sec <<< ERROR!
> java.lang.IllegalStateException: Cannot find
> 'client/tools/DatabaseHome': javax.naming.NameNotFoundException Name
> "client/tools/DatabaseHome" not found.
> at org.apache.openejb.test.DerbyTestDatabase.start(DerbyTestDatabase.java:121)
> at org.apache.openejb.test.TestManager.start(TestManager.java:71)
> at org.apache.openejb.iTest.setUp(iTest.java:50)
> at org.apache.openejb.test.TestSuite.run(TestSuite.java:40)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:160)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:81)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:182)
> at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:743)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira