Re: Migration JDK11 - Tomcat 9 - NoClassDefFoundError: java/sql/Statement

[Rob Sargent]

On 3/29/22 10:54, Senguttuvan, Gopalakrishnan (CWM-NR) wrote:

Hi Thomas,

Thanks for the response.
This issue occurred when I have start the Tomcat server in Linux-QA machine.


Regards,
Gopalakrishnan S


Double check your runtime environment - something there is out of whack 
I suspect.


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

RE: Migration JDK11 - Tomcat 9 - NoClassDefFoundError: java/sql/Statement

[Senguttuvan, Gopalakrishnan (CWM-NR)]

Hi Thomas,

Thanks for the response.
This issue occurred when I have start the Tomcat server in Linux-QA machine.


Regards,
Gopalakrishnan S

-Original Message-


From: Thomas Hoffmann (Speed4Trade GmbH) 
[mailto:thomas.hoffm...@speed4trade.com.INVALID] 
Sent: March 26, 22 1:39 AM
To: Tomcat Users List 
Subject: AW: Migration JDK11 - Tomcat 9 - NoClassDefFoundError: 
java/sql/Statement

[External]

Hello,
does this error show up in IntelliJ ?
Seems like there is a bug in IntelliJ:
https://stackoverflow.com/questions/52981800/getting-noclassfoundexception-java-sql-sqlexception-in-intellij-idea-for-jdk-1

java.sql.statement is shipped with Java 11.

Greetings,
Thomsa

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

> -Ursprüngliche Nachricht-
> Von: Senguttuvan, Gopalakrishnan (CWM-NR) 
> 
> Gesendet: Freitag, 25. März 2022 17:13
> An: users@tomcat.apache.org
> Betreff: Migration JDK11 - Tomcat 9 - NoClassDefFoundError:
> java/sql/Statement
>
> Hi Team,
>
> We are migrating our application from JDK8 to JDK11 (RedHat OpenJDK11).
> Modified the JAVA_HOME to JDK11 path.
> Currently we are using Tomcat version 9. (It is working fine with JDK8).
> Since the JDK11 won't support the JAVA_ENDORSED_DIRS, so I have 
> removed the "-Djava.endorsed.dirs" in catalina.sh.
>
> Once removed endorsed entry, got the below exception while start the
> application:
> java.lang.NoClassDefFoundError: java/sql/Statement
> at
> java.xml/com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.close(U
> TF
> 8Reader.java)
> at
> java.xml/com.sun.org.apache.xerces.internal.impl.XMLEntityManager.clos
> eR
> eaders(XMLEntityManager.java:1452)
> at
> java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration
> .cl
> eanup(XML11Configuration.java:803)
> at
> java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration
> .p
> arse(XML11Configuration.java:844)
> at
> java.xml/com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XM
> L
> Parser.java:141)
> at
> java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.
> par
> se(AbstractSAXParser.java:1216)
> at
> java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAX
> P
> arser.parse(SAXParserImpl.java:635)
> at 
> org.apache.tomcat.util.digester.Digester.parse(Digester.java:1517)
> at
> org.apache.catalina.startup.Catalina.parseServerXml(Catalina.java:584)
> at 
> org.apache.catalina.startup.Catalina.load(Catalina.java:675)
> at 
> org.apache.catalina.startup.Catalina.load(Catalina.java:712)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeM
> et
> hodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Del
> ega
> tingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at 
> org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:302)
> at
> org.apache.catalina.startup.Bootstrap.mainStatement(Bootstrap.java:472
> ) Exception in thread "Thread-0" java.lang.NoClassDefFoundError:
> java/sql/Statement
> at java.base/java.io.PrintWriter.close(PrintWriter.java)
> at 
> org.apache.juli.FileHandler.closeWriter(FileHandler.java:339)
> at org.apache.juli.FileHandler.close(FileHandler.java:327)
> at
> org.apache.juli.ClassLoaderLogManager.resetLoggers(ClassLoaderLogManag
> er.java:397)
> at
> org.apache.juli.ClassLoaderLogManager.shutdown(ClassLoaderLogManager.j
> ava:376)
> at
> org.apache.juli.ClassLoaderLogManager$Cleaner.run(ClassLoaderLogManage
> r.java:80)
>
>
> Kindly help us to resolve this issue and let me know if you need any 
> further details.
>
>
>
>
> Regards,
> Gopalakrishnan S
>

__ This 
email is intended only for the use of the individual(s) to whom it is addressed 
and may be privileged and confidential. Unauthorised use or disclosure is 
prohibited. If you receive this e-mail in error, please advise immediately and 
delete the original message. This message may have been altered without your or 
our knowledge and the sender does not accept any liability for any errors or 
omissions in the message. Emails are monitored by supervisory personnel in 
jurisdictions where monitoring is permitted. Such communications are retained 
and may be produced to regulatory authorities 

Re: Migration from Tomcat 7 to 9 results in more open file descriptors

[Mark Thomas]

On 03/06/2019 22:46, Mark Thomas wrote:
>> Florian,
>>
>>> On 5/23/19 06:59, Florian Trimmel wrote: We were able to figure out
>>> what was causing the file descriptor leak.
>>
>>> The leak has occured in the JSF2 MyFaces Implementation we are
>>> using. It is described here:
>>> https://marc.info/?l=myfaces-dev=152536956716792=2 The problem
>>> was found using this tool: http://file-leak-detector.kohsuke.org/
>>
>> Yup, that'll do it.
>>
>> Thanks for coming back to report your results.
> 
> +1.
> 
> This got me thinking. We should add a debugging section to the Wiki and
> include this tool.

Done:
https://cwiki.apache.org/confluence/display/TOMCAT/Debugging

Additional content welcome.

Mark

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

Re: Migration from Tomcat 7 to 9 results in more open file descriptors

[Mark Thomas]

> Florian,
> 
>> On 5/23/19 06:59, Florian Trimmel wrote: We were able to figure out
>> what was causing the file descriptor leak.
> 
>> The leak has occured in the JSF2 MyFaces Implementation we are
>> using. It is described here:
>> https://marc.info/?l=myfaces-dev=152536956716792=2 The problem
>> was found using this tool: http://file-leak-detector.kohsuke.org/
> 
> Yup, that'll do it.
> 
> Thanks for coming back to report your results.

+1.

This got me thinking. We should add a debugging section to the Wiki and
include this tool.

Mark

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

Re: Migration from Tomcat 7 to 9 results in more open file descriptors

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Florian,

> On 5/23/19 06:59, Florian Trimmel wrote: We were able to figure out
> what was causing the file descriptor leak.
> 
> The leak has occured in the JSF2 MyFaces Implementation we are
> using. It is described here:
> https://marc.info/?l=myfaces-dev=152536956716792=2 The problem
> was found using this tool: http://file-leak-detector.kohsuke.org/

Yup, that'll do it.

Thanks for coming back to report your results.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlz1kpIACgkQHPApP6U8
pFifABAAj3rtiX284coPU1v6lxIA+Xyh7+YBdboS4bOjXBDL3zszIPO8Emwja5Q6
N5zdu1HL48uL/PaYbb4WdhErne7H9116wVM3VJRGEbYDN2QFXm/EawnBQqhET1A6
zk+IFUDpzQYoQUu9ZOjJZlCrlShxzn45YrD9W8AU1lhBCxxDJqKoNQ8hL0kXQNTX
xKZ4ex5xd+nawzap1In7KpsTewAC/X46N6Q4FPbb8N8tArLXdL9ZDg/sBPdQ/JnZ
cIt+L5lorw2OqmTmawXWOK+JN09vY6yaCbZrzt4+PlkVdgP179znkxBc0DLS5/+z
2W/SpGhnuB4LePiu7ISRajYchfwsk338jxXKuUqhFtD+r4BwODWWFdGsdo0GyVk2
dLx7VWIAieJzZng+CyTiayJKYmw6SxslKzEfNFFR5gfqwitKfFUUjtTbB4cLATWR
vrgCyQJGevNMnMYmHPpeiZKBsxfe4psJY5seZ2X9zjb0Y+jKSpGnbheBJ17sah0W
HJvXs8QdR4PEDn6pumpSyFr6k5j6uw6/W++rLRhZVCZcFBDdZFuvjb/qgKS4C8/n
7tqBn1E4iWiTqTaIIfd8H6s5dti8eDFMOqx1wxKREb8fFA1bGJsLEW4zBH25iBCK
g6jiywtDaDXkjLIUrvpiuxBmWEJ0pCGDcv8daHx5mZuWgiFe0JY=
=DN0D
-END PGP SIGNATURE-

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

Re: Migration from Tomcat 7 to 9 results in more open file descriptors

[Florian Trimmel]

Am Do., 23. Mai 2019 um 17:14 Uhr schrieb Christopher Schultz <
ch...@christopherschultz.net>:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Florian,
>
> On 5/23/19 06:59, Florian Trimmel wrote:
> > After migrating from Tomact 7 to Tomcat 9.0.20 (running with same
> > Java Version 1.8.0_25) we have a problem with our JSF2 web
> > application on Linux RHEL 7. After some time we get Exceptions like
> > this:
> >
> >
> >
> > java.io.FileNotFoundException:
> > /f4m/tomcat/tomcat_f4mbs/webapps/ACM/WEB-INF/acm-config.xml (Too
> > many open files)
> >
> > at java.io.FileInputStream.open0(Native Method)
> >
> > at java.io.FileInputStream.open(FileInputStream.java:195)
> >
> > at java.io.FileInputStream.(FileInputStream.java:138)
> >
> > at java.io.FileInputStream.(FileInputStream.java:93)
> >
> >
> >
> >
> >
> > After searching around a while, I have found out that there are
> > many open file descriptors to xhtml files
>
> Do you know if your application opens these files, or are they
> (likely) being opened by Tomcat in response to incoming client
> requests for those files?
>
> > [snip]
> >
> > This is not the complete list - there are many more.
> >
> > The number of listed files goes up and down. For me it seems that
> > xhtml (or one of its used components) has an open file descriptor
> > as long as a page is shown in Browser.
>
> ... and when you close the browser, the fd is closed too? Spooky.
>
> > I already know how to increase the maximum number of open file
> > descriptors, what bothers me is that if I deploy the same
> > application on Tomcat 7 again, I can only see open file descriptors
> > for JAR Files, Sockets, but NEVER for xhtml's.
> >
> > Can someone please explain why this happens?
>
> The obvious explanation would be a fd leak within Tomcat but I see no
> data to support that. The "resources" (aka file-reading)
> implementation changed between Tomcat 7 and 9 and if your application
> is being a little lazy about resource-management, this could cause fds
> to be left open now where they were being cleaned-up for you in the past
> .
>
> Improper caching configuration could also leave file descriptors open,
> but multiple fds open to the same file is the exact opposite of
> caching, so the configuration would have to indeed be particularly bad.
>
> Are you able to attach a profiler to the JVM process? If so, try
> launching Tomcat, attaching the profiler, and then making some
> requests. The profiler ought to be able to show you where certain
> objects were allocated and you can track-down where e.g.
> FileInputStream objects are created. If they are being created in
> Tomcat's code without being called from your application (e.g. from
> within DefaultServlet), then something is very wrong.
>
> But at this point, the new resources implementation is fairly mature
> and I wouldn't expect it to leak like this.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlzmuOUACgkQHPApP6U8
> pFgqwg/9FUmsAS/mOin0NKIlU1LOPRyf72/gT+8n5vyquC+CBk8jWFBqxNFZEoGV
> Fc+5rfwF1pqK8aTgDM2dzEb4bJ9s3sVGY/SLvspGyeRU81/uqZW4CnSGIL7VzrJk
> xpTi4hk02rNFbq8yNjMDqCUx2t41Bi8NUVJh9TUtHRPZRQWhy3JsG32HQdPrPklj
> AipBl/NkpizGZQlAGqMz87rYvFIEz1e1hA47CPfUFg7x8WCib7X9JcHHZYF5gQjS
> y/h5IdRT9A6F1Lu2arW00cFPSfoYoZA+gHWzQMGHmTXSQplwzF8h9tafNLXf4u4u
> Knav+K3KTPeskzuKUqxLTa2GwX6MNLnEnw3uicvuHT13JYncLTz6LCgSE31/xgj9
> EcnME4zQca7X14DrHaldwwejuvqL/HYTVkYc6YOt24E3FCAbkcPg8MOYo1QjT408
> u1GXl+n4HBgNsHO//FsAVYDEm14YXmvWyB+33aVc9OKbCk1X+vRbkq8Fe//Bz05T
> 72Mb5potJWGFhHVseSuiYp1XyhlgSWDqzQkqoYV8ffm5ecfbYd96gRqFxveK0S2I
> 9/9X6k8a/6lqQMidfNoqKfoA1G+5soI436j6LYlna4vqIgB+ZjCoTmnzJh4+NMy7
> VcAZ+S2uRb3bnTccsttcNbCKOM9BD9C9rSosS3N48XDl3u5ooL4=
> =B0WJ
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Christopher,
Thank you for your quick reply
We were able to figure out what was causing the file descriptor leak.

The leak has occured in the JSF2 MyFaces Implementation we are using.
It is described here: https://marc.info/?l=myfaces-dev=152536956716792=2
The problem was found using this tool:
http://file-leak-detector.kohsuke.org/


Thanks,
Florian

Re: Migration from Tomcat 7 to 9 results in more open file descriptors

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Florian,

On 5/23/19 06:59, Florian Trimmel wrote:
> After migrating from Tomact 7 to Tomcat 9.0.20 (running with same
> Java Version 1.8.0_25) we have a problem with our JSF2 web
> application on Linux RHEL 7. After some time we get Exceptions like
> this:
> 
> 
> 
> java.io.FileNotFoundException: 
> /f4m/tomcat/tomcat_f4mbs/webapps/ACM/WEB-INF/acm-config.xml (Too
> many open files)
> 
> at java.io.FileInputStream.open0(Native Method)
> 
> at java.io.FileInputStream.open(FileInputStream.java:195)
> 
> at java.io.FileInputStream.(FileInputStream.java:138)
> 
> at java.io.FileInputStream.(FileInputStream.java:93)
> 
> 
> 
> 
> 
> After searching around a while, I have found out that there are
> many open file descriptors to xhtml files

Do you know if your application opens these files, or are they
(likely) being opened by Tomcat in response to incoming client
requests for those files?

> [snip]
> 
> This is not the complete list - there are many more.
> 
> The number of listed files goes up and down. For me it seems that
> xhtml (or one of its used components) has an open file descriptor
> as long as a page is shown in Browser.

... and when you close the browser, the fd is closed too? Spooky.

> I already know how to increase the maximum number of open file
> descriptors, what bothers me is that if I deploy the same
> application on Tomcat 7 again, I can only see open file descriptors
> for JAR Files, Sockets, but NEVER for xhtml's.
> 
> Can someone please explain why this happens?

The obvious explanation would be a fd leak within Tomcat but I see no
data to support that. The "resources" (aka file-reading)
implementation changed between Tomcat 7 and 9 and if your application
is being a little lazy about resource-management, this could cause fds
to be left open now where they were being cleaned-up for you in the past
.

Improper caching configuration could also leave file descriptors open,
but multiple fds open to the same file is the exact opposite of
caching, so the configuration would have to indeed be particularly bad.

Are you able to attach a profiler to the JVM process? If so, try
launching Tomcat, attaching the profiler, and then making some
requests. The profiler ought to be able to show you where certain
objects were allocated and you can track-down where e.g.
FileInputStream objects are created. If they are being created in
Tomcat's code without being called from your application (e.g. from
within DefaultServlet), then something is very wrong.

But at this point, the new resources implementation is fairly mature
and I wouldn't expect it to leak like this.

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlzmuOUACgkQHPApP6U8
pFgqwg/9FUmsAS/mOin0NKIlU1LOPRyf72/gT+8n5vyquC+CBk8jWFBqxNFZEoGV
Fc+5rfwF1pqK8aTgDM2dzEb4bJ9s3sVGY/SLvspGyeRU81/uqZW4CnSGIL7VzrJk
xpTi4hk02rNFbq8yNjMDqCUx2t41Bi8NUVJh9TUtHRPZRQWhy3JsG32HQdPrPklj
AipBl/NkpizGZQlAGqMz87rYvFIEz1e1hA47CPfUFg7x8WCib7X9JcHHZYF5gQjS
y/h5IdRT9A6F1Lu2arW00cFPSfoYoZA+gHWzQMGHmTXSQplwzF8h9tafNLXf4u4u
Knav+K3KTPeskzuKUqxLTa2GwX6MNLnEnw3uicvuHT13JYncLTz6LCgSE31/xgj9
EcnME4zQca7X14DrHaldwwejuvqL/HYTVkYc6YOt24E3FCAbkcPg8MOYo1QjT408
u1GXl+n4HBgNsHO//FsAVYDEm14YXmvWyB+33aVc9OKbCk1X+vRbkq8Fe//Bz05T
72Mb5potJWGFhHVseSuiYp1XyhlgSWDqzQkqoYV8ffm5ecfbYd96gRqFxveK0S2I
9/9X6k8a/6lqQMidfNoqKfoA1G+5soI436j6LYlna4vqIgB+ZjCoTmnzJh4+NMy7
VcAZ+S2uRb3bnTccsttcNbCKOM9BD9C9rSosS3N48XDl3u5ooL4=
=B0WJ
-END PGP SIGNATURE-

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

Re: migration from tomcat 7.0 to 8.5

[Mark Thomas]

On 04/10/2017 15:53, Aquatic Safaris Diver wrote:
> 
> I've read the migration manuals and have tried to make the changes to
> my configuration to work correctly in tomcat v8.5, but it's not.  I'm
> not an experton XML files and JDK so please help me.   I'm sure this is crazy 
> simple
> for you experts.

Why make life difficult for yourself? Just package those libraries in
your web application's WEB-INF/lib directory.

Mark

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

RE: Migration tomcat 7 to 9 : export static files

[andre seame]

My  server.xml is the delivered server.xml file + my declaration of testresult
===




  
  
  
  
  
  
  
  
  

  
  


  

  
  





















  
  

  
  


  

  










  

  


===
thanks
PHL.


De : Christopher Schultz 
Envoyé : jeudi 3 janvier 2019 14:52
À : users@tomcat.apache.org
Objet : Re: Migration tomcat 7 to 9 : export static files

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

André,

On 1/3/19 03:56, andre seame wrote:
> Hello,
>
> In tomcat 7, I have a server.xml config file. In the host section I
> have
>
> 
>
> So, I can access to static file :
> http://server:8080/testresults/myfile.png, where the file is stored
> in d:\TESTRESULTS\myfile.png
>
> When using the HTML gui management interface
> -http://server:8080/manager/html), I see the list of applications
> that are running on my tomcat server. There is my application and a
> "testresult" application.
>
> In tomcat 9, I try the same configuration, but I get an error 404
> when I try to access to http://server:8080/testresults/myfile.png
>
> The
> http://server-tomat-9:8080/manager/html<http://server:8080/manager/htm
l>
> gives only y application (no more /testresults).
>
> My bug ? Tomcat 9 bug ? Insuffisant configuration or new security
> mechanism for tomcat 9.

What does your Tomcat 9 conf/server.xml file look like?

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwuIZwACgkQHPApP6U8
pFhlXg//boCo965yTmAs+HVb925dSHemgVaWqNHsO0P6sfX58F6oxoNwcs6ZI2h7
GAgXEeSXUVwSwisRGjcRuLcxRf/o2nm+oU6p2OlK7WE+t9xulYsN7YUhVq09Mba9
bUNpY7wK2gk853B3ih4GtmVLOq3qJu+w1aanasoSJUAEC9SY6xg18qZgFc64oAgr
Sz4ij0gfQv3uvb+3mbSTe0LSBA0yApHMTQ8ETo9fXf7Z352FwUAeWM2Lx6WVDlvG
vCXLCDFRmkRvWzE6K5dOlQMMdbuFIs92peoFr/MPztdVYiiZIvR5Zl0xLZEPP/va
of+Va/JKgkJy1JZ0dt0VaqTPP8LgoauprvnyyhhzQYUz/LLmDGq6PGGmoihddKQ0
3Kkv3c+ug0Et+28Ef+aRLk8AJH7Joy16xNOutZbZY2+Nskc67X9Lc3OmSy2R0CEs
tSjo+ZflCAfXBUF2N8LdmtqMdI2XCpOijlTqkl00f3z/5keW0nwLfo7QUVyagDM4
ONg2cj4RbQgLqIgLTEQnIdm6TzWDOad+yOXBPM/8WAS+Qvo4p3aIgOzHBOL/JX89
+3bqMzNWTHGQpEELFtAsaGKQoW/ne1zSiK+uT+S7NR33KJnEBihgQC6LChvqrt5X
uk6b9KGHbphGVVNhWOCfctmI5nSsENXqgrHphoYKjtiu1fCOxVw=
=TDXs
-END PGP SIGNATURE-

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

Re: Migration tomcat 7 to 9 : export static files

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

André,

On 1/3/19 03:56, andre seame wrote:
> Hello,
> 
> In tomcat 7, I have a server.xml config file. In the host section I
> have
> 
> 
> 
> So, I can access to static file :
> http://server:8080/testresults/myfile.png, where the file is stored
> in d:\TESTRESULTS\myfile.png
> 
> When using the HTML gui management interface
> -http://server:8080/manager/html), I see the list of applications
> that are running on my tomcat server. There is my application and a
> "testresult" application.
> 
> In tomcat 9, I try the same configuration, but I get an error 404
> when I try to access to http://server:8080/testresults/myfile.png
> 
> The
> http://server-tomat-9:8080/manager/html
> gives only y application (no more /testresults).
> 
> My bug ? Tomcat 9 bug ? Insuffisant configuration or new security
> mechanism for tomcat 9.

What does your Tomcat 9 conf/server.xml file look like?

- -chris
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwuIZwACgkQHPApP6U8
pFhlXg//boCo965yTmAs+HVb925dSHemgVaWqNHsO0P6sfX58F6oxoNwcs6ZI2h7
GAgXEeSXUVwSwisRGjcRuLcxRf/o2nm+oU6p2OlK7WE+t9xulYsN7YUhVq09Mba9
bUNpY7wK2gk853B3ih4GtmVLOq3qJu+w1aanasoSJUAEC9SY6xg18qZgFc64oAgr
Sz4ij0gfQv3uvb+3mbSTe0LSBA0yApHMTQ8ETo9fXf7Z352FwUAeWM2Lx6WVDlvG
vCXLCDFRmkRvWzE6K5dOlQMMdbuFIs92peoFr/MPztdVYiiZIvR5Zl0xLZEPP/va
of+Va/JKgkJy1JZ0dt0VaqTPP8LgoauprvnyyhhzQYUz/LLmDGq6PGGmoihddKQ0
3Kkv3c+ug0Et+28Ef+aRLk8AJH7Joy16xNOutZbZY2+Nskc67X9Lc3OmSy2R0CEs
tSjo+ZflCAfXBUF2N8LdmtqMdI2XCpOijlTqkl00f3z/5keW0nwLfo7QUVyagDM4
ONg2cj4RbQgLqIgLTEQnIdm6TzWDOad+yOXBPM/8WAS+Qvo4p3aIgOzHBOL/JX89
+3bqMzNWTHGQpEELFtAsaGKQoW/ne1zSiK+uT+S7NR33KJnEBihgQC6LChvqrt5X
uk6b9KGHbphGVVNhWOCfctmI5nSsENXqgrHphoYKjtiu1fCOxVw=
=TDXs
-END PGP SIGNATURE-

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

AW: [EXTERNAL] Re: Migration from Tomcat 8.0.37 to 8.5.24 , changes to protocol at Http11NioProtocol , from http-nio to https-jsse-nio

[Lauria Giuseppe]

Hi Marek, Hi Mark.
Thank you very much.

Best regards
G

-Ursprüngliche Nachricht-
Von: Mark Thomas [mailto:ma...@apache.org] 
Gesendet: Mittwoch, 7. Februar 2018 09:51
An: Tomcat Users List <users@tomcat.apache.org>
Betreff: [EXTERNAL] Re: Migration from Tomcat 8.0.37 to 8.5.24 , changes to 
protocol at Http11NioProtocol , from http-nio to https-jsse-nio

On 07/02/18 08:41, Lauria Giuseppe wrote:
> Hi tomcat users.
> 
> 
> We are in transition from Tomcat 8.0.37 to 8.5.24.



> What is the meaning of this ? Is this just naming change ?
> Or did functionality change ? If yes, what is different between http-nio and 
> https-jsse-nio ?

8.0.x only supports JSSE for TLS with NIO (and NIO2) HTTP connectors.

8.5.x supports JSSE or OpenSSL for TLS with NIO (and NIO2) HTTP connectors.

Therefore, the protocol name in 8.5.x was extended to indicate which TLS 
implementation is in use.

http-nio in 8.0.x is equivalent to http-jsse-nio in 8.5.x.

Mark

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

Re: Migration from Tomcat 8.0.37 to 8.5.24 , changes to protocol at Http11NioProtocol , from http-nio to https-jsse-nio

[Marek Czernek]

Hi Lauria,

This seems like everything is the same for you on both Tomcat 8 and 8.5; 
what changed is that the SSL implementation gets displayed in the console.


JSSE means you're using Java runtime JSSE implementation. There's the 
possibility to use OpenSSL implementation as well. See the docs [1 
] 
for further details on the SSL implementation with regards to your 
connector settings.


Someone please do correct me if I'm wrong, but the bottom line seems to 
be that nothing functional has changed in this case.


HTH!

[1] 
https://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Edit_the_Tomcat_Configuration_File


On 02/07/2018 09:41 AM, Lauria Giuseppe wrote:

Hi tomcat users.


We are in transition from Tomcat 8.0.37 to 8.5.24.

We checked Tomcat docs and FAQ and searched in google for this topic but did 
not find an explanation.

Question:

Even we did not change server.xml for the connector , now the 'protocol' in the 
log changed to different value; from 'http-nio' to 'https-jsse-nio'.

Definition im server.xml :


--

Marek Czernek

Associate Quality Engineer

Re: Migration from Tomcat 8.0.37 to 8.5.24 , changes to protocol at Http11NioProtocol , from http-nio to https-jsse-nio

[Mark Thomas]

On 07/02/18 08:41, Lauria Giuseppe wrote:
> Hi tomcat users.
> 
> 
> We are in transition from Tomcat 8.0.37 to 8.5.24.



> What is the meaning of this ? Is this just naming change ?
> Or did functionality change ? If yes, what is different between http-nio and 
> https-jsse-nio ?

8.0.x only supports JSSE for TLS with NIO (and NIO2) HTTP connectors.

8.5.x supports JSSE or OpenSSL for TLS with NIO (and NIO2) HTTP connectors.

Therefore, the protocol name in 8.5.x was extended to indicate which TLS
implementation is in use.

http-nio in 8.0.x is equivalent to http-jsse-nio in 8.5.x.

Mark

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

Re: migration from tomcat 7.0 to 8.5

[Konstantin Kolinko]

2017-10-04 17:53 GMT+03:00 Aquatic Safaris Diver :
>
> I've read the migration manuals and have tried to make the changes to
> my configuration to work correctly in tomcat v8.5, but it's not.  I'm
> not an experton XML files and JDK so please help me.   I'm sure this is crazy 
> simple
> for you experts.
>
> The server.xml conf file is OK between the two versions.   But my
> application's deployment is having problems.
>
> In my tomcat v7 conf/Catalina/localhost directory, I have ed.xml file
> for my application containing:
>
> 
> 

"path" cannot be used here, ignored

docBase is rare to be seen here, but OK (it is outside of webapps)

> 
> 
> 
> virtualClasspath="/usr/local/calendar/libs/google-api-client-1.22.0.jar;/usr/local/calendar/google-api-services-calendar-v3-rev230-1.22.0.jar;/usr/local/calendar/libs/google-http-client-1.22.0.jar;/usr/local/calendar/libs/google-http-client-jackson2-1.22.0.jar;/usr/local/calendar/libs/google-oauth-client-1.22.0.jar;/usr/local/calendar/libs/jackson-core-2.1.3.jar"/>
> 
>
> After spending about 6 hours and reading tons of other web posts from
> others trying to do the same thing, I finally have
> something working, kinda.  My web application at least deploys when
> tomcat starts.  The Loader part in the .xml was replaced with:
> 
>  className="org.apache.catalina.webresources.JarResourceSet"
>base="/usr/local/calendar/libs/google-api-client-1.22.0.jar" 
> webAppMount="/WEB-INF/lib" internalPath="/."/>
>  className="org.apache.catalina.webresources.JarResourceSet"
>
> base="/usr/local/calendar/google-api-services-calendar-v3-rev230-1.22.0.jar" 
> webAppMount="/WEB-INF/lib" internalPath="/."/>
>  className="org.apache.catalina.webresources.JarResourceSet"
>base="/usr/local/calendar/libs/google-http-client-1.22.0.jar" 
> webAppMount="/WEB-INF/lib" internalPath="/."/>
>  className="org.apache.catalina.webresources.JarResourceSet"
>
> base="/usr/local/calendar/libs/google-http-client-jackson2-1.22.0.jar" 
> webAppMount="/WEB-INF/lib" internalPath="/."/>
>  className="org.apache.catalina.webresources.JarResourceSet"
>base="/usr/local/calendar/libs/google-oauth-client-1.22.0.jar" 
> webAppMount="/WEB-INF/lib" internalPath="/."/>
>  className="org.apache.catalina.webresources.JarResourceSet"
>base="/usr/local/calendar/libs/jackson-core-2.1.3.jar" 
> webAppMount="/WEB-INF/lib" internalPath="/."/>
> 

I'd use org.apache.catalina.webresources.FileResourceSet.  There is an
example in "Ordering" section here:
http://tomcat.apache.org/tomcat-8.5-doc/config/resources.html#Nested_Components

The docs could be better.

> However, when I access the JSP page that need to resolve classes in these 
> .jar's, I get
> org.apache.jasper.JasperException: Unable to compile class for JSP:
>
> An error occurred at line: [20] in the generated java file: 
> [/work/Catalina/localhost/ed/org/apache/jsp/charters_jsp.java]
> Only a type can be imported. com.google.api.client.json.JsonFactory resolves 
> to a package
>
> Line 20 is:
> import com.google.api.client.json.JsonFactory;

It is odd.
Stacktrace?

In my experience I faced
https://bz.apache.org/bugzilla/show_bug.cgi?id=47323
but it is quite different from your case.

isPackage(className) check mentioned there tries to load (className +
".class") as a resource and reports "true, it is a package" if the
class resource is not found.

> I think I'm up to 12 hours messing with this and reading everything I can get 
> my hands on.
> Something that was so simple in tomcat 7 has turned out to be a nightmare in 
> tomcat 8.
> I still don't have a good understanding of what webAppMount is or what I 
> should set it to.
> I changed PostResources to JarResources and nothing changed.   The jar files 
> are not getting found
> or the classes in the jar files are not getting found.
>
> There is no way this can be this hard and complicated in tomcat 8.
>
> Please help.

Best regards,
Konstantin Kolinko

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

RE: Migration

[Berneburg, Cris J. - US]

Osama

> I have been asked by a company to update their existing working
> tomcat 5 application, which is working on an old Windows 2003
> platform and accessing SQL 2005. The new servers are Windows and
> SQL 2012. I downloaded  and installed Tomcat 8.5.12. So, what I
> need to do for migrating the existing application to work on the
> new environment?

If you do not have automated integrated testing to test your current SQL, 
stored procedures, etc., on the new SQL Server 2012 platform, one thing I would 
recommend is using the "SQL Server 2012 Upgrade Advisor".  It will help point 
out the areas in your current SQL server 2005 database that are not compatible 
with 2012.  There are some differences that could cause your stored procedures 
and other SQL to no longer run/compile.

--
Cris Berneburg
CACI Lead Software Engineer



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

Re: Migration

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Osama,

On 3/21/17 3:43 PM, M. Osama Alghwell wrote:
> On Mar 21, 2017 7:21 PM, "Christopher Schultz"
>  wrote:
> 
> Osama,
> 
> On 3/21/17 1:10 PM, M. Osama Alghwell wrote:
 I have been asked by a company to update their existing
 working tomcat 5 application, which is working on an old
 Windows 2003 platform and accessing SQL 2005. The new servers
 are Windows and SQL 2012. I downloaded  and installed Tomcat
 8.5.12. So, what I need to do for migrating the existing
 application to work on the new environment? Thank you in
 advance for your reply.
> 
>> Read through the Migration Guide: 
>> http://tomcat.apache.org/migration.html

> The migration guide for migrating from Tomcat 7 to 8

Is it?

> I need from 5 to 8.

I understand. The Migration Guide covers all (reasonably-recent) version
s.

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

iQIcBAEBCAAGBQJY0qHgAAoJEBzwKT+lPKRYoY4P/iu3h8vTd9m19PaaN847SZVE
ir1003x1rLyFdodhaYLKW+atMLeaGl+Y4pzjL+f54wzYKFGl7O/kK7+w4ji1pHrt
VpL+oUXd379Z1BPrG8iZXKE/lqdqpWArVrsanPz3/5a+UKoiEkz0l7Bu7zULhKBj
dx7L9c9x2qiXgaICeIa/ZgP04Sz8CZry6koeFHaATCsWiyr/VBzDt4cpfmVOsRIx
IRnixreh9l30+PVbDIZR864+M5G88xjLs26Mkc4YNtXmwPAb8q5LtQGDhHrVAWes
aZMbhR2iPsv5LOCj5DLpI2+AXmFiGWhDzhcYc9emqLKhB+r1DQNR+CtMz5gd/Ocz
SxNXdD4y2qB/gy1Jpkwyb4ne0+DrU4Ff4uR4XcY6JtPewZZN+RxtQKhvROKBr3ZI
BwoT0mB8CEkQr+IFaDfBlLPLRf18y0zZFIHBwiGrECr0Mia8UOABu/eGG6xIIh0/
/DE23PUf2pq4Vgy4I2adj9NpngytkUpO/Mm+j1PBiMRW11bPwBNVsUNQF9SIHAFc
D6BGFXEBlLXeBzohhxYL0MkAfewc60FlNHJAAVTzppwZ/JQfDOciJIfBpTyMSah9
PhN7DUiLrom5UMj995QmhLOrf+JCsbxBTbeuMgVW6opJgllLQujcN8A1J7nGCPPf
R+kSlAzBtHivI3Vb3pBd
=uihm
-END PGP SIGNATURE-

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

Re: Migration

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Osama,

On 3/21/17 3:46 PM, M. Osama Alghwell wrote:
> On Mar 21, 2017 7:25 PM, "Caldarale, Charles R"
>  wrote:
> 
>>> From: M. Osama Alghwell [mailto:malghw...@gmail.com] Subject:
>>> Migration
>> 
>>> I have been asked by a company to update their existing working
>>> tomcat 5 application, which is working on an old Windows 2003
>>> platform and
>> accessing
>>> SQL 2005. The new servers are Windows and SQL 2012. I
>>> downloaded  and installed Tomcat 8.5.12. So, what I need to do
>>> for migrating the existing application to work on the new
>>> environment?
>> 
>> The first step is to read the migration guides: 
>> http://tomcat.apache.org/migration.html
>> 
>> You'll need to look at all the ones that change levels, since the
>> steps are cumulative and there is no 5 -> 8.5 doc.
>> 
>> Once you've absorbed that, come back with specific questions.
> 
> I will follow the steps from 5 to 6, from 6 to 7, then from 7 to
> 8, is this what I should do?

You need to read and understand the migrations from 5.0 -> 8.5, but
there's no reason to actually install and test with each individual
major version in between.

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

iQIcBAEBCAAGBQJY0qGZAAoJEBzwKT+lPKRYfTAP/jnayHvU3lNAy8zB4S+ca3n4
V1ZU8rUjAIYkaWQwnVVIN76OkYhexNixKOjJ7BlvEZp5Gt4a+lA4/gbqsQwIZeWg
eIj0S4I0rW1HYzvGWxTau17hzSZi5XZKmeaYuffXz0labQJH7PldJcTamXMitCpK
rN2MtdWnzUS9l1Jj6p8wFf+oEWmCQJl3nwUut+oC8tgGPBf2ie+1Li4owXBTVvKZ
IOfRgASeOODzlf233pSLhgQWC8VQCtWkfofPwzgy+CS+Qtz2YVBKmhB5OwteY7J1
kkPxxSHRyUYE0FInb/btgU/Zj2nlYoJGTNxI8128bSvSwkVguyH6JVSqeePx+yNJ
vfE1UJ0ipgaF61jItj9dlAC1yP2UdBEwGyootHHVjZ+yUXIB/pknQfmsRRGHOEh4
im9gMqBOyORWc0WKGD7ia1Te08D/54D49tC+pFxjkYTJ5Nu31A4SecK6sso3ozZS
cGqUaqvBJTdlEGcEdBKrQM7/V16uRVIlScfAn9NsT9pL0kATdHbXm2Sc/QhIGajx
Fwn/QPdfTq6F6vUCDw2/4ydWIHedkgQQYZnJbXTME89FvuBx//tOupse9TiNURk0
88qQ8UzNG5YHKTflICR1nT9hw2WsRk5Xl9abSkZvrMYu6XKmK7+ZAuZsrw/2U/zA
ytKUfgtTlQoCJGEvNVNk
=NmkW
-END PGP SIGNATURE-

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

RE: Migration

[M. Osama Alghwell]

I will follow the steps from 5 to 6, from 6 to 7, then from 7 to 8, is this
what I should do?

On Mar 21, 2017 7:25 PM, "Caldarale, Charles R" 
wrote:

> > From: M. Osama Alghwell [mailto:malghw...@gmail.com]
> > Subject: Migration
>
> > I have been asked by a company to update their existing working tomcat 5
> > application, which is working on an old Windows 2003 platform and
> accessing
> > SQL 2005. The new servers are Windows and SQL 2012. I downloaded  and
> > installed Tomcat 8.5.12. So, what I need to
> > do for migrating the existing application to work on the new environment?
>
> The first step is to read the migration guides:
> http://tomcat.apache.org/migration.html
>
> You'll need to look at all the ones that change levels, since the steps
> are cumulative and there is no 5 -> 8.5 doc.
>
> Once you've absorbed that, come back with specific questions.
>
>  - 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: Migration

[M. Osama Alghwell]

The migration guide for migrating from Tomcat 7 to 8, I need from 5 to 8.
Thank you.

On Mar 21, 2017 7:21 PM, "Christopher Schultz" 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Osama,
>
> On 3/21/17 1:10 PM, M. Osama Alghwell wrote:
> > I have been asked by a company to update their existing working
> > tomcat 5 application, which is working on an old Windows 2003
> > platform and accessing SQL 2005. The new servers are Windows and
> > SQL 2012. I downloaded  and installed Tomcat 8.5.12. So, what I
> > need to do for migrating the existing application to work on the
> > new environment? Thank you in advance for your reply.
>
> Read through the Migration Guide:
> http://tomcat.apache.org/migration.html
>
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJY0WELAAoJEBzwKT+lPKRY5pQQAMVUxSFa+gNZLgCR1swbKWyV
> ksGQn6J18MUgX0opMd82NIyjyUjUt6a01E5O7FCr9zBECNRBZnEtGTmSGp8Yyh9i
> 6MmUGyjmmyI3UExhyRkprAfJ74QGGz5wKt5NDNX7igss3xRig9cx1LlfWmJSGHxa
> cZ5Xh2RDpqes4he09GKAdAjC7/dboRoAAZ4fNJABxNZxxHW2gGX/FZeEDuOMaD1O
> jLsuDyDpb4TdVLy/Yxn/mBc4scsXCx229pGHBV0PYD7SylvlJXa+/k6cJgj3f5iZ
> X+hxnFeTaR47M1Thqoa/WOxSkFKlvDbXi3DjEQx9nvnudm9TqZCYqXcrq7Pw9Qd6
> bpOP5cKXxrl1LCSDtxhc+6NUJKGu+piRuPibSRDcUNCcKNHmczf1zcMGwQ/GE3p/
> pYijz4v5FGfmIS/rt92igUJfAonGhAkiIKJdDUwSW+n7kUXVqj/TfCZlasQB+SsB
> sOAHruXr+9S0wa9wt3ekvVGkfkCQn1XXoTacV1sUe+N5x/zqpmA5Bv16hrMLr+xH
> kLk8dAm2SgC3WnOcEF1eUJ/KI1CP47eUqpziKyhlizuZhEi+QSWJz1w8HU3DtuHF
> uw1tPrDCEcyWdPJ2AzX2DnCCWYYO8Gp6GIHik3J/jry3k+bseeJBRbuYGqP5GfSI
> kNBDGVorkFNcx8hd1Yg8
> =CkDe
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

RE: Migration

[Caldarale, Charles R]

> From: M. Osama Alghwell [mailto:malghw...@gmail.com] 
> Subject: Migration

> I have been asked by a company to update their existing working tomcat 5
> application, which is working on an old Windows 2003 platform and accessing
> SQL 2005. The new servers are Windows and SQL 2012. I downloaded  and
> installed Tomcat 8.5.12. So, what I need to
> do for migrating the existing application to work on the new environment?

The first step is to read the migration guides:
http://tomcat.apache.org/migration.html

You'll need to look at all the ones that change levels, since the steps are 
cumulative and there is no 5 -> 8.5 doc.

Once you've absorbed that, come back with specific questions.

 - 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: Migration

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Osama,

On 3/21/17 1:10 PM, M. Osama Alghwell wrote:
> I have been asked by a company to update their existing working
> tomcat 5 application, which is working on an old Windows 2003
> platform and accessing SQL 2005. The new servers are Windows and
> SQL 2012. I downloaded  and installed Tomcat 8.5.12. So, what I
> need to do for migrating the existing application to work on the
> new environment? Thank you in advance for your reply.

Read through the Migration Guide:
http://tomcat.apache.org/migration.html


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

iQIcBAEBCAAGBQJY0WELAAoJEBzwKT+lPKRY5pQQAMVUxSFa+gNZLgCR1swbKWyV
ksGQn6J18MUgX0opMd82NIyjyUjUt6a01E5O7FCr9zBECNRBZnEtGTmSGp8Yyh9i
6MmUGyjmmyI3UExhyRkprAfJ74QGGz5wKt5NDNX7igss3xRig9cx1LlfWmJSGHxa
cZ5Xh2RDpqes4he09GKAdAjC7/dboRoAAZ4fNJABxNZxxHW2gGX/FZeEDuOMaD1O
jLsuDyDpb4TdVLy/Yxn/mBc4scsXCx229pGHBV0PYD7SylvlJXa+/k6cJgj3f5iZ
X+hxnFeTaR47M1Thqoa/WOxSkFKlvDbXi3DjEQx9nvnudm9TqZCYqXcrq7Pw9Qd6
bpOP5cKXxrl1LCSDtxhc+6NUJKGu+piRuPibSRDcUNCcKNHmczf1zcMGwQ/GE3p/
pYijz4v5FGfmIS/rt92igUJfAonGhAkiIKJdDUwSW+n7kUXVqj/TfCZlasQB+SsB
sOAHruXr+9S0wa9wt3ekvVGkfkCQn1XXoTacV1sUe+N5x/zqpmA5Bv16hrMLr+xH
kLk8dAm2SgC3WnOcEF1eUJ/KI1CP47eUqpziKyhlizuZhEi+QSWJz1w8HU3DtuHF
uw1tPrDCEcyWdPJ2AzX2DnCCWYYO8Gp6GIHik3J/jry3k+bseeJBRbuYGqP5GfSI
kNBDGVorkFNcx8hd1Yg8
=CkDe
-END PGP SIGNATURE-

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

Re: Migration to Tomcat 8.0 Post/PreResources vs VirtualWebappLoader with optional resources

[Mark Thomas]

On 07/12/2016 09:01, Berg, R. van den (Robin) wrote:
> Hello!
> I have an issue that seems not supported anymore with Tomcat 8.
> The same problem is also posted in the comments on: 
> https://tomcat.apache.org/tomcat-8.0-doc/config/resources.html
> 
> PROBLEM:
> We used the virtualWebAppLoader to get some extra libraries and classes that 
> were on the machine on the classloader.
> The virtualClasspath-property of the virtualWebAppLoader was a ';'-seperated 
> list of directories. If one of them was empty, that was not a problem.
> We used the fact that non-existing/empty directories were not loaded, without 
> any exception. MQ were imported on
> Test-acceptance-production. However, in a local/dev-setup we do not provide 
> these libraries, since MQ-services are stubbed out.
> 
> We used the {Jar|File|Dir}ResourceSet in the context.xml as replacement for 
> the virtualWebAppLoader, as recommended by the migration guide.
> However, these fail when the base-property is non-existent. Therefore, it 
> breaks dev/local.
> 
> In the comments in 
> https://tomcat.apache.org/tomcat-8.0-doc/config/resources.html a solution was 
> posted to extend the {Jar|File|Dir}ResourceSet.
> However, that solution won't work for us, since we can't provide the 
> tomcat-instances on test-acc-prd with an extra class/library with the 
> extended class. (access-rights/cloud-solution only allows default setup).

Can you not simply create an empty directory in the right place for
dev/local ?

Mark

> 
> PREFERRRED SOLUTION:
> Just like the tomcat 7  virtualWebAppLoader we would like the ResourceSet to 
> be optional/non-failing if the resource is not available. Is there any 
> configuration/property I can use to do that?
> 
> Thanks,
> Kind Regards,
> 
> 
> ATTENTION:
> The information in this e-mail is confidential and only meant for the 
> intended recipient. If you are not the intended recipient, don't use or 
> disclose it in any way. Please let the sender know and delete the message 
> immediately.
> --
> 
> -
> 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: Migration to Tomcat 8.0 Post/PreResources vs VirtualWebappLoader with optional resources

[Berg, R. van den (Robin)]

Hi,

No. For the record: I didn't posted the issue on  
https://tomcat.apache.org/tomcat-8.0-doc/config/resources.html. I merely 
stumbled upon somebody having the same issue. I wanted to file an enhancement 
request. But, as also noted by the "what to do before posting a 
bug/enhancement"-page, I wanted to be 
sure there is no solution to this problem yet. 
I was interested whether this was already fixed perhaps, even though I couldn't 
find anything.
Also, maybe somebody knows a 'workaround', which would me because I don't have 
time to wait for the enhancement. Furthermore, I can't even use the 
newest version, unfortunately. That depends on the PAAS party.

Kind Regards,

-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
Sent: Wednesday, December 07, 2016 10:58 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Migration to Tomcat 8.0 Post/PreResources vs VirtualWebappLoader 
with optional resources

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Robin,

On 12/7/16 4:01 AM, Berg, R. van den (Robin) wrote:
> Hello! I have an issue that seems not supported anymore with Tomcat 8. 
> The same problem is also posted in the comments on:
> https://tomcat.apache.org/tomcat-8.0-doc/config/resources.html
> 
> PROBLEM: We used the virtualWebAppLoader to get some extra libraries 
> and classes that were on the machine on the classloader.
> The virtualClasspath-property of the virtualWebAppLoader was a 
> ';'-seperated list of directories. If one of them was empty, that was 
> not a problem. We used the fact that non-existing/empty directories 
> were not loaded, without any exception. MQ were imported on 
> Test-acceptance-production. However, in a local/dev-setup we do not 
> provide these libraries, since MQ-services are stubbed out.
> 
> We used the {Jar|File|Dir}ResourceSet in the context.xml as 
> replacement for the virtualWebAppLoader, as recommended by the 
> migration guide. However, these fail when the base-property is 
> non-existent. Therefore, it breaks dev/local.
> 
> In the comments in
> https://tomcat.apache.org/tomcat-8.0-doc/config/resources.html a 
> solution was posted to extend the {Jar|File|Dir}ResourceSet.
> However, that solution won't work for us, since we can't provide the 
> tomcat-instances on test-acc-prd with an extra class/library with the 
> extended class. (access-rights/cloud-solution only allows default 
> setup).
> 
> PREFERRRED SOLUTION: Just like the tomcat 7  virtualWebAppLoader we 
> would like the ResourceSet to be optional/non-failing if the resource 
> is not available. Is there any configuration/property I can use to do 
> that?

Did you file an enhancement request as suggested by Konstantin all those months 
ago?

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

iQIcBAEBCAAGBQJYSIXzAAoJEBzwKT+lPKRYRlcP/ip62nstdty643NjIdy8ImN4
/lhGdpw9qUfGTDiGF/wtqfOeAcTOIfoH1f0ZmnNaP9lZFMu917IT6Z0y3+fOwwnE
M3GPKBCZTQne3wY2oHqZujv4WVAiYzmcNlPDxeHljxP/aSiAf6DOyaWwGFLlUIml
7RiGBE+oJGQAMhohulPvSlh1ldSAsF637+xJA0O18DpRdSx9ikgDeeodRtA9Ei1d
R8sbZ9atYTqMH9ee4GBkc8yJDfZqf3Fo1FUjKghB3S4M9yxyjKqLqJORrFm4fOLH
PM4Oq7gkLEJNBWhkzABj6ruMw5/PHXrz4BV+K7rapdCSH7Bg5WXASiX0O0Z/rw1G
nVgd4kVwLRqDnRANjyU8+BnzyDq0sQ0Ndp6EZ/Sw4xBnaopQyYX9jsaqkQ8tqSg2
md4LdkX4axn/w0EhnE/XtVLBmmsjC4L7ALuGFleG+Etp2gh3vKE1rmhphwHUqvXX
GEKjR6HnXbCGKwJHkWt9lawpmK8N+VmI9FSbyx0vh4kheMjIUQmkH7uNnJhGOQc4
FO5GrS+zqEJwuDoBVZny2ZjSeOctu5bPJGfwd2nZa0uG8qra6Qhi8RCLSkG2ZPsq
EABJEpoLZMeiB6U6TFNQrxUFUTn1dtLQgQxKdbq8hUxX4n5KMl/12pZNhyapfor4
/PvNObLiXIy6930k/0Ag
=+++8
-END PGP SIGNATURE-

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



ATTENTION:
The information in this e-mail is confidential and only meant for the intended 
recipient. If you are not the intended recipient, don't use or disclose it in 
any way. Please let the sender know and delete the message immediately.
--

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

Re: Migration to Tomcat 8.0 Post/PreResources vs VirtualWebappLoader with optional resources

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Robin,

On 12/7/16 4:01 AM, Berg, R. van den (Robin) wrote:
> Hello! I have an issue that seems not supported anymore with Tomcat
> 8. The same problem is also posted in the comments on:
> https://tomcat.apache.org/tomcat-8.0-doc/config/resources.html
> 
> PROBLEM: We used the virtualWebAppLoader to get some extra
> libraries and classes that were on the machine on the classloader. 
> The virtualClasspath-property of the virtualWebAppLoader was a
> ';'-seperated list of directories. If one of them was empty, that
> was not a problem. We used the fact that non-existing/empty
> directories were not loaded, without any exception. MQ were
> imported on Test-acceptance-production. However, in a
> local/dev-setup we do not provide these libraries, since
> MQ-services are stubbed out.
> 
> We used the {Jar|File|Dir}ResourceSet in the context.xml as
> replacement for the virtualWebAppLoader, as recommended by the
> migration guide. However, these fail when the base-property is
> non-existent. Therefore, it breaks dev/local.
> 
> In the comments in
> https://tomcat.apache.org/tomcat-8.0-doc/config/resources.html a
> solution was posted to extend the {Jar|File|Dir}ResourceSet. 
> However, that solution won't work for us, since we can't provide
> the tomcat-instances on test-acc-prd with an extra class/library
> with the extended class. (access-rights/cloud-solution only allows
> default setup).
> 
> PREFERRRED SOLUTION: Just like the tomcat 7  virtualWebAppLoader we
> would like the ResourceSet to be optional/non-failing if the
> resource is not available. Is there any configuration/property I
> can use to do that?

Did you file an enhancement request as suggested by Konstantin all
those months ago?

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

iQIcBAEBCAAGBQJYSIXzAAoJEBzwKT+lPKRYRlcP/ip62nstdty643NjIdy8ImN4
/lhGdpw9qUfGTDiGF/wtqfOeAcTOIfoH1f0ZmnNaP9lZFMu917IT6Z0y3+fOwwnE
M3GPKBCZTQne3wY2oHqZujv4WVAiYzmcNlPDxeHljxP/aSiAf6DOyaWwGFLlUIml
7RiGBE+oJGQAMhohulPvSlh1ldSAsF637+xJA0O18DpRdSx9ikgDeeodRtA9Ei1d
R8sbZ9atYTqMH9ee4GBkc8yJDfZqf3Fo1FUjKghB3S4M9yxyjKqLqJORrFm4fOLH
PM4Oq7gkLEJNBWhkzABj6ruMw5/PHXrz4BV+K7rapdCSH7Bg5WXASiX0O0Z/rw1G
nVgd4kVwLRqDnRANjyU8+BnzyDq0sQ0Ndp6EZ/Sw4xBnaopQyYX9jsaqkQ8tqSg2
md4LdkX4axn/w0EhnE/XtVLBmmsjC4L7ALuGFleG+Etp2gh3vKE1rmhphwHUqvXX
GEKjR6HnXbCGKwJHkWt9lawpmK8N+VmI9FSbyx0vh4kheMjIUQmkH7uNnJhGOQc4
FO5GrS+zqEJwuDoBVZny2ZjSeOctu5bPJGfwd2nZa0uG8qra6Qhi8RCLSkG2ZPsq
EABJEpoLZMeiB6U6TFNQrxUFUTn1dtLQgQxKdbq8hUxX4n5KMl/12pZNhyapfor4
/PvNObLiXIy6930k/0Ag
=+++8
-END PGP SIGNATURE-

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

Re: Migration from Tomcat6-Cluster to Tomcat7-Cluster: Digest Authentication problem

[Rainer Jung]

Am 17.03.2015 um 15:40 schrieb Sascha Skorupa:

Hi Rainer,

currently not (Apache 2.2) but it might be an option to upgrade the OS and the 
Apache if it leads to a solution.


OK. But think twice, whether it is better to just compile mod_jk from 
sources or do the big update. Updating to 2.4 will bring many 
interesting achievements, but just for fixing this issue quickly it 
would be better to update mod_jk, even if this means switching to a 
non-OS-provided variant.


If you seriously plan the 2.4 update and you have a test system, I could 
provide you with the non-trivial workaround letting Apache set the 
cookie. You would need to thoroughly test this though.


Regards,

Rainer

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

Re: Migration from Tomcat6-Cluster to Tomcat7-Cluster: Digest Authentication problem

[Rainer Jung]

Hi Sascha,

Am 17.03.2015 um 13:02 schrieb Sascha Skorupa:

Rainer, thank you for this hint, but unfortunately, this feature is too new to 
be included in any current mod_jk linux package and building it from source it 
not an option for a production environment. Too bad because that is exactly 
what we need that.


are you using Apache 2.4? In that case I might have an alternative 
recipe for you.


Regards,

Rainer


Christopher, your suggestion sounds interesting. Would it be an option for 
future releases of tomcat?

Sascha

-Ursprüngliche Nachricht-
Von: Christopher Schultz [mailto:ch...@christopherschultz.net]
Gesendet: Freitag, 13. März 2015 19:24
An: Tomcat Users List
Betreff: Re: Migration from Tomcat6-Cluster to Tomcat7-Cluster: Digest 
Authentication problem

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Rainer,

On 3/13/15 12:15 PM, Rainer Jung wrote:

Am 13.03.2015 um 16:28 schrieb Christopher Schultz:

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256

Mark,

On 3/12/15 1:13 PM, Mark Thomas wrote:

On 12/03/2015 15:20, Sascha Skorupa wrote:

Hi,

here:

http://grokbase.com/t/tomcat/users/13bvsbwb8s/multiple-servers-and-
digest-authentication









the same problem is described and the recommended solution is to use

sticky load balancing. But, the problem in a tomcat cluster is that
the session ID is generated after a successful authentication. The
first http response (401 with Authentication
Header) does not contain a session ID.


How should sticky load balancing be configured or how to enforce
session id generation before authentication?


Most load-balancers have various options for doing this that don't
depend on the back-end server at all.


Perhaps an option in Tomcat that will force the creation of a session
when a DIGEST authentication is requested might be useful. This would
tie e.g. mod_jk to the proper back-end server.

I'm not sure how this could be done using mod_jk without such a
feature, or changes to mod_jk itself to annotate the request with the
chosen worker, which could then be converted into a cookie in order
to keep the node-hint associated with the client.


Yes, mod_jk can help since version 1.2.38: Look for
set_session_cookie on
http://tomcat.apache.org/connectors-doc/reference/workers.html.
Using that attribute you can let mod_jk set the cookie, if it doesn't
find one already set by Tomcat. You need to also set
session_cookie=JSESSIONID and session_cookie_path=/myapp where you
adjust myapp to your context path.


Oh, good: I had missed that feature. Thanks for pointing it out!

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJVAytTAAoJEBzwKT+lPKRYO9EP/1NnmcKmXYwYYvtnb97dMZmz
NI7GIaZYDhx1NLb7w5UFDrPNhaAvBDSvzmNxnhZPfdPcwUK93k95+KVymrpI49xh
wJ7wbBlFPJcB6coK35jwp0oZnfKbUyHFZ6Qr/r4fbrd57PDqCKGLc/6YicY11nm+
3EGCYHKe/B2orPNJvw+B5ZCm4cJFwh/VWespkAylCWbqJV1k882zG4MJEwZWgXdn
FBLggaCW1N5V6LNAhKiwyrrZrcV9TY3zoMI4Dd8M8yzq8MoTbUK2g2sYZh0LNm0d
0ZbcE07uBUgO5NamNk049vSK+yx0gfHmnL1Gst/jdQ23I8876cTYNCkJKyb0/uDq
x5nv2K+dYj1rDeak3j4PS35W+Z6C/SCyp8n3W2L16xtLYtDRQTYv4OTOv1oVTuA2
UueFMwnqRoJV24nLathp29RnjODK7shYce1JqShiAVXzyKSgAkWsu2J8V07txUjP
4v+E0LrWOGEimvHfrOYqdTmH+Ed6YEcttrYU2ddH1g2z4Hz9n+S+fsO2fQgLhY/S
V6RluOXfAlg6+IFEtW7DW2PzXuQxOHfKfIX3dlBDGrJGoYNFdYY+uaZO6TPyp7qR
UVO9BRA0Roxtpvn7TpJJjygjNXM7uac5MMeCJtA4KPd29PT0sxAnJv+NYpYJ1F35
XROKEh5OIpcNKOPxBoof
=w+jN
-END PGP SIGNATURE-


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

Re: Migration from Tomcat6-Cluster to Tomcat7-Cluster: Digest Authentication problem

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Rainer,

On 3/17/15 11:12 AM, Rainer Jung wrote:
 Am 17.03.2015 um 15:40 schrieb Sascha Skorupa:
 Hi Rainer,
 
 currently not (Apache 2.2) but it might be an option to upgrade
 the OS and the Apache if it leads to a solution.
 
 OK. But think twice, whether it is better to just compile mod_jk
 from sources or do the big update.

+1

I find it hard to believe that you (or your NOC) would be willing to
upgrade the OS and the web server to use an alternative solution, but
not willing to upgrade to a newer version of single, specialized
module for the web server.

Note that you don't have to have a compiler on the target system; you
just need to be able to cross-compile to that test system (or do what
I do and have a spare server with identical architecture, etc.
available for module builds).

 Updating to 2.4 will bring many interesting achievements, but just
 for fixing this issue quickly it would be better to update mod_jk,
 even if this means switching to a non-OS-provided variant.

+1

Building is trivial.

 If you seriously plan the 2.4 update and you have a test system, I
 could provide you with the non-trivial workaround letting Apache
 set the cookie. You would need to thoroughly test this though.

- -chris

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJVCFHcAAoJEBzwKT+lPKRYOQAQAJnIlsepWBvZlO438/zwXIYM
WI0X3LspAUt1v1c0JOXagL5VUdZO68/euBV7rmoKaHvo11lEH5lFQ9M91unvRWer
d7AQZoTc1+VQDcnBrGDzw6M7jQqlKf2Y7Jadlj9TfNm68cwCYFhpan1Wcv/XCMpy
/1Q5j/gW77AdPNpAvtFGOXZ0HPbMpkC+ZpsfFjgpOrwUBPL195xpQXM5nJLoYpAa
7uR34FCAbIIR0Glho/IHqzadxrSBq3AEVZau1uiGi3t8BjuWcOfq85bMZ0dCGdl+
Hlj6wKaTpS6AJi9By5d0xbXkqu5wBY2qFgY6wNq/cHO/Js+svPPMtME7eUZiOPAY
t2dUszkzqw0JOEqTN0I1gr0cGVOhJYbHMAdCHrb15FtWACeQVHVK7ikI0GJvKMG3
8EUIW21go3ID4jHBpexMC23QZDKfDTIhzx9Ec300lxRbjkfzpTCEvu3mM36w6y7+
fsRPPkpY0KqFe25nYw/DZCMS4KeAZ5dZSQa3sQSYgpozP71UrRZJw2+cqdALj29Q
Ozru/eLGLAvJuOKbXgSMIBfEQugx8vTGzE60Db7e61thMPmyHXlHqi1+zKDnODej
g6kbQtNDhak+0AfI2oFbmvHGz+hN8bAJa62hA/3jDKiYphxwH2JpJW4qmcs7HI91
qRp/u8yrAe8S/UAc+x+2
=95gA
-END PGP SIGNATURE-

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

Re: Migration from Tomcat6-Cluster to Tomcat7-Cluster: Digest Authentication problem

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Rainer,

On 3/13/15 12:15 PM, Rainer Jung wrote:
 Am 13.03.2015 um 16:28 schrieb Christopher Schultz:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
 
 Mark,
 
 On 3/12/15 1:13 PM, Mark Thomas wrote:
 On 12/03/2015 15:20, Sascha Skorupa wrote:
 Hi,
 
 here:
 
 http://grokbase.com/t/tomcat/users/13bvsbwb8s/multiple-servers-and-digest-authentication





 
the same problem is described and the recommended solution is to use
 sticky load balancing. But, the problem in a tomcat cluster is
 that the session ID is generated after a successful
 authentication. The first http response (401 with Authentication
 Header) does not contain a session ID.
 
 How should sticky load balancing be configured or how to
 enforce session id generation before authentication?
 
 Most load-balancers have various options for doing this that
 don't depend on the back-end server at all.
 
 Perhaps an option in Tomcat that will force the creation of a
 session when a DIGEST authentication is requested might be
 useful. This would tie e.g. mod_jk to the proper back-end
 server.
 
 I'm not sure how this could be done using mod_jk without such a 
 feature, or changes to mod_jk itself to annotate the request with
 the chosen worker, which could then be converted into a cookie in
 order to keep the node-hint associated with the client.
 
 Yes, mod_jk can help since version 1.2.38: Look for
 set_session_cookie on
 http://tomcat.apache.org/connectors-doc/reference/workers.html.
 Using that attribute you can let mod_jk set the cookie, if it
 doesn't find one already set by Tomcat. You need to also set
 session_cookie=JSESSIONID and session_cookie_path=/myapp where
 you adjust myapp to your context path.

Oh, good: I had missed that feature. Thanks for pointing it out!

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJVAytTAAoJEBzwKT+lPKRYO9EP/1NnmcKmXYwYYvtnb97dMZmz
NI7GIaZYDhx1NLb7w5UFDrPNhaAvBDSvzmNxnhZPfdPcwUK93k95+KVymrpI49xh
wJ7wbBlFPJcB6coK35jwp0oZnfKbUyHFZ6Qr/r4fbrd57PDqCKGLc/6YicY11nm+
3EGCYHKe/B2orPNJvw+B5ZCm4cJFwh/VWespkAylCWbqJV1k882zG4MJEwZWgXdn
FBLggaCW1N5V6LNAhKiwyrrZrcV9TY3zoMI4Dd8M8yzq8MoTbUK2g2sYZh0LNm0d
0ZbcE07uBUgO5NamNk049vSK+yx0gfHmnL1Gst/jdQ23I8876cTYNCkJKyb0/uDq
x5nv2K+dYj1rDeak3j4PS35W+Z6C/SCyp8n3W2L16xtLYtDRQTYv4OTOv1oVTuA2
UueFMwnqRoJV24nLathp29RnjODK7shYce1JqShiAVXzyKSgAkWsu2J8V07txUjP
4v+E0LrWOGEimvHfrOYqdTmH+Ed6YEcttrYU2ddH1g2z4Hz9n+S+fsO2fQgLhY/S
V6RluOXfAlg6+IFEtW7DW2PzXuQxOHfKfIX3dlBDGrJGoYNFdYY+uaZO6TPyp7qR
UVO9BRA0Roxtpvn7TpJJjygjNXM7uac5MMeCJtA4KPd29PT0sxAnJv+NYpYJ1F35
XROKEh5OIpcNKOPxBoof
=w+jN
-END PGP SIGNATURE-

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

Re: Migration from Tomcat6-Cluster to Tomcat7-Cluster: Digest Authentication problem

[Rainer Jung]

Am 13.03.2015 um 16:28 schrieb Christopher Schultz:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Mark,

On 3/12/15 1:13 PM, Mark Thomas wrote:

On 12/03/2015 15:20, Sascha Skorupa wrote:

Hi,

here:

http://grokbase.com/t/tomcat/users/13bvsbwb8s/multiple-servers-and-digest-authentication




the same problem is described and the recommended solution is to use
sticky load balancing. But, the problem in a tomcat cluster is that the
session ID is generated after a successful authentication. The first
http response (401 with Authentication Header) does not contain a
session ID.


How should sticky load balancing be configured or how to enforce
session id generation before authentication?


Most load-balancers have various options for doing this that don't
depend on the back-end server at all.


Perhaps an option in Tomcat that will force the creation of a session
when a DIGEST authentication is requested might be useful. This would
tie e.g. mod_jk to the proper back-end server.

I'm not sure how this could be done using mod_jk without such a
feature, or changes to mod_jk itself to annotate the request with the
chosen worker, which could then be converted into a cookie in order to
keep the node-hint associated with the client.


Yes, mod_jk can help since version 1.2.38: Look for set_session_cookie 
on http://tomcat.apache.org/connectors-doc/reference/workers.html. Using 
that attribute you can let mod_jk set the cookie, if it doesn't find one 
already set by Tomcat. You need to also set session_cookie=JSESSIONID 
and session_cookie_path=/myapp where you adjust myapp to your context 
path.


Regards,

Rainer

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

Re: Migration Tomcat 5x to 7.0.8

[Konstantin Kolinko]

2011/8/19 Kumar, Kiran P kiran.p.kumar...@nielsen.com

 Team,
 We are migrating form tomcat 5x to 7.0.8
 In Tomcat 5.0 we are defining the url below
 url = 
 path/APReports/servlet/com.nielsenmedia.umi.ap.hwsw.QuerySWServlet;  and 
 sending the  request using the ajax
 Like o.open(POST, url , true);
 So I am not getting any problem in Tomcat 5
 In Tomcat7, I am getting below error

 What are the changes required  to do in  Tomcat 7.0.8.


Do not use invoker servlet. It is broken by design. You have to
provide mappings for all your servlets explicitly, e.g.:

servlet
servlet-nameQuerySWServlet/servlet-name

servlet-classcom.nielsenmedia.umi.ap.hwsw.QuerySWServlet/servlet-class
/servlet
servlet-mapping
servlet-nameQuerySWServlet/servlet-name

url-pattern/servlet/com.nielsenmedia.umi.ap.hwsw.QuerySWServlet/url-pattern
/servlet-mapping

(servlet name can be arbitrary but must be the same between servlet
and servlet-mapping).

See here for longer story, and it is also mentioned in the FAQ:
http://www.coderanch.com/how-to/java/InvokerServlet

Best regards,
Konstantin Kolinko

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

Re: migration from apache tomcat 5.5.20 to 6.0.26 procedure required.

[Pid]

On 03/06/2010 12:21, prakash mahavrataya wrote:
 Hi All,
 
 I have to migrate the existing tomcat from 5.5.20 to 6.0.26. As i found that
 the folders common and shared do not exist in 6.0.26. So I am not sure how
 to migrate from the current to the latest. Please send me the procedure
 for successful migration without any loss of files and folders.

Step 1: read the documentation for version 6.0.

 http://tomcat.apache.org/tomcat-6.0-doc/

Carefully read the release notes, changelog etc.

Step 2: download and install the current binary and familiarise yourself
with the config files and new layout.


If you have specific questions, come back and ask them.


p


 Regards
 Prakash
 




signature.asc
Description: OpenPGP digital signature

Re: migration from apache tomcat 5.5.20 to 6.0.26 procedure required.

[Mark Thomas]

On 03/06/2010 12:28, Pid wrote:
 On 03/06/2010 12:21, prakash mahavrataya wrote:
 Hi All,

 I have to migrate the existing tomcat from 5.5.20 to 6.0.26. As i found that
 the folders common and shared do not exist in 6.0.26. So I am not sure how
 to migrate from the current to the latest. Please send me the procedure
 for successful migration without any loss of files and folders.
 
 Step 1: read the documentation for version 6.0.
 
  http://tomcat.apache.org/tomcat-6.0-doc/
 
 Carefully read the release notes, changelog etc.

Also http://tomcat.apache.org/migration.html

Mark

 
 Step 2: download and install the current binary and familiarise yourself
 with the config files and new layout.
 
 
 If you have specific questions, come back and ask them.
 
 
 p
 
 
 Regards
 Prakash

 
 




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

Re: migration to 5.5.27

[Mark Thomas]

Timothy J Schumacher wrote:
 Hi,
 
 I am currently running tomcat 5.0.12 and want to upgrade to 5.5.27.

snip /

Please don't hijack threads.

Mark


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

Re: Migration from Tomcat 4.1 to 6.0 Urgent

[Rashid Malik]

Chris/Chuck,

You are probably right about httpd.  Please see the attached images for 
details.  The reason why I thought I had a 2.2 application is because whenever 
I shutdown the 2.2 service, the main web site running on port 80 would not 
launch.  Please excuse my naiveness about our configuration.  I just recently 
inherited this system and was not provide any documentation.. so I am trying to 
figure it all out.  Anyway, I only need to keep the tomcat 6.0 version of the 
tomcat.  Can you please explain how I should configure httpd to work with the 
tomcat 6.0 version of the application, not 4.1.  Chris provided me with the 
following instructions.  It seems like I have to use mod_proxy_http or 
mod_proxy_ajp.  Can you please provide me step by step instruction on how I 
should change my existing configuration to work with the newer application?  
Thank you so so much.  God Bless...


Rashid,

On 4/7/2009 5:08 PM, Rashid Malik wrote:
 Hi, I changed port 8080 to 80 and I get page not found error.  Please
 note that I have another website that is running on an older version
 of tomcat.

Aah, you didn't mention that.

Only one process may bind to a particular interface/port combination. In
your case, port 80 is already taken (by Tomcat 4.1). If you want both
Tomcat 4.1 ans 6.0 to appear to be using port 80, you will need to put
another piece of software out in front in order to play traffic cop and
properly route the requests to the appropriate server (app on TC4.1
versus app on TC6.0).

Apache httpd is a popular choice for accomplishing this.

You will have to:

1. Change Tomcat 4.1's configuration so that the HTTP port is
   something /other/ than port 80 (8080 is a popular choice)
2. Change Tomcat 6.0's configuration so that the HTTP port is
   something /other/ than port 80 and 8080 (8081?)
3. Install Apache httpd and have it listen on port 80
4. Configure httpd to send the appropriate requests to the
   appropriate back-end server

To accomplish #4, you will need to use either mod_proxy_http,
mod_proxy_ajp (both built-into Apache httpd 2.2.x) or mod_jk (which is a
separate download).

There is a lot of documentation for using mod_jk here:
http://tomcat.apache.org/connectors-doc/ 

If you use mod_proxy_http, you'll need to do:

ProxyPass /appA http://localhost:8080/appA 
ProxyPass /appB http://localhost:8081/appB 

That should be enough to get you started.

- -chris


 Christopher Schultz ch...@christopherschultz.net 4/7/2009 6:03:42 pm 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rashid,

On 4/7/2009 5:45 PM, Rashid Malik wrote:
 What I mean here is that I have three 3 installations of tomcat not
 2.

How many total web applications do you have?

Do any of them have any requirements for which Tomcat version on which
they are running?

It sounds like the answer is I have 3 webapps and at least one of them
requires Tomcat 6.0. If there are no other constraints, then just move
all your webapps to Tomcat 6.0, uninstall Tomcat 4.1, and change Tomcat
6.0's Connector to port=80 as I said previously.

 There is tomcat 2.2 application (using port 80)

As Chuck suggests, that is probably Apache httpd, which might actually
make things easier. If this is the case, you have not correctly
configured httpd to support your new application. Go into httpd's
configuration and find out where your other application is configured.
Read and /understand/ the configuration before you start changing
things. Reading that configuration plus the config reference I already
posted should clear a lot of things up.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ 

iEYEARECAAYFAknbzb4ACgkQ9CaO5/Lv0PCgngCeJLFU7QsoPwisTu7EVwvLHJ+g
3aEAoKgI0amw4JfW1BU0+5fbmG1rRO4G
=1bQY
-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

RE: Migration from Tomcat 4.1 to 6.0

[Jorge Medina]

http://httpd.apache.org/docs/2.2/

Read Compiling and Installing section
You will need to undertand the modules and directives of several
modules.

You will find in the Apache site instructions for mod_proxy, but if you
decide mod_jk then here are the instructions

http://tomcat.apache.org/connectors-doc/webserver_howto/apache.html


http://www.linuxjournal.com/article/8561


Can you please provide me step by step instruction...

Don't expect the people in the list to do your work.  
Research, read, experiment! Then come back with specific questions.

-Jorge

-Original Message-
From: Rashid Malik [mailto:rma...@dhmh.state.md.us] 
Sent: Wednesday, April 08, 2009 10:48 AM
To: Tomcat Users List
Subject: Re: Migration from Tomcat 4.1 to 6.0 Urgent

Chris/Chuck,

You are probably right about httpd.  Please see the attached images for
details.  The reason why I thought I had a 2.2 application is because
whenever I shutdown the 2.2 service, the main web site running on port
80 would not launch.  Please excuse my naiveness about our
configuration.  I just recently inherited this system and was not
provide any documentation.. so I am trying to figure it all out.
Anyway, I only need to keep the tomcat 6.0 version of the tomcat.  Can
you please explain how I should configure httpd to work with the tomcat
6.0 version of the application, not 4.1.  Chris provided me with the
following instructions.  It seems like I have to use mod_proxy_http or
mod_proxy_ajp.  Can you please provide me step by step instruction on
how I should change my existing configuration to work with the newer
application?  Thank you so so much.  God Bless...


Rashid,

On 4/7/2009 5:08 PM, Rashid Malik wrote:
 Hi, I changed port 8080 to 80 and I get page not found error.  Please 
 note that I have another website that is running on an older version 
 of tomcat.

Aah, you didn't mention that.

Only one process may bind to a particular interface/port combination. In
your case, port 80 is already taken (by Tomcat 4.1). If you want both
Tomcat 4.1 ans 6.0 to appear to be using port 80, you will need to put
another piece of software out in front in order to play traffic cop and
properly route the requests to the appropriate server (app on TC4.1
versus app on TC6.0).

Apache httpd is a popular choice for accomplishing this.

You will have to:

1. Change Tomcat 4.1's configuration so that the HTTP port is
   something /other/ than port 80 (8080 is a popular choice) 2. Change
Tomcat 6.0's configuration so that the HTTP port is
   something /other/ than port 80 and 8080 (8081?) 3. Install Apache
httpd and have it listen on port 80 4. Configure httpd to send the
appropriate requests to the
   appropriate back-end server

To accomplish #4, you will need to use either mod_proxy_http,
mod_proxy_ajp (both built-into Apache httpd 2.2.x) or mod_jk (which is a
separate download).

There is a lot of documentation for using mod_jk here:
http://tomcat.apache.org/connectors-doc/ 

If you use mod_proxy_http, you'll need to do:

ProxyPass /appA http://localhost:8080/appA ProxyPass /appB
http://localhost:8081/appB 

That should be enough to get you started.

- -chris


 Christopher Schultz ch...@christopherschultz.net 4/7/2009 6:03:42 
 pm 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rashid,

On 4/7/2009 5:45 PM, Rashid Malik wrote:
 What I mean here is that I have three 3 installations of tomcat not 2.

How many total web applications do you have?

Do any of them have any requirements for which Tomcat version on which
they are running?

It sounds like the answer is I have 3 webapps and at least one of them
requires Tomcat 6.0. If there are no other constraints, then just move
all your webapps to Tomcat 6.0, uninstall Tomcat 4.1, and change Tomcat
6.0's Connector to port=80 as I said previously.

 There is tomcat 2.2 application (using port 80)

As Chuck suggests, that is probably Apache httpd, which might actually
make things easier. If this is the case, you have not correctly
configured httpd to support your new application. Go into httpd's
configuration and find out where your other application is configured.
Read and /understand/ the configuration before you start changing
things. Reading that configuration plus the config reference I already
posted should clear a lot of things up.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ 

iEYEARECAAYFAknbzb4ACgkQ9CaO5/Lv0PCgngCeJLFU7QsoPwisTu7EVwvLHJ+g
3aEAoKgI0amw4JfW1BU0+5fbmG1rRO4G
=1bQY
-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

Re: Migration from Tomcat 4.1 to 6.0 Urgent

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rashid,

On 4/7/2009 4:45 PM, Rashid Malik wrote:
 To give you an example, the URL to get to the application in 4.1 is:
 
 http://localhost/MyWebAPP/
 
 However, after shutting down tomcat 4.1, installing and configuring
 tomcat 6.0, I can use the new web app only using the following URL.

 http://localhost:8080/MyWebAPP/

Your new 6.0 configuration does not match your old 4.1 configuration.
Check server.xml for an active (that is, not commented-out) Connector
element. It should have the port=8080 attribute. Just change this to
port=80 and you will no longer need to specify the port number.

 Taking out the port number 8080 from the following URL returns page
 not found.

That's because the port number is required if your server is not
listening on port 80 (the default port for HTTP).

 Please note that the 4.1 manager does not work for some reason.

You should use the 6.0 manager with Tomcat 6.0. The 4.1 manager will be
incompatible with Tomcat 6.0.

 P.s.  Also, is there a way to change the port from 8080 to something
 else?

See above.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAknbveAACgkQ9CaO5/Lv0PAybgCgliNBGcU7ul+gA6kwat/KErci
XnoAn2v/4+a0hPAjDhcja9QrG+9DDumL
=k/AZ
-END PGP SIGNATURE-

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

Re: Migration from Tomcat 4.1 to 6.0 Urgent

[Rashid Malik]

Hi,
I changed port 8080 to 80 and I get page not found error.  Please note that I 
have another website that is running on an older version of tomcat.  that 
website is already using port 80.  On that page, there is a link that connects 
to http://localhost/MyWebAPP/ .  If I use the older version of this site (4.1), 
it works.  However, using a 6.0 version only works with this URL:  
http://localhost:8080/MyWebAPP/ .  Please help

 Christopher Schultz ch...@christopherschultz.net 4/7/2009 4:56 PM 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rashid,

On 4/7/2009 4:45 PM, Rashid Malik wrote:
 To give you an example, the URL to get to the application in 4.1 is:
 
 http://localhost/MyWebAPP/ 
 
 However, after shutting down tomcat 4.1, installing and configuring
 tomcat 6.0, I can use the new web app only using the following URL.

 http://localhost:8080/MyWebAPP/ 

Your new 6.0 configuration does not match your old 4.1 configuration.
Check server.xml for an active (that is, not commented-out) Connector
element. It should have the port=8080 attribute. Just change this to
port=80 and you will no longer need to specify the port number.

 Taking out the port number 8080 from the following URL returns page
 not found.

That's because the port number is required if your server is not
listening on port 80 (the default port for HTTP).

 Please note that the 4.1 manager does not work for some reason.

You should use the 6.0 manager with Tomcat 6.0. The 4.1 manager will be
incompatible with Tomcat 6.0.

 P.s.  Also, is there a way to change the port from 8080 to something
 else?

See above.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ 

iEYEARECAAYFAknbveAACgkQ9CaO5/Lv0PAybgCgliNBGcU7ul+gA6kwat/KErci
XnoAn2v/4+a0hPAjDhcja9QrG+9DDumL
=k/AZ
-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

Re: Migration from Tomcat 4.1 to 6.0 Urgent

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rashid,

On 4/7/2009 5:08 PM, Rashid Malik wrote:
 Hi, I changed port 8080 to 80 and I get page not found error.  Please
 note that I have another website that is running on an older version
 of tomcat.

Aah, you didn't mention that.

Only one process may bind to a particular interface/port combination. In
your case, port 80 is already taken (by Tomcat 4.1). If you want both
Tomcat 4.1 ans 6.0 to appear to be using port 80, you will need to put
another piece of software out in front in order to play traffic cop and
properly route the requests to the appropriate server (app on TC4.1
versus app on TC6.0).

Apache httpd is a popular choice for accomplishing this.

You will have to:

1. Change Tomcat 4.1's configuration so that the HTTP port is
   something /other/ than port 80 (8080 is a popular choice)
2. Change Tomcat 6.0's configuration so that the HTTP port is
   something /other/ than port 80 and 8080 (8081?)
3. Install Apache httpd and have it listen on port 80
4. Configure httpd to send the appropriate requests to the
   appropriate back-end server

To accomplish #4, you will need to use either mod_proxy_http,
mod_proxy_ajp (both built-into Apache httpd 2.2.x) or mod_jk (which is a
separate download).

There is a lot of documentation for using mod_jk here:
http://tomcat.apache.org/connectors-doc/

If you use mod_proxy_http, you'll need to do:

ProxyPass /appA http://localhost:8080/appA
ProxyPass /appB http://localhost:8081/appB

That should be enough to get you started.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAknbw/sACgkQ9CaO5/Lv0PA/TgCfUuclAcTXu9aQwp7Ov2qSK7I5
nacAoK2ple5RH6My3jwaTIeQBXB88caf
=rcZe
-END PGP SIGNATURE-

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

Re: Migration from Tomcat 4.1 to 6.0 Urgent

[Rashid Malik]

Hello Chris,

Thanks for your quick response.  What you said makes sense to me but let me 
clarify my situation further.  

 Hi, I changed port 8080 to 80 and I get page not found error.  Please
 note that I have another website that is running on an older version
 of tomcat.

What I mean here is that I have three 3 installations of tomcat not 2.  There 
is tomcat 2.2 application (using port 80) that is being used for a very basic 
web page that has nothing but URLs to various parts of the application that is 
being run on Tomcat 6.0.  This tomcat 6.0 application is running on port 8080.  
The older version of this application was using tomcat 4.1 and listening on 
port 8080 also.  However, after upgrading the application to 6.0, I shutdown 
the tomcat 4.1 application.  From the tomcat 2.2 homepage, I can just click the 
link that will take me directly to  http://localhost/MyWebAPP/

However, after shutting down tomcat 4.1, installing and configuring tomcat 6.0, 
I can use the new web app only using the following URL.

http://localhost:8080/MyWebAPP/

Do I still need to do what you mentioned in your previous email or should there 
be a different approach.  I can completely uninstall tomcat 4.1 if I have to.  
Thanks, Rashid


 Christopher Schultz ch...@christopherschultz.net 4/7/2009 5:22 PM 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rashid,

On 4/7/2009 5:08 PM, Rashid Malik wrote:
 Hi, I changed port 8080 to 80 and I get page not found error.  Please
 note that I have another website that is running on an older version
 of tomcat.

Aah, you didn't mention that.

Only one process may bind to a particular interface/port combination. In
your case, port 80 is already taken (by Tomcat 4.1). If you want both
Tomcat 4.1 ans 6.0 to appear to be using port 80, you will need to put
another piece of software out in front in order to play traffic cop and
properly route the requests to the appropriate server (app on TC4.1
versus app on TC6.0).

Apache httpd is a popular choice for accomplishing this.

You will have to:

1. Change Tomcat 4.1's configuration so that the HTTP port is
   something /other/ than port 80 (8080 is a popular choice)
2. Change Tomcat 6.0's configuration so that the HTTP port is
   something /other/ than port 80 and 8080 (8081?)
3. Install Apache httpd and have it listen on port 80
4. Configure httpd to send the appropriate requests to the
   appropriate back-end server

To accomplish #4, you will need to use either mod_proxy_http,
mod_proxy_ajp (both built-into Apache httpd 2.2.x) or mod_jk (which is a
separate download).

There is a lot of documentation for using mod_jk here:
http://tomcat.apache.org/connectors-doc/ 

If you use mod_proxy_http, you'll need to do:

ProxyPass /appA http://localhost:8080/appA 
ProxyPass /appB http://localhost:8081/appB 

That should be enough to get you started.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ 

iEYEARECAAYFAknbw/sACgkQ9CaO5/Lv0PA/TgCfUuclAcTXu9aQwp7Ov2qSK7I5
nacAoK2ple5RH6My3jwaTIeQBXB88caf
=rcZe
-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

RE: Migration from Tomcat 4.1 to 6.0 Urgent

[Caldarale, Charles R]

 From: Rashid Malik [mailto:rma...@dhmh.state.md.us]
 Subject: Re: Migration from Tomcat 4.1 to 6.0 Urgent
 
 There is tomcat 2.2 application (using port 80)

There was never any Tomcat 2.2 release.  You may actually have httpd on port 
80, since there is a 2.2 version of that.  httpd usually communicates with 
Tomcat via port 8009 using mod_jk; is that what's really going on?

What you have described so far as your existing installation is not physically 
possible.

 - 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: Migration from Tomcat 4.1 to 6.0 Urgent

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rashid,

On 4/7/2009 5:45 PM, Rashid Malik wrote:
 What I mean here is that I have three 3 installations of tomcat not
 2.

How many total web applications do you have?

Do any of them have any requirements for which Tomcat version on which
they are running?

It sounds like the answer is I have 3 webapps and at least one of them
requires Tomcat 6.0. If there are no other constraints, then just move
all your webapps to Tomcat 6.0, uninstall Tomcat 4.1, and change Tomcat
6.0's Connector to port=80 as I said previously.

 There is tomcat 2.2 application (using port 80)

As Chuck suggests, that is probably Apache httpd, which might actually
make things easier. If this is the case, you have not correctly
configured httpd to support your new application. Go into httpd's
configuration and find out where your other application is configured.
Read and /understand/ the configuration before you start changing
things. Reading that configuration plus the config reference I already
posted should clear a lot of things up.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAknbzb4ACgkQ9CaO5/Lv0PCgngCeJLFU7QsoPwisTu7EVwvLHJ+g
3aEAoKgI0amw4JfW1BU0+5fbmG1rRO4G
=1bQY
-END PGP SIGNATURE-

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

Re: Migration tomcat 6.0.16 to 6.0.18

[Scott Dunbar]

What problems are you having?  This is a very simply migration.  I was 
able to just deploy my apps and my server.xml to the 6.0.18 server and 
go.  No code, no configuration changes for me at least.




vicens wrote:
How can I migrate a tomcat 6.0.16 to tomcat 6.0.18? 


Where I can found any tutorial?

Thanks
  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration tomcat 6.0.16 to 6.0.18

[vicens]

I doesn't have any problem yet, but why I need to re-deploy my apps when I
only want to upgrade a minor version of tomcat?



stdunbar wrote:
 
 What problems are you having?  This is a very simply migration.  I was 
 able to just deploy my apps and my server.xml to the 6.0.18 server and 
 go.  No code, no configuration changes for me at least.
 
 
 
 vicens wrote:
 How can I migrate a tomcat 6.0.16 to tomcat 6.0.18? 

 Where I can found any tutorial?

 Thanks
   
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Migration-tomcat-6.0.16-to-6.0.18-tp19900027p19900829.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration tomcat 6.0.16 to 6.0.18

[Scott Dunbar]

Ok, I may have assumed too much.  My configuration has virtual hosts 
spread over the file system.  I stopped 6.0.16, copied over the 
server.xml and Context XML's to 6.0.18, copied a required JDBC library 
to the lib directory, started 6.0.18 and I was done.  I guess that this 
isn't really a re-deploy.




vicens wrote:

I doesn't have any problem yet, but why I need to re-deploy my apps when I
only want to upgrade a minor version of tomcat?



stdunbar wrote:
  
What problems are you having?  This is a very simply migration.  I was 
able to just deploy my apps and my server.xml to the 6.0.18 server and 
go.  No code, no configuration changes for me at least.




vicens wrote:

How can I migrate a tomcat 6.0.16 to tomcat 6.0.18? 


Where I can found any tutorial?

Thanks
  
  

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from Tomcat 4.x to 5.5

[Gregor Schneider]

http://tomcat.apache.org/connectors-doc/

rgds

gregor

-- 
what's puzzlin' you, is the nature of my game
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.de:11371

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from Tomcat 4.x to 5.5

[Mark Thomas]

Arun Raj Ramkumar wrote:
 Hi all,
  
 I need to migrate my web application from tomcat 4.1.29 to tomcat 5.5. I
 have installed tomcat 5.5 with JDK 1.6 and deployed my web application, its
 working fine. 
 Tell me what are all the changes need to be done to connect apache 2.0 to
 tomcat 5.5. Earlier  apache 2.0 server was connected to tomcat 4.1.29. 
 In tomcat 4.1.29 server.xml there was the below tag for AJP connector
 !-- Define an AJP 1.3 Connector on port 8009 --
 Connector className=org.apache.ajp.tomcat4.Ajp1.3Connector
 port=8029 minProcessors=5 maxProcessors=150
 acceptCount=10 tomcatAuthentication=false debug=0/ 
  
 Is there any similar kind of above tag  for tomcat 5.5 so that i can enable
 authentication for my web application.

http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.html

The sample that comes with 5.5 in server.xml is:
Connector port=8009
   enableLookups=false
   redirectPort=8443 protocol=AJP/1.3 /

 Also tell me wat are all the changes need to be done in mod_jk.conf ,
 workers.properties and httpd.conf files as am migrating to tomcat5.5.

None.

Mark


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from Tomcat 4.x to 5.5

[David Smith]

Take a look at the server.xml that came with 5.5 and you'll see a
similar connector in there.  There won't be a className attribute --
instead it'll contain a protocol attribute with the value of AJP/1.3. 

With regard to authentication, the old tomcatAuthentication=false
still exists in version 5.5.

With regard to mod_jk, if you have a current version, no changes should
be required.  If however you have an older version, upgrade to the
latest version of mod_jk (currently 1.2.26).  Don't go after mod-jk2 as
it's a dead release.  More details are available at:

http://tomcat.apache.org/connectors-doc/

If you were considering using the version 4.1.x server.xml as the tomcat
5.5 server.xml, don't do it.  Take a copy of server.xml from 5.5, strip
out all the documentation comments, and then modify  to provide similar
functionality to the tomcat 4.1.x server.xml. 

--David

Arun Raj Ramkumar wrote:
 Hi all,
  
 I need to migrate my web application from tomcat 4.1.29 to tomcat 5.5. I
 have installed tomcat 5.5 with JDK 1.6 and deployed my web application, its
 working fine. 
 Tell me what are all the changes need to be done to connect apache 2.0 to
 tomcat 5.5. Earlier  apache 2.0 server was connected to tomcat 4.1.29. 
 In tomcat 4.1.29 server.xml there was the below tag for AJP connector
 !-- Define an AJP 1.3 Connector on port 8009 --
 Connector className=org.apache.ajp.tomcat4.Ajp1.3Connector
 port=8029 minProcessors=5 maxProcessors=150
 acceptCount=10 tomcatAuthentication=false debug=0/ 
  
 Is there any similar kind of above tag  for tomcat 5.5 so that i can enable
 authentication for my web application.
 Also tell me wat are all the changes need to be done in mod_jk.conf ,
 workers.properties and httpd.conf files as am migrating to tomcat5.5.
  
 Its very urgent. Thanks in advance for ur help.
  
 Regards,
 Arun.

   


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 4.1 to 6

[Jody Williams]

I can't go into much detail about the current operational system.
This is a Navy system.  I don't have the ability or authority to bring
another machine online for testing (whether it be a physical or VM).

Is it possible to have the 4.1 and 6 run concurrently?

Jody


On Sat, Aug 30, 2008 at 12:16 AM, Christopher Schultz
[EMAIL PROTECTED] wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Jody,

 Jody Williams wrote:
 I need to migrate from tomcat 4.1 to 6.  Are there any concerns I need
 to know about before starting?  Are there any suggestions to make the
 transition easier?

 Whatever you do, don't try to re-use your server.xml from 4.1. Start
 over with the one that ships with TC 6 and add capability as you go.
 Also, remember:

 1. Context elements don't go into server.xml anymore
   http://tomcat.apache.org/tomcat-6.0-doc/config/context.html

 2. Logging is completely different
   http://tomcat.apache.org/tomcat-6.0-doc/logging.html

 In the data center, we are using a RedHat (AS 2.1 I believe) server.
 I don't have the ability to test the application on another server to
 verify compatibility.

 That could be a problem. Do you mean that you're going to switch your
 production platform with no prior testing? :(

 Have you considered VMWare?

 - -chris
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAki4yacACgkQ9CaO5/Lv0PAzBACeIwfbcuT3tWTkzEAz30pyjhtw
 rCoAn3oV34GVsXHuF6rYZEblPXpezS5D
 =9Z1T
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 4.1 to 6

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jody,

Jody Williams wrote:
 I can't go into much detail about the current operational system.
 
 Is it possible to have the 4.1 and 6 run concurrently?

Of course. But, you'll have to set the Connector ports differently for
each one.

Ideally, your webapp should have all of its configuration packaged into
the WAR file (see the docs on context.xml I sent in my previous
message), so deployment onto your TC 6 should not take too much in the
way of configuration. TC 4.1 still requires Context elements in the
server-wide server.xml, though.

 This is a Navy system.  I don't have the ability or authority to bring
 another machine online for testing (whether it be a physical or VM).

Does your boss understand that not being able to test before deployment
is a grave error? Likewise, testing on a production system can be
disastrous.

Good luck,
- -chris

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAki5c/EACgkQ9CaO5/Lv0PB9bwCeNEYgmM9MnmuToJFF1X8+q+Gy
HC0AniU+nSnakbPb1ZK69r6SxdOQrhLN
=yxNH
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 4.1 to 6

[Jody Williams]

I will look into running both concurrently.  My boss understands.  The
issue is the time it takes to get a machine authorized to be placed on
the network.  For a server can take several months.  Since this is on
the legacy network that is going away, getting the authorization is
difficult.

I think my boss wants me to do the research and have an plan to
migrate if we are forced to do so.  We can probably buy some time.

Jody

On Sat, Aug 30, 2008 at 12:23 PM, Christopher Schultz
[EMAIL PROTECTED] wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Jody,

 Jody Williams wrote:
 I can't go into much detail about the current operational system.

 Is it possible to have the 4.1 and 6 run concurrently?

 Of course. But, you'll have to set the Connector ports differently for
 each one.

 Ideally, your webapp should have all of its configuration packaged into
 the WAR file (see the docs on context.xml I sent in my previous
 message), so deployment onto your TC 6 should not take too much in the
 way of configuration. TC 4.1 still requires Context elements in the
 server-wide server.xml, though.

 This is a Navy system.  I don't have the ability or authority to bring
 another machine online for testing (whether it be a physical or VM).

 Does your boss understand that not being able to test before deployment
 is a grave error? Likewise, testing on a production system can be
 disastrous.

 Good luck,
 - -chris

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAki5c/EACgkQ9CaO5/Lv0PB9bwCeNEYgmM9MnmuToJFF1X8+q+Gy
 HC0AniU+nSnakbPb1ZK69r6SxdOQrhLN
 =yxNH
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 4.1 to 6

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jody,

Jody Williams wrote:
 I need to migrate from tomcat 4.1 to 6.  Are there any concerns I need
 to know about before starting?  Are there any suggestions to make the
 transition easier?

Whatever you do, don't try to re-use your server.xml from 4.1. Start
over with the one that ships with TC 6 and add capability as you go.
Also, remember:

1. Context elements don't go into server.xml anymore
   http://tomcat.apache.org/tomcat-6.0-doc/config/context.html

2. Logging is completely different
   http://tomcat.apache.org/tomcat-6.0-doc/logging.html

 In the data center, we are using a RedHat (AS 2.1 I believe) server.
 I don't have the ability to test the application on another server to
 verify compatibility.

That could be a problem. Do you mean that you're going to switch your
production platform with no prior testing? :(

Have you considered VMWare?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAki4yacACgkQ9CaO5/Lv0PAzBACeIwfbcuT3tWTkzEAz30pyjhtw
rCoAn3oV34GVsXHuF6rYZEblPXpezS5D
=9Z1T
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: migration from tomcat 4.1 to 5.5

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Itay,

itay sahar wrote:
 i have an application running on tomcat 4.1.
 i want to make a huge addings to this application but first i want to work
 on tomcat 5.5 version.
 is there a way i can do it ? (i know it's not easy).

I recently upgraded 5 applications from 4.1.36 to 5.5.23 and it was
relatively smooth. The best advice I can give you is:

1. Move any Realm and/or DataSource elements from server.xml to
   [yourwebapp]/META-INF/context.xml (yes, that's META-INF, not WEB-INF)

2. Throw out your old server.xml. Start again with the one that ships
   with Tomcat 5.5 and customize it to meet your needs. You may find
   that, after doing #1 above that you no longer need any customizations
   to the server.xml file.

3. Throw out servlet-api.jar and servlet.jar from your application.
   Tomcat will ignore them at best (which I think is the case) and fail
   at worst.

 commons-beanutils.jar
 commons-collections-2.1.jar
 commons-dbcp-1.1.jar
 commons-digester.jar
 commons-logging.jar

You might want to check that you have the most recent (compatible)
versions of these libraries. I know that some of them have newer
versions. I wouldn't do this until after you have TC 5.5 working, though.

 mysql-connector-java-3.0.9-stable-bin.jar

Latest MySQL connector is 5.0.something (I have 5.0.7 right now). I
strongly recommend upgrading after you get everything else working. Note
that from 3.0 to 5.0 a lot of JDBC spec stuff was fixed (MySQL had not
been compliant in several instances) so some behavior has changed (for
instance, inserting more data than will fit into a character column now
throws an exception instead of issuing a warning). Check the docs to see
how to deal with these changes. In most cases, you can configure the
JDBC driver to revert to the old (non-JDBC-compliant) behavior.

 but i cannot use:javax.servlet.jsp.tagext.TagSupport
 and also javax.servlet.jsp.JspException is not available.

Do you have a problem compiling, or a problem deploying? Can you post a
full stack trace of the first error you encounter?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJ1Hs9CaO5/Lv0PARAlJiAKC4qUzX3yago9BSc04tE03h7k/yYQCgmElL
z/Y6O2l2yvLSkWp8zi4TtVA=
=8jqv
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: migration from tomcat 4.1 to 5.5

[David Smith]

Throw out servlet-api.jar, servlet.jar.  Servlet-api.jar is provided in 
the common/lib folder.  As to TagSupport and JspException, they should 
be provided by common/lib/jsp-api.jar.


--David

itay sahar wrote:


hi,

i have an application running on tomcat 4.1.
i want to make a huge addings to this application but first i want to work
on tomcat 5.5 version.
is there a way i can do it ? (i know it's not easy).

my project lib include the following jar files:  (works fine on tomcat
4.1)

aopalliance.jar
cglib-2.0-rc2.jar
commons-beanutils.jar
commons-collections-2.1.jar
commons-dbcp-1.1.jar
commons-digester.jar
commons-logging.jar
dom4j-1.4.jar
hibernate2.jar
jsf-api.jar
jsf-impl.jar
jstl.jar (i don't see any use in the application but the jar exist
anyway)
jta.jar
log4j.jar
mysql-connector-java-3.0.9-stable-bin.jar
odmg-3.0.jar
servlet.jar  (probably Servlet 2.3).
spring.jar
struts.jar


i'v tried to remove sevlet.jar and use servlet-api.jar (tomcat 5.5 version
-- Servlet 2.4) but i cannot use:javax.servlet.jsp.tagext.TagSupport
and also javax.servlet.jsp.JspException is not available.

thanks in advance,
itay

 




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: migration from tomcat 4.1 to 5.5

[itay sahar]

hi thanks for reply,

The DataSource details is in applicationContext.xml (spring).
There is no data moved from context.xml/server.xml from tomcat 4.1 to tomcat
5.5. (i just don't have it...)
succeeded run on the default 4.1 version.

I'm using the default files as they created by tomcat 5.5.
Tomcat ignore servlet.jar so it removed by me from the lib folder.
(in Apache only)

* In eclipse i still need it to compile!! i do want to work with the new jar
(servlet-api.jar)
but when i removed the servlet.jar from the class path i got this error on
one of the classes:

The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is
indirectly referenced from required .class files
*The application is up and running but when click on the application from
tomcat manager i got the followiong error:


java.lang.NoSuchMethodError:
javax.servlet.jsp.tagext.TagAttributeInfo.init(Ljava/lang/String;ZLjava/lang/String;ZZ)V

org.apache.jasper.compiler.TagLibraryInfoImpl.createAttribute(TagLibraryInfoImpl.java:581)

org.apache.jasper.compiler.TagLibraryInfoImpl.createTagInfo(TagLibraryInfoImpl.java:402)

org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:249)

org.apache.jasper.compiler.TagLibraryInfoImpl.init(TagLibraryInfoImpl.java:180)
org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:424)
org.apache.jasper.compiler.Parser.parseDirective(Parser.java:493)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1557)
org.apache.jasper.compiler.Parser.parse(Parser.java:127)

org.apache.jasper.compiler.ParserController.doParse(ParserController.java:212)

org.apache.jasper.compiler.ParserController.parse(ParserController.java:101)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:156)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:296)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:277)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:265)

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:564)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:299)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)

com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:142)

com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)

org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:691)

org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:661)
org.apache.jsp.index_jsp._jspService(index_jsp.java:48)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:328)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)




On 10/30/07, Christopher Schultz [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Itay,

 itay sahar wrote:
  i have an application running on tomcat 4.1.
  i want to make a huge addings to this application but first i want to
 work
  on tomcat 5.5 version.
  is there a way i can do it ? (i know it's not easy).

 I recently upgraded 5 applications from 4.1.36 to 5.5.23 and it was
 relatively smooth. The best advice I can give you is:

 1. Move any Realm and/or DataSource elements from server.xml to
   [yourwebapp]/META-INF/context.xml (yes, that's META-INF, not WEB-INF)

 2. Throw out your old server.xml. Start again with the one that ships
   with Tomcat 5.5 and customize it to meet your needs. You may find
   that, after doing #1 above that you no longer need any customizations
   to the server.xml file.

 3. Throw out servlet-api.jar and servlet.jar from your application.
   Tomcat will ignore them at best (which I think is the case) and fail
   at worst.

  commons-beanutils.jar
  commons-collections-2.1.jar
  commons-dbcp-1.1.jar
  commons-digester.jar
  commons-logging.jar

 You might want to check that you have the most recent (compatible)
 versions of these libraries. I know that some of them have newer
 versions. I wouldn't do this until after you have TC 5.5 working, though.

  

Re: migration from tomcat 4.1 to 5.5

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Itay,

itay sahar wrote:
 The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is
 indirectly referenced from required .class files
 *The application is up and running but when click on the application from
 tomcat manager i got the followiong error:

Hmm.. it's possible that something changed from Servlet 2.3 (Tomcat 4.x)
to Servlet 2.4 (Tomcat 5.x). Actually, it's probably the difference
between JSP 1.2 (Tomcat 4.x) and JSP 2.0 (Tomcat 5.5). In either case,
the API has changed, and you need to change along with it. The error you
are getting does not point to an API issue, but it's worth a check.

In your project, replace servlet-api.jar with the one you can find in
the Tomcat distribution. Re-compile and you'll probably get errors
(method not found?). Fix those errors and you'll probably be able to
deploy after that.

You can completely remove servlet.jar from your project (you do not need
it even to compile). This may be interfering, since this is the
implementation JAR. I think Tomcat will veto loading the servlet API
jar, but it might not detect the other one as a problem.

Once you do all that, let us know how it goes.

- -chris

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJ2w29CaO5/Lv0PARApq+AJ9IYAHhlaYEs6nvo7ZaQjhUgH0u8QCeOd0d
bENAJ2AAS3p9mW+vMdc/8Lc=
=i87r
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: migration from tomcat 4.1 to 5.5

[itay sahar]

well i change the classpath to work with the new servlet-api.jar and 
jsp-api.jar (new version from tomcat)
After deploy i removed from the folder the two jar mention above since they
already exist in common/lib.

so now:
1. No errors in eclipse ( after using the new jars).
2. Tomcat is starting with no errors.
3. But i still get the error: java.lang.NoSuchMethodError:
javax.servlet.jsp.tagext.TagAttributeInfo
when tring launch the application.

do you have an idea where is the conflict came from ?


On 10/30/07, Christopher Schultz [EMAIL PROTECTED] wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Itay,

 itay sahar wrote:
  The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is
  indirectly referenced from required .class files
  *The application is up and running but when click on the application
 from
  tomcat manager i got the followiong error:

 Hmm.. it's possible that something changed from Servlet 2.3 (Tomcat 4.x)
 to Servlet 2.4 (Tomcat 5.x). Actually, it's probably the difference
 between JSP 1.2 (Tomcat 4.x) and JSP 2.0 (Tomcat 5.5). In either case,
 the API has changed, and you need to change along with it. The error you
 are getting does not point to an API issue, but it's worth a check.

 In your project, replace servlet-api.jar with the one you can find in
 the Tomcat distribution. Re-compile and you'll probably get errors
 (method not found?). Fix those errors and you'll probably be able to
 deploy after that.

 You can completely remove servlet.jar from your project (you do not need
 it even to compile). This may be interfering, since this is the
 implementation JAR. I think Tomcat will veto loading the servlet API
 jar, but it might not detect the other one as a problem.

 Once you do all that, let us know how it goes.

 - -chris

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.7 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iD8DBQFHJ2w29CaO5/Lv0PARApq+AJ9IYAHhlaYEs6nvo7ZaQjhUgH0u8QCeOd0d
 bENAJ2AAS3p9mW+vMdc/8Lc=
 =i87r
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

RE: migration from tomcat 4.1 to 5.5

[Propes, Barry L]

I think that is mainly it is that the API has changed; I had a problem when I 
tried to bump up the JRE/JDK on mine (w/ 4.1) and had to revert back to Java 
2SE 1.4.0.2


-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 30, 2007 12:39 PM
To: Tomcat Users List
Subject: Re: migration from tomcat 4.1 to 5.5


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Itay,

itay sahar wrote:
 The type javax.servlet.jsp.tagext.TagSupport cannot be resolved. It is
 indirectly referenced from required .class files
 *The application is up and running but when click on the application from
 tomcat manager i got the followiong error:

Hmm.. it's possible that something changed from Servlet 2.3 (Tomcat 4.x)
to Servlet 2.4 (Tomcat 5.x). Actually, it's probably the difference
between JSP 1.2 (Tomcat 4.x) and JSP 2.0 (Tomcat 5.5). In either case,
the API has changed, and you need to change along with it. The error you
are getting does not point to an API issue, but it's worth a check.

In your project, replace servlet-api.jar with the one you can find in
the Tomcat distribution. Re-compile and you'll probably get errors
(method not found?). Fix those errors and you'll probably be able to
deploy after that.

You can completely remove servlet.jar from your project (you do not need
it even to compile). This may be interfering, since this is the
implementation JAR. I think Tomcat will veto loading the servlet API
jar, but it might not detect the other one as a problem.

Once you do all that, let us know how it goes.

- -chris

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJ2w29CaO5/Lv0PARApq+AJ9IYAHhlaYEs6nvo7ZaQjhUgH0u8QCeOd0d
bENAJ2AAS3p9mW+vMdc/8Lc=
=i87r
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: migration from tomcat 4.1 to 5.5

[Caldarale, Charles R]

 From: itay sahar [mailto:[EMAIL PROTECTED] 
 Subject: Re: migration from tomcat 4.1 to 5.5
 
 3. But i still get the error: java.lang.NoSuchMethodError:
 javax.servlet.jsp.tagext.TagAttributeInfo
 when tring launch the application.

There are three versions of the TagAttributeInfo constructor,
differentiated by the arguments, implemented at different versions of
the JSP spec.  Which one are you trying to use?  Your stack trace should
tell you.

 - 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: migration from tomcat 4.1 to 5.5

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Itay,

itay sahar wrote:
 well i change the classpath to work with the new servlet-api.jar and 
 jsp-api.jar (new version from tomcat)
 After deploy i removed from the folder the two jar mention above since they
 already exist in common/lib.
 
 so now:
 1. No errors in eclipse ( after using the new jars).
 2. Tomcat is starting with no errors.
 3. But i still get the error: java.lang.NoSuchMethodError:
 javax.servlet.jsp.tagext.TagAttributeInfo
 when trying launch the application.
 
 do you have an idea where is the conflict came from ?

That is very weird. Are you running Tomcat through Eclipse, or by
itself? Are you using a packaged version of Tomcat from somewhere other
than tomcat.apache.org?

- -chris

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJ5n59CaO5/Lv0PARAiBmAKC6PDQk+XYm9A/n7m0sTkBI0FvxRACgoMgX
DPyUs0fGKLPe2XajXc8rjCc=
=1uWi
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: migration from tomcat 4.1 to 5.5

[itay sahar]

i'm using the servlet-api.jar that come with tomcat 5.5 installation (
download from tomcat website).
it's should be 2.4. (according the spec).

my code is build in  eclipse with this jar version.
the problem is in runtime...
note: i don't want to get back to 1.4.
maybe i need to change somthing in the code:

this is the code display with the error mention above:

org.apache.jasper.JasperException: Exception in JSP: /index.jsp:5

2:   head
3:   /head
4:   body
5: jsp:forward page=main.jsf/
6:   /body
7: /html




On 10/30/07, Caldarale, Charles R [EMAIL PROTECTED] wrote:

  From: itay sahar [mailto:[EMAIL PROTECTED]
  Subject: Re: migration from tomcat 4.1 to 5.5
 
  3. But i still get the error: java.lang.NoSuchMethodError:
  javax.servlet.jsp.tagext.TagAttributeInfo
  when tring launch the application.

 There are three versions of the TagAttributeInfo constructor,
 differentiated by the arguments, implemented at different versions of
 the JSP spec.  Which one are you trying to use?  Your stack trace should
 tell you.

 - 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 start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

Re: migration from tomcat 4.1 to 5.5

[itay sahar]

running Tomcat by itself downloaded from tomcat.apache.org


On 10/30/07, itay sahar [EMAIL PROTECTED] wrote:

 i'm using the servlet-api.jar that come with tomcat 5.5 installation (
 download from tomcat website).
 it's should be 2.4. (according the spec).

 my code is build in  eclipse with this jar version.
 the problem is in runtime...
 note: i don't want to get back to 1.4.
 maybe i need to change somthing in the code:

 this is the code display with the error mention above:

 org.apache.jasper.JasperException: Exception in JSP: /index.jsp:5

 2:   head
 3:   /head
 4:   body
 5: jsp:forward page=main.jsf/
 6:   /body
 7: /html




 On 10/30/07, Caldarale, Charles R [EMAIL PROTECTED] wrote:
 
   From: itay sahar [mailto:[EMAIL PROTECTED]
   Subject: Re: migration from tomcat 4.1 to 5.5
  
   3. But i still get the error: java.lang.NoSuchMethodError:
   javax.servlet.jsp.tagext.TagAttributeInfo
   when tring launch the application.
 
  There are three versions of the TagAttributeInfo constructor,
  differentiated by the arguments, implemented at different versions of
  the JSP spec.  Which one are you trying to use?  Your stack trace should
  tell you.
 
  - 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 start a new topic, e-mail: users@tomcat.apache.org
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 

Re: Migration of Tomcat 3.2 to Tomcat 6.0

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Vishnu,

Parandhaman, Vishnu Prasad (STSD) wrote:
 Hi,
 Could anyone point out if there's a practical guide / tip to migrate
 from tomcat 3.2 to tomcat 6.0 ?
 ([has] anyone done [this] before)

I don't think anyone has ever made that jump before, so I don't think
there is such a guide out there. We'd appreciate any notes you take
during your upgrade, though!

 Basically there are lot of changes between the 3.2 and 6.0 versions in
 terms of structure and files. 

Yes. Although the servlet API is mostly (if not entirely) backward
compatible, your configuration will have to change dramatically.

 Moreover the older tomcat 3.2 was used along with apache (through
 mod_jk). 

mod_jk can still be used today. You may decide that you do not need it,
as Tomcat's ability to serve static content has improved quite a bit in
the, uh, 4 versions you're skipping.

 Now when we start with the new tomcat 6 as a HTTP  Web Server it throws
 up a lot of exceptions.

The first thing you have to do is throw out any server.xml files you may
have lying around from your old install. I tried upgrading from 4.1 to
5.5 by tweaking my old server.xml file, but it was a fool's errand. It's
much better to start with the server.xml file that is included with
Tomcat 6.0 and modify it until it meets your needs.

There is plenty of documentation on how to configure things in the new
versions on Tomcat. All of the documentation is available here:
http://tomcat.apache.org/tomcat-6.0-doc/index.html

The most useful things to read are probably going to be:

* Realms and AAA
* JDBC DataSources
* Connectors (if you choose to continue to use mod_jk)

That's about it. If you understood your 3.2 configuration, you should be
able to understand everything else just by reading the comments in the
server.xml file itself (there are LOTS of comments).

Hope that helps,
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG+mmC9CaO5/Lv0PARAgznAJwLLbvCuLfHv2ACx895Z3DB0DNVKQCfclfP
pYSeZw4rXJvbRrxyepW9UEs=
=KUod
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 5.5.20 to 6.0.10: parser issue on application deployment

[Rémy Maucherat]

On 3/3/07, Etienne Giraudy [EMAIL PROTECTED] wrote:

Shall this be considered as a regression as in that case tomcat
configuration is somehow altered by a web app?
(in that case I'll fill a bug in bugzilla))


I don't think there can be a change of behavior in this sort of thing
between TC 5.5 and 6.0.

Rémy

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 5.5.20 to 6.0.10: parser issue on application deployment

[Rémy Maucherat]

On 3/4/07, Etienne Giraudy [EMAIL PROTECTED] wrote:

I guess that the point that is questionnable here is the way the API
is designed: modifying the system property 'legal' and, AFAIK, it is
the only way to choose the parser implementation we want to use
(http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/parsers/SAXParser.html).

From that point of view, shouldn't Tomcat protect itself against
bad-designed standard APIs usage?


To see how standard and legal this usage is, you can try enabling
the security manager (the only way to control writing to system
properties - which are always JVM wide, so since Tomcat uses JAXP,
Tomcat cannot avoid being affected to some extent when a webapp
changes the parser factory - is to use the security manager) :) The
other problem is that this by defeinition won't behave the same in
different VMs (1.4, and same if you have a 5.0 VM with the
compatibility pack for TC 5.5).

You can send me a WAR to test however, I would be interested to look
at this alleged difference in behavior.

Rémy

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 5.5.20 to 6.0.10: parser issue on application deployment

[Etienne Giraudy]

To see how standard and legal this usage is, you can try enabling
the security manager (the only way to control writing to system
properties - which are always JVM wide, so since Tomcat uses JAXP,
Tomcat cannot avoid being affected to some extent when a webapp
changes the parser factory - is to use the security manager) :) The
other problem is that this by defeinition won't behave the same in
different VMs (1.4, and same if you have a 5.0 VM with the
compatibility pack for TC 5.5).


Not allowing the application to modify this system property is not an
option for me.



You can send me a WAR to test however, I would be interested to look
at this alleged difference in behavior.



I've filled a bug report to which I attached a simple web app for
reproducing the issue:
http://issues.apache.org/bugzilla/show_bug.cgi?id=41759


Etienne

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Migration from 5.5.20 to 6.0.10: parser issue on application deployment

[Caldarale, Charles R]

 From: Etienne Giraudy [mailto:[EMAIL PROTECTED] 
 Subject: Migration from 5.5.20 to 6.0.10: parser issue on 
 application deployment
 
 One of the web app running on that server includes 
 xercesImpl.jar and use it through modifying the system
 property javax.xml.parsers.SAXParserFactory.

That behavior looks rather questionable to me.  Having a webapp modify a
global property that has the potential of affecting everything running
in that JVM - including other webapps and the container - seems like a
very risky strategy, raising serious compatibility and operability
issues.  The fact that it happened to work in one version of one
container doesn't imply that it's an appropriate thing to do.

 - 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 5.5.20 to 6.0.10: parser issue on application deployment

[Etienne Giraudy]

On 3/3/07, Caldarale, Charles R [EMAIL PROTECTED] wrote:

 From: Etienne Giraudy [mailto:[EMAIL PROTECTED]
 Subject: Migration from 5.5.20 to 6.0.10: parser issue on
 application deployment

 One of the web app running on that server includes
 xercesImpl.jar and use it through modifying the system
 property javax.xml.parsers.SAXParserFactory.

That behavior looks rather questionable to me.  Having a webapp modify a
global property that has the potential of affecting everything running
in that JVM - including other webapps and the container - seems like a
very risky strategy, raising serious compatibility and operability
issues.  The fact that it happened to work in one version of one
container doesn't imply that it's an appropriate thing to do.


I guess that the point that is questionnable here is the way the API
is designed: modifying the system property 'legal' and, AFAIK, it is
the only way to choose the parser implementation we want to use
(http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/parsers/SAXParser.html).


From that point of view, shouldn't Tomcat protect itself against

bad-designed standard APIs usage?

Etienne

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from jk2 to jk, problems with uri context

[Rainer Jung]

What about changing

worker.worker1.mount=/foo/* foo

to

worker.worker1.mount=/foo/* /foo

Regards,

Rainer

james edwards schrieb:
 I am moving to jk (1.2.18) from jk2  am having problems with the
 workers.properties file. I have separate apache and tomcat servers. Here is
 my working jk2 (workers2.properties) config:
 
 [logger]
 level=ERROR
 [config:]
 file=${serverRoot}/conf/workers2.properties
 debug=0
 debugEnv=0
 [uriMap:]
 info=Maps the requests. Options: debug
 debug=0
 [logger.file:0]
 level=ERROR
 file=${serverRoot}/logs/jk2.log
 [shm:]
 info=Scoreboard. Required for reconfiguration and status with multiprocess
 servers
 file=${serverRoot}/logs/jk2.shm
 size=100
 debug=0
 disabled=0
 [workerEnv:]
 info=Global server options
 timing=1
 debug=0
 [channel.socket:whatever.whoever.com:]
 host=whatever.whoever.com
 port=
 info=Ajp13 forwarding over socket
 debug=0
 tomcatId=myTomcat
 [ajp13:whatever.whoever.com:]
 channel=channel.socket:myTomcat
 [channel.jni:jni]
 info=The jni channel, used if tomcat is started inprocess
 [status:]
 info=Status worker, displays runtime informations
 [vm:]
 info=Parameters used to load a JVM in the server process
 classpath=${CATALINA_HOME}/bin/tomcat-jni.jar
 classpath=${CATALINA_HOME}/server/lib/commons-logging.jar
 OPT=-Dtomcat.home=${CATALINA_HOME}
 OPT=-Dcatalina.home=${CATALINA_HOME}
 OPT=-Xmx768M
 disabled=1
 [uri:/foo/*]
 context=/foo
 debug=0
 
 
 I am trying to get a basic config working before I convert the rest from
 the
 old config. I cannot get
 the uri part to work. Here is the config I am running (workers.properties):
 
 
 worker.list= worker1
 worker.worker1.type=ajp13
 worker.worker1.host=whatever.whoever.com
 worker.worker1.port=
 worker.worker1.connection_pool_size=10
 worker.worker1.connection_pool_timeout=600
 worker.worker1.socket_keepalive=1
 worker.worker1.mount=/foo/* foo
 
 Here are the error logs from apache:
 
 [Fri Sep 01 14:37:06 2006] [notice] Graceful restart requested, doing
 restart
 [Fri Sep 01 14:37:06 2006] [notice] Apache/2.0.55 (Unix) mod_ssl/2.0.55
 OpenSSL/0.9.7a PHP/5.1.2 mod_jk/1.2.18 configured -- resuming normal
 operations
 [Fri Sep 01 14:37:17 2006] [error] [client 222.33.45.67] File does not
 exist: /var/www/html/foo, referer: http://noone.whoever.com
 
 The jk logs:
 
 [Fri Sep 01 15:20:53 2006] [21388:34496] [error]
 uri_worker_map_add::jk_uri_worker_map.c (322): invalid context foo
 [Fri Sep 01 15:20:53 2006] [21388:34496] [error]
 wc_create_worker::jk_worker.c (183): validate failed for worker1
 [Fri Sep 01 15:20:53 2006] [21388:34496] [error]
 build_worker_map::jk_worker.c (256): failed to create worker worker1
 [Fri Sep 01 15:20:53 2006] [21389:34496] [error]
 uri_worker_map_add::jk_uri_worker_map.c (322): invalid context foo
 [Fri Sep 01 15:20:53 2006] [21389:34496] [error]
 wc_create_worker::jk_worker.c (183): validate failed for worker1
 [Fri Sep 01 15:20:53 2006] [21389:34496] [error]
 build_worker_map::jk_worker.c (256): failed to create worker worker1
 
 I have tried several variations with the / and * syntax here:
 worker.worker1.mount=/foo/* foo
 
 With no luck. Can someone point me in the right direction ?
 
 

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from jk2 to jk, problems with uri context

[brian bay]

I have this working with tomcat 5.5.17 and apache2, jk1

You need mod_jk.so in apache/modules..for me
/usr/lib/apache2/modules/mod_jk.so

In apache home ---create workers.properties

workers.tomcat.home=/path/to/tomcat
ps=/
workers.list=worker1
worker.ajp13.type=ajp13
worker.ajp13.host=whatever.whoever.com
worker.ajp13.port=8009


In httpd.conf or apache2.conf---
LoadModule jk_module /usr/lib/apache2/modules/mod_jk.so
JkWorkersFile /path/to/apache/workers.properties

in virtual-host section of apache
JkMount /foo*  worker1  #worker1 defined in workers.properties.
JkMount /*.jsp worker1 #if you do http://wherever.whoever.com/index.jsp
   #you will bring up the tomcat homepage



On the tomcat end, there is a small amount of config in server.xml


   Listener className=org.apache.jk.config.ApacheConfig
modJk=/usr/lib/apache2/modules/mod_jk.so
workersConfig=/etc/apache2/workers.properties/


  Connector port=8009
redirectPort=8443
connectionTimeout=-1
  protocol=AJP/1.3
  /Connector

make sure to stop and restart apache..

hope this helps...




On 9/1/06, james edwards [EMAIL PROTECTED] wrote:


I am moving to jk (1.2.18) from jk2  am having problems with the
workers.properties file. I have separate apache and tomcat servers. Here
is
my working jk2 (workers2.properties) config:

[logger]
level=ERROR
[config:]
file=${serverRoot}/conf/workers2.properties
debug=0
debugEnv=0
[uriMap:]
info=Maps the requests. Options: debug
debug=0
[logger.file:0]
level=ERROR
file=${serverRoot}/logs/jk2.log
[shm:]
info=Scoreboard. Required for reconfiguration and status with multiprocess
servers
file=${serverRoot}/logs/jk2.shm
size=100
debug=0
disabled=0
[workerEnv:]
info=Global server options
timing=1
debug=0
[channel.socket:whatever.whoever.com:]
host=whatever.whoever.com
port=
info=Ajp13 forwarding over socket
debug=0
tomcatId=myTomcat
[ajp13:whatever.whoever.com:]
channel=channel.socket:myTomcat
[channel.jni:jni]
info=The jni channel, used if tomcat is started inprocess
[status:]
info=Status worker, displays runtime informations
[vm:]
info=Parameters used to load a JVM in the server process
classpath=${CATALINA_HOME}/bin/tomcat-jni.jar
classpath=${CATALINA_HOME}/server/lib/commons-logging.jar
OPT=-Dtomcat.home=${CATALINA_HOME}
OPT=-Dcatalina.home=${CATALINA_HOME}
OPT=-Xmx768M
disabled=1
[uri:/foo/*]
context=/foo
debug=0


I am trying to get a basic config working before I convert the rest from
the
old config. I cannot get
the uri part to work. Here is the config I am running (workers.properties
):


worker.list= worker1
worker.worker1.type=ajp13
worker.worker1.host=whatever.whoever.com
worker.worker1.port=
worker.worker1.connection_pool_size=10
worker.worker1.connection_pool_timeout=600
worker.worker1.socket_keepalive=1
worker.worker1.mount=/foo/* foo

Here are the error logs from apache:

[Fri Sep 01 14:37:06 2006] [notice] Graceful restart requested, doing
restart
[Fri Sep 01 14:37:06 2006] [notice] Apache/2.0.55 (Unix) mod_ssl/2.0.55
OpenSSL/0.9.7a PHP/5.1.2 mod_jk/1.2.18 configured -- resuming normal
operations
[Fri Sep 01 14:37:17 2006] [error] [client 222.33.45.67] File does not
exist: /var/www/html/foo, referer: http://noone.whoever.com

The jk logs:

[Fri Sep 01 15:20:53 2006] [21388:34496] [error]
uri_worker_map_add::jk_uri_worker_map.c (322): invalid context foo
[Fri Sep 01 15:20:53 2006] [21388:34496] [error]
wc_create_worker::jk_worker.c (183): validate failed for worker1
[Fri Sep 01 15:20:53 2006] [21388:34496] [error]
build_worker_map::jk_worker.c (256): failed to create worker worker1
[Fri Sep 01 15:20:53 2006] [21389:34496] [error]
uri_worker_map_add::jk_uri_worker_map.c (322): invalid context foo
[Fri Sep 01 15:20:53 2006] [21389:34496] [error]
wc_create_worker::jk_worker.c (183): validate failed for worker1
[Fri Sep 01 15:20:53 2006] [21389:34496] [error]
build_worker_map::jk_worker.c (256): failed to create worker worker1

I have tried several variations with the / and * syntax here:
worker.worker1.mount=/foo/* foo

With no luck. Can someone point me in the right direction ?


--
James H. Edwards
Senior Network Systems Administrator
Judicial Information Division
[EMAIL PROTECTED]

Re: Migration from 1.0 to 1.2.x: Gotchas?

[Wendy Smoak]

On 1/14/06, Venkat  Radha Venkataramanan [EMAIL PROTECTED] wrote:

 I have an Pharma J2EE application developed using the Struts framework
 running on a weblogic 6.0 server (yes, and it's only 3 years old!).

 We are upgrading to weblogic 9.0 since 6.0 is no longer supported by BEA.
 And, I learnt that 9.0 supports only Struts 1.2.x.

 Does anybody gone through the exercise of migrating from 1.0 and 1.2? Are
 there pearls of wisdom to be shared? Or, is it just a tedious task of
 re-compiling all the JSP pages?

You'll probably want to ask on the Struts list instead of Tomcat. :)
   http://struts.apache.org/mail.html#Subscribing

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration from 1.0 to 1.2.x: Gotchas?

[Bill Barker]

Wendy Smoak [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
On 1/14/06, Venkat  Radha Venkataramanan [EMAIL PROTECTED] 
wrote:

 I have an Pharma J2EE application developed using the Struts framework
 running on a weblogic 6.0 server (yes, and it's only 3 years old!).

 We are upgrading to weblogic 9.0 since 6.0 is no longer supported by BEA.
 And, I learnt that 9.0 supports only Struts 1.2.x.

 Does anybody gone through the exercise of migrating from 1.0 and 1.2? Are
 there pearls of wisdom to be shared? Or, is it just a tedious task of
 re-compiling all the JSP pages?

You'll probably want to ask on the Struts list instead of Tomcat. :)
   http://struts.apache.org/mail.html#Subscribing


Wendy's suggestion is probably your best bet.  I know it was a huge commit 
to move Tomcat's admin webapp to 1.2.x (but mostly mindless changes :). 
AIRC, it was mostly renaming the 'process' method to 'execute', so you'll 
hit it soon enough if you re-compile your app against struts-1.2 with 
deprecation on.

It's probably going to be an even bigger headache to move the admin webapp 
to struts-2, but I wouldn't know now since my Gump early warning system 
hasn't built struts-taglib in months ;-).

--
Wendy 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration

[Oto Bossert]

Yoo,

We need more info! At least the stack trace and the code it is pointing
to...

Greetings O.

On 1/6/06, Abh N [EMAIL PROTECTED] wrote:

   Hi,

   We are migrating our applications from Tomcat to Websphere server.
   We are getting some issues (in Websphere )with code which used to work
 fine in Tomcat.
   Server is not recognizing IOException in jsp code. I am now putting
 import java.io.*  to resolve this.
   Am not able to understand how it used to work in Tomcat env without
 error.
   Can anybody give some pointers regarding this.

   Thanks





 Send instant messages to your online friends http://in.messenger.yahoo.com

Re: Migration

[David Delbecq]

Hi Abh,

Out of curiosity i took a look a at tomcat generated jsp class.
(tomcat: 5.5.7)

import directive found in .java file generated from .jsp:

import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;

No import directive were present in original .jsp and, as you see, there is no 
java.io.* class imported by tomcat.
All IOException which may occur during processing are managed with their full 
package:

  public void _jspService(HttpServletRequest request, HttpServletResponse 
response)
throws java.io.IOException, ServletException {

Could you send us a demo .jsp that used to work with tomcat but not websphere, 
and specify tomcat version used.


Le Vendredi 6 Janvier 2006 10:51, Abh N a écrit :
   Hi,

   We are migrating our applications from Tomcat to Websphere server.
   We are getting some issues (in Websphere )with code which used to work fine 
 in Tomcat.
   Server is not recognizing IOException in jsp code. I am now putting import 
 java.io.*  to resolve this.
   Am not able to understand how it used to work in Tomcat env without error.
   Can anybody give some pointers regarding this.

   Thanks

 
 
 
 
 Send instant messages to your online friends http://in.messenger.yahoo.com 

-- 
David Delbecq
Royal Meteorological Institute of Belgium

-
Pingouins dans les champs, hiver méchant

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Migration

[Tim Funk]

The servlet spec requires that the following packages are imported in your jsp:
javax.servlet.*;
javax.servlet.http.*;
javax.servlet.jsp.*;

Other vendors in the past have also done things such as also include
import java.util.*
import java.io.*

These actions are not mentioned by the spec and create non portable code.

If your app is using the 2.4 servlet spec, you can use a preclude. Add this 
to web.xml. (See google for more details)

jsp-property-group
  url-pattern/*.jsp/url-pattern
  include-prelude
 /WEB-INF/jsps/include/preclude-common-imports.jspf
  /include-prelude
/jsp-property-group

Where preclude-common-imports.jspf is a one liner
%@ page import='java.io.*' %


-Tim


Abh N wrote:

  Hi,
   
  We are migrating our applications from Tomcat to Websphere server.

  We are getting some issues (in Websphere )with code which used to work fine 
in Tomcat.
  Server is not recognizing IOException in jsp code. I am now putting import 
java.io.*  to resolve this.
  Am not able to understand how it used to work in Tomcat env without error.
  Can anybody give some pointers regarding this.
   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]