java.net.SocketException: Connection reset by peer: JVM_recv
I am seeing this error in jboss output stream for Jboss 2.4.4:
[WARN,OILServerILService] Connection failure (1).
java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:86)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
at java.io.BufferedInputStream.read(BufferedInputStream.java:204)
at java.io.ObjectInputStream.peekCode(ObjectInputStream.java:1550)
at java.io.ObjectInputStream.refill(ObjectInputStream.java:1684)
at java.io.ObjectInputStream.read(ObjectInputStream.java:1660)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:1906)
at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:219)
at java.lang.Thread.run(Thread.java:484)
Client code is using the testQueue, here is snippit...
D:\jdk1.3.1_01\bin\javaw -classpath "D:\jms\OReilly\QueueTester\QueueTester\classes;D:\JBoss-2.4.4_Tomcat-3.2.3\jboss\lib\ext\jndi.jar;D:\JBoss-2.4.4_Tomcat-3.2.3\jboss\lib;D:\JBoss-2.4.4_Tomcat-3.2.3\jboss\lib\ext\jboss-j2ee.jar;D:\JBoss-2.4.4_Tomcat-3.2.3\jboss\lib\ext\jbossmq.jar;D:\JBoss-2.4.4_Tomcat-3.2.3\jboss\client\jnp-client.jar;D:\JBoss-2.4.4_Tomcat-3.2.3\jboss\client\jboss-client.jar;D:\JBoss-2.4.4_Tomcat-3.2.3\jboss\client\log4j.jar;D:\swiftmq_2_1_3\jars\jcert.jar;D:\swiftmq_2_1_3\jars\jms.jar;D:\swiftmq_2_1_3\jars\jndi.jar;D:\swiftmq_2_1_3\jars\jnet.jar;D:\swiftmq_2_1_3\jars\jsse.jar;D:\swiftmq_2_1_3\jars\jta-spec1_0_1.jar;D:\swiftmq_2_1_3\jars\smqclient.jar;D:\swiftmq_2_1_3\jars\swiftmq.jar;D:\jdk1.3.1_01\demo\jfc\Java2D\Java2Demo.jar;D:\jdk1.3.1_01\jre\lib\i18n.jar;D:\jdk1.3.1_01\jre\lib\jaws.jar;D:\jdk1.3.1_01\jre\lib\rt.jar;D:\jdk1.3.1_01\jre\lib\sunrsasign.jar;D:\jdk1.3.1_01\lib\dt.jar;D:\jdk1.3.1_01\lib\htmlconverter.jar;D:\jdk1.3.1_01\lib\tools.jar" -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_shmem,address=javadebug,suspend=y queuetester.QWholesaler testTopic scott scott
CODE:
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
env.put(Context.PROVIDER_URL, "localhost:1099");
env.put("java.naming.rmi.security.manager", "yes");
env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming");
jndi = new InitialContext(env);
tFactory =
(TopicConnectionFactory)jndi.lookup("TopicConnectionFactory");
qFactory =
(QueueConnectionFactory)jndi.lookup("QueueConnectionFactory");
tConnect = tFactory.createTopicConnection ();
qConnect = qFactory.createQueueConnection ();
tSession =
tConnect.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
qSession =
qConnect.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
>>>>> hotDealsTopic = (Topic)jndi.lookup("MyTestTopic"); >>>>> this line trows the exception...
receiveQueue = (Queue)jndi.lookup("MyTestQueue");
jboss.jmcl snippit...
I have the queue and topic defined in the jboss.jmcl file and see that number of queues and topics started...
<!-- The following three line create 3 topics named: testTopic, example, and bob -->
<!-- The following 9 line create 9 topics named: testQueue, controlQueue, A, B, -->
<!-- C, D, E, F, and ex -->
client stack trace...
javax.naming.NameNotFoundException: MyTestTopic not bound
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:245)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:349)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at queuetester.QWholesaler.(QWholesaler.java:84)
at queuetester.QWholesaler.main(QWholesaler.java:157)