asking again: admin application does not start in Tomcat 5.0.28 on Solaris 9

[Ambarish Chitnis]

Hi All,

I am trying to start my admin application in Tomcat 5.0.28. However, the 
manager application is reporting that it could not start the admin 
application. The tomcat logs are not reporting any exception.


Any tips on how i can debug this problem ? How can i enable verbose 
server logging and where can i see manager web app  logs ? What exactly 
occurs when an application is started ?


Thanks,
Ambarish

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

Re: Admin Application messes up HTTPS Connectors in server.xml

[Peter Rossbach]

Hey Ankit,
I found the bug and hope you can test my fix at cvs head.
Thanks
Peter
Ankit Shah schrieb:
Hi Peter,
Thanks for your response. I double-checked to make sure that secure="true" 
is present. Also, the admin app does write out that attribute. It is 
indeed the missing sslProtocol attribute that's the root of all problems.

Here are the 2 connector elements from configs:
Configured Manually. Works fine:
   
  maxThreads="15" minSpareThreads="5" maxSpareThreads="10"
  enableLookups="false" disableUploadTimeout="true" 
maxKeepAliveRequests="1"
  acceptCount="10" debug="0" scheme="https" secure="true"
  keystorePass="mypassword"
  keystoreFile="c:\path\to\certificate\file"
  clientAuth="false" sslProtocol="TLS" />

Saved by Admin App: Breaks
 
   maxSpareThreads="10" debug="0" maxThreads="15" 
maxKeepAliveRequests="1" minSpareThreads="5
   clientAuth="false" acceptCount="10" /> 

To fix the above so that it works:
 
   maxSpareThreads="10" debug="0" maxThreads="15" 
maxKeepAliveRequests="1" minSpareThreads="5
   clientAuth="false" acceptCount="10" sslProtocol="TLS" /> 

Note that secure="true" is printed out by the admin app
I have been investigating the source code to track the file that is doing 
the job of saving the connector configuration to disk. It should be one of 
the files belonging to the storeconfig.jar classes. As a stop-gap 
arrangement i might tweak the code to force printing that attribute and 
over-ride all checks for just that attribute. (Messy ... but it will work 
until a more thorough investigation is done. Everyone knows how deadlines 
go ... ;) )

Thanks again,
Ankit




[EMAIL PROTECTED] 
05/15/2005 06:55 PM
Please respond to
"Tomcat Users List" <[EMAIL PROTECTED]>

To
tomcat-user@jakarta.apache.org
cc
Subject
tomcat-user Digest 15 May 2005 22:55:08 - Issue 5626
  Message from Peter Rossbach <[EMAIL PROTECTED]> on Sun, 15 May 2005 
20:16:01 +0200 -
To:
Tomcat Users List 
Subject:
Re: Admin Application messes up HTTPS Connectors in server.xml

Hey Ankit,
can it be that you forget the secure="true" attribute at your https 
connector?

I have look inside Http11Protocol code and find this:
  public void setProtocol( String k ) {
   setSecure(true);
   setAttribute("protocol", k);
   }
The sslProtocol="TLS" is the default and the StoreConfig
handler delete all defaults before saving.
This is really a bad side effect, but with correct secure attribute 
setting it works for me!

This https config is also documented at:
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/ssl-howto.html
When problem still exists, please send your working and breaking 
Connector element config from server.xml

Thanks
Peter
Ankit Shah schrieb:
 

Hi,
The Tomcat admin utility doesn't save the HTTPS connectors properly. It 
misses out the 'sslProtocol' attribute and this results in the failed 
connector. Does anyone have a fix around this?

The following is the current state of our server:
Tomcat 5.5.9 with 1.4.2 compatibility add-on.
JRE version 1.4.2_05
My Tests and results:
About certificates:
  We are using our own keytool generated unsigned certificates. 
Everytime i point firefox to the admin app, it will present the 
certificate for my approval. I temporarily accept the certificate for my 
session.

1. Install tomcat, configure an HTTPS connector
  Run the admin app and change a parameter (acceptCount in my case: 
   

 

raised it from 8 to 10) and click Save and then Commit Changes
  Restart tomcat. Restart Firefox. Pointing the browser to the 
   

admin 
 

app homepage will not load anything.
  No Certificate presented!!
2. Manually did a diff on server.xml and server.xml. . The 
difference is the missing 'sslProtocol' attribute. The docs say this 
attribute is optional, but that doesn't seem like the case. Added the 
attribute manually
  sslProtocol="TLS"

  Restart Tomcat. Restart Firefox. Certificate presented. Admin App 
   

 

Homepage Loaded.
3. By seeing the server.xml written out by Admin app, it is clear that 
only attributes with non-default values are written out.
  From the admin app, set SSL Protocol field's value to SSL. Save. 
Commit Changes

  Restart Tomcat. Restart Firefox. NO Certificate Presented. Admin 
App homepage NOT loaded.

  In server.xml - sslProtocol attribute is NOT written out.
I also inspected the logs (Generated by Log4J and logging level set to 
debug)

Upon save:
  bean is updated with sslProtocol's n

Re: Admin Application messes up HTTPS Connectors in server.xml

[Ankit Shah]

Hi Peter,
Thanks for your response. I double-checked to make sure that secure="true" 
is present. Also, the admin app does write out that attribute. It is 
indeed the missing sslProtocol attribute that's the root of all problems.

Here are the 2 connector elements from configs:

Configured Manually. Works fine:



Saved by Admin App: Breaks
   

To fix the above so that it works:
   

Note that secure="true" is printed out by the admin app

I have been investigating the source code to track the file that is doing 
the job of saving the connector configuration to disk. It should be one of 
the files belonging to the storeconfig.jar classes. As a stop-gap 
arrangement i might tweak the code to force printing that attribute and 
over-ride all checks for just that attribute. (Messy ... but it will work 
until a more thorough investigation is done. Everyone knows how deadlines 
go ... ;) )

Thanks again,
Ankit









[EMAIL PROTECTED] 
05/15/2005 06:55 PM
Please respond to
"Tomcat Users List" <[EMAIL PROTECTED]>


To
tomcat-user@jakarta.apache.org
cc

Subject
tomcat-user Digest 15 May 2005 22:55:08 - Issue 5626

  Message from Peter Rossbach <[EMAIL PROTECTED]> on Sun, 15 May 2005 
20:16:01 +0200 -
To:
Tomcat Users List 
Subject:
Re: Admin Application messes up HTTPS Connectors in server.xml

Hey Ankit,

can it be that you forget the secure="true" attribute at your https 
connector?

I have look inside Http11Protocol code and find this:

   public void setProtocol( String k ) {
setSecure(true);
setAttribute("protocol", k);
}

The sslProtocol="TLS" is the default and the StoreConfig
handler delete all defaults before saving.
This is really a bad side effect, but with correct secure attribute 
setting it works for me!

This https config is also documented at:

http://jakarta.apache.org/tomcat/tomcat-5.5-doc/ssl-howto.html

When problem still exists, please send your working and breaking 
Connector element config from server.xml

Thanks
Peter
 
Ankit Shah schrieb:

>Hi,
>The Tomcat admin utility doesn't save the HTTPS connectors properly. It 
>misses out the 'sslProtocol' attribute and this results in the failed 
>connector. Does anyone have a fix around this?
>
>The following is the current state of our server:
>Tomcat 5.5.9 with 1.4.2 compatibility add-on.
>JRE version 1.4.2_05
>
>My Tests and results:
>About certificates:
>We are using our own keytool generated unsigned certificates. 
>Everytime i point firefox to the admin app, it will present the 
>certificate for my approval. I temporarily accept the certificate for my 
>session.
>
>1. Install tomcat, configure an HTTPS connector
>Run the admin app and change a parameter (acceptCount in my case: 

>raised it from 8 to 10) and click Save and then Commit Changes
>
>Restart tomcat. Restart Firefox. Pointing the browser to the 
admin 
>app homepage will not load anything.
>No Certificate presented!!
>
>2. Manually did a diff on server.xml and server.xml. . The 
>difference is the missing 'sslProtocol' attribute. The docs say this 
>attribute is optional, but that doesn't seem like the case. Added the 
>attribute manually
>sslProtocol="TLS"
>
>Restart Tomcat. Restart Firefox. Certificate presented. Admin App 

>Homepage Loaded.
>
>3. By seeing the server.xml written out by Admin app, it is clear that 
>only attributes with non-default values are written out.
>From the admin app, set SSL Protocol field's value to SSL. Save. 
>Commit Changes
>
>Restart Tomcat. Restart Firefox. NO Certificate Presented. Admin 
>App homepage NOT loaded.
>
>In server.xml - sslProtocol attribute is NOT written out.
>
>I also inspected the logs (Generated by Log4J and logging level set to 
>debug)
>
>Upon save:
>bean is updated with sslProtocol's new value
>Upon Commit:
>the list of attributes for the connector doesn't have sslProtocol 

>as one of the attributes that will be written out
>
>Can you help me how i can make admin application available for Tomcat 
>administration by the assigned administrators? What fixes will be needed. 

>If there are any known get-arounds for this.
>
>Thanks in advance for all your help and appreciate your patience in 
>reading through my email.
>
>Ankit
>PS: I can mail you the log files if you want (I have about 11 of them, 
>each is 10M). Thanks once again
>
>
> 

Re: Admin Application messes up HTTPS Connectors in server.xml

[Ankit Shah]

Hi Peter,
Thanks for your response. I double-checked to make sure that secure="true" 
is present. Also, the admin app does write out that attribute. It is 
indeed the missing sslProtocol attribute that's the root of all problems.

Here are the 2 connector elements from configs:

Configured Manually. Works fine:



Saved by Admin App: Breaks
   

To fix the above so that it works:
   

Note that secure="true" is printed out by the admin app

I have been investigating the source code to track the file that is doing 
the job of saving the connector configuration to disk. It should be one of 
the files belonging to the storeconfig.jar classes. As a stop-gap 
arrangement i might tweak the code to force printing that attribute and 
over-ride all checks for just that attribute. (Messy ... but it will work 
until a more thorough investigation is done. Everyone knows how deadlines 
go ... ;) )

Thanks again,
Ankit









[EMAIL PROTECTED] 
05/15/2005 06:55 PM
Please respond to
"Tomcat Users List" <[EMAIL PROTECTED]>


To
tomcat-user@jakarta.apache.org
cc

Subject
tomcat-user Digest 15 May 2005 22:55:08 - Issue 5626

  Message from Peter Rossbach <[EMAIL PROTECTED]> on Sun, 15 May 2005 
20:16:01 +0200 -
To:
Tomcat Users List 
Subject:
Re: Admin Application messes up HTTPS Connectors in server.xml

Hey Ankit,

can it be that you forget the secure="true" attribute at your https 
connector?

I have look inside Http11Protocol code and find this:

   public void setProtocol( String k ) {
setSecure(true);
setAttribute("protocol", k);
}

The sslProtocol="TLS" is the default and the StoreConfig
handler delete all defaults before saving.
This is really a bad side effect, but with correct secure attribute 
setting it works for me!

This https config is also documented at:

http://jakarta.apache.org/tomcat/tomcat-5.5-doc/ssl-howto.html

When problem still exists, please send your working and breaking 
Connector element config from server.xml

Thanks
Peter
 
Ankit Shah schrieb:

>Hi,
>The Tomcat admin utility doesn't save the HTTPS connectors properly. It 
>misses out the 'sslProtocol' attribute and this results in the failed 
>connector. Does anyone have a fix around this?
>
>The following is the current state of our server:
>Tomcat 5.5.9 with 1.4.2 compatibility add-on.
>JRE version 1.4.2_05
>
>My Tests and results:
>About certificates:
>We are using our own keytool generated unsigned certificates. 
>Everytime i point firefox to the admin app, it will present the 
>certificate for my approval. I temporarily accept the certificate for my 
>session.
>
>1. Install tomcat, configure an HTTPS connector
>Run the admin app and change a parameter (acceptCount in my case: 

>raised it from 8 to 10) and click Save and then Commit Changes
>
>Restart tomcat. Restart Firefox. Pointing the browser to the 
admin 
>app homepage will not load anything.
>No Certificate presented!!
>
>2. Manually did a diff on server.xml and server.xml. . The 
>difference is the missing 'sslProtocol' attribute. The docs say this 
>attribute is optional, but that doesn't seem like the case. Added the 
>attribute manually
>sslProtocol="TLS"
>
>Restart Tomcat. Restart Firefox. Certificate presented. Admin App 

>Homepage Loaded.
>
>3. By seeing the server.xml written out by Admin app, it is clear that 
>only attributes with non-default values are written out.
>From the admin app, set SSL Protocol field's value to SSL. Save. 
>Commit Changes
>
>Restart Tomcat. Restart Firefox. NO Certificate Presented. Admin 
>App homepage NOT loaded.
>
>In server.xml - sslProtocol attribute is NOT written out.
>
>I also inspected the logs (Generated by Log4J and logging level set to 
>debug)
>
>Upon save:
>bean is updated with sslProtocol's new value
>Upon Commit:
>the list of attributes for the connector doesn't have sslProtocol 

>as one of the attributes that will be written out
>
>Can you help me how i can make admin application available for Tomcat 
>administration by the assigned administrators? What fixes will be needed. 

>If there are any known get-arounds for this.
>
>Thanks in advance for all your help and appreciate your patience in 
>reading through my email.
>
>Ankit
>PS: I can mail you the log files if you want (I have about 11 of them, 
>each is 10M). Thanks once again
>
>
> 

Re: Admin Application messes up HTTPS Connectors in server.xml

[Peter Rossbach]

Hey Ankit,
can it be that you forget the secure="true" attribute at your https 
connector?

I have look inside Http11Protocol code and find this:
  public void setProtocol( String k ) {
   setSecure(true);
   setAttribute("protocol", k);
   }
The sslProtocol="TLS" is the default and the StoreConfig
handler delete all defaults before saving.
This is really a bad side effect, but with correct secure attribute 
setting it works for me!

This https config is also documented at:
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/ssl-howto.html
When problem still exists, please send your working and breaking 
Connector element config from server.xml

Thanks
Peter
Ankit Shah schrieb:
Hi,
The Tomcat admin utility doesn't save the HTTPS connectors properly. It 
misses out the 'sslProtocol' attribute and this results in the failed 
connector. Does anyone have a fix around this?

The following is the current state of our server:
Tomcat 5.5.9 with 1.4.2 compatibility add-on.
JRE version 1.4.2_05
My Tests and results:
About certificates:
   We are using our own keytool generated unsigned certificates. 
Everytime i point firefox to the admin app, it will present the 
certificate for my approval. I temporarily accept the certificate for my 
session.

1. Install tomcat, configure an HTTPS connector
   Run the admin app and change a parameter (acceptCount in my case: 
raised it from 8 to 10) and click Save and then Commit Changes

   Restart tomcat. Restart Firefox. Pointing the browser to the admin 
app homepage will not load anything.
   No Certificate presented!!

2. Manually did a diff on server.xml and server.xml. . The 
difference is the missing 'sslProtocol' attribute. The docs say this 
attribute is optional, but that doesn't seem like the case. Added the 
attribute manually
   sslProtocol="TLS"

   Restart Tomcat. Restart Firefox. Certificate presented. Admin App 
Homepage Loaded.

3. By seeing the server.xml written out by Admin app, it is clear that 
only attributes with non-default values are written out.
   From the admin app, set SSL Protocol field's value to SSL. Save. 
Commit Changes

   Restart Tomcat. Restart Firefox. NO Certificate Presented. Admin 
App homepage NOT loaded.

   In server.xml - sslProtocol attribute is NOT written out.
I also inspected the logs (Generated by Log4J and logging level set to 
debug)

Upon save:
   bean is updated with sslProtocol's new value
Upon Commit:
   the list of attributes for the connector doesn't have sslProtocol 
as one of the attributes that will be written out

Can you help me how i can make admin application available for Tomcat 
administration by the assigned administrators? What fixes will be needed. 
If there are any known get-arounds for this.

Thanks in advance for all your help and appreciate your patience in 
reading through my email.

Ankit
PS: I can mail you the log files if you want (I have about 11 of them, 
each is 10M). Thanks once again

 


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

Admin Application messes up HTTPS Connectors in server.xml

[Ankit Shah]

Hi,
The Tomcat admin utility doesn't save the HTTPS connectors properly. It 
misses out the 'sslProtocol' attribute and this results in the failed 
connector. Does anyone have a fix around this?

The following is the current state of our server:
Tomcat 5.5.9 with 1.4.2 compatibility add-on.
JRE version 1.4.2_05

My Tests and results:
About certificates:
We are using our own keytool generated unsigned certificates. 
Everytime i point firefox to the admin app, it will present the 
certificate for my approval. I temporarily accept the certificate for my 
session.

1. Install tomcat, configure an HTTPS connector
Run the admin app and change a parameter (acceptCount in my case: 
raised it from 8 to 10) and click Save and then Commit Changes

Restart tomcat. Restart Firefox. Pointing the browser to the admin 
app homepage will not load anything.
No Certificate presented!!

2. Manually did a diff on server.xml and server.xml. . The 
difference is the missing 'sslProtocol' attribute. The docs say this 
attribute is optional, but that doesn't seem like the case. Added the 
attribute manually
sslProtocol="TLS"

Restart Tomcat. Restart Firefox. Certificate presented. Admin App 
Homepage Loaded.

3. By seeing the server.xml written out by Admin app, it is clear that 
only attributes with non-default values are written out.
From the admin app, set SSL Protocol field's value to SSL. Save. 
Commit Changes

Restart Tomcat. Restart Firefox. NO Certificate Presented. Admin 
App homepage NOT loaded.

In server.xml - sslProtocol attribute is NOT written out.

I also inspected the logs (Generated by Log4J and logging level set to 
debug)

Upon save:
bean is updated with sslProtocol's new value
Upon Commit:
the list of attributes for the connector doesn't have sslProtocol 
as one of the attributes that will be written out

Can you help me how i can make admin application available for Tomcat 
administration by the assigned administrators? What fixes will be needed. 
If there are any known get-arounds for this.

Thanks in advance for all your help and appreciate your patience in 
reading through my email.

Ankit
PS: I can mail you the log files if you want (I have about 11 of them, 
each is 10M). Thanks once again

Problem With Tomcat Admin Application

[Farid Izem]

Hi all,

I have installed a new tomcat server 5.0.28 on Linux Slackware 10.
I' m facing a strange problem configuring my tomcat admin webapps.
I wrote my own server.xml to learn how tomcat is working.
I'm fully accessing the tomcat manager and Tomcat Administration.
The Authentication is made using tomcat-users.xml.
i can manage each item of Tomcat Administration except the Service catalina.
i can create groups, roles, users, jdbc, mail sessions but accessing to 
The Service Catalina gives me a http 500 Error Code with the
followings messages :

2005-05-10 22:19:29 ApplicationDispatcher[/admin] Servlet.service()
for servlet admin.service.service_jsp threw exception
javax.servlet.jsp.JspException: Define tag cannot set a null value
at org.apache.struts.taglib.bean.DefineTag.doEndTag(DefineTag.java:272)
at admin.service.service_jsp._jspService(service_jsp.java:237)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at 
org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at 
org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at 
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at 
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.ja

Admin Application doesn't save correctly - Tomcat 5.5.7

[Ankit Shah]

Hi,
We are experiencing a strange problem with the Tomcat admin utility. Upon 
clicking 'Commit Changes', NOT ALL options are written out to the 
server.xml file !! Here is the tag that was messed up:

Before:
 

After:
 

The only changes we did were to add an environment variable for tomcat.

Tomcat Configuration in use:
Tomcat version: 5.5.7 with 1.4.2 compatibility kit
Platform: Win2K
JRE: 1.4.2_05

If anyone has any suggestions/clues as to why this is happenning, please 
do let us know. Also has anyone else encountered similar problems which 
they can share with us for our information, that would be great.

Thanks in advance,
Ankit

Re: Admin application creates duplicate "secure" attribute in server.xml

[Peter Rossbach]

Hello Jeffrey,
I have no time to made a storeconfig backport to the Tomcat 5.0 tree. 
Sorry, the 5.0.x is in some places very
unfriendly. When you want a local workaround look inside 
StandardServer#storeConnector.
The probleme is the storeAttributes method calls for real Connector and 
also for ProtocolHandler
L_1107
---
   writer.print("
   storeAttributes(writer, connector);
  
   if (connector instanceof CoyoteConnector) {
   ProtocolHandler protocolHandler =
   ((CoyoteConnector)connector).getProtocolHandler();
   storeAttributes(writer, protocolHandler);
   }
  
   writer.println(">");

-
What you need is a frontup merge, defaulthandling and renaming of some 
attributes (protocol at ProtocolHandler means sslProtocol at Connector 
Element) ?Arggh, ... very bad, but the 5.5.x Connector is complete 
rewritten and has a nice storeconfig module to handle some bad cases :-)
Implement a better Connector attribute saving algo, send me the code for 
testing

Why you want to wait, Tomat 5.5.9 is really stabler as 5.0.28.
Peter
Jeffrey Barnett schrieb:
Peter,
Many thanks for finding and fixing the bug, however we are currently 
running 5.0.28, and not likely to upgrade until summer.  Can you 
describe enough about the problem that I could track it down and 
create a local fix / work around until then?

Peter Rossbach wrote:
Yes the wrong saving SSL Connector is a bug and I fix it for Tomcat 
5.5.x.

The old StandardServer saving code was strange. The new StoreConfig 
module has
a flexible customizable API to store server.xml and context.xml.

You can activate the new saving module with

  



This listener register a new MBean with more options to save the 
tomcat configurations.

Give 5.5.9 a try ... :-)
Peter
Jeffrey Barnett schrieb:
Mike, unfortunately I'm only gotten better at restoring server.xml 
after it has been corrupted.  You are the first person from the 
tomcat-user list to even confirm that the problem exits on other 
sites.. One consultant I consulted said that they had never heard of 
the problem, but that we were also the first site he had worked with 
that actually used the admin function actively,  By the way, just 
for the record, not only the secure attribute, but also the protocol 
attribute is duplicated, right?  And only on the SSL connector.

Mike Dippold wrote:
I just wanted to check to see if you have figured anything out with 
the tomcat admin ssl duplicate problem.  I have tried it on 5.0.28 
and also 5.5.7 and every time I change a datasource or anything 
else, it corrupts the xml.

Thanks,
Mike Dippold  


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


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




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

Re: Admin application creates duplicate "secure" attribute in server.xml

[Jeffrey Barnett]

Peter,
Many thanks for finding and fixing the bug, however we are currently 
running 5.0.28, and not likely to upgrade until summer.  Can you 
describe enough about the problem that I could track it down and create 
a local fix / work around until then?

Peter Rossbach wrote:
Yes the wrong saving SSL Connector is a bug and I fix it for Tomcat 
5.5.x.

The old StandardServer saving code was strange. The new StoreConfig 
module has
a flexible customizable API to store server.xml and context.xml.

You can activate the new saving module with

  



This listener register a new MBean with more options to save the 
tomcat configurations.

Give 5.5.9 a try ... :-)
Peter
Jeffrey Barnett schrieb:
Mike, unfortunately I'm only gotten better at restoring server.xml 
after it has been corrupted.  You are the first person from the 
tomcat-user list to even confirm that the problem exits on other 
sites.. One consultant I consulted said that they had never heard of 
the problem, but that we were also the first site he had worked with 
that actually used the admin function actively,  By the way, just for 
the record, not only the secure attribute, but also the protocol 
attribute is duplicated, right?  And only on the SSL connector.

Mike Dippold wrote:
I just wanted to check to see if you have figured anything out with 
the tomcat admin ssl duplicate problem.  I have tried it on 5.0.28 
and also 5.5.7 and every time I change a datasource or anything 
else, it corrupts the xml.

Thanks,
Mike Dippold  

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


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

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

Re: Admin application creates duplicate "secure" attribute in server.xml

[Peter Rossbach]

Yes the wrong saving SSL Connector is a bug and I fix it for Tomcat 5.5.x.
The old StandardServer saving code was strange. The new StoreConfig 
module has
a flexible customizable API to store server.xml and context.xml.

You can activate the new saving module with

 



This listener register a new MBean with more options to save the tomcat 
configurations.

Give 5.5.9 a try ... :-)
Peter
Jeffrey Barnett schrieb:
Mike, unfortunately I'm only gotten better at restoring server.xml 
after it has been corrupted.  You are the first person from the 
tomcat-user list to even confirm that the problem exits on other 
sites.. One consultant I consulted said that they had never heard of 
the problem, but that we were also the first site he had worked with 
that actually used the admin function actively,  By the way, just for 
the record, not only the secure attribute, but also the protocol 
attribute is duplicated, right?  And only on the SSL connector.

Mike Dippold wrote:
I just wanted to check to see if you have figured anything out with 
the tomcat admin ssl duplicate problem.  I have tried it on 5.0.28 
and also 5.5.7 and every time I change a datasource or anything else, 
it corrupts the xml.

Thanks,
Mike Dippold   


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


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

AutoReply: Re: Admin application creates duplicate "secure" attribute in server.xml

[j2ee]

Hello tomcat-user@jakarta.apache.org,
 
This refers to your mail with subject as "Re: Admin application creates 
duplicate "secure" attribute in server.xml".
Thank you for sending your CV and registering with A.S. Consultancy Services.
 
Our team will review your CV and match it against current requirements. If your 
profile matches with any ongoing opening, we will contact you by telephone / 
email.
 
We recommend that you update your profile and send us an updated CV whenever 
your contact details or your career path changes, so that your record is 
up-to-date with us.
 
Please be assured that your CV will remain confidential with us and we will 
submit your profile to our clients only after due consultation with you.
 
In case you require any further information please do contact us.
with warm regards,
 
Staffing Team
A.S. Consultancy Services 
#1205, 2nd Main, 2nd Cross, Vijayanagar, Bangalore - 560040, India
Tele - 91 80 2310 9012, Telefax - 91 80 2330 5364, Email - [EMAIL PROTECTED] 
URL: www.asconsultancy.com


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

Re: Admin application creates duplicate "secure" attribute in server.xml

[Jeffrey Barnett]

Mike, unfortunately I'm only gotten better at restoring server.xml after 
it has been corrupted.  You are the first person from the tomcat-user 
list to even confirm that the problem exits on other sites.. One 
consultant I consulted said that they had never heard of the problem, 
but that we were also the first site he had worked with that actually 
used the admin function actively,  By the way, just for the record, not 
only the secure attribute, but also the protocol attribute is 
duplicated, right?  And only on the SSL connector.

Mike Dippold wrote:
I just wanted to check to see if you have figured anything out with the tomcat 
admin ssl duplicate problem.  I have tried it on 5.0.28 and also 5.5.7 and 
every time I change a datasource or anything else, it corrupts the xml.
Thanks,
Mike Dippold 
   
  
 


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

Admin Application

[George Sexton]

I'm hitting the error below with tomcat 5.5.8

This happens when I click on any object contained in a service (Host,
connector, etc). Clicking on a resource and the user database works.

The server.xml is at:

http://www.mhsoftware.com/~gsexton/server.xml

And the admin.xml is:

http://www.mhsoftware.com/~gsexton/admin.xml



 ERROR http-8080-Processor4
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/admin] -
action: Error retrieving attribute debug
 javax.management.AttributeNotFoundException:  Cannot find attribute debug
at
org.apache.commons.modeler.BaseModelMBean.getAttribute(BaseModelMBean.java:3
06)
at
mx4j.server.interceptor.InvokerMBeanServerInterceptor.getAttribute(InvokerMB
eanServerInterceptor.java:244)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMB
eanServerInterceptor.java:135)
at
mx4j.server.interceptor.SecurityMBeanServerInterceptor.getAttribute(Security
MBeanServerInterceptor.java:106)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMB
eanServerInterceptor.java:135)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMB
eanServerInterceptor.java:135)
at
mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.getAttribut
e(ContextClassLoaderMBeanServerInterceptor.java:269)
at
mx4j.server.MX4JMBeanServer.getAttribute(MX4JMBeanServer.java:1002)
at
org.apache.webapp.admin.service.EditServiceAction.perform(EditServiceAction.
java:173)
at org.apache.struts.action.Action.execute(Action.java:420)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProces
sor.java:484)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:178)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
.java:482)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126
)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105
)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:743)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav
a:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo
rkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
at java.lang.Thread.run(Thread.java:534)

George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
 


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

Re: Admin application creates duplicate "secure" attribute in server.xml

[Jeffrey Barnett]

More info:
Apparently the manual change didn't fix things after all.  The server 
starts, and some webapps run, but those using ssl get the following 
error message:

Connection refused when attempting to contact :8443
The full service definition follows:

   
   
   
   
   
   
   
 
   
 
 
 
   
 

Jeffrey Barnett wrote:
We have recently upgraded from Tomcat 4 to Tomcat 5.0.27.  Now 
whenever we use the Admin application to alter webapp context 
parameters the new server.xml that gets written out contains an extra 
'secure="true"' attribute at the end of the ssl , which 
causes the server to fail with a SEVERE: Parse Fatal Error on 
restart.  Removing the extra attribute manually allows the server to 
be started, but is operationally unacceptable.

Where is the extra attribute coming from (is there a template 
somewhere)?  How can we stop this from happening?  Why is a new 
server.xml created at all? (Nothing is changed but the addition of the 
incorrect attribute)

Here is the exception:
Jan 29, 2005 7:30:54 AM org.apache.commons.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 22 column 221: Attribute "secure" 
was already specified for element "Connector".
org.xml.sax.SAXParseException: Attribute "secure" was already 
specified for element "Connector".

And here is the offending element (second attribute highlighted):
   
   

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

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

Use of Admin application creates duplicate "secure" attribute in server.xml

[Jeffrey Barnett]

We have recently upgraded from Tomcat 4 to Tomcat 5.0.27.  Now whenever 
we use the Admin application to alter webapp context parameters the new 
server.xml that gets written out contains an extra 'secure="true"' 
attribute at the end of the ssl , which causes the server to 
fail with a SEVERE: Parse Fatal Error on restart.  Removing the extra 
attribute manually allows the server to be started, but is operationally 
unacceptable.

Where is the extra attribute coming from (is there a template 
somewhere)?  How can we stop this from happening?  Why is a new 
server.xml created at all? (Nothing is changed but the addition of the 
incorrect attribute)

Here is the exception:
Jan 29, 2005 7:30:54 AM org.apache.commons.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 22 column 221: Attribute "secure" was 
already specified for element "Connector".
org.xml.sax.SAXParseException: Attribute "secure" was already specified 
for element "Connector".

And here is the offending element (second attribute highlighted):
   
   

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

Re: Unable to access Tomcat Admin Application

[Punit Duggal]

I now installed 5.0.28. In this, the admin application works as expected. 
Since 5.0.30 is still in beta, looks like its better to use 28 !!!

From: Drew Jorgenson <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" 
To: Tomcat Users List 
Subject: Re: Unable to access Tomcat Admin Application
Date: Fri, 28 Jan 2005 14:57:19 -0800
Does Tomcat come with a full installer on Windows? if not did you
unzip/tar to a FAT or NTFS partition?
On Fri, 2005-01-28 at 12:22, Punit Duggal wrote:
> I  installed Tomcat 5.0.30 on my PC and added the admin role to the
> tomcat-users.xml file.
> When I try to access the admin app using http://localhost:8080/admin 
nothing
> shows up in the browser and here is the error that I get in the cmd 
prompt
> window :
> Jan 28, 2005 12:17:21 PM 
org.apache.catalina.authenticator.FormAuthenticator
> au
> henticate
> WARNING: Unexpected error forwarding to login page
> javax.servlet.ServletException: Cannot find message resources under key
> org.apa
> he.struts.action.MESSAGE
> at
> org.apache.jasper.runtime.PageContextImpl.doHandlePageException(Page
> ontextImpl.java:846)
> at
> org.apache.jasper.runtime.PageContextImpl.handlePageException(PageCo
> textImpl.java:779)
> at admin.login_jsp._jspService(login_jsp.java:115)
> at
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(App
> icationFilterChain.java:252)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(Application
> ilterChain.java:173)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDis
> atcher.java:696)
> at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(Applic
> tionDispatcher.java:474)
>
> Anyone has an idea as to what I am doing wrong ??
>
> Thanks !
>
> _
> FREE pop-up blocking with the new MSN Toolbar  get it now!
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

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

Re: Unable to access Tomcat Admin Application

[Drew Jorgenson]

Does Tomcat come with a full installer on Windows? if not did you
unzip/tar to a FAT or NTFS partition?

On Fri, 2005-01-28 at 12:22, Punit Duggal wrote:
> I  installed Tomcat 5.0.30 on my PC and added the admin role to the 
> tomcat-users.xml file.
> When I try to access the admin app using http://localhost:8080/admin nothing 
> shows up in the browser and here is the error that I get in the cmd prompt 
> window :
> Jan 28, 2005 12:17:21 PM org.apache.catalina.authenticator.FormAuthenticator 
> au
> henticate
> WARNING: Unexpected error forwarding to login page
> javax.servlet.ServletException: Cannot find message resources under key 
> org.apa
> he.struts.action.MESSAGE
> at 
> org.apache.jasper.runtime.PageContextImpl.doHandlePageException(Page
> ontextImpl.java:846)
> at 
> org.apache.jasper.runtime.PageContextImpl.handlePageException(PageCo
> textImpl.java:779)
> at admin.login_jsp._jspService(login_jsp.java:115)
> at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(App
> icationFilterChain.java:252)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(Application
> ilterChain.java:173)
> at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDis
> atcher.java:696)
> at 
> org.apache.catalina.core.ApplicationDispatcher.processRequest(Applic
> tionDispatcher.java:474)
> 
> Anyone has an idea as to what I am doing wrong ??
> 
> Thanks !
> 
> _
> FREE pop-up blocking with the new MSN Toolbar  get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


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

RE: Unable to access Tomcat Admin Application

[Drew Jorgenson]

ok, my bad ;-)

On Fri, 2005-01-28 at 14:48, Caldarale, Charles R wrote:
> > From: Drew Jorgenson [mailto:[EMAIL PROTECTED]
> > Subject: Re: Unable to access Tomcat Admin Application
> > 
> > I don't think admin comes bundled with Tomcat 5 by default, 
> > you need to install it yourself.
> 
> He's using 5.0.30, which includes the admin app in the regular download.  
> It's only the 5.5 series that has a separate download for admin.
> 
>  - 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


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

RE: Unable to access Tomcat Admin Application

[Caldarale, Charles R]

> From: Drew Jorgenson [mailto:[EMAIL PROTECTED]
> Subject: Re: Unable to access Tomcat Admin Application
> 
> I don't think admin comes bundled with Tomcat 5 by default, 
> you need to install it yourself.

He's using 5.0.30, which includes the admin app in the regular download.  It's 
only the 5.5 series that has a separate download for admin.

 - 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Unable to access Tomcat Admin Application

[Drew Jorgenson]

I don't think admin comes bundled with Tomcat 5 by default, you need to
install it yourself.

Drew.

On Fri, 2005-01-28 at 12:22, Punit Duggal wrote:
> I  installed Tomcat 5.0.30 on my PC and added the admin role to the 
> tomcat-users.xml file.
> When I try to access the admin app using http://localhost:8080/admin nothing 
> shows up in the browser and here is the error that I get in the cmd prompt 
> window :
> Jan 28, 2005 12:17:21 PM org.apache.catalina.authenticator.FormAuthenticator 
> au
> henticate
> WARNING: Unexpected error forwarding to login page
> javax.servlet.ServletException: Cannot find message resources under key 
> org.apa
> he.struts.action.MESSAGE
> at 
> org.apache.jasper.runtime.PageContextImpl.doHandlePageException(Page
> ontextImpl.java:846)
> at 
> org.apache.jasper.runtime.PageContextImpl.handlePageException(PageCo
> textImpl.java:779)
> at admin.login_jsp._jspService(login_jsp.java:115)
> at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(App
> icationFilterChain.java:252)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(Application
> ilterChain.java:173)
> at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDis
> atcher.java:696)
> at 
> org.apache.catalina.core.ApplicationDispatcher.processRequest(Applic
> tionDispatcher.java:474)
> 
> Anyone has an idea as to what I am doing wrong ??
> 
> Thanks !
> 
> _
> FREE pop-up blocking with the new MSN Toolbar  get it now! 
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


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

Unable to access Tomcat Admin Application

[Punit Duggal]

I  installed Tomcat 5.0.30 on my PC and added the admin role to the 
tomcat-users.xml file.
When I try to access the admin app using http://localhost:8080/admin nothing 
shows up in the browser and here is the error that I get in the cmd prompt 
window :
Jan 28, 2005 12:17:21 PM org.apache.catalina.authenticator.FormAuthenticator 
au
henticate
WARNING: Unexpected error forwarding to login page
javax.servlet.ServletException: Cannot find message resources under key 
org.apa
he.struts.action.MESSAGE
   at 
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(Page
ontextImpl.java:846)
   at 
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageCo
textImpl.java:779)
   at admin.login_jsp._jspService(login_jsp.java:115)
   at 
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(App
icationFilterChain.java:252)
   at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(Application
ilterChain.java:173)
   at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDis
atcher.java:696)
   at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(Applic
tionDispatcher.java:474)

Anyone has an idea as to what I am doing wrong ??
Thanks !
_
FREE pop-up blocking with the new MSN Toolbar – get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

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

RE: Tomcat 5.5.4 Admin application deploy

[Jeff Urlwin]

> 
> > From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> > Subject: RE: Tomcat 5.5.4 Admin application deploy
> > 
> > It must have been the missing commons-modeler.jar which
> > caused it to not work and when I tried fixing it, I moved 
> > it around.  So, the lack of commons-modeler.jar is still 
> > an issue.
> 
> The commons-modeler.jar is distributed in server/lib as part 
> of the main Tomcat download.  I didn't have to do anything 
> with it, so I still don't see the problem there.

I'm betting that the server/lib path is only for applications which are in 
server/webapps
and doesn't apply to applications in webapps.  My fault for not copying the 
install
correctly.

> 
> > Also, I used the installer to install Tomcat in the first
> > place, which alllows you to pick your directory tree and 
> > suggests something under "Program Files", which is still a
> > pet-peeve for me.
> 
> Which is one reason I don't use it (the main one being it's 
> platform-specific, so is of no use on most of the systems I 
> play with).

I'm a Tomcat newbie, actually (couldn't you tell :), but I've been using 
Oracle's 9iAS for
the last 4 years.  So, I used what should have been the simplest to get 
started...  Oh
well.  Thanks for your help!

Regards,

Jeff



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

RE: Tomcat 5.5.4 Admin application deploy

[Caldarale, Charles R]

> From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 5.5.4 Admin application deploy
> 
> It must have been the missing commons-modeler.jar which 
> caused it to not work and when I tried fixing it, I moved 
> it around.  So, the lack of commons-modeler.jar is still 
> an issue.

The commons-modeler.jar is distributed in server/lib as part of the main Tomcat 
download.  I didn't have to do anything with it, so I still don't see the 
problem there.

> Also, I used the installer to install Tomcat in the first 
> place, which alllows you to pick your directory tree and 
> suggests something under "Program Files", which is still a
> pet-peeve for me.

Which is one reason I don't use it (the main one being it's platform-specific, 
so is of no use on most of the systems I play with).

 - 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat 5.5.4 Admin application deploy

[Jeff Urlwin]

> 
> 
> I think your mistake is copying
>   jakarta-tomcat-5.5.4\server\webapp\admin\*.*
> to
>   $CATALINA_HOME\webapp\admin
> 
> You should copy it to the correct location:
>   $CATALINA_HOME\server\webapp\admin
> 
> The admin.xml file expects it to be under server/webapps, see:
>privileged="true" antiResourceLocking="false" antiJARLocking="false">
> 
> 
> 
>   
> 
> 

Thanks -- you are right.  That did work.  Strange.  It thought it was missing 
the Registry
class, but now that I put it in the right place it's not even asking for the
commons-modeler.  I just moved it out of the common\lib directory and it still 
works.

Regards,

Jeff

> HTH - Richard
> 
> 
> -Original Message-
> From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 20, 2005 10:20 AM
> To: tomcat-user@jakarta.apache.org
> Subject: Tomcat 5.5.4 Admin application deploy
> 
> 
> I'm trying a new Tomcat installation (5.5.4) under Windows XP 
> SP2.  I googled for this, but didn't find an answer.
> 
> Tomcat comes up fine and the management application comes up fine.
> 
> I have copied all of the 
> jakarta-tomcat-5.5.4\server\webapp\admin\*.* to my 
> $CATALINA_HOME\webapp\admin and restarted Tomcat.
> 
> When I tried to run the web app, I get the log as per below.  
> I've solved this by downloading commons-modeler.jar and 
> putting it into my $CATALINA_HOME\common\lib directory.  Can 
> this be included in future releases to save others the problems I had?
> 
> Thanks,
> 
> Jeff
> 
> 
> SEVERE: End event threw error
> java.lang.NoClassDefFoundError: org/apache/commons/modeler/Registry
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)
>   at java.lang.Class.getMethod0(Class.java:2611)
>   at java.lang.Class.getMethod(Class.java:1579)
>   at 
> org.apache.commons.beanutils.MethodUtils.getMatchingAccessible
> Method(Met
> hodUtils.java:535)
>   at 
> org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUt
> ils.java:2
> 09)
>   at
> org.apache.commons.digester.CallMethodRule.end(CallMethodRule.
> java:505)
>   at org.apache.commons.digester.Rule.end(Rule.java:276)
>   at 
> org.apache.commons.digester.Digester.endElement(Digester.java:1058)
>   at 
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.e
> ndElement(
> AbstractSAXParser.
> java:633)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerIm
> pl.scanEnd
> Element(XMLNSDocum
> entScannerImpl.java:719)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentSca
> nnerImpl$F
> ragmentContentDisp
> atcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentSca
> nnerImpl.s
> canDocument(XMLDoc
> umentFragmentScannerImpl.java:368)
>   at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.
> parse(XML1
> 1Configuration.jav
> a:834)
>   at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.
> parse(XML1
> 1Configuration.jav
> a:764)
>   at 
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XML
> Parser.jav
> a:148)
>   at 
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.p
> arse(Abstr
> actSAXParser.java:
> 1242)
>   at 
> org.apache.commons.digester.Digester.parse(Digester.java:1567)
>   at 
> org.apache.struts.action.ActionServlet.initServlet(ActionServl
> et.java:11
> 12)
>   at 
> org.apache.struts.action.ActionServlet.init(ActionServlet.java:324)
>   at
> org.apache.webapp.admin.ApplicationServlet.init(ApplicationSer
> vlet.java:
> 105)
>   at javax.servlet.GenericServlet.init(GenericServlet.java:211)
>   at 
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardW
> rapper.jav
> a:1053)
>   at 
> org.apache.catalina.core.StandardWrapper.allocate(StandardWrap
> per.java:7
> 11)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.invoke(Applicat
> ionDispatc
> her.java:643)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.doInclude(Appli
> cationDisp
> atcher.java:541)
>   at 
> org.apache.catalina.core.ApplicationDispatcher.include(Applica
> tionDispat
> cher.java:501)
>   at admin.login_jsp._jspService(login_jsp.java:69)
>   at 
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
>   at javax.servlet.http.HttpServlet.service(Http

RE: Tomcat 5.5.4 Admin application deploy

[Jeff Urlwin]

> 
> 
> > From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> > Subject: RE: Tomcat 5.5.4 Admin application deploy
> > 
> > > 1) Download the tomcat 5.5.4
> > > 2) Download the Admin tool 5.5.4
> > > 3) Unzip the tomcat file
> > > 4) Unzip the admin file
> > > 5) Copy the contents of the admin folder into the folder of tomcat
> > > 6) edit the tomcat-user.xml adding the needed user with admin role
> > > 7) start tomcat
> 
> Actually, if you use the default unzip folder, step 5 is 
> unnecessary.  I just did a clean install of 5.5.7 on WinXP to verify.
> 
> > Did you have commons-modeler somewhere in your class path?
> > Other than that, that's exactly what I did.
> 
> Not quite: your original message said that you put admin under
>%CATALINA_HOME%\webapps
> but the admin app expects to be in
>%CATALINA_HOME%\server\webapps
> which is also where the manager app resides.
> 
> The admin unzip also updates
>%CATALINA_HOME%\conf\Catalina\localhost
> with the admin.xml file.

Ok -- that makes the Mbean messages go away, which was my next task (THANKS!).  
At first,
I had trouble putting the app under server\webapps.  I've cleaned it and done 
it again and
it works.  It must have been the missing commons-modeler.jar which caused it to 
not work
and when I tried fixing it, I moved it around.  So, the lack of 
commons-modeler.jar is
still an issue.

Also, I used the installer to install Tomcat in the first place, which alllows 
you to pick
your directory tree and suggests something under "Program Files", which is 
still a
pet-peeve for me.

Thanks and Regards,

Jeff




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

RE: Tomcat 5.5.4 Admin application deploy

[Richard Mixon (qwest)]

I think your mistake is copying
  jakarta-tomcat-5.5.4\server\webapp\admin\*.*
to
  $CATALINA_HOME\webapp\admin

You should copy it to the correct location:
  $CATALINA_HOME\server\webapp\admin

The admin.xml file expects it to be under server/webapps, see:
  



  


HTH - Richard


-Original Message-
From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 20, 2005 10:20 AM
To: tomcat-user@jakarta.apache.org
Subject: Tomcat 5.5.4 Admin application deploy


I'm trying a new Tomcat installation (5.5.4) under Windows XP SP2.  I
googled for this,
but didn't find an answer.

Tomcat comes up fine and the management application comes up fine.

I have copied all of the jakarta-tomcat-5.5.4\server\webapp\admin\*.* to
my
$CATALINA_HOME\webapp\admin and restarted Tomcat.

When I tried to run the web app, I get the log as per below.  I've
solved this by
downloading commons-modeler.jar and putting it into my
$CATALINA_HOME\common\lib
directory.  Can this be included in future releases to save others the
problems I had?

Thanks,

Jeff


SEVERE: End event threw error
java.lang.NoClassDefFoundError: org/apache/commons/modeler/Registry
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)
at java.lang.Class.getMethod0(Class.java:2611)
at java.lang.Class.getMethod(Class.java:1579)
at
org.apache.commons.beanutils.MethodUtils.getMatchingAccessibleMethod(Met
hodUtils.java:535)
at
org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:2
09)
at
org.apache.commons.digester.CallMethodRule.end(CallMethodRule.java:505)
at org.apache.commons.digester.Rule.end(Rule.java:276)
at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(
AbstractSAXParser.
java:633)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEnd
Element(XMLNSDocum
entScannerImpl.java:719)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$F
ragmentContentDisp
atcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.s
canDocument(XMLDoc
umentFragmentScannerImpl.java:368)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
1Configuration.jav
a:834)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML1
1Configuration.jav
a:764)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.jav
a:148)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Abstr
actSAXParser.java:
1242)
at org.apache.commons.digester.Digester.parse(Digester.java:1567)
at
org.apache.struts.action.ActionServlet.initServlet(ActionServlet.java:11
12)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:324)
at
org.apache.webapp.admin.ApplicationServlet.init(ApplicationServlet.java:
105)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav
a:1053)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:7
11)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc
her.java:643)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDisp
atcher.java:541)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispat
cher.java:501)
at admin.login_jsp._jspService(login_jsp.java:69)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.ja
va:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:157)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc
her.java:674)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(Applicatio
nDispatcher.java:4
65)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp
atcher.java:400)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispat
cher.java:303)
at
org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAut
henticator.java:21
5)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator
Base.java:446)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:

RE: Tomcat 5.5.4 Admin application deploy

[Caldarale, Charles R]

> From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 5.5.4 Admin application deploy
> 
> > 1) Download the tomcat 5.5.4
> > 2) Download the Admin tool 5.5.4
> > 3) Unzip the tomcat file
> > 4) Unzip the admin file
> > 5) Copy the contents of the admin folder into the folder of tomcat
> > 6) edit the tomcat-user.xml adding the needed user with admin role
> > 7) start tomcat

Actually, if you use the default unzip folder, step 5 is unnecessary.  I just 
did a clean install of 5.5.7 on WinXP to verify.

> Did you have commons-modeler somewhere in your class path?  
> Other than that, that's exactly what I did.

Not quite: your original message said that you put admin under
   %CATALINA_HOME%\webapps
but the admin app expects to be in
   %CATALINA_HOME%\server\webapps
which is also where the manager app resides.

The admin unzip also updates
   %CATALINA_HOME%\conf\Catalina\localhost
with the admin.xml file.

 - 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat 5.5.4 Admin application deploy

[Jeff Urlwin]

> 
> > And when you unzip the admin download, it's automatically 
> put in the 
> > proper place for execution.  So why did you try to move it 
> somewhere 
> > else?
> 
> It depends by where you are unzipping the downloaded admin tool. 
> I have done this operation exactly today following this steps 
> (I was using a linux server, but I think is not important):
> 1) Download the tomcat 5.5.4
> 2) Download the Admin tool 5.5.4
> 3) Unzip the tomcat file
> 4) Unzip the admin file
> 5) Copy the contents of the admin folder into the folder of tomcat
> 6) edit the tomcat-user.xml adding the needed user with admin role
> 7) start tomcat
> 
> this work for me, bye

Did you have commons-modeler somewhere in your class path?  Other than that, 
that's
exactly what I did.

Jeff
 


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

RE: Tomcat 5.5.4 Admin application deploy

[Jeff Urlwin]

> 
> > From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> > Subject: RE: Tomcat 5.5.4 Admin application deploy
> > 
> > The admin application is not included in the newer tomcat
> > distributions, so it has to be installed separately.
> 
> And when you unzip the admin download, it's automatically put 
> in the proper place for execution.  So why did you try to 
> move it somewhere else?

Because the path in the zip is jakarta-tomcat-5.5.4 and my install path is 
c:\java\Tomcat
5.5, which is different. 

Jeff
 


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

Re: Tomcat 5.5.4 Admin application deploy

[Omar Adobati]

> And when you unzip the admin download, it's automatically put in the proper 
> place for execution.  So why did you try to move it somewhere else?

It depends by where you are unzipping the downloaded admin tool. 
I have done this operation exactly today following this steps (I was
using a linux server, but I think is not important):
1) Download the tomcat 5.5.4
2) Download the Admin tool 5.5.4
3) Unzip the tomcat file
4) Unzip the admin file
5) Copy the contents of the admin folder into the folder of tomcat
6) edit the tomcat-user.xml adding the needed user with admin role
7) start tomcat

this work for me, bye

-- 
Adobati Omar
[EMAIL PROTECTED]

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

RE: Tomcat 5.5.4 Admin application deploy

[Caldarale, Charles R]

> From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> Subject: RE: Tomcat 5.5.4 Admin application deploy
> 
> The admin application is not included in the newer tomcat 
> distributions, so it has to be installed separately.

And when you unzip the admin download, it's automatically put in the proper 
place for execution.  So why did you try to move it somewhere else?

 - 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat 5.5.4 Admin application deploy

[Jeff Urlwin]

> 
> 
> > From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> > Subject: Tomcat 5.5.4 Admin application deploy
> > 
> > I have copied all of the
> > jakarta-tomcat-5.5.4\server\webapp\admin\*.* to my
> > $CATALINA_HOME\webapp\admin and restarted Tomcat.
> 
> Why?
Why what?  
Restart Tomcat or copied the files?  The admin application is not included in 
the newer
tomcat distributions, so it has to be installed separately.

Jeff

> 
>  - Chuck
>


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

RE: Tomcat 5.5.4 Admin application deploy

[Caldarale, Charles R]

> From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> Subject: Tomcat 5.5.4 Admin application deploy
> 
> I have copied all of the 
> jakarta-tomcat-5.5.4\server\webapp\admin\*.* to my
> $CATALINA_HOME\webapp\admin and restarted Tomcat.

Why?

 - 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 5.5.4 Admin application deploy

[Jeff Urlwin]

I'm trying a new Tomcat installation (5.5.4) under Windows XP SP2.  I googled 
for this,
but didn't find an answer.  

Tomcat comes up fine and the management application comes up fine.

I have copied all of the jakarta-tomcat-5.5.4\server\webapp\admin\*.* to my
$CATALINA_HOME\webapp\admin and restarted Tomcat.

When I tried to run the web app, I get the log as per below.  I've solved this 
by
downloading commons-modeler.jar and putting it into my $CATALINA_HOME\common\lib
directory.  Can this be included in future releases to save others the problems 
I had?

Thanks,

Jeff


SEVERE: End event threw error
java.lang.NoClassDefFoundError: org/apache/commons/modeler/Registry
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2365)
at java.lang.Class.getMethod0(Class.java:2611)
at java.lang.Class.getMethod(Class.java:1579)
at
org.apache.commons.beanutils.MethodUtils.getMatchingAccessibleMethod(MethodUtils.java:535)
at 
org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:209)
at 
org.apache.commons.digester.CallMethodRule.end(CallMethodRule.java:505)
at org.apache.commons.digester.Rule.end(Rule.java:276)
at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.
java:633)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocum
entScannerImpl.java:719)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDisp
atcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDoc
umentFragmentScannerImpl.java:368)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.jav
a:834)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.jav
a:764)
at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:
1242)
at org.apache.commons.digester.Digester.parse(Digester.java:1567)
at 
org.apache.struts.action.ActionServlet.initServlet(ActionServlet.java:1112)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:324)
at 
org.apache.webapp.admin.ApplicationServlet.init(ApplicationServlet.java:105)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at 
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1053)
at 
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:711)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:643)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:541)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:501)
at admin.login_jsp._jspService(login_jsp.java:69)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja
va:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:674)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:4
65)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:400)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:303)
at
org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:21
5)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Pr
otocol.java:731)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.jav
a:80)
at
org.apache.tomcat.util.threads

Re: Problems whith admin application and users management

[fmancini]

Thank you so much. Your're right! Perhaps the minimal
configuration was too much minimal...
Thanks to anyone who has looked for this problem too.

Enjoy your life,

--- Hassan Schroeder <[EMAIL PROTECTED]> wrote:

> Shapira, Yoav wrote:
> 
> >>I'm using the minimal server config xml file and
> sha
> >>for users' password encryption.
> 
> > This is probably the cause: a misconfiguration
> somewhere along the way.
> 
> The "minimal" caught my eye this morning and I
> realized that I'd
> also used it as the basis for my server.xml -- it's
> missing these
> two lines found in the "full-figured" example
> server.xml file :-)
> 
> 
className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
> 
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
> 
> Add, restart, admin app is now happy...
> 
> -- 
> Hassan Schroeder -
> [EMAIL PROTECTED]
> Webtuitive Design ===  (+1) 408-938-0567   ===
> http://webtuitive.com
> 
>dream.  code.
> 
> 
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 


=
[--~~
fmancini
   ~~--]



__ 
Do you Yahoo!? 
Dress up your holiday email, Hollywood style. Learn more. 
http://celebrity.mail.yahoo.com

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

Re: Problems whith admin application and users management

[Hassan Schroeder]

Shapira, Yoav wrote:
I'm using the minimal server config xml file and sha
for users' password encryption.

This is probably the cause: a misconfiguration somewhere along the way.
The "minimal" caught my eye this morning and I realized that I'd
also used it as the basis for my server.xml -- it's missing these
two lines found in the "full-figured" example server.xml file :-)


Add, restart, admin app is now happy...
--
Hassan Schroeder - [EMAIL PROTECTED]
Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com
  dream.  code.

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

Re: Problems whith admin application and users management

[fzlists]

Hey thanks Hassan!  I was lurking, but this thread caught my eye because I 
recently upgraded Tomcat and for the first time decided to use the admin app, 
and I had this very problem.  Your solution solved it because I did basically 
the same thing, I started with minimal.xml and put in just what I needed for my 
apps, so I didn't have these entries.  Cool!

-- 
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com

On Mon, December 13, 2004 10:13 am, Hassan Schroeder said:
> Shapira, Yoav wrote:
> 
>>>I'm using the minimal server config xml file and sha
>>>for users' password encryption.
> 
>> This is probably the cause: a misconfiguration somewhere along the way.
> 
> The "minimal" caught my eye this morning and I realized that I'd
> also used it as the basis for my server.xml -- it's missing these
> two lines found in the "full-figured" example server.xml file :-)
> 
>  className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
>  className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
> 
> Add, restart, admin app is now happy...
> 
> --
> Hassan Schroeder - [EMAIL PROTECTED]
> Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com
> 
>dream.  code.
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

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

RE: Problems whith admin application and users management

[Shapira, Yoav]

Hola,

>configuration in admin webapp: if I click on any
>element under "Users definition" in the tree on the
>left pane I got this error message:
>
>"Error retrieving attribute users."
>[Exception shown at bottom]

It works for me (with the default, out-of-the-box everything) on Tomcat
5.5.6-alpha.  Try this release.

>I'm using the minimal server config xml file and sha
>for users' password encryption.

This is probably the cause: a misconfiguration somewhere along the way.

Yoav Shapira http://www.yoavshapira.com




This e-mail, including any attachments, is a confidential business 
communication, and may contain information that is confidential, proprietary 
and/or privileged.  This e-mail is intended only for the individual(s) to whom 
it is addressed, and may not be saved, copied, printed, disclosed or used by 
anyone else.  If you are not the(an) intended recipient, please immediately 
delete this e-mail from your computer system and notify the sender.  Thank you.


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

RE: Problems whith admin application and users management

[fmancini]

No. I've just downloaded it and placed the files under
the appropriate directories in tomcat installation
dir.

[--~~
fmancini
   ~~--]

--- "Kelly, Steve" <[EMAIL PROTECTED]>
wrote:

> Did you have to do anything in particular to get the
> 'admin' application
> to work. I and a number of other subscribers to this
> forum cannot even
> get into 'admin'. Even after downloading the
> separate admin webapp when
> I click on it I simply get a message saying I need
> to download and
> install it. 
> 
> Steve.  
> 
> -Original Message-
> From: fmancini [mailto:[EMAIL PROTECTED] 
> Sent: 12 December 2004 18:58
> To: [EMAIL PROTECTED]
> Subject: Problems whith admin application and users
> management
> 
> Hi everybody,
> I'm running admin webapp using Tomcat5.5.4 [both
> downloaded yesterday].
> Everything seems to work except the users
> configuration in admin webapp:
> if I click on any element under "Users definition"
> in the tree on the
> left pane I got this error message:
> 
> "Error retrieving attribute users."
> [Exception shown at bottom]
> 
> I'm using the minimal server config xml file and sha
> for users' password
> encryption.
> 
> Has anyone the same problem?
> Thank you in advance,
> Enjoy your life.
> 
> fstmncn
> 
>  exception 
> SEVERE: action: Error retrieving attribute users
> javax.management.InstanceNotFoundException:
> Users:type=UserDatabase,database=Use
> rDatabase
> at
>
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Defaul
> tMBeanServerInterceptor.java:1010)
> at
>
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(De
> faultMBeanServerInterceptor.java:627)
> at
>
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.ja
> va:659)
> at
>
org.apache.webapp.admin.users.UserUtils.getUsersForm(UserUtils.java:1
> 12)
> at
>
org.apache.webapp.admin.users.ListUsersAction.execute(ListUsersAction
> .java:105)
> at
>
org.apache.struts.action.RequestProcessor.processActionPerform(Reques
> tProcessor.java:421)
> at
>
org.apache.struts.action.RequestProcessor.process(RequestProcessor.ja
> va:226)
> at
>
org.apache.struts.action.ActionServlet.process(ActionServlet.java:116
> 4)
> at
>
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
> at
>
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at
>
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:237)
> at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:157)
> at
>
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
> alve.java:214)
> at
>
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
> alve.java:178)
> at
>
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
> torBase.java:482)
> at
>
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
> ava:126)
> at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
> ava:105)
> at
>
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
> ve.java:107)
> at
>
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
> a:148)
> at
>
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
> :825)
> at
>
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
> ssConnection(Http11Protocol.java:731)
> at
>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
> int.java:526)
> at
>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
> lowerWorkerThread.java:80)
> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
> ool.java:684)
> at java.lang.Thread.run(Thread.java:595)
> 
> 
>   
> __
> Do you Yahoo!? 
> Send a seasonal email greeting and help others. Do
> good. 
> http://celebrity.mail.yahoo.com
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

Re: Problems whith admin application and users management

[Hassan Schroeder]

fmancini wrote:
I'm running admin webapp using Tomcat5.5.4 

Everything seems to work except the users
configuration in admin webapp: if I click on any
element under "Users definition" in the tree on the
left pane I got this error message:
FWIW, I get the same error -- haven't cared enough to troubleshoot
it yet :-) but I'm also using TC5.5.4 w/JDK1.5.0...
 exception 
SEVERE: action: Error retrieving attribute users
javax.management.InstanceNotFoundException:
Users:type=UserDatabase,database=Use
rDatabase
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Defaul
tMBeanServerInterceptor.java:1010)
--
Hassan Schroeder - [EMAIL PROTECTED]
Webtuitive Design ===  (+1) 408-938-0567   === http://webtuitive.com
  dream.  code.

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

RE: Problems whith admin application and users management

[Kelly, Steve]

Did you have to do anything in particular to get the 'admin' application
to work. I and a number of other subscribers to this forum cannot even
get into 'admin'. Even after downloading the separate admin webapp when
I click on it I simply get a message saying I need to download and
install it. 

Steve.  

-Original Message-
From: fmancini [mailto:[EMAIL PROTECTED] 
Sent: 12 December 2004 18:58
To: [EMAIL PROTECTED]
Subject: Problems whith admin application and users management

Hi everybody,
I'm running admin webapp using Tomcat5.5.4 [both downloaded yesterday].
Everything seems to work except the users configuration in admin webapp:
if I click on any element under "Users definition" in the tree on the
left pane I got this error message:

"Error retrieving attribute users."
[Exception shown at bottom]

I'm using the minimal server config xml file and sha for users' password
encryption.

Has anyone the same problem?
Thank you in advance,
Enjoy your life.

fstmncn

 exception 
SEVERE: action: Error retrieving attribute users
javax.management.InstanceNotFoundException:
Users:type=UserDatabase,database=Use
rDatabase
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Defaul
tMBeanServerInterceptor.java:1010)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(De
faultMBeanServerInterceptor.java:627)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.ja
va:659)
at
org.apache.webapp.admin.users.UserUtils.getUsersForm(UserUtils.java:1
12)
at
org.apache.webapp.admin.users.ListUsersAction.execute(ListUsersAction
.java:105)
at
org.apache.struts.action.RequestProcessor.processActionPerform(Reques
tProcessor.java:421)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.ja
va:226)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:116
4)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
torBase.java:482)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:825)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:731)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:526)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Thread.java:595)



__
Do you Yahoo!? 
Send a seasonal email greeting and help others. Do good. 
http://celebrity.mail.yahoo.com

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



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

Problems whith admin application and users management

[fmancini]

Hi everybody,
I'm running admin webapp using Tomcat5.5.4 [both
downloaded yesterday].
Everything seems to work except the users
configuration in admin webapp: if I click on any
element under "Users definition" in the tree on the
left pane I got this error message:

"Error retrieving attribute users."
[Exception shown at bottom]

I'm using the minimal server config xml file and sha
for users' password encryption.

Has anyone the same problem?
Thank you in advance,
Enjoy your life.

fstmncn

 exception 
SEVERE: action: Error retrieving attribute users
javax.management.InstanceNotFoundException:
Users:type=UserDatabase,database=Use
rDatabase
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(Defaul
tMBeanServerInterceptor.java:1010)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(De
faultMBeanServerInterceptor.java:627)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.ja
va:659)
at
org.apache.webapp.admin.users.UserUtils.getUsersForm(UserUtils.java:1
12)
at
org.apache.webapp.admin.users.ListUsersAction.execute(ListUsersAction
.java:105)
at
org.apache.struts.action.RequestProcessor.processActionPerform(Reques
tProcessor.java:421)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.ja
va:226)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:116
4)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:214)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
torBase.java:482)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:825)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:731)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:526)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Thread.java:595)



__ 
Do you Yahoo!? 
Send a seasonal email greeting and help others. Do good. 
http://celebrity.mail.yahoo.com

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

Help installing the Admin Application

[Venkat & Radha Venkataramanan]

Hello:

I downloaded the 5.5.5Admin zip file and copied the different files into the
appropriate directories. But I don't see the Admin application listed in the
Tomcat Web Application Manager. When I click on the first application which
is displayed as /, I see the Jakarta default page.

When I click on the Tomcat Administration link on this page, I get a
message, "Tomcat's administration web application is no longer installed by
default. Download and install the "admin" package to use it."

Is there more to installing the Admin application?

Thanks.

venkat



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

Re: Problem with Admin Application (SOLVED)...

[Quinton Delpeche]

On Tuesday 23 November 2004 15:43, Quinton Delpeche wrote:

Hi,

For those that are interested I manage to solve this problem last night.

This happens because of incorrect permissions on the admin.xml stored 
in /etc/tomcat5/base/Catalina/localhost/ directory.

By default SuSE 9.2 sets the attributes as follows:
-rw-r-  1 root   tomcat 862 Oct  5 03:20 admin.xml
-rw-rw  1 root   tomcat 322 Nov 18 16:15 manager.xml

I mereley changed it to:
-rw-rw  1 root   tomcat 862 Oct  5 03:20 admin.xml

And everything started working properly again.

I wonder if SuSE is aware of this bug?

Q
-- 
Quinton Delpeche
Internal Systems Developer
Softline VIP

Telephone: +27 12 420 7000
Direct:+27 12 420 7007
Facsimile: +27 12 420 7344

http://www.vippayroll.co.za/

The more laws and order are made prominent, the more thieves and
robbers there will be.
-- Lao Tsu


pgpxcF5uLAyWI.pgp
Description: PGP signature

RE: Problem with Admin Application...

[Shapira, Yoav]

Hi,
If you post the complete stack trace from the log that accompanies this
500 error, we might be able to help more.  Without it, it's fairly
hopeless.

The admin webapp works out of the box for me ;)

Yoav Shapira http://www.yoavshapira.com


>-Original Message-
>From: Quinton Delpeche [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, November 23, 2004 8:43 AM
>To: [EMAIL PROTECTED]
>Subject: Problem with Admin Application...
>
>Hi everybody... ...again. :p
>
>In my forays to fix my Mail problem and I have found another strange
one.
>
>For some unknown reason the changes I make manually in the server.xml
file
>are
>never reflected in the Admin Application and visa versa.
>
>I have also noted that when I click commit changes I get the following
>error
>in the top frame:
>
>
>HTTP Status 500 - Error invoking operation storeConfig
>
>type Status report
>
>message Error invoking operation storeConfig
>
>description The server encountered an internal error (Error invoking
>operation
>storeConfig) that prevented it from fulfilling this request.
>Apache Tomcat/5.0
>
>
>
>Q
>--
>Quinton Delpeche
>Internal Systems Developer
>Softline VIP
>
>Telephone: +27 12 420 7000
>Direct:+27 12 420 7007
>Facsimile: +27 12 420 7344
>
>http://www.vippayroll.co.za/
>
>"I'd love to go out with you, but my favorite commercial is on TV."



This e-mail, including any attachments, is a confidential business 
communication, and may contain information that is confidential, proprietary 
and/or privileged.  This e-mail is intended only for the individual(s) to whom 
it is addressed, and may not be saved, copied, printed, disclosed or used by 
anyone else.  If you are not the(an) intended recipient, please immediately 
delete this e-mail from your computer system and notify the sender.  Thank you.


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

Problem with Admin Application...

[Quinton Delpeche]

Hi everybody... ...again. :p

In my forays to fix my Mail problem and I have found another strange one.

For some unknown reason the changes I make manually in the server.xml file are 
never reflected in the Admin Application and visa versa.

I have also noted that when I click commit changes I get the following error 
in the top frame:


HTTP Status 500 - Error invoking operation storeConfig

type Status report

message Error invoking operation storeConfig

description The server encountered an internal error (Error invoking operation 
storeConfig) that prevented it from fulfilling this request.
Apache Tomcat/5.0



Q
-- 
Quinton Delpeche
Internal Systems Developer
Softline VIP

Telephone: +27 12 420 7000
Direct:+27 12 420 7007
Facsimile: +27 12 420 7344

http://www.vippayroll.co.za/

"I'd love to go out with you, but my favorite commercial is on TV."


pgpUk0caxaeY0.pgp
Description: PGP signature

Re: Tomcat 5 admin application "403"

[Raymond Blum]

D-UH!

Thanks!  I had been using the "tomcat" role.

On Apr 6, 2004, at 10:07 PM, Parsons Technical Services wrote:

Raymond,

You have user names and passwords defined. Now for each of these did 
you
also define the role?

For a user to access the administration page the role of admin must be 
added
for that person.
One thing, is if you did add roles, is to check the syntax. Try 
setting up a
user with only the role of admin.

Are you using the .xml file or a database?

Doug
www.parsonstechnical.com
- Original Message -
From: "Raymond Blum" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 06, 2004 9:59 PM
Subject: Tomcat 5 admin application "403"

Hi
   I've installed Tomcat 5.0.19 on MacOSX 10.3 and all is well 
EXCEPT...
(of course)
When I try to get to the admin application, the login page comes up
fine. If I enter a username and password NOT defined in
conf/tomcat-users.xml I get an "invalid username..." page (as I 
should)
BUT when I enter a valid user and password I get a "403" (forbidden)
page with the description
"Access to the specified resource (Access to the requested resource 
has
been denied) has been forbidden."

I've checked permissions in Unix, Googled like crazy and looked in
catalina.out for any error msgs.  An admin log file is not being
created in logs/
Any help GREATLY appreciated
TIA
---Raymond


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


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

Re: Tomcat 5 admin application "403"

[Parsons Technical Services]

Raymond,

You have user names and passwords defined. Now for each of these did you
also define the role?

For a user to access the administration page the role of admin must be added
for that person.
One thing, is if you did add roles, is to check the syntax. Try setting up a
user with only the role of admin.

Are you using the .xml file or a database?

Doug
www.parsonstechnical.com


- Original Message - 
From: "Raymond Blum" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 06, 2004 9:59 PM
Subject: Tomcat 5 admin application "403"


> Hi
>I've installed Tomcat 5.0.19 on MacOSX 10.3 and all is well EXCEPT...
> (of course)
> When I try to get to the admin application, the login page comes up
> fine. If I enter a username and password NOT defined in
> conf/tomcat-users.xml I get an "invalid username..." page (as I should)
> BUT when I enter a valid user and password I get a "403" (forbidden)
> page with the description
> "Access to the specified resource (Access to the requested resource has
> been denied) has been forbidden."
>
> I've checked permissions in Unix, Googled like crazy and looked in
> catalina.out for any error msgs.  An admin log file is not being
> created in logs/
>
> Any help GREATLY appreciated
> TIA
> ---Raymond



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

Tomcat 5 admin application "403"

[Raymond Blum]

Hi
  I've installed Tomcat 5.0.19 on MacOSX 10.3 and all is well EXCEPT... 
(of course)
When I try to get to the admin application, the login page comes up 
fine. If I enter a username and password NOT defined in 
conf/tomcat-users.xml I get an "invalid username..." page (as I should)
BUT when I enter a valid user and password I get a "403" (forbidden) 
page with the description
"Access to the specified resource (Access to the requested resource has 
been denied) has been forbidden."

I've checked permissions in Unix, Googled like crazy and looked in 
catalina.out for any error msgs.  An admin log file is not being 
created in logs/

Any help GREATLY appreciated
TIA
---Raymond

Tomcat 5 - Struts Error in Admin application

[James Neville]

Hi guys,

We've just started testing TC 5.0.16, with a view to running in production.
Unfortunately we're getting errors with the admin application (something 
we've come to rely on recently).

_1. Tomcat Service Node throws this error:-_

javax.servlet.ServletException: Define tag cannot set a null value

org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:867)

org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:800)
admin.service.service_jsp._jspService(service_jsp.java:840)
*
root cause*
javax.servlet.jsp.JspException: Define tag cannot set a null value
org.apache.struts.taglib.bean.DefineTag.doEndTag(DefineTag.java:272)
admin.service.service_jsp._jspService(service_jsp.java:235)
_2.  Host link throws this error:-_

java.lang.NullPointerException

org.apache.struts.taglib.logic.CompareTagBase.condition(CompareTagBase.java:179)
org.apache.struts.taglib.logic.NotEqualTag.condition(NotEqualTag.java:90)

org.apache.struts.taglib.logic.ConditionalTagBase.doStartTag(ConditionalTagBase.java:218)
admin.host.host_jsp._jspService(host_jsp.java:437)
_3. Context Nodes throw these errors:-_

*type* Status report

*message* _Error retrieving attribute debug_

*description* _The server encountered an internal error (Error 
retrieving attribute debug) that prevented it from fulfilling this request._

 
I found this entry in Bugzilla (when clicking the back button in Mozilla):-

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24086

I'm using Mozilla, but the error appears on every browser available 
(MSIE 5/5.5/6 Mac/Pc and all Netscapes).
Its plainly clear theres some kind of Struts incompatability, but is 
this confined to my installation, or is anyone else experiencing it?

Does anyone know if the admin app has changed since 4.1.29?

I can provide full logs if anyones interested.

_Setup:-_
Debian 2.4.18-1
tc 5.0.16
jk 2.0.2
http 2.0.48
As a final note - I have tried this on both my development and 
production machines with similar results.
I'm going to attempt replacing the Struts jars in the admin's 
WEB-INF/lib, but I reckon thats probably a dead end (last resort).
I'm pretty sure its not my installation, but i'll add it to Bugzilla if 
i'm able to confirm.

Thanks in advance for any insight.

James.



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

See WebApps in Manager and Admin application

[Michel-Ange Anton]

Hello,

I'm using Tomcat-5.0.16 with the default configuration.
I have just added in the "tomcat-users.xml" file, my user with "admin" 
and "manager" role.
In the Manager application, I see all the webapps : (/), (/admin), 
(/balancer), (/jsp-examples), (/manager), (/servlets-examples), 
(/tomcat-docs).
In the Admin application, too.

In the Manager application, I undeploy the (/tomcat-docs) webapp (Click 
on the "Undeploy" link).
This webapp disappears of the webapps list.
But it doesn't disappear in the Admin application.
The (/tomcat-docs) webapp is always in the list of context in the host node.
And if I click on the Context (/tomcat-docs) link, I have a HTTP 500 error.

It's normal or a bug ?
Someone can explain me ?
michelange





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

RE: Admin Application

[Shapira, Yoav]

Howdy,
Your points are good.

The manager app is designed to run under a host, so you need one per
host.  It would be a welcome patch if you made it able to handle
multiple hosts.

The manager servlet is privileged, so its context must have the
privileged attribute, as you know by now.  I thought the Admin webapp
let you specify that attribute?  I'm pretty sure it does in tomcat5.

Finally, the admin webapp doesn't have functionality to
stop/start/reload contexts, as that functionality is already in the
manager webapp.  One could make an argument about how the two really
should be one webapp.

Yoav Shapira
Millennium ChemInformatics


>-Original Message-
>From: George Sexton [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, November 05, 2003 8:04 PM
>To: [EMAIL PROTECTED]
>Subject: Admin Application
>
>I created a new virtual host using the Admin Application, and attempted
>to deploy the "Manager" application using the interface. Initial
>attempts gave this message:
>
>java.lang.ClassNotFoundException:
>org.apache.catalina.manager.HTMLManagerServlet
>
>org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassL
o
>ader.java:891)
>
>org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassL
o
>ader.java:756)
>
>org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticato
r
>Base.java:594)
>
>
>After some fooling around, I found that the issue was that the context
>need the "privileged" attribute set to "true". I looked, but I don't
>understand how to use the Admin application to set this attribute for a
>context.
>
>More to the point, is it possible for the manager application to work
>across multiple virtual hosts? It seems like quite a waste to have to
>configure the manager application for each virtual host?
>
>I guess another, perhaps better question is why does the Admin
>application not have controls to stop, start, and re-load contexts?
>
>
>George Sexton
>MH Software, Inc.
>Voice: 303 438 9585
>http://www.mhsoftware.com
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


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

More Admin Application: Service Reloading Question

[George Sexton]

I am evaluating Tomcat 5.0.14 for use in a ASP Hosting environment. As
part of this environment I would need to routinely create (or destroy)
virtual hosts. One major showstopper seems to be that if I create a
virtual host and click on the "Commit Changes", then the service
reloads, including all of the virtual hosts, and their associated
contexts.

Is there some setting I don't see that can affect this restarting
behavior?

Without the capability to create virtual hosts on the fly, I will have
to schedule routine re-starts of the servlet engine. This is really less
than optimal. Any ideas would be appreciated.

George Sexton
MH Software, Inc.
Voice: 303 438 9585
http://www.mhsoftware.com 
 


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

Admin Application

[George Sexton]

I created a new virtual host using the Admin Application, and attempted
to deploy the "Manager" application using the interface. Initial
attempts gave this message:

java.lang.ClassNotFoundException:
org.apache.catalina.manager.HTMLManagerServlet

org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLo
ader.java:891)

org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLo
ader.java:756)

org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticator
Base.java:594)


After some fooling around, I found that the issue was that the context
need the "privileged" attribute set to "true". I looked, but I don't
understand how to use the Admin application to set this attribute for a
context.

More to the point, is it possible for the manager application to work
across multiple virtual hosts? It seems like quite a waste to have to
configure the manager application for each virtual host?

I guess another, perhaps better question is why does the Admin
application not have controls to stop, start, and re-load contexts?


George Sexton
MH Software, Inc.
Voice: 303 438 9585
http://www.mhsoftware.com 
 


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

RE: Admin Application wont start on Tomcat 4.1.24 w/ JDK 1.4.1_03

[David Kramer]

Im not really sure why you replied to my posting with an issue.  But I
recommend re-submitting your error to the list with its own subject title.

Thanks,

DK

> -Original Message-
> From: VijayaLakshmi Seshadri [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 18, 2003 12:09 PM
> To: Tomcat Users List
> Subject: Re: Admin Application wont start on Tomcat 4.1.24 w/ JDK
> 1.4.1_03
> 
> 
> Hai
> I have installed Tomcat 4.0.1 in my machine and i have
> Apache 2.0
> Now when iam trying to integrate the both 
> by downloading mod_webapp.so ,apache is not starting 
> It gives following error
> undefined symbol -as_pstrdup
> 
> can kindly anybody help me figuring out the problem
> viji
>  --- David Kramer <[EMAIL PROTECTED]> wrote: > I
> just compiled Tomcat from source and was able to
> > get everything working
> > except the Admin application.  I found the following
> > error posted on the net
> > and attempted the response(added
> > ApplicationResource.properties to my
> > WEB-INF/classes dir), but it still had not affect. 
> > I even tried removing
> > the   entry in my header.jsp and
> > still no luck.  Any one have
> > any idea whats going on?
> > 
> > org.apache.jasper.JasperException: Cannot find
> > message resources under key
> > org.apache.struts.action.MESSAGE
> > at
> >
> org.apache.jasper.servlet.JspServletWrapper.service(JspServlet
> Wrapper.java:2
> > 54)
> > at
> >
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet
> .java:295)
> > at
> >
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
> > at
> >
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilt
> er(Application
> > FilterChain.java:247)
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(Appli
> cationFilterCh
> > ain.java:193)
> > at
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardW
> rapperValve.ja
> > va:256)
> > at
> >
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invok
> > eNext(StandardPipeline.java:643)
> > at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
> ine.java:480)
> > at
> >
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> > at
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardC
> ontextValve.ja
> > va:191)
> > at
> >
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invok
> > eNext(StandardPipeline.java:643)
> > at
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(Aut
> henticatorBase
> > .java:551)
> > at
> >
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invok
> > eNext(StandardPipeline.java:641)
> > at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
> ine.java:480)
> > at
> >
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> > at
> >
> org.apache.catalina.core.StandardContext.invoke(StandardContex
> t.java:2415)
> > at
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHost
> Valve.java:180
> > )
> > at
> >
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invok
> > eNext(StandardPipeline.java:643)
> > at
> >
> org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDi
> spatcherValve.
> > java:171)
> > at
> >
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invok
> > eNext(StandardPipeline.java:641)
> > at
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReport
> Valve.java:172
> > )
> > at
> >
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invok
> > eNext(StandardPipeline.java:641)
> > at
> >
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
> ine.java:480)
> > at
> >
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> > at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEn
> gineValve.java
> > :174)
> > at
> >
> org.apache.catalina.core.StandardPipeline$StandardPipelineValv
> eContext.invok
> > eNext(StandardPipeline.java:643)
> > at
> >
> org.apache

Re: Admin Application wont start on Tomcat 4.1.24 w/ JDK 1.4.1_03

[VijayaLakshmi Seshadri]

Hai
I have installed Tomcat 4.0.1 in my machine and i have
Apache 2.0
Now when iam trying to integrate the both 
by downloading mod_webapp.so ,apache is not starting 
It gives following error
undefined symbol -as_pstrdup

can kindly anybody help me figuring out the problem
viji
 --- David Kramer <[EMAIL PROTECTED]> wrote: > I
just compiled Tomcat from source and was able to
> get everything working
> except the Admin application.  I found the following
> error posted on the net
> and attempted the response(added
> ApplicationResource.properties to my
> WEB-INF/classes dir), but it still had not affect. 
> I even tried removing
> the   entry in my header.jsp and
> still no luck.  Any one have
> any idea whats going on?
> 
> org.apache.jasper.JasperException: Cannot find
> message resources under key
> org.apache.struts.action.MESSAGE
>   at
>
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
> 54)
>   at
>
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
>   at
>
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
>   at
>
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>   at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
> FilterChain.java:247)
>   at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
> ain.java:193)
>   at
>
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
> va:256)
>   at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
> eNext(StandardPipeline.java:643)
>   at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
>   at
>
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
>   at
>
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
> va:191)
>   at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
> eNext(StandardPipeline.java:643)
>   at
>
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
> .java:551)
>   at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
> eNext(StandardPipeline.java:641)
>   at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
>   at
>
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
>   at
>
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
>   at
>
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
> )
>   at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
> eNext(StandardPipeline.java:643)
>   at
>
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
> java:171)
>   at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
> eNext(StandardPipeline.java:641)
>   at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
> )
>   at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
> eNext(StandardPipeline.java:641)
>   at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
>   at
>
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
>   at
>
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
> :174)
>   at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
> eNext(StandardPipeline.java:643)
>   at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
>   at
>
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
>   at
>
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
>   at
>
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
>   at
>
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
> ction(Http11Protocol.java:392)
>   at
>
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
>   at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
> a:619)
>   at java.lang.Thread.run(Thread.java:536)
> root cause 
> javax.servlet.ServletException: Cannot find message
> resources under key
> org.apache.struts.action.MESSAGE
>   at
>
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
> l.java:533)
>   at
>
org.apache.jsp.login_jsp._jspService(login_jsp.java:192)
>   at
>
org.apache.jasper.runtime.HttpJspBase.service(HttpJsp

Admin Application wont start on Tomcat 4.1.24 w/ JDK 1.4.1_03

[David Kramer]

I just compiled Tomcat from source and was able to get everything working
except the Admin application.  I found the following error posted on the net
and attempted the response(added ApplicationResource.properties to my
WEB-INF/classes dir), but it still had not affect.  I even tried removing
the   entry in my header.jsp and still no luck.  Any one have
any idea whats going on?

org.apache.jasper.JasperException: Cannot find message resources under key
org.apache.struts.action.MESSAGE
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
54)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
.java:551)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:392)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:619)
at java.lang.Thread.run(Thread.java:536)
root cause 
javax.servlet.ServletException: Cannot find message resources under key
org.apache.struts.action.MESSAGE
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
l.java:533)
at org.apache.jsp.login_jsp._jspService(login_jsp.java:192)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
10)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java

RE: Problem with mod_jk and admin application in Tomcat 4.1

[J.P. Wadkin C9951627]

Great - no more messing with damn mod_jk2. Relief!

Thanks

John

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: 14 August 2003 15:03
To: Tomcat Users List
Subject: Re: Problem with mod_jk and admin application in Tomcat 4.1



I didn't mean mod_jk2.

I meant CoyoteConnector in server.xml.

In server.xml, you have a connector listening on some port (like 8009) 
for communications from Apache.  This connector has a class parameter. 
In your case, the class is "org.apache.ajp.tomcat4.Ajp13Connector".

Make it "org.apache.coyote.tomcat4.CoyoteConnector" instead and you will

be able to use MBeans.

CoyoteConnector can handle AJP13 from either mod_jk or mod_jk2, as well 
as HTTP and HTTPS.

There are actually two Apache connectors in server.xml by default, one 
uses Ajp13Connector, one uses CoyoteConnector:

 
 

 
 

You want the first one, not the second one.

John

J.P. Wadkin C9951627 wrote:

> I would use JK2 if it worked on Solaris 8 with Apache 2, which it
> doesn't - or at least I haven't been able to get it to work and I've
> tried everything.
> 
> 
> John
> 
> -Original Message-
> From: John Turner [mailto:[EMAIL PROTECTED] 
> Sent: 14 August 2003 14:43
> To: Tomcat Users List
> Subject: Re: Problem with mod_jk and admin application in Tomcat 4.1
> 
> 
> 
> You're using a sledgehammer where a light tap will do fine.
> 
> Ajp13Connector doesn't like MBeans, or vice versa.
> 
> Either don't use MBeans, or use CoyoteConnector instead of 
> Ajp13Connector.  The latter is preferred and recommended,
Ajp13Connector
> 
> is deprecated.
> 
> John
> 
> J.P. Wadkin C9951627 wrote:
> 
> 
>>It seems that it's not possible to use mod_jk with the admin
> 
> application
> 
>>in Tomcat 4.1
>>
>>On startup this appears in catalina.out
>>
>>ServerLifecycleListener: Creating MBean for Service
>>StandardService[Tomcat-JK]
>>ServerLifecycleListener: Creating MBean for Connector
>>[EMAIL PROTECTED]
>>ServerLifecycleListener: createMBeans: MBeanException
>>java.lang.Exception: ManagedBean is not found with Ajp13Connector
>>   
>>
>>So I edited the mbeans-descriptors.xml file in the catalina.jar and
>>added an mbean for the Ajp13Connector. Tomcat started fine (no errors)
>>but mod_jk no longer works - any request to a webapp URL results in a
>>404 error. There's nothing in the logs - just the 404 errors. I'm not
>>sure why this is - there's a mbean for the Coyote/jk2 connector so
>>presumably this works?
>>
>>
>>Thanks
>>
>>John
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 



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


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

Problem with mod_jk and admin application in Tomcat 4.1

[J.P. Wadkin C9951627]

It seems that it's not possible to use mod_jk with the admin application
in Tomcat 4.1

On startup this appears in catalina.out

ServerLifecycleListener: Creating MBean for Service
StandardService[Tomcat-JK]
ServerLifecycleListener: Creating MBean for Connector
[EMAIL PROTECTED]
ServerLifecycleListener: createMBeans: MBeanException
java.lang.Exception: ManagedBean is not found with Ajp13Connector
   

So I edited the mbeans-descriptors.xml file in the catalina.jar and
added an mbean for the Ajp13Connector. Tomcat started fine (no errors)
but mod_jk no longer works - any request to a webapp URL results in a
404 error. There's nothing in the logs - just the 404 errors. I'm not
sure why this is - there's a mbean for the Coyote/jk2 connector so
presumably this works?


Thanks

John

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

RE: Problem with mod_jk and admin application in Tomcat 4.1

[J.P. Wadkin C9951627]

I would use JK2 if it worked on Solaris 8 with Apache 2, which it
doesn't - or at least I haven't been able to get it to work and I've
tried everything.


John

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: 14 August 2003 14:43
To: Tomcat Users List
Subject: Re: Problem with mod_jk and admin application in Tomcat 4.1



You're using a sledgehammer where a light tap will do fine.

Ajp13Connector doesn't like MBeans, or vice versa.

Either don't use MBeans, or use CoyoteConnector instead of 
Ajp13Connector.  The latter is preferred and recommended, Ajp13Connector

is deprecated.

John

J.P. Wadkin C9951627 wrote:

> It seems that it's not possible to use mod_jk with the admin
application
> in Tomcat 4.1
> 
> On startup this appears in catalina.out
> 
> ServerLifecycleListener: Creating MBean for Service
> StandardService[Tomcat-JK]
> ServerLifecycleListener: Creating MBean for Connector
> [EMAIL PROTECTED]
> ServerLifecycleListener: createMBeans: MBeanException
> java.lang.Exception: ManagedBean is not found with Ajp13Connector
>
> 
> So I edited the mbeans-descriptors.xml file in the catalina.jar and
> added an mbean for the Ajp13Connector. Tomcat started fine (no errors)
> but mod_jk no longer works - any request to a webapp URL results in a
> 404 error. There's nothing in the logs - just the 404 errors. I'm not
> sure why this is - there's a mbean for the Coyote/jk2 connector so
> presumably this works?
> 
> 
> Thanks
> 
> John
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 



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


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

Re: Problem with mod_jk and admin application in Tomcat 4.1

[John Turner]

You're using a sledgehammer where a light tap will do fine.

Ajp13Connector doesn't like MBeans, or vice versa.

Either don't use MBeans, or use CoyoteConnector instead of 
Ajp13Connector.  The latter is preferred and recommended, Ajp13Connector 
is deprecated.

John

J.P. Wadkin C9951627 wrote:

It seems that it's not possible to use mod_jk with the admin application
in Tomcat 4.1
On startup this appears in catalina.out

ServerLifecycleListener: Creating MBean for Service
StandardService[Tomcat-JK]
ServerLifecycleListener: Creating MBean for Connector
[EMAIL PROTECTED]
ServerLifecycleListener: createMBeans: MBeanException
java.lang.Exception: ManagedBean is not found with Ajp13Connector
   
So I edited the mbeans-descriptors.xml file in the catalina.jar and
added an mbean for the Ajp13Connector. Tomcat started fine (no errors)
but mod_jk no longer works - any request to a webapp URL results in a
404 error. There's nothing in the logs - just the 404 errors. I'm not
sure why this is - there's a mbean for the Coyote/jk2 connector so
presumably this works?
Thanks

John

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


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

Re: Problem with mod_jk and admin application in Tomcat 4.1

[John Turner]

I didn't mean mod_jk2.

I meant CoyoteConnector in server.xml.

In server.xml, you have a connector listening on some port (like 8009) 
for communications from Apache.  This connector has a class parameter. 
In your case, the class is "org.apache.ajp.tomcat4.Ajp13Connector".

Make it "org.apache.coyote.tomcat4.CoyoteConnector" instead and you will 
be able to use MBeans.

CoyoteConnector can handle AJP13 from either mod_jk or mod_jk2, as well 
as HTTP and HTTPS.

There are actually two Apache connectors in server.xml by default, one 
uses Ajp13Connector, one uses CoyoteConnector:



protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>



You want the first one, not the second one.

John

J.P. Wadkin C9951627 wrote:

I would use JK2 if it worked on Solaris 8 with Apache 2, which it
doesn't - or at least I haven't been able to get it to work and I've
tried everything.
John

-Original Message-
From: John Turner [mailto:[EMAIL PROTECTED] 
Sent: 14 August 2003 14:43
To: Tomcat Users List
Subject: Re: Problem with mod_jk and admin application in Tomcat 4.1



You're using a sledgehammer where a light tap will do fine.

Ajp13Connector doesn't like MBeans, or vice versa.

Either don't use MBeans, or use CoyoteConnector instead of 
Ajp13Connector.  The latter is preferred and recommended, Ajp13Connector

is deprecated.

John

J.P. Wadkin C9951627 wrote:


It seems that it's not possible to use mod_jk with the admin
application

in Tomcat 4.1

On startup this appears in catalina.out

ServerLifecycleListener: Creating MBean for Service
StandardService[Tomcat-JK]
ServerLifecycleListener: Creating MBean for Connector
[EMAIL PROTECTED]
ServerLifecycleListener: createMBeans: MBeanException
java.lang.Exception: ManagedBean is not found with Ajp13Connector
  
So I edited the mbeans-descriptors.xml file in the catalina.jar and
added an mbean for the Ajp13Connector. Tomcat started fine (no errors)
but mod_jk no longer works - any request to a webapp URL results in a
404 error. There's nothing in the logs - just the 404 errors. I'm not
sure why this is - there's a mbean for the Coyote/jk2 connector so
presumably this works?
Thanks

John

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




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


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

Tomcat ADMIN Application

[Hari Om]

When I run my Tomcat Application "admin" (this is the one which comes with 
Tomcat) as http://localhost/admin/index.jsp - it gives following error - 
wonder why:

Any related information on this is appreciated!

My other applications i.e: "examples" , "manager" etc are working great.

Error report is:

---
HTTP Status 500 - Internal Server Error


org.apache.jasper.JasperException: Cannot find message resources under key 
org.apache.struts.action.MESSAGE
	at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
	at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
	at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java(Compiled 
Code))
	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java(Compiled 
Code))
	at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:551)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java(Compiled 
Code))
	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
	at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java(Compiled 
Code))
	at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java(Compiled 
Code))
	at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java(Compiled 
Code))
	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java(Compiled 
Code))
	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:466)
	at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:585)
	at java.lang.Thread.run(Thread.java:512)

---

_
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

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

Re: Extended characters in passwords working with admin application?

[Tim Funk]

This might help.
http://www.w3.org/TR/REC-html40/interact/forms.html#adef-accept-charset
I really don't know.

-Tim

Jeff Tulley wrote:
Thanks I just found it in the archives.  I had been at JavaOne last week and so did a mass-delete of this list when I returned, and I also did not pick that up in the archives for some reason until you pointed it out.

So, there is still a problem with Tomcat when a login page specifies <%@ page  contentType="text/html; charset=UTF-8" %>  (which the login.jsp of the /admin application indeed does).  According to this FAQ, the inclusion of such a declaration is CORRECT.  So, is Tomcat just missing the conversion part?

If so, I hope that it can be changed.  It seems like such a change would be a huge potential backwards compatibility issue and is therefore risky.

I still challenge whether with the existing tomcat-provided login.jsp and authentication mechanism, whether you can log in with a user that has extended characters.  If anybody has successfully done that please let me know.  (I'm only successful if contentType=ISO-8859-1).

Also, that FAQ mentions passing in a "-Dfile.encoding=UTF-8", which Tomcat does not currently do.  This is another backwards compatibility issue for getting this to be the default Tomcat behavior.

Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
 


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

Re: Extended characters in passwords working with admin application?

[Tim Funk]

http://jakarta.apache.org/tomcat/faq/misc.html#utf8

-Tim

Tim Shaw wrote:
There was an extremely detailed UTF-8/ISO-8859-1 'how to' on this list 
recently (past week or so). I don't remember the details but it seemed 
to do it for the others.

tim

Jeff Tulley wrote:

Has anybody successfully authenticated to the /admin application, with 
a user who has a password that has extended characters?  (español is 
what I've been trying - espa(n tilde)ol if that doesn't come through 
the email).

I thought this was a side-effect of my use of the JNDIRealm, but I 
cannot get it to work for me using the MemoryRealm as well.

The problem seems to be the specification of encoding="utf-8" in 
login.jsp.  If you do not set this content type, Tomcat seems to 
default to "ISO-8859-1".  While I realize that this will only work for 
those who can live with ISO-8859-1 (Latin 1?), it seems that UTF-8 
isn't working at all.

Note to the first objections I forsee:  I wrote out the tomcat-users 
file using a UTF-8 compatible editor, and the password was for sure 
stored in my LDAP directory in UTF-8 as well.  I also tried all sorts 
of combinations of encodings while authenticating, from hitting 
alt-164 and alt-0241 on Windows to copy and pasting the full UTF-8 
encoded multiple character value into the password field.

Anybody get this to work?  I want to see if I'm just doing it wrong 
before suggesting the change of taking the utf-8 declaration out 
completely.

Thanks,

Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


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



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

Re: Extended characters in passwords working with admin application?

[Tim Shaw]

There was an extremely detailed UTF-8/ISO-8859-1 'how to' on this list 
recently (past week or so). I don't remember the details but it seemed 
to do it for the others.

tim

Jeff Tulley wrote:
Has anybody successfully authenticated to the /admin application, with a user who has a password that has extended characters?  (español is what I've been trying - espa(n tilde)ol if that doesn't come through the email).

I thought this was a side-effect of my use of the JNDIRealm, but I cannot get it to work for me using the MemoryRealm as well.

The problem seems to be the specification of encoding="utf-8" in login.jsp.  If you do not set this content type, Tomcat seems to default to "ISO-8859-1".  While I realize that this will only work for those who can live with ISO-8859-1 (Latin 1?), it seems that UTF-8 isn't working at all.

Note to the first objections I forsee:  I wrote out the tomcat-users file using a UTF-8 compatible editor, and the password was for sure stored in my LDAP directory in UTF-8 as well.  I also tried all sorts of combinations of encodings while authenticating, from hitting alt-164 and alt-0241 on Windows to copy and pasting the full UTF-8 encoded multiple character value into the password field.

Anybody get this to work?  I want to see if I'm just doing it wrong before suggesting the change of taking the utf-8 declaration out completely.

Thanks,

Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


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

Problem with Admin application

[Mike Hedman]

I've been having nothing but trouble getting Admin to work - ugh.  I just
re-installed 4.1.18, and Tomcat is running (the Manager app works).

But when I run Admin I'm getting the following:
org.apache.jasper.JasperException: Missing message for key application.title
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:248)

I've checked and the resources files are there - it's a new, complete install.

I've got JAVA_HOME and CATALINA_HOME set.

Here's my current setup:
Win2000 - running as a service
j2sdk1.4.1_01
jakarta-tomcat-4.1.18

Any ideas, I have to believe it's something pretty simple,
Thanks!
Mike


__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Tomcat 4.1.12 Admin Application Functions without using theadmin interface...

[Craig R. McClanahan]

On Fri, 22 Nov 2002, Brandon Cruz wrote:

> Date: Fri, 22 Nov 2002 11:56:06 -0600
> From: Brandon Cruz <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>,
>  [EMAIL PROTECTED]
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: Tomcat 4.1.12 Admin Application Functions without using the
> admin interface...
>
> Hi,
> Is there a servlet or some internal tomcat class available that will tomcat
> to see changes made to server.xml?  I would like to be able to add new
> virtual hosts and contexts those hosts without having to use the admin
> application.
>
> Is this possible?
>

You'd need to write a servlet that makes the same kinds of internal calls
that the admin webapp does (via JMX MBeans) to accomplish those kinds of
things.  Don't forget to declare the webapp as privileged (and spell it
correctly :-).

>
> Brandon

Craig


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

Tomcat 4.1.12 Admin Application Functions without using the admin interface...

[Brandon Cruz]

Hi,
Is there a servlet or some internal tomcat class available that will tomcat
to see changes made to server.xml?  I would like to be able to add new
virtual hosts and contexts those hosts without having to use the admin
application.

Is this possible?


Brandon


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

Re: 4.1.7b admin application

[Craig R. McClanahan]

On Wed, 17 Jul 2002, Martin Grebac wrote:

> Date: Wed, 17 Jul 2002 15:13:40 +0200
> From: Martin Grebac <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>,
>  [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: 4.1.7b admin application
>
> Hi,
>  I just installed the 4.1.7b, and was keen to see the admin application.
> Everything except admin app works ok, but I can't log into the
> application. I always get
>
>
>   HTTP Status 403 - Access to the requested resource has been denied
>
> I didn't know what's wrong, so I tried to look for some documentation
> for the app (especially what needs to be setup to make it running and
> what login should be used), but did not find anything. I'd appreciate
> any hints, or links to the docs.
>  Thanks a lot,
>   Martin
>

Before you can use the admin app, you have to set up a user with
role "admin" in the user database file (conf/tomcat-users.xml).  There is
no such user when Tomcat is first installed (for obvious security
reasons).

Craig



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

Re: Antwort: 4.1.7b admin application

[Martin Grebac]

Yes, thanks, I already found the problem when I ran the .exe installer 
(previously I didn't). The installer creates admin user and assigns the 
'admin' and 'manager' roles to him.
  Martin

[EMAIL PROTECTED] wrote:

>Martin Grebac <[EMAIL PROTECTED]> am 17.07.2002 15:13:40
>
>Bitte antworten an "Tomcat Users List" <[EMAIL PROTECTED]>
>
>An:   [EMAIL PROTECTED]
>Kopie:
>
>Thema:4.1.7b admin application
>
>
>Hi,
> I just installed the 4.1.7b, and was keen to see the admin application.
>Everything except admin app works ok, but I can't log into the
>application. I always get
>
>
>  HTTP Status 403 - Access to the requested resource has been denied
>
>I didn't know what's wrong, so I tried to look for some documentation
>for the app (especially what needs to be setup to make it running and
>what login should be used), but did not find anything. I'd appreciate
>any hints, or links to the docs.
> Thanks a lot,
>  Martin
>
>
>
>You must edit the tomcat-users.xml File.
>
>Add the Role Manager and a Password to a user.
>
>With these User you can log in the Manager App
>
>
>
>
>
>
>--
>To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>  
>


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

Antwort: 4.1.7b admin application

[Joern . Karthaus]

Martin Grebac <[EMAIL PROTECTED]> am 17.07.2002 15:13:40

Bitte antworten an "Tomcat Users List" <[EMAIL PROTECTED]>

An:   [EMAIL PROTECTED]
Kopie:

Thema:4.1.7b admin application


Hi,
 I just installed the 4.1.7b, and was keen to see the admin application.
Everything except admin app works ok, but I can't log into the
application. I always get


  HTTP Status 403 - Access to the requested resource has been denied

I didn't know what's wrong, so I tried to look for some documentation
for the app (especially what needs to be setup to make it running and
what login should be used), but did not find anything. I'd appreciate
any hints, or links to the docs.
 Thanks a lot,
  Martin



You must edit the tomcat-users.xml File.

Add the Role Manager and a Password to a user.

With these User you can log in the Manager App






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

4.1.7b admin application

[Martin Grebac]

Hi,
 I just installed the 4.1.7b, and was keen to see the admin application. 
Everything except admin app works ok, but I can't log into the 
application. I always get


  HTTP Status 403 - Access to the requested resource has been denied

I didn't know what's wrong, so I tried to look for some documentation 
for the app (especially what needs to be setup to make it running and 
what login should be used), but did not find anything. I'd appreciate 
any hints, or links to the docs.
 Thanks a lot,
  Martin

Admin application will not accept admin/password

[Peter Schauss]

Environment:  Windows 98
Tomcat 3.2.2

When I try to access the Context Admin option from the
Tomcat Administration Tools screen (http://localhost:8080/admin/index.html)
it asks me for an id and password.  I have an entry in tomcat-users.xml



but the screen refuses to accept it.

I am not sure whether this is related, but I am also getting the following
error
on the screen from which Tomcat is running:

log4j:ERROR No appenders could be found for category
(org.jboss.tomcat.security.
JBossSecurityMgrRealm).
log4j:ERROR Please initialize the log4j system properly.

Any suggestions.

Thanks,

Peter Schauss