Server startup with Tomcat
I see how servlets can be loaded at the startup of Tomcat and you can pass initialization parameters to it. Is this the mechanism if you wanted to start additional thread classes that are not servlets? I have a queue class and a thread that acts on the queue. When items are added, it processes them a removes it from the queue. I'd like to have these be created and running at the Tomcat startup. Is there a more preferred mechanism for accomplishing this?
Basically, when Tomcat starts, I would like a few singleton classes to be created and available. With the queue example, if the Tomcat restarts, it should be able to rebuild itself from stored information on continue executing.
Take a look at listeners:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/servlet
pi/javax/servlet/ServletContextListener.html
You could listen to the start/stop of the context, and
then initialize your singletons.
Patrickokay, I see how that can be done. Is this the preferred method or pattern? Would the event be thrown if there were servlets that loaded upon startup or would it only start when a user accessed it?
Similar Messages
-
Remote Server Debugging with Tomcat and Eclipse
Hi ,
I am using Tomcat 4.0, Jdk1.3 and eclipse 2.1 ,Windows 2000
I am trying for past 5 days, Remote Server Debugging.
But I can't acheive.Please help in this tough situation.
I have configured Tomcat to run in debug mode by the following steps:
1) In catalina.bat, SET CATALINA_OPTS=-server -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000
2) Then I set the JAVA_HOME AND TOMCAT_HOME in the environment mode.
3) Then I clicked the startup.bat in the bin directory.
In Eclipse side , I followed as,
1) Run/Debug/Remote Java Application/New/
In the connect tab, I gave host:localhost and port:8000
2) Then I clicked Debug button.
I didn't use any plugin.
But it producing "Failed to connect to Remote VM.Connection refused."
So I gave host:localhost and port:8080 in eclipse side,
but this I am getting errorin eclipse side as "Failed to connect to Remote VM".In server side, I am getting error as,
java.lang.NullPointerException
at org.apache.catalina.connector.http.HttpResponseStream.checkHead(HttpR
esponseStream.java:253)
at org.apache.catalina.connector.http.HttpResponseStream.<init>(HttpResp
onseStream.java:104)
at org.apache.catalina.connector.http.HttpResponseImpl.createOutputStrea
m(HttpResponseImpl.java:220)
at org.apache.catalina.connector.ResponseBase.getOutputStream(ResponseBa
se.java:725)
at org.apache.catalina.connector.ResponseBase.finishResponse(ResponseBas
e.java:469)
at org.apache.catalina.connector.HttpResponseBase.finishResponse(HttpRes
ponseBase.java:236)
at org.apache.catalina.connector.http.HttpResponseImpl.finishResponse(Ht
tpResponseImpl.java:288)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcesso
r.java:1039)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.ja
va:1107)
at java.lang.Thread.run(Thread.java:484)
Please do the needful
If you have anwser, Please mail to [email protected]Well, once you're already using MyEclipse, I have it set up even simpler than that. Go to Window/Preferences/MyEclipse/Application Servers/Tomcat4/Launch and set the launch mode to debug.
This works if the project is successfully setup as a webproject in MyEclipse.
My problem is that I have a project that was not developed with MyEclipse and for some reason does not work when I set it up as a web project in MyEclipse. MyEclipse seem to do something funny with it when I establish the project. Now, if I set it up simply as a java project (as oppposed to Web Project) in myEclipse, then MyEclipse does not give me an option of deploying it.
Any ideas about how I would go about debugging a project that's not set up as a Web Project in my eclipse? -
Hi guys,
I am with a very strange problem with my job here.
We had a server working with Tomcat 5 and it didn't have problem, but wanted to changed to Tomcat 6.
So.. we changed and it ran normal and well.
The problem is when we stress the server with one or more big queries, execptions is showed that didn't show with Tomcat 5:
java.lang.Exception: [Microsoft][SQLServer 2000 Driver for JDBC]Object has been closed
Using SQL Server 2000
java.lang.Exception: The connection is closed.
Using SQL Server 2005
java.lang.Exception: I/O Error: socket closed.
Using SQL Server 2005 with jTDS driver
It happens with Oracle too.
Can anybody help me?
Thanks!hi i'm having a similar problem launching a servlet in eclipse. I did the above changes and still nothing:
instead i keep getting :
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Wrapper cannot find servlet class DataServlet or a class it depends on -
Need help to conect a server application with Tomcat by JNDI
exactly what are you trying to do with jndi & tomcat?
-
How do I uninstall SyncMate Server, Activity Monitor shows it still there after appzapper uninstall of SyncMate app? Killing in AM proceeds with a SyncMate Server startup again??
Mavricks, MacbookPro, typical config of everything and standard business user, no heavy graphics, animation or media editing. MS Office, web apps, etc.
I have the same issue with Logmein, which I installed a trial, uninstalled with appzapper, which I thought does a good job of untangling the components of apps but for these 2 it doesn't. Any help would be greatly appreciated.
Thx,Usually applications like these have their own uninstallers, either build into the installer ( ! ) itself or as a separate uninstaller app. Check the site of the software provider for instructions.
Here's the instructions for SyncMate: http://wiki.eltima.com/user-guides/syncmate-mac-os/uninstall.html
And LogMeIn: http://help.logmein.com/SelfServiceKnowledgeRenderer?type=FAQ&id=kA030000000DGF1 CAO&kw= -
Error with SQL Server 2000 and Tomcat 4.1.12
I'm using a JDBC Datasource with Tomcat 4.1.12 as follows.
Server.xml snippet:
<Resource name="jdbc/indemand" scope="Shareable" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/indemand">
<parameter>
<name>validationQuery</name>
<value>select top 100 * from Subscriber</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:microsoft:sqlserver://vc34:1433;databaseName=TibcoClearHouse</value>
</parameter>
<parameter>
<name>password</name>
<value>tibco_user</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>10</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>5000</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>com.microsoft.jdbcx.sqlserver.SQLServerDataSource</value>
</parameter>
<parameter>
<name>username</name>
<value>tibco_user</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>2</value>
</parameter>
</ResourceParams>
END OF Server.xml Snippet
My Web XML specifies the JDBC resource as follows:
<resource-ref>
<description>Clearinghouse DB Connectio</description>
<res-ref-name>jdbc/indemand</res-ref-name>
<res-type>com.microsoft.jdbcx.sqlserver.SQLServerDataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
When I cause a database access within my application, I get the following horrifying result. It's the "Error Establishing Socket" error that's worrying me, as I'm using the native Microsoft SQL Server Drivers. The ones in my lib directory are msutil.jar, msutil.jar, and mssqlserver.jar
Any thoughts?
John
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at com.thoughtworks.util.pool.JDCConnectionPool.getConnection(JDCConnectionPool.java:174)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnectionForTibco(ConnectionFactory.java:59)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnection(ConnectionFactory.java:40)
at com.thoughtworks.clearinghouse.util.DatabaseUtility.getUserByName(DatabaseUtility.java:123)
at com.thoughtworks.clearinghouse.web.service.UserProfileService.validateUserNamePassword(UserProfileService.jav
a:16)
at com.thoughtworks.clearinghouse.web.servlet.LogonAction.actionExecuted(LogonAction.java:48)
at com.thoughtworks.clearinghouse.web.servlet.AbstractAction.execute(AbstractAction.java:38)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:437)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:264)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1109)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:470)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.StandardContext.invoke(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.invokeNext(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:405)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:536)
com.thoughtworks.clearinghouse.util.SystemException: failed to load user
at com.thoughtworks.clearinghouse.util.DatabaseUtility.getUserByName(DatabaseUtility.java:147)
at com.thoughtworks.clearinghouse.web.service.UserProfileService.validateUserNamePassword(UserProfileService.jav
a:16)
at com.thoughtworks.clearinghouse.web.servlet.LogonAction.actionExecuted(LogonAction.java:48)
at com.thoughtworks.clearinghouse.web.servlet.AbstractAction.execute(AbstractAction.java:38)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:437)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:264)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1109)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:470)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.StandardContext.invoke(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.invokeNext(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:405)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at com.thoughtworks.util.pool.JDCConnectionPool.getConnection(JDCConnectionPool.java:174)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnectionForTibco(ConnectionFactory.java:59)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnection(ConnectionFactory.java:40)
at com.thoughtworks.clearinghouse.util.DatabaseUtility.getUserByName(DatabaseUtility.java:123)
... 38 more
Cause:
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at com.thoughtworks.util.pool.JDCConnectionPool.getConnection(JDCConnectionPool.java:174)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnectionForTibco(ConnectionFactory.java:59)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnection(ConnectionFactory.java:40)
at com.thoughtworks.clearinghouse.util.DatabaseUtility.getUserByName(DatabaseUtility.java:123)
at com.thoughtworks.clearinghouse.web.service.UserProfileService.validateUserNamePassword(UserProfileService.jav
a:16)
at com.thoughtworks.clearinghouse.web.servlet.LogonAction.actionExecuted(LogonAction.java:48)
at com.thoughtworks.clearinghouse.web.servlet.AbstractAction.execute(AbstractAction.java:38)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:437)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:264)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1109)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:470)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.StandardContext.invoke(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(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.invokeNext(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:405)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:536)You can check two things
1. Whether the ports to the database server are blocked by a fire wall.
2. And more simpler and most probably the case here, you can try to findout if you can see the database server from the webserver. i.e. ping the database server from a console in the webserver. -
Server Startup issue with Weblogic 10!!!
Hi All,
We are on weblogic 10 and have deployed few portlets along with Vignette Portl 7.4. Whenever, we are doing a restart of managed server, we are getting below error in managed01.out:
Failed to load servlet Class: FileOutputServletIgnoring: unable to load class:java.lang.ClassNotFoundException: FileOutputServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: FileOutputServletIgnoring: unable to load class:java.lang.ClassNotFoundException: FileOutputServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)log4j:ERROR Could not parse address [].
javax.mail.internet.AddressException: Illegal address in string ``''
at javax.mail.internet.InternetAddress.<init>(InternetAddress.java:66)
at org.apache.log4j.net.SMTPAppender.getAddress(Unknown Source)
at org.apache.log4j.net.SMTPAppender.activateOptions(Unknown Source)
at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
After this, all applications are starting up without any issue. Please let me know if someone have already faced this issue before or any pointers on this?
Thanks & Regards,
SanjeevHi,
I have deployed 10 or more portlets on same managed server and every portlet have a logging initiator servlet which uses log4j. During managed server startup, above exception only comes ones and after that, all portlets are starting fine. There is no issue at all with other portlet.
I was getting same error if I am not having log4j.jar in manged server JVM startup classpath for every portlet. But, once I added log4j.jar to classpath, it is coming only once and after that, all portlets are starting fine.
Any pointer to look at? I tried to add log4j.properties to startup classpath as well, but with no luck :(
Thanks,
Sanjeev -
Debug the Flex Application with tomcat Server
Hi,
I have the adobe flex builder plugin with my eclipse and I created a Flex project which is running on my Tomcat Server. Now, I would like to run my application in debug mode and I could not see the debug perspective. But, if my application is not configured with tomcat server, I can the debug perspective in my eclipse.
Do we need to do any additional settings for viewing the debug perspective for Flex Applications which is configured in tomcat Server?You can't debug an app on the server, at least not using the debug perspective. Troubleshooting deployed apps if far more difficult.
If this post answers your question or helps, please mark it as such. -
Hi ,
I want to add the conext information to my server.xml of tomcat for my hibernate configuration.....
the conext information is as follows ....
<Context path="/quickstart" docBase="quickstart">
<Resource name="jdbc/quickstart" scope="Shareable" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/quickstart">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<!-- DBCP database connection settings -->
<parameter>
<name>url</name>
<value>jdbc:postgresql://localhost/quickstart</value>
</parameter>
<parameter>
<name>driverClassName</name><value>org.postgresql.Driver</value>
</parameter>
<parameter>
<name>username</name>
<value>quickstart</value>
</parameter>
<parameter>
<name>password</name>
<value>secret</value>
</parameter>
<!-- DBCP connection pooling options -->
<parameter>
<name>maxWait</name>
<value>3000</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>100</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>10</value>
</parameter>
</ResourceParams>
</Context>
Where in my server.xml should i put
the server.xml looks like this :
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="8005" shutdown="SHUTDOWN">
<!-- Comment these entries out to disable JMX MBeans support used for the
administration web application -->
<Listener className="org.apache.catalina.core.AprLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
<Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
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" />
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Catalina">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 5 documentation bundle for more detailed
instructions):
* If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector
port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to 0 -->
<!-- Note : To use gzip compression you could set the following properties :
compression="on"
compressionMinSize="2048"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml"
-->
<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
<!--
<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
-->
<!-- Define an AJP 1.3 Connector on port 8009 -->
<Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
<!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector port="8082"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" acceptCount="100" connectionTimeout="20000"
proxyPort="80" disableUploadTimeout="true" />
-->
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- You should set jvmRoute to support load-balancing via AJP ie :
<Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">
-->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Catalina" defaultHost="localhost">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.4
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- Because this Realm is here, an instance will be shared globally -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!--
<Realm className="org.apache.catalina.realm.MemoryRealm" />
-->
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority"
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!-- Define the default virtual host
Note: XML Schema validation will not work with Xerces 2.2.
-->
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
<!-- Defines a cluster for this node,
By defining this element, means that every manager will be changed.
So when running a cluster, only make sure that you have webapps in there
that need to be clustered and remove the other ones.
A cluster has the following parameters:
className = the fully qualified name of the cluster class
name = a descriptive name for your cluster, can be anything
mcastAddr = the multicast address, has to be the same for all the nodes
mcastPort = the multicast port, has to be the same for all the nodes
mcastBindAddr = bind the multicast socket to a specific address
mcastTTL = the multicast TTL if you want to limit your broadcast
mcastSoTimeout = the multicast readtimeout
mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat
mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received
tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes
tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
in case of multiple ethernet cards.
auto means that address becomes
InetAddress.getLocalHost().getHostAddress()
tcpListenPort = the tcp listen port
tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
has a wakup bug in java.nio. Set to 0 for no timeout
printToScreen = true means that managers will also print to std.out
expireSessionsOnShutdown = true means that
useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
false means to replicate the session after each request.
false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
<%
HashMap map = (HashMap)session.getAttribute("map");
map.put("key","value");
%>
replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
* Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
* Synchronous means that the thread that executes the request, is also the
thread the replicates the data to the other nodes, and will not return until all
nodes have received the information.
* Asynchronous means that there is a specific 'sender' thread for each cluster node,
so the request thread will queue the replication request into a "smart" queue,
and then return to the client.
The "smart" queue is a queue where when a session is added to the queue, and the same session
already exists in the queue from a previous request, that session will be replaced
in the queue instead of replicating two requests. This almost never happens, unless there is a
large network delay.
-->
<!--
When configuring for clustering, you also add in a valve to catch all the requests
coming in, at the end of the request, the session may or may not be replicated.
A session is replicated if and only if all the conditions are met:
1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
2. a session exists (has been created)
3. the request is not trapped by the "filter" attribute
The filter attribute is to filter out requests that could not modify the session,
hence we don't replicate the session after the end of this request.
The filter is negative, ie, anything you put in the filter, you mean to filter out,
ie, no replication will be done on requests that match one of the filters.
The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.
filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
ending with .gif and .js are intercepted.
The deployer element can be used to deploy apps cluster wide.
Currently the deployment only deploys/undeploys to working members in the cluster
so no WARs are copied upons startup of a broken node.
The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
When a new war file is added the war gets deployed to the local instance,
and then deployed to the other instances in the cluster.
When a war file is deleted from the watchDir the war is undeployed locally
and cluster wide
-->
<!--
<Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
managerClassName="org.apache.catalina.cluster.session.DeltaManager"
expireSessionsOnShutdown="false"
useDirtyFlag="true"
notifyListenersOnReplication="true">
<Membership
className="org.apache.catalina.cluster.mcast.McastService"
mcastAddr="228.0.0.4"
mcastPort="45564"
mcastFrequency="500"
mcastDropTime="3000"/>
<Receiver
className="org.apache.catalina.cluster.tcp.ReplicationListener"
tcpListenAddress="auto"
tcpListenPort="4001"
tcpSelectorTimeout="100"
tcpThreadCount="6"/>
<Sender
className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
replicationMode="pooled"
ackTimeout="15000"/>
<Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
<Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
tempDir="/tmp/war-temp/"
deployDir="/tmp/war-deploy/"
watchDir="/tmp/war-listen/"
watchEnabled="false"/>
</Cluster>
-->
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across all web applications contained
in this virtual host. -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn" />
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
This access log implementation is optimized for maximum performance,
but is hardcoded to support only the "common" and "combined" patterns.
-->
<!--
<Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
</Host>
</Engine>
</Service>
</Server>
Can Some one Help me pleaseeeeeePlease don't cross-post in multiple forums. I have answered
this in your other thread. -
I am attempting to use the Tomcat servlet engine with Apache on Win 98. The versions I am using are Apache/1.3.20 and Tomcat 4.0.1. I have unzipped the tomcat binary to C:\jakarta-tomcat-4.0.1 and set CATALINA_HOME to C:\jakarta-tomcat-4.0.1.
I am running the same versions of Apache and Tomcat at work on NT 4.0 and had no problems. But on my Win 98 machine when I try to start Tomcat with "startup" I am getting the following (at least I think it is the equivalent on startup with what I'm getting on shutdown--the startup console window is closing before I can capture the message):
C:\jakarta-tomcat-4.0.1\bin>shutdown
Using CATALINA_BASE: C:\jakarta-tomcat-4.0.1
Using CATALINA_HOME: C:\jakarta-tomcat-4.0.1
Using CLASSPATH: C:\jakarta-tomcat-4.0.1\bin\bootstrap.jar;C:\jdk1.3\l
ls.jar;C:\jdk1.3\jre\lib\ext\lib\jcert.jar;C:\jdk1.3\jre\lib\ext\lib\jnet.
\jdk1.3\jre\lib\ext\lib\jsse.jar
Using JAVA_HOME: C:\jdk1.3
ERROR reading C:\jakarta-tomcat-4.0.1\conf\server.xml
At http://xml.org/sax/features/raw-names
Catalina.stop: org.xml.sax.SAXNotRecognizedException: http://xml.org/sax/f
s/raw-names
org.xml.sax.SAXNotRecognizedException: http://xml.org/sax/features/raw-nam
at org.apache.xerces.framework.XMLParser.setFeature(XMLParser.java
at org.apache.xerces.parsers.SAXParser.setFeature(SAXParser.java:5
at org.xml.sax.helpers.XMLReaderAdapter.setupXMLReader(XMLReaderAd
java:204)
at org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.jav
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:290)
at org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:2
at org.apache.catalina.startup.Catalina.stop(Catalina.java:817)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:683)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at java.lang.reflect.Method.invoke(Native Method)
Thanks in advance for your assistance.
RoyVery simple. On the start up Jakarta is looking for server.xml file. Apparently, it can not read it.
Check all your env. variables. Make sure you have
JAVA_HOME, TOMCAT_HOME set correctly. If TOMCAT_HOME is not set up correctly, it would not be able to locate server.xml file. -
I have installed..WSAD5.1.2 with 5.0 Test Environment and IBM WebSphere MQ 5.3.
I have created a PointToPoint Messaging Client. with a QueueConnectionFactory n Queue JNDI name.
I am getting following problems during the server startup...
*** Starting the server ***
************ Start Display Current Environment ************
WebSphere Platform 5.0 [BASE 5.0.2 ptf2M0325.01] running with process name localhost\localhost\server1 and process id 2088
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.3.1 IBM Windows 32 build cn131-20030711a (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5
user.install.root = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5
Java Home = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\java\jre
ws.ext.dirs = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/lib;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/classes;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/classes;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/ext;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/web/help;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.webservice_5.1.2/runtime/worf.jar
Classpath = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/properties;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/properties;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/bootstrap.jar;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/j2ee.jar;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/lib/lmproxy.jar;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wteServers.jar;C:/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wasToolsCommon.jar
Java Library path = C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5/java/jre/bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;.;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;C:\IBM\WebSphere MQ\Java\lib;C:\dev\MKS\IntegrityClient\bin;c:\dev\Perl\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\dev\cygwin\bin;C:\dev\4NT302;C:\dev\apache-ant-1.5.4\bin;C:\dev\jdk1.3.1_08\bin;C:\dev\jakarta-tomcat-4.1.30\bin;C:\dev\mksscripts\src;C:\tbs\bin;C:\Program Files\IBM\WebSphere MQ\WEMPS\bin;c:\dev\MQ\bin;C:\IBM\WebSphere MQ\Java\bin;C:\IBM\WebSphere MQ\WEMPS\bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\bin;C:\IBM\WebSphere MQ\bin;;C:\IBM\WebSphere MQ\bin;C:\IBM\WebSphere MQ\Java\bin;C:\IBM\WebSphere MQ\WEMPS\bin;C:\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\bin;.;C:\dev\NMake;C:\dev\ZipUnzip;
************* End Display Current Environment *************
[6/7/04 11:59:06:000 IST] 4eee356d ManagerAdmin I TRAS0017I: The startup trace state is *=all=disabled.
[6/7/04 11:59:06:516 IST] 4eee356d AdminInitiali A ADMN0015I: AdminService initialized
[6/7/04 11:59:07:500 IST] 4eee356d Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
[6/7/04 11:59:07:547 IST] 4eee356d SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
[6/7/04 11:59:07:641 IST] 4eee356d SecurityCompo I SECJ0309I: Java 2 Security is disabled.
[6/7/04 11:59:07:656 IST] 4eee356d SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[6/7/04 11:59:07:656 IST] 4eee356d SecurityCompo I SECJ0240I: Security service initialization completed successfully
[6/7/04 11:59:09:797 IST] 4eee356d JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager
[6/7/04 11:59:11:125 IST] 4eee356d JMSEmbeddedPr A MSGS0051I: Queue Manager open for business
[6/7/04 11:59:11:125 IST] 4eee356d JMSEmbeddedPr A MSGS0052I: Starting the Broker
[6/7/04 11:59:11:297 IST] 4eee356d SystemErr R MQJE001: Completion Code 2, Reason 2085
[6/7/04 11:59:11:297 IST] 4eee356d BrokerManager E MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
[6/7/04 11:59:11:328 IST] 4eee356d JMSService E MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1527)
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1579)
at com.ibm.ws.messaging.BrokerManager.attachToMQ(BrokerManager.java:439)
at com.ibm.ws.messaging.BrokerManager.startBroker(BrokerManager.java:234)
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:194)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Please let me know what is the problem and how to solve it. This is urgent. TnxDid you go into Websphere MQ and set up the queue you are using? Defining the queue in JNDI is not enough.
Broker Manager unable to attach to Queue Manager - unknown Queue -
JSP: work with TomCat 5.5.9 and NOT work with TomCat 6.0.16
Hi all,
I'm Antony and I have a problem with a .JSP page of my server.
In my server there are 2 users: "u1" and "u2"; there are 2 TomCat, version 5.5.9 and version 6.0.16. There is Apache WebServer version 2. The 2 TomCat servers have the same configuration files: server.xml and web.xml (in the dir /conf of the main server's root). They not work simultaneously.
When the user "root" launch the TomCat 5.5.9 all work fine: the server will show correctly the JSP pages of "u1" and the pages of "u2".
When the user "root" launch the TomCat 6.0.16 the JSP pages of "u1" work fine but the JSP pages of "u2" not work: it seems that there are problems with the path where the server want to search the pages of u2.
In the server.xml there is this code (for the handle of u2's site):
<Host name="u2site.com" appBase="/home/u2/public_html/">
<Alias>www.u2site.com</Alias>
<Context path="" reloadable="false" docBase="/home/u2/public_html/" debug="0"/>
<Context path="/manager" debug="0" privileged="true"
docBase="/usr/local/jakarta/tomcat/server/webapps/manager">
</Context>
</Host>and this code (for the u1's site)
<Host name="u1site.com" appBase="/home/u1/public_html/">
<Context path="" reloadable="false" docBase="/home/u1/public_html" debug="1"/>
<Context path="/manager" debug="0" privileged="true"
docBase="/usr/local/jakarta/tomcat/server/webapps/manager">
</Context>
</Host>The problems with the JSP pages of u2 are one of the following:
org.apache.jasper.JasperException: /login2.jsp(4,0) The value for the useBean class attribute com.u2.beans.access.Autenticator is invalid.and this one that appear with the pages that have the inclusion of another JSP page
/u2page.jsp(3,0) File "/../support/_formatting.jsp" not foundI think that the TomCat know how to find the page that the browser request to Apache WebServer (and that the webserver request to Tomcat by the connector) 'cause for pages that haven't inclusion or call to method in packages all work fine...but the TomCat have problems to locate the pages included or the method located in a JAR (the jars are located in WEB-INF/lib/ of the u2's site).
How I can resolve this problem with TomCat 6.0.16? I repeat that with TomCat 5.5.9 all work fine...same configuration!
Any ideas?
Thank you very much,
Antony.Hi stevejluke, 'cause in the page "/supporto/_formatting.jsp" there are only the definition of some variables it's normal that the output at the browser it's a blank page.
The problem it's that Tomcat 6.0.16 cannot know how "navigate" the pages beginning from one...it know where is the "x.jsp" page requested directly by Apache WebServer, where is "y.jsp" request directly by Apache, where is "z.jsp" requested directly by Apache but if "x.jsp" request, includes, "y.jsp" Tomcat cannot know where "y.jsp" is located. There is some file where I can "say" this to Tomcat?
The page "/mostre/elenco_mostre.jsp" includes directly the "/supporto/_formatting.jsp".
Another thing: in /mostre/elenco_mostre.jsp there is an inclusion directive for /supporto/_formatting.jsp that is so:
<%@ include file="../supporto/_formatting.jsp"%>you can see that the included file is "../supporto/_formatting.jsp" and NOT "/../supporto/_formatting.jsp"...the "/" at the begin of the path is included by Tomcat!
In the catalina.out there are this lines, when the page is called:
Jul 6, 2008 3:15:00 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /elenco_mostre.jsp(3,0) File "/../supporto/_formatting.jsp" not found
In catalina.out before server start there are this lines:
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '1' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '1' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '1' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '1' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '1' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '1' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
Jul 6, 2008 1:43:49 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 358 ms
Jul 6, 2008 1:43:49 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jul 6, 2008 1:43:49 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.16
Jul 6, 2008 1:43:52 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/23 config=null
Jul 6, 2008 1:43:52 AM org.apache.catalina.connector.MapperListener registerEngine
WARNING: Unknown default host: localhost
Jul 6, 2008 1:43:52 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2512 msThe file "web.xml" is located in "$Tomcat_home/conf" and it's:
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4">
<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>xpoweredBy</param-name>
<param-value>false</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>jsp</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>jsp</servlet-name>
<url-pattern>*.jspx</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>30</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
</web-app>there are not web.xml file in /WEB-INF/ of the web application.
Maybe the problem it's that Tomcat want the conf file in "Server/Service/Engine/Host/Context" ? I must move the block HOST of the server.xml file in this path?
Good Sunday and thank you!
Antony. -
Server.xml in tomcat access denied
hello,
I am using tomcat 5.5.9 with suse (linux), and I am using jdk 1.6.0
The CATALINA_HOME, JAVA_HOME are defined,
When I try to startup the tomcat as root user every thing is ok, it
start (with port 8080)
I have create a new user with permissions to logs and work
directories, and try to startup the tomcat from command
like that su - tomcatuser -c /user/tomcathome/bin/startup.sh
every thing is ok
but wenn I try to start it from eclipse I get this message:
In Catalina.out
Jul 12, 2006 6:03:26 PM org.apache.catalina.startup.Catalina load
WARNING: Can't load server.xml
Jul 12, 2006 6:03:26 PM org.apache.catalina.startup.Catalina load
WARNING: Can't load server.xml
Jul 12, 2006 6:03:26 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 0 ms
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
Caused by: java.lang.NullPointerException
at org.apache.catalina.startup.Catalina.await(Catalina.java:600)
at org.apache.catalina.startup.Catalina.start(Catalina.java:560) Can any one help,
ThanksClick Start, click Run, type cmd in the
Open box, and then click OK.
Switch to the <var>Drive</var>:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 folder. In this folder, <var>Drive</var> is the drive where Windows is installed. To do this, type the following line at the command prompt, and then press Enter:
cd <var>Drive</var>:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
Add the appropriate permissions to the Network Service group for the Temporary ASP.NET Files folder. To do this, type the following line, and then press Enter:
aspnet_regiis -ir
cd <var>Drive</var>:\WINDOWS\Microsoft.NET\Framework\v4
Add the appropriate permissions to the Network Service group for the Temporary ASP.NET Files folder. To do this, type the following line, and then press Enter:
aspnet_regiis -ir
http://social.technet.microsoft.com/Forums/sharepoint/en-US/bf6bb272-eb75-4435-8264-6980e9e7268f/sharepoint-server-2010-access-denied-error?forum=sharepointadminprevious
Is this a claims based web application? If yes, the super reader and super user need to be added with the in the format "i:0#.w|domain\username". Also, add them with full read and full control on the web application as well.
Check AAM settings
Can you check that your databases are not set to read only. I had a similar issue after backing up the farm users were not allowed to do anything on the site. Turned out the database was set to read only in SQL.
If this helped you resolve your issue, please mark it Answered -
Error while running application with Tomcat 5.0
Hi,
I am trying to run my application on Tomcat 5.0. I have java environment version 1.4
I am getting the following error during the server start up :
Mar 30, 2007 3:51:03 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Mar 30, 2007 3:51:03 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1047 ms
Mar 30, 2007 3:51:03 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Mar 30, 2007 3:51:03 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.28
Mar 30, 2007 3:51:03 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Mar 30, 2007 3:51:03 PM org.apache.catalina.core.StandardHost
getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Mar 30, 2007 3:51:03 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Processing Context configuration file URL file:C:\Program
Files\Apache Sof
tware Foundation\Tomcat 5.0\conf\Catalina\localhost\admin.xml
Mar 30, 2007 3:51:04 PM org.apache.struts.util.PropertyMessageResources
<init>
INFO: Initializing, config='org.apache.struts.util.LocalStrings',
returnNull=tru
e
Mar 30, 2007 3:51:04 PM org.apache.struts.util.PropertyMessageResources
<init>
INFO: Initializing, config='org.apache.struts.action.ActionResources',
returnNul
l=true
Mar 30, 2007 3:51:05 PM org.apache.struts.util.PropertyMessageResources
<init>
INFO: Initializing,
config='org.apache.webapp.admin.ApplicationResources', retur
nNull=true
Mar 30, 2007 3:51:06 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Processing Context configuration file URL file:C:\Program
Files\Apache Sof
tware Foundation\Tomcat 5.0\conf\Catalina\localhost\balancer.xml
Mar 30, 2007 3:51:07 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Processing Context configuration file URL file:C:\Program
Files\Apache Sof
tware Foundation\Tomcat 5.0\conf\Catalina\localhost\manager.xml
Mar 30, 2007 3:51:07 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /jsp-examples from URL
file:C:\
Program Files\Apache Software Foundation\Tomcat 5.0\webapps\jsp-examples
Mar 30, 2007 3:51:07 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path from URL
file:C:\Program Files
\Apache Software Foundation\Tomcat 5.0\webapps\ROOT
Mar 30, 2007 3:51:07 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /servlets-examples from
URL fil
e:C:\Program Files\Apache Software Foundation\Tomcat
5.0\webapps\servlets-exampl
es
Mar 30, 2007 3:51:07 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /tomcat-docs from URL
file:C:\P
rogram Files\Apache Software Foundation\Tomcat 5.0\webapps\tomcat-docs
Mar 30, 2007 3:51:07 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /webdav from URL
file:C:\Progra
m Files\Apache Software Foundation\Tomcat 5.0\webapps\webdav
Mar 30, 2007 3:51:07 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Mar 30, 2007 3:51:07 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Mar 30, 2007 3:51:07 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/31 config=C:\Program Files\Apache Software
Foundat
ion\Tomcat 5.0\conf\jk2.properties
Mar 30, 2007 3:51:08 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 4266 ms
Mar 30, 2007 3:53:07 PM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /Hyperceller from URL
file:C:\P
rogram Files\Apache Software Foundation\Tomcat 5.0\webapps\Hyperceller
Mar 30, 2007 3:53:08 PM org.apache.struts.util.PropertyMessageResources
<init>
INFO: Initializing, config='org.apache.struts.util.LocalStrings',
returnNull=tru
e
Mar 30, 2007 3:53:08 PM org.apache.struts.util.PropertyMessageResources
<init>
INFO: Initializing, config='org.apache.struts.action.ActionResources',
returnNul
l=true
Mar 30, 2007 3:53:09 PM org.apache.commons.digester.Digester
startElement
SEVERE: Begin event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.commons.beanutils.PropertyUtils.setSimpleProperty(Property
Utils.java:1656)
at
org.apache.commons.beanutils.PropertyUtils.setNestedProperty(Property
Utils.java:1551)
at
org.apache.commons.beanutils.PropertyUtils.setProperty(PropertyUtils.
java:1580)
at
org.apache.commons.beanutils.BeanUtils.setProperty(BeanUtils.java:919
at
org.apache.commons.beanutils.BeanUtils.populate(BeanUtils.java:726)
at
org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule
.java:251)
at org.apache.commons.digester.Rule.begin(Rule.java:152)
at
org.apache.commons.digester.Digester.startElement(Digester.java:1361)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour
ce)
at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unkn
own Source)
at
org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown Sourc
e)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unkn
own Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.commons.digester.Digester.parse(Digester.java:1647)
at
org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionSe
rvlet.java:1006)
at
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet
.java:955)
at
org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
java:1029)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:86
2)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex
t.java:4013)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4
357)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:823)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:80
7)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDep
loyer.java:277)
at
org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j
ava:701)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:432
at
org.apache.catalina.startup.HostConfig.check(HostConfig.java:1083)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:327)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:119)
at
org.apache.catalina.core.StandardHost.backgroundProcess(StandardHost.
java:800)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
rocessChildren(ContainerBase.java:1619)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
rocessChildren(ContainerBase.java:1628)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.r
un(ContainerBase.java:1608)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.UnsupportedClassVersionError:
com/hyperceller/form/LoginFor
m (Unsupported major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
3)
at
org.apache.catalina.loader.WebappClassLoader.findClassInternal(Webapp
ClassLoader.java:1634)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoa
der.java:860)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
der.java:1307)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
der.java:1189)
at
org.apache.struts.config.FormBeanConfig.formBeanClass(FormBeanConfig.
java:320)
at
org.apache.struts.config.FormBeanConfig.setType(FormBeanConfig.java:1
91)
... 46 more
Mar 30, 2007 3:53:09 PM org.apache.struts.action.ActionServlet
handleConfigExcep
tion
SEVERE: Parsing error processing resource path
java.lang.reflect.InvocationTargetException
at
org.apache.commons.digester.Digester.createSAXException(Digester.java
:2919)
at
org.apache.commons.digester.Digester.createSAXException(Digester.java
:2945)
at
org.apache.commons.digester.Digester.startElement(Digester.java:1364)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour
ce)
at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unkn
own Source)
at
org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown Sourc
e)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unkn
own Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.commons.digester.Digester.parse(Digester.java:1647)
at
org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionSe
rvlet.java:1006)
at
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet
.java:955)
at
org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
java:1029)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:86
2)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex
t.java:4013)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4
357)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:823)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:80
7)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDep
loyer.java:277)
at
org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.j
ava:701)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:432
at
org.apache.catalina.startup.HostConfig.check(HostConfig.java:1083)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:327)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:119)
at
org.apache.catalina.core.StandardHost.backgroundProcess(StandardHost.
java:800)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
rocessChildren(ContainerBase.java:1619)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.p
rocessChildren(ContainerBase.java:1628)
at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.r
un(ContainerBase.java:1608)
at java.lang.Thread.run(Thread.java:534)
Mar 30, 2007 3:53:44 PM org.apache.struts.util.PropertyMessageResources
<init>
INFO: Initializing, config='org.apache.struts.taglib.html.LocalStrings',
returnN
ull=true
Mar 30, 2007 3:53:44 PM org.apache.struts.util.PropertyMessageResources
<init>
INFO: Initializing, config='org.apache.struts.util.LocalStrings',
returnNull=tru
e
Mar 30, 2007 3:53:44 PM org.apache.struts.util.PropertyMessageResources
<init>
INFO: Initializing, config='org.apache.struts.taglib.html.LocalStrings',
returnN
ull=true
could anyone tell me what the problem may be???
Note: When I configure my application on the Tomcat 5.5 and java 1.5 then it runs fine. But the problem arises when I compile my code on the java 1.4 and run on the Tomcat 5.0
Thanks in advance!!I am sorry that I forgot to tell you that I am running a struts application. Struts 1.1
-
Message bean does not start automatically during application server startup
I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
at java.lang.Class.getConstructor0(Class.java:1930)
at java.lang.Class.newInstance0(Class.java:278)
at java.lang.Class.newInstance(Class.java:261)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:379)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve
Maybe you are looking for
-
Problem with Queue and linked list
Hi... i've got an assignment it start like this. You are required to write a complete console program in java includin main() to demonstrate the following: Data Structure: Queue, Priority Queue Object Involved: Linked-List, PrintJob Operations Involv
-
Time Capsule and Thunderbolt HDD very slow access via wifi enabled MacBook Air
I have a Q-RAID thunderbolt external drive attached to the Time Capsule. I use it to archive movies for viewing via a media server around the house (mostly via WIFI). Using my MacBook Air to access the files, performance is very spotty. Sometimes
-
Cant get into BIOS via DEL key, screen goes blank on load RD240
Hello group, having an issue with a RD240 rackmount server attempting to bring it online for the first time. Currently in a one CPU configuration with one stick on RAM in the correct slot, using SAS. When the computer first boots prompting you to hit
-
Project Server 2010 Adding attachments to PDP
Is there a way for a user to attach documents to a PDP? I understand that in SharePoint you can add attach documents to a list. How would I combine the two? Thanks! David L. Crooks
-
RfcAdapter received a synchronous message. Trying to send sRFC for SALERT_C
Hi All, I am receiving the message 'RfcAdapter received a synchronous message. Trying to send sRFC for SALERT_CREATE' in my receiver RFC channel used to trigger alerts from PI to ECC. no emails are getting generated. Please advice. Regards.