Re: TomEE 7.0.3. : Requests are rejected

2018-05-23 Thread Jean-Louis Monteiro
Hi,

If you don't see anything in the access logs for such request then it might
be because they don't get to the server itself.
Do you by chance get the reason in uptime monitor?

Can be Socket timeout or not found or something else.

JLouis

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

On Tue, May 22, 2018 at 11:32 AM, jolinnen  wrote:

> Hello,
> since this year we use an uptime monitor for our webservice. From time to
> time this monitor reports that our service is unavailable for just a short
> time.
> I see in our logfiles (and even in catalina.out), that the service is still
> online at this time, but it seems that some requests are rejected.
>
> In  localhost_access_log I found entries like this:
>
> 194.187.221.160 - - [22/May/2018:14:31:51 +0200] "GET /OurService/version
> HTTP/1.1" 200 47
> 194.187.221.160 - - [22/May/2018:14:35:28 +0200] "GET /OurService/version
> HTTP/1.1" 200 47
> 194.187.221.160 - - [22/May/2018:14:37:02 +0200] "GET /OurService/version
> HTTP/1.1" 200 47
> *194.187.221.160 - - [22/May/2018:14:40:36 +0200] "GET /OurService/version
> HTTP/1.1" 500 73*
> 194.187.221.160 - - [22/May/2018:14:40:36 +0200] "GET /OurService/version
> HTTP/1.1" 200 47
> 194.187.221.160 - - [22/May/2018:14:42:26 +0200] "GET /OurService/version
> HTTP/1.1" 200 47
>
> and in catalina.out I can see an entry for the requests with HTTP status
> 200, but not for the 500 status. So my guess is that the uptime monitor
> complains about this.
>
> We are using default parameters in server.xml.
>
> Have someone an idea what's happened? Should we increase maxThreads or what
> ever?  Is there a possibility for getting more information about the reason
> for the rejects?
>
> Many thanks in advance
>
> Cheers
>
> Jörg
>
>
>
>
>
>
>
> --
> Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-
> f979441.html
>


Re: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages

2018-05-23 Thread Romain Manni-Bucau
Hi Matthew,

looks like a classloader issue like that but would need more details

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mer. 23 mai 2018 à 10:52, Matthew Broadhead <
matthew.broadh...@nbmlaw.co.uk> a écrit :

> After TomEE 7.0.3 has been running for a long time, maybe weeks, it starts
> producing these messages when users try to transform XML using XSLT
> (usually to generate PDF using FOP).  The container has to be restarted in
> order for it to start working again.  Is this related to the Xalan problem?
>
> java.util.MissingResourceException: Could not load any resource bundle by
> com.sun.org.apache.xerces.internal.impl.msg.SAXMessages
> at
> com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:174)
> at
> com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:166)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> com.sun.org.apache.xerces.internal.utils.SecuritySupport.getResourceBundle(SecuritySupport.java:166)
> at
> com.sun.org.apache.xerces.internal.util.SAXMessageFormatter.formatMessage(SAXMessageFormatter.java:58)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.setProperty(AbstractSAXParser.java:1949)
> at
> com.sun.org.apache.xerces.internal.parsers.SAXParser.setProperty(SAXParser.java:175)
> at
> org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:476)
>
>


Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages

2018-05-23 Thread Matthew Broadhead

After TomEE 7.0.3 has been running for a long time, maybe weeks, it starts 
producing these messages when users try to transform XML using XSLT (usually to 
generate PDF using FOP).  The container has to be restarted in order for it to 
start working again.  Is this related to the Xalan problem?

java.util.MissingResourceException: Could not load any resource bundle by 
com.sun.org.apache.xerces.internal.impl.msg.SAXMessages
at 
com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:174)
at 
com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:166)
at java.security.AccessController.doPrivileged(Native Method)
at 
com.sun.org.apache.xerces.internal.utils.SecuritySupport.getResourceBundle(SecuritySupport.java:166)
at 
com.sun.org.apache.xerces.internal.util.SAXMessageFormatter.formatMessage(SAXMessageFormatter.java:58)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.setProperty(AbstractSAXParser.java:1949)
at 
com.sun.org.apache.xerces.internal.parsers.SAXParser.setProperty(SAXParser.java:175)
at 
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:476)