[Installation, Configuration & DEPLOYMENT] - connect over internet to jms queue
by jlashmet
Hi everyone,
So here is my setup. I've got jboss 4.0.3SP1 running on linux bound to port 192.168.1.2. I've configured my router to forward all ports to this ip address and I've turned off my firewall temporarily. I have a JMS queue running which I am able to send an receive messages from on any computer in my network by specifying 192.168.1.2 as the jndi provider url. Now I'm trying to connect to this same queue over the internet from a remote box, and I'm unable to even create the Initial Context. I get this error.
java.rmi.ConnectException: Connection refused to host: 192.168.1.2; nested exception is:
java.net.ConnectException: Connection timed out: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(Unknown Source)
Now, what is interesting is that in the jndi properties file I've specified my WAN ip address as the jndi provider url, but in the error message I see the internal 192.168.1.2 address. So I guess it is forwarding correctly at least. Also if from the remote machine I do telnet [wanip] 1099 I get this:
üÃÂsrâÂÂjava.rmi.MarshalledObject|âÂÂâ²ùÃÂcâ¿>âÂȉÂÂ¥Iâ¦hashlocBytestâ»[BobjBytesq~âºxpâ¨F)áurâ»[B
â¨ðTñâ»xp3üÃÂt"http://localhost.localdomain:8083/q~q~uq~âÂ¥âŸÃÂsr org.jnp.server.Namin
gServer_StubâÂȉ»xrjava.rmi.server.RemoteStubÃÂâ âÂÂâÂÂïÃÂeâ»xrâÂÂjava.rmi.server.RemoteObjec
tâÂÂaâ¤æ
a3â²âÂÂ¥xpw6
UnicastRef2
192.168.1.2â¦Jâ¤ÃÂ
1/âºâÂÂâ L+âÂÂÃÂâºx `L!t
Connection to host lost.
Any ideas why I can't connect?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191576#4191576
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191576
17 years, 7 months
[Installation, Configuration & DEPLOYMENT] - connect over internet to jms queue
by jlashmet
Hi everyone,
So here is my setup. I've got jboss 4.0.3SP1 running on linux bound to port 192.168.1.2. I've configured my router to forward all ports to this ip address and I've turned off my firewall temporarily. I have a JMS queue running which I am able to send an receive messages from on any computer in my network by specifying 192.168.1.2 as the jndi provider url. Now I'm trying to connect to this same queue over the internet from a remote box, and I'm unable to even create the Initial Context. I get this error.
java.rmi.ConnectException: Connection refused to host: 192.168.1.2; nested exception is:
java.net.ConnectException: Connection timed out: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(Unknown Source)
Now, what is interesting is that in the jndi properties file I've specified my WAN ip address as the jndi provider url, but in the error message I see the internal 192.168.1.2 address. So I guess it is forwarding correctly at least. Also if from the remote machine I do telnet [wanip] 1099 I get this:
üÃÂsrâÂÂjava.rmi.MarshalledObject|âÂÂâ²ùÃÂcâ¿>âÂȉÂÂ¥Iâ¦hashlocBytestâ»[BobjBytesq~âºxpâ¨F)áurâ»[B
â¨ðTñâ»xp3üÃÂt"http://localhost.localdomain:8083/q~q~uq~âÂ¥âŸÃÂsr org.jnp.server.Namin
gServer_StubâÂȉ»xrjava.rmi.server.RemoteStubÃÂâ âÂÂâÂÂïÃÂeâ»xrâÂÂjava.rmi.server.RemoteObjec
tâÂÂaâ¤æ
a3â²âÂÂ¥xpw6
UnicastRef2
192.168.1.2â¦Jâ¤ÃÂ
1/âºâÂÂâ L+âÂÂÃÂâºx `L!t
Connection to host lost.
Any ideas why I can't connect?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191575#4191575
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191575
17 years, 7 months
[JBoss Messaging] - Re: JBM deadlock cause by socket write
by lanceliao1
Thanks for reply.
We are using Remoting 2.2.2sp7. I make sure using thre same version of remoting on both client and server.The remoting-bisocket-service.xml file:
| <invoker transport="bisocket">
|
| <!-- There should be no reason to change these parameters - warning!
| Changing them may stop JBoss Messaging working correctly -->
| <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
| <attribute name="dataType" isParam="true">jms</attribute>
| <attribute name="socket.check_connection" isParam="true">false</attribute>
| <attribute name="timeout" isParam="true">0</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">4457</attribute>
| <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
| <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
| <attribute name="numberOfCallRetries" isParam="true">1</attribute>
| <attribute name="pingFrequency" isParam="true">214748364</attribute>
| <attribute name="pingWindowFactor" isParam="true">10</attribute>
| <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
| <!-- End immutable parameters -->
|
| <!-- Periodicity of client pings. Server window by default is twice this figure -->
| <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
|
| <!-- Number of seconds to wait for a connection in the client pool to become free -->
| <attribute name="numberOfRetries" isParam="true">10</attribute>
|
| <!-- Max Number of connections in client pool. This should be significantly higher than
| the max number of sessions/consumers you expect -->
| <attribute name="JBM_clientMaxPoolSize" isParam="true">1000</attribute>
| <!-- The maximum time to wait before timing out on trying to write a message to socket for delivery -->
| <attribute name="callbackTimeout">10000</attribute>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191574#4191574
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191574
17 years, 7 months
[Microcontainer] - BeanMetaData and management
by bob.mcwhirter
So, for the JBoss Rails deployers, I've taked the advice of Ales and Adrian, hopefully correctly, and am now deploying BeanMetaData instead of doing actual work in my deployers, where possible.
The BMD I'm returning are my "deployments" (is that the correct term?) that represents the actual running object. A Rails app. A set of scheduler tasks.
MC instantiates them and calls start(), everything is happy, and I've replaced a ServiceMetaData.
http://github.com/bobmcwhirter/jboss-rails/tree/master/src%2Fmain%2Fjava%...
But I've lost my visibility of my rails app deployment in the jmx-console.
I've attempted to add @JMX annotations, but got either a mixture of "nothing" or "already installed" errors.
I also tried to gain a clue about Scott's @ManagementObject/ManagedObject stuff, but also never got anything visible in the jmx-console.
Should I be looking for some other console (JOPR-embedded?), or is there some way to wire things up to automatically appear in JMX consoles?
Thanks!
-Bob
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191573#4191573
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191573
17 years, 7 months