All geek questions in one place

Access to ejb deployed in JBoss 7.0.1 from another client

By deploying the EJB module in JBoss 7.0.1, I am trying to access it from a client that is working on another JVM. However, I cannot understand which banks on the client side need to be added to my path to the client.

I tried with the following: -

  • JBoss-EJB-api_3.1_spec-1.0.1.Final.jar
  • JBoss-EJB-client-1.0.0.Beta11.jar 3.jboss-logging 3.1.0.CR2.jar
  • JBoss-sorting 1.3.4.GA.jar 5.jboss-sorting river-1.3.4.GA.jar
  • JBoss-Remoting-3.2.0.CR8.jar 7.jboss-SASL-1.0.0.Beta9.jar
  • JBoss transaction api_1.1_spec-1.0.0.Final.jar
  • xnio-api-3.0.0.CR7.jar

There seems to be some inconsistency in this setting, and I get this exception: -

INFO: JBoss EJB Client version 1.0.0.Beta11 November 9, 2012 12:01:04 org.xnio.Xnio INFO: XNIO version 3.0.0.CR7 November 9, 2012 12:01:04 AM org.jboss. ejb.client.ConfigBasedEJBClientContextSelector createConnections ERROR: Failed to create connection to connect named default java.lang.IllegalArgumentException: XNIO does not match the provider found in org.xnio.Xnio.doGetInstance (Xnio.java:192) in org.nnxxget (Xnio.java:146) at org.jboss.remoting3.Remoting.createEndpoint (Remoting.java:73)

...

I had no problems when the client got access to the ejb installed in JBoss 7.1.0 Final, JBoss 6.1.0 Final or Glassfish. Banks needed for war on the client side.

I am new to Java EE and application servers, and I try to learn in this process.

Thanks.

+4
source share
2 answers

add xnio-nio-3.0.3.GA.jar to your classpath

+10
source

In addition to Ramkumar's answer, I am adding a maven dependency for this jar. After maven dependency for jar:

<dependency> <groupId>org.jboss.xnio</groupId> <artifactId>xnio-nio</artifactId> <version>3.0.3.GA</version> </dependency>
+4
source

Source: https://habr.com/ru/post/1444903/

More articles:


All Articles