RE: Upgrading Tomcat 8.0.23 to Tomcat 8.50

[Venkataramani, Sundar]

Thanks Philip - We are using Apache as load balancer which we will redirect the 
requests to Tomcat Server

Current Apache version is Apache 2.4.18. Do we need to upgrade Apache also when 
we go to Tomcat 8.50 or we can leave as it is.

Thanks
Sundar.V



-Original Message-
From: Philip Hachey [mailto:philip.hac...@nrc-cnrc.gc.ca] 
Sent: Wednesday, July 6, 2016 9:52 PM
To: Tomcat Users List 
Subject: Re: Upgrading Tomcat 8.0.23 to Tomcat 8.50

I would do a fresh install to a new directory and change what you need to to 
match your previous configuration, taking into account changes between Tomcat 
versions (see: http://tomcat.apache.org/migration.html).  
You will need to update system environment variables such as $CATALINA_HOME 
and/or symbolic links.  Of course, it should go without
saying: backup everything! :-)

Good luck!
Philip

On 16-07-06 10:28 AM, Venkataramani, Sundar wrote:
> Help Required.
>
> We need to upgrade our tomcat version from Tomcat 8.0.23  to Tomcat 8.50?. Do 
> we need an upgrade path for these or do we need to do fresh install?.
>
> Thanks
> Sundar.V
>
>
>


-
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: Fedora 23 ROOT##000 just hangs on startup.

[Paul Roubekas]

On 7/6/2016 5:36 PM, Christopher Schultz wrote:
> Paul,
>
> On 7/6/16 5:11 PM, Paul Roubekas wrote:
> > On 7/6/2016 5:00 PM, Paul Roubekas wrote:
> >> On 7/6/2016 4:39 PM, Christopher Schultz wrote:
> >>> Paul,
> >>>
> >>> On 7/6/16 4:10 PM, Paul Roubekas wrote:
>  Works just find on my window 7 workstation with Eclipse 4.5.2
>  but now on Fedora 23 the startup just hangs.
> >>>
> >>> What do you mean "just hangs"? Take a thread dump of the
> >>> process to see what it's doing. What do the logs say?
> >>>
>  Moved the webapps/ROOT directory to ${CATALINA_HOME} which
>  work just fine on the windows workstation.
> >>>
> >>> So:
> >>>
> >>> $ mv ${CATALINA_HOME}/webapps/ROOT ${CATALINA_HOME}
> >>>
> >>> ??
> >> Yes that is what I did.  I could have moved it to /tmp.  But
> >> since there were no issue on the workstation I did the same thing
> >> on the server.
> >>>
> >>> So, ROOT is now ${CATALINA_HOME}/ROOT?
> >> Yes
> >>>
>  Double checked the server.xml file.
> >>>
>  Made sure the WAR had the same owner and group as all the
>  other tomcat artifacts.
> >>>
>  Windows startup allows "/" in the 'path' but Fedora startup
>  gave a warning so I changed path to "".   Which stopped the
>  warning on startup.
> >>>
> >>> A context path of "/" is invalid. Leave it as "". Better yet,
> >>> remove the whole  element from server.xml.
> >>>
> > All that did was cause the startup to lockup sooner, at the step
> > below. INFO: OpenWebBeans Container has started, it took 283 ms.
> > Jul 06, 2016 5:08:19 PM
> > org.apache.tomee.catalina.TomcatWebAppBuilder deployWebApps INFO:
> > using context file
> > /opt/tomee/webapps/ROOT##000/META-INF/context.xml Jul 06, 2016
> > 5:08:19 PM org.apache.tomee.catalina.TomcatWebAppBuilder init INFO:
> > - localhost -> /
>
> So you get that INFO message and then .. nothing?
>
> This is evidently TomEE which may do things slightly differently, but
> generally speaking, if you have a WAR file in webapps/ then it will be
> automatically-deployed and you don't need any other
> application-specific configuration: just drop your WAR file in there
> and let it deploy. Using ROOT##000.war will use the WAR file "version"
> of 000 which will allow for parallel deployment of the ROOT context.
>
> Are there no other messages in the log file? Are there any other log
> files in logs/ ?
>
> What about a thread dump after Tomcat stops responding?
>
> -chris
Ugh!  lack of entropy on my server was the cause, again.   In the past
when I had this problem the "hang" was at a different spot in the
startup, that is what fooled me, even though I was giving the startup ~5
minutes.  I have a HTTPS page on my site which requires some entropy for
"randomness".  I installed haveged to fix this very issue.  This time I
have added a java program that pulls down a popular light weight daily
news web site once a minute to try and fix this issue... again.

Jul 06, 2016 5:15:04 PM org.apache.catalina.util.SessionIdGeneratorBase
createSecureRandom
INFO: Creation of SecureRandom instance for session ID generation using
[SHA1PRNG] took [403,772] milliseconds.

Thanks for the help.  Hope to return the favor some day. 

I did get some good info about not needing the  in the
server.xml file.



signature.asc
Description: OpenPGP digital signature

Re: Load Balancing Oracle Apex Application on Apache tomcat.

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Chandra,

On 7/6/16 5:34 PM, chandra sekhar wrote:
> Oracle Apex is a web application to build a web based
> application.It will retrieves the static file content from DB by
> executing stored procedures etc.Hence,for this it creates sessions
> in the DB as well.Session can be distributed.So we are thinking to
> load balance.Please advice.

Tomcat is happy to live behind any kind of reverse proxy. If you want
to use sticky sessions (usually a good idea), you'll want to make the
reverse proxy aware of the JSESSIONID session cookie and/or the
jsessionid path parameter to provide sticky-session-handling.

If you use Apache httpd + mod_jk, you get some configuration-less
configuration for free such as TLS information being forwarded
automatically to the Tomcat node.

If you want to use HTTP as your proxying protocol, then you'll have to
arrange for the various data to be packed-into HTTP headers to be sent
to Tomcat. You can use Tomcat's RemoteIPValve to consume those HTTP
headers to provide the reverse proxy's connection information to
Tomcat (and thus, your web application).

Members of this list have experience with all kinds of reverse-proxy
servers. My deepest experience is with httpd+mod_jk+Tomcat while
others may use httpd+mod_proxy_http+Tomcat or nginx+Tomcat or
haproxy+Tomcat or squid+Tomcat. Or even IIS + Tomcat if necessary.

Apache httpd is a fairly heavy web server to use if all you want to do
is load-balancing and proxying. If there is another reason to use
httpd then by all means use it.

I would say you should check to see who will be supporting the
load-balancer and ask them what their preference is. It's far more
important to make sure the load-balancer is maintained properly than
to pick one based solely upon the recommendations of the members of
this mailing list.

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

iQIcBAEBCAAGBQJXfXvjAAoJEBzwKT+lPKRYlG0P/2Ng5ruyCxSqRg1Sqp6wYKqT
i79Pw12xzi0oCN3ekJtPvZDGF5hd2YRjorhCljKbt2yBWw2wMhJE159TMI5T3wvB
8P88dpGLDDLAWxgxT2YaRzlpCYYBQyTwQ/vYboA1UjJuLqE4jj9z7xlvwS0w7yeL
3aWsYyxRcCTu2NGv+VT0ayib2C4iqYkJGD2gqHp7hsN91fqb69/fRJtvhy5Ix4W1
U9cvGrwo8MfBzJ4/8KDE+DbWxBLX9bo3hkzo9Uaavb9rhlcMJIaP8iQv2/GP7qID
yc0geI5rUmkLp0nIb+REzmGAAki/mWDyYp+YHQz9N05kqUKj352ffY01L823RLHd
2lNosx8xuOu94NbnVq8QGM/B55AKdB4hx+ShhzwfA8MJocaLv79odaQG3JrE99i/
xsQ0LZOhxlwVJjGJtsEP6cdjx6vgAjyOXqvlu1/On0mECz7FNFpCYUTpTkb78F5p
vxNQe1a2PRXIFhPl4mXRIXMlCyDhXn5cja81V5oqhuOT5rb2D+PT3z+0xar0YgXy
/xdyBebKVH/0ndE9KDIqz2Yqf0QVq+WKiQqQA6TNYB5NKg1NpyBzCoYk110H8uyx
bLYVJWaNZGrwoqmrkl1VAPK6Eu4DD+RhtSmosAiHerJ7BDtB7q1mq7iLk2qoaTrr
M4eOM5j8IWyh9vhJEfUw
=sFyG
-END PGP SIGNATURE-

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

Re: Fedora 23 ROOT##000 just hangs on startup.

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Paul,

On 7/6/16 5:11 PM, Paul Roubekas wrote:
> On 7/6/2016 5:00 PM, Paul Roubekas wrote:
>> On 7/6/2016 4:39 PM, Christopher Schultz wrote:
>>> Paul,
>>> 
>>> On 7/6/16 4:10 PM, Paul Roubekas wrote:
 Works just find on my window 7 workstation with Eclipse 4.5.2
 but now on Fedora 23 the startup just hangs.
>>> 
>>> What do you mean "just hangs"? Take a thread dump of the
>>> process to see what it's doing. What do the logs say?
>>> 
 Moved the webapps/ROOT directory to ${CATALINA_HOME} which
 work just fine on the windows workstation.
>>> 
>>> So:
>>> 
>>> $ mv ${CATALINA_HOME}/webapps/ROOT ${CATALINA_HOME}
>>> 
>>> ??
>> Yes that is what I did.  I could have moved it to /tmp.  But
>> since there were no issue on the workstation I did the same thing
>> on the server.
>>> 
>>> So, ROOT is now ${CATALINA_HOME}/ROOT?
>> Yes
>>> 
 Double checked the server.xml file.
>>> 
 Made sure the WAR had the same owner and group as all the
 other tomcat artifacts.
>>> 
 Windows startup allows "/" in the 'path' but Fedora startup
 gave a warning so I changed path to "".   Which stopped the
 warning on startup.
>>> 
>>> A context path of "/" is invalid. Leave it as "". Better yet,
>>> remove the whole  element from server.xml.
>>> 
> All that did was cause the startup to lockup sooner, at the step
> below. INFO: OpenWebBeans Container has started, it took 283 ms. 
> Jul 06, 2016 5:08:19 PM
> org.apache.tomee.catalina.TomcatWebAppBuilder deployWebApps INFO:
> using context file
> /opt/tomee/webapps/ROOT##000/META-INF/context.xml Jul 06, 2016
> 5:08:19 PM org.apache.tomee.catalina.TomcatWebAppBuilder init INFO:
> - localhost -> /

So you get that INFO message and then .. nothing?

This is evidently TomEE which may do things slightly differently, but
generally speaking, if you have a WAR file in webapps/ then it will be
automatically-deployed and you don't need any other
application-specific configuration: just drop your WAR file in there
and let it deploy. Using ROOT##000.war will use the WAR file "version"
of 000 which will allow for parallel deployment of the ROOT context.

Are there no other messages in the log file? Are there any other log
files in logs/ ?

What about a thread dump after Tomcat stops responding?

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

iQIcBAEBCAAGBQJXfXnYAAoJEBzwKT+lPKRYs/IP/0xAzwHu+Bq4ElgZPzRAW/hO
10poYOXjz2e02ayFqzeSVQtSO2N4taVagWzc9y14X0ydQAEidp9u/KddMdddvtLE
p4RUl2+gk9ckQ9BnFSZubNq6qIsKGMBN0oeWqoyNn8F9Eo9l/LIFB6CqJLEOCmnH
VzfSbNUl1gLsDktbfEZx6WXJEEj0taO1of0trqnRz37bxNaS2Cdjgk1SU/cWkduw
OUwEf2kcgBUq4Z5nz9oYqFV7S9e56stiQ4cjYXZYBwoKDcn5SoyfdH+bwNmu3fZj
oDCeEBfYgfp2hYu3QdtPyhVLmkLr5LL9WlowtyBlsMb8C/teBoLvlPCtW3pzA6jS
2HNJKFblyUiEqnWw9YVnAQgkvIxocf1mLRrbwe+rrnYcIdp4RE3Y8YGfI6C01lvQ
nIKNiMbdIz7zYO4RD+GokCMK28OlS0RGPZCjJh3u0wcM1NnEU/64c2PJuWOabUKn
FNBp9dXfUTdS5BLA2cBv9QQ0xHidKnUnls1/Pcu4wKYCnegh+SvxfsX27hYPlzlx
rhGT2MWyvObosFEXFFjFFe/6EbMw1Nl/dLluh9mzkVbK6rGQfOxxezcQH9hShUlE
M7J/gsSAVuyx4eaNKk3C8zk/KTAuHuY8OYSSei7iLku1ozgZDz/jVuGO2/MAh/7o
cwBxhMXlEzix/zY8ZzJc
=/G+p
-END PGP SIGNATURE-

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

Re: Load Balancing Oracle Apex Application on Apache tomcat.

[chandra sekhar]

Hi Christopher,

Oracle Apex is a web application to build a web based application.It will
retrieves the static file content from DB by executing stored procedures
etc.Hence,for this it creates sessions in the DB as well.Session can be
distributed.So we are thinking to load balance.Please advice.

Thanks,
Chandra

On Wed, Jul 6, 2016 at 4:05 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Chandra,
>
> On 7/6/16 12:08 PM, chandra sekhar wrote:
> > We were using  apache-tomcat-7.0.55 for our Oracle Apex 4.2.5
> > Application on Linux(Linux 2.6.32-573.22.1.el6.x86_64 x86_64
> > GNU/Linux).
> >
> > As we have around 300-500 users using this application,we would
> > like to know if we can load balance our Oracle Apex Application on
> > 2 or 3 frontend servers to distribute the load.Hence,kindly help me
> > how to configure load balance on Apache tomcat.
> >
> > I'm open to tips and advices ;)
>
> We need more requirements to actually help. For example, I have no
> clue what Oracle Apex is. Does it use sessions? Are they
> distributable? Do you just want load-balancing, or do you need
> seamless-failover?
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJXfWSIAAoJEBzwKT+lPKRYZq8P/iU7fUMmDT3/9UEFy2jazLZy
> D0EhDJjhrzaAjQQCUL2Ywl6XkmS0EnaxU2pySoWoG+mzI1mrBNiGP+RvmUoOLGZc
> wjx+e56z7P2UTNl+6k+Q7qjEodqlWe6XTB9RrLg8ecXqHa/1TY5dWR0Jg7HylK7m
> OYiIQ0iygkyhcquAxmeCqqQNN5ByhXtIE5uHXMJgzQeELj2RwQ+AiX8nPYYb7Yq4
> JvPjun/RHgRT3zUEByflCdGvdedesItKjvACvVCwGQMzSgRYlqtzvisP0oi0il5R
> tFvePF/6knlAlFSLtAG4Uy5dWpOnouHznAra8Ud9MsXFHI695I8+7xSE+7dx/cUd
> ipLGk9JpZyDyuwJ1tpThMjBmBTtnPDNSs7GHZAcsFtzhButvnZOwO4kz64aNk7Yt
> Dwsw3H939KITr0yCffcc7TZ6V0vOLJl12MANX2xxsKejbhSO+VAyC27JpRFivUQL
> lidJrXk50g3Ka2v3nUDE/cmOLzYO6ibwEwXs3zqzt2S1w390A/8igwhiLR/+nc+4
> xCTUyZBRcPZ7sC9DSCqiztfChoRIYc8IOXE0BE8NyoOJl1SWSO/L6LjElX3UtF4O
> UpohbzbFHVigfsjaHM3NXhMkNsLfVN2n0/tE1GZQ7rBvmPlGfknwB/t0hWFw98Av
> 1xw98gTVREZwumaCFnsg
> =QW1U
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: poor upload performance with isapi_redirect.dll and IIS

[hugh holston]

please unsubscribe. thanks

  From: Christopher Schultz 
 To: Tomcat Users List  
 Sent: Wednesday, July 6, 2016 3:08 PM
 Subject: Re: poor upload performance with isapi_redirect.dll and IIS
   
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Andy,

On 7/6/16 4:05 PM, Wang, Andy wrote:
> On Fri, 2016-07-01 at 17:16 +, Wang, Andy wrote:
>> We're seeing some really poor performance with isapi_redirect.dll
>> and uploading files with IIS.
>> 
>> In a particular example, using a 200MB file, the file upload
>> (POST) takes ~50 seconds on localhost.
>> 
>> The same upload using Apache and mod_jk takes about ~6 seconds.
>> 
>> The interesting thing is, on a remote client, the behavior is
>> almost the same. Upload to IIS takes ~50 seconds, upload to
>> apache/mod_jk takes ~7 seconds.
>> 
>> I've done some wireshark captures have found some of the
>> differences.
>> 
>> Apache streams to mod_jk as the upload is occurring.
>> 
>> IIS appears to be buffering the entire upload before finally 
>> streaming to tomcat via ajp.  The TCP recieve window is regularly
>> being starved (ZeroWindow) and the client has to wait for a
>> window update before being able to send more.  I'm not familiar
>> with ISAPI at all, so I don't know if the responsibility on the
>> buffering of the POST is an IIS issue, or is the isapi_redirect
>> filter the problem?  Or is there some overall limitation with
>> isapi?
>> 
> 
> Apparently the site that was running into this problem had someone
> set uploadReadAheadSize to 2GB in IIS.  That specifically controls
> the amount that IIS buffers before sending to isapi.
> 
> So that was it.  Dialing that back appears to have solved the
> issue.

Thanks for posting back. It's a good addition to the archives even
though nobody here ended up helping you :)

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

iQIcBAEBCAAGBQJXfWUsAAoJEBzwKT+lPKRYj6sQAK1aBF/wO/CuS6QSgIH1HFiO
r29An9vcXYBU+axOgMvwfewo1wpvYjSm6PL49Twivn84xQn4B+a+jtIj826OoyUg
QblP4jEI/kiephVX3PXOhUye9ECFv44IiKcTAcUIXAFiSDKOQxRtPNHZxAmFkbT5
rucfaKSge87Hx10UtnccMgRbpezl/xylty+aI/QKdEaLFhnyYt8s9LtbDiEnqjtW
p4mOw6yQ/6i+ajSQ+1r+M2/ZUqlDwmUf/nUeCemVB2kYOj99mU6lbWPr1+nIbvh7
CVbKQCW2Jx6dKfMLNmdnXM6C3oPQ7H3D1IA/MkmnHpIdKKm+iBsYOFIirA7QLx2o
HthzsNi6cFBWCy2QlUhy1VvAsFC/uJKqQXPOEI2Em84o6Cx2n+WDQDP7T0GAwx+u
DCLxqabhxRBCR63ZBNwzi3chB/5bfG8b8x+17VL9wFCUpjhw2mSOML0CH+a+0Y9W
mR/h5d7/qLtnmVlB48PGAs7IYILHxuaQp1LCtXN48W9CP00G/W8T0Kqeuo2mXg72
WQ1sMxbXSwCyiYN1GTcRC8blhR6wS3ytQ0ol6mDHAq1sLMMnumOYuLJxlIa/mJPU
KP3e0yvuMX73WHhQ5OOKmpzWSiwEM8apMtUti8IqXmv/+YOqyOypLc1hO6ryefYI
TPPzcVJ7j3sPbjkZfjOr
=uzQu
-END PGP SIGNATURE-

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



  

Re: Fedora 23 ROOT##000 just hangs on startup.

[Paul Roubekas]

On 7/6/2016 5:00 PM, Paul Roubekas wrote:
> On 7/6/2016 4:39 PM, Christopher Schultz wrote:
>> Paul,
>>
>> On 7/6/16 4:10 PM, Paul Roubekas wrote:
>> > Works just find on my window 7 workstation with Eclipse 4.5.2 but
>> > now on Fedora 23 the startup just hangs.
>>
>> What do you mean "just hangs"? Take a thread dump of the process to
>> see what it's doing. What do the logs say?
>>
>> > Moved the webapps/ROOT directory to ${CATALINA_HOME} which work
>> > just fine on the windows workstation.
>>
>> So:
>>
>> $ mv ${CATALINA_HOME}/webapps/ROOT ${CATALINA_HOME}
>>
>> ??
> Yes that is what I did.  I could have moved it to /tmp.  But since
> there were no issue on the workstation I did the same thing on the server.
>>
>> So, ROOT is now ${CATALINA_HOME}/ROOT?
> Yes
>>
>> > Double checked the server.xml file.
>>
>> > Made sure the WAR had the same owner and group as all the other
>> > tomcat artifacts.
>>
>> > Windows startup allows "/" in the 'path' but Fedora startup gave a
>> > warning so I changed path to "".   Which stopped the warning on
>> > startup.
>>
>> A context path of "/" is invalid. Leave it as "". Better yet, remove
>> the whole  element from server.xml.
>>
All that did was cause the startup to lockup sooner, at the step below.
INFO: OpenWebBeans Container has started, it took 283 ms.
Jul 06, 2016 5:08:19 PM org.apache.tomee.catalina.TomcatWebAppBuilder
deployWebApps
INFO: using context file /opt/tomee/webapps/ROOT##000/META-INF/context.xml
Jul 06, 2016 5:08:19 PM org.apache.tomee.catalina.TomcatWebAppBuilder init
INFO: - localhost -> /

>> > On the windows workstation I could pull up the tomcat manager page
>> > with "http://70.63.204.226/manager/html;.  But that is not up and
>> > running at the time of the startup hang either.
>>
>> > At the time of the hang the following were in the
>> > webapps/directory.
>>
>> > ROOT##000.war
>>
>> > ROOT##000.unpacked
>>
>> > ROOT
>>
>> > == server.xml ==
>>
>> > 
>>
>> Why are you deploying from server.xml instead of just using ROOT##000.wa
>> r?
> Did not know that was an option.  I will try that and report back the
> results.
>>
>> >  startup 
>>
>> > INFO: Deployed Application(path=/opt/tomee/webapps/ROOT##000) Jul
>> > 06, 2016 3:52:02 PM
>> > org.apache.openejb.persistence.PersistenceBootstrap
>> > getDefaultProvider INFO: Default JPA Provider changed to
>> > org.eclipse.persistence.jpa.PersistenceProvider Jul 06, 2016
>> > 3:52:03 PM org.apache.catalina.startup.SetAllPropertiesRule begin
>> > WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
>> > property 'maxSpareThreads' to '75' did not find a matching
>> > property. Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: Server
>> > version:Apache Tomcat (TomEE)/7.0.68 (1.7.4) Jul 06, 2016
>> > 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener log
>> > INFO: Server built:  Feb 8 2016 20:25:54 UTC Jul 06, 2016
>> > 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener log
>> > INFO: Server number: 7.0.68.0 Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: OS
>> > Name:   Linux Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: OS
>> > Version:4.4.7-300.fc23.x86_64 Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO:
>> > Architecture:  amd64 Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: Java
>> > Home:
>> > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc23.x86_64/jre Jul
>> > 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: JVM
>> > Version:   1.8.0_91-b14 Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: JVM
>> > Vendor:Oracle Corporation Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO:
>> > CATALINA_BASE: /opt/tomee Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO:
>> > CATALINA_HOME: /opt/tomee Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: Command
>> > line argument:
>> > -Djava.util.logging.config.file=/opt/tomee/conf/logging.properties
>> > Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: Command
>> > line argument:
>> > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>> > Jul 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: Command
>> > line argument: -javaagent:/opt/tomee/lib/openejb-javaagent.jar Jul
>> > 06, 2016 3:52:03 PM
>> > org.apache.catalina.startup.VersionLoggerListener log INFO: Command
>> > line argument: -Djava.endorsed.dirs=/opt/tomee/endorsed Jul 06,
>> > 2016 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener
>> > log 

Re: Fedora 23 ROOT##000 just hangs on startup.

[Paul Roubekas]

On 7/6/2016 4:39 PM, Christopher Schultz wrote:
> Paul,
>
> On 7/6/16 4:10 PM, Paul Roubekas wrote:
> > Works just find on my window 7 workstation with Eclipse 4.5.2 but
> > now on Fedora 23 the startup just hangs.
>
> What do you mean "just hangs"? Take a thread dump of the process to
> see what it's doing. What do the logs say?
>
> > Moved the webapps/ROOT directory to ${CATALINA_HOME} which work
> > just fine on the windows workstation.
>
> So:
>
> $ mv ${CATALINA_HOME}/webapps/ROOT ${CATALINA_HOME}
>
> ??
Yes that is what I did.  I could have moved it to /tmp.  But since there
were no issue on the workstation I did the same thing on the server.
>
> So, ROOT is now ${CATALINA_HOME}/ROOT?
Yes
>
> > Double checked the server.xml file.
>
> > Made sure the WAR had the same owner and group as all the other
> > tomcat artifacts.
>
> > Windows startup allows "/" in the 'path' but Fedora startup gave a
> > warning so I changed path to "".   Which stopped the warning on
> > startup.
>
> A context path of "/" is invalid. Leave it as "". Better yet, remove
> the whole  element from server.xml.
>
> > On the windows workstation I could pull up the tomcat manager page
> > with "http://70.63.204.226/manager/html;.  But that is not up and
> > running at the time of the startup hang either.
>
> > At the time of the hang the following were in the
> > webapps/directory.
>
> > ROOT##000.war
>
> > ROOT##000.unpacked
>
> > ROOT
>
> > == server.xml ==
>
> > 
>
> Why are you deploying from server.xml instead of just using ROOT##000.wa
> r?
Did not know that was an option.  I will try that and report back the
results.
>
> >  startup 
>
> > INFO: Deployed Application(path=/opt/tomee/webapps/ROOT##000) Jul
> > 06, 2016 3:52:02 PM
> > org.apache.openejb.persistence.PersistenceBootstrap
> > getDefaultProvider INFO: Default JPA Provider changed to
> > org.eclipse.persistence.jpa.PersistenceProvider Jul 06, 2016
> > 3:52:03 PM org.apache.catalina.startup.SetAllPropertiesRule begin
> > WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
> > property 'maxSpareThreads' to '75' did not find a matching
> > property. Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: Server
> > version:Apache Tomcat (TomEE)/7.0.68 (1.7.4) Jul 06, 2016
> > 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener log
> > INFO: Server built:  Feb 8 2016 20:25:54 UTC Jul 06, 2016
> > 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener log
> > INFO: Server number: 7.0.68.0 Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: OS
> > Name:   Linux Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: OS
> > Version:4.4.7-300.fc23.x86_64 Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO:
> > Architecture:  amd64 Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: Java
> > Home:
> > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc23.x86_64/jre Jul
> > 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: JVM
> > Version:   1.8.0_91-b14 Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: JVM
> > Vendor:Oracle Corporation Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO:
> > CATALINA_BASE: /opt/tomee Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO:
> > CATALINA_HOME: /opt/tomee Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: Command
> > line argument:
> > -Djava.util.logging.config.file=/opt/tomee/conf/logging.properties
> > Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: Command
> > line argument:
> > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> > Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: Command
> > line argument: -javaagent:/opt/tomee/lib/openejb-javaagent.jar Jul
> > 06, 2016 3:52:03 PM
> > org.apache.catalina.startup.VersionLoggerListener log INFO: Command
> > line argument: -Djava.endorsed.dirs=/opt/tomee/endorsed Jul 06,
> > 2016 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener
> > log INFO: Command line argument: -Dcatalina.base=/opt/tomee Jul 06,
> > 2016 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener
> > log INFO: Command line argument: -Dcatalina.home=/opt/tomee Jul 06,
> > 2016 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener
> > log INFO: Command line argument: -Djava.io.tmpdir=/opt/tomee/temp
> > Jul 06, 2016 3:52:03 PM
> > org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO:
> > The APR based Apache Tomcat Native library which allows optimal
> > performance in production environments was not found 

Re: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Steve,

On 7/6/16 4:22 PM, Mekkelsen Madden, Steve wrote:
> Here is the image I tried attaching.  Sorry about that. 
> [redacted... my SMTP server really doesn't like that URL]

So... what are we looking at, here?

I see a POST URL that looks perfectly fine. I also see XML in the POST
request. Is this a shot of Fiddler? Where is the problem?

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

iQIcBAEBCAAGBQJXfW3LAAoJEBzwKT+lPKRYGsMP/3h+wQNIHoC/95G0VxQY75Kh
ClI+ny5Z5NeyVsA8iCrZ1rIr/fBEzE/nnHWlX16yPhkaCBQ8PwJ+i2MV11rYArU9
yUIhL2xyAxVAqyBUZGrNidzz6gydvJd2MPNGrtHg6shaIA7XtflX9gMUV16J+3m+
7VC+E+lLBwOEcrYbpxJNni36Cn4QQ6f6sHMgLKsbGZZ6PSl7MGVPts6oz6SUkt6T
rwwPF6QLuovnndWlqt9HDaJtTD9/a9emSZgXKPQYACp8poSZ8xM7SxPn9f1XnX6l
iyOEc9RYJ3bvKocC8iMKCpSn41/XAGpiS3dwpYbNrN15sd2emRze2seDfJVI4Xtm
1d7GRqXUadjCjq/PzDSihrFjHBU+6+7BKd/hdqn6raci6HbtQPizkUTkPDWPXUTg
T9Y7TOvi9zZNro9jLxErluN/A/niY8so53DFqT2kxV9wr2COf3dRu8UTyFM/4Mul
6bcGpno5CjvpfwVltlB8BTwRUctGEWe3kYcUfUBOTMNFFAMUYq+/4saL/gOATD8P
LMcNXqbkex5fPrARU+vGgQvanFGeZMR7w9UXJbd9ACEWJUgRAnr18/5RtbVzWVjO
gd4uPaLFgyFV573Hpe4Luzg7OngDu7BXZqThKXXaiG4cZSKmdjyjJVb4709GMOWc
ARZb7MipIot/KGBBJhNd
=bPg7
-END PGP SIGNATURE-

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

Re: tomcat 7.0.55 jdbc pool "Not a wrapper of oracle.jdbc.OracleConnection"

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Vishal,

On 6/30/16 10:46 AM, Balana, Vishal wrote:
> I have following resource configuration for Oracle Data source
> Pool and trying to unwrap the connection object using:
> 
> OracleConnection conn = connection.unwrap(OracleConnection.class);

Why do you need an OracleConnection instead of a standard
java.sql.Connection?

> And getting following exception:
> 
> com.sun.proxy.$Proxy77.unwrap exception : java.sql.SQLException:
> Not a wrapper of oracle.jdbc.OracleConnection
> 
> Anybody has any idea what is missing here?
> 
>  type="javax.sql.DataSource" 
> factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" 
> driverClassName="oracle.jdbc.driver.OracleDriver" 
> url="jdbc:oracle:thin:@(XYZ)" username="ABC" password="ABC" 
> initialSize="10" maxActive="10" minIdle="10" maxIdle="10" 
> maxWait="1" timeBetweenEvictionRunsMillis="3" 
> minEvictableIdleTimeMillis="3" testOnBorrow="true" 
> validationQuery="select 1 from dual" validationInterval="3" 
> removeAbandoned="true" removeAbandonedTimeout="600" 
> logAbandoned="true" testWhileIdle="false" testOnReturn="false" 
> jmxEnabled="true" accessToUnderlyingConnectionAllowed="true" 
> jdbcInterceptors="org.apache.tomcat.jdbc.pool.interceptor.ConnectionSt
ate;org.apache.tomcat.jdbc.pool.interceptor.StatementFinalizer;org.apach
e.tomcat.jdbc.pool.interceptor.ResetAbandonedTimer"/>

You
> 
are using a JDBC connection pool, so the connections coming from
the pool aren't raw OracleConnections.

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

iQIcBAEBCAAGBQJXfW0dAAoJEBzwKT+lPKRYU9UP/3+YNbwMbGAnugOJ1SFXQg4K
w7j2MkuzQzAAJ1RHOqITdLKhsC0p+FYvGZvvop9m+c5KEarhrEqkT4AS13kQauKh
frsjxZwBEGh9XJp/D/7bbmY9C7z/2jcx2QAk4ddfBY3CVzKUyaR8WG/hNi4yTXFE
oiOBDLDOjj1zPjsSK8bwhm9g84eeyJF4zxocWF5YXECrVXl6FypV+yUcWEoOzCqG
fUVsII1HnRN0bg/CvH+38kIa6tdnnbMtxW2iBmpoZak4tYar/UR3gtkdR/oQ4COA
yKiP1vmMCbka2LAcK0Y9eysFiuhU/IXxxK+jyxl5QRTI9IIaf6/RYogjgi4mhv/e
q5E6nmHkalpMU6l1Fbp3vhuXFBGgwQDtu0XRPyIYy1JKV6GtQqEuh31bUQf3Ntc0
ZI1TMMc1SmwbYO+Jv4uoo72maL2aL8z+v3Ad6lynQ064/x+GtRfQJHmzm8NGcGOK
Fl8z5ef6GxhmXZxs0GJp6dygWTJ2ZZ8kgX7lyhM8XruifQggdCZ6/PFst1R6ivWx
nMegJ2RTk1musMYHk7izpPlNGsDCG9fqyjYMu7FIBtASYlbeoLK7flExkVl1Dvee
D+CuSEsP9EckNLLe7WOUEvAD0vAAVYJJljUvj0Ka4Nif9VgytNRffr4glk0AWoX6
VAyhTcl9qzJ93C5KMn14
=McMB
-END PGP SIGNATURE-

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

Re: Fedora 23 ROOT##000 just hangs on startup.

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Paul,

On 7/6/16 4:10 PM, Paul Roubekas wrote:
> Works just find on my window 7 workstation with Eclipse 4.5.2 but
> now on Fedora 23 the startup just hangs.

What do you mean "just hangs"? Take a thread dump of the process to
see what it's doing. What do the logs say?

> Moved the webapps/ROOT directory to ${CATALINA_HOME} which work
> just fine on the windows workstation.

So:

$ mv ${CATALINA_HOME}/webapps/ROOT ${CATALINA_HOME}

??

So, ROOT is now ${CATALINA_HOME}/ROOT?

> Double checked the server.xml file.
> 
> Made sure the WAR had the same owner and group as all the other
> tomcat artifacts.
> 
> Windows startup allows "/" in the 'path' but Fedora startup gave a 
> warning so I changed path to "".   Which stopped the warning on
> startup.

A context path of "/" is invalid. Leave it as "". Better yet, remove
the whole  element from server.xml.

> On the windows workstation I could pull up the tomcat manager page
> with "http://70.63.204.226/manager/html;.  But that is not up and
> running at the time of the startup hang either.
> 
> At the time of the hang the following were in the
> webapps/directory.
> 
> ROOT##000.war
> 
> ROOT##000.unpacked
> 
> ROOT
> 
> == server.xml ==
> 
> 

Why are you deploying from server.xml instead of just using ROOT##000.wa
r?

>  startup 
> 
> INFO: Deployed Application(path=/opt/tomee/webapps/ROOT##000) Jul
> 06, 2016 3:52:02 PM 
> org.apache.openejb.persistence.PersistenceBootstrap
> getDefaultProvider INFO: Default JPA Provider changed to 
> org.eclipse.persistence.jpa.PersistenceProvider Jul 06, 2016
> 3:52:03 PM org.apache.catalina.startup.SetAllPropertiesRule begin 
> WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting 
> property 'maxSpareThreads' to '75' did not find a matching
> property. Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: Server
> version:Apache Tomcat (TomEE)/7.0.68 (1.7.4) Jul 06, 2016
> 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener log 
> INFO: Server built:  Feb 8 2016 20:25:54 UTC Jul 06, 2016
> 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener log 
> INFO: Server number: 7.0.68.0 Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: OS
> Name:   Linux Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: OS
> Version:4.4.7-300.fc23.x86_64 Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO:
> Architecture:  amd64 Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: Java
> Home: 
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc23.x86_64/jre Jul
> 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: JVM
> Version:   1.8.0_91-b14 Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: JVM
> Vendor:Oracle Corporation Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO:
> CATALINA_BASE: /opt/tomee Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO:
> CATALINA_HOME: /opt/tomee Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: Command
> line argument: 
> -Djava.util.logging.config.file=/opt/tomee/conf/logging.properties 
> Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: Command
> line argument: 
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
> Jul 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: Command
> line argument: -javaagent:/opt/tomee/lib/openejb-javaagent.jar Jul
> 06, 2016 3:52:03 PM 
> org.apache.catalina.startup.VersionLoggerListener log INFO: Command
> line argument: -Djava.endorsed.dirs=/opt/tomee/endorsed Jul 06,
> 2016 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener
> log INFO: Command line argument: -Dcatalina.base=/opt/tomee Jul 06,
> 2016 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener
> log INFO: Command line argument: -Dcatalina.home=/opt/tomee Jul 06,
> 2016 3:52:03 PM org.apache.catalina.startup.VersionLoggerListener
> log INFO: Command line argument: -Djava.io.tmpdir=/opt/tomee/temp 
> Jul 06, 2016 3:52:03 PM
> org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO:
> The APR based Apache Tomcat Native library which allows optimal 
> performance in production environments was not found on the 
> java.library.path: 
> /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib Jul
> 06, 2016 3:52:03 PM org.apache.coyote.AbstractProtocol init INFO:
> Initializing ProtocolHandler ["http-bio-80"] Jul 06, 2016 3:52:03
> PM org.apache.coyote.AbstractProtocol init INFO: Initializing
> ProtocolHandler ["http-bio-443"] Jul 06, 2016 3:52:04 PM
> 

Re: Fedora 23 ROOT##000 just hangs on startup.

[Paul Roubekas]

On 7/6/2016 4:19 PM, André Warnier (tomcat) wrote:
> On 06.07.2016 22:10, Paul Roubekas wrote:
>> Works just find on my window 7 workstation with Eclipse 4.5.2 but now on
>> Fedora 23 the startup just hangs.
>>
>> Moved the webapps/ROOT directory to ${CATALINA_HOME} which work just
>> fine on the windows workstation.
>>
>> Double checked the server.xml file.
>>
>> Made sure the WAR had the same owner and group as all the other tomcat
>> artifacts.
>>
>> Windows startup allows "/" in the 'path' but Fedora startup gave a
>> warning so I changed path to "".   Which stopped the warning on startup.
>>
>> On the windows workstation I could pull up the tomcat manager page with
>> "http://70.63.204.226/manager/html;.  But that is not up and running at
>> the time of the startup hang either.
>>
>> At the time of the hang the following were in the webapps/directory.
>>
>>  ROOT##000.war
>>
>>  ROOT##000.unpacked
>>
>>  ROOT
>>
>> == server.xml ==
>>
>>  
>>
>>  startup 
>>
>> INFO: Deployed Application(path=/opt/tomee/webapps/ROOT##000)
>> Jul 06, 2016 3:52:02 PM
>> org.apache.openejb.persistence.PersistenceBootstrap getDefaultProvider
>> INFO: Default JPA Provider changed to
>> org.eclipse.persistence.jpa.PersistenceProvider
>> Jul 06, 2016 3:52:03 PM org.apache.catalina.startup.SetAllPropertiesRule
>> begin
>> WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
>> property 'maxSpareThreads' to '75' did not find a matching property.
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Server version:Apache Tomcat (TomEE)/7.0.68 (1.7.4)
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Server built:  Feb 8 2016 20:25:54 UTC
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Server number: 7.0.68.0
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: OS Name:   Linux
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: OS Version:4.4.7-300.fc23.x86_64
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Architecture:  amd64
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Java Home:
>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc23.x86_64/jre
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: JVM Version:   1.8.0_91-b14
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: JVM Vendor:Oracle Corporation
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: CATALINA_BASE: /opt/tomee
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: CATALINA_HOME: /opt/tomee
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Command line argument:
>> -Djava.util.logging.config.file=/opt/tomee/conf/logging.properties
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Command line argument:
>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Command line argument:
>> -javaagent:/opt/tomee/lib/openejb-javaagent.jar
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Command line argument: -Djava.endorsed.dirs=/opt/tomee/endorsed
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Command line argument: -Dcatalina.base=/opt/tomee
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Command line argument: -Dcatalina.home=/opt/tomee
>> Jul 06, 2016 3:52:03 PM
>> org.apache.catalina.startup.VersionLoggerListener log
>> INFO: Command line argument: -Djava.io.tmpdir=/opt/tomee/temp
>> Jul 06, 2016 3:52:03 PM org.apache.catalina.core.AprLifecycleListener
>> lifecycleEvent
>> INFO: The APR based Apache Tomcat Native library which allows optimal
>> performance in production environments was not found on the
>> java.library.path:
>> /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
>> Jul 06, 2016 3:52:03 PM org.apache.coyote.AbstractProtocol init
>> INFO: Initializing ProtocolHandler ["http-bio-80"]
>> Jul 06, 2016 3:52:03 PM org.apache.coyote.AbstractProtocol init
>> INFO: Initializing ProtocolHandler ["http-bio-443"]
>> Jul 06, 2016 3:52:04 PM org.apache.coyote.AbstractProtocol init
>> INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
>> Jul 06, 2016 3:52:05 PM org.apache.openejb.util.OptionsLog info
>> INFO: Using
>> 'openejb.jdbc.datasource-creator=org.apache.tomee.jdbc.TomEEDataSourceCreator'
>>
>> Jul 06, 2016 3:52:05 PM 

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

[Mekkelsen Madden, Steve]

Here is the image I tried attaching.  Sorry about that.  
https://ibin.co/2n9zIx3n9qUH.jpg


Regards,

Steve Mekkelsen Madden  |  Systems Engineer Fellow / DBA / Certified Scrum 
Master  | GCS |  Pegasystems Inc.
Office: (617) 866.6023 | Mobile: (828) 729.9948 | Email: 
steve.mekkelsen.mad...@pega.com | www.pega.com


-Original Message-
From: Mekkelsen Madden, Steve 
Sent: Wednesday, July 06, 2016 3:44 PM
To: users@tomcat.apache.org
Subject: RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

Thanks Felix. See below


-Original Message-
From: Felix Schumacher [mailto:felix.schumac...@internetallee.de]
Sent: Wednesday, July 06, 2016 3:29 PM
To: users@tomcat.apache.org
Subject: Re: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

Am 06.07.2016 um 19:14 schrieb Mekkelsen Madden, Steve:
> This particular issue has raised a lot of issues in-house and we would 
> greatly appreciate a response from someone having more details on why NIO2 no 
> longer works.
>
> Thanks!
>
>
> -Original Message-
> From: Mekkelsen Madden, Steve
> Sent: Friday, July 01, 2016 12:56 PM
> To: Tomcat Users List 
> Subject: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding 
> issues
>
> Hi all,
>
> Is anyone aware of why after upgrading from Tomcat 8.0.32x64 (Windows) to 
> 8.5.3x64 using the connector protocol of: 
> protocol="org.apache.coyote.http11.Http11Nio2Protocol"  fails with url 
> encoding errors?  Once it was changed back to 
> protocol="org.apache.coyote.http11.Http11NioProtocol" all the errors stopped. 
>  This completely broke the application and made it unusable as the xml being 
> returned was not decoded and resulted in sax parse exceptions with our AJAX 
> connections.   I haven't found anything related to the protocol changing, 
> only the parameters for the SSL/TLS attributes which are in place and work.  
> It's almost like it's blocking the requests when it should be unblocking the 
> requests?  Thanks!!
Have you tried to compare the responses, that you get through the two 
connectors? Especially the characters before the xml prolog would be 
interesting.
Do you get the same errors, when you are requesting the url without tls?

Regards,
  Felix

Steve: We did not try turning off TLS in this case since this is what was 
already enabled in Production and required due to servers being accessible 
outside the network.  What the engineer found is that Fiddler showed all XML 
content (all the strings) that is being sent to and from the server were being 
encoded.  However, the XML content in fiddler does not have the encoded 
content.  I've attached a screenshot showing the request if that helps.

>
> Database Type: Oracle 12c Linux x64
> Driver used: ojdbc7.jar
> Connector attribute:  
>protocol="org.apache.coyote.http11.Http11NioProtocol"
>   maxThreads="150" disableUploadTimeout="true"
>   SSLEnabled="true"
>   sslDefaultHost="vgcspsteste1.rpega.com">
>
>certificateKeystoreFile="D:\certificates\ourcert.keystore" 
> certificateKeystorePassword="***" certificateKeyAlias="ourAlias" 
> type="RSA"/>
>
>   
> An example of the error looks like the below:
> 23 Jun 2016 01:28:39,731 [sl-nio2-8443-exec-11] 
> (ngineinterface.service.HttpAPI) ERROR: Error adopting XML from post data 
> com.pega.pegarules.pub.clipboard.InvalidStreamError: InvalidStream  
> com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(String, 
> StorageStream)   sax parse error: Content is not allowed in prolog.
> From: (H64E3757ED751A9AEE78817056219F4F9:10.224.243.66)
>   at 
> com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:477)
>   at 
> com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:432)
>   at 
> com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.adoptXMLForm(ClipboardPageImpl.java:818)
>   at 
> com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.mapInputData(HttpAPI.java:2481)
>   at 
> com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(EngineAPI.java:554)
>   at 
> com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:388)
>   at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1277)
>   at 
> com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1015)
>   at 
> com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:848)
>   at 
> 

Re: Fedora 23 ROOT##000 just hangs on startup.

[tomcat]

On 06.07.2016 22:10, Paul Roubekas wrote:

Works just find on my window 7 workstation with Eclipse 4.5.2 but now on
Fedora 23 the startup just hangs.

Moved the webapps/ROOT directory to ${CATALINA_HOME} which work just
fine on the windows workstation.

Double checked the server.xml file.

Made sure the WAR had the same owner and group as all the other tomcat
artifacts.

Windows startup allows "/" in the 'path' but Fedora startup gave a
warning so I changed path to "".   Which stopped the warning on startup.

On the windows workstation I could pull up the tomcat manager page with
"http://70.63.204.226/manager/html;.  But that is not up and running at
the time of the startup hang either.

At the time of the hang the following were in the webapps/directory.

 ROOT##000.war

 ROOT##000.unpacked

 ROOT

== server.xml ==

 

 startup 

INFO: Deployed Application(path=/opt/tomee/webapps/ROOT##000)
Jul 06, 2016 3:52:02 PM
org.apache.openejb.persistence.PersistenceBootstrap getDefaultProvider
INFO: Default JPA Provider changed to
org.eclipse.persistence.jpa.PersistenceProvider
Jul 06, 2016 3:52:03 PM org.apache.catalina.startup.SetAllPropertiesRule
begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
property 'maxSpareThreads' to '75' did not find a matching property.
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version:Apache Tomcat (TomEE)/7.0.68 (1.7.4)
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built:  Feb 8 2016 20:25:54 UTC
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number: 7.0.68.0
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name:   Linux
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version:4.4.7-300.fc23.x86_64
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture:  amd64
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc23.x86_64/jre
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version:   1.8.0_91-b14
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor:Oracle Corporation
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE: /opt/tomee
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME: /opt/tomee
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument:
-Djava.util.logging.config.file=/opt/tomee/conf/logging.properties
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument:
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -javaagent:/opt/tomee/lib/openejb-javaagent.jar
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.endorsed.dirs=/opt/tomee/endorsed
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.base=/opt/tomee
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=/opt/tomee
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.io.tmpdir=/opt/tomee/temp
Jul 06, 2016 3:52:03 PM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Jul 06, 2016 3:52:03 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-80"]
Jul 06, 2016 3:52:03 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-443"]
Jul 06, 2016 3:52:04 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jul 06, 2016 3:52:05 PM org.apache.openejb.util.OptionsLog info
INFO: Using
'openejb.jdbc.datasource-creator=org.apache.tomee.jdbc.TomEEDataSourceCreator'
Jul 06, 2016 3:52:05 PM org.apache.openejb.OpenEJB$Instance 
INFO:

Jul 06, 2016 3:52:05 PM org.apache.openejb.OpenEJB$Instance 
INFO: OpenEJB http://tomee.apache.org/
Jul 06, 2016 3:52:05 PM org.apache.openejb.OpenEJB$Instance 
INFO: Startup: Wed Jul 06 15:52:05 EDT 2016
Jul 06, 2016 3:52:05 PM org.apache.openejb.OpenEJB$Instance 

Fedora 23 ROOT##000 just hangs on startup.

[Paul Roubekas]

Works just find on my window 7 workstation with Eclipse 4.5.2 but now on
Fedora 23 the startup just hangs. 

Moved the webapps/ROOT directory to ${CATALINA_HOME} which work just
fine on the windows workstation. 

Double checked the server.xml file. 

Made sure the WAR had the same owner and group as all the other tomcat
artifacts. 

Windows startup allows "/" in the 'path' but Fedora startup gave a
warning so I changed path to "".   Which stopped the warning on startup. 

On the windows workstation I could pull up the tomcat manager page with
"http://70.63.204.226/manager/html;.  But that is not up and running at
the time of the startup hang either.

At the time of the hang the following were in the webapps/directory.

ROOT##000.war

ROOT##000.unpacked

ROOT

== server.xml ==



 startup 

INFO: Deployed Application(path=/opt/tomee/webapps/ROOT##000)
Jul 06, 2016 3:52:02 PM
org.apache.openejb.persistence.PersistenceBootstrap getDefaultProvider
INFO: Default JPA Provider changed to
org.eclipse.persistence.jpa.PersistenceProvider
Jul 06, 2016 3:52:03 PM org.apache.catalina.startup.SetAllPropertiesRule
begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting
property 'maxSpareThreads' to '75' did not find a matching property.
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version:Apache Tomcat (TomEE)/7.0.68 (1.7.4)
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built:  Feb 8 2016 20:25:54 UTC
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number: 7.0.68.0
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name:   Linux
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version:4.4.7-300.fc23.x86_64
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture:  amd64
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home:
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-2.b14.fc23.x86_64/jre
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version:   1.8.0_91-b14
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor:Oracle Corporation
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE: /opt/tomee
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME: /opt/tomee
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument:
-Djava.util.logging.config.file=/opt/tomee/conf/logging.properties
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument:
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -javaagent:/opt/tomee/lib/openejb-javaagent.jar
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.endorsed.dirs=/opt/tomee/endorsed
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.base=/opt/tomee
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=/opt/tomee
Jul 06, 2016 3:52:03 PM
org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.io.tmpdir=/opt/tomee/temp
Jul 06, 2016 3:52:03 PM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Jul 06, 2016 3:52:03 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-80"]
Jul 06, 2016 3:52:03 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-443"]
Jul 06, 2016 3:52:04 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jul 06, 2016 3:52:05 PM org.apache.openejb.util.OptionsLog info
INFO: Using
'openejb.jdbc.datasource-creator=org.apache.tomee.jdbc.TomEEDataSourceCreator'
Jul 06, 2016 3:52:05 PM org.apache.openejb.OpenEJB$Instance 
INFO:

Jul 06, 2016 3:52:05 PM org.apache.openejb.OpenEJB$Instance 
INFO: OpenEJB http://tomee.apache.org/
Jul 06, 2016 3:52:05 PM org.apache.openejb.OpenEJB$Instance 
INFO: Startup: Wed Jul 06 15:52:05 EDT 2016
Jul 06, 2016 3:52:05 PM org.apache.openejb.OpenEJB$Instance 
INFO: Copyright 1999-2015 (C) 

Re: poor upload performance with isapi_redirect.dll and IIS

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Andy,

On 7/6/16 4:05 PM, Wang, Andy wrote:
> On Fri, 2016-07-01 at 17:16 +, Wang, Andy wrote:
>> We're seeing some really poor performance with isapi_redirect.dll
>> and uploading files with IIS.
>> 
>> In a particular example, using a 200MB file, the file upload
>> (POST) takes ~50 seconds on localhost.
>> 
>> The same upload using Apache and mod_jk takes about ~6 seconds.
>> 
>> The interesting thing is, on a remote client, the behavior is
>> almost the same. Upload to IIS takes ~50 seconds, upload to
>> apache/mod_jk takes ~7 seconds.
>> 
>> I've done some wireshark captures have found some of the
>> differences.
>> 
>> Apache streams to mod_jk as the upload is occurring.
>> 
>> IIS appears to be buffering the entire upload before finally 
>> streaming to tomcat via ajp.  The TCP recieve window is regularly
>> being starved (ZeroWindow) and the client has to wait for a
>> window update before being able to send more.  I'm not familiar
>> with ISAPI at all, so I don't know if the responsibility on the
>> buffering of the POST is an IIS issue, or is the isapi_redirect
>> filter the problem?  Or is there some overall limitation with
>> isapi?
>> 
> 
> Apparently the site that was running into this problem had someone
> set uploadReadAheadSize to 2GB in IIS.  That specifically controls
> the amount that IIS buffers before sending to isapi.
> 
> So that was it.  Dialing that back appears to have solved the
> issue.

Thanks for posting back. It's a good addition to the archives even
though nobody here ended up helping you :)

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

iQIcBAEBCAAGBQJXfWUsAAoJEBzwKT+lPKRYj6sQAK1aBF/wO/CuS6QSgIH1HFiO
r29An9vcXYBU+axOgMvwfewo1wpvYjSm6PL49Twivn84xQn4B+a+jtIj826OoyUg
QblP4jEI/kiephVX3PXOhUye9ECFv44IiKcTAcUIXAFiSDKOQxRtPNHZxAmFkbT5
rucfaKSge87Hx10UtnccMgRbpezl/xylty+aI/QKdEaLFhnyYt8s9LtbDiEnqjtW
p4mOw6yQ/6i+ajSQ+1r+M2/ZUqlDwmUf/nUeCemVB2kYOj99mU6lbWPr1+nIbvh7
CVbKQCW2Jx6dKfMLNmdnXM6C3oPQ7H3D1IA/MkmnHpIdKKm+iBsYOFIirA7QLx2o
HthzsNi6cFBWCy2QlUhy1VvAsFC/uJKqQXPOEI2Em84o6Cx2n+WDQDP7T0GAwx+u
DCLxqabhxRBCR63ZBNwzi3chB/5bfG8b8x+17VL9wFCUpjhw2mSOML0CH+a+0Y9W
mR/h5d7/qLtnmVlB48PGAs7IYILHxuaQp1LCtXN48W9CP00G/W8T0Kqeuo2mXg72
WQ1sMxbXSwCyiYN1GTcRC8blhR6wS3ytQ0ol6mDHAq1sLMMnumOYuLJxlIa/mJPU
KP3e0yvuMX73WHhQ5OOKmpzWSiwEM8apMtUti8IqXmv/+YOqyOypLc1hO6ryefYI
TPPzcVJ7j3sPbjkZfjOr
=uzQu
-END PGP SIGNATURE-

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

Re: Load Balancing Oracle Apex Application on Apache tomcat.

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Chandra,

On 7/6/16 12:08 PM, chandra sekhar wrote:
> We were using  apache-tomcat-7.0.55 for our Oracle Apex 4.2.5
> Application on Linux(Linux 2.6.32-573.22.1.el6.x86_64 x86_64
> GNU/Linux).
> 
> As we have around 300-500 users using this application,we would
> like to know if we can load balance our Oracle Apex Application on
> 2 or 3 frontend servers to distribute the load.Hence,kindly help me
> how to configure load balance on Apache tomcat.
> 
> I'm open to tips and advices ;)

We need more requirements to actually help. For example, I have no
clue what Oracle Apex is. Does it use sessions? Are they
distributable? Do you just want load-balancing, or do you need
seamless-failover?

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

iQIcBAEBCAAGBQJXfWSIAAoJEBzwKT+lPKRYZq8P/iU7fUMmDT3/9UEFy2jazLZy
D0EhDJjhrzaAjQQCUL2Ywl6XkmS0EnaxU2pySoWoG+mzI1mrBNiGP+RvmUoOLGZc
wjx+e56z7P2UTNl+6k+Q7qjEodqlWe6XTB9RrLg8ecXqHa/1TY5dWR0Jg7HylK7m
OYiIQ0iygkyhcquAxmeCqqQNN5ByhXtIE5uHXMJgzQeELj2RwQ+AiX8nPYYb7Yq4
JvPjun/RHgRT3zUEByflCdGvdedesItKjvACvVCwGQMzSgRYlqtzvisP0oi0il5R
tFvePF/6knlAlFSLtAG4Uy5dWpOnouHznAra8Ud9MsXFHI695I8+7xSE+7dx/cUd
ipLGk9JpZyDyuwJ1tpThMjBmBTtnPDNSs7GHZAcsFtzhButvnZOwO4kz64aNk7Yt
Dwsw3H939KITr0yCffcc7TZ6V0vOLJl12MANX2xxsKejbhSO+VAyC27JpRFivUQL
lidJrXk50g3Ka2v3nUDE/cmOLzYO6ibwEwXs3zqzt2S1w390A/8igwhiLR/+nc+4
xCTUyZBRcPZ7sC9DSCqiztfChoRIYc8IOXE0BE8NyoOJl1SWSO/L6LjElX3UtF4O
UpohbzbFHVigfsjaHM3NXhMkNsLfVN2n0/tE1GZQ7rBvmPlGfknwB/t0hWFw98Av
1xw98gTVREZwumaCFnsg
=QW1U
-END PGP SIGNATURE-

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

Re: poor upload performance with isapi_redirect.dll and IIS

[Wang, Andy]

On Fri, 2016-07-01 at 17:16 +, Wang, Andy wrote:
> We're seeing some really poor performance with isapi_redirect.dll and
> uploading files with IIS.
> 
> In a particular example, using a 200MB file, the file upload (POST)
> takes ~50 seconds on localhost. 
> 
> The same upload using Apache and mod_jk takes about ~6 seconds.
> 
> The interesting thing is, on a remote client, the behavior is almost
> the same.
> Upload to IIS takes ~50 seconds, upload to apache/mod_jk takes ~7
> seconds.
> 
> I've done some wireshark captures have found some of the differences.
> 
> Apache streams to mod_jk as the upload is occurring.
> 
> IIS appears to be buffering the entire upload before finally
> streaming
> to tomcat via ajp.  The TCP recieve window is regularly being starved
> (ZeroWindow) and the client has to wait for a window update before
> being able to send more.  I'm not familiar with ISAPI at all, so I
> don't know if the responsibility on the buffering of the POST is an
> IIS
> issue, or is the isapi_redirect filter the problem?  Or is there some
> overall limitation with isapi?
> 

Apparently the site that was running into this problem had someone set
uploadReadAheadSize to 2GB in IIS.  That specifically controls the
amount that IIS buffers before sending to isapi. 

So that was it.  Dialing that back appears to have solved the issue.

Andy

Re: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

[tomcat]

On 06.07.2016 21:43, Mekkelsen Madden, Steve wrote:

I've attached a screenshot showing the request if that helps.


Unfortunately, as you may notice, this list strips most attachments.
It would thus be better if you uploaded that screenshot somewhere, and provided 
a link to it.


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

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

[Mekkelsen Madden, Steve]

Thanks Felix. See below


-Original Message-
From: Felix Schumacher [mailto:felix.schumac...@internetallee.de] 
Sent: Wednesday, July 06, 2016 3:29 PM
To: users@tomcat.apache.org
Subject: Re: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

Am 06.07.2016 um 19:14 schrieb Mekkelsen Madden, Steve:
> This particular issue has raised a lot of issues in-house and we would 
> greatly appreciate a response from someone having more details on why NIO2 no 
> longer works.
>
> Thanks!
>
>
> -Original Message-
> From: Mekkelsen Madden, Steve
> Sent: Friday, July 01, 2016 12:56 PM
> To: Tomcat Users List 
> Subject: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding 
> issues
>
> Hi all,
>
> Is anyone aware of why after upgrading from Tomcat 8.0.32x64 (Windows) to 
> 8.5.3x64 using the connector protocol of: 
> protocol="org.apache.coyote.http11.Http11Nio2Protocol"  fails with url 
> encoding errors?  Once it was changed back to 
> protocol="org.apache.coyote.http11.Http11NioProtocol" all the errors stopped. 
>  This completely broke the application and made it unusable as the xml being 
> returned was not decoded and resulted in sax parse exceptions with our AJAX 
> connections.   I haven't found anything related to the protocol changing, 
> only the parameters for the SSL/TLS attributes which are in place and work.  
> It's almost like it's blocking the requests when it should be unblocking the 
> requests?  Thanks!!
Have you tried to compare the responses, that you get through the two 
connectors? Especially the characters before the xml prolog would be 
interesting.
Do you get the same errors, when you are requesting the url without tls?

Regards,
  Felix

Steve: We did not try turning off TLS in this case since this is what was 
already enabled in Production and required due to servers being accessible 
outside the network.  What the engineer found is that Fiddler showed all XML 
content (all the strings) that is being sent to and from the server were being 
encoded.  However, the XML content in fiddler does not have the encoded 
content.  I've attached a screenshot showing the request if that helps.

>
> Database Type: Oracle 12c Linux x64
> Driver used: ojdbc7.jar
> Connector attribute:  
>protocol="org.apache.coyote.http11.Http11NioProtocol"
>   maxThreads="150" disableUploadTimeout="true"
>   SSLEnabled="true"
>   sslDefaultHost="vgcspsteste1.rpega.com">
>
>certificateKeystoreFile="D:\certificates\ourcert.keystore" 
> certificateKeystorePassword="***" certificateKeyAlias="ourAlias" 
> type="RSA"/>
>
>   
> An example of the error looks like the below:
> 23 Jun 2016 01:28:39,731 [sl-nio2-8443-exec-11] 
> (ngineinterface.service.HttpAPI) ERROR: Error adopting XML from post data 
> com.pega.pegarules.pub.clipboard.InvalidStreamError: InvalidStream  
> com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(String, 
> StorageStream)   sax parse error: Content is not allowed in prolog.
> From: (H64E3757ED751A9AEE78817056219F4F9:10.224.243.66)
>   at 
> com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:477)
>   at 
> com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:432)
>   at 
> com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.adoptXMLForm(ClipboardPageImpl.java:818)
>   at 
> com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.mapInputData(HttpAPI.java:2481)
>   at 
> com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(EngineAPI.java:554)
>   at 
> com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:388)
>   at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1277)
>   at 
> com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1015)
>   at 
> com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:848)
>   at 
> com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:331)
>   at 
> com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:817)
>   at 
> com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:327)
>   at 
> com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:270)
>   at 
> 

Re: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

[Felix Schumacher]

Am 06.07.2016 um 19:14 schrieb Mekkelsen Madden, Steve:

This particular issue has raised a lot of issues in-house and we would greatly 
appreciate a response from someone having more details on why NIO2 no longer 
works.

Thanks!


-Original Message-
From: Mekkelsen Madden, Steve
Sent: Friday, July 01, 2016 12:56 PM
To: Tomcat Users List 
Subject: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

Hi all,

Is anyone aware of why after upgrading from Tomcat 8.0.32x64 (Windows) to 8.5.3x64 using the 
connector protocol of: protocol="org.apache.coyote.http11.Http11Nio2Protocol"  fails with 
url encoding errors?  Once it was changed back to 
protocol="org.apache.coyote.http11.Http11NioProtocol" all the errors stopped.  This 
completely broke the application and made it unusable as the xml being returned was not decoded and 
resulted in sax parse exceptions with our AJAX connections.   I haven't found anything related to 
the protocol changing, only the parameters for the SSL/TLS attributes which are in place and work.  
It's almost like it's blocking the requests when it should be unblocking the requests?  Thanks!!
Have you tried to compare the responses, that you get through the two 
connectors? Especially the characters before the xml prolog would be 
interesting.

Do you get the same errors, when you are requesting the url without tls?

Regards,
 Felix


Database Type: Oracle 12c Linux x64
Driver used: ojdbc7.jar
Connector attribute:

 

 

An example of the error looks like the below:
23 Jun 2016 01:28:39,731 [sl-nio2-8443-exec-11] 
(ngineinterface.service.HttpAPI) ERROR: Error adopting XML from post data 
com.pega.pegarules.pub.clipboard.InvalidStreamError: InvalidStream
com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(String, 
StorageStream)   sax parse error: Content is not allowed in prolog.
From: (H64E3757ED751A9AEE78817056219F4F9:10.224.243.66)
at 
com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:477)
at 
com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:432)
at 
com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.adoptXMLForm(ClipboardPageImpl.java:818)
at 
com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.mapInputData(HttpAPI.java:2481)
at 
com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(EngineAPI.java:554)
at 
com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:388)
at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1277)
at 
com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1015)
at 
com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:848)
at 
com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:331)
at 
com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:817)
at 
com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:327)
at 
com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:270)
at 
com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:247)
at 
com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:278)
at 
com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:223)
at 
com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:574)
at 
com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:374)
at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:338)
at 
com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:379)
at 
com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)
at 
com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:265)
at 

RE: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

[Mekkelsen Madden, Steve]

This particular issue has raised a lot of issues in-house and we would greatly 
appreciate a response from someone having more details on why NIO2 no longer 
works.

Thanks!


-Original Message-
From: Mekkelsen Madden, Steve 
Sent: Friday, July 01, 2016 12:56 PM
To: Tomcat Users List 
Subject: SSL/TLS 8.5.3 upgrade from 8.0.32 using NIO2 url encoding issues

Hi all,

Is anyone aware of why after upgrading from Tomcat 8.0.32x64 (Windows) to 
8.5.3x64 using the connector protocol of: 
protocol="org.apache.coyote.http11.Http11Nio2Protocol"  fails with url encoding 
errors?  Once it was changed back to 
protocol="org.apache.coyote.http11.Http11NioProtocol" all the errors stopped.  
This completely broke the application and made it unusable as the xml being 
returned was not decoded and resulted in sax parse exceptions with our AJAX 
connections.   I haven't found anything related to the protocol changing, only 
the parameters for the SSL/TLS attributes which are in place and work.  It's 
almost like it's blocking the requests when it should be unblocking the 
requests?  Thanks!!

Database Type: Oracle 12c Linux x64
Driver used: ojdbc7.jar
Connector attribute: 

 

 

An example of the error looks like the below:
23 Jun 2016 01:28:39,731 [sl-nio2-8443-exec-11] 
(ngineinterface.service.HttpAPI) ERROR: Error adopting XML from post data 
com.pega.pegarules.pub.clipboard.InvalidStreamError: InvalidStream
com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(String, 
StorageStream)   sax parse error: Content is not allowed in prolog.
From: (H64E3757ED751A9AEE78817056219F4F9:10.224.243.66) 
at 
com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:477)
at 
com.pega.pegarules.data.internal.clipboard.XMLStream.newStream(XMLStream.java:432)
at 
com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.adoptXMLForm(ClipboardPageImpl.java:818)
at 
com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.mapInputData(HttpAPI.java:2481)
at 
com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(EngineAPI.java:554)
at 
com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:388)
at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1277)
at 
com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1015)
at 
com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:848)
at 
com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:331)
at 
com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:817)
at 
com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:327)
at 
com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:270)
at 
com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:247)
at 
com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:278)
at 
com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:223)
at 
com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:574)
at 
com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:374)
at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:338)
at 
com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:379)
at 
com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)
at 
com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:265)
at 
com.pega.pegarules.internal.web.servlet.WebStandardBoot.doPost(WebStandardBoot.java:118)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at 

Re: Load Balancing Oracle Apex Application on Apache tomcat.

[chandra sekhar]

Thanks for the info Abhijit,

Let me go through these links and will get back to you if need any help.

On Wed, Jul 6, 2016 at 12:45 PM, Abhijit Das  wrote:

> start here — http://www.haproxy.org/#desc 
>
> And, then search on internet, lots and lots of examples configuring
> haproxy with tomcat as backend. you could SSL client offload (need TPROXY
> enabled), etc etc.
>
>
>
> On Jul 6, 2016, at 9:41 AM, chandra sekhar  wrote:
>
> Yes.we have an option to offload load balancing to a different server.Could
> you please explain more on haproxy if you can and please share me doc
> related to this and load balancing?
>
> On Wed, Jul 6, 2016 at 12:10 PM, Abhijit Das  wrote:
>
> > Do you have the option to offload load balancing to a different server?
> If
> > so, look at haproxy and/or nginx. haproxy would be more customizable. If
> > there are bandwidth constraints, implement a DSR VIP (IP triangulation).
> >
> >
> > On Jul 6, 2016, at 9:08 AM, chandra sekhar 
> wrote:
> >
> > Hi,
> >
> > We were using  apache-tomcat-7.0.55 for our Oracle Apex 4.2.5 Application
> > on Linux(Linux 2.6.32-573.22.1.el6.x86_64 x86_64 GNU/Linux).
> >
> > As we have around 300-500 users using this application,we would like to
> > know if we can load balance our Oracle Apex Application on 2 or 3
> frontend
> > servers to distribute the load.Hence,kindly help me how to configure load
> > balance on Apache tomcat.
> >
> > I'm open to tips and advices ;)
> >
> > Thanks,
> > Chandra
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
>
>

Re: Load Balancing Oracle Apex Application on Apache tomcat.

[Abhijit Das]

start here — http://www.haproxy.org/#desc 

And, then search on internet, lots and lots of examples configuring haproxy 
with tomcat as backend. you could SSL client offload (need TPROXY enabled), etc 
etc.



On Jul 6, 2016, at 9:41 AM, chandra sekhar  wrote:

Yes.we have an option to offload load balancing to a different server.Could
you please explain more on haproxy if you can and please share me doc
related to this and load balancing?

On Wed, Jul 6, 2016 at 12:10 PM, Abhijit Das  wrote:

> Do you have the option to offload load balancing to a different server? If
> so, look at haproxy and/or nginx. haproxy would be more customizable. If
> there are bandwidth constraints, implement a DSR VIP (IP triangulation).
> 
> 
> On Jul 6, 2016, at 9:08 AM, chandra sekhar  wrote:
> 
> Hi,
> 
> We were using  apache-tomcat-7.0.55 for our Oracle Apex 4.2.5 Application
> on Linux(Linux 2.6.32-573.22.1.el6.x86_64 x86_64 GNU/Linux).
> 
> As we have around 300-500 users using this application,we would like to
> know if we can load balance our Oracle Apex Application on 2 or 3 frontend
> servers to distribute the load.Hence,kindly help me how to configure load
> balance on Apache tomcat.
> 
> I'm open to tips and advices ;)
> 
> Thanks,
> Chandra
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 

Re: Load Balancing Oracle Apex Application on Apache tomcat.

[chandra sekhar]

Yes.we have an option to offload load balancing to a different server.Could
you please explain more on haproxy if you can and please share me doc
related to this and load balancing?

On Wed, Jul 6, 2016 at 12:10 PM, Abhijit Das  wrote:

> Do you have the option to offload load balancing to a different server? If
> so, look at haproxy and/or nginx. haproxy would be more customizable. If
> there are bandwidth constraints, implement a DSR VIP (IP triangulation).
>
>
> On Jul 6, 2016, at 9:08 AM, chandra sekhar  wrote:
>
> Hi,
>
> We were using  apache-tomcat-7.0.55 for our Oracle Apex 4.2.5 Application
> on Linux(Linux 2.6.32-573.22.1.el6.x86_64 x86_64 GNU/Linux).
>
> As we have around 300-500 users using this application,we would like to
> know if we can load balance our Oracle Apex Application on 2 or 3 frontend
> servers to distribute the load.Hence,kindly help me how to configure load
> balance on Apache tomcat.
>
> I'm open to tips and advices ;)
>
> Thanks,
> Chandra
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Upgrading Tomcat 8.0.23 to Tomcat 8.50

[Philip Hachey]

I would do a fresh install to a new directory and change what you need 
to to match your previous configuration, taking into account changes 
between Tomcat versions (see: http://tomcat.apache.org/migration.html).  
You will need to update system environment variables such as 
$CATALINA_HOME and/or symbolic links.  Of course, it should go without 
saying: backup everything! :-)


Good luck!
Philip

On 16-07-06 10:28 AM, Venkataramani, Sundar wrote:

Help Required.

We need to upgrade our tomcat version from Tomcat 8.0.23  to Tomcat 8.50?. Do 
we need an upgrade path for these or do we need to do fresh install?.

Thanks
Sundar.V






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

Re: Load Balancing Oracle Apex Application on Apache tomcat.

[Abhijit Das]

Do you have the option to offload load balancing to a different server? If so, 
look at haproxy and/or nginx. haproxy would be more customizable. If there are 
bandwidth constraints, implement a DSR VIP (IP triangulation). 


On Jul 6, 2016, at 9:08 AM, chandra sekhar  wrote:

Hi,

We were using  apache-tomcat-7.0.55 for our Oracle Apex 4.2.5 Application
on Linux(Linux 2.6.32-573.22.1.el6.x86_64 x86_64 GNU/Linux).

As we have around 300-500 users using this application,we would like to
know if we can load balance our Oracle Apex Application on 2 or 3 frontend
servers to distribute the load.Hence,kindly help me how to configure load
balance on Apache tomcat.

I'm open to tips and advices ;)

Thanks,
Chandra


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

Re: Suggestions for deploying context.xml for different environments?

[Philip Hachey]

Thank you for the reply, Christoph.

On 16-07-05 03:32 AM, Christoph Nenning wrote:

Hello.  I am seeking some advice for the best ways to deploy Java web
applications to different Tomcat environments.

In particular, my application requires that a JNDI resource be defined
for a database, where the database server address and credentials will
vary depending on the environment the application is deployed to.

* Tomcat: 8.0.36
* OS: varies depending on the environment deployed to

If I include in the WAR file, a META-INF/context.xml that includes the
Resource element, Tomcat will use that to create the file:
$CATALINA_HOME/conf/engine/host/my-application.xml

The context file my-application.xml can then be modified so that the
Resource settings are appropriate for the environment.

However, if, for any reason, the application is undeployed and then
re-deployed, my-application.xml will be recreated with the settings as
they originally appeared in the WAR file.

The options that seem evident to me are:

1) Create a different WAR file for each environment.  This strikes me as
a bit onerous.

2) Use environment variables in my-application.xml such as:
url="${databaseurl}" and then define those environment variables using
the Environment element in the GlobalNamingResources of Tomcat's

server.xml.

Regarding #2, would it be possible to instead use a properties file to
define the variables?  I assume adding entries to catalina.properties
would work, but is it possible to define a properties file separate from
catalina.properties which deals more with system properties rather than
application properties?


We set such system properties in setenv.sh, e.g.:

JAVA_OPTS="$JAVA_OPTS -Ddatabase.password=$DATABASE_PASSWORD"


The environment variable $DATABASE_PASSWORD is used because we wrap our
applications along with tomcat and jvm in docker images. Operations
specify environment specific parameters (as database passwords) when they
launch the docker container with -e switch, e.g.:

docker run -d -e DATABASE_PASSWORD=secret .


Due to docker we don't need context.xml files inside WARs. Instead we have
application specific tomcat config files in our source trees. Our build
process includes them in the docker image as top level tomcat config. As
we build application specific images there is just one app per image and
thus per tomcat instance.


Of course that is linux only.


I don't believe docker is an option for me.  At least, not at this 
time.  I do like the idea of setting environment-specific variables as 
system properties in the setenv.sh.  However, setting passwords there 
gives me pause for security reasons since it would be visible to 
anything running within the Tomcat environment, should there be some way 
to exploit a vulnerability and access Tomcat's system properties or 
environment variables remotely.


Thank you for sharing,
Philip




regards,
Christoph




I haven't been able to find a documented standard methodology for Tomcat
deployments to different environments, but I'm certain there must be
some common and elegant ways of doing this.  I'm interested in hearing
what others have done.

Thank you,
Philip

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







This Email was scanned by Sophos Anti Virus




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

Load Balancing Oracle Apex Application on Apache tomcat.

[chandra sekhar]

Hi,

We were using  apache-tomcat-7.0.55 for our Oracle Apex 4.2.5 Application
on Linux(Linux 2.6.32-573.22.1.el6.x86_64 x86_64 GNU/Linux).

As we have around 300-500 users using this application,we would like to
know if we can load balance our Oracle Apex Application on 2 or 3 frontend
servers to distribute the load.Hence,kindly help me how to configure load
balance on Apache tomcat.

I'm open to tips and advices ;)

Thanks,
Chandra

Upgrading Tomcat 8.0.23 to Tomcat 8.50

[Venkataramani, Sundar]

Help Required.

We need to upgrade our tomcat version from Tomcat 8.0.23  to Tomcat 8.50?. Do 
we need an upgrade path for these or do we need to do fresh install?.

Thanks
Sundar.V

Re: Need help setting up SSL on Tomcat 8

[Ognjen Blagojevic]

Sean,

On 5.7.2016 17:14, Sean Son wrote:

Hello Daniel and all

Here is the output.. the full output

http://pastebin.com/AQckw6ig


Keytool output indicates that there are two entries in keystore:

1. Entry with alias "root", created Jun 16, 2016, which is intermediate 
certificate for Go Daddy:


Owner: CN=Go Daddy Secure Certificate Authority - G2 ...
Issuer: CN=Go Daddy Root Certificate Authority - G2 ...

This is "trustedCertEntry", which means that it does not contain a 
private key, and therefore may not be used for encryption necessary for 
TLS / HTTPS communication.



2. Entry with alias "{b81d8607-57e9-4c35-a058-cd46099e7797}", created 
Jun 16, 2016. This is certificate for domain example.com, signed by Go 
Daddy:


Owner: CN=*.example.com, OU=Domain Control Validated
Issuer: CN=Go Daddy Secure Certificate Authority - G2, ...

This is PrivateKeyEntry which means that it contains private and public 
key pair, and since owner is different from issuer it means it also 
contains associated certificate. This entry may be used to encrypt data 
for TLS / HTTPS communication.



Therefore, you must point Tomcat to use second entry from your keystore. 
Try adding keyAlias="{b81d8607-57e9-4c35-a058-cd46099e7797}" to your 
connector configuration.


-Ognjen



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