Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-3261

Serialization of EJB handles

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • No Release
    • JBossAS-3.2.8.SP1, JBossAS-4.0.4.GA
    • EJB2
    • None

    Description

      According to JBAS-1620, we have to use org.jboss.naming.NamingContextFactory to allow the handle to remember the JNDI environment that was in effect when it was created. But what about handles constructed inside the JBoss server JVM and later serialized into the client JVM? Each JVM may use different properties to access the JNDI - e.g. the "java.naming.provider.url" property, which is not available in the JBoss JVM but is required in a client JVM. Sure, I can add the "java.naming.provider.url" property to the $JBOSS_SERVER_HOME/conf/jndi.properties file, but as far as I know this forces in-VM calls to use RMI.

      Please have a look at the attached testcase (sources are included). The code works in our production environment (v3.2.7) but fails with the latest JBoss releases (4.0.4.GA and 3.2.8.SP1).

      Regards,
      lkral

      Attachments

        Issue Links

          Activity

            People

              starksm64 Scott Stark (Inactive)
              lkral_jira Lars Kral (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: