Note that there are some explanatory texts on larger screens.

plurals
  1. POXML.loadString in WebSphere throws java.lang.VerifyError
    primarykey
    data
    text
    <p>I'm calling <code>XML.loadString(...)</code> in a MDB in WebSphere 6.1 ND. I'm getting <code>java.lang.VerifyError</code>, similar to that described in <a href="https://stackoverflow.com/questions/2861807/was-6-1-java-lang-verifyerror-class-loading-constraint-violated">this question</a>.</p> <p>The stacktrace is:</p> <pre><code>java.lang.VerifyError: class loading constraint violated (class: scala/collection/mutable/StringBuilder method: toSeq()Lscala/collection/Seq;) at pc: 0 at java.lang.J9VMInternals.verifyImpl(Native Method) at java.lang.J9VMInternals.verify(J9VMInternals.java:59) at java.lang.J9VMInternals.initialize(J9VMInternals.java:120) at scala.xml.parsing.FactoryAdapter.&lt;init&gt;(FactoryAdapter.scala:40) at scala.xml.parsing.NoBindingFactoryAdapter.&lt;init&gt;(NoBindingFactoryAdapter.scala:18) at scala.xml.factory.XMLLoader$class.adapter(XMLLoader.scala:24) at scala.xml.XML$.adapter(XML.scala:40) at scala.xml.factory.XMLLoader$class.loadXML(XMLLoader.scala:37) at scala.xml.XML$.loadXML(XML.scala:40) at scala.xml.factory.XMLLoader$class.loadString(XMLLoader.scala:59) at scala.xml.XML$.loadString(XML.scala:40) at my code </code></pre> <p>It happens if I use <code>ConstructingParser</code> too:</p> <pre><code>java.lang.VerifyError: class loading constraint violated (class: scala/collection/mutable/StringBuilder method: toSeq()Lscala/collection/Seq;) at pc: 0 at java.lang.J9VMInternals.verifyImpl(Native Method) at java.lang.J9VMInternals.verify(J9VMInternals.java:59) at java.lang.J9VMInternals.initialize(J9VMInternals.java:120) at scala.xml.parsing.MarkupParser$class.$init$(MarkupParser.scala:102) at scala.xml.parsing.ConstructingParser.&lt;init&gt;(ConstructingParser.scala:47) at scala.xml.parsing.ConstructingParser$.fromSource(ConstructingParser.scala:22) </code></pre> <p>I'm using Scala v2.9.0.1</p> <p>How can I diagnose this class linkage problem?</p> <p><strong>Edit #1</strong></p> <p>On some reflection I realised that the problem occured after an unrelated change. On a hunch I fully uninstalled the application from WAS and then reinstalled it. The problem was gone. The problem recurred after the next application <em>update</em> (i.e. overwrite).</p> <p>After several more hours, and other changes unlreated to Scala XML parsing, I forgot to uninstall/reinstall and did an update instead. The problem did not recur. I can no longer replicate the issue.</p> <p><strong>Edit #2</strong></p> <p>The problem came back and can not be solved with uninstall/reinstall alone. Retried with Scala 2.8.1, but the problem persists. Will now try uninstall/turn off server/delete temp files/reinstall/restart server. Wish me luck.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload