Hm yes i also read this post (first google entry) :-) But i didn't found an explanation why it works for the "normal" ofbiz start and not for a test run. IMHO it's not an general issue, it's related to the test-container configuration.
2012/4/26 Pierre Smits <[email protected]>: > Sascha, > > I found this thread that deals with the same issue: > http://forum.springsource.org/showthread.php?33711-RMI-invocation-attempts-connecting-to-127-0-0-1 > > And explanation on the subject via this thread: > http://docs.oracle.com/javase/1.4.2/docs/guide/rmi/faq.html#nethostname > > I trust this will help. > > Regards, > > Pierre > > > Op 26 april 2012 09:57 schreef Sascha Rodekamp < > [email protected]> het volgende: > >> I have problems binding objects to JNDI during a unit test. Seems that >> the jndi server is not running correctly. >> This error occurs when i run a single unit test suite. >> >> Does someone have an idea? The configuration seems similar to a normal run. >> >> Exception: javax.naming.ServiceUnavailableException >> Message: null >> ---- cause >> --------------------------------------------------------------------- >> Exception: java.rmi.ConnectException >> Message: Connection refused to host: 127.0.0.1; nested exception is: >> java.net.ConnectException: Connection refused: connect >> ---- cause >> --------------------------------------------------------------------- >> Exception: java.net.ConnectException >> Message: Connection refused: connect >> ---- stack trace >> --------------------------------------------------------------- >> java.net.ConnectException: Connection refused: connect >> -- >> -- Sascha Rodekamp Visit the new german OFBiz Blog: http://www.ofbiz.biz Lynx-Consulting GmbH Johanniskirchplatz 6 D-33615 Bielefeld http://www.lynx.de
