This week's book giveaway is in the Python forum.
We're giving away four copies of Python Continuous Integration and Delivery and have Moritz Lenz on-line!
See this thread for details.
Win a copy of Python Continuous Integration and Delivery this week in the Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Devaka Cooray
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Tim Holloway
  • Claude Moore
  • Stephan van Hulst
Bartenders:
  • Winston Gutkowski
  • Carey Brown
  • Frits Walraven

18:37:59,950 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1)  RSS feed

 
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am trying stateless session bean  sample in jboss7.1 with eclipse.

Client application code  as  below.

public static void main(String[] args) {
try {
Properties props = new Properties();
props.setProperty("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
props.setProperty("java.naming.factory.url.pkgs",
"org.jboss.naming:org.jnp.interfaces");
props.setProperty("java.naming.provider.url", "localhost:9999");

InitialContext ctx = new InitialContext(props);
System.out.println("Initial context created");
ExampleBeanRemote exampleBean = (ExampleBeanRemote) ctx.lookup("ExampleBean/remote");
System.out.println("Message from Bean :" + exampleBean.getMessage());
} catch (NamingException e) {
e.printStackTrace();
}

}


I  am getting  the  below error, as well  as   the port  no :9999.is correct  or not.Kindly help me  to  solve this below issue


18:37:59,950 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host

 
Ranch Hand
Posts: 275
2
Fedora Netbeans IDE Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
put the whole log please
 
kannan vimal
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

serverside deployment

19:21:22,417 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
19:21:24,141 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
19:21:24,217 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
19:21:30,104 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
19:21:30,106 INFO  [org.xnio] XNIO Version 3.0.3.GA
19:21:30,167 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
19:21:30,237 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
19:21:30,308 INFO  [org.jboss.as.security] JBAS013101: Activating Security Subsystem
19:21:30,317 INFO  [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.
19:21:30,328 INFO  [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
19:21:30,329 INFO  [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem
19:21:30,330 INFO  [org.jboss.as.osgi] JBAS011940: Activating OSGi Subsystem
19:21:30,313 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
19:21:30,344 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
19:21:30,543 INFO  [org.jboss.as.connector] (MSC service thread 1-5) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
19:21:31,934 INFO  [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service
19:21:32,123 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
19:21:32,335 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
19:21:32,561 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
19:21:34,081 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
19:21:34,434 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
19:21:35,859 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\param\learning\softwares\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
19:21:35,867 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found EjbExample.jar in deployment directory. To trigger deployment create a file called EjbExample.jar.dodeploy
19:21:35,909 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:4447
19:21:35,909 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:9999
19:21:36,353 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "EjbExample.jar"
19:21:36,412 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry javax.ejb-3.1.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
19:21:36,413 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jboss-client.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
19:21:36,764 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ExampleBean in deployment unit deployment "EjbExample.jar" are as follows:

java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:module/ExampleBean!com.ejbs.ExampleBeanRemote
java:jboss/exported/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:module/ExampleBean!com.ejbs.ExampleBeanLocal

19:21:37,188 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015951: Admin console listening on http://127.0.0.1:9990
19:21:37,189 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 16009ms - Started 173 of 250 services (76 services are passive or on-demand)
19:21:37,274 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "EjbExample.jar"

After running  the client application
19:29:17,236 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
 
Al Hobbs
Ranch Hand
Posts: 275
2
Fedora Netbeans IDE Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What about the stacktrace for the exception? Anyway it's an io exception so something is wrong with whatever connection you are trying to make.  Maybe the url or port  or firewall or something else
 
kannan vimal
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Based  on the below url

https://stackoverflow.com/posts/30036591/edit


https://developer.jboss.org/thread/201728#sthash.o0m10eDj.dpuf


I changed the standalone.xml.

Now my entire trace as below
22:32:43,379 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
22:32:43,649 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
22:32:43,704 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
22:32:44,692 INFO  [org.xnio] XNIO Version 3.0.3.GA
22:32:44,692 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
22:32:44,704 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
22:32:44,713 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
22:32:44,744 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
22:32:44,749 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
22:32:44,757 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
22:32:44,782 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
22:32:44,788 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
22:32:44,806 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
22:32:44,854 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
22:32:44,865 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
22:32:44,889 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
22:32:44,941 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
22:32:45,067 INFO  [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service
22:32:45,079 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]
22:32:45,170 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
22:32:45,674 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
22:32:45,887 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory C:\param\learning\softwares\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
22:32:45,897 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found EjbExample.jar in deployment directory. To trigger deployment create a file called EjbExample.jar.dodeploy
22:32:45,906 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on localhost/127.0.0.1:4447
22:32:45,907 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:8999
22:32:46,086 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
22:32:46,146 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "EjbExample.jar"
22:32:46,194 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry javax.ejb-3.1.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
22:32:46,197 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jboss-client.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
22:32:46,394 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ExampleBean in deployment unit deployment "EjbExample.jar" are as follows:

java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:module/ExampleBean!com.ejbs.ExampleBeanRemote
java:jboss/exported/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:module/ExampleBean!com.ejbs.ExampleBeanLocal

22:32:46,606 INFO  [org.jboss.as] (MSC service thread 1-5) JBAS015951: Admin console listening on http://127.0.0.1:8990
22:32:46,608 INFO  [org.jboss.as] (MSC service thread 1-5) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3537ms - Started 173 of 250 services (76 services are passive or on-demand)
22:32:46,662 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "EjbExample.jar"
22:33:38,190 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:38:32,706 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:40:20,593 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:43:32,978 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:50:01,433 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host


 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!