You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Andy Cohen <ac...@stanford.edu> on 2004/12/20 18:29:59 UTC

Admin app fails with "MBeanServer is not available"

I've searched the mailing list archives, and the net at large, but I haven't
seen anyone report this problem for Tomcat 5:

I downloaded and installed Tomcat 5.5.4, and version 5.5.4 of the Admin
webapp. The Admin webapp starts up fine, but when I click on the
"Environment Entries" button in the Admin webapp, I get the error message
which I've appended to this email. I've tried downloading various
incarnations of JMX jars, and putting them in various Tomcat folders, as
some archived messages recommended for this problem under Tomcat 4.x, but
to no avail.

Is this a real bug, or am I just doing something wrong?

Thanks for any help,

    Andy Cohen
    System Software Developer
    acohen@stanford.edu

================================================================================

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it
from fulfilling this request.

exception

javax.servlet.ServletException: MBeanServer is not available
	org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:845)
	org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:778)
	admin.resources.listEnvEntries_jsp._jspService(listEnvEntries_jsp.java:437)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
	org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:388)
	org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
	org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
	org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:388)
	org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
	org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

root cause

javax.servlet.jsp.JspException: MBeanServer is not available
	org.apache.webapp.admin.AttributeTag.doEndTag(AttributeTag.java:163)
	admin.resources.listEnvEntries_jsp._jspx_meth_controls_attribute_0(listEnvEntries_jsp.java:766)
	admin.resources.listEnvEntries_jsp._jspService(listEnvEntries_jsp.java:380)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
	org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:388)
	org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
	org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
	org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:388)
	org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
	org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

autodeploy

Posted by Andreas Vombach <an...@psi.ch>.
For some reason if I use a db pool the auto-deploy of war files does not 
seem to work anymore. The change in the server.xml is that the 
jndi-ressources have to be declared.
Are there any known influences? The dbcp only works if I declare it for 
my app, a "global" one is not being found.

  <Service name="Catalina">
    <Connector port="80" redirectPort="8443" maxSpareThreads="75" 
maxThreads="150" minSpareThreads="25">
    </Connector>
    <Connector port="8009" protocol="AJP/1.3" 
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" 
redirectPort="8443">
    </Connector>
    <Engine defaultHost="localhost" name="Catalina">
      <Host name="localhost" appBase="webapps" unpackWARs="true" 
autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false">
        <Context displayName="myapp" docBase="myapp" path="/myapp" 
workDir="work\Catalina\localhost\myapp">
          <Resource auth="Container" description="" 
name="jdbc/JNDI_myapp" type="javax.sql.DataSource" password="***" 
driverClassName="oracle.jdbc.driver.OracleDriver" maxIdle="10" 
maxWait="-1" username="user" url="jdbc:oracle:thin:@mydriver" 
maxActive="20"/>
        </Context>
      </Host>
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"/>
    </Engine>
  </Service>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org