EJB invocation in wildfly 9.x from standalone application

[wasiuddin.qazi]

I am getting below during lookup below is my code i also kept jboss-ejb-client.properties in class path below is properties file i am passing to Initial context.

   Properties jndiProps = new Properties();

    jndiProps.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");

    jndiProps.put(Context.PROVIDER_URL,"http-remoting://localhost:4447");

    jndiProps.put(Context.SECURITY_PRINCIPAL, "admin");

    jndiProps.put(Context.SECURITY_CREDENTIALS, "admin");

    jndiProps.put("jboss.naming.client.ejb.context", true);

    Context  ctx = new InitialContext(jndiProps);

EJBSessionRemote libraryRemote= (EJBSessionRemote) ctx.lookup("EJBComponenet/EJBSession!com.test.EJBSessionRemote");

javax.naming.NamingException: Failed to connect to any server. Servers tried: [http-remoting://localhost:4447]

  at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)

[wasiuddin.qazi]

ANd same code is working on Jbos 6.1 EAP only i have change port 4447 for jboss.

[tomekadamski]

Hi Wasee,

Port 4447 is no longer used in default configuration and port 8080 to handle ejb invocations. Please change your configuration:

jndiProps.put(Context.PROVIDER_URL,"http-remoting://localhost:8080");

More details here: JNDI Lookup Failing

Regards,

Tomek

[wasiuddin.qazi]

Yes i have pointed to 8080 only for wildfly i was using 4447 for jboss.

[tomekadamski]

Why is there 4447 port in the stacktrace? What is the problem after changing port to 8080?

[wasiuddin.qazi]

Issue was with jboss-client.jar. Jboss jboss-client.jar was in my class path issue resolved after replaced with wildfly jar.

But now I am able invoke EJB even with wrong credential. How can I add security here?