glassfish
  1. glassfish
  2. GLASSFISH-20507

NullPointerException in RuntimeModelBuilder.java line 195

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: web_services
    • Labels:
      None
    • Environment:

      GlassFish 3.1.2.2, Win 7 Pro SP 1 (32 Bit), JDK 1.7.0_21

      Description

      Application is working well on GlassFish 3.1.1, but not on 3.1.2.2!

      When deploying on GlassFish 3.1.2.2 instead (with same environmental conditions), it crashes when JAXB-unmarshalling the exact same data! Since it works in GF 3.1.1, it seems GF 3.1.2.2 replaces working parts of JAXB by failing replacements!

      Simplified stack trace:

      com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder$IDTransducerImpl.parse() (line 195) <--- throws NPE here
      com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTransducedAccessorImpl.parse() (line 247)
      ...
      javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal() (line 219)
      de.quipsy.util.http.HttpClient (line ...) <--- catched in my code when doing marshaller.unmarshal(InputStream).

      Strange but true, this happens only with some XML content, but not with any other. And no, the InputStream is not null.

      We cannot migrate from 3.1.1 to 3.1.2.2 because of this issue!

      1. GF_20507.tar.gz
        2 kB
        Iaroslav Savytskyi

        Activity

        Hide
        kdevaras added a comment -

        I got caught up with urgent issues. I'm now back to this one.

        Strangely, I don't seem to be able to reproduce this issue anymore.
        I'm using the same steps you described in go.cmd. I've checked on both 3.1.2.7 and 3.1.2.8.

        Show
        kdevaras added a comment - I got caught up with urgent issues. I'm now back to this one. Strangely, I don't seem to be able to reproduce this issue anymore. I'm using the same steps you described in go.cmd. I've checked on both 3.1.2.7 and 3.1.2.8.
        Hide
        mkarg added a comment -

        kdevaras, I'm currently reviewing the list of issues I reported against GF4 and kindly like to ask for a status update on the following of your above comments: "This issue may be fixed in jaxb 2.2.8/2.2.9 as the Threadlocal strategy was reworked for an NPE. I'm trying to verify with that version.". Did you find the time for this test and hence can you confirm that the problem is gone in JAXB 2.2.9? Also I wonder what the correct way is to ask the GlassFish team to incorporate at least 2.2.9 in GF 4.0.1 / 4.1 (whom to ask for that)?

        Show
        mkarg added a comment - kdevaras, I'm currently reviewing the list of issues I reported against GF4 and kindly like to ask for a status update on the following of your above comments: "This issue may be fixed in jaxb 2.2.8/2.2.9 as the Threadlocal strategy was reworked for an NPE. I'm trying to verify with that version.". Did you find the time for this test and hence can you confirm that the problem is gone in JAXB 2.2.9? Also I wonder what the correct way is to ask the GlassFish team to incorporate at least 2.2.9 in GF 4.0.1 / 4.1 (whom to ask for that)?
        Hide
        kdevaras added a comment -

        Not sure if I can ask that.

        Even if the fix is merged after the release, I'll try to provide a patch that can applied.

        Thanks.

        Show
        kdevaras added a comment - Not sure if I can ask that. Even if the fix is merged after the release, I'll try to provide a patch that can applied. Thanks.
        Hide
        mkarg added a comment -

        Thanks for the status update.

        As GF-4.0.1 is soon to come, can you please inform GF team that 4.0.1 must not be published before your fix is merged into GF? I think it is really essential for GF as JAXB is a core technology. Without a recent status update they may think there will be no fix in time and publish without pulling latest JAXB. Thanks.

        Show
        mkarg added a comment - Thanks for the status update. As GF-4.0.1 is soon to come, can you please inform GF team that 4.0.1 must not be published before your fix is merged into GF? I think it is really essential for GF as JAXB is a core technology. Without a recent status update they may think there will be no fix in time and publish without pulling latest JAXB. Thanks.
        Hide
        kdevaras added a comment -

        Btw, Glassfish seems to be using 2.2.5-5.

        Show
        kdevaras added a comment - Btw, Glassfish seems to be using 2.2.5-5.

          People

          • Assignee:
            Iaroslav Savytskyi
            Reporter:
            mkarg
          • Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated: