Hello Frito and hello to all the other people,
I think I didn't mention my case properly: I tried to access the bean of server
b from a business method of a session bean residing in server a. The exception
I posted was the result of trying to use a new InitialContext, so I was not
able to use a newly created InitialContext with URL pointing to server b. But I
was successful using a new InitialContext from my client application residing
in server a to connect to a bean in server b. My problem is, that a bean inside
of server a has to communicate with a bean in server b. Maybe my properties set
was incorrect? As I tried to connect from bean a in server a to bean b in
server b, I took these properties:
Properties properties = System.getProperties();
properties.put("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
properties.put("java.naming.provider.url",
"jnp://ip.of.remote.server:1099");
properties.put("java.naming.security.principal", "myuser");
properties.put("java.naming.security.credentials", "mypass");
Does server a or server b need some configuration changes compared to the
configuration out-of-the-box as it was coming with jboss4.0.1 linux tar.bz in
order to create a connection to another server? Does default config meet my
case or do I have to start both servers with the all configuration? Do I have
to create a role in order to connect to the jndi service using the username and
password I put into the properties? I am ashamed to ask this question, but I
really can't help me out:)...
You were then speaking about the jboss clustering and hajndi, so here is a new
question;) : is it possible to use this setup if the same jar file was deployed
to server a and server b? Because of that, the jndi names are identical in both
jndi namespaces comparing server a and server b. May one map the jndi context
of server b into the namespace of server a? My problem experimenting with jboss
clustering so far: as soon as I deploy the ejbset.jar file to server b, the
jndi namespace of server a seems to be overwritten resulting in the problem
that I am not able to find any bean in server a because of the identical jndi
names of the beans in server a and server b. Remember: same jar file deployed.
I am sorry to ask, and maybe it would be a better place to ask in the newbie
forum, but as I reply to you, I post here.
I already read the jboss4guide (especially chapter 3) and I am not cleverer
than before:(
So, thank You for Your reply and I hope there is someone out there who may
bring me to the light of wisdom to create a connection between two beans in tow
different servers on two different machines.
Greetings from Oldenburg, Germany, snowy winter scenario
Ralph
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863409#3863409
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863409
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
