Orbeon Forms community mailing list

Tomcat 500 Error with Nightly Build

classic Classic list List threaded Threaded
♦
♦
 10 messages Options
Jay Klehr
Reply | Threaded
Open this post in threaded view
♦
♦
|

Tomcat 500 Error with Nightly Build

Jay Klehr
Hello,
 
Been struggling with a Tomcat 500 error lately after installing a nightly build from last week (8/10/2006, right when it was announced that the minimal-js property was added).  Currently we're running today's build, but having the same problem (this particular app works ok on the nightly build from 8/4/2006, and nothing else was changed in the app other than updating Orbeon).
 
The error itself gives no explanation as to why it happened.  The mod_jk logs (serving with apache) show that Tomcat returned a 500 error.  I browsed through all the Tomcat logs (they're being generated through log4j) and don't see any reason why this error is being generated.
 
Another form we're serving is using an older version of Orbeon (though also a nightly build) and it works fine (through the same Tomcat and same Apache).
 
I was hoping that someone had some insight to offer as to how to figure out what is causing this error.  Perhaps there is a logging option I can enable, or a log I might've overlooked that would have this information in it.  To the devs: could this be an incompatible package issue in regards to the changes that were made for the new Javascript dynamic loading stuff?
 
Please help! :)
 
Jay


--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Erik Bruchez
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Tomcat 500 Error with Nightly Build

Erik Bruchez
Administrator
Jay,

To upgrade, be sure you update ops.jar and ops-resources-private.jar,
and also that you backup and then remove resources/ops and
resources/config/theme.

Besides packaging, there aren't any significant differences in the way
OPS serves pages, and exceptions caused by OPS should definitely show up
in logs.

Can you access your application without going through mod_jk? Maybe
Tomcat will give you a better error in this case (although I have some
doubts).

-Erik

Jay Klehr wrote:

> Hello,
>  
> Been struggling with a Tomcat 500 error lately after installing a
> nightly build from last week (8/10/2006, right when it was announced
> that the minimal-js property was added).  Currently we're running
> today's build, but having the same problem (this particular app works ok
> on the nightly build from 8/4/2006, and nothing else was changed in the
> app other than updating Orbeon).
>  
> The error itself gives no explanation as to why it happened.  The mod_jk
> logs (serving with apache) show that Tomcat returned a 500 error.  I
> browsed through all the Tomcat logs (they're being generated through
> log4j) and don't see any reason why this error is being generated.
>  
> Another form we're serving is using an older version of Orbeon (though
> also a nightly build) and it works fine (through the same Tomcat and
> same Apache).
>  
> I was hoping that someone had some insight to offer as to how to figure
> out what is causing this error.  Perhaps there is a logging option I can
> enable, or a log I might've overlooked that would have this information
> in it.  To the devs: could this be an incompatible package issue in
> regards to the changes that were made for the new Javascript dynamic
> loading stuff?
>  
> Please help! :)
>  
> Jay
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Jay Klehr
Reply | Threaded
Open this post in threaded view
♦
♦
|

RE: Tomcat 500 Error with Nightly Build

Jay Klehr
Erik,
 
Thanks for the reply, I was sure that everything was getting updated (and removed the two directories as well).  We use subversion and a nice diff tool when updating to the nightly builds to be sure that we get all the changes (and to merge any changes we've made to the files coming in).
 
I attempted dropping the application into Tomcat's webapps folder and hitting Tomcat on port 8080 (default) and ended up getting this exception (which was actually more verbose than before, to your surprise :)  ).
 

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException
        org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:146)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:74)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

root cause

java.lang.NullPointerException
        org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1774)
        org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1575)
        org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860)
        org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307)
        org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189)
        java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        org.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:242)
        org.apache.log4j.Category.forcedLog(Category.java:467)
        org.apache.log4j.Category.error(Category.java:394)
        org.orbeon.oxf.webapp.ProcessorService.serviceStaticError(ProcessorService.java:173)
        org.orbeon.oxf.webapp.ProcessorService.serviceError(ProcessorService.java:134)
        org.orbeon.oxf.webapp.ProcessorService.service(ProcessorService.java:106)
        org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:144)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:74)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

The other app (that's on the older version of Orbeon) started ok after being dumped into the webapp folder and being hit on port 8080.

It should be noted that the apps are nearly identical in functionality and setup.

Thanks,

Jay



________________________________

From: Erik Bruchez on behalf of Erik Bruchez
Sent: Mon 8/14/2006 4:42 PM
To: [hidden email]
Subject: Re: [ops-users] Tomcat 500 Error with Nightly Build



Jay,

To upgrade, be sure you update ops.jar and ops-resources-private.jar,
and also that you backup and then remove resources/ops and
resources/config/theme.

Besides packaging, there aren't any significant differences in the way
OPS serves pages, and exceptions caused by OPS should definitely show up
in logs.

Can you access your application without going through mod_jk? Maybe
Tomcat will give you a better error in this case (although I have some
doubts).

-Erik

Jay Klehr wrote:

> Hello,
>
> Been struggling with a Tomcat 500 error lately after installing a
> nightly build from last week (8/10/2006, right when it was announced
> that the minimal-js property was added).  Currently we're running
> today's build, but having the same problem (this particular app works ok
> on the nightly build from 8/4/2006, and nothing else was changed in the
> app other than updating Orbeon).
>
> The error itself gives no explanation as to why it happened.  The mod_jk
> logs (serving with apache) show that Tomcat returned a 500 error.  I
> browsed through all the Tomcat logs (they're being generated through
> log4j) and don't see any reason why this error is being generated.
>
> Another form we're serving is using an older version of Orbeon (though
> also a nightly build) and it works fine (through the same Tomcat and
> same Apache).
>
> I was hoping that someone had some insight to offer as to how to figure
> out what is causing this error.  Perhaps there is a logging option I can
> enable, or a log I might've overlooked that would have this information
> in it.  To the devs: could this be an incompatible package issue in
> regards to the changes that were made for the new Javascript dynamic
> loading stuff?
>
> Please help! :)
>
> Jay
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/





--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

winmail.dat (9K) Download Attachment
Jay Klehr
Reply | Threaded
Open this post in threaded view
♦
♦
|

RE: Tomcat 500 Error with Nightly Build

Jay Klehr
In reply to this post by Erik Bruchez
For some more testing, I took a completely default Orbeon install (from today's build) and dropped it into my Tomcat webapps folder and accessed it through port 8080 and it ran ok (examples portlet).
 
Something in our code doesn't seem to like the new code it seems.
 
Hope this helps some, I'll continue to dig around some.
 
Jay

________________________________

From: Erik Bruchez on behalf of Erik Bruchez
Sent: Mon 8/14/2006 4:42 PM
To: [hidden email]
Subject: Re: [ops-users] Tomcat 500 Error with Nightly Build



Jay,

To upgrade, be sure you update ops.jar and ops-resources-private.jar,
and also that you backup and then remove resources/ops and
resources/config/theme.

Besides packaging, there aren't any significant differences in the way
OPS serves pages, and exceptions caused by OPS should definitely show up
in logs.

Can you access your application without going through mod_jk? Maybe
Tomcat will give you a better error in this case (although I have some
doubts).

-Erik

Jay Klehr wrote:

> Hello,
>
> Been struggling with a Tomcat 500 error lately after installing a
> nightly build from last week (8/10/2006, right when it was announced
> that the minimal-js property was added).  Currently we're running
> today's build, but having the same problem (this particular app works ok
> on the nightly build from 8/4/2006, and nothing else was changed in the
> app other than updating Orbeon).
>
> The error itself gives no explanation as to why it happened.  The mod_jk
> logs (serving with apache) show that Tomcat returned a 500 error.  I
> browsed through all the Tomcat logs (they're being generated through
> log4j) and don't see any reason why this error is being generated.
>
> Another form we're serving is using an older version of Orbeon (though
> also a nightly build) and it works fine (through the same Tomcat and
> same Apache).
>
> I was hoping that someone had some insight to offer as to how to figure
> out what is causing this error.  Perhaps there is a logging option I can
> enable, or a log I might've overlooked that would have this information
> in it.  To the devs: could this be an incompatible package issue in
> regards to the changes that were made for the new Javascript dynamic
> loading stuff?
>
> Please help! :)
>
> Jay
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/





--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

winmail.dat (7K) Download Attachment
Erik Bruchez
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Tomcat 500 Error with Nightly Build

Erik Bruchez
Administrator
In reply to this post by Jay Klehr
Jay,

The last line in OPS code is:

org.orbeon.oxf.webapp.ProcessorService.serviceStaticError(ProcessorService.java:173)

this contains:

logger.error("Unable to load stylesheet error.css while serving static
error page. Resuming.", e);

So indirectly, the NPE comes from a call to log4j. I don't have more
insight at this point.

-Erik

Jay Klehr wrote:

> Erik,
>  
> Thanks for the reply, I was sure that everything was getting updated (and removed the two directories as well).  We use subversion and a nice diff tool when updating to the nightly builds to be sure that we get all the changes (and to merge any changes we've made to the files coming in).
>  
> I attempted dropping the application into Tomcat's webapps folder and hitting Tomcat on port 8080 (default) and ended up getting this exception (which was actually more verbose than before, to your surprise :)  ).
>  
>
> type Exception report
>
> message
>
> description The server encountered an internal error () that prevented it from fulfilling this request.
>
> exception
>
> javax.servlet.ServletException
> org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:146)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:74)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> root cause
>
> java.lang.NullPointerException
> org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1774)
> org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1575)
> org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860)
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307)
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189)
> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> org.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:242)
> org.apache.log4j.Category.forcedLog(Category.java:467)
> org.apache.log4j.Category.error(Category.java:394)
> org.orbeon.oxf.webapp.ProcessorService.serviceStaticError(ProcessorService.java:173)
> org.orbeon.oxf.webapp.ProcessorService.serviceError(ProcessorService.java:134)
> org.orbeon.oxf.webapp.ProcessorService.service(ProcessorService.java:106)
> org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:144)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:74)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> The other app (that's on the older version of Orbeon) started ok after being dumped into the webapp folder and being hit on port 8080.
>
> It should be noted that the apps are nearly identical in functionality and setup.
>
> Thanks,
>
> Jay
>
>
>
> ________________________________
>
> From: Erik Bruchez on behalf of Erik Bruchez
> Sent: Mon 8/14/2006 4:42 PM
> To: [hidden email]
> Subject: Re: [ops-users] Tomcat 500 Error with Nightly Build
>
>
>
> Jay,
>
> To upgrade, be sure you update ops.jar and ops-resources-private.jar,
> and also that you backup and then remove resources/ops and
> resources/config/theme.
>
> Besides packaging, there aren't any significant differences in the way
> OPS serves pages, and exceptions caused by OPS should definitely show up
> in logs.
>
> Can you access your application without going through mod_jk? Maybe
> Tomcat will give you a better error in this case (although I have some
> doubts).
>
> -Erik
>
> Jay Klehr wrote:
>> Hello,
>>
>> Been struggling with a Tomcat 500 error lately after installing a
>> nightly build from last week (8/10/2006, right when it was announced
>> that the minimal-js property was added).  Currently we're running
>> today's build, but having the same problem (this particular app works ok
>> on the nightly build from 8/4/2006, and nothing else was changed in the
>> app other than updating Orbeon).
>>
>> The error itself gives no explanation as to why it happened.  The mod_jk
>> logs (serving with apache) show that Tomcat returned a 500 error.  I
>> browsed through all the Tomcat logs (they're being generated through
>> log4j) and don't see any reason why this error is being generated.
>>
>> Another form we're serving is using an older version of Orbeon (though
>> also a nightly build) and it works fine (through the same Tomcat and
>> same Apache).
>>
>> I was hoping that someone had some insight to offer as to how to figure
>> out what is causing this error.  Perhaps there is a logging option I can
>> enable, or a log I might've overlooked that would have this information
>> in it.  To the devs: could this be an incompatible package issue in
>> regards to the changes that were made for the new Javascript dynamic
>> loading stuff?
>>
>> Please help! :)
>>
>> Jay
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> 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
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
> --
> Orbeon - XForms Everywhere:
> http://www.orbeon.com/blog/
>
>
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Jay Klehr
Reply | Threaded
Open this post in threaded view
♦
♦
|

RE: Tomcat 500 Error with Nightly Build

Jay Klehr
So far no luck here, but I did see another exception in the catalina.out log file when starting Tomcat.  This is running 8/12's nightly build, with my app (that throws the 500 error).  It's the only app in the webapps directory, not using apache.
 
Starting PresentationServer Release 3.0.1.200608120905
Initializing Resource Manager with: {org.orbeon.oxf.resources.WebAppResourceManagerImplServletContext=org.apache.catalina.core.ApplicationContextFacade@149105b, oxf.resources.priority.2=org.orbeon.oxf.resources.ClassLoaderResourceManagerFactory, oxf.resources.factory=org.orbeon.oxf.resources.PriorityResourceManagerFactory, oxf.resources.priority.1=org.orbeon.oxf.resources.WebAppResourceManagerFactory, oxf.resources.webapp.rootdir=/WEB-INF/resources}
log4j:ERROR exception setting timeout, shutting down server socket.
java.net.BindException: Address already in use
        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at java.net.ServerSocket.<init>(ServerSocket.java:97)
        at org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(SocketHubAppender.java:348)
        at java.lang.Thread.run(Thread.java:595)
IN CONFIGURE
cluster.journal.maxStore 65000
cluster.journal.shift 100

Is this related to the exception I pasted earlier?
 
Jay

________________________________

From: Erik Bruchez on behalf of Erik Bruchez
Sent: Mon 8/14/2006 6:39 PM
To: [hidden email]
Subject: Re: [ops-users] Tomcat 500 Error with Nightly Build



Jay,

The last line in OPS code is:

org.orbeon.oxf.webapp.ProcessorService.serviceStaticError(ProcessorService.java:173)

this contains:

logger.error("Unable to load stylesheet error.css while serving static
error page. Resuming.", e);

So indirectly, the NPE comes from a call to log4j. I don't have more
insight at this point.

-Erik

Jay Klehr wrote:

> Erik,
>
> Thanks for the reply, I was sure that everything was getting updated (and removed the two directories as well).  We use subversion and a nice diff tool when updating to the nightly builds to be sure that we get all the changes (and to merge any changes we've made to the files coming in).
>
> I attempted dropping the application into Tomcat's webapps folder and hitting Tomcat on port 8080 (default) and ended up getting this exception (which was actually more verbose than before, to your surprise :)  ).
>
>
> type Exception report
>
> message
>
> description The server encountered an internal error () that prevented it from fulfilling this request.
>
> exception
>
> javax.servlet.ServletException
>       org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:146)
>       javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>       org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:74)
>       javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> root cause
>
> java.lang.NullPointerException
>       org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1774)
>       org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1575)
>       org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860)
>       org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307)
>       org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189)
>       java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>       org.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:242)
>       org.apache.log4j.Category.forcedLog(Category.java:467)
>       org.apache.log4j.Category.error(Category.java:394)
>       org.orbeon.oxf.webapp.ProcessorService.serviceStaticError(ProcessorService.java:173)
>       org.orbeon.oxf.webapp.ProcessorService.serviceError(ProcessorService.java:134)
>       org.orbeon.oxf.webapp.ProcessorService.service(ProcessorService.java:106)
>       org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:144)
>       javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>       org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:74)
>       javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> The other app (that's on the older version of Orbeon) started ok after being dumped into the webapp folder and being hit on port 8080.
>
> It should be noted that the apps are nearly identical in functionality and setup.
>
> Thanks,
>
> Jay
>
>
>
> ________________________________
>
> From: Erik Bruchez on behalf of Erik Bruchez
> Sent: Mon 8/14/2006 4:42 PM
> To: [hidden email]
> Subject: Re: [ops-users] Tomcat 500 Error with Nightly Build
>
>
>
> Jay,
>
> To upgrade, be sure you update ops.jar and ops-resources-private.jar,
> and also that you backup and then remove resources/ops and
> resources/config/theme.
>
> Besides packaging, there aren't any significant differences in the way
> OPS serves pages, and exceptions caused by OPS should definitely show up
> in logs.
>
> Can you access your application without going through mod_jk? Maybe
> Tomcat will give you a better error in this case (although I have some
> doubts).
>
> -Erik
>
> Jay Klehr wrote:
>> Hello,
>>
>> Been struggling with a Tomcat 500 error lately after installing a
>> nightly build from last week (8/10/2006, right when it was announced
>> that the minimal-js property was added).  Currently we're running
>> today's build, but having the same problem (this particular app works ok
>> on the nightly build from 8/4/2006, and nothing else was changed in the
>> app other than updating Orbeon).
>>
>> The error itself gives no explanation as to why it happened.  The mod_jk
>> logs (serving with apache) show that Tomcat returned a 500 error.  I
>> browsed through all the Tomcat logs (they're being generated through
>> log4j) and don't see any reason why this error is being generated.
>>
>> Another form we're serving is using an older version of Orbeon (though
>> also a nightly build) and it works fine (through the same Tomcat and
>> same Apache).
>>
>> I was hoping that someone had some insight to offer as to how to figure
>> out what is causing this error.  Perhaps there is a logging option I can
>> enable, or a log I might've overlooked that would have this information
>> in it.  To the devs: could this be an incompatible package issue in
>> regards to the changes that were made for the new Javascript dynamic
>> loading stuff?
>>
>> Please help! :)
>>
>> Jay
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> 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
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
> --
> Orbeon - XForms Everywhere:
> http://www.orbeon.com/blog/
>
>
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/





--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

winmail.dat (14K) Download Attachment
Erik Bruchez
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Tomcat 500 Error with Nightly Build

Erik Bruchez
Administrator
Jay,

As the exception indicates, your Tomcat starts listening on a port that
is already in use by something else on your machine. This has nothing to
do with OPS. You will have to identify what port this is. In particular,
look at your Tomcat's server.xml to figure out what ports are used by
connectors.

-Erik

Jay Klehr wrote:

> So far no luck here, but I did see another exception in the catalina.out log file when starting Tomcat.  This is running 8/12's nightly build, with my app (that throws the 500 error).  It's the only app in the webapps directory, not using apache.
>  
> Starting PresentationServer Release 3.0.1.200608120905
> Initializing Resource Manager with: {org.orbeon.oxf.resources.WebAppResourceManagerImplServletContext=org.apache.catalina.core.ApplicationContextFacade@149105b, oxf.resources.priority.2=org.orbeon.oxf.resources.ClassLoaderResourceManagerFactory, oxf.resources.factory=org.orbeon.oxf.resources.PriorityResourceManagerFactory, oxf.resources.priority.1=org.orbeon.oxf.resources.WebAppResourceManagerFactory, oxf.resources.webapp.rootdir=/WEB-INF/resources}
> log4j:ERROR exception setting timeout, shutting down server socket.
> java.net.BindException: Address already in use
>         at java.net.PlainSocketImpl.socketBind(Native Method)
>         at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
>         at java.net.ServerSocket.bind(ServerSocket.java:319)
>         at java.net.ServerSocket.<init>(ServerSocket.java:185)
>         at java.net.ServerSocket.<init>(ServerSocket.java:97)
>         at org.apache.log4j.net.SocketHubAppender$ServerMonitor.run(SocketHubAppender.java:348)
>         at java.lang.Thread.run(Thread.java:595)
> IN CONFIGURE
> cluster.journal.maxStore 65000
> cluster.journal.shift 100
>
> Is this related to the exception I pasted earlier?
>  
> Jay
>
> ________________________________
>
> From: Erik Bruchez on behalf of Erik Bruchez
> Sent: Mon 8/14/2006 6:39 PM
> To: [hidden email]
> Subject: Re: [ops-users] Tomcat 500 Error with Nightly Build
>
>
>
> Jay,
>
> The last line in OPS code is:
>
> org.orbeon.oxf.webapp.ProcessorService.serviceStaticError(ProcessorService.java:173)
>
> this contains:
>
> logger.error("Unable to load stylesheet error.css while serving static
> error page. Resuming.", e);
>
> So indirectly, the NPE comes from a call to log4j. I don't have more
> insight at this point.
>
> -Erik
>
> Jay Klehr wrote:
>> Erik,
>>
>> Thanks for the reply, I was sure that everything was getting updated (and removed the two directories as well).  We use subversion and a nice diff tool when updating to the nightly builds to be sure that we get all the changes (and to merge any changes we've made to the files coming in).
>>
>> I attempted dropping the application into Tomcat's webapps folder and hitting Tomcat on port 8080 (default) and ended up getting this exception (which was actually more verbose than before, to your surprise :)  ).
>>
>>
>> type Exception report
>>
>> message
>>
>> description The server encountered an internal error () that prevented it from fulfilling this request.
>>
>> exception
>>
>> javax.servlet.ServletException
>>       org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:146)
>>       javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>       org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:74)
>>       javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>
>> root cause
>>
>> java.lang.NullPointerException
>>       org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1774)
>>       org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1575)
>>       org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860)
>>       org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307)
>>       org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189)
>>       java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>>       org.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:242)
>>       org.apache.log4j.Category.forcedLog(Category.java:467)
>>       org.apache.log4j.Category.error(Category.java:394)
>>       org.orbeon.oxf.webapp.ProcessorService.serviceStaticError(ProcessorService.java:173)
>>       org.orbeon.oxf.webapp.ProcessorService.serviceError(ProcessorService.java:134)
>>       org.orbeon.oxf.webapp.ProcessorService.service(ProcessorService.java:106)
>>       org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:144)
>>       javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>       org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:74)
>>       javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>
>> The other app (that's on the older version of Orbeon) started ok after being dumped into the webapp folder and being hit on port 8080.
>>
>> It should be noted that the apps are nearly identical in functionality and setup.
>>
>> Thanks,
>>
>> Jay
>>
>>
>>
>> ________________________________
>>
>> From: Erik Bruchez on behalf of Erik Bruchez
>> Sent: Mon 8/14/2006 4:42 PM
>> To: [hidden email]
>> Subject: Re: [ops-users] Tomcat 500 Error with Nightly Build
>>
>>
>>
>> Jay,
>>
>> To upgrade, be sure you update ops.jar and ops-resources-private.jar,
>> and also that you backup and then remove resources/ops and
>> resources/config/theme.
>>
>> Besides packaging, there aren't any significant differences in the way
>> OPS serves pages, and exceptions caused by OPS should definitely show up
>> in logs.
>>
>> Can you access your application without going through mod_jk? Maybe
>> Tomcat will give you a better error in this case (although I have some
>> doubts).
>>
>> -Erik
>>
>> Jay Klehr wrote:
>>> Hello,
>>>
>>> Been struggling with a Tomcat 500 error lately after installing a
>>> nightly build from last week (8/10/2006, right when it was announced
>>> that the minimal-js property was added).  Currently we're running
>>> today's build, but having the same problem (this particular app works ok
>>> on the nightly build from 8/4/2006, and nothing else was changed in the
>>> app other than updating Orbeon).
>>>
>>> The error itself gives no explanation as to why it happened.  The mod_jk
>>> logs (serving with apache) show that Tomcat returned a 500 error.  I
>>> browsed through all the Tomcat logs (they're being generated through
>>> log4j) and don't see any reason why this error is being generated.
>>>
>>> Another form we're serving is using an older version of Orbeon (though
>>> also a nightly build) and it works fine (through the same Tomcat and
>>> same Apache).
>>>
>>> I was hoping that someone had some insight to offer as to how to figure
>>> out what is causing this error.  Perhaps there is a logging option I can
>>> enable, or a log I might've overlooked that would have this information
>>> in it.  To the devs: could this be an incompatible package issue in
>>> regards to the changes that were made for the new Javascript dynamic
>>> loading stuff?
>>>
>>> Please help! :)
>>>
>>> Jay
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> --
>>> 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
>>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>
>> --
>> Orbeon - XForms Everywhere:
>> http://www.orbeon.com/blog/
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> 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
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
> --
> Orbeon - XForms Everywhere:
> http://www.orbeon.com/blog/
>
>
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Arnout Engelen
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Tomcat 500 Error with Nightly Build

Arnout Engelen
In reply to this post by Jay Klehr
Jay Klehr schreef:
> java.net.BindException: Address already in use
>  

Sounds to me like there's another instance of Tomcat already running.
Try shutting that one down first before starting a new one.


Arnout



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Jay Klehr
Reply | Threaded
Open this post in threaded view
♦
♦
|

RE: Tomcat 500 Error with Nightly Build

Jay Klehr
In reply to this post by Jay Klehr
Alright, so I've started with a fresh copy of Tomcat 5.5, and dug around some to figure out how to watch Orbeon's logs and have some more information here.
 
First, when I start Tomcat, Orbeon spits this out at the end of the log (logging is set to debug level):
 
main WARN  http.Descriptor - giving up unable to read descriptor file

Not sure if that's normal or not, everything else I saw was either DEBUG or INFO level.
 
When hitting my app, this exception comes up:
 
http-8080-Processor25 ERROR webapp.ProcessorService - Exception at oxf:/config/epilogue.xpl, line 41, column 58, description reading processor output
org.orbeon.oxf.resources.ResourceNotFoundException: Cannot load "/ops/pfc/xforms-epilogue.xpl" with webapp loader
        at org.orbeon.oxf.resources.WebAppResourceManagerImpl.getContentAsStream(WebAppResourceManagerImpl.java:74)
        at org.orbeon.oxf.resources.ResourceManagerBase.getContentAsSAX(ResourceManagerBase.java:133)
        at org.orbeon.oxf.resources.PriorityResourceManagerImpl$4.run(PriorityResourceManagerImpl.java:105)
        at org.orbeon.oxf.resources.PriorityResourceManagerImpl.delegate(PriorityResourceManagerImpl.java:254)
        at org.orbeon.oxf.resources.PriorityResourceManagerImpl.getContentAsSAX(PriorityResourceManagerImpl.java:103)
        at org.orbeon.oxf.processor.generator.URLGenerator$OXFResourceHandler.readXML(URLGenerator.java:655)
        at org.orbeon.oxf.processor.generator.URLGenerator$1.readImpl(URLGenerator.java:402)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.validation.MSVValidationProcessor.access$700(MSVValidationProcessor.java:44)
        at org.orbeon.oxf.processor.validation.MSVValidationProcessor$5.readImpl(MSVValidationProcessor.java:219)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.access$1000(PipelineProcessor.java:66)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$5.readImpl(PipelineProcessor.java:457)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsDOM4J(ProcessorImpl.java:403)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsDOM4J(ProcessorImpl.java:412)
        at org.orbeon.oxf.processor.pipeline.PipelineReader.start(PipelineReader.java:79)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.readPipelineConfig(PipelineProcessor.java:469)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.access$2300(PipelineProcessor.java:66)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$9.read(PipelineProcessor.java:626)
        at org.orbeon.oxf.processor.ProcessorImpl.readCacheInputAsObject(ProcessorImpl.java:470)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:622)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$1.getInput(PipelineProcessor.java:140)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$1.readImpl(PipelineProcessor.java:89)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.access$1500(PipelineProcessor.java:66)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$6.run(PipelineProcessor.java:572)
        at org.orbeon.oxf.processor.ProcessorImpl.executeParents(ProcessorImpl.java:554)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.access$1600(PipelineProcessor.java:66)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$InternalTopOutput.readImpl(PipelineProcessor.java:568)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.access$1500(PipelineProcessor.java:66)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$6.run(PipelineProcessor.java:572)
        at org.orbeon.oxf.processor.ProcessorImpl.executeParents(ProcessorImpl.java:554)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.access$1600(PipelineProcessor.java:66)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$InternalTopOutput.readImpl(PipelineProcessor.java:568)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.pipeline.TeeProcessor.access$100(TeeProcessor.java:36)
        at org.orbeon.oxf.processor.pipeline.TeeProcessor$1.readImpl(TeeProcessor.java:59)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsDOM4J(ProcessorImpl.java:403)
        at org.orbeon.oxf.processor.ProcessorImpl$4.read(ProcessorImpl.java:427)
        at org.orbeon.oxf.processor.ProcessorImpl.readCacheInputAsObject(ProcessorImpl.java:470)
        at org.orbeon.oxf.processor.ProcessorImpl.readCacheInputAsDOM4J(ProcessorImpl.java:425)
        at org.orbeon.oxf.processor.pipeline.choose.ConcreteChooseProcessor.start(ConcreteChooseProcessor.java:186)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$11.run(PipelineProcessor.java:652)
        at org.orbeon.oxf.processor.ProcessorImpl.executeChildren(ProcessorImpl.java:536)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:649)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$11.run(PipelineProcessor.java:652)
        at org.orbeon.oxf.processor.ProcessorImpl.executeChildren(ProcessorImpl.java:536)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:649)
        at org.orbeon.oxf.processor.pipeline.choose.ConcreteChooseProcessor.start(ConcreteChooseProcessor.java:233)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$11.run(PipelineProcessor.java:652)
        at org.orbeon.oxf.processor.ProcessorImpl.executeChildren(ProcessorImpl.java:536)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:649)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$11.run(PipelineProcessor.java:652)
        at org.orbeon.oxf.processor.ProcessorImpl.executeChildren(ProcessorImpl.java:536)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:649)
        at org.orbeon.oxf.processor.pipeline.choose.ConcreteChooseProcessor.start(ConcreteChooseProcessor.java:233)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$11.run(PipelineProcessor.java:652)
        at org.orbeon.oxf.processor.ProcessorImpl.executeChildren(ProcessorImpl.java:536)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:649)
        at org.orbeon.oxf.processor.PageFlowControllerProcessor.start(PageFlowControllerProcessor.java:417)
        at org.orbeon.oxf.pipeline.InitUtils.runProcessor(InitUtils.java:86)
        at org.orbeon.oxf.webapp.ProcessorService.service(ProcessorService.java:95)
        at org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:147)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:75)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:595)

 
And another one a bit later after that:
 
 
http-8080-Processor25 ERROR webapp.ProcessorService - Exception at oxf:/config/error.xpl, line 53, column 44, description reading processor output
org.orbeon.oxf.resources.ResourceNotFoundException: Cannot load "/config/theme/theme.xsl" with webapp loader
        at org.orbeon.oxf.resources.WebAppResourceManagerImpl.getContentAsStream(WebAppResourceManagerImpl.java:74)
        at org.orbeon.oxf.resources.ResourceManagerBase.getContentAsSAX(ResourceManagerBase.java:133)
        at org.orbeon.oxf.resources.PriorityResourceManagerImpl$4.run(PriorityResourceManagerImpl.java:105)
        at org.orbeon.oxf.resources.PriorityResourceManagerImpl.delegate(PriorityResourceManagerImpl.java:254)
        at org.orbeon.oxf.resources.PriorityResourceManagerImpl.getContentAsSAX(PriorityResourceManagerImpl.java:103)
        at org.orbeon.oxf.processor.generator.URLGenerator$OXFResourceHandler.readXML(URLGenerator.java:655)
        at org.orbeon.oxf.processor.generator.URLGenerator$1.readImpl(URLGenerator.java:402)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.xml.ProcessorOutputXMLReader.parse(ProcessorOutputXMLReader.java:40)
        at org.orbeon.saxon.event.Sender.sendSAXSource(Sender.java:270)
        at org.orbeon.saxon.event.Sender.send(Sender.java:124)
        at org.orbeon.saxon.event.Sender.send(Sender.java:46)
        at org.orbeon.saxon.PreparedStylesheet.loadStylesheetModule(PreparedStylesheet.java:204)
        at org.orbeon.saxon.PreparedStylesheet.prepare(PreparedStylesheet.java:126)
        at org.orbeon.saxon.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:135)
        at org.orbeon.oxf.xml.TransformerUtils.getTemplates(TransformerUtils.java:263)
        at org.orbeon.oxf.processor.transformer.xslt.XSLTTransformer$1.createTransformer(XSLTTransformer.java:354)
        at org.orbeon.oxf.processor.transformer.xslt.XSLTTransformer$1.readImpl(XSLTTransformer.java:124)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:353)
        at org.orbeon.oxf.processor.converter.AbstractRewrite.access$000(AbstractRewrite.java:71)
        at org.orbeon.oxf.processor.converter.AbstractRewrite$RewriteOutput.readImpl(AbstractRewrite.java:856)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:353)
        at org.orbeon.oxf.processor.converter.QNameConverter.access$400(QNameConverter.java:33)
        at org.orbeon.oxf.processor.converter.QNameConverter$1.readImpl(QNameConverter.java:73)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.serializer.legacy.HTMLSerializer.readInput(HTMLSerializer.java:54)
        at org.orbeon.oxf.processor.serializer.HttpTextSerializer$1.readImpl(HttpTextSerializer.java:101)
        at org.orbeon.oxf.processor.ProcessorImpl$6.read(ProcessorImpl.java:1012)
        at org.orbeon.oxf.processor.ProcessorImpl$ProcessorOutputImpl.read(ProcessorImpl.java:1195)
        at org.orbeon.oxf.processor.ProcessorImpl.readInputAsSAX(ProcessorImpl.java:348)
        at org.orbeon.oxf.processor.serializer.HttpSerializer.readInput(HttpSerializer.java:42)
        at org.orbeon.oxf.processor.serializer.HttpSerializerBase$1.read(HttpSerializerBase.java:147)
        at org.orbeon.oxf.processor.ProcessorImpl.readCacheInputAsObject(ProcessorImpl.java:470)
        at org.orbeon.oxf.processor.serializer.HttpSerializerBase.start(HttpSerializerBase.java:138)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor$11.run(PipelineProcessor.java:652)
        at org.orbeon.oxf.processor.ProcessorImpl.executeChildren(ProcessorImpl.java:536)
        at org.orbeon.oxf.processor.pipeline.PipelineProcessor.start(PipelineProcessor.java:649)
        at org.orbeon.oxf.pipeline.InitUtils.runProcessor(InitUtils.java:86)
        at org.orbeon.oxf.webapp.ProcessorService.serviceError(ProcessorService.java:130)
        at org.orbeon.oxf.webapp.ProcessorService.service(ProcessorService.java:106)
        at org.orbeon.oxf.servlet.OPSServletDelegate.service(OPSServletDelegate.java:147)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at org.orbeon.oxf.servlet.OPSServlet.service(OPSServlet.java:75)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:595)

 
And the last error I see in the log is:
 
http-8080-Processor25 ERROR webapp.ProcessorService - org.orbeon.oxf.common.OXFException: oxf:/config/error.xpl, line 92, column 45, description executing processor: oxf:/config/error.xpl, line 53, column 44, description reading processor output: Cannot load "/config/theme/theme.xsl" with webapp loader: Cannot load "/config/theme/theme.xsl" with webapp loader
Cannot load "/config/theme/theme.xsl" with webapp loader: Cannot load "/config/theme/theme.xsl" with webapp loader
oxf:/config/error.xpl, line 53, column 44, description reading processor output: Cannot load "/config/theme/theme.xsl" with webapp loader: Cannot load "/config/theme/theme.xsl" with webapp loader
Cannot load "/config/theme/theme.xsl" with webapp loader: Cannot load "/config/theme/theme.xsl" with webapp loader

Any advice?  I'm done messing with it today, but tomorrow I'll look at the files mentioned to be sure they are correct (I did look at epilogue.xpl, and it's referring to this line:
 
        <p:output name="xformed-data" id="xformed-data"/>
 
Which seems ok.)
 
Thanks in advance,
 
Jay


--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

winmail.dat (22K) Download Attachment
Erik Bruchez
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Tomcat 500 Error with Nightly Build

Erik Bruchez
Administrator
Jay,

 > Alright, so I've started with a fresh copy of Tomcat 5.5, and dug
 > around some to figure out how to watch Orbeon's logs and have some
 > more information here.
 >
 > First, when I start Tomcat, Orbeon spits this out at the end of the
 > log (logging is set to debug level):
 >
 > main WARN http.Descriptor - giving up unable to read descriptor file

As far as I can tell, this message doesn't come from OPS.

 > Not sure if that's normal or not, everything else I saw was either
DEBUG or INFO level.
 >
 > When hitting my app, this exception comes up:
 >
 > http-8080-Processor25 ERROR webapp.ProcessorService - Exception at
oxf:/config/epilogue.xpl, line 41, column 58, description reading
processor output
 >        at
org.orbeon.oxf.resources.WebAppResourceManagerImpl.getContentAsStream(WebAppResourceManagerImpl.java:74)

[...]

 > And another one a bit later after that:
 >
 > http-8080-Processor25 ERROR webapp.ProcessorService - Exception at
oxf:/config/error.xpl, line 53, column 44, description reading processor
output
 > org.orbeon.oxf.resources.ResourceNotFoundException: Cannot load
"/config/theme/theme.xsl" with webapp loader

[...]

The above suggests you have a serious issue with the OPS resources. If
your OPS web.xml messed-up? Did you change anything to the
configuration of the resource managers? The initial warning you saw
first could possibly indicate that. But it looks like Tomcat (or
whoever spits that first message) is broken and unable to report an
error that makes sense.

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Free forum by Nabble Edit this page