|
Replies:
19
-
Last Post:
Jun 3, 2009 11:05 AM
by: dani_drio
|
|
|
|
|
|
|
Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 17, 2008 4:15 PM
|
|
|
Hi guys, I asked about this few days ago and I couldn´t get an answer to the issue:
I have a Glassfish server behind a router at the office. The router´s IP is 213.60.194.251, the server IP on the local Network is 192.168.1.11 when I download the client throught java web start at
http://213.60.194.251:8080/Xxxxx/Xxxxx-app-client
I get the exception below. I´ve tried this same story in three different servers from three different internet locations and I always come to the same story. Does anyone know what is going on???
Java Web Start 1.6.0_10-beta
Usar versión JRE 1.6.0_10-beta Java HotSpot(TM) Client VM
Directorio local del usuario = C:\Documents and Settings\usuario
----------------------------------------------------
c: borrar ventana de consola
f: finalizar objetos en la cola de finalización
g: liberación de recursos
h: presentar este mensaje de ayuda
m: imprimir sintaxis de memoria
o: activar registro
p: recargar configuración de proxy
q: ocultar consola
r: recargar configuración de norma
s: volcar propiedades del sistema y de despliegue
t: volcar lista de subprocesos
v: volcar pila de subprocesos
0-5: establecer nivel de rastreo en <n>
----------------------------------------------------
JNLP JREDesc in Component ignored: http://213.60.194.251:8080/__JWSappclients/__appserver/${appserver.mainext.jnlp.filename}
JNLP JREDesc in Component ignored: http://213.60.194.251:8080/__JWSappclients/__appserver/${appserver.mainext.jnlp.filename}
JNLP JREDesc in Component ignored: http://213.60.194.251:8080/__JWSappclients/__appserver/${appserver.mainext.jnlp.filename}
18-jul-2008 0:50:02 com.sun.enterprise.appclient.MainWithModuleSupport prepareSecurity
INFO: Security Manager is ON.
18-jul-2008 0:50:02 com.sun.enterprise.appclient.MainWithModuleSupport setTargetServerProperties
INFO: ACC001:Using ClientContainer file: [C:\DOCUME~1\usuario\CONFIG~1\Temp\sunacc44698.xml].
18-jul-2008 0:50:02 com.sun.enterprise.appclient.MainWithModuleSupport <init>
INFO: ACC024: IIOP endpoint(s) = 213.60.194.251:3700
18-jul-2008 0:50:36 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
ADVERTENCIA: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 192.168.1.11; port: 3920"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
at org.omg.CORBA.portable.ObjectImpl._is_a(Unknown Source)
at org.omg.CosNaming.NamingContextHelper.narrow(Unknown Source)
at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
at com.sun.enterprise.naming.SerialContext.getCachedProvider(SerialContext.java:247)
at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:205)
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.sun.enterprise.util.Utility.lookupObject(Utility.java:145)
at com.sun.enterprise.ServerConfiguration.<init>(ServerConfiguration.java:96)
at com.sun.enterprise.ServerConfiguration.getConfiguration(ServerConfiguration.java:80)
at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.createTransactionManager(J2EETransactionManagerImpl.java:294)
at com.sun.enterprise.appclient.AppContainer.initializeNaming(AppContainer.java:204)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:364)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.sun.enterprise.appclient.jws.boot.JWSACCMain.run(JWSACCMain.java:221)
at com.sun.enterprise.appclient.jws.boot.JWSACCMain.main(JWSACCMain.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection timed out: connect
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
... 34 more
Caused by: java.net.ConnectException: Connection timed out: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
... 35 more
Message was edited by: pablopina
Message was edited by: pablopina
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 18, 2008 3:05 PM
in response to: pablopina
|
|
|
Hi Pablo
Have you noticed these messages?:
INFO: ACC024: IIOP endpoint(s) = 213.60.194.251:3700
18-jul-2008 0:50:36 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
ADVERTENCIA: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 192.168.1.11; port: 3920"
It seems there is some kind of port connection failure. Maybe port 3920 or 3700 are not open or incorrectly NATted. Be sure the required port to be connected from the client is open on the router / firewall.
Aniceto Perez
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 18, 2008 5:11 PM
in response to: aperezymadrid
|
|
|
Hi aperez
( o quizá Hola Aniceto)
I can do telnet on port 3700 and my router /firewall is doing NAT on everything from 3700 to 4848 to the server, still, I can´t get it going. Have you ever run a client across the internet?
Pablo.
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 19, 2008 9:21 AM
in response to: pablopina
|
|
|
Pablo
Why log records two port numbers apparently related to IIOP? Which is your current configuration of IIOP ports in GF?
Consider that a web-start client application is a jnlp application, a downloaded application from the server running on your desktop machine. If that client application must connect with the server, the application must know how to do it: external IP and port and a firewall whith the right rules to enable and NAT those connections.
If you are interested in my experience with IIOP, I don't trust it to be used between applications running in two different machines. If you read some threads in this forum, you can see there are some problems when locating references not registered in the same jvm.
I suppose you have tested you application running the client and server in the same machine. I suggest to test the application with the client running in a different box inside tour local network and later put a router in the middle.
Ya me contarás
Aniceto Perez
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 19, 2008 10:07 AM
in response to: aperezymadrid
|
|
|
Hola Aniceto,
Thank you very much for noticing that about the ports I had not seen it before. I went to the server and I realised thre are three IIOP listeners and there was one on port 3920 it apparently is for SSL,
I just tried to run the client again to identify why was it trying to connect to that particular one and I realised that actually the client tries to connect to all three IIOP listeners at the following ports 3700, 3820 and 3920 and it gets the same exception from all three IIOP listeners.
We are running our EJB application on the local network with swing clients. It has been going very nicely (within the LAN) since two months. clients are downloaded with JavaWebStart and it runs excelently, even a JMS service we have setted up for the server to notify clients on certain events.
Theses is the full exception I get on the Java Console, first while trying to connect to 3700 then 3820 and lastly 3920, after that it tries to connect again to 3700 and so on.
Gracias.
JNLP JREDesc in Component ignored: http://vpina.mooo.com:8080/__JWSappclients/__appserver/${appserver.mainext.jnlp.filename}
19-jul-2008 18:41:28 com.sun.enterprise.appclient.MainWithModuleSupport prepareSecurity
INFO: Security Manager is ON.
19-jul-2008 18:41:28 com.sun.enterprise.appclient.MainWithModuleSupport setTargetServerProperties
INFO: ACC001:Using ClientContainer file: [C:\DOCUME~1\usuario\CONFIG~1\Temp\sunacc21833.xml].
19-jul-2008 18:41:29 com.sun.enterprise.appclient.MainWithModuleSupport <init>
INFO: ACC024: IIOP endpoint(s) = vpina.mooo.com:3700
19-jul-2008 18:42:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
ADVERTENCIA: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 192.168.1.11; port: 3700"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
at org.omg.CORBA.portable.ObjectImpl._is_a(Unknown Source)
at org.omg.CosNaming.NamingContextHelper.narrow(Unknown Source)
at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
at com.sun.enterprise.naming.SerialContext.getCachedProvider(SerialContext.java:247)
at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:205)
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.sun.enterprise.util.Utility.lookupObject(Utility.java:145)
at com.sun.enterprise.ServerConfiguration.<init>(ServerConfiguration.java:96)
at com.sun.enterprise.ServerConfiguration.getConfiguration(ServerConfiguration.java:80)
at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.createTransactionManager(J2EETransactionManagerImpl.java:294)
at com.sun.enterprise.appclient.AppContainer.initializeNaming(AppContainer.java:204)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:364)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.sun.enterprise.appclient.jws.boot.JWSACCMain.run(JWSACCMain.java:221)
at com.sun.enterprise.appclient.jws.boot.JWSACCMain.main(JWSACCMain.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection timed out: connect
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
... 34 more
Caused by: java.net.ConnectException: Connection timed out: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
... 35 more
19-jul-2008 18:46:07 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
ADVERTENCIA: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 192.168.1.11; port: 3820"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
at org.omg.CORBA.portable.ObjectImpl._is_a(Unknown Source)
at org.omg.CosNaming.NamingContextHelper.narrow(Unknown Source)
at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
at com.sun.enterprise.naming.SerialContext.getCachedProvider(SerialContext.java:247)
at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:205)
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.sun.enterprise.util.Utility.lookupObject(Utility.java:145)
at com.sun.enterprise.ServerConfiguration.<init>(ServerConfiguration.java:96)
at com.sun.enterprise.ServerConfiguration.getConfiguration(ServerConfiguration.java:80)
at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.createTransactionManager(J2EETransactionManagerImpl.java:294)
at com.sun.enterprise.appclient.AppContainer.initializeNaming(AppContainer.java:204)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:364)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.sun.enterprise.appclient.jws.boot.JWSACCMain.run(JWSACCMain.java:221)
at com.sun.enterprise.appclient.jws.boot.JWSACCMain.main(JWSACCMain.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection timed out: connect
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
... 34 more
Caused by: java.net.ConnectException: Connection timed out: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
... 35 more
19-jul-2008 18:46:41 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
ADVERTENCIA: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 192.168.1.11; port: 3920"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
at org.omg.CORBA.portable.ObjectImpl._is_a(Unknown Source)
at org.omg.CosNaming.NamingContextHelper.narrow(Unknown Source)
at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
at com.sun.enterprise.naming.SerialContext.getCachedProvider(SerialContext.java:247)
at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:205)
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.sun.enterprise.util.Utility.lookupObject(Utility.java:145)
at com.sun.enterprise.ServerConfiguration.<init>(ServerConfiguration.java:96)
at com.sun.enterprise.ServerConfiguration.getConfiguration(ServerConfiguration.java:80)
at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.createTransactionManager(J2EETransactionManagerImpl.java:294)
at com.sun.enterprise.appclient.AppContainer.initializeNaming(AppContainer.java:204)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:364)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.sun.enterprise.appclient.jws.boot.JWSACCMain.run(JWSACCMain.java:221)
at com.sun.enterprise.appclient.jws.boot.JWSACCMain.main(JWSACCMain.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection timed out: connect
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
... 34 more
Caused by: java.net.ConnectException: Connection timed out: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
... 35 more
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 19, 2008 5:48 PM
in response to: pablopina
|
|
|
did you modify your sun-acc.xml to point your client at the server?
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 20, 2008 3:36 PM
in response to: agyepong
|
|
|
No, i didn´t even know that file exists. I´ve just found it, thanks for that... still I am not certain the changes I should make, if any.
Can you help me with this, will the clients still work both inside the lan and over the internet, thank you?
<client-container>
<target-server name="equipo" address="equipo" port="3700"/>
<log-service file="" level="WARNING"/>
<message-security-config auth-layer="SOAP">
<!-- turned off by default -->
<provider-config class-name="com.sun.xml.wss.provider.ClientSecurityAuthModule" provider-id="XWS_ClientProvider" provider-type="client">
<request-policy auth-source="content"/>
<response-policy auth-source="content"/>
<property name="encryption.key.alias" value="s1as"/>
<property name="signature.key.alias" value="s1as"/>
<property name="dynamic.username.password" value="false"/>
<property name="debug" value="false"/>
</provider-config>
<provider-config class-name="com.sun.xml.wss.provider.ClientSecurityAuthModule" provider-id="ClientProvider" provider-type="client">
<request-policy auth-source="content"/>
<response-policy auth-source="content"/>
<property name="encryption.key.alias" value="s1as"/>
<property name="signature.key.alias" value="s1as"/>
<property name="dynamic.username.password" value="false"/>
<property name="debug" value="false"/>
<property name="security.config" value="C:/Sun/SDK/lib/appclient/wss-client-config-1.0.xml"/>
</provider-config>
</message-security-config>
</client-container>
Message was edited by: pablopina
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 22, 2008 12:21 PM
in response to: pablopina
|
|
|
I have been out of the office a few days and am only now able to respond.
Briefly...
1. The sun-acc.xml file is normally used only when you launch with the appclient command. The settings there are not used - currently - during a Java Web Start launch.
2. Using the build-in Java Web Start support (as it appears you are doing), the server automatically places the address of the server-side ORB into the generated JNLP document that launches the client. This value is obtained from the ORB logic on the server side.
I will let the ORB folks know of this forum post and let's see if they have anything to add.
- Tim
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 22, 2008 5:28 PM
in response to: tjquinn
|
|
|
Thank you so much Tim, I´ve been dragging this problem for around two months...
I tried changing names for I.P adresses on the sun-acc.xml but I got no success. The same story happend again, the application client tried to to establish a connection against a local adress and not against the remote router´s IP.
It would save us soooo much work to be eable to run our app clients across the internet,
Thank´s for your help Tim.
Pablo
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 23, 2008 8:49 PM
in response to: pablopina
|
|
|
I got exactly the same problem, then I used jdk 6u7 and app server 9.1.2.
this time I got different error. it did not even launch on the local network.
i found this problem the same as http://forums.java.net/jive/thread.jspa?threadID=44411&tstart=0
could this be a bug on JWS/JDK or my mistakes? I am more confused now.
could you try JDK 6u7 and see if we are on the same boat?
thanks, Tedjo
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 23, 2008 9:16 PM
in response to: bedjo
|
|
|
Yes, it's a different problem. Changes in Java Web Start from 6u6 to 6u7 have caused the problem discussed in the other thread.
I'm stilll in the process of looking into the details of those changes.
- Tim
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 24, 2008 1:25 PM
in response to: tjquinn
|
|
|
Since JWS directing to local IP, i wonder if enterprise app is designed to be installed only on local network?
if it is true, could we overcome this issue by setting up a VPN?
i never had any experience with VPN. but i'll find out how is gonna be. I read setting up VPN is pain in the as.
Thanks,
Tedjo
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 24, 2008 2:02 PM
in response to: bedjo
|
|
|
Using the Java Web Start feature across the network should not be a problem in general and should not require using a VPN.
Can you please do one thing? From the command line enter the
javaws -viewer
command. One of the two windows lists the apps that Java Web Start has downloaded. For your app, right-click on it and choose Show JNLP File. Look for any property definitions that refer to IIOP and post them here?
- Tim
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 24, 2008 11:00 PM
in response to: tjquinn
|
|
|
Tim, thank for your help.
here is the JLNP
<jnlp spec="1.0+" codebase="http://125.164.10.201:8080/__JWSappclients/__appclient/KWLog/KWLog-app-client/" href="http://125.164.10.201:8080/__JWSappclients/__appclient/KWLog/KWLog-app-client/main.jnlp">
<information>
<title>KWLog-app-client</title>
<vendor>Application Client</vendor>
<homepage href="http://125.164.10.201:8080/main-jnlp.html"/>
<description kind="short">Application description</description>
<description kind="one-line">KWLog-app-client</description>
<offline-allowed/>
</information>
<security>
<all-permissions/>
</security>
<update check="timeout" policy="always"/>
<resources>
<java version="1.5+"/>
<jar href="http://125.164.10.201:8080/__JWSappclients/__appserver/aslib/appserv-jwsacc.jar" download="eager" main="true"/>
<extension href="http://125.164.10.201:8080/__JWSappclients/__appclient/KWLog/KWLog-app-client/main-ext.jnlp" name="mainext"/>
<extension href="http://125.164.10.201:8080/__JWSappclients/__appclient/KWLog/KWLog-app-client/client-client.jnlp" name="appclient"/>
<property name="javax.xml.parsers.SAXParserFactory" value="com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl"/>
<property name="javax.xml.parsers.DocumentBuilderFactory" value="com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl"/>
<property name="javax.xml.transform.TransformerFactory" value="com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl"/>
<property name="org.xml.sax.parser" value="org.xml.sax.helpers.XMLReaderAdapter"/>
<property name="org.xml.sax.driver" value="com.sun.org.apache.xerces.internal.parsers.SAXParser"/>
<property name="java.util.logging.manager" value="com.sun.enterprise.server.logging.ACCLogManager"/>
<property name="javax.enterprise.resource.corba.level" value="FINE"/>
<property name="java.naming.factory.initial" value="com.sun.enterprise.naming.SerialInitContextFactory"/>
<property name="java.naming.factory.url.pkgs" value="com.sun.enterprise.naming"/>
<property name="java.naming.factory.state" value="com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl"/>
<property name="com.sun.aas.jws.iiop.defaultHost" value="125.164.10.201"/>
<property name="com.sun.aas.jws.iiop.defaultPort" value="3700"/>
<property name="com.sun.aas.jws.retainTempFiles" value="false"/>
<property name="com.sun.aas.jws.isJWS" value="true"/>
<property name="com.sun.aas.jws.download.host" value="125.164.10.201"/>
<property name="com.sun.aas.user.code.signed" value="true"/>
</resources>
<application-desc main-class="com.sun.enterprise.appclient.jws.boot.JWSACCMain">
<argument>-mainclass</argument>
<argument>KWLogAppClient.frmPassword</argument>
</application-desc>
</jnlp>
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 25, 2008 10:38 AM
in response to: bedjo
|
|
|
Early in the log output, the ACC reports the IIOP endpoint it will use as 125.164.10.201:3700. That is because the JNLP document includes the setting for the two IIOP-related properties.
Once the client-side ORB first contacts that server-side ORB, the ORBs exchange information including network information. It's possible that this information is using the local LAN address instead of the WAN address.
What I'm a little puzzled about is that the initial address - 125.164.10.201 - comes from server-side ORB-related logic.
Let me ping the ORB team again about this and see if they can shed some light on what might be happening.
- Tim
|
|
|
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 26, 2008 5:47 AM
in response to: tjquinn
|
|
|
THANKS TO TIM for the link and THANKS TO FLORIAN for the instructions.
It works eventually, eventhough it doesnt load smoothly.
at first JWS shows java.net.ConnectException: Connection timed out
but after 11 attempts, it loads the app. (thanks God I got stomach ache and went to toilet at that time)
well, i dont know why it shows connection time out. Is it maybe I am using dialup connection on the client? (and when I was downloading the app, I got stalled all the times. I have to connect the client pc to LAN first before launching it on dial up connection)
I think the problems could be on
1. Glassfish when producing extentions files. (directing to ORB listener IP)
2. JWS when downloading & connecting to the server.
Thanks
Tedjo
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jul 28, 2008 6:23 AM
in response to: bedjo
|
|
|
I don't know about the time-out. Dial-up could be a factor.
Just to add a little more background to what I think is happening...
When the app client container (ACC) starts up it contacts the server-side ORB using the IIOP endpoint(s) provided to it. If you launch using the appclient command the endpoint(s) come from the sun-acc.xml file. If you launch using Java Web Start the endpoint(s) come from the server and are assigned in the generated JNLP document that starts the client.
This initial contact is for "bootstrapping" the connection from the client ORB to an ORB on the back-end. Once this initial connection is made the ORB on the client side and the ORB on the server side exchange information about other ORBs in the same cluster as the one contacted initially. (If the server is not in a cluster then the client will not do any ORB fail-over or load balancing to the back-end.)
Also, the server-side ORB provides the client-side ORB with, essentially, network addresses where the remote EJBs and other resources can be reached. I think that this is where the problem with servers behind NAT firewalls comes in. The server-side ORB, in figuring out those addresses, uses the ORB settings in the configuration for the server (stored in domain.xml and settable using the admin GUI). These are defaulted to 0.0.0.0, and for a server behind a NAT firewall 0.0.0.0 gets translated to the servers's private LAN address, which of course are meaningless for the client which lies outside the firewall.
Florian's point is that by setting the ORB-related values in the server's configuration explicitly you can avoid the translation to the local, private address. Instead the ORB will use the value you set in the configuration.
Florian's further suggestion in his post is to create a DNS entry for the router using the router's outside address (a.b.c.d, not 192.168.x.y), set up address mapping in the router/firewall so requests to the GlassFish ports (including the ORB ports) are forwarded to the server, and specify the DNS name (instead of the default 0.0.0.0) in the GlassFish ORB configuration. I would think another way to do this, at least as a test, would be to use the public numeric IP address of the router in the GlassFish ORB settings. That avoids the need to create the DNS entry but obviously makes your configuration dependent on the numeric a.b.c.d address. If that is assigned dynamically (DHCP) then that is not very appealing. But people in this situation could try that as an experiment to see if that avoids the problem, at least until the router's outward IP address is changed.
I hope this helps explain what's going on.
- Tim
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Aug 29, 2008 10:43 AM
in response to: tjquinn
|
|
|
I started web service hello example in J2EE tutorial. I had a very similar problem. As I read this posting, I found a problem where sun-acc.xml in the domian1 directory did not have a correct URL to my laptop. After I corrected this wrong URL and restarted the glassfish server, the probelm was gone.
|
|
|
|
|
|
|
|
|
Re: Can´t launch GlassFish Application Client from behind a router
Posted:
Jun 3, 2009 11:05 AM
in response to: tjquinn
|
|
|
Hello, do you resolved these problems?
I have exactly the same problems and the time from user click to the web start application is running is unacceptable.
|
|
|
|
|
java.net RSS
