Re: I want to know how use the parsing of Jaspar from outside.

[西原 良二]

Hi Chris,

I want to use this method.
org.apache.jasper.compiler.Parser#parse

I want to get this instance.
org.apache.jasper.compiler.Node

Those classes are 'package-private'.

It does not mean want to compile.
I want to get parser tree of JSP.



Best Regards


On Tue, 26 Jan 2016 10:29:29 -0500
Christopher Schultz  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 西原 良二,
> 
> On 1/26/16 5:05 AM, 西原 良二 wrote:
> > Hello,
> > 
> > When I am looking for information in this mailing list in an
> > attempt to use the Jaspar, I found the following thread . 
> > https://mail-archives.apache.org/mod_mbox/tomcat-users/201509.mbox/%3C
> 55f29c78.2000...@apache.org%3E
> >
> >  But I can not use well because there is access modifier
> > 'private'. I would be really grateful if you could help me to use
> > that parser with no access modifier 'private'.
> 
> Which method (or constructor)?
> 
> You might want to look at the ant tasks (jspc) and how they work.
> 
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iEYEARECAAYFAlankNkACgkQ9CaO5/Lv0PDMmACgv0zZQ3wugrlb383oAnnRFKva
> UbMAoMOlfUJ8GKgvPDGG/r2YOBNtdYg8
> =ozwe
> -END PGP SIGNATURE-
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

SOLVED, Re: Tomcat 7.0.67 crashing on takeoff

[James H. H. Lampert]

On 1/26/16 3:01 PM, Caldarale, Charles R wrote:

You found the right documentation page.  Update the 
JreMemoryLeakPreventionListener entry in your conf/server.xml to look like this:




Thanks, Messrs. Caldarale, Thomas, and Schultz. The above change worked 
(by then, I'd just barely caught on that it was probably in server.xml, 
but had no ready example of the syntax for the change), and within about 
a minute of my launching with my standard Tomcat-launcher CL program 
(following the usual IBM Midrange naming conventions, it's called 
STRTOMCAT), the port opened, and I was able to connect to the default 
ROOT context, and then to the Manager context.


Definitely adding that to my installation docs.

--
JHHL


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: More, Re: Tomcat 7.0.67 crashing on takeoff

[Caldarale, Charles R]

> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com] 
> Subject: Re: More, Re: Tomcat 7.0.67 crashing on takeoff

> On 1/26/16 2:25 PM, Mark Thomas wrote:
> > Setting xmlParsingProtection="false" on the
> > JreMemoryLeakPreventionListener should stop the exception.

> Ok, but how? Is there a way to do that from a configuration file? I'm 
> looking at 
>  but I 
> don't have a clue what to do with what I see.

You found the right documentation page.  Update the 
JreMemoryLeakPreventionListener entry in your conf/server.xml to look like this:



 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Socket Read long running

[Rallavagu]

On 1/21/16 4:13 AM, Christopher Schultz wrote:

Rallavagu,

On 1/19/16 6:14 PM, Rallavagu wrote:



On 1/19/16 2:43 PM, Mark Thomas wrote:

On 19/01/2016 22:36, Rallavagu wrote:

Also, it could be keep-alive for client connection as well. In any case,
how long a keep-alive connection will be in this state by default?
Thanks.


This behaviour is entirely normal. Why are you concerned about it?


I was analyzing thread dump as the application experiences sudden high
response times and eventually becomes normal.



Regarding how long the thread will be in this state, the default
keep-alive timeout for the HTTP BIO connector can be found in the
documentation.
(Yes, I do happen to know what it is but think of this as an exercise
for the reader.)


 From the documentation keepAliveTimeout defaults to connectionTimeout.


"The number of milliseconds this Connector will wait, after accepting a
connection, for the request URI line to be presented. Use a value of -1
to indicate no (i.e. infinite) timeout. The default value is 6 (i.e.
60 seconds) but note that the standard server.xml that ships with Tomcat
sets this to 2 (i.e. 20 seconds). Unless disableUploadTimeout is set
to false, this timeout will also be used when reading the request body
(if any)."


You might want to consider switching to an NIO-based connector. The
NIO-based connectors do not block a request-processing thread during the
keep-alive wait time, so fewer threads can handle the same number of
actual incoming requests (instead of waiting-around potentially doing no
additional work).

You may still have a response-time problem after that, but it won't be
due to the threading model.

If your load-balancer configured to maintain keep-alive connections to
your Tomcat instance(s)? If so, what are the details of that configuration?


They have configured for a pool of 50 keep-alive connections with 10 
seconds timeout.


Thanks



-chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: More, Re: Tomcat 7.0.67 crashing on takeoff

[James H. H. Lampert]

On 1/26/16 2:25 PM, Mark Thomas wrote:

Setting xmlParsingProtection="false" on the
JreMemoryLeakPreventionListener should stop the exception.

It looks like your XML implementation isn't compatible for the fix for
that memory leak. I never did get to the root of what triggered the
memory leak. It may be that your XML implementation doesn't suffer from
it. Either a way a possible memory leak is probably better than a server
that won't start.


Ok, but how? Is there a way to do that from a configuration file? I'm 
looking at 
 but I 
don't have a clue what to do with what I see.


Please don't tell me that it's something that requires recompilation 
from source. Assuming I could even get Tomcat to compile from source, I 
wouldn't be inclined to trust my own build.


--
James H. H. Lampert


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: WebEx meeting invitation: Apache Tomcat: TLS Virtual Hosting

[Mark Thomas]

On 26/01/2016 21:47, gustavo.avitab...@unina.it wrote:
> Mark:
>I tried to access your meeting again. I tried on
> Tuesday, Jan 26 at 9pm, meeting number 647 936 105.
> I failed again.
>I used a notebook  with Windows 10, and I got a
> message that WebEx doesn't support Windows 10.
>Then I switched to Ubuntu. I accessed the meeting,
> but I got a message: The Audio device is unaccessible
> now. I could see no slides.
>It looks like the settings for such meetings are
> not working yet.
>  Gustavo Avitabile

Sorry about that. Other people were able to see the slides and hear the
audio so it does look like an incompatibility between WebEx and your
environment. Was any sort of on-line help option available?

The recording should be available on YouTube tomorrow. I'll post when it
is ready.

Kind regards,

Mark

> 
> Quoting Mark Thomas :
> 
>> On 10 December 2015 15:28:03 GMT+00:00, gustavo.avitab...@unina.it wrote:
>>> Quoting Mark Thomas :
>>>
 On 08/12/2015 10:19, gustavo.avitab...@unina.it wrote:
> Hi Mark,
>I tried to attend this meeting. I connected with WebEx,
> I could see the slides, but I got no audio. The same
> happened at you first meeting, a few days ago. I looked
> at the first meeting you published in YouTube, with no
> problems: the audio was there.
>Can you suggest how can I attend the live meeting?

 The meetings are currently set up so you have to use a telephone to
 connect to the audio. You can either dial in or get the system to
>>> call
 you back.

 It looks like something did go wrong with the audio for this
>>> morning's
 meeting. As I said when I sent the first invitations out, this is new
 for us and we expect to have a few issues as we figure out how best
>>> to
 do this.

 For this evening's meeting I am going to try a couple of different
>>> things:
 1. See if I can enable audio via the same device you are watching the
 video so you don;t need a separate phone line.
 2. Dial in from a separate line and ensure that my audio feed is
>>> working.

 Mark
>>> Thank you Mark:
>>>As I live in Italy, I am afraid dialing or being recalled
>>> is not a solution.
>>
>> Why does living in Italy stop you receiving a call-back?
>>
>> Mark
>>
>>> I will wait until you succeed enabling
>>> audio on the same channel you have video. In the meantime,
>>> I will renounce to attend meetings live and will limit to
>>> look at them on YouTube.
>>>  Gustavo Avitabile


>Thank you
>Gustavo Avitabile
>
> Quoting Mark Thomas :
>
>>
>> Hello,
>>
>> Mark Thomas invites you to join this WebEx meeting.
>>
>>
>> Apache Tomcat: TLS Virtual Hosting
>> Tuesday, 8 December 2015
>> 10:00  |  GMT Time (London, GMT)  |  1 hr
>>
>>
>> JOIN WEBEX MEETING
>>
>>> https://pivotal.webex.com/pivotal/j.php?MTID=md04c20b9c83695a23992a9a2f9ea1302
>>>
>>
>> Meeting number: 640 832 227
>>
>>
>> JOIN BY PHONE
>> Call-in toll-free number: 1-877-8818371  (US)
>> Call-in number: 1-617-3374371  (US)
>> Show global numbers:
>>
>>> https://sites.google.com/a/pivotal.io/pivotal-it/pivotal-conferencing
>> Attendee access code: 289 459 03
>>
>>
>>
>> Add this meeting to your calendar:
>>
>>> https://pivotal.webex.com/pivotal/j.php?MTID=m9e9c0d24e609886438948d2f4265823d
>>>
>>
>>
>>
>> Can't join the meeting? Contact support here:
>> https://pivotal.webex.com/pivotal/mc
>>
>>
>> IMPORTANT NOTICE: Please note that this WebEx service allows audio
>>> and
>> other information sent during the session to be recorded, which may
>>> be
>> discoverable in a legal matter. By joining this session, you
>> automatically consent to such recordings. If you do not consent to
>> being recorded, discuss your concerns with the host or do not join
>>> the
>> session.
>>
>
>
>
>
>
>>> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org



>>>
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>>
> 
> 
> 
> 
> -

Re: More, Re: Tomcat 7.0.67 crashing on takeoff

[Mark Thomas]

On 26/01/2016 21:58, James H. H. Lampert wrote:
> On 1/26/16 12:55 PM, Christopher Schultz wrote:
> 
>> If you are explicitly configuring the APR connector and the APR
>> library (or some required dependency -- e.g. OpenSSL -- then Tomcat
>> will not start.
> 
> to which I just replied:
>> This is quite literally straight out of apache-tomcat-7.0.67.zip.
>> We're currently using 7.0.54 on our own AS/400, and we have customer
>> boxes anywhere from 7.0.47 to 7.0.62. And we use JSSE for SSL.
> 
> I just noticed something about my original email.
> 
> Somehow, the crucial exception itself got missed when I was cutting and
> pasting from the terminal session into the email, which suggests.
> 
> Immediately following the INFO message about APR came the exceptions and
> stack traces, reproduced here:

Setting xmlParsingProtection="false" on the
JreMemoryLeakPreventionListener should stop the exception.

It looks like your XML implementation isn't compatible for the fix for
that memory leak. I never did get to the root of what triggered the
memory leak. It may be that your XML implementation doesn't suffer from
it. Either a way a possible memory leak is probably better than a server
that won't start.

Mark


> 
>> java.lang.ClassCastException:
>> org.apache.crimson.tree.DOMImplementationImpl incompatible with
>> org.w3c.dom.ls.DOMImplementationLS
>> at
>> org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:459)
>>
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
>>
>> at
>> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
>>
>> at
>> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
>>
>> at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:99)
>> at org.apache.catalina.startup.Catalina.load(Catalina.java:642)
>> at org.apache.catalina.startup.Catalina.load(Catalina.java:667)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>>
>> at java.lang.reflect.Method.invoke(Method.java:611)
>> at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:253)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:427)
>> Jan 26, 2016 12:38:02 PM org.apache.catalina.startup.Catalina start
>> SEVERE: The required Server component failed to start so Tomcat is
>> unable to start.
>> Throwable occurred: org.apache.catalina.LifecycleException: An invalid
>> Lifecycle transition was attempted ([before_start]) for compoonent
>> [StandardServer[8005]] in state [INITIALIZING]
>> at
>> org.apache.catalina.util.LifecycleBase.invalidTransition(LifecycleBase.java:409)
>>
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:144)
>> at org.apache.catalina.startup.Catalina.start(Catalina.java:693)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>>
>> at java.lang.reflect.Method.invoke(Method.java:611)
>> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)
> 
> -- 
> JHHL
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

More, Re: Tomcat 7.0.67 crashing on takeoff

[James H. H. Lampert]

On 1/26/16 12:55 PM, Christopher Schultz wrote:


If you are explicitly configuring the APR connector and the APR
library (or some required dependency -- e.g. OpenSSL -- then Tomcat
will not start.


to which I just replied:
> This is quite literally straight out of apache-tomcat-7.0.67.zip.
> We're currently using 7.0.54 on our own AS/400, and we have customer
> boxes anywhere from 7.0.47 to 7.0.62. And we use JSSE for SSL.

I just noticed something about my original email.

Somehow, the crucial exception itself got missed when I was cutting and 
pasting from the terminal session into the email, which suggests.


Immediately following the INFO message about APR came the exceptions and 
stack traces, reproduced here:



java.lang.ClassCastException: org.apache.crimson.tree.DOMImplementationImpl 
incompatible with org.w3c.dom.ls.DOMImplementationLS
at 
org.apache.catalina.core.JreMemoryLeakPreventionListener.lifecycleEvent(JreMemoryLeakPreventionListener.java:459)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at 
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:99)
at org.apache.catalina.startup.Catalina.load(Catalina.java:642)
at org.apache.catalina.startup.Catalina.load(Catalina.java:667)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:253)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:427)
Jan 26, 2016 12:38:02 PM org.apache.catalina.startup.Catalina start
SEVERE: The required Server component failed to start so Tomcat is unable to 
start.
Throwable occurred: org.apache.catalina.LifecycleException: An invalid 
Lifecycle transition was attempted ([before_start]) for compoonent 
[StandardServer[8005]] in state [INITIALIZING]
at 
org.apache.catalina.util.LifecycleBase.invalidTransition(LifecycleBase.java:409)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:144)
at org.apache.catalina.startup.Catalina.start(Catalina.java:693)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)


--
JHHL


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 7.0.67 crashing on takeoff

[James H. H. Lampert]

On 1/26/16 12:55 PM, Christopher Schultz wrote:


If you are explicitly configuring the APR connector and the APR
library (or some required dependency -- e.g. OpenSSL -- then Tomcat
will not start.


This is quite literally straight out of apache-tomcat-7.0.67.zip. We're 
currently using 7.0.54 on our own AS/400, and we have customer boxes 
anywhere from 7.0.47 to 7.0.62. And we use JSSE for SSL.


--
JHHL


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: WebEx meeting invitation: Apache Tomcat: TLS Virtual Hosting

[gustavo . avitabile]

Mark:
   I tried to access your meeting again. I tried on
Tuesday, Jan 26 at 9pm, meeting number 647 936 105.
I failed again.
   I used a notebook  with Windows 10, and I got a
message that WebEx doesn't support Windows 10.
   Then I switched to Ubuntu. I accessed the meeting,
but I got a message: The Audio device is unaccessible
now. I could see no slides.
   It looks like the settings for such meetings are
not working yet.
 Gustavo Avitabile

Quoting Mark Thomas :


On 10 December 2015 15:28:03 GMT+00:00, gustavo.avitab...@unina.it wrote:

Quoting Mark Thomas :


On 08/12/2015 10:19, gustavo.avitab...@unina.it wrote:

Hi Mark,
   I tried to attend this meeting. I connected with WebEx,
I could see the slides, but I got no audio. The same
happened at you first meeting, a few days ago. I looked
at the first meeting you published in YouTube, with no
problems: the audio was there.
   Can you suggest how can I attend the live meeting?


The meetings are currently set up so you have to use a telephone to
connect to the audio. You can either dial in or get the system to

call

you back.

It looks like something did go wrong with the audio for this

morning's

meeting. As I said when I sent the first invitations out, this is new
for us and we expect to have a few issues as we figure out how best

to

do this.

For this evening's meeting I am going to try a couple of different

things:

1. See if I can enable audio via the same device you are watching the
video so you don;t need a separate phone line.
2. Dial in from a separate line and ensure that my audio feed is

working.


Mark

Thank you Mark:
   As I live in Italy, I am afraid dialing or being recalled
is not a solution.


Why does living in Italy stop you receiving a call-back?

Mark


I will wait until you succeed enabling
audio on the same channel you have video. In the meantime,
I will renounce to attend meetings live and will limit to
look at them on YouTube.
 Gustavo Avitabile




   Thank you
   Gustavo Avitabile

Quoting Mark Thomas :



Hello,

Mark Thomas invites you to join this WebEx meeting.


Apache Tomcat: TLS Virtual Hosting
Tuesday, 8 December 2015
10:00  |  GMT Time (London, GMT)  |  1 hr


JOIN WEBEX MEETING


https://pivotal.webex.com/pivotal/j.php?MTID=md04c20b9c83695a23992a9a2f9ea1302


Meeting number: 640 832 227


JOIN BY PHONE
Call-in toll-free number: 1-877-8818371  (US)
Call-in number: 1-617-3374371  (US)
Show global numbers:


https://sites.google.com/a/pivotal.io/pivotal-it/pivotal-conferencing

Attendee access code: 289 459 03



Add this meeting to your calendar:


https://pivotal.webex.com/pivotal/j.php?MTID=m9e9c0d24e609886438948d2f4265823d




Can't join the meeting? Contact support here:
https://pivotal.webex.com/pivotal/mc


IMPORTANT NOTICE: Please note that this WebEx service allows audio

and

other information sent during the session to be recorded, which may

be

discoverable in a legal matter. By joining this session, you
automatically consent to such recordings. If you do not consent to
being recorded, discuss your concerns with the host or do not join

the

session.








-

To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 7.0.67 crashing on takeoff

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

James,

On 1/26/16 2:02 PM, James H. H. Lampert wrote:
> I'm attempting to install Tomcat 7.0.67 on an AS/400 (something
> I've done several times before), and when I launch, I get a
> crash-on-takeoff with an exception I've never seen before. Here's
> the complete catalina.out:
> 
>> Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Server version:Apache Tomcat/7.0.67 Jan 26, 2016 12:37:47
>> PM org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Server built:  Dec 7 2015 13:07:11 UTC Jan 26, 2016
>> 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener
>> log INFO: Server number: 7.0.67.0 Jan 26, 2016 12:37:47
>> PM org.apache.catalina.startup.VersionLoggerListener log INFO: OS
>> Name:   OS/400 Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO: OS
>> Version:V6R1M0 Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Architecture:  PowerPC Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO: Java
>> Home: /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre Jan 26, 2016
>> 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener
>> log INFO: JVM Version:   jvmap3260sr10-20111208 Jan 26,
>> 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO: JVM
>> Vendor:IBM Corporation Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> CATALINA_BASE: /wintouch/tomcat Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> CATALINA_HOME: /wintouch/tomcat Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: -Xjcl:jclscar_24 Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: 
>> -Dcom.ibm.oti.vm.bootstrap.library.path=/QOpenSys/QIBM/ProdData/JavaV
M/jdk60/32bit/jre/lib/ppc
>>
>>
>> 
Jan 26, 2016 12:37:47 PM
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: 
>> -Dsun.boot.library.path=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jr
e/lib/ppc
>>
>>
>> 
Jan 26, 2016 12:37:47 PM
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: 
>> -Djava.library.path=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/li
b/ppc:/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc:/QOpenSys/Q
IBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc/classic:/QOpenSys/QIBM/ProdD
ata/JavaVM/jdk60/32bit/jre/lib/ppc:/QOpenSys/QIBM/ProdData/JavaVM/jdk60/
32bit/jre/lib/ppc/classic:/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre
/lib/ppc/default:/usr/lib:/usr/lib
>>
>>
>> 
Jan 26, 2016 12:37:47 PM
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: 
>> -Djava.home=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre Jan
>> 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: 
>> -Djava.ext.dirs=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ex
t
>>
>> 
Jan 26, 2016 12:37:47 PM
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: -Duser.dir=/ Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: _j2se_j9=71168 Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: -Xdump Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: 
>> -Dos400.vm.inputargs=-Djava.util.logging.config.file=/wintouch/tomcat
/conf/logging.properties
>>
>> 
- -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>> -Dos400.awt.native=true -Djava.awt.headless=true
>> -Djava.version=1.6 -Xms512m -Xmx2048m
>> -Djava.endorsed.dirs=/wintouch/tomcat/endorsed 
>> -Dcatalina.base=/wintouch/tomcat
>> -Dcatalina.home=/wintouch/tomcat 
>> -Djava.io.tmpdir=/wintouch/tomcat/temp Jan 26, 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: 
>> -Djava.util.logging.config.file=/wintouch/tomcat/conf/logging.propert
ies
>>
>> 
Jan 26, 2016 12:37:47 PM
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: 
>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>>
>> 
Jan 26, 2016 12:37:47 PM
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: -Dos400.awt.native=true Jan 26, 2016
>> 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener
>> log INFO: Command line argument: -Djava.awt.headless=true Jan 26,
>> 2016 12:37:47 PM 
>> org.apache.catalina.startup.VersionLoggerListener log INFO:
>> Command line argument: -Xms512m Jan 26, 2016 12:37:47 PM 
>>

Re: JDBC Connection pooling

[Felix Schumacher]

Am 22.01.2016 um 12:35 schrieb R. Sriram:

Hello I am trying to establish connection pooling.
Should I be using dbcp?
If you want to use db connection pooling, it is probably a good idea to 
use the pooling method the container gives you, as it will be used by a 
lot of people and therefore has gotten a lot of testing.


In the case of tomcat that would be a copy of commons dbcp(2).

Regards,
 Felix



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 7.0.67 crashing on takeoff

[James H. H. Lampert]

I'm attempting to install Tomcat 7.0.67 on an AS/400 (something I've 
done several times before), and when I launch, I get a crash-on-takeoff 
with an exception I've never seen before. Here's the complete catalina.out:



Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version:Apache Tomcat/7.0.67
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built:  Dec 7 2015 13:07:11 UTC
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number: 7.0.67.0
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name:   OS/400
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version:V6R1M0
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture:  PowerPC
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home: /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version:   jvmap3260sr10-20111208
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor:IBM Corporation
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE: /wintouch/tomcat
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME: /wintouch/tomcat
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Xjcl:jclscar_24
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Dcom.ibm.oti.vm.bootstrap.library.path=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Dsun.boot.library.path=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Djava.library.path=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc:/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc:/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc/classic:/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc:/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc/classic:/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ppc/default:/usr/lib:/usr/lib
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Djava.home=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Djava.ext.dirs=/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit/jre/lib/ext
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Duser.dir=/
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: _j2se_j9=71168
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Xdump
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Dos400.vm.inputargs=-Djava.util.logging.config.file=/wintouch/tomcat/conf/logging.properties
 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
-Dos400.awt.native=true -Djava.awt.headless=true -Djava.version=1.6 -Xms512m 
-Xmx2048m -Djava.endorsed.dirs=/wintouch/tomcat/endorsed 
-Dcatalina.base=/wintouch/tomcat -Dcatalina.home=/wintouch/tomcat 
-Djava.io.tmpdir=/wintouch/tomcat/temp
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Djava.util.logging.config.file=/wintouch/tomcat/conf/logging.properties
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dos400.awt.native=true
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.awt.headless=true
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Xms512m
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Xmx2048m
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.endorsed.dirs=/wintouch/tomcat/endorsed
Jan 26, 2016 12:37:47 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.base=/wintouch/tomcat
Ja

Re: I want to know how use the parsing of Jaspar from outside.

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

西原 良二,

On 1/26/16 5:05 AM, 西原 良二 wrote:
> Hello,
> 
> When I am looking for information in this mailing list in an
> attempt to use the Jaspar, I found the following thread . 
> https://mail-archives.apache.org/mod_mbox/tomcat-users/201509.mbox/%3C
55f29c78.2000...@apache.org%3E
>
>  But I can not use well because there is access modifier
> 'private'. I would be really grateful if you could help me to use
> that parser with no access modifier 'private'.

Which method (or constructor)?

You might want to look at the ant tasks (jspc) and how they work.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlankNkACgkQ9CaO5/Lv0PDMmACgv0zZQ3wugrlb383oAnnRFKva
UbMAoMOlfUJ8GKgvPDGG/r2YOBNtdYg8
=ozwe
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Deployment of WEB App from ANT build fails with IOException.

[Karl Hauschildt]

Thank you, thank you, thank you. Yes I should have seen that in the doc you
reference but equally surprised that no post, anywhere, bothered to mention
the URL change as it's pretty important. So, now it deploy's find but will
not start which I had been chasing elsewhere. The error is Tomcat throws an
exception of unable to create JAXB Instance very early during
initialization.

On Mon, Jan 25, 2016 at 7:45 PM, Konstantin Kolinko 
wrote:

> 2016-01-25 0:49 GMT+03:00 Karl Hauschildt :
> >
> >
> > Background:
> >
> > JAVA Web application, Eclipse workspace with an ANT build.xml.
> >
> > Using Windows, this project builds using java 1.7, deploys to multiple
> > Solaris environments running Tomcat 5, 6 or 7 and runs cleanly.
> >
> >
> >
> > I have to deploy the preceding to a Linux environment with Tomcat 8.
> Which
> > is running JAVA 1.8
> >
> >
> >
> > Problem:
> >
> > The deploy task fails with: BUILD FAILED java.io.IOException: Error
> > writing request body to server
> >
> > Looking in the Tomcat, localhost.log, I see: "PUT
> > /manager/deploy?path=%2FFXInSite&update=true HTTP/1.1" 403 3196
>
> Note that the above URL can be used only with Tomcat 6 and earlier.
>
> Once you fix your users, you have to change the url in your Ant task,
> or you would end up with error 404.
>
> Migration guide:
> http://tomcat.apache.org/migration-7.html#Manager_application
>
>
> > The other logs contain no errors or warnings.
>
> [...]
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: switching between Java8 and Java 7 under tomcat7 leads to error

[Christoph P.U. Kukulies]

Am 26.01.2016 um 10:40 schrieb André Warnier (tomcat):

On 26.01.2016 10:19, Christoph P.U. Kukulies wrote:

Am 26.01.2016 um 09:36 schrieb Christoph P.U. Kukulies:

Am 25.01.2016 um 19:34 schrieb George Sexton:



On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:

Thanks. Will give that a try.

How can I tell, which java engine Tomcat is actually using?

At a CMD prompt I'm getting:


C:\> java -version
java version "1.8.0_71"
Java(TM) SE Runtime Environment (build 1.8.0_71-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)


If you have a utility that shows what open files the Tomcat process 
has, that would
work. Alternatively, get the Manager application running and see 
what information it

provides under the Server Status screen.



That made me ask myself, whether the parameters and settings I can 
see and set through

the manager (tomcat6w.exe) are those that the
Windows7 service really "sees" at startup.

Would like to have added -Xmx768m to the startup parameters. Looking 
into the registry

HKLM\System\CurrentControlSet\Services\tomcat6
I can only see the ImagePath that is started ("c:\Program
Files\Apache_Group\Tomcat_6.0.39\bin\tomcat6.exe" //RS//Tomcat6), 
the paramters

Key is empty.

Or does tomcat6w write these parameters elsewhere?

Thanks.



Sorry, discard my question above. I forgot for the moment that -Xmx 
is a Java parameter,

not Tomcat.
Nonetheless would be interesting to know, where the configurator puts 
its parameter

settings and
how one can control whether the jvm parameters are really effective.

--
Christoph



Maybe time to read the FAQ ?
http://wiki.apache.org/tomcat/FAQ/Windows#Q11



OK, fine. I read it and understood about tomcat6.exe being a wrapper 
that starts the jvm etc.

Explains a lot.
Logging is fine also. This enabled me to discover that the jvm options 
have to put in one line one by one.

I had -Xms512m - Xmx1024m in one line causing the service start to fail.


--
Christoph




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

I want to know how use the parsing of Jaspar from outside.

[西原 良二]

Hello,

When I am looking for information in this mailing list in an attempt to use the 
Jaspar, 
I found the following thread .
https://mail-archives.apache.org/mod_mbox/tomcat-users/201509.mbox/%3c55f29c78.2000...@apache.org%3E

But I can not use well because there is access modifier 'private'.
I would be really grateful if you could help me to use that parser with no 
access modifier 'private'.

Best Regards


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: switching between Java8 and Java 7 under tomcat7 leads to error

[Konstantin Kolinko]

2016-01-26 12:19 GMT+03:00 Christoph P.U. Kukulies :
> Am 26.01.2016 um 09:36 schrieb Christoph P.U. Kukulies:
>>
>> Am 25.01.2016 um 19:34 schrieb George Sexton:
>>>
>>>
>>>
>>> On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:

 Thanks. Will give that a try.

 How can I tell, which java engine Tomcat is actually using?

 At a CMD prompt I'm getting:


 C:\> java -version
 java version "1.8.0_71"
 Java(TM) SE Runtime Environment (build 1.8.0_71-b15)
 Java HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)
>>>
>>>
>>> If you have a utility that shows what open files the Tomcat process has,
>>> that would work. Alternatively, get the Manager application running and see
>>> what information it provides under the Server Status screen.
>>>
>>
>> That made me ask myself, whether the parameters and settings I can see and
>> set through the manager (tomcat6w.exe) are those that the
>> Windows7 service really "sees" at startup.
>>
>> Would like to have added -Xmx768m to the startup parameters. Looking into
>> the registry HKLM\System\CurrentControlSet\Services\tomcat6
>> I can only see the ImagePath that is started ("c:\Program
>> Files\Apache_Group\Tomcat_6.0.39\bin\tomcat6.exe" //RS//Tomcat6), the
>> paramters
>> Key is empty.
>>
>> Or does tomcat6w write these parameters elsewhere?
>>
>> Thanks.
>>
>
> Sorry, discard my question above. I forgot for the moment that -Xmx is a
> Java parameter, not Tomcat.
> Nonetheless would be interesting to know, where the configurator puts its
> parameter settings and
> how one can control whether the jvm parameters are really effective.
>

The settings are written into Windows Registry
http://commons.apache.org/proper/commons-daemon/procrun.html

The service runner has debug logging, that you can enable via GUI (tomcat6w.exe)

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: switching between Java8 and Java 7 under tomcat7 leads to error

[tomcat]

On 26.01.2016 10:19, Christoph P.U. Kukulies wrote:

Am 26.01.2016 um 09:36 schrieb Christoph P.U. Kukulies:

Am 25.01.2016 um 19:34 schrieb George Sexton:



On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:

Thanks. Will give that a try.

How can I tell, which java engine Tomcat is actually using?

At a CMD prompt I'm getting:


C:\> java -version
java version "1.8.0_71"
Java(TM) SE Runtime Environment (build 1.8.0_71-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)


If you have a utility that shows what open files the Tomcat process has, that 
would
work. Alternatively, get the Manager application running and see what 
information it
provides under the Server Status screen.



That made me ask myself, whether the parameters and settings I can see and set 
through
the manager (tomcat6w.exe) are those that the
Windows7 service really "sees" at startup.

Would like to have added -Xmx768m to the startup parameters. Looking into the 
registry
HKLM\System\CurrentControlSet\Services\tomcat6
I can only see the ImagePath that is started ("c:\Program
Files\Apache_Group\Tomcat_6.0.39\bin\tomcat6.exe" //RS//Tomcat6), the paramters
Key is empty.

Or does tomcat6w write these parameters elsewhere?

Thanks.



Sorry, discard my question above. I forgot for the moment that -Xmx is a Java 
parameter,
not Tomcat.
Nonetheless would be interesting to know, where the configurator puts its 
parameter
settings and
how one can control whether the jvm parameters are really effective.

--
Christoph



Maybe time to read the FAQ ?
http://wiki.apache.org/tomcat/FAQ/Windows#Q11




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: switching between Java8 and Java 7 under tomcat7 leads to error

[Christoph P.U. Kukulies]

Am 26.01.2016 um 09:36 schrieb Christoph P.U. Kukulies:

Am 25.01.2016 um 19:34 schrieb George Sexton:



On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:

Thanks. Will give that a try.

How can I tell, which java engine Tomcat is actually using?

At a CMD prompt I'm getting:


C:\> java -version
java version "1.8.0_71"
Java(TM) SE Runtime Environment (build 1.8.0_71-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)


If you have a utility that shows what open files the Tomcat process 
has, that would work. Alternatively, get the Manager application 
running and see what information it provides under the Server Status 
screen.




That made me ask myself, whether the parameters and settings I can see 
and set through the manager (tomcat6w.exe) are those that the

Windows7 service really "sees" at startup.

Would like to have added -Xmx768m to the startup parameters. Looking 
into the registry HKLM\System\CurrentControlSet\Services\tomcat6
I can only see the ImagePath that is started ("c:\Program 
Files\Apache_Group\Tomcat_6.0.39\bin\tomcat6.exe" //RS//Tomcat6), the 
paramters

Key is empty.

Or does tomcat6w write these parameters elsewhere?

Thanks.



Sorry, discard my question above. I forgot for the moment that -Xmx is a 
Java parameter, not Tomcat.
Nonetheless would be interesting to know, where the configurator puts 
its parameter settings and

how one can control whether the jvm parameters are really effective.

--
Christoph


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: switching between Java8 and Java 7 under tomcat7 leads to error

[Christoph P.U. Kukulies]

Am 25.01.2016 um 19:34 schrieb George Sexton:



On 1/25/2016 3:52 AM, Christoph P.U. Kukulies wrote:

Thanks. Will give that a try.

How can I tell, which java engine Tomcat is actually using?

At a CMD prompt I'm getting:


C:\> java -version
java version "1.8.0_71"
Java(TM) SE Runtime Environment (build 1.8.0_71-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)


If you have a utility that shows what open files the Tomcat process 
has, that would work. Alternatively, get the Manager application 
running and see what information it provides under the Server Status 
screen.




That made me ask myself, whether the parameters and settings I can see 
and set through the manager (tomcat6w.exe) are those that the

Windows7 service really "sees" at startup.

Would like to have added -Xmx768m to the startup parameters. Looking 
into the registry HKLM\System\CurrentControlSet\Services\tomcat6
I can only see the ImagePath that is started ("c:\Program 
Files\Apache_Group\Tomcat_6.0.39\bin\tomcat6.exe" //RS//Tomcat6), the 
paramters

Key is empty.

Or does tomcat6w write these parameters elsewhere?

Thanks.

--
Christoph



At Am 22.01.2016 um 18:28 schrieb George Sexton:



On 1/22/2016 6:06 AM, Christoph P.U. Kukulies wrote:

Windows 7:

Today I installed Java 8 on my windows 7 machine and did an upgrade 
of the CMS at the same time (from OpenCMS 9.5.2 to 9.5.3).
After the Java update and the CMS update suddenly my tomcat 6.0.39 
didn't start any longer. The service gave an error at start time:


Der Dienst "Apache Tomcat 6.0 Tomcat6" wurde mit folgendem 
dienstspezifischem Fehler beendet: Unzulässige Funktion..




I've seen this on Windows when upgrading the JRE. The solution that 
worked for me (multiple times) was to uninstall Java, and then 
re-install it. Make sure you grab the correct version (x86, x64) to 
go with your Tomcat install.




My thoughts came to tomcat6 possibly not being compatible with 
Java8 and so I decided to install tomcat 7.0 which started fine.


When starting my CMS system again I now found that it did some 
unpleasant things for which I wanted to rule out tomcat7 being the 
culprit
and switch the jvm.dll in the tomcat7 configurator to the jre1.7 
jvm.dll.


Then suddenly I got the same error as under tomcat6.0 when I tried 
to start tomcat7 again.


Could it be that the Java8 installer screws the existing Java 7 ? 
Or does it change some global parameters that tomcat reads at start 
time.



Thanks.

--
Christoph




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org