From: Richard G C. <rg...@ze...> - 2004-12-22 14:59:22
|
Sounds like the transaction service is starting before the naming service or the inital references arn't configured correctly (see the default.xml and OpenORB.xml config files). The reason why they work when stated in the same directory is that OpenORB uses stringified IOR's as a automatic fallback. -Richard. Timo Buschick wrote: > Thanx, > > and I´ll found a solution today. > > When the NamingService and the TransactionService is startet directly > (like > java org.openorb.ins.Server) in the same folder as where I start my > application it works. But this seems to me as a workaround, as the > services > should be available throught out the whole system. > > cu, Timo. > > > >> I'll try to investigate that over the holiday season. >> >> >> >>> to be a little more precise, I get the following error when trying >>> to use >>> the Transaction Service: >>> >>> org.omg.CORBA.INTERNAL: Unable to connect to the transaction >>> factory >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://productguide.itmanagersjournal.com/ >> _______________________________________________ >> openorb-users mailing list >> ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openorb-users >> >> > > > > |