You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Bo <bo...@bochen.ch> on 2018/12/18 05:10:57 UTC
why can't i login to tomcat7 status page from clean install zip
I do a clean install of the tomcat7 folder and rename it to just tomcat, and without changing ANYTHING and without adding any old files yet, I start the tomcat service and try to get to the status page, but this time it won't even let me log into anything at all either, no matter what I try.
This is the tomcat7 fresh download links I used
https://tomcat.apache.org/download-70.cgi
http://apache.mirrors.tds.net/tomcat/tomcat-7/v7.0.92/bin/apache-tomcat-7.0.92-windows-x86.zip
https://tomcat.apache.org/tomcat-7.0-doc/appdev/deployment.html
I unzip the apache-tomcat-7.0.92-windows-x86.zip <http://apache.mirrors.tds.net/tomcat/tomcat-7/v7.0.92/bin/apache-tomcat-7.0.92-windows-x86.zip> and put it in the root of a custom web app that I have and then I use the service.bat install to trigger the services install, this is on windows server so I start it up in services.msc
I can go to localhost fine, but it won't let me login
I checked the tomcat user xml file a trillion times to triple check to make sure I have it right, but no matter what, even after multiple restarts, it won't even let me login to the status page!!!!!
401 Unauthorized
You are not authorized to view this page. If you have not changed any configuration files, please examine the file conf/tomcat-users.xml in your installation. That file must contain the credentials to let you use this webapp.
For example, to add the manager-gui role to a user named tomcat with a password of s3cret, add the following to the config file listed above.
<role rolename="manager-gui"/>
<user username="tomcat" password="s3cret" roles="manager-gui"/>
Note that for Tomcat 7 onwards, the roles required to use the manager application were changed from the single manager role to the following four roles. You will need to assign the role(s) required for the functionality you wish to access.
manager-gui - allows access to the HTML GUI and the status pages
manager-script - allows access to the text interface and the status pages
manager-jmx - allows access to the JMX proxy and the status pages
manager-status - allows access to the status pages only
The HTML interface is protected against CSRF but the text and JMX interfaces are not. To maintain the CSRF protection:
Users with the manager-gui role should not be granted either the manager-script or manager-jmx roles.
If the text or jmx interfaces are accessed through a browser (e.g. for testing since these interfaces are intended for tools not humans) then the browser must be closed afterwards to terminate the session.
For more information - please see the Manager App HOW-TO.
Re: why can't i login to tomcat7 status page from clean install zip
Posted by Mark Thomas <ma...@apache.org>.
On 18/12/2018 13:46, Bo wrote:
> apologize for what?
Your statement that "tomcat is horribly broken and buggy"
who did i insult
Everyone who has contributed to Tomcat.
Which, by the way, is provided to you free of charge. As is the support
you are receiving on this list.
> i stand by my claim,
Really? You haven't looked at the catalina.yyyy-mm-dd.log file yet then.
I strongly suggest that you do so. After all, what is the point of
asking for help (even if you aren't very polite when you do so) if you
aren't going to then take the help when it is offered?
> seems thousands people having this issue, if it was
> intuitively and well designed, this wouldnt be a thing now would it
> https://www.centos.org/forums/viewtopic.php?t=46150
As that thread makes clear, some folks don't read instructions. Those
instructions are:
- in the file that needs to be edited
- right next to the part that needs to be edited
- in a dedicated comment block to separate them from other comments
in the file.
And when those instructions aren't followed, there will be a nice
message in the log file explaining what the problem is. As you will find
when you look at the log files on your system.
Still waiting for that apology...
Mark
>
>
> On Tue, Dec 18, 2018, at 7:15 AM, Mark Thomas wrote:
>> On 18/12/2018 12:55, Bo wrote:
>>> i tested every possible combination.
>>>
>>> anyone can try it themselves
>>> i listed the steps to duplicate this already
>>> its 100 percent generic
>>>
>>> tomcat is horribly broken and buggy
>>> it wont even allow me to login
>>
>> When things go wrong it is usually a good idea to assume that you have> made the error rather than throwing around insults - especially
>> when you> are relying on the people you are insulting to help you.
>>
>> I suggest you take a look at the logs.
>> catalina.yyyy-mm-dd.log should be illuminating.
>>
>> The error message for the first stack trace that appears in that file> after Tomcat starts should be sufficient.
>>
>> When you are ready to apologise for the "tomcat is horribly broken and> buggy" comment, an apology on this thread will be fine.
>>
>> Mark
>>
>>
>>
>>>
>>>
>>> On Tue, Dec 18, 2018, at 1:00 AM, Bob Hall wrote:
>>>> Bo,
>>>> On Monday, December 17, 2018, 9:49:34 PM PST, Bo <bo...@bochen.ch>
>>>> wrote:>>>>>> here is screenshot
>>>>>
>>>>> I just tried again still no working\
>>>>>
>>>>> . https://i.imgur.com/8bQH2YB.png
>>>>
>>>> At the risk of stating the obvious, your screenshot shows: - a tomcat->>> users.xml file with three usernames: dog, god, and role1.> - a
>>>> Tomcat login page with username admin>>> Did you try logging in with username god or adding a user with
>>>> username admin?> - Bob
>>>>
>>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: why can't i login to tomcat7 status page from clean install zip
Posted by Bo <bo...@bochen.ch>.
apologize for what? who did i insult
i stand by my claim, seems thousands people having this issue, if it was
intuitively and well designed, this wouldnt be a thing now would it
https://www.centos.org/forums/viewtopic.php?t=46150
On Tue, Dec 18, 2018, at 7:15 AM, Mark Thomas wrote:
> On 18/12/2018 12:55, Bo wrote:
>> i tested every possible combination.
>>
>> anyone can try it themselves
>> i listed the steps to duplicate this already
>> its 100 percent generic
>>
>> tomcat is horribly broken and buggy
>> it wont even allow me to login
>
> When things go wrong it is usually a good idea to assume that you have> made the error rather than throwing around insults - especially
> when you> are relying on the people you are insulting to help you.
>
> I suggest you take a look at the logs.
> catalina.yyyy-mm-dd.log should be illuminating.
>
> The error message for the first stack trace that appears in that file> after Tomcat starts should be sufficient.
>
> When you are ready to apologise for the "tomcat is horribly broken and> buggy" comment, an apology on this thread will be fine.
>
> Mark
>
>
>
>>
>>
>> On Tue, Dec 18, 2018, at 1:00 AM, Bob Hall wrote:
>>> Bo,
>>> On Monday, December 17, 2018, 9:49:34 PM PST, Bo <bo...@bochen.ch>
>>> wrote:>>>>>> here is screenshot
>>>>
>>>> I just tried again still no working\
>>>>
>>>> . https://i.imgur.com/8bQH2YB.png
>>>
>>> At the risk of stating the obvious, your screenshot shows: - a tomcat->>> users.xml file with three usernames: dog, god, and role1.> - a
>>> Tomcat login page with username admin>>> Did you try logging in with username god or adding a user with
>>> username admin?> - Bob
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: why can't i login to tomcat7 status page from clean install zip
Posted by Mark Thomas <ma...@apache.org>.
On 18/12/2018 12:55, Bo wrote:
> i tested every possible combination.
>
> anyone can try it themselves
> i listed the steps to duplicate this already
> its 100 percent generic
>
> tomcat is horribly broken and buggy
> it wont even allow me to login
When things go wrong it is usually a good idea to assume that you have
made the error rather than throwing around insults - especially when you
are relying on the people you are insulting to help you.
I suggest you take a look at the logs.
catalina.yyyy-mm-dd.log should be illuminating.
The error message for the first stack trace that appears in that file
after Tomcat starts should be sufficient.
When you are ready to apologise for the "tomcat is horribly broken and
buggy" comment, an apology on this thread will be fine.
Mark
>
>
> On Tue, Dec 18, 2018, at 1:00 AM, Bob Hall wrote:
>> Bo,
>> On Monday, December 17, 2018, 9:49:34 PM PST, Bo <bo...@bochen.ch> wrote:>
>>> > here is screenshot
>>>
>>> I just tried again still no working\
>>>
>>> . https://i.imgur.com/8bQH2YB.png
>>
>> At the risk of stating the obvious, your screenshot shows: - a tomcat-
>> users.xml file with three usernames: dog, god, and role1.> - a Tomcat login page with username admin
>> Did you try logging in with username god or adding a user with
>> username admin?> - Bob
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: why can't i login to tomcat7 status page from clean install zip
Posted by Bo <bo...@bochen.ch>.
i tested every possible combination.
anyone can try it themselves
i listed the steps to duplicate this already
its 100 percent generic
tomcat is horribly broken and buggy
it wont even allow me to login
On Tue, Dec 18, 2018, at 1:00 AM, Bob Hall wrote:
> Bo,
> On Monday, December 17, 2018, 9:49:34 PM PST, Bo <bo...@bochen.ch> wrote:>
> > > here is screenshot
>>
>> I just tried again still no working\
>>
>> . https://i.imgur.com/8bQH2YB.png
>
> At the risk of stating the obvious, your screenshot shows: - a tomcat-
> users.xml file with three usernames: dog, god, and role1.> - a Tomcat login page with username admin
> Did you try logging in with username god or adding a user with
> username admin?> - Bob
>
>
Re: why can't i login to tomcat7 status page from clean install zip
Posted by Bob Hall <rf...@yahoo.com.INVALID>.
Bo,
On Monday, December 17, 2018, 9:49:34 PM PST, Bo <bo...@bochen.ch> wrote:
> > here is screenshot
>
> I just tried again still no working\
>
>. https://i.imgur.com/8bQH2YB.png
At the risk of stating the obvious, your screenshot shows: - a tomcat-users.xml file with three usernames: dog, god, and role1.
- a Tomcat login page with username admin
Did you try logging in with username god or adding a user with username admin?
- Bob
Re: Migrating app from Tomcat5.5.17 to Tomcat7, getting Description
The origin server did not find a current representation for the target
resource
Posted by Mark Thomas <ma...@apache.org>.
Still ignoring the original question due to the thread hijacking.
As much as I'd like to leave this thread alone, here is some more
factual correction for the archives...
If you don't want/need a Windows service wrapper and you have a 64-bit
JVM for your OS that meets the minimum Java version for the version of
Tomcat you want to use, any Tomcat version will run quite happily on
that 64-bit JVM.
If you want to run a 64-bit JVM as a Windows service then the first
version of Tomcat that ships with all the bits you need is 5.5.28. All
subsequent versions also include everything you need.
You can get Tomcat versions before 5.5.28 running as a 64-bit Windows
service, it just requires a little manual configuration.
On 20/12/2018 13:48, Bo wrote:
> thats not true, i used winmerge to compare 32bit vs 64bit tomcat6, two
> changes are the tomcat6.exe is different as well as a .dll or something
> within the same location.since 32bit tomcat5 can only see and only use and only set 1024m, else
> service doesnt even start in services.msc, only option is to go to
> 64bit.
Not correct. a 32-bit process can see up to 2 GB by default and up to
3GB if you configure Windows with the right boot time options (that
takes me back). The Java heap that is available is going to vary based
on multiple factors. If the process has 2GB available then a maximum
heap of 1GB is a little on the low side (I'd normally expect a little
over 1.5GB) but it does depend what other options you are starting the
JVM with.
> tomcat6 has zips of 32bit vs 64bit, not true for tomcat5. so
> while 32bit tomcat5 runs under a 64bit os, thats not the definition of
> supporting 64bit
It is correct that Tomcat 5 does not have separate 32-bit and 64-bit
distributions. However...
apache-tomcat-5.5.28.zip contains:
/bin/tomcat5.exe - 32-bit service wrapper (for 32-bit JVM)
/bin/tomcat5w.exe - 32-bit service manager (for 32 or 64-bit JVM)
/bin/procrun/amd64/tomcat5.exe - 64-bit service wrapper (for 64-bit JVM)
/bin/procrun/ia64/tomcat5.exe - 64-bit service wrapper (for 64-bit JVM)
So Tomcat 5 (from 5.5.28) does contain everything required to run as a
64-bit Windows service (on Itanium or Intel/AMD).
The separate 32-bit and 64-bit packages were added to make it easier for
users so they did not have to copy the right version of tomcat6.exe into
the bin directory. They just downloaded the right zip for their
architecture and the right tomcat6.exe was already in place.
Mark
>
>
>
> On Thu, Dec 20, 2018, at 7:26 AM, Olaf Kock wrote:
>>
>> On 20.12.18 14:04, Bo wrote:
>>> there is no 64bit for v5, but i see one for v6 and above
>>>
>> There doesn't need to be one. The installer just needs to find the 64> bit JRE (or JDK, can't remember when this requirement was changed) and> use it to start tomcat, e.g. for the service.
>>
>> Tomcat itself, apart from optional native libraries, is pure Java and> architecturally doesn't care about the underlying bitsize. It
>> just needs> to work with the different limitations that come with the various
>> options, e.g. lower max memory options.
>>
>> My 2 cent on the rest of the thread:
>>
>> You already got Mark's attention. If you're hoping that you get more
>> qualified answers than from him, carry on and upset him. My prediction> is though, that you'll get a solution to your problem sooner
>> (or at all)> when you play nice and don't assume that everybody (or Mark in
>> particular) is working against you. Follow his suggestions in
>> the other> mails on the thread - if they help: Thank him and apologize. If they
>> don't help: Provide what he has asked for (and apologize anyway).
>>
>> Unless you're just interested in trolling. Then you'll rather get a
>> first row seat on everybody's ignore list. But until then, let's not
>> discuss what has been delivered in a Tomcat version that saw
>> its end of> life in 2012.
>>
>>
>>
>> ---------------------------------------------------------------------> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Migrating app from Tomcat5.5.17 to Tomcat7,
getting Description The origin server did not find a current
representation for the target resource
Posted by Bo <bo...@bochen.ch>.
thats not true, i used winmerge to compare 32bit vs 64bit tomcat6, two
changes are the tomcat6.exe is different as well as a .dll or something
within the same location.since 32bit tomcat5 can only see and only use and only set 1024m, else
service doesnt even start in services.msc, only option is to go to
64bit. tomcat6 has zips of 32bit vs 64bit, not true for tomcat5. so
while 32bit tomcat5 runs under a 64bit os, thats not the definition of
supporting 64bit
On Thu, Dec 20, 2018, at 7:26 AM, Olaf Kock wrote:
>
> On 20.12.18 14:04, Bo wrote:
>> there is no 64bit for v5, but i see one for v6 and above
>>
> There doesn't need to be one. The installer just needs to find the 64> bit JRE (or JDK, can't remember when this requirement was changed) and> use it to start tomcat, e.g. for the service.
>
> Tomcat itself, apart from optional native libraries, is pure Java and> architecturally doesn't care about the underlying bitsize. It
> just needs> to work with the different limitations that come with the various
> options, e.g. lower max memory options.
>
> My 2 cent on the rest of the thread:
>
> You already got Mark's attention. If you're hoping that you get more
> qualified answers than from him, carry on and upset him. My prediction> is though, that you'll get a solution to your problem sooner
> (or at all)> when you play nice and don't assume that everybody (or Mark in
> particular) is working against you. Follow his suggestions in
> the other> mails on the thread - if they help: Thank him and apologize. If they
> don't help: Provide what he has asked for (and apologize anyway).
>
> Unless you're just interested in trolling. Then you'll rather get a
> first row seat on everybody's ignore list. But until then, let's not
> discuss what has been delivered in a Tomcat version that saw
> its end of> life in 2012.
>
>
>
> ---------------------------------------------------------------------> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: Migrating app from Tomcat5.5.17 to Tomcat7, getting Description
The origin server did not find a current representation for the target
resource
Posted by Olaf Kock <to...@olafkock.de>.
On 20.12.18 14:04, Bo wrote:
> there is no 64bit for v5, but i see one for v6 and above
>
There doesn't need to be one. The installer just needs to find the 64
bit JRE (or JDK, can't remember when this requirement was changed) and
use it to start tomcat, e.g. for the service.
Tomcat itself, apart from optional native libraries, is pure Java and
architecturally doesn't care about the underlying bitsize. It just needs
to work with the different limitations that come with the various
options, e.g. lower max memory options.
My 2 cent on the rest of the thread:
You already got Mark's attention. If you're hoping that you get more
qualified answers than from him, carry on and upset him. My prediction
is though, that you'll get a solution to your problem sooner (or at all)
when you play nice and don't assume that everybody (or Mark in
particular) is working against you. Follow his suggestions in the other
mails on the thread - if they help: Thank him and apologize. If they
don't help: Provide what he has asked for (and apologize anyway).
Unless you're just interested in trolling. Then you'll rather get a
first row seat on everybody's ignore list. But until then, let's not
discuss what has been delivered in a Tomcat version that saw its end of
life in 2012.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Migrating app from Tomcat5.5.17 to Tomcat7, getting Description
The origin server did not find a current representation for the target
resource
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 20.12.2018 14:04, Bo wrote:
> there is no 64bit for v5, but i see one for v6 and above
That may be the case, but it has nothing to do with your problem.
I think that you may be a bit confused as to what tomcat is, and how it runs under Windows.
Maybe you should read this first : https://wiki.apache.org/tomcat/FAQ/Windows#Q11
And then, when you have calmed down and have really understood what that means, re-read
Mark's and others previous answers, and you may understand what they mean.
And if you still do not understand,
- compose and send a /new/ messages to the list, with a new subject, to ask your question.
Do not just hit "reply" on some other message (not even this one).
(If you do not understand this part, see :
https://www.urbandictionary.com/define.php?term=Thread%20Hijacking)
- do not start shouting your mouth about things that you do not understand, and affirm
things that are technically not true.
That upsets other people, in particular the people who donate their time to create tomcat
and provide it to you for free, and the people who donate their time to answer your
questions on this list, also for free.
>
>
>
>
> On Thu, Dec 20, 2018, at 3:18 AM, Mark Thomas wrote:
>> Ignoring most of this due to thread hijacking but correcting factual
>> errors for the benefit of the archives.
>>
>> On 20/12/2018 06:52, Bo wrote:
>>
>> okay tomcat 6 is earliest/latest version that supports 64bit...
>>
>>
>> The above statement is incorrect.
>>
>> Any version of Tomcat will run on either a 32-bit or 64-bit JVM
>> providing that that JVM meets the minimum Java version required by the
>> version used of Tomcat.
>>
>> The Windows installer has supported 64-bit since 5.5.28. So the Windows
>> installer provided by all current versions support 64-bit JVMs.
>>
>> <snip/>
>>
>> Long story short, next I'm trying to migrate from Tomcat 5.5.17 to Tomcat7. I
>> see that the officially supported route is two paths, migrating/updating 1 level
>> at a time, from Tomcat5.5 to Tomcat 6 and then from Tomcat6 to Tomcat7.
>>
>>
>> The above statement is incorrect.
>>
>> The Tomcat community does not require migration one major version at a
>> time. If anything, we'd recommend the exact opposite - upgrade to the
>> latest available version.
>>
>> Migration of any well written web application from 5.5.x to 9.0.x is
>> trivial.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> <ma...@tomcat.apache.org>
>> For additional commands, e-mail: users-help@tomcat.apache.org
>> <ma...@tomcat.apache.org>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Migrating app from Tomcat5.5.17 to Tomcat7,
getting Description The origin server did not find a current
representation for the target resource
Posted by Bo <bo...@bochen.ch>.
there is no 64bit for v5, but i see one for v6 and above
On Thu, Dec 20, 2018, at 3:18 AM, Mark Thomas wrote:
> Ignoring most of this due to thread hijacking but correcting factual
> errors for the benefit of the archives.
>
> On 20/12/2018 06:52, Bo wrote:
>> okay tomcat 6 is earliest/latest version that supports 64bit...
>
> The above statement is incorrect.
>
> Any version of Tomcat will run on either a 32-bit or 64-bit JVM
> providing that that JVM meets the minimum Java version required by the> version used of Tomcat.
>
> The Windows installer has supported 64-bit since 5.5.28. So the
> Windows> installer provided by all current versions support 64-bit JVMs.
>
> <snip/>
>
>>> Long story short, next I'm trying to migrate from Tomcat 5.5.17 to
>>> Tomcat7. I see that the officially supported route is two paths,
>>> migrating/updating 1 level at a time, from Tomcat5.5 to Tomcat 6 and
>>> then from Tomcat6 to Tomcat7.>
> The above statement is incorrect.
>
> The Tomcat community does not require migration one major version at a> time. If anything, we'd recommend the exact opposite - upgrade to the> latest available version.
>
> Migration of any well written web application from 5.5.x to 9.0.x is
> trivial.
>
> Mark
>
> ---------------------------------------------------------------------> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: Migrating app from Tomcat5.5.17 to Tomcat7, getting Description
The origin server did not find a current representation for the target
resource
Posted by Mark Thomas <ma...@apache.org>.
Ignoring most of this due to thread hijacking but correcting factual
errors for the benefit of the archives.
On 20/12/2018 06:52, Bo wrote:
> okay tomcat 6 is earliest/latest version that supports 64bit...
The above statement is incorrect.
Any version of Tomcat will run on either a 32-bit or 64-bit JVM
providing that that JVM meets the minimum Java version required by the
version used of Tomcat.
The Windows installer has supported 64-bit since 5.5.28. So the Windows
installer provided by all current versions support 64-bit JVMs.
<snip/>
>> Long story short, next I'm trying to migrate from Tomcat 5.5.17 to Tomcat7. I see that the officially supported route is two paths, migrating/updating 1 level at a time, from Tomcat5.5 to Tomcat 6 and then from Tomcat6 to Tomcat7.
The above statement is incorrect.
The Tomcat community does not require migration one major version at a
time. If anything, we'd recommend the exact opposite - upgrade to the
latest available version.
Migration of any well written web application from 5.5.x to 9.0.x is
trivial.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Migrating app from Tomcat5.5.17 to Tomcat7, getting Description The origin server did not find a current representation for the target resource
Posted by Bo <bo...@bochen.ch>.
okay tomcat 6 is earliest/latest version that supports 64bit...
so instead of going from 5.5.17 to 7, when attemting to just go from 5.5.17 to 64bit version of 6, it crashes ... without the program it starts but adding it gives error like
Dec 19, 2018 10:48:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.2.10 using APR version 1.5.2.
Dec 19, 2018 10:48:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Dec 19, 2018 10:48:57 PM org.apache.tomcat.util.digester.Digester startElement
SEVERE: Begin event threw error
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.apache.coyote.ajp.AjpAprProtocol.<clinit>(AjpAprProtocol.java:52)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at org.apache.catalina.connector.Connector.<init>(Connector.java:84)
at org.apache.catalina.startup.ConnectorCreateRule.begin(ConnectorCreateRule.java:55)
at org.apache.tomcat.util.digester.Rule.begin(Rule.java:152)
at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1386)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1685)
at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
at org.apache.catalina.startup.Catalina.load(Catalina.java:562)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 26 more
2018-12-19 22:48:57 Commons Daemon procrun stderr initialized
Dec 19, 2018 10:48:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.2.10 using APR version 1.5.2.
Dec 19, 2018 10:48:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Dec 19, 2018 10:48:57 PM org.apache.tomcat.util.digester.Digester startElement
SEVERE: Begin event threw error
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.apache.coyote.ajp.AjpAprProtocol.<clinit>(AjpAprProtocol.java:52)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at org.apache.catalina.connector.Connector.<init>(Connector.java:84)
at org.apache.catalina.startup.ConnectorCreateRule.begin(ConnectorCreateRule.java:55)
at org.apache.tomcat.util.digester.Rule.begin(Rule.java:152)
at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1386)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1685)
at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
at org.apache.catalina.startup.Catalina.load(Catalina.java:562)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 26 more
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.apache.coyote.ajp.AjpAprProtocol.<clinit>(AjpAprProtocol.java:52)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at org.apache.catalina.connector.Connector.<init>(Connector.java:84)
at org.apache.catalina.startup.ConnectorCreateRule.begin(ConnectorCreateRule.java:55)
at org.apache.tomcat.util.digester.Rule.begin(Rule.java:152)
at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1386)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1685)
at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
at org.apache.catalina.startup.Catalina.load(Catalina.java:562)
... 6 more
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 26 more
On Wed, Dec 19, 2018, at 7:03 PM, Bo wrote:
> Hi:
>
> I'm trying to migrate a custom app running Tomcat5.5.17 to Tomcat7. This application is installed in its own folder on the root directory of a Windows 2008 R2 64-bit machine. The application itself was originally "installed" via the unzip method, and its tomcat folder is inside of the application folder, which itself is placed in the C:\ root drive. As a test, to confirm I'm doing this right, I go to Apache Tomcat archive pages and download the .zip for Tomcat 5.5.17 ( https://archive.apache.org/dist/tomcat/tomcat-5/v5.5.17/ ) and unzip it and see if I can do a successful in place migration from the existing version to the exact same version from a clean install etc and it works 100%. During this process I also was able to use WinMerge tool to find all folder and file diffs and comparing the two different tomcat5.5.17 folders side by side to see exactly what values and lines changed from the fresh install to the already installed version... I will include a short summary of all said relevant and pertinent edits/changes at the end of this message.
>
> Long story short, next I'm trying to migrate from Tomcat 5.5.17 to Tomcat7. I see that the officially supported route is two paths, migrating/updating 1 level at a time, from Tomcat5.5 to Tomcat 6 and then from Tomcat6 to Tomcat7. There doesn't seem to be a single migration instruction or guide to go from directly Tomcat5.5 to Tomcat7. In any case, its logical enough that I can combine or merge all the changes from 5.5 to 6 and 6 to 7 to be able to infer what is the total effective elements of change needed to do the successful upgrading from version 5.5.17 to version 7.
>
> see http://tomcat.apache.org/migration-6.html
> http://tomcat.apache.org/migration-7.html
>
> So I first download Tomcat7 the zip file from here : http://mirror.olnevhost.net/pub/apache/tomcat/tomcat-7/v7.0.92/bin/apache-tomcat-7.0.92-windows-x86.zip
>
> Then I unzip it and put it in my application directory, after first renaming and backing up the existing old tomcat folder etc...
>
> I use the service.bat to install the service for tomcat7, and confirm that it starts, I can see the status page just fine... so I proceed to install the custom application.
>
> I do step by step, initially just copying over the application folder in the webapps from the tomcat5 to tomcat7 folder, then I restart the tomcat7 service, sign back in to the status page, and I see the application is now listed under the List Applications section. I try to run/start it but of course it won't run or start yet giving error of : "FAIL - Application at context path /qms could not be started"
>
> I realize some major structural changes occurred from version 5.5 to version 6, namely detailed here about the merging and consolidation of some directories and especially related to lib folders into a single \tomcat\lib folder in version 6 and version 7.
>
> So I copy/paste and transplant all the stuff in \common\endorsed and \common\lib and \shared\lib to the right locations in the tomcat7 and I follow that with updating the tomcat-users.xml in conf
>
>
> Then I restart the tomcat7 service, and go back to the status page to start up my custom application but instead of getting a "FAIL - Application at context path /qms could not be started" error message, I'm now getting a new error message that states:
>
> *_Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists._*
> *_Apache Tomcat/7.0.92_*
>
> I googled around and people advised that need to use Eclipse tool to help, but my server doesn't have it installed, the application was originally never built with it, never used it and didn't come with it, plus furthermore it doesn't appear some of the solutions are relevant to the issue that I'm facing...
>
> What can I do to get this to work on tomcat7?
>
>
>
> *diff changes from tomcat.initialoriginal to tomcat5517zip***
> **
> **
> *in C:\VE4_0\tomcat.initialoriginal\bin***
> *jmx.jar LEFT SIDE ONLY***
> **
> *=====***
> *In***
> *C:\VE4_0\tomcat.initialoriginal\bin\service.bat***
> **
> **
> *LINE 103 "%EXECUTABLE%" //US//%SERVICE_NAME% --JvmOptions "-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\common\endorsed -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9000 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" --StartMode jvm --StopMode jvm***
> *vs "%EXECUTABLE%" //US//%SERVICE_NAME% --JvmOptions "-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\common\endorsed" --StartMode jvm --StopMode jvm***
> **
> *LINE 108 "%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-Djava.io.tmpdir=%CATALINA_BASE%\temp" --JvmMs 1620 --JvmMx 1620***
> *vs "%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-Djava.io.tmpdir=%CATALINA_BASE%\temp" --JvmMs 128 --JvmMx 256***
> **
> *=====***
> **
> *in C:\VE4_0\tomcat.initialoriginal\common\endorsed***
> *exists***
> *serializer.jar***
> *xalan.jar***
> *xercesImpl.jar***
> *xml-apis.jar***
> *xmlParserAPIs.jar***
> **
> *in C:\VE4_0\tomcat.initialoriginal\common\lib***
> *exxists***
> *activation.jar***
> *commons-codec.jar***
> *commons-httpclient.jar***
> *jdbc2_0-stdext.jar***
> *jta.jar***
> *mail.jar***
> **
> *=====***
> **
> *in C:\VE4_0\tomcat.initialoriginal\conf***
> *exists***
> *Saved tomcat-users.xml***
> *server.xml.bak***
> **
> *=====***
> **
> *C:\VE4_0\tomcat.initialoriginal\conf\server.xml***
> **
> *LINE 76 to 70***
> * <!-- Define a non-SSL HTTP/1.1 Connector on port 80 -->***
> * <Connector port="80" maxHttpHeaderSize="8192"***
> * maxThreads="500" minSpareThreads="50" maxSpareThreads="125"***
> * enableLookups="false" redirectPort="8443" acceptCount="500"***
> * ***
> *vs***
> **
> * <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->***
> * <Connector port="8080" maxHttpHeaderSize="8192"***
> * maxThreads="150" minSpareThreads="25" maxSpareThreads="75"***
> * enableLookups="false" redirectPort="8443" acceptCount="100"***
> * ***
> * ***
> *LINE 341 this section is NOT commented out***
> **
> *<Valve className="org.apache.catalina.valves.AccessLogValve"***
> * directory="logs" prefix="localhost_access_log." suffix=".txt"***
> * pattern="common" resolveHosts="false"/>***
> **
> *LINE 363 this section is new data***
> *<!--<Host name="lonestar.intelliun.net" debug="4" appBase="webapps" autoDeploy="false" >***
> * <Context path="" docBase="qms" reloadable="true" debug="4" />***
> * </Host>-->***
> * ***
> * ***
> * ***
> * ***
> * /////////////////////////***
> * ***
> *in C:\VE4_0\tomcat.initialoriginal\shared\lib***
> *exists***
> **
> *activation.jar***
> *alk.jar***
> *HTMLParser.jar***
> *jcommon-1.0.0-rc1.jar***
> *jfreechart-1.0.0-rc1.jar***
> *jta.jar***
> *kawa-1.7.90.jar***
> *ldap.jar***
> *mail.jar***
> *microstar.jar***
> *naming-factory-dbcp.jar***
> *pcmiler-city-latlong.jar***
> *pdf.jar***
> *veserver.jar***
> *vewsf.jar***
> *w3c.jar***
> *webdav-servlet.jar***
> *xml.jar***
> **
> **
> *//////////////////////***
> **
> **
> *in C:\VE4_0\tomcat.initialoriginal\webapps***
> *exists***
> **
> *C:\VE4_0\tomcat.initialoriginal\webapps\mantis***
> *C:\VE4_0\tomcat.initialoriginal\webapps\qms***
> *C:\VE4_0\tomcat.initialoriginal\webapps\ve***
> **
> **
> */////////***
> **
> **
> *in C:\VE4_0\tomcat.initialoriginal\work***
> *exists***
> *C:\VE4_0\tomcat.initialoriginal\work\Catalina***
> **
> *in C:\VE4_0\tomcat.initialoriginal\work***
> *exists***
> *C:\VE4_0\tomcat.initialoriginal\veindex***
> *C:\VE4_0\tomcat.initialoriginal\weblogs***
> **
> **
> *//////***
> **
> **
> *in C:\VE4_0\tomcat.initialoriginal\***
> *exists***
> *C:\VE4_0\tomcat.initialoriginal\veindex***
> *C:\VE4_0\tomcat.initialoriginal\weblogs*
>
>
> On Tue, Dec 18, 2018, at 7:22 AM, Christopher Schultz wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Bo,
>>
>> On 12/18/18 00:49, Bo wrote:
>> > here is screenshot
>> >
>> > I just tried again still no working
>> >
>> >
>> > https://i.imgur.com/8bQH2YB.png
>>
>> Your XML is invalid and can't be loaded. The log file should confirm
>> this. Unfortunately, Notepad++ makes it look (via syntax highlighting)
>> like your XML file is properly-formed but it is not.
>>
>> - -chris
>> -----BEGIN PGP SIGNATURE-----
>> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>>
>> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwZEMEACgkQHPApP6U8
>> pFgV8w/9GfZaU8HaYv5N/xN512qUhensuJfjsXM8SCBM6SWUTbKPL9TOsUq6gzSB
>> DMP4NkGH9q9nMXjoM1y9oz+IpmkTeuO1B8FBZq+pMfFANpUfUGvNHI9jtM/fANmT
>> HJDV5U6LiTbsgyZHeGe7TW6YoiLNhniSji5F+5jlPM5aFJURgTwvufUyduzVfDLb
>> eCi3CBlpb20ETlNWHaYlxPkBXiAPCOhyIxIEkszW34aZxxt01/VYvPnOI4igbYlQ
>> WHKhly5tHu1Vup2GUcnjKy1VPWQjCfynfZOBFOeUosGqzXbRovBTSNCo48dSJd6O
>> M+yElR5//fGOsdv5PjEn9Wz29j/VIBCCfnneA+2wS9BflchCcPwFH2IToDTfbT8j
>> tYdY7ux3clHJ5QN/pJt5bkdggwKq0VdIIOBLucDmNGGoFHURA/0IrmlfY4/F7VM0
>> PropnJvbrHi6MF6aSxPtxZtJeCxAwfASwOpDyKKv3wNQ1VYjLOdzkpT/+0sD6mq8
>> 03d29Ecvywuiq7VGhzdWvK8oSSj3PoIggJtLql6h3ohurRwqXZrPUV0PU9rDRhfs
>> 2b76pk6we+xJLbA7yyA1zftgH8iNBvIc6Q6HnYjcnxHTeiVi1SU6OAaJeRvRUsUE
>> as8CaRonVjvwBMWcsWLyH8Y3K5ehfOoUuMpFNGrJg9HspyWIhNs=
>> =u6nK
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
Re: Migrating app from Tomcat5.5.17 to Tomcat7, getting Description
The origin server did not find a current representation for the target
resource
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Bo,
Please do not:
1. Hijack threads
2. Email me personally
- -chris
On 12/20/18 00:03, Bo wrote:
> Hi:
>
> I'm trying to migrate a custom app running Tomcat5.5.17 to Tomcat7.
> This application is installed in its own folder on the root
> directory of a Windows 2008 R2 64-bit machine. The application
> itself was originally "installed" via the unzip method, and its
> tomcat folder is inside of the application folder, which itself is
> placed in the C:\ root drive. As a test, to confirm I'm doing this
> right, I go to Apache Tomcat archive pages and download the .zip
> for Tomcat 5.5.17 (
> https://archive.apache.org/dist/tomcat/tomcat-5/v5.5.17/ ) and
> unzip it and see if I can do a successful in place migration from
> the existing version to the exact same version from a clean install
> etc and it works 100%. During this process I also was able to use
> WinMerge tool to find all folder and file diffs and comparing the
> two different tomcat5.5.17 folders side by side to see exactly what
> values and lines changed from the fresh install to the already
> installed version... I will include a short summary of all said
> relevant and pertinent edits/changes at the end of this message.
>
> Long story short, next I'm trying to migrate from Tomcat 5.5.17 to
> Tomcat7. I see that the officially supported route is two paths,
> migrating/updating 1 level at a time, from Tomcat5.5 to Tomcat 6
> and then from Tomcat6 to Tomcat7. There doesn't seem to be a single
> migration instruction or guide to go from directly Tomcat5.5 to
> Tomcat7. In any case, its logical enough that I can combine or
> merge all the changes from 5.5 to 6 and 6 to 7 to be able to infer
> what is the total effective elements of change needed to do the
> successful upgrading from version 5.5.17 to version 7.
>
> see http://tomcat.apache.org/migration-6.html
> http://tomcat.apache.org/migration-7.html
>
> So I first download Tomcat7 the zip file from here :
> http://mirror.olnevhost.net/pub/apache/tomcat/tomcat-7/v7.0.92/bin/apa
che-tomcat-7.0.92-windows-x86.zip
>
> Then I unzip it and put it in my application directory, after
> first renaming and backing up the existing old tomcat folder
> etc...
>
> I use the service.bat to install the service for tomcat7, and
> confirm that it starts, I can see the status page just fine... so I
> proceed to install the custom application.
>
> I do step by step, initially just copying over the application
> folder in the webapps from the tomcat5 to tomcat7 folder, then I
> restart the tomcat7 service, sign back in to the status page, and I
> see the application is now listed under the List Applications
> section. I try to run/start it but of course it won't run or start
> yet giving error of : "FAIL - Application at context path /qms
> could not be started"
>
> I realize some major structural changes occurred from version 5.5
> to version 6, namely detailed here about the merging and
> consolidation of some directories and especially related to lib
> folders into a single \tomcat\lib folder in version 6 and version
> 7.
>
> So I copy/paste and transplant all the stuff in \common\endorsed
> and \common\lib and \shared\lib to the right locations in the
> tomcat7 and I follow that with updating the tomcat-users.xml in
> conf
>
>
> Then I restart the tomcat7 service, and go back to the status page
> to start up my custom application but instead of getting a "FAIL -
> Application at context path /qms could not be started" error
> message, I'm now getting a new error message that states:
>
> *_Description The origin server did not find a current
> representation for the target resource or is not willing to
> disclose that one exists. _* *_Apache Tomcat/7.0.92_*
>
> I googled around and people advised that need to use Eclipse tool
> to help, but my server doesn't have it installed, the application
> was originally never built with it, never used it and didn't come
> with it, plus furthermore it doesn't appear some of the solutions
> are relevant to the issue that I'm facing...
>
> What can I do to get this to work on tomcat7?
>
>
>
> *diff changes from tomcat.initialoriginal to tomcat5517zip** * * *
> * * *in C:\VE4_0\tomcat.initialoriginal\bin** * *jmx.jar LEFT SIDE
> ONLY** * * * *=====** * *In** *
> *C:\VE4_0\tomcat.initialoriginal\bin\service.bat** * * * * * *LINE
> 103 "%EXECUTABLE%" //US//%SERVICE_NAME% --JvmOptions
> "-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djav
a.endorsed.dirs=%CATALINA_HOME%\common\endorsed
> -Dcom.sun.management.jmxremote
> -Dcom.sun.management.jmxremote.port=9000
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false" --StartMode jvm
> --StopMode jvm** * *vs "%EXECUTABLE%" //US//%SERVICE_NAME%
> --JvmOptions
> "-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djav
a.endorsed.dirs=%CATALINA_HOME%\common\endorsed"
> --StartMode jvm --StopMode jvm** * * * *LINE 108 "%EXECUTABLE%"
> //US//%SERVICE_NAME% ++JvmOptions
> "-Djava.io.tmpdir=%CATALINA_BASE%\temp" --JvmMs 1620 --JvmMx
> 1620** * *vs "%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions
> "-Djava.io.tmpdir=%CATALINA_BASE%\temp" --JvmMs 128 --JvmMx 256**
> * * * *=====** * * * *in
> C:\VE4_0\tomcat.initialoriginal\common\endorsed** * *exists** *
> *serializer.jar** * *xalan.jar** * *xercesImpl.jar** *
> *xml-apis.jar** * *xmlParserAPIs.jar** * * * *in
> C:\VE4_0\tomcat.initialoriginal\common\lib** * *exxists** *
> *activation.jar** * *commons-codec.jar** *
> *commons-httpclient.jar** * *jdbc2_0-stdext.jar** * *jta.jar** *
> *mail.jar** * * * *=====** * * * *in
> C:\VE4_0\tomcat.initialoriginal\conf** * *exists** * *Saved
> tomcat-users.xml** * *server.xml.bak** * * * *=====** * * *
> *C:\VE4_0\tomcat.initialoriginal\conf\server.xml** * * * *LINE 76
> to 70** * * <!-- Define a non-SSL HTTP/1.1 Connector on port 80
> -->** * * <Connector port="80" maxHttpHeaderSize="8192"** * *
> maxThreads="500" minSpareThreads="50" maxSpareThreads="125"** * *
> enableLookups="false" redirectPort="8443" acceptCount="500"** * *
> ** * *vs** * * * * <!-- Define a non-SSL HTTP/1.1 Connector on port
> 8080 -->** * * <Connector port="8080" maxHttpHeaderSize="8192"** *
> * maxThreads="150" minSpareThreads="25" maxSpareThreads="75"** * *
> enableLookups="false" redirectPort="8443" acceptCount="100"** * *
> ** * * ** * *LINE 341 this section is NOT commented out** * * *
> *<Valve className="org.apache.catalina.valves.AccessLogValve"** * *
> directory="logs" prefix="localhost_access_log." suffix=".txt"** * *
> pattern="common" resolveHosts="false"/>** * * * *LINE 363 this
> section is new data** * *<!--<Host name="lonestar.intelliun.net"
> debug="4" appBase="webapps" autoDeploy="false" >** * * <Context
> path="" docBase="qms" reloadable="true" debug="4" />** * *
> </Host>-->** * * ** * * ** * * ** * * ** * *
> /////////////////////////** * * ** * *in
> C:\VE4_0\tomcat.initialoriginal\shared\lib** * *exists** * * *
> *activation.jar** * *alk.jar** * *HTMLParser.jar** *
> *jcommon-1.0.0-rc1.jar** * *jfreechart-1.0.0-rc1.jar** *
> *jta.jar** * *kawa-1.7.90.jar** * *ldap.jar** * *mail.jar** *
> *microstar.jar** * *naming-factory-dbcp.jar** *
> *pcmiler-city-latlong.jar** * *pdf.jar** * *veserver.jar** *
> *vewsf.jar** * *w3c.jar** * *webdav-servlet.jar** * *xml.jar** * *
> * * * *//////////////////////** * * * * * *in
> C:\VE4_0\tomcat.initialoriginal\webapps** * *exists** * * *
> *C:\VE4_0\tomcat.initialoriginal\webapps\mantis** *
> *C:\VE4_0\tomcat.initialoriginal\webapps\qms** *
> *C:\VE4_0\tomcat.initialoriginal\webapps\ve** * * * * *
> */////////** * * * * * *in C:\VE4_0\tomcat.initialoriginal\work**
> * *exists** * *C:\VE4_0\tomcat.initialoriginal\work\Catalina** * *
> * *in C:\VE4_0\tomcat.initialoriginal\work** * *exists** *
> *C:\VE4_0\tomcat.initialoriginal\veindex** *
> *C:\VE4_0\tomcat.initialoriginal\weblogs** * * * * * *//////** * *
> * * * *in C:\VE4_0\tomcat.initialoriginal\** * *exists** *
> *C:\VE4_0\tomcat.initialoriginal\veindex** *
> *C:\VE4_0\tomcat.initialoriginal\weblogs*
>
>
> On Tue, Dec 18, 2018, at 7:22 AM, Christopher Schultz wrote: Bo,
>
> On 12/18/18 00:49, Bo wrote:
>>>> here is screenshot
>>>>
>>>> I just tried again still no working
>>>>
>>>>
>>>> https://i.imgur.com/8bQH2YB.png
>
> Your XML is invalid and can't be loaded. The log file should
> confirm this. Unfortunately, Notepad++ makes it look (via syntax
> highlighting) like your XML file is properly-formed but it is not.
>
> -chris
>>
>> ---------------------------------------------------------------------
>>
>>
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwbGqcACgkQHPApP6U8
pFhoWxAArXrT7/5LVxLwj6rGKsA4fnH6pxBOjnKiYXO2/nj2MTQcMroy/L0K1bCp
t74ZgkLJquAG/lZLrNiYPZ2jgX5RX/01KS1ZJ/U0zAsXr38hl6HluPkPS9sZm6Lr
XyIfaWGYeji8He0L7kk05k6id7aRXyvSv7h9iZln5giE1L1s1jPOqykH4v9baw5w
XJqwPfe/9HWIc8MTpBtL5HP2tGG9unPzq4xlo5usg4s+ZUKb0i5HnW6CLZpy0UJz
/kjSYFrStJMkJvLt4wyY7Tr7TCQ8R+MQKtf58imRvgFk6MIAHfuFF00zbdTsDjZM
5P4RZMbgPAf2ZxABYhfI22uM34atFY9Q4e8TxS2qrW6QR15zOG6a4STge4B8m1Ku
LnGfCsQ9wKUVvWlTGrjir50VvSPTs4ZKAJjGfMyo63V/UlU+w7h137oclOt5KW9r
jCv3IaEaqGc1RUIM+An45HBX7EApYRvx7Hgj81bIbXR6JbzGc2BW41A3830tkHQe
wg5YupEfGo+ZfKy1NyJy/eyzV5C9YY0CoRl4C1Ufg6ynyVqK68fmOCyr+E0K/L2E
k/D/efzJMu+S3qOLiKTQOxxKmfG4cmKJKChK49QhDTbLEscOQ+wyo/sjDHy32EnT
h+DCSjuUzG2XD+uZj9QiwFEg68TDaQBqTa5sBoQStRseZI7cw2c=
=J7oU
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Migrating app from Tomcat5.5.17 to Tomcat7, getting Description The origin server did not find a current representation for the target resource
Posted by Bo <bo...@bochen.ch>.
Hi:
I'm trying to migrate a custom app running Tomcat5.5.17 to Tomcat7. This application is installed in its own folder on the root directory of a Windows 2008 R2 64-bit machine. The application itself was originally "installed" via the unzip method, and its tomcat folder is inside of the application folder, which itself is placed in the C:\ root drive. As a test, to confirm I'm doing this right, I go to Apache Tomcat archive pages and download the .zip for Tomcat 5.5.17 ( https://archive.apache.org/dist/tomcat/tomcat-5/v5.5.17/ ) and unzip it and see if I can do a successful in place migration from the existing version to the exact same version from a clean install etc and it works 100%. During this process I also was able to use WinMerge tool to find all folder and file diffs and comparing the two different tomcat5.5.17 folders side by side to see exactly what values and lines changed from the fresh install to the already installed version... I will include a short summary of all said relevant and pertinent edits/changes at the end of this message.
Long story short, next I'm trying to migrate from Tomcat 5.5.17 to Tomcat7. I see that the officially supported route is two paths, migrating/updating 1 level at a time, from Tomcat5.5 to Tomcat 6 and then from Tomcat6 to Tomcat7. There doesn't seem to be a single migration instruction or guide to go from directly Tomcat5.5 to Tomcat7. In any case, its logical enough that I can combine or merge all the changes from 5.5 to 6 and 6 to 7 to be able to infer what is the total effective elements of change needed to do the successful upgrading from version 5.5.17 to version 7.
see http://tomcat.apache.org/migration-6.html
http://tomcat.apache.org/migration-7.html
So I first download Tomcat7 the zip file from here : http://mirror.olnevhost.net/pub/apache/tomcat/tomcat-7/v7.0.92/bin/apache-tomcat-7.0.92-windows-x86.zip
Then I unzip it and put it in my application directory, after first renaming and backing up the existing old tomcat folder etc...
I use the service.bat to install the service for tomcat7, and confirm that it starts, I can see the status page just fine... so I proceed to install the custom application.
I do step by step, initially just copying over the application folder in the webapps from the tomcat5 to tomcat7 folder, then I restart the tomcat7 service, sign back in to the status page, and I see the application is now listed under the List Applications section. I try to run/start it but of course it won't run or start yet giving error of : "FAIL - Application at context path /qms could not be started"
I realize some major structural changes occurred from version 5.5 to version 6, namely detailed here about the merging and consolidation of some directories and especially related to lib folders into a single \tomcat\lib folder in version 6 and version 7.
So I copy/paste and transplant all the stuff in \common\endorsed and \common\lib and \shared\lib to the right locations in the tomcat7 and I follow that with updating the tomcat-users.xml in conf
Then I restart the tomcat7 service, and go back to the status page to start up my custom application but instead of getting a "FAIL - Application at context path /qms could not be started" error message, I'm now getting a new error message that states:
*_Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
_*
*_Apache Tomcat/7.0.92_*
I googled around and people advised that need to use Eclipse tool to help, but my server doesn't have it installed, the application was originally never built with it, never used it and didn't come with it, plus furthermore it doesn't appear some of the solutions are relevant to the issue that I'm facing...
What can I do to get this to work on tomcat7?
*diff changes from tomcat.initialoriginal to tomcat5517zip**
*
*
*
*
*
*in C:\VE4_0\tomcat.initialoriginal\bin**
*
*jmx.jar LEFT SIDE ONLY**
*
*
*
*=====**
*
*In**
*
*C:\VE4_0\tomcat.initialoriginal\bin\service.bat**
*
*
*
*
*
*LINE 103 "%EXECUTABLE%" //US//%SERVICE_NAME% --JvmOptions "-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\common\endorsed -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9000 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" --StartMode jvm --StopMode jvm**
*
*vs "%EXECUTABLE%" //US//%SERVICE_NAME% --JvmOptions "-Dcatalina.base=%CATALINA_BASE%;-Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\common\endorsed" --StartMode jvm --StopMode jvm**
*
*
*
*LINE 108 "%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-Djava.io.tmpdir=%CATALINA_BASE%\temp" --JvmMs 1620 --JvmMx 1620**
*
*vs "%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions "-Djava.io.tmpdir=%CATALINA_BASE%\temp" --JvmMs 128 --JvmMx 256**
*
*
*
*=====**
*
*
*
*in C:\VE4_0\tomcat.initialoriginal\common\endorsed**
*
*exists**
*
*serializer.jar**
*
*xalan.jar**
*
*xercesImpl.jar**
*
*xml-apis.jar**
*
*xmlParserAPIs.jar**
*
*
*
*in C:\VE4_0\tomcat.initialoriginal\common\lib**
*
*exxists**
*
*activation.jar**
*
*commons-codec.jar**
*
*commons-httpclient.jar**
*
*jdbc2_0-stdext.jar**
*
*jta.jar**
*
*mail.jar**
*
*
*
*=====**
*
*
*
*in C:\VE4_0\tomcat.initialoriginal\conf**
*
*exists**
*
*Saved tomcat-users.xml**
*
*server.xml.bak**
*
*
*
*=====**
*
*
*
*C:\VE4_0\tomcat.initialoriginal\conf\server.xml**
*
*
*
*LINE 76 to 70**
*
* <!-- Define a non-SSL HTTP/1.1 Connector on port 80 -->**
*
* <Connector port="80" maxHttpHeaderSize="8192"**
*
* maxThreads="500" minSpareThreads="50" maxSpareThreads="125"**
*
* enableLookups="false" redirectPort="8443" acceptCount="500"**
*
* **
*
*vs**
*
*
*
* <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->**
*
* <Connector port="8080" maxHttpHeaderSize="8192"**
*
* maxThreads="150" minSpareThreads="25" maxSpareThreads="75"**
*
* enableLookups="false" redirectPort="8443" acceptCount="100"**
*
* **
*
* **
*
*LINE 341 this section is NOT commented out**
*
*
*
*<Valve className="org.apache.catalina.valves.AccessLogValve"**
*
* directory="logs" prefix="localhost_access_log." suffix=".txt"**
*
* pattern="common" resolveHosts="false"/>**
*
*
*
*LINE 363 this section is new data**
*
*<!--<Host name="lonestar.intelliun.net" debug="4" appBase="webapps" autoDeploy="false" >**
*
* <Context path="" docBase="qms" reloadable="true" debug="4" />**
*
* </Host>-->**
*
* **
*
* **
*
* **
*
* **
*
* /////////////////////////**
*
* **
*
*in C:\VE4_0\tomcat.initialoriginal\shared\lib**
*
*exists**
*
*
*
*activation.jar**
*
*alk.jar**
*
*HTMLParser.jar**
*
*jcommon-1.0.0-rc1.jar**
*
*jfreechart-1.0.0-rc1.jar**
*
*jta.jar**
*
*kawa-1.7.90.jar**
*
*ldap.jar**
*
*mail.jar**
*
*microstar.jar**
*
*naming-factory-dbcp.jar**
*
*pcmiler-city-latlong.jar**
*
*pdf.jar**
*
*veserver.jar**
*
*vewsf.jar**
*
*w3c.jar**
*
*webdav-servlet.jar**
*
*xml.jar**
*
*
*
*
*
*//////////////////////**
*
*
*
*
*
*in C:\VE4_0\tomcat.initialoriginal\webapps**
*
*exists**
*
*
*
*C:\VE4_0\tomcat.initialoriginal\webapps\mantis**
*
*C:\VE4_0\tomcat.initialoriginal\webapps\qms**
*
*C:\VE4_0\tomcat.initialoriginal\webapps\ve**
*
*
*
*
*
*/////////**
*
*
*
*
*
*in C:\VE4_0\tomcat.initialoriginal\work**
*
*exists**
*
*C:\VE4_0\tomcat.initialoriginal\work\Catalina**
*
*
*
*in C:\VE4_0\tomcat.initialoriginal\work**
*
*exists**
*
*C:\VE4_0\tomcat.initialoriginal\veindex**
*
*C:\VE4_0\tomcat.initialoriginal\weblogs**
*
*
*
*
*
*//////**
*
*
*
*
*
*in C:\VE4_0\tomcat.initialoriginal\**
*
*exists**
*
*C:\VE4_0\tomcat.initialoriginal\veindex**
*
*C:\VE4_0\tomcat.initialoriginal\weblogs*
On Tue, Dec 18, 2018, at 7:22 AM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Bo,
>
> On 12/18/18 00:49, Bo wrote:
> > here is screenshot
> >
> > I just tried again still no working
> >
> >
> > https://i.imgur.com/8bQH2YB.png
>
> Your XML is invalid and can't be loaded. The log file should confirm
> this. Unfortunately, Notepad++ makes it look (via syntax highlighting)
> like your XML file is properly-formed but it is not.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwZEMEACgkQHPApP6U8
> pFgV8w/9GfZaU8HaYv5N/xN512qUhensuJfjsXM8SCBM6SWUTbKPL9TOsUq6gzSB
> DMP4NkGH9q9nMXjoM1y9oz+IpmkTeuO1B8FBZq+pMfFANpUfUGvNHI9jtM/fANmT
> HJDV5U6LiTbsgyZHeGe7TW6YoiLNhniSji5F+5jlPM5aFJURgTwvufUyduzVfDLb
> eCi3CBlpb20ETlNWHaYlxPkBXiAPCOhyIxIEkszW34aZxxt01/VYvPnOI4igbYlQ
> WHKhly5tHu1Vup2GUcnjKy1VPWQjCfynfZOBFOeUosGqzXbRovBTSNCo48dSJd6O
> M+yElR5//fGOsdv5PjEn9Wz29j/VIBCCfnneA+2wS9BflchCcPwFH2IToDTfbT8j
> tYdY7ux3clHJ5QN/pJt5bkdggwKq0VdIIOBLucDmNGGoFHURA/0IrmlfY4/F7VM0
> PropnJvbrHi6MF6aSxPtxZtJeCxAwfASwOpDyKKv3wNQ1VYjLOdzkpT/+0sD6mq8
> 03d29Ecvywuiq7VGhzdWvK8oSSj3PoIggJtLql6h3ohurRwqXZrPUV0PU9rDRhfs
> 2b76pk6we+xJLbA7yyA1zftgH8iNBvIc6Q6HnYjcnxHTeiVi1SU6OAaJeRvRUsUE
> as8CaRonVjvwBMWcsWLyH8Y3K5ehfOoUuMpFNGrJg9HspyWIhNs=
> =u6nK
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: why can't i login to tomcat7 status page from clean install zip
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Bo,
On 12/18/18 00:49, Bo wrote:
> here is screenshot
>
> I just tried again still no working
>
>
> https://i.imgur.com/8bQH2YB.png
Your XML is invalid and can't be loaded. The log file should confirm
this. Unfortunately, Notepad++ makes it look (via syntax highlighting)
like your XML file is properly-formed but it is not.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwZEMEACgkQHPApP6U8
pFgV8w/9GfZaU8HaYv5N/xN512qUhensuJfjsXM8SCBM6SWUTbKPL9TOsUq6gzSB
DMP4NkGH9q9nMXjoM1y9oz+IpmkTeuO1B8FBZq+pMfFANpUfUGvNHI9jtM/fANmT
HJDV5U6LiTbsgyZHeGe7TW6YoiLNhniSji5F+5jlPM5aFJURgTwvufUyduzVfDLb
eCi3CBlpb20ETlNWHaYlxPkBXiAPCOhyIxIEkszW34aZxxt01/VYvPnOI4igbYlQ
WHKhly5tHu1Vup2GUcnjKy1VPWQjCfynfZOBFOeUosGqzXbRovBTSNCo48dSJd6O
M+yElR5//fGOsdv5PjEn9Wz29j/VIBCCfnneA+2wS9BflchCcPwFH2IToDTfbT8j
tYdY7ux3clHJ5QN/pJt5bkdggwKq0VdIIOBLucDmNGGoFHURA/0IrmlfY4/F7VM0
PropnJvbrHi6MF6aSxPtxZtJeCxAwfASwOpDyKKv3wNQ1VYjLOdzkpT/+0sD6mq8
03d29Ecvywuiq7VGhzdWvK8oSSj3PoIggJtLql6h3ohurRwqXZrPUV0PU9rDRhfs
2b76pk6we+xJLbA7yyA1zftgH8iNBvIc6Q6HnYjcnxHTeiVi1SU6OAaJeRvRUsUE
as8CaRonVjvwBMWcsWLyH8Y3K5ehfOoUuMpFNGrJg9HspyWIhNs=
=u6nK
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: why can't i login to tomcat7 status page from clean install zip
Posted by Bo <bo...@bochen.ch>.
here is screenshot
I just tried again still no working
https://i.imgur.com/8bQH2YB.png
On Mon, Dec 17, 2018, at 11:27 PM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Bo,
>
> On 12/18/18 00:10, Bo wrote:
> > I do a clean install of the tomcat7 folder and rename it to just
> > tomcat, and without changing ANYTHING and without adding any old
> > files yet, I start the tomcat service and try to get to the status
> > page, but this time it won't even let me log into anything at all
> > either, no matter what I try.
> By default, Tomcat does not allow users to view the status (manager,
> right?) page.
>
> You have to specifically edit the tomcat-users.xml file in order to
> allow access.
>
> > This is the tomcat7 fresh download links I used
> >
> > https://tomcat.apache.org/download-70.cgi
> >
> > http://apache.mirrors.tds.net/tomcat/tomcat-7/v7.0.92/bin/apache-tomca
> t-7.0.92-windows-x86.zip
> >
> > https://tomcat.apache.org/tomcat-7.0-doc/appdev/deployment.html
> >
> > I unzip the apache-tomcat-7.0.92-windows-x86.zip and put it in the
> > root of a custom web app that I have and then I use the
> > service.bat install to trigger the services install, this is on
> > windows server so I start it up in services.msc
> >
> > I can go to localhost fine, but it won't let me login
> >
> >
> > I checked the tomcat user xml file a trillion times to triple check
> > to make sure I have it right, but no matter what, even after
> > multiple restarts, it won't even let me login to the status
> > page!!!!!
>
> When you say you "checked it", do you mean you /edited/ it, or is it
> still the same file that shipped with Tomcat?
>
> > 401 Unauthorized
> >
> > You are not authorized to view this page. If you have not changed
> > any configuration files, please examine the file
> > conf/tomcat-users.xml in your installation. That file must contain
> > the credentials to let you use this webapp.
> >
> > For example, to add the manager-gui role to a user named tomcat
> > with a password of s3cret, add the following to the config file
> > listed above.
> >
> > <role rolename="manager-gui"/> <user username="tomcat"
> > password="s3cret" roles="manager-gui"/>
> >
> > Note that for Tomcat 7 onwards, the roles required to use the
> > manager application were changed from the single manager role to
> > the following four roles. You will need to assign the role(s)
> > required for the functionality you wish to access.
> >
> > manager-gui - allows access to the HTML GUI and the status pages
> > manager-script - allows access to the text interface and the status
> > pages manager-jmx - allows access to the JMX proxy and the status
> > pages manager-status - allows access to the status pages only
> >
> > The HTML interface is protected against CSRF but the text and JMX
> > interfaces are not. To maintain the CSRF protection:
> >
> > Users with the manager-gui role should not be granted either the
> > manager-script or manager-jmx roles. If the text or jmx interfaces
> > are accessed through a browser (e.g. for testing since these
> > interfaces are intended for tools not humans) then the browser must
> > be closed afterwards to terminate the session.
> >
> > For more information - please see the Manager App HOW-TO.
> >
>
> Without revealing any passwords, can you post your ENTIRE (again,
> redacted) tomcat-users.xml file?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwYhR4ACgkQHPApP6U8
> pFhZ6BAAkhA4xXe6iSF2k4kK4NoK0N9ViCaW8CaFQjcM324FkyN4t66lnOEQXAVm
> hIcnOdyveCRQxuNK6TYbBSOG+0KXmuReXelGaGs37hMHGEzaxGUkrkoU7ntDZBvB
> euvXOUmOjJDNgGVP5FnH5iiqsRhRpL6Fd7a5n1upAzJSryXelOVuf3q+kD7y+7Fm
> vuT6NAiee/2efnN2vXGv0vGqAGoSLDUHIvGKXinv/JGbIf6JIIqb1ZGo9KuUPp+j
> tIEaKSB42blqZ/SntEk44i5hmQctX6eTlvbl+u8XDExfQGNCnru0A9xCtV9/3v5q
> ZbNB9e8Z2DhoaB4S57wuCxNCqsXuyOvZz4YWsQ70Cx+u5G8tmfVfUZUfmndUWuqC
> /dvIEreFZLzcSr+eh7mym7iRbktcb0G6iXnVJBpl0zYhLZsdckZ4WpArjHZHuC2J
> O/5umGbavG59SI6SYl41Ww1aYRxIKMKsXcVoi/RjVk202EcaSQ/xti8/9ar51CmN
> 2QtdoTGqud+qJVT1OflcxB+rirrw/ZEGWg8nVOA5A5acqMsPgF6HxjI+aOgZvO+Q
> ewQUpjkYamhnIo0JgZR9H7TyhpB6v+emhvd+h1ny+v0nozJPiv3NSjsLJkd8uepa
> LT8q43HxySWk7m53t60GRnOS/R9un4XOFRZ+VdTya78hK4ONdBA=
> =yC4/
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: why can't i login to tomcat7 status page from clean install zip
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Bo,
On 12/18/18 00:10, Bo wrote:
> I do a clean install of the tomcat7 folder and rename it to just
> tomcat, and without changing ANYTHING and without adding any old
> files yet, I start the tomcat service and try to get to the status
> page, but this time it won't even let me log into anything at all
> either, no matter what I try.
By default, Tomcat does not allow users to view the status (manager,
right?) page.
You have to specifically edit the tomcat-users.xml file in order to
allow access.
> This is the tomcat7 fresh download links I used
>
> https://tomcat.apache.org/download-70.cgi
>
> http://apache.mirrors.tds.net/tomcat/tomcat-7/v7.0.92/bin/apache-tomca
t-7.0.92-windows-x86.zip
>
> https://tomcat.apache.org/tomcat-7.0-doc/appdev/deployment.html
>
> I unzip the apache-tomcat-7.0.92-windows-x86.zip and put it in the
> root of a custom web app that I have and then I use the
> service.bat install to trigger the services install, this is on
> windows server so I start it up in services.msc
>
> I can go to localhost fine, but it won't let me login
>
>
> I checked the tomcat user xml file a trillion times to triple check
> to make sure I have it right, but no matter what, even after
> multiple restarts, it won't even let me login to the status
> page!!!!!
When you say you "checked it", do you mean you /edited/ it, or is it
still the same file that shipped with Tomcat?
> 401 Unauthorized
>
> You are not authorized to view this page. If you have not changed
> any configuration files, please examine the file
> conf/tomcat-users.xml in your installation. That file must contain
> the credentials to let you use this webapp.
>
> For example, to add the manager-gui role to a user named tomcat
> with a password of s3cret, add the following to the config file
> listed above.
>
> <role rolename="manager-gui"/> <user username="tomcat"
> password="s3cret" roles="manager-gui"/>
>
> Note that for Tomcat 7 onwards, the roles required to use the
> manager application were changed from the single manager role to
> the following four roles. You will need to assign the role(s)
> required for the functionality you wish to access.
>
> manager-gui - allows access to the HTML GUI and the status pages
> manager-script - allows access to the text interface and the status
> pages manager-jmx - allows access to the JMX proxy and the status
> pages manager-status - allows access to the status pages only
>
> The HTML interface is protected against CSRF but the text and JMX
> interfaces are not. To maintain the CSRF protection:
>
> Users with the manager-gui role should not be granted either the
> manager-script or manager-jmx roles. If the text or jmx interfaces
> are accessed through a browser (e.g. for testing since these
> interfaces are intended for tools not humans) then the browser must
> be closed afterwards to terminate the session.
>
> For more information - please see the Manager App HOW-TO.
>
Without revealing any passwords, can you post your ENTIRE (again,
redacted) tomcat-users.xml file?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwYhR4ACgkQHPApP6U8
pFhZ6BAAkhA4xXe6iSF2k4kK4NoK0N9ViCaW8CaFQjcM324FkyN4t66lnOEQXAVm
hIcnOdyveCRQxuNK6TYbBSOG+0KXmuReXelGaGs37hMHGEzaxGUkrkoU7ntDZBvB
euvXOUmOjJDNgGVP5FnH5iiqsRhRpL6Fd7a5n1upAzJSryXelOVuf3q+kD7y+7Fm
vuT6NAiee/2efnN2vXGv0vGqAGoSLDUHIvGKXinv/JGbIf6JIIqb1ZGo9KuUPp+j
tIEaKSB42blqZ/SntEk44i5hmQctX6eTlvbl+u8XDExfQGNCnru0A9xCtV9/3v5q
ZbNB9e8Z2DhoaB4S57wuCxNCqsXuyOvZz4YWsQ70Cx+u5G8tmfVfUZUfmndUWuqC
/dvIEreFZLzcSr+eh7mym7iRbktcb0G6iXnVJBpl0zYhLZsdckZ4WpArjHZHuC2J
O/5umGbavG59SI6SYl41Ww1aYRxIKMKsXcVoi/RjVk202EcaSQ/xti8/9ar51CmN
2QtdoTGqud+qJVT1OflcxB+rirrw/ZEGWg8nVOA5A5acqMsPgF6HxjI+aOgZvO+Q
ewQUpjkYamhnIo0JgZR9H7TyhpB6v+emhvd+h1ny+v0nozJPiv3NSjsLJkd8uepa
LT8q43HxySWk7m53t60GRnOS/R9un4XOFRZ+VdTya78hK4ONdBA=
=yC4/
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org