Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-190

hashCode() fails when called on a @remote interface

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • EJB 3.0 Beta 1
    • Preview 5
    • EJB3 Extensions
    • None

      The following code from a remote client throws an exception within jBoss:

      InitialContext ctx = new InitialContext();
      MemoryRemote memory = (MemoryRemote) ctx.lookup(MemoryRemote.class.getName());
      memory.hashCode() <<----- FAILS

      This produces:

      15:03:41,793 INFO [STDOUT] java.lang.RuntimeException: Could not resolve beanClass method from proxy call
      15:03:41,793 INFO [STDOUT] at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:156
      )
      15:03:41,793 INFO [STDOUT] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:107)
      15:03:41,793 INFO [STDOUT] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationH
      andler.java:74)
      15:03:41,793 INFO [STDOUT] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:295)
      15:03:41,793 INFO [STDOUT] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:169)
      15:03:41,793 INFO [STDOUT] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:
      259)
      15:03:41,793 INFO [STDOUT] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:321)
      15:03:41,803 INFO [STDOUT] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:141)

      All the best,

      T

            kkhan1@redhat.com Kabir Khan
            janaudy Thierry Janaudy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: