Re: ManagedBean is not found with Ajp13Connector
Use the Coyote connector. Look into a recent server.xml, and you will
see that the default is the Coyote Connector with the JkHandler, like
this:
Whereas the one you are probably using is the older, deprecated AJP13
connector
The confusion comes in the naming; the Coyote Connector is used for
more than one thing (hence the "protocolHandlerClassName" attribute to
differentiate its use as an AJP connector from its use elsewhere as the
internal HTTP stack), and even though there is no "AJP13" in the name,
it DOES work with the apache mod_jk, just like the Ajp13Connector did.
That, or you can patch the mbeans-descriptor.xml, to give the AJP13
connector a JMX MBean definition. I'd move to the new connector
though.
Jeff Tulley ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., the leading provider of Net business solutions
http://www.novell.com
>>> [EMAIL PROTECTED] 3/6/03 11:58:01 AM >>>
I've been looking in the mailing list archives for my problem, and
I've
found the message I pasted below.
But the problem is that I don't understand what I exactly need to do
with
that answer. Can anybody help me with this?
- Original Message -----
From: Ben Jessel
Subject: Re: ManagedBean is not found with Ajp13Connector
Date: Fri, 03 Jan 2003 04:35:52 -0800
It's o.k I found the solution. Don't use AJP and JMX together. I guess
they
put in JMX support and didn't want to support the old Ajp13Connector.
Use
coyote instead. Having said that, that's as far as i've got...
- Original Message -
From: "Ben Jessel" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Friday, January 03, 2003 11:43 AM
Subject: ManagedBean is not found with Ajp13Connector
Hi, I've been suffering with trying to configure mod_jk + apache 1.3 +
tomcat 1.4.18 for a while.
I've managed to get to a stage where I have a workers.properties, and
an
auto-created configuration for apache. However, I'm getting an error
with
this line of my server.xml
ServerLifecycleListener: Creating MBean for Service
StandardService[Tomcat-Standalone]
ServerLifecycleListener: Creating MBean for Connector
[EMAIL PROTECTED]
ServerLifecycleListener: Creating MBean for Connector
[EMAIL PROTECTED]
java.lang.Exception: ManagedBean is not found with
Ajp13Connector
at
org.apache.catalina.mbeans.MBeanUtils.createMean(MBeanUtils.java:234)
..
...
-
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]
ManagedBean is not found with Ajp13Connector
I've been looking in the mailing list archives for my problem, and I've found the message I pasted below. But the problem is that I don't understand what I exactly need to do with that answer. Can anybody help me with this? - Original Message - From: Ben Jessel Subject: Re: ManagedBean is not found with Ajp13Connector Date: Fri, 03 Jan 2003 04:35:52 -0800 It's o.k I found the solution. Don't use AJP and JMX together. I guess they put in JMX support and didn't want to support the old Ajp13Connector. Use coyote instead. Having said that, that's as far as i've got... - Original Message - From: "Ben Jessel" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Friday, January 03, 2003 11:43 AM Subject: ManagedBean is not found with Ajp13Connector Hi, I've been suffering with trying to configure mod_jk + apache 1.3 + tomcat 1.4.18 for a while. I've managed to get to a stage where I have a workers.properties, and an auto-created configuration for apache. However, I'm getting an error with this line of my server.xml ServerLifecycleListener: Creating MBean for Service StandardService[Tomcat-Standalone] ServerLifecycleListener: Creating MBean for Connector [EMAIL PROTECTED] ServerLifecycleListener: Creating MBean for Connector [EMAIL PROTECTED] java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMean(MBeanUtils.java:234) .. ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ManagedBean is not found with Ajp13Connector
Use the Coyote connector for AJP, not the deprecated ajp connector. Either that or comment out the entries at the top of server.xml when using the deprecated ajp connector to avoid the exception. Jake At 08:03 PM 2/1/2003 +0100, you wrote: Hi! Accessing the /admin or /manager web interface makes Tomcat 4.1.18 to throw MBeanServer UnavailableException. This did happen on solaris from the beginning and does for some unknown reason on my NT machine now as well. Actually the same problems was once already discussed here (http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg79377.html) but came to no satisfying conclusion Timo -- http://nitwit.de/ "Sixty years ago I knew everything; now I know nothing; education is a progressive discovery of our own ignorance." - Will Durant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ManagedBean is not found with Ajp13Connector
Hi! Accessing the /admin or /manager web interface makes Tomcat 4.1.18 to throw MBeanServer UnavailableException. This did happen on solaris from the beginning and does for some unknown reason on my NT machine now as well. Actually the same problems was once already discussed here (http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg79377.html) but came to no satisfying conclusion Timo -- http://nitwit.de/ "Sixty years ago I knew everything; now I know nothing; education is a progressive discovery of our own ignorance." - Will Durant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ManagedBean is not found with Ajp13Connector
Yep, that's the solution. If you have any more problems, post back to the list. John > -Original Message- > From: Ben Jessel [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 03, 2003 7:35 AM > To: Tomcat Users List; Ben Jessel > Subject: Re: ManagedBean is not found with Ajp13Connector > > > It's o.k I found the solution. Don't use AJP and JMX > together. I guess they > put in JMX support and didn't want to support the old > Ajp13Connector. Use > coyote instead. Having said that, that's as far as i've got... > > - Original Message - > From: "Ben Jessel" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Friday, January 03, 2003 11:43 AM > Subject: ManagedBean is not found with Ajp13Connector > > > Hi, I've been suffering with trying to configure mod_jk + apache 1.3 + > tomcat 1.4.18 for a while. > I've managed to get to a stage where I have a > workers.properties, and an > auto-created configuration for apache. However, I'm getting > an error with > this line of my server.xml > > port="8009" minProcessors="5" maxProcessors="75" > acceptCount="10" debug="99"/> > > ServerLifecycleListener: Creating MBean for Service > StandardService[Tomcat-Standalone] > ServerLifecycleListener: Creating MBean for Connector > org.apache.coyote.tomcat4.CoyoteConnector@19ce060 > ServerLifecycleListener: Creating MBean for Connector > org.apache.ajp.tomcat4.Ajp13Connector@13d28e3 > java.lang.Exception: ManagedBean is not found with > Ajp13Connector > at > org.apache.catalina.mbeans.MBeanUtils.createMean(MBeanUtils.java:234) > .. > ... > > > Is tomcat4.1.18 not compatible with mod_jk? > > > Here's the server.xml > > > > > > > > > > >modJk="/etc/httpd/modules/mod_jk.so" > jkDebug="info" > workersConfig="/usr/jakarta-tomcat-4.1.18/conf/workers.properties" > jkLog="/usr/jakarta-tomcat-4.1.18/logs/mod_jk.log" /> > > > > >className="org.apache.catalina.mbeans.ServerLifecycleListener" > debug="99"/> >className="org.apache.catalina.mbeans.GlobalResourcesLifecycle > Listener" > debug="99"/> > > > > > > value="30"/> > > >type="org.apache.catalina.UserDatabase" >description="User database that can be updated and saved"> > > > > factory > > org.apache.catalina.users.MemoryUserDatabaseFactory > > > pathname > conf/tomcat-users.xml > > > > > > > > > > > > > > port="8080" minProcessors="5" maxProcessors="75" >enableLookups="true" redirectPort="8443" >acceptCount="100" debug="99" connectionTimeout="2" >useURIValidationHack="false" > disableUploadTimeout="true" /> > > > > > > > > > port="8009" minProcessors="5" maxProcessors="75" >acceptCount="10" debug="99"/> > > > > > > > > > > > > > > > > > > > > > > > prefix="catalina_log." suffix=".txt" > timestamp="true"/> > > > > > debug="99" resourceName="UserDatabase"/> > > > > > > > > > > > > > > unpackWARs="true" autoDeploy="true"> > > className="org.apache.ajp.tomcat4.config.ApacheConfig" > accept="true"/> > > > > > > > > > directory="logs" prefix="localhost_log." > suffix=".txt" > timestamp="true"/> > > > > > > > reloadable="
Re: ManagedBean is not found with Ajp13Connector
It's o.k I found the solution. Don't use AJP and JMX together. I guess they
put in JMX support and didn't want to support the old Ajp13Connector. Use
coyote instead. Having said that, that's as far as i've got...
- Original Message -
From: "Ben Jessel" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Friday, January 03, 2003 11:43 AM
Subject: ManagedBean is not found with Ajp13Connector
Hi, I've been suffering with trying to configure mod_jk + apache 1.3 +
tomcat 1.4.18 for a while.
I've managed to get to a stage where I have a workers.properties, and an
auto-created configuration for apache. However, I'm getting an error with
this line of my server.xml
ServerLifecycleListener: Creating MBean for Service
StandardService[Tomcat-Standalone]
ServerLifecycleListener: Creating MBean for Connector
org.apache.coyote.tomcat4.CoyoteConnector@19ce060
ServerLifecycleListener: Creating MBean for Connector
org.apache.ajp.tomcat4.Ajp13Connector@13d28e3
java.lang.Exception: ManagedBean is not found with Ajp13Connector
at
org.apache.catalina.mbeans.MBeanUtils.createMean(MBeanUtils.java:234)
..
...
Is tomcat4.1.18 not compatible with mod_jk?
Here's the server.xml
factory
org.apache.catalina.users.MemoryUserDatabaseFactory
pathname
conf/tomcat-users.xml
usernamesa
password
driverClassName
org.hsql.jdbcDriver
url
jdbc:HypersonicSQL:database
mail.smtp.host
localhost
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
ManagedBean is not found with Ajp13Connector
Hi, I've been suffering with trying to configure mod_jk + apache 1.3 + tomcat 1.4.18 for a while. I've managed to get to a stage where I have a workers.properties, and an auto-created configuration for apache. However, I'm getting an error with this line of my server.xml ServerLifecycleListener: Creating MBean for Service StandardService[Tomcat-Standalone] ServerLifecycleListener: Creating MBean for Connector org.apache.coyote.tomcat4.CoyoteConnector@19ce060 ServerLifecycleListener: Creating MBean for Connector org.apache.ajp.tomcat4.Ajp13Connector@13d28e3 java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMean(MBeanUtils.java:234) .. ... Is tomcat4.1.18 not compatible with mod_jk? Here's the server.xml factory org.apache.catalina.users.MemoryUserDatabaseFactory pathname conf/tomcat-users.xml usernamesa password driverClassName org.hsql.jdbcDriver url jdbc:HypersonicSQL:database mail.smtp.host localhost
Tomcat output an error during startup: ManagedBean is not found with Ajp13Connector
Hello everybody, Tomcat output an error during startup: Nov 28, 2002 1:18:47 PM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Nov 28, 2002 1:18:48 PM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Nov 28, 2002 1:18:51 PM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(Unknown Source) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(Unknown Source) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(Unknown Source) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(Unknown Source) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(Unknown Source) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(Unknown Source) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Unknown Source) at org.apache.catalina.core.StandardServer.start(Unknown Source) at org.apache.catalina.startup.Catalina.start(Unknown Source) at org.apache.catalina.startup.Catalina.execute(Unknown Source) at org.apache.catalina.startup.Catalina.process(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Unknown Source) Starting service Tomcat-Standalone Apache Tomcat/4.1 Tomcat will start normally Thanks -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
RE: ManagedBean is not found with Ajp13Connector
Yeah, his response didn't make total sense. By default, everything in Tomcat Catalina should have a MBean equivalent that you shouldn't have to worry about as a user. It is something "under the covers" to make management of tomcat (the /admin app) work better. It is just that, when somebody went to define the MBean resources in an XML file in the source code, they skipped the AJP13Connector since it is considered "deprecated". If I am not mistaken, the problem caused by this exception is that the admin app doesn't always function correctly. Sometimes it simply comes up with a "page not found" and I think this exception might be the problem. Shutdown is also problematic because the JMX stuff isn't fully set up right. The default server.xml (Tomcat 4.1.7 and higher, I think, 4.1.12 for sure) should use the Coyote connector JkHandler by default, and the AJP13Connector should be commented out. I know this to be the case because on NetWare we had to explicitly switch that around to use the AJP13Connector. I think in the future we are also going to move to using the defaults, just keeping the Coyote Connector. Are you adverse to fixing up your tomcat instance? I can send the patch that I have - to jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/mbeans-descriptors.xml This adds in a section that describes the AJP13Connector, getting rid of the immediate problem. You would have to then replace the mbeans-descriptors.xml file in server\lib\catalina.jar with your patched one (with the right path, org\apache\catalina\mbeans). That fixed the problem for us, though long term I'd move away from this connector. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> [EMAIL PROTECTED] 11/14/02 2:33:14 PM >>> What do you mean "set up your configuration with the coyote connector"? I followed the documenation as given and it uses the AjpConnector. What is it that is using MBeans? I'm totally confused! I am completely new to tomcat and apache and would appreciate any clarification! How can I comment out the MBeans that are causing the exception? Will this exception cause instability or can I just ignore it without fear of further problems? Please Help!!! I've looked at the default server.xml and I don't see any help there. -Original Message- From: Jacob Kjome [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 14, 2002 3:20 PM To: Tomcat Users List Subject: Re: ManagedBean is not found with Ajp13Connector Hello M., The Ajp13Connector doesn't support MBeans. You need to set up your AJP configuration with the CoyoteConnector instead. Or, just comment out the MBeans that are causing the exception. See Tomcat-4.1.12's default server.xml for reference. Jake Thursday, November 14, 2002, 2:12:41 PM, you wrote: AMP> I have just completed setting up the Apache 1.3.27 web server which will be AMP> used with Tomcat 4.1 to serve the servlet and jsp pages. I am also using AMP> j2sdk1.4.0_02. I have set up the configuration of my server.xml and AMP> https.conf files as described in the tomcat online help for the AMP> ajp13Connector. When I run them, however, I get an exception stack that AMP> looks like this (this is from my stdout.log file): AMP> Bootstrap: Create Catalina server AMP> Bootstrap: Starting service AMP> ServerLifecycleListener: createMBeans: MBeanException AMP> java.lang.Exception: ManagedBean is not found with Ajp13Connector AMP> at AMP> org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:369) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:777) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:751) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:339) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife AMP> cycleListener.java:206) AMP> at AMP> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor AMP> t.java:166) AMP> at AMP> org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) AMP> at AMP> org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:271) AMP> at java.lang.reflect.Method.invoke(Native Method) AMP> at AMP> org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245 AMP> ) AMP> at AMP> org.apache.catalina.startup.
Re: ManagedBean is not found with Ajp13Connector
Have you searched the user list archives? I've answered this problem about 3 times in the last month or so. It is common; I've patched the actual problem, but the Tomcat committers recommend you move to the JkHandler of the Coyote Connector instead of using the Ajp13Connector, which is deprecated. The coyote connector does work fine with mod_jk. The patch is to the XML file that defines the MBeans corresponding to the various connectors and such. It is pretty simple. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> [EMAIL PROTECTED] 11/14/02 1:12:41 PM >>> I have just completed setting up the Apache 1.3.27 web server which will be used with Tomcat 4.1 to serve the servlet and jsp pages. I am also using j2sdk1.4.0_02. I have set up the configuration of my server.xml and https.conf files as described in the tomcat online help for the ajp13Connector. When I run them, however, I get an exception stack that looks like this (this is from my stdout.log file): Bootstrap: Create Catalina server Bootstrap: Starting service ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:369) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:777) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:751) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:339) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife cycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) at org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:271) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245 ) at org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) Starting service Tomcat-Standalone Apache Tomcat/4.1.12 The server works fine and I can invoke my servlets and jsp pages through apache without a problem. My question concerns this error. I have searched the net to find an answer but I can't find what this problem is. I am satisfied that I have configured the servers properly since I can view my pages but I need to know what that error is so I can be satisfied it won't cause any future problems. Any help would be greatly appreciated!! Paul -- 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]>
Re: ManagedBean is not found with Ajp13Connector
On Fri, 15 Nov 2002, Bill Barker wrote: > - Original Message - > From: "Milt Epstein" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Cc: "Bill Barker" <[EMAIL PROTECTED]> > Sent: Friday, November 15, 2002 8:25 AM > Subject: Re: ManagedBean is not found with Ajp13Connector > > > > On Fri, 15 Nov 2002, Bill Barker wrote: > > > > > In the default 4.1.x server.xml file there is an un-commented out > > > entry: > > className="org.apache.coyote.tomcat4.CoyoteConnector" port="8009" > > > minProcessors="5" maxProcessors="75" enableLookups="true" > > > redirectPort="8443" acceptCount="10" debug="0" > > > connectionTimeout="2" useURIValidationHack="false" > > > protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" /> > > > > > > This is the "coyote connector". Use this one instead of the > > > AjpConnector if you want to enable the "admin" webapp that has the > > > very nice GUI to allow you to configure your server. If you don't > > > care about this, remove (or comment out) the two lines under > > > that have > > className="org.apache.catalina.mbeans" />. In this case, the > > > "admin" application won't work, but you can use the legacy > > > AjpConnector. > > > > The CoyoteConnector apparently has a bug where isSecure() and > > getScheme() don't work correctly on SSL requests. This is pretty core > > functionality, and makes it unusable for many applications/environments. > > Has this bug been fixed? > > It's been fixed since 4.1.13. [ ... ] Great, thanks! Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: ManagedBean is not found with Ajp13Connector
- Original Message - From: "Milt Epstein" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Cc: "Bill Barker" <[EMAIL PROTECTED]> Sent: Friday, November 15, 2002 8:25 AM Subject: Re: ManagedBean is not found with Ajp13Connector > On Fri, 15 Nov 2002, Bill Barker wrote: > > > In the default 4.1.x server.xml file there is an un-commented out > > entry: > className="org.apache.coyote.tomcat4.CoyoteConnector" port="8009" > > minProcessors="5" maxProcessors="75" enableLookups="true" > > redirectPort="8443" acceptCount="10" debug="0" > > connectionTimeout="2" useURIValidationHack="false" > > protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" /> > > > > This is the "coyote connector". Use this one instead of the > > AjpConnector if you want to enable the "admin" webapp that has the > > very nice GUI to allow you to configure your server. If you don't > > care about this, remove (or comment out) the two lines under > > that have > className="org.apache.catalina.mbeans" />. In this case, the > > "admin" application won't work, but you can use the legacy > > AjpConnector. > > The CoyoteConnector apparently has a bug where isSecure() and > getScheme() don't work correctly on SSL requests. This is pretty core > functionality, and makes it unusable for many applications/environments. > Has this bug been fixed? It's been fixed since 4.1.13. > > Thanks. > > > > "Anderson, M. Paul" <[EMAIL PROTECTED]> wrote in message > > news:D66093F40B7B4B428A20AD9796835FD17FE442@;central.ssd.jhuapl.edu... > > > What do you mean "set up your configuration with the coyote connector"? I > > > followed the documenation as given and it uses the AjpConnector. What is > > it > > > that is using MBeans? I'm totally confused! I am completely new to > > tomcat > > > and apache and would appreciate any clarification! How can I comment out > > > the MBeans that are causing the exception? Will this exception cause > > > instability or can I just ignore it without fear of further problems? > > > > > > Please Help!!! I've looked at the default server.xml and I don't see any > > > help there. > > > > > > -Original Message- > > > From: Jacob Kjome [mailto:hoju@;visi.com] > > > Sent: Thursday, November 14, 2002 3:20 PM > > > To: Tomcat Users List > > > Subject: Re: ManagedBean is not found with Ajp13Connector > > > > > > > > > Hello M., > > > > > > The Ajp13Connector doesn't support MBeans. You need to set up your > > > AJP configuration with the CoyoteConnector instead. Or, just comment > > > out the MBeans that are causing the exception. See Tomcat-4.1.12's > > > default server.xml for reference. > > > > > > Jake > [ ... ] > > Milt Epstein > Research Programmer > Integration and Software Engineering (ISE) > Campus Information Technologies and Educational Services (CITES) > University of Illinois at Urbana-Champaign (UIUC) > [EMAIL PROTECTED] > -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
Re: ManagedBean is not found with Ajp13Connector
On Fri, 15 Nov 2002, Bill Barker wrote: > In the default 4.1.x server.xml file there is an un-commented out > entry: className="org.apache.coyote.tomcat4.CoyoteConnector" port="8009" > minProcessors="5" maxProcessors="75" enableLookups="true" > redirectPort="8443" acceptCount="10" debug="0" > connectionTimeout="2" useURIValidationHack="false" > protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" /> > > This is the "coyote connector". Use this one instead of the > AjpConnector if you want to enable the "admin" webapp that has the > very nice GUI to allow you to configure your server. If you don't > care about this, remove (or comment out) the two lines under > that have className="org.apache.catalina.mbeans" />. In this case, the > "admin" application won't work, but you can use the legacy > AjpConnector. The CoyoteConnector apparently has a bug where isSecure() and getScheme() don't work correctly on SSL requests. This is pretty core functionality, and makes it unusable for many applications/environments. Has this bug been fixed? Thanks. > "Anderson, M. Paul" <[EMAIL PROTECTED]> wrote in message > news:D66093F40B7B4B428A20AD9796835FD17FE442@;central.ssd.jhuapl.edu... > > What do you mean "set up your configuration with the coyote connector"? I > > followed the documenation as given and it uses the AjpConnector. What is > it > > that is using MBeans? I'm totally confused! I am completely new to > tomcat > > and apache and would appreciate any clarification! How can I comment out > > the MBeans that are causing the exception? Will this exception cause > > instability or can I just ignore it without fear of further problems? > > > > Please Help!!! I've looked at the default server.xml and I don't see any > > help there. > > > > -Original Message- > > From: Jacob Kjome [mailto:hoju@;visi.com] > > Sent: Thursday, November 14, 2002 3:20 PM > > To: Tomcat Users List > > Subject: Re: ManagedBean is not found with Ajp13Connector > > > > > > Hello M., > > > > The Ajp13Connector doesn't support MBeans. You need to set up your > > AJP configuration with the CoyoteConnector instead. Or, just comment > > out the MBeans that are causing the exception. See Tomcat-4.1.12's > > default server.xml for reference. > > > > Jake [ ... ] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
Re: ManagedBean is not found with Ajp13Connector
In the default 4.1.x server.xml file there is an un-commented out entry: This is the "coyote connector". Use this one instead of the AjpConnector if you want to enable the "admin" webapp that has the very nice GUI to allow you to configure your server. If you don't care about this, remove (or comment out) the two lines under that have . In this case, the "admin" application won't work, but you can use the legacy AjpConnector. "Anderson, M. Paul" <[EMAIL PROTECTED]> wrote in message news:D66093F40B7B4B428A20AD9796835FD17FE442@;central.ssd.jhuapl.edu... > What do you mean "set up your configuration with the coyote connector"? I > followed the documenation as given and it uses the AjpConnector. What is it > that is using MBeans? I'm totally confused! I am completely new to tomcat > and apache and would appreciate any clarification! How can I comment out > the MBeans that are causing the exception? Will this exception cause > instability or can I just ignore it without fear of further problems? > > Please Help!!! I've looked at the default server.xml and I don't see any > help there. > > -Original Message- > From: Jacob Kjome [mailto:hoju@;visi.com] > Sent: Thursday, November 14, 2002 3:20 PM > To: Tomcat Users List > Subject: Re: ManagedBean is not found with Ajp13Connector > > > Hello M., > > The Ajp13Connector doesn't support MBeans. You need to set up your > AJP configuration with the CoyoteConnector instead. Or, just comment > out the MBeans that are causing the exception. See Tomcat-4.1.12's > default server.xml for reference. > > Jake > > Thursday, November 14, 2002, 2:12:41 PM, you wrote: > > AMP> I have just completed setting up the Apache 1.3.27 web server which > will be > AMP> used with Tomcat 4.1 to serve the servlet and jsp pages. I am also > using > AMP> j2sdk1.4.0_02. I have set up the configuration of my server.xml and > AMP> https.conf files as described in the tomcat online help for the > AMP> ajp13Connector. When I run them, however, I get an exception stack > that > AMP> looks like this (this is from my stdout.log file): > > AMP> Bootstrap: Create Catalina server > AMP> Bootstrap: Starting service > AMP> ServerLifecycleListener: createMBeans: MBeanException > AMP> java.lang.Exception: ManagedBean is not found with Ajp13Connector > AMP> at > AMP> org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) > AMP> at > AMP> > org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy > AMP> cleListener.java:369) > AMP> at > AMP> > org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy > AMP> cleListener.java:777) > AMP> at > AMP> > org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy > AMP> cleListener.java:751) > AMP> at > AMP> > org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy > AMP> cleListener.java:339) > AMP> at > AMP> > org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife > AMP> cycleListener.java:206) > AMP> at > AMP> > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor > AMP> t.java:166) > AMP> at > AMP> org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) > AMP> at > AMP> > org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:271) > AMP> at java.lang.reflect.Method.invoke(Native Method) > AMP> at > AMP> > org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245 > AMP> ) > AMP> at > AMP> > org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) > AMP> Starting service Tomcat-Standalone > AMP> Apache Tomcat/4.1.12 > > AMP> The server works fine and I can invoke my servlets and jsp pages > through > AMP> apache without a problem. My question concerns this error. I have > searched > AMP> the net to find an answer but I can't find what this problem is. I am > AMP> satisfied that I have configured the servers properly since I can view > my > AMP> pages but I need to know what that error is so I can be satisfied it > won't > AMP> cause any future problems. > > AMP> Any help would be greatly appreciated!! > > AMP> Paul > > AMP> -- > AMP> To unsubscribe, e-mail: > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > AMP> For additional commands, e-mail: > <mailto:tomcat-user-help@;jakarta.apache.org> > > > > -- > Best regards, > Jacobmailto:hoju@;visi.com > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
RE: ManagedBean is not found with Ajp13Connector
What do you mean "set up your configuration with the coyote connector"? I followed the documenation as given and it uses the AjpConnector. What is it that is using MBeans? I'm totally confused! I am completely new to tomcat and apache and would appreciate any clarification! How can I comment out the MBeans that are causing the exception? Will this exception cause instability or can I just ignore it without fear of further problems? Please Help!!! I've looked at the default server.xml and I don't see any help there. -Original Message- From: Jacob Kjome [mailto:hoju@;visi.com] Sent: Thursday, November 14, 2002 3:20 PM To: Tomcat Users List Subject: Re: ManagedBean is not found with Ajp13Connector Hello M., The Ajp13Connector doesn't support MBeans. You need to set up your AJP configuration with the CoyoteConnector instead. Or, just comment out the MBeans that are causing the exception. See Tomcat-4.1.12's default server.xml for reference. Jake Thursday, November 14, 2002, 2:12:41 PM, you wrote: AMP> I have just completed setting up the Apache 1.3.27 web server which will be AMP> used with Tomcat 4.1 to serve the servlet and jsp pages. I am also using AMP> j2sdk1.4.0_02. I have set up the configuration of my server.xml and AMP> https.conf files as described in the tomcat online help for the AMP> ajp13Connector. When I run them, however, I get an exception stack that AMP> looks like this (this is from my stdout.log file): AMP> Bootstrap: Create Catalina server AMP> Bootstrap: Starting service AMP> ServerLifecycleListener: createMBeans: MBeanException AMP> java.lang.Exception: ManagedBean is not found with Ajp13Connector AMP> at AMP> org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:369) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:777) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:751) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:339) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife AMP> cycleListener.java:206) AMP> at AMP> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor AMP> t.java:166) AMP> at AMP> org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) AMP> at AMP> org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:271) AMP> at java.lang.reflect.Method.invoke(Native Method) AMP> at AMP> org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245 AMP> ) AMP> at AMP> org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) AMP> Starting service Tomcat-Standalone AMP> Apache Tomcat/4.1.12 AMP> The server works fine and I can invoke my servlets and jsp pages through AMP> apache without a problem. My question concerns this error. I have searched AMP> the net to find an answer but I can't find what this problem is. I am AMP> satisfied that I have configured the servers properly since I can view my AMP> pages but I need to know what that error is so I can be satisfied it won't AMP> cause any future problems. AMP> Any help would be greatly appreciated!! AMP> Paul AMP> -- AMP> To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> AMP> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- Best regards, Jacobmailto:hoju@;visi.com -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
RE: ManagedBean is not found with Ajp13Connector
I tried commenting out the lines: in the server.xml file but now my servlet gives me a page not found error. Is there a simple solution to this? -Original Message- From: Jacob Kjome [mailto:hoju@;visi.com] Sent: Thursday, November 14, 2002 3:20 PM To: Tomcat Users List Subject: Re: ManagedBean is not found with Ajp13Connector Hello M., The Ajp13Connector doesn't support MBeans. You need to set up your AJP configuration with the CoyoteConnector instead. Or, just comment out the MBeans that are causing the exception. See Tomcat-4.1.12's default server.xml for reference. Jake Thursday, November 14, 2002, 2:12:41 PM, you wrote: AMP> I have just completed setting up the Apache 1.3.27 web server which will be AMP> used with Tomcat 4.1 to serve the servlet and jsp pages. I am also using AMP> j2sdk1.4.0_02. I have set up the configuration of my server.xml and AMP> https.conf files as described in the tomcat online help for the AMP> ajp13Connector. When I run them, however, I get an exception stack that AMP> looks like this (this is from my stdout.log file): AMP> Bootstrap: Create Catalina server AMP> Bootstrap: Starting service AMP> ServerLifecycleListener: createMBeans: MBeanException AMP> java.lang.Exception: ManagedBean is not found with Ajp13Connector AMP> at AMP> org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:369) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:777) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:751) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:339) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife AMP> cycleListener.java:206) AMP> at AMP> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor AMP> t.java:166) AMP> at AMP> org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) AMP> at AMP> org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:271) AMP> at java.lang.reflect.Method.invoke(Native Method) AMP> at AMP> org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245 AMP> ) AMP> at AMP> org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) AMP> Starting service Tomcat-Standalone AMP> Apache Tomcat/4.1.12 AMP> The server works fine and I can invoke my servlets and jsp pages through AMP> apache without a problem. My question concerns this error. I have searched AMP> the net to find an answer but I can't find what this problem is. I am AMP> satisfied that I have configured the servers properly since I can view my AMP> pages but I need to know what that error is so I can be satisfied it won't AMP> cause any future problems. AMP> Any help would be greatly appreciated!! AMP> Paul AMP> -- AMP> To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> AMP> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- Best regards, Jacobmailto:hoju@;visi.com -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
Re: ManagedBean is not found with Ajp13Connector
Hello M., The Ajp13Connector doesn't support MBeans. You need to set up your AJP configuration with the CoyoteConnector instead. Or, just comment out the MBeans that are causing the exception. See Tomcat-4.1.12's default server.xml for reference. Jake Thursday, November 14, 2002, 2:12:41 PM, you wrote: AMP> I have just completed setting up the Apache 1.3.27 web server which will be AMP> used with Tomcat 4.1 to serve the servlet and jsp pages. I am also using AMP> j2sdk1.4.0_02. I have set up the configuration of my server.xml and AMP> https.conf files as described in the tomcat online help for the AMP> ajp13Connector. When I run them, however, I get an exception stack that AMP> looks like this (this is from my stdout.log file): AMP> Bootstrap: Create Catalina server AMP> Bootstrap: Starting service AMP> ServerLifecycleListener: createMBeans: MBeanException AMP> java.lang.Exception: ManagedBean is not found with Ajp13Connector AMP> at AMP> org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:369) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:777) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:751) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy AMP> cleListener.java:339) AMP> at AMP> org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife AMP> cycleListener.java:206) AMP> at AMP> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor AMP> t.java:166) AMP> at AMP> org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) AMP> at AMP> org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:271) AMP> at java.lang.reflect.Method.invoke(Native Method) AMP> at AMP> org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245 AMP> ) AMP> at AMP> org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) AMP> Starting service Tomcat-Standalone AMP> Apache Tomcat/4.1.12 AMP> The server works fine and I can invoke my servlets and jsp pages through AMP> apache without a problem. My question concerns this error. I have searched AMP> the net to find an answer but I can't find what this problem is. I am AMP> satisfied that I have configured the servers properly since I can view my AMP> pages but I need to know what that error is so I can be satisfied it won't AMP> cause any future problems. AMP> Any help would be greatly appreciated!! AMP> Paul AMP> -- AMP> To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> AMP> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- Best regards, Jacobmailto:hoju@;visi.com -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
ManagedBean is not found with Ajp13Connector
I have just completed setting up the Apache 1.3.27 web server which will be used with Tomcat 4.1 to serve the servlet and jsp pages. I am also using j2sdk1.4.0_02. I have set up the configuration of my server.xml and https.conf files as described in the tomcat online help for the ajp13Connector. When I run them, however, I get an exception stack that looks like this (this is from my stdout.log file): Bootstrap: Create Catalina server Bootstrap: Starting service ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:369) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:777) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:751) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecy cleListener.java:339) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLife cycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) at org.apache.catalina.startup.CatalinaService.start(CatalinaService.java:271) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.BootstrapService.start(BootstrapService.java:245 ) at org.apache.catalina.startup.BootstrapService.main(BootstrapService.java:307) Starting service Tomcat-Standalone Apache Tomcat/4.1.12 The server works fine and I can invoke my servlets and jsp pages through apache without a problem. My question concerns this error. I have searched the net to find an answer but I can't find what this problem is. I am satisfied that I have configured the servers properly since I can view my pages but I need to know what that error is so I can be satisfied it won't cause any future problems. Any help would be greatly appreciated!! Paul -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
