2 Replies Latest reply on Jun 24, 2002 4:34 PM by dsundstrom

    client throws an UnmarshalException

      Hi,

      When i try to launch a client, it display the following error message :


      javax.naming.CommunicationException. Root exception is java.rmi.UnmarshalExcept
      ion: error unmarshalling return; nested exception is:
      java.lang.ClassNotFoundException: org.jnp.interfaces.MarshalledValuePair
      (no security manager: RMI class loader disabled)
      java.lang.ClassNotFoundException: org.jnp.interfaces.MarshalledValuePair (no sec
      urity manager: RMI class loader disabled)
      at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:318)
      at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:132)
      at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.jav
      a:143)
      at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java
      :918)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
      at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
      at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:300)
      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:134)
      at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:365)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:349)
      at javax.naming.InitialContext.lookup(InitialContext.java:350)
      at annuaire.initComponents(annuaire.java:31)
      at annuaire.(annuaire.java:22)
      at annuaire.main(annuaire.java:59)


      I'm using JBoss3.0.0RC3 w/ Tomcat (binary downloaded from SourceForge)

      - Service file for the jdbc connection works fine.
      - Bean deployment works fine too
      - No error message displayed in the server terminal when the client fails

      the jndi.property file I use is :

      java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
      java.naming.provider.url=grsun36:1080
      java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces


      this bean and its clients works fine with 3.0.0beta (which i use before)


      thanks,
      ionel

        • 1. Re: client throws an UnmarshalException
          giorgio42


          Hi,

          I'm running into the same problem, but
          while I am accessing an external (federated) context.

          Have you been able to solve your problem?
          My application used to work with the betas, too.

          Currently I am using the 3.0.0 release.

          Any help would be greatly appreciated.

          Cheers
          Georg

          • 2. Re: client throws an UnmarshalException
            dsundstrom

            This is really not the right forum for this question; this forum is for database issues. My guess is the client and server code are out of sync. Pull the new client jars down to you client deployment and it will most likely start working again. If that doesn't fix it, try posting to the EJB forum.