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

JBoss 6: NotSerializableException org.jboss.resource.work.JBossWorkManager

    Details

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Switch from JNDI/RMI to direct approach:

      • add:
        import org.jboss.mx.util.MBeanServerLocator;
      • change:
        InitialContext jndiContext = new InitialContext();
        MBeanServerConnection mconn = (MBeanServerConnection) jndiContext.lookup("jmx/invoker/RMIAdaptor");
        -->
        MBeanServer mconn = MBeanServerLocator.locateJBoss();

      in the referencing code

      Show
      Switch from JNDI/RMI to direct approach: add: import org.jboss.mx.util.MBeanServerLocator; change: InitialContext jndiContext = new InitialContext(); MBeanServerConnection mconn = (MBeanServerConnection) jndiContext.lookup("jmx/invoker/RMIAdaptor"); --> MBeanServer mconn = MBeanServerLocator.locateJBoss(); in the referencing code

      Description

      Use of JBoss JCA WorkManager via JNDI throws java.io.NotSerializableException: org.jboss.resource.work.JBossWorkManager at JBossAS 6.0.0
      Sample code (and known workaround) in the referenced forum thread.
      The currently known workaround is to use more direct approach but this introduces a direct dependency on the JBoss code. As this issue affects for example Spring Framework I'm affraid such workaround isn't sufficient here.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jesper.pedersen Jesper Pedersen
                Reporter:
                hostalp Petr Hostalek
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: