Orbeon Forms community mailing list

Odd issue deploying under Websphere 6.1.013

Classic

List

Threaded

10 messages Options

Rodney Gitzel

Odd issue deploying under Websphere 6.1.013

There's no explanation I can think of for this, but in order to get orbeon.war (from orbeon-3.6.0.200712061930) to deploy under WAS 6.1.0.13 (with the web services fixpack) is to remove "jaxen-1_1_beta_9.jar" from the WAR and put it somewhere on the classpath manually. Seriously!

When I don't, I get the following exception:

java.lang.NoClassDefFoundError: org.jaxen.NamespaceContext
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:68)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:129)
at org.dom4j.DocumentFactory.createXPath(DocumentFactory.java:230)
at org.dom4j.tree.AbstractNode.createXPath(AbstractNode.java:207)
at org.orbeon.oxf.xml.XPathUtils.selectIterator(XPathUtils.java:70)
at org.orbeon.oxf.xml.XPathUtils.selectIterator(XPathUtils.java:43)

THAT makes no sense, especially given the exception is thrown from an orbeon jar in the same folder!

This occured both on my laptop and on one of our dev servers, so it's not just me. If put the jar outside the WAR, it works properly, in both cases.

Meanwhile, the original jar works fine as-is under vanilla Tomcat 5.5.

Weird.

rodney

Rodney Gitzel

Re: Odd issue deploying under Websphere 6.1.013

Incidentally, a co-worker swears that the WAR worked fine with no changes under WAS 6.1.0.9...

Erik Bruchez

Re: Re: Odd issue deploying under Websphere 6.1.013

Administrator

> Incidentally, a co-worker swears that the WAR worked fine with no
> changes
> under WAS 6.1.0.9...

This could happen if WAS has its own version of Jaxen in the path, or
some similar oddity.

You may want to try to tell your container to first load webapp
classes, then other classes. Most containers have such an option. This
sometimes fixes this kind of issues.

As a side note, the J2EE / JEE stuff completely missed the boat with
class loading since the beginning, and there is no end in sight for
class loading issues. A container should be *prevented* from exposing
its own classes to applications, unless explicitly requested by the
application. Oh well.

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Rodney Gitzel

Re: Re: Odd issue deploying under Websphere 6.1.0.13

Erik Bruchez wrote

This could happen if WAS has its own version of Jaxen in the path, or
some similar oddity.

That's what I thought, too, but I've found no trace of another version of Jaxen.

It's not the only problem, things get even stranger if you try to do a 'cross-context' app. I've sent the WARs off to a colleague who still has 6.1.0.9 installed to see if things are better there.

Tomcat should suffice for the prototype I'm working on, and if that's successful, then we'll assign some folks to dig into the WAS issue in more detail. So far it's definitely seems to be an issue with WAS 6.1.0.13, and not an issue with OPS.

If we come up with any solutions, I'll post them here. Otherwise, hopefully anyone else trying and failing will find this post and know they're not alone. ;-)

Thanks!

rodney

Erik Bruchez

Re: Re: Re: Odd issue deploying under Websphere 6.1.0.13

Administrator

Rodney,

That sounds good, please keep the list informed.

-Erik

On Feb 11, 2008, at 9:45 AM, Rodney Gitzel wrote:

>
>
> Erik Bruchez wrote:
>>
>> This could happen if WAS has its own version of Jaxen in the path, or
>> some similar oddity.
>>
>
> That's what I thought, too, but I've found no trace of another
> version of
> Jaxen.
>
> It's not the only problem, things get even stranger if you try to do a
> 'cross-context' app. I've sent the WARs off to a colleague who
> still has
> 6.1.0.9 installed to see if things are better there.
>
> Tomcat should suffice for the prototype I'm working on, and if that's
> successful, then we'll assign some folks to dig into the WAS issue
> in more
> detail. So far it's definitely seems to be an issue with WAS
> 6.1.0.13, and
> not an issue with OPS.
>
> If we come up with any solutions, I'll post them here. Otherwise,
> hopefully anyone else trying and failing will find this post and know
> they're not alone. ;-)
>
> Thanks!
>
> rodney

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Rodney Gitzel

Re: Re: Re: Odd issue deploying under Websphere 6.1.0.13

Good news, I guess, we are no longer having problems with 6.1.0.13. :-)

Bad news is I'm not sure why not. ;-) The only thing I can think is the version of Jaxen I was using. A coworker downloaded the OPS war and dropped in a 1.1 Jaxen jar and things went just fine: I had used a beta of 1.1.

So... it seems to work fine now, the only "change" needed is to add a Jaxen 1.1 jar file to the classpath.

rodney

Erik Bruchez wrote

Rodney,

That sounds good, please keep the list informed.

-Erik

On Feb 11, 2008, at 9:45 AM, Rodney Gitzel wrote:

>
>
> Erik Bruchez wrote:
>>
>> This could happen if WAS has its own version of Jaxen in the path, or
>> some similar oddity.
>>
>
> That's what I thought, too, but I've found no trace of another
> version of
> Jaxen.
>
> It's not the only problem, things get even stranger if you try to do a
> 'cross-context' app. I've sent the WARs off to a colleague who
> still has
> 6.1.0.9 installed to see if things are better there.
>
> Tomcat should suffice for the prototype I'm working on, and if that's
> successful, then we'll assign some folks to dig into the WAS issue
> in more
> detail. So far it's definitely seems to be an issue with WAS
> 6.1.0.13, and
> not an issue with OPS.
>
> If we come up with any solutions, I'll post them here. Otherwise,
> hopefully anyone else trying and failing will find this post and know
> they're not alone. ;-)
>
> Thanks!
>
> rodney

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Alessandro Vernet

Re: Re: Re: Re: Odd issue deploying under Websphere 6.1.0.13

Administrator

Rodney,

On Mon, May 26, 2008 at 10:57 AM, Rodney Gitzel <[hidden email]> wrote:
> Bad news is I'm not sure why not. ;-) The only thing I can think is the
> version of Jaxen I was using. A coworker downloaded the OPS war and dropped
> in a 1.1 Jaxen jar and things went just fine: I had used a beta of 1.1.
>
> So... it seems to work fine now, the only "change" needed is to add a Jaxen
> 1.1 jar file to the classpath.

Do you know if things are fine as well with 1.1.1? I'd rather upgrade
to 1.1.1 rather than 1.1 while we are at it. I read: "1.1.1 is a minor
upgrades that fixes assorted small bugs" and "1.1.1 is backwards
compatible with code written to the 1.0 APIs", which gives me reasons
to be optimistic.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Rodney Gitzel

Re: Re: Re: Re: Odd issue deploying under Websphere 6.1.0.13

Sorry, seems my memory is spotty these days. It wasn't an issue with the jaxen *beta* per se. Rather, for some unexplained reason Websphere does not see the jaxen jar file in the Orbeon war. Not at all.

I just tried this:

- removed jaxen from my WAS classpath, OPS fails to start due to "java.lang.NoClassDefFoundError: org.jaxen.NamespaceContext"

- put 1.1.1 jaxen jar into Orbeon WEB-INF/lib (removing the beta)... same exception

- take it right out, same exception

- put 1.1.1 in the WAS classpath, and OPS starts up just fine

?!?!?!?!?!?!?

I thought it might just be my workspace, but other co-workers find the same issue, and we also had to manually add the jaxen jar to the Websphere classpath on AIX. ?!?!?! It doesn't seem to be missing any other jars from WEB-INF/lib.

So, anyway, 1.1.1 is fine, AFAIK. And to get OPS running on late-model WebSphere you need to manually add a jaxen jar outside of the war.

*befuddled*

rodney

Alessandro Vernet wrote

Rodney,

On Mon, May 26, 2008 at 10:57 AM, Rodney Gitzel <rodney@dropd.com> wrote:
> Bad news is I'm not sure why not. ;-) The only thing I can think is the
> version of Jaxen I was using. A coworker downloaded the OPS war and dropped
> in a 1.1 Jaxen jar and things went just fine: I had used a beta of 1.1.
>
> So... it seems to work fine now, the only "change" needed is to add a Jaxen
> 1.1 jar file to the classpath.

Do you know if things are fine as well with 1.1.1? I'd rather upgrade
to 1.1.1 rather than 1.1 while we are at it. I read: "1.1.1 is a minor
upgrades that fixes assorted small bugs" and "1.1.1 is backwards
compatible with code written to the 1.0 APIs", which gives me reasons
to be optimistic.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet

--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

-----
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/

Jean Luc-2

Re: Re: Re: Re: Re: Odd issue deploying under Websphere 6.1.0.13

Check if the jars coming with Websphere don't already come with Jaxen (I had
a similar problem several years ago), either in its own jar or in jdom*.jar
Search in files for 'NamespaceContext.class' - the filenames are not
compressed in a zip.

Check the class loading order set for Orbeon. By default, it will be
parent-first, so if there is a Jaxen bundled with WAS, that one will be
loaded instead of the one inside Orbeon. Set the class-loading order to
child-first when you deploy Orbeon.
When you put jaxen 1.1.1 in the WAS classpath, it's a matter of chance that
that jar is loaded before the other bundled one so your application happens
to work (and other applications might break now).

----- Original Message -----
From: "Rodney Gitzel" <[hidden email]>
To: <[hidden email]>
Sent: Tuesday, May 27, 2008 2:33 PM
Subject: [ops-users] Re: Re: Re: Re: Odd issue deploying under Websphere
6.1.0.13

>
> Sorry, seems my memory is spotty these days. It wasn't an issue with the
> jaxen *beta* per se. Rather, for some unexplained reason Websphere does
> not
> see the jaxen jar file in the Orbeon war. Not at all.
>
> I just tried this:
>
> - removed jaxen from my WAS classpath, OPS fails to start due to
> "java.lang.NoClassDefFoundError: org.jaxen.NamespaceContext"
>
> - put 1.1.1 jaxen jar into Orbeon WEB-INF/lib (removing the beta)... same
> exception
>
> - take it right out, same exception
>
> - put 1.1.1 in the WAS classpath, and OPS starts up just fine
>
> ?!?!?!?!?!?!?
>
> I thought it might just be my workspace, but other co-workers find the
> same
> issue, and we also had to manually add the jaxen jar to the Websphere
> classpath on AIX. ?!?!?! It doesn't seem to be missing any other jars
> from WEB-INF/lib.
>
> So, anyway, 1.1.1 is fine, AFAIK. And to get OPS running on late-model
> WebSphere you need to manually add a jaxen jar outside of the war.
>
> *befuddled*
>
> rodney
>
>
>
>
> Alessandro Vernet wrote:
>>
>> Rodney,
>>
>> On Mon, May 26, 2008 at 10:57 AM, Rodney Gitzel <[hidden email]> wrote:
>>> Bad news is I'm not sure why not. ;-) The only thing I can think is
>>> the
>>> version of Jaxen I was using. A coworker downloaded the OPS war and
>>> dropped
>>> in a 1.1 Jaxen jar and things went just fine: I had used a beta of 1.1.
>>>
>>> So... it seems to work fine now, the only "change" needed is to add a
>>> Jaxen
>>> 1.1 jar file to the classpath.
>>
>> Do you know if things are fine as well with 1.1.1? I'd rather upgrade
>> to 1.1.1 rather than 1.1 while we are at it. I read: "1.1.1 is a minor
>> upgrades that fixes assorted small bugs" and "1.1.1 is backwards
>> compatible with code written to the 1.0 APIs", which gives me reasons
>> to be optimistic.
>>
>> Alex
>> --
>> Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
>> Orbeon's Blog: http://www.orbeon.com/blog/
>> Personal Blog: http://avernet.blogspot.com/
>> Twitter - http://twitter.com/avernet
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email] mailing
>> list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>
>>
>> -----
>> Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
>> http://www.orbeon.com/
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Odd-issue-deploying-under-Websphere-6.1.013-tp15325839p17497033.html
> Sent from the ObjectWeb OPS - Users mailing list archive at Nabble.com.
>
>

--------------------------------------------------------------------------------

>
> --
> You receive this message as a subscriber of the [hidden email] mailing
> list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Rodney Gitzel

Re: Re: Re: Re: Re: Odd issue deploying under Websphere 6.1.0.13

My assumption is that if Jaxen *were* included in the mass of WAS jars, then NamespaceContext wouldn't be missing. We ran into this with JAXB: if we don't explicitly add the JAXB jars to one of our apps, then it doesn't work on Tomcat (missing class errors) but works just fine on WAS, as WAS has JAXB buried in one of its monster jars.

On AIX we did have the class-loading order set to child-first, and that did NOT work, we had to set it to parent-first *and* put a Jaxen jar out on the WAS classpath.

I can't come up with any conceivable reason for WAS to not see the jar in WEB-INF/lib, so the only thing I can think of is the jar shipped with OPS is somehow rejected by WAS. Though of course I have yet to find anything in the log to that effect. Then again this morning I tried replacing the beta jar with the 1.1.1 jar, and that didn't work either.

Apparently there were no such issues with 6.1.0.9, so.... ????

rodney

Jean Luc wrote

Check if the jars coming with Websphere don't already come with Jaxen (I had
a similar problem several years ago), either in its own jar or in jdom*.jar
Search in files for 'NamespaceContext.class' - the filenames are not
compressed in a zip.

Check the class loading order set for Orbeon. By default, it will be
parent-first, so if there is a Jaxen bundled with WAS, that one will be
loaded instead of the one inside Orbeon. Set the class-loading order to
child-first when you deploy Orbeon.
When you put jaxen 1.1.1 in the WAS classpath, it's a matter of chance that
that jar is loaded before the other bundled one so your application happens
to work (and other applications might break now).