名称 [ejb:..] 未绑定在此上下文中。在 Wildfly 中找不到 [ejb: ].]，根本原因是 javax.naming.NameNotFoundException

Question

我正在尝试在远程环境中调用我的 EJB，并且我使用 Wildfly 作为我的容器。

抱歉，这是我第一次尝试以远程方式调用 EJB。

我已使用以下说明在 Wildfly 中调用 EJB。 https://docs.jboss.org/author/display/WFLY8/EJB+invocations+from+a+remote+client+using+JNDI

但是，我在调用这些 EJB 时出错，我不知道我的配置出了什么问题。

查看下面的错误堆栈跟踪：

SEVERE: Servlet.service() for servlet [dispatcher] in context with path [/Project-demo] threw exception [Request processing failed; nested exception is javax.naming.NameNotFoundException: Name [ejb: /ImageService-1.0-SNAPSHOT//GrayscaleImageServiceImpl!com.project.imageservice.ImageManipulateService] is not bound in this Context. Unable to find [ejb: ].] with root cause
javax.naming.NameNotFoundException: Name [ejb: /ImageService-1.0-SNAPSHOT//GrayscaleImageServiceImpl!com.project.imageservice.ImageManipulateService] is not bound in this Context. Unable to find [ejb: ].
    at org.apache.naming.NamingContext.lookup(NamingContext.java:820)
    at org.apache.naming.NamingContext.lookup(NamingContext.java:168)
    at org.apache.naming.SelectorContext.lookup(SelectorContext.java:158)
    at javax.naming.InitialContext.lookup(InitialContext.java:417)
    at com.sketchy.remote.context.RemoteContext.lookupRemoteGrayscaleService(RemoteContext.java:30)
    at com.sketchy.controllers.ServiceController.grayscaleService(ServiceController.java:78)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205)
    at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133)
    at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97)
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827)
    at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738)
    at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:963)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
    at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:861)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
    at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
    at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1041)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:603)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:748)

我在远程服务器和客户端的界面：

public interface ImageManipulateService{
    public UploadedImage manipulate(UploadedImage img) throws IOException, Exception;
}

我在远程服务器（Wildfly）中的 EJB：

@Service
@Stateless
@Remote(ImageManipulateService.class)
public class GrayscaleImageServiceImpl implements ImageManipulateService{

    @Override
    public Object manipulate(Object img) throws IOException, Exception {
        ....
    }

}

客户端：

jboss-ejb-client.properties

remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false

remote.connections=default

remote.connection.default.host = localhost
remote.connection.default.port = 9090
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false

我一直在 tomcat 服务器 (:8080) 中运行我的客户端，我正在尝试通过 localhost:9090 在 Wildfly 上调用 EJB。 （对吗？）

我的 Maven 依赖项中也包含 jboss-client.jar。我 使用版本 4.0.2。 (jboss-client-4.0.2.jar)

我创建了一个 java 类，它会调用服务查找以便方便地调用它们。

public class RemoteContext {

    public static ImageManipulateService lookupRemoteGrayscaleService() throws NamingException {
        Hashtable jndiProperties = new Hashtable();
        jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
        Context context = new InitialContext(jndiProperties);

        String appName = "";
        String moduleName = "ImageService-1.0-SNAPSHOT";
        String distinctName = "";
        String beanName = "GrayscaleImageServiceImpl";
        String viewClassName = "com.project.imageservice.ImageManipulateService";

        return (ImageManipulateService) context.lookup("ejb: " + appName + "/" + moduleName + "/" + distinctName + "/" + beanName + "!" + viewClassName);
    }

    public static ImageManipulateService lookupRemoteTimestampService() throws NamingException {
        Hashtable jndiProperties = new Hashtable();
        jndiProperties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
        Context context = new InitialContext(jndiProperties);

        String appName = "";
        String moduleName = "ImageService-1.0-SNAPSHOT";
        String distinctName = "";
        String beanName = "TimestampImageServiceImpl";
        String viewClassName = "com.project.imageservice.ImageManipulateService";

        return (ImageManipulateService) context.lookup("ejb: " + appName + "/" + moduleName + "/" + distinctName + "/" + beanName + "!" + viewClassName);
    }


}

Answer 1

您的主要问题是您使用了错误的jboss-client.jar。您选择的那个是用于 JBoss 4.0.x 的，根本不适用于 WildFly。

如果您使用 Maven 构建，那么您将在客户端应用程序（即战争项目）中包含以下依赖项：

    <dependency>
        <groupId>org.wildfly</groupId>
        <artifactId>wildfly-ejb-client-bom</artifactId>
        <version>10.1.0.Final</version>
        <type>pom</type>
    </dependency>

但由于您似乎没有使用 Maven，因此替代方法是添加您将在 WildFly 安装的 bin/client/ 目录中找到的 jboss-client.jar。它是一个“uber-jar”，包含上面显示的 maven 依赖项定义的所有内容。

一旦您解决了这个问题，您可能需要一些有关 JNDI 名称的帮助。我们将能够通过您的 server.log 的部署输出来解决这个问题，它记录了您的所有 EJB 应用程序的 JNDI 名称。

Answer 2

如果您的 EJB 部署在一个战争中，那么 JNDI 名称中的应用程序名称应该是 empty。尽管您的appName 变量包含一个空字符串，但您在“ejb:”之后有一个空格字符。删除此空间，使其与文档中的一样：

ejb:/jboss-as-ejb-remote-app//CalculatorBean!org.jboss.as.quickstarts.ejb.remote.stateless.RemoteCalculator