WildFly-从远程客户端调用EJB-操作失败,状态为WAITING [英] WildFly - EJB invocations from a remote client - Operation failed with status WAITING

查看:184
本文介绍了WildFly-从远程客户端调用EJB-操作失败,状态为WAITING的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

以下是我的代码来调用ejb,但是它等待连接并失败.我将端口更改为4447,但是没有运气.

Following is my code to invoke an ejb, but it wait for the connection and get failed. I changed the port to 4447 but no luck.

private DataGridService lookupRemoteEJB() throws NamingException {

    Context context = null;
    try {

        Properties clientProperties = new Properties();
        clientProperties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED", "false");
        clientProperties.put("remote.connections", "default");
        clientProperties.put("remote.connection.default.port", "4447");
        clientProperties.put("remote.connection.default.host", "127.0.0.1");
        clientProperties.put("remote.connection.default.username", "admin");
        clientProperties.put("remote.connection.default.password", "password");
        clientProperties.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS", "false");

        EJBClientConfiguration ejbClientConfiguration = new PropertiesBasedEJBClientConfiguration(clientProperties);
        ContextSelector<EJBClientContext> contextSelector = new ConfigBasedEJBClientContextSelector(ejbClientConfiguration);
        EJBClientContext.setSelector(contextSelector);

        Properties properties = new Properties();
        properties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
        context = new InitialContext(properties);

        String jndiName = "ejb:poc_ear-1.0/poc_ejbs-1.0//DataGridServiceImpl!com.oms.ejbs.DataGridService";
        System.out.println("____" + jndiName);

        return (DataGridService) context.lookup(jndiName);

    } finally {
        if (context != null) {
            context.close();
        }
    }
}

服务器控制台中用于无状态会话bean的JNDI.

JNDI in server console for the stateless session bean.

11:00:53,220 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean name
d DataGridServiceImpl in deployment unit subdeployment "poc_ejbs-1.0.jar" of deployment "poc_ear-1.0.ear" are as follows:

        java:global/poc_ear-1.0/poc_ejbs-1.0/DataGridServiceImpl!com.oms.ejbs.DataGridService
        java:app/poc_ejbs-1.0/DataGridServiceImpl!com.oms.ejbs.DataGridService
        java:module/DataGridServiceImpl!com.oms.ejbs.DataGridService
        java:jboss/exported/poc_ear-1.0/poc_ejbs-1.0/DataGridServiceImpl!com.oms.ejbs.DataGridService
        java:global/poc_ear-1.0/poc_ejbs-1.0/DataGridServiceImpl
        java:app/poc_ejbs-1.0/DataGridServiceImpl
        java:module/DataGridServiceImpl

11:00:53,284 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live
11:00:53,285 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [73e4f957-b7a5-11

错误跟踪:

____ejb:poc_ear-1.0/poc_ejbs-1.0//DataGridServiceImpl!com.oms.ejbs.DataGridService
Feb 19, 2015 10:48:33 AM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 2.0.1.Final
Feb 19, 2015 10:48:34 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.2.2.Final
Feb 19, 2015 10:48:36 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.2.2.Final
Feb 19, 2015 10:48:38 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version (unknown)
Feb 19, 2015 10:48:44 AM org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector setupEJBReceivers
WARN: Could not register a EJB receiver for connection to 127.0.0.1:1099
java.lang.RuntimeException: Operation failed with status WAITING
    at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:94)
    at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:77)
    at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
    at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:155)
    at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:115)
    at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:47)
    at org.jboss.ejb.client.EJBClientContext.getCurrent(EJBClientContext.java:271)
    at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:281)
    at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:176)
    at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)
    at com.sun.proxy.$Proxy0.getData(Unknown Source)
    at com.oms.client.EJBInvoker.main(EJBInvoker.java:40)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)

推荐答案

下面的行解决了我的问题,端口必须更改为8080

Following line solved my problem, port has to be changed to 8080

clientProperties.put("remote.connection.default.port", "8080");

这篇关于WildFly-从远程客户端调用EJB-操作失败,状态为WAITING的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆