JiBX

wrong Classloader used

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: JiBX 1.0.1
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    JBoss 4.0.4cr2
  • Number of attachments :
    0

Description

1) deploy ear using jibx deserialisation inside
2) undeploy the ear
3) deploy the same ear again

Now BindingDirectory.getFactory(class) leads to the following Exception:
"java.lang.ClassNotFoundException: Invalid use of destroyed classloader"

Jibx tries to load classes from the classloader used in 1) but this classloader is no longer valid.

The problem is a blocker for hot deployment, because the whole server needs to be restarted to be able to deploy the ear again.

Look at jaxb2; it seems like they had the same issue: https://jaxb.dev.java.net/faq/index.html
(Q. Why can't I cast the unmarshalled object into the generated type)

thx,
Bernhard

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dennis Sosnoski added a comment -

I'm not sure why this would occur offhand, but if you can send me full details (including stack trace) I should be able to find a way around the problem. Please first build the JiBX jars from your distribution with debug turned on so you'll see line numbers - this can be done by going into the unzipped build directory of the distribution and running "ant current".

Show
Dennis Sosnoski added a comment - I'm not sure why this would occur offhand, but if you can send me full details (including stack trace) I should be able to find a way around the problem. Please first build the JiBX jars from your distribution with debug turned on so you'll see line numbers - this can be done by going into the unzipped build directory of the distribution and running "ant current".
Hide
Permalink
Dennis Sosnoski added a comment -

After a look at the JiBX BindingDirectory.getFactory() code I suspect the problem is that the user passed in a class instance that came from the old classloader. Since there's been no response from the reporter to the request for more information I'm resolving this.

Show
Dennis Sosnoski added a comment - After a look at the JiBX BindingDirectory.getFactory() code I suspect the problem is that the user passed in a class instance that came from the old classloader. Since there's been no response from the reporter to the request for more information I'm resolving this.

People

  • Assignee:
    Dennis Sosnoski
    Reporter:
    Bernhard Neuhauser
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: