1 Reply Latest reply on Feb 8, 2002 11:11 AM by sergeibatiuk

    Problem connecting to JBossMQ from an applet

    sergeibatiuk

      Hello,

      I have created a Chat applet that uses JBossMQ. It works perfectly on localhost. However, when I run the applet from other hosts on the network, it doesn't work, and gives no error messages. What could be the problem?

      I use JBoss 2.4.3, jdk 1.3 on Windows 2000 Professional.

      My jsp page:

      <jsp:plugin type="applet"
      jreversion="1.2"
      code="bsv.chat.ChatApplet.class"
      archive="Chat.jar,jnp-client.jar,jbossmq-client.jar,jboss-j2ee.jar,log4j.jar"
      width="600"
      height="400"
      >
      </jsp:plugin>

      Please help!

      Sincerely,
      Sergei Batiuk.

        • 1. Re: Problem connecting to JBossMQ from an applet
          sergeibatiuk

          I have just found out that when a client from localhost connects to JBoss, JBossMQ says:

          [OILClientIL] ConnectionReceiverOILClient is connecting to: 192.168.0.16:1519
          (Please note that 192.168.0.16 is IP of my computer, where JBoss is running, i.e. my localhost).

          Now, when a client from a different host attempts to connect to JBoss ( NOT 192.168.0.16 ) it says:

          [OILClientIL] ConnectionReceiverOILClient is connecting to: 127.0.0.1:3890
          [ClientConsumer:ID3] Could not send messages to a receiver.
          java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server
          at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:98)

          at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:84)
          at org.jboss.mq.il.oil.OILClientIL.receive(OILClientIL.java:69)
          at org.jboss.mq.server.ClientConsumer.run(ClientConsumer.java:212)
          at java.lang.Thread.run(Thread.java:484)
          [JMSServer] The connection to client ID3 failed.

          I don't have any idea why it tries to connect to localhost, when the client is actually a remote machine....

          Any ideas?

          Sincerely,
          Sergei Batiuk.