Uploaded image for project: 'HornetQ'
  1. HornetQ
  2. HORNETQ-782

HornetQObjectMessage cannot handle deserialization of its object whose class is loaded by an "isolated" classloader when HornetQ is running as a service in AS container

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: 2.2.6.Final
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Use the attached test. Steps:

      Start a AS 5 default profile with hornetq installed. Then unzip the test, run the following commands
      ant dist
      ant deploy
      ant test

      Observing the server console output, and you'll see the exception.

      Show
      Use the attached test. Steps: Start a AS 5 default profile with hornetq installed. Then unzip the test, run the following commands ant dist ant deploy ant test Observing the server console output, and you'll see the exception.

      Description

      When a class is loaded with an isolated deployment, it cannot be resolved by HornetQ as hornetq knows nothing of the class. When HornetQObjectMessage.getObject() is called, it will get ClassNotFound exception.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  gaohoward Yong Hao Gao
                  Reporter:
                  gaohoward Yong Hao Gao
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: