We ended up having to add the following to the startup on the server side as part of the JAVA_OPTS:

-Djava.rmi.server.useLocalHostname=true -Djava.rmi.server.hostname=appserver.domain.com

where "appserver.domain.com" is the hostname of the jboss server.


Then, on the client side added the following to the JAVA_OPTS for tomcat:


-Djava.rmi.server.hostname=appserver.domain.com


We ended up then defining appserver.domain.com in the hosts table on the client system to avoid a dns lookup.


An excellent way to check the configuration from the client side is to use telnet like:

telnet appserver.domain.com 1099

It should come back with something looking like:

Trying [ip address of appserver.domain.com]...
Connected to appserver.domain.com.
Escape character is '^]'.
??srjava.rmi.MarshalledObject|???c?>IhashlocBytest[BobjBytesq~xp)?&? ur[B??T?xp.??thttp://appserver.domain.com:8083/q~q~uq~Ç?sr org.jnp.server.NamingServer_Stubxrjava.rmi.server.RemoteStub???É? exrjava.rmi.server.RemoteObject?a??
a3xpw;
UnicastRef2appserver.domain.comJ???ËZ?xConnection closed by foreign host.


You should see buried in the response the hostname you expect to see. If it is there, cool. If an ip address or some other hostname, you have more to do.

Also, don't forget to open all the required ports between these servers on the firewall.

Frank

On May 3, 2005, at 9:57 AM, ice wrote:

"darranl" wrote : Anyone asking how to get JBoss to use a different Tomcat has got their tiers back to front.
|
| The web tier should make use of the EJB tier, however the EJB tier should have no knowledge of the web tier.
|
| You should be asking how can I get a standalone Tomcat to make use of JBoss.
|
| Obtaining the Context should be the same as obtaining the context for any stand alone application. i.e.
|
| Context ctx = new InitialContext() and make sure that you have a jndi.properties on the classpath of the web app, alternatively pass in the connection properties to the contructor.
|
| As described earlier in this post you will need to copy soem JBoss jars to the Tomcat installation.


The problem here, is that we want to connect a standAlone TOMCAT to our JBOSS (standing on a distant computer) and that without changing the application's code. just working on the configuration files of JBOSS...

View the original post : http://www.jboss.org/index.html? module=bb&op=viewtopic&p=3876280#3876280

Reply to the post : http://www.jboss.org/index.html? module=bb&op=posting&mode=reply&p=3876280


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user





------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id281&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to