Tomcat context problem
I am working on a webapplication with Tomcat4.1. I have a MenuUtil.xml in the folder
D:\Tomcat4\webapps\MyApp\WEB-INF\classes\com\\web\myapp
and I have menu.dtd in the same folder.I want to refer to this dtd from the xml file
like
<!DOCTYPE Menus SYSTEM "com/web/myapp/menu.dtd">
But gives FileNotFoundException..
Even <!DOCTYPE Menus SYSTEM "web-inf/classes/com/web/myapp/menu.dtd"> is not working..
Please help
did you try:
<!DOCTYPE Menus SYSTEM "menu.dtd">
Similar Messages
-
Opening an attachment from outside the tomcat context
I am creating a simple mail software. In my incoming message screen i'm showing all the Attachments as hyperlinks. I want that when the user clicks the hyperlink the Attachment should open in a new browser window.
My problem is that the attachments are there in a folder outside the tomcat context i.e. in a folder outside the tomcat's folder on the server's c:/Attachments folder.
If I put the attachments in the root folder of my application under webapps folder it is working properly. But I want to open it from the outside folder c:/Attachments, and also I can't hardcode this path in my code. It can be any path outside tomcat.
Please help me, if u have any solution.Make that path a parameter in web.xml
<context-param>
<param-name>beginyear</param-name>
<param-value>2004</param-value>
<description>starting year of the application</description>
</context-param> -
Apache webserver can't find tomcat - mod_jk problem?
Hi
I have recently upgraded HP-UX apache software
FROM
Apache webserver: 2.0.55
Apache tomcat : 5.5.9
TO
Apache webserver: 2.0.55
Apache tomcat : 5.5.9
I have 2 tomcats running, one JVM for a daytime service and another for a nighttime service.
So while 1 tomcat is down, the other is up, apache always running.
However, since I have upgraded, I see the following error messages in jk.log:
[Mon Nov 20 07:00:41 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common
.c (949): ERROR: can't receive the response message from tomcat, network problems or tomcat is down (127.0.0.1:8059), err=-232
The tomcat in question is up - and the messages returned are 500 responses - server configuration issue.
Get several a day.
Basically using mod_jk to bind the tomcat installations to apache webserver.
What is new though in mod_jk 1.2.10 is that a shared memory file is specified. I am wondering what happens to this memory that is used to load balance the workers when tomcats are bounced.
Issues go away after a bounce of apache - but after each tomcat has been stopped once - messages start to fail intermittently after that.
Done some googling but do not see any solutions - so here's hoping!
Thanks.Noticed my deliberate mistake!
From
Apache 2.0.32
Tomcat 3
Still no joy with with this in terms of finding a solution to why the newer version of apache cannot find tomcat after it has been bounced.
mod_jk.so version 1.2.9 introduced the shared memory for the workers, which as far as I can is the main config change in the 2 versions of apache that came from HP.
So rolled back to the old version of apache with the new version of tomcat - and everything works fine! -
Error in Tomcat --- context start up failed due to previous errors
Feb 27, 2008 11:05:11 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/jstl] startup failed due to previous errors
Feb 27, 2008 11:05:13 AM com.sun.faces.config.rules.ComponentRule end
WARNING: [ComponentRule]{faces-config/component} Merge(com.mycompany.TabLabel)
Feb 27, 2008 11:05:13 AM com.sun.faces.config.rules.ComponentRule end
WARNING: [ComponentRule]{faces-config/component} Merge(com.mycompany.Tree)
Feb 27, 2008 11:05:13 AM com.sun.faces.config.rules.ValidatorRule end
WARNING: [ValidatorRule]{faces-config/validator} Merge(com.mycompany.jsf.validat
or.LATER_THAN)
Feb 27, 2008 11:05:14 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Feb 27, 2008 11:05:14 AM org.apache.catalina.core.StandardContext startHello frnds i dont understand what should i do? anybody familiar with this kind of error. please let me know in this case what should i do?
even if i am trying to copy whole files in another folder it shows same msg for that folder too. please help me
Thankyou everybodyHi ,
I also face this same kind of problem.
I tried to fix the problem but not work out.
I got another solution. I am not sure its a current solution .
Try it carefully.
Finally 1, I take back up -copy of server.xml and common/lib .
2, Un-install Tomcat server.
3, After i have installed fresh tomcat server.
4, Replace back-up copy of server.xml and common/lib.
its working fine -
WebLogic 8.1 and Tomcat connection problem
I am using Tomcat 4.0.6 for my JSPs and WebLogic for my EJBs.
Everything worked fine under WebLogic 6.1 but I am trying
to upgrade to WebLogic 8.1 and it is not working.
I can also connect to WebLogic 8.1 from a standalone class
but not using Tomcat. What is wrong?
This is the basic code I am using to connect:
Hashtable ht = new Hashtable(4);
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,"t3://localhost:7009");
InitialContext ic = new InitialContext(ht);
Object obj = ic.lookup("NsbInfoHome");
NsbInfoHome home = ( NsbInfoHome) PortableRemoteObject.
narrow(obj, NsbInfoHome.class);
NsbInfo nsbInfo = home.create();
NsbMemberPrimaryInfo info = nsbInfo.getMemberPrimaryInfo(1);
And this is the error
java.lang.NullPointerException
at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGenerator.java:694)
at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:666)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:712)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:699)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:76)
at weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(WLInitialContextFactoryDelegate.java:486)
at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:449)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:345)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:672)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:250)
at javax.naming.InitialContext.init(InitialContext.java:226)
at javax.naming.InitialContext.<init>(InitialContext.java:202)
at org.apache.jsp.testWL2$jsp._jspService(testWL2$jsp.java:81)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
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:243)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
at java.lang.Thread.run(Thread.java:536)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed to
generate class for weblogic.jndi.internal.ServerNamingNode_WLStub ] -
with nested exception:
[java.lang.NullPointerException]
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:716)
at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:699)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:76)
at weblogic.jndi.WLInitialContextFactoryDelegate.newRootNamingNodeStub(WLInitialContextFactoryDelegate.java:486)
at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:449)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:345)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:308)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:234)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:672)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:250)
at javax.naming.InitialContext.init(InitialContext.java:226)
at javax.naming.InitialContext.<init>(InitialContext.java:202)
at org.apache.jsp.testWL2$jsp._jspService(testWL2$jsp.java:81)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473)
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:243)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
at java.lang.Thread.run(Thread.java:536)
Any ideas how to fix this?
Thanks,
DanHi,
I work under a sligthly different seeting like Dan used (Java Client instead of JSPs, but same context properties), but the problem is exactly the same: weblogic.rmi.internal.StubGenerator.getStubOnClient() results in a NullPointerException.
What does this method actually do? I provided the weblogic.jar in the client's runtime environment; is it possible that the method asks for something else on the client side that I have to provide (only guessing...)
PS: I found the error myself. Its the Eclipse 3.0 IDE that won't work together with the factory class of BEA for some obscure reason. Switching to another IDE solved the problem...
Message was edited by c_web at Dec 1, 2004 6:03 AM -
TOMCAT server problem at startup
Hello
I use apache-tomcat-4.1.37. When I start tomcat I get an long
error-output in catalina.out. Can anybody help me to fix this?
Sorry for this long error-posting!
Jan 13, 2006 12:18:54 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL
file:/srv/www/tomcat5/base/webapps/webdav
Jan 13, 2006 12:18:54 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jan 13, 2006 12:18:54 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Jan 13, 2006 12:18:54 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/21 config=/usr/share/tomcat5/conf/jk2.properties
Jan 13, 2006 12:18:55 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3422 ms
Jan 13, 2006 12:19:24 AM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /admin
Jan 13, 2006 12:19:25 AM org.apache.catalina.logger.LoggerBase stop
INFO: unregistering logger Catalina:type=Logger,path=/admin,host=localhost
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /webdav
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /servlets-examples
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /jsp-examples
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /balancer
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /tomcat-docs
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /umin
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /servlet
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path
Jan 13, 2006 12:19:25 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /manager
Jan 13, 2006 12:19:25 AM org.apache.catalina.logger.LoggerBase stop
INFO: unregistering logger Catalina:type=Logger,host=localhost
Jan 13, 2006 12:19:25 AM org.apache.catalina.logger.LoggerBase stop
INFO: unregistering logger Catalina:type=Logger
Jan 13, 2006 12:19:25 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Jan 13, 2006 12:19:28 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jan 13, 2006 12:19:28 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1249 ms
Jan 13, 2006 12:19:28 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jan 13, 2006 12:19:28 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0
Jan 13, 2006 12:19:28 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jan 13, 2006 12:19:28 AM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Jan 13, 2006 12:19:28 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL
file:/etc/tomcat5/base/Catalina/localhost/balancer.xml
Jan 13, 2006 12:19:29 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL
file:/etc/tomcat5/base/Catalina/localhost/admin.xml
Jan 13, 2006 12:19:30 AM org.apache.commons.digester.Digester error
SEVERE: Parse Error at line 1062 column 94: Element type "message-resources"
must be declared.
org.xml.sax.SAXParseException: Element type "message-resources" must be
declared.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1647)
at
org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:708)
at
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:670)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:329)
at
org.apache.webapp.admin.ApplicationServlet.init(ApplicationServlet.java:105)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1044)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:876)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4017)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at
org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:903)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:216)
at org.apache.commons.digester.Rule.end(Rule.java:230)
at org.apache.commons.digester.Digester.endElement(Digester.java:1130)
at
org.apache.catalina.util.CatalinaDigester.endElement(CatalinaDigester.java:76)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1666)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:488)
at
org.apache.catalina.core.StandardHost.install(StandardHost.java:863)
at
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:483)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:427)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:983)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at
org.apache.catalina.core.StandardService.start(StandardService.java:480)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
Jan 13, 2006 12:19:30 AM org.apache.commons.digester.Digester error
SEVERE: Parse Error at line 1064 column 17: The content of element type
"struts-config" must match
"(data-sources?,form-beans?,global-forwards?,action-mappings?)".
org.xml.sax.SAXParseException: The content of element type "struts-config"
must match "(data-sources?,form-beans?,global-forwards?,action-mappings?)".
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1647)
at
org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:708)
at
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:670)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:329)
at
org.apache.webapp.admin.ApplicationServlet.init(ApplicationServlet.java:105)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1044)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:876)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4017)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at
org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:903)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:216)
at org.apache.commons.digester.Rule.end(Rule.java:230)
at org.apache.commons.digester.Digester.endElement(Digester.java:1130)
at
org.apache.catalina.util.CatalinaDigester.endElement(CatalinaDigester.java:76)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1666)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:488)
at
org.apache.catalina.core.StandardHost.install(StandardHost.java:863)
at
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:483)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:427)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:983)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at
org.apache.catalina.core.StandardService.start(StandardService.java:480)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
Jan 13, 2006 12:19:31 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL
file:/etc/tomcat5/base/Catalina/localhost/manager.xml
Jan 13, 2006 12:19:31 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /umin from URL
file:/usr/share/tomcat5/webapps/umin
Jan 13, 2006 12:19:31 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /servlet from URL
file:/usr/share/tomcat5/webapps/servlet
Jan 13, 2006 12:19:31 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path from URL
file:/srv/www/tomcat5/base/webapps/ROOT
Jan 13, 2006 12:19:31 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /jsp-examples from URL
file:/srv/www/tomcat5/base/webapps/jsp-examples
Jan 13, 2006 12:19:31 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /servlets-examples from URL
file:/srv/www/tomcat5/base/webapps/servlets-examples
Jan 13, 2006 12:19:31 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /tomcat-docs from URL
file:/srv/www/tomcat5/base/webapps/tomcat-docs
Jan 13, 2006 12:19:31 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Installing web application at context path /webdav from URL
file:/srv/www/tomcat5/base/webapps/webdav
Jan 13, 2006 12:19:31 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jan 13, 2006 12:19:32 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Jan 13, 2006 12:19:32 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=1/21 config=/usr/share/tomcat5/conf/jk2.properties
Jan 13, 2006 12:19:32 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3422 ms
Environment variables are all set ok.
I cannot know why i got these many errors.
i have into the WEB-INF folder the file build.xml, i typed asant to compile the xml file, and build was succesful
anyway, i;m going to do what is this: http://maestric.com/en/doc/java/spring/mvc
but when accessing http://localhost:8080/springmvc/list_cars.html
i got an error, it is not displayed what is in that example
help me please
Thankswell, no, i downloaded the apache-tomcat version 4, i'm not mixing versions, but i had apache tomcat 6, probably the log is from there. today i tried again starting that application, here is the log:
2008-09-07 00:10:53 HostConfig[localhost]: Deploying configuration descriptor admin.xml
2008-09-07 00:10:55 HostConfig[localhost]: Deploying configuration descriptor manager.xml
2008-09-07 00:10:55 WebappLoader[manager]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\manager
2008-09-07 00:10:55 ContextConfig[manager]: Configured an authenticator for method BASIC
2008-09-07 00:10:55 StandardManager[manager]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:10:55 StandardManager[manager]: Seeding of random number generator has been completed
2008-09-07 00:10:55 StandardWrapper[manager:default]: Loading container servlet default
2008-09-07 00:10:55 StandardWrapper[manager:invoker]: Loading container servlet invoker
2008-09-07 00:10:55 HostConfig[localhost]: Deploying web application directory ROOT
2008-09-07 00:10:55 StandardHost[localhost]: Installing web application at context path from URL file:C:\apache-tomcat-4.1.37\webapps\ROOT
2008-09-07 00:10:55 WebappLoader[]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\_
2008-09-07 00:10:55 StandardManager[]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:10:55 StandardManager[]: Seeding of random number generator has been completed
2008-09-07 00:10:55 StandardWrapper[:default]: Loading container servlet default
2008-09-07 00:10:55 StandardWrapper[:invoker]: Loading container servlet invoker
2008-09-07 00:10:55 HostConfig[localhost]: Deploying web application directory springmvc
2008-09-07 00:10:55 StandardHost[localhost]: Installing web application at context path /springmvc from URL file:C:\apache-tomcat-4.1.37\webapps\springmvc
2008-09-07 00:10:55 WebappLoader[springmvc]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\springmvc
2008-09-07 00:10:55 WebappLoader[springmvc]: Deploy class files /WEB-INF/classes to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\classes
2008-09-07 00:10:55 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/commons-logging.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\commons-logging.jar
2008-09-07 00:10:55 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/jstl.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\jstl.jar
2008-09-07 00:10:55 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/servlet-api.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\servlet-api.jar
2008-09-07 00:10:55 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/spring-webmvc.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\spring-webmvc.jar
2008-09-07 00:10:55 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/spring.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\spring.jar
2008-09-07 00:10:55 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/standard.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\standard.jar
2008-09-07 00:10:56 StandardManager[springmvc]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:10:56 StandardManager[springmvc]: Seeding of random number generator has been completed
2008-09-07 00:10:56 StandardWrapper[springmvc:default]: Loading container servlet default
2008-09-07 00:10:56 Initializing Spring FrameworkServlet 'springmvc'
2008-09-07 00:10:57 StandardContext[springmvc]: Servlet /springmvc threw load() exception
javax.servlet.ServletException: Servlet.init() for servlet springmvc threw exception
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:908)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:777)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:760)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:538)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:265)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:731)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:379)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:808)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:335)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1156)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
at org.apache.catalina.startup.Catalina.start(Catalina.java:484)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:371)
at org.apache.catalina.startup.Catalina.process(Catalina.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
----- Root Cause -----
org.springframework.beans.factory.CannotLoadBeanClassException: Error loading class [springmvc.web.HelloWorldController] for bean with name '/hello_world.html' defined in ServletContext resource [WEB-INF/springmvc-servlet.xml]: problem with class file or dependent class; nested exception is java.lang.UnsupportedClassVersionError: springmvc/web/HelloWorldController (Unsupported major.minor version 49.0)
at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1163)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:581)
at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1364)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:406)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:735)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:332)
at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:266)
at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:236)
at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:126)
at javax.servlet.GenericServlet.init(GenericServlet.java:213)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:880)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:777)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:760)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:538)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:265)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:731)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:379)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:808)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:335)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1156)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
at org.apache.catalina.startup.Catalina.start(Catalina.java:484)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:371)
at org.apache.catalina.startup.Catalina.process(Catalina.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
Caused by: java.lang.UnsupportedClassVersionError: springmvc/web/HelloWorldController (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:123)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1787)
at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1049)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1507)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386)
at org.springframework.util.ClassUtils.forName(ClassUtils.java:230)
at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:371)
at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1157)
... 38 more
2008-09-07 00:10:57 StandardWrapper[springmvc:invoker]: Loading container servlet invoker
2008-09-07 00:10:57 HostConfig[localhost]: Deploying web application directory tomcat-docs
2008-09-07 00:10:57 StandardHost[localhost]: Installing web application at context path /tomcat-docs from URL file:C:\apache-tomcat-4.1.37\webapps\tomcat-docs
2008-09-07 00:10:57 WebappLoader[tomcat-docs]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\tomcat-docs
2008-09-07 00:10:57 StandardManager[tomcat-docs]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:10:57 StandardManager[tomcat-docs]: Seeding of random number generator has been completed
2008-09-07 00:10:57 StandardWrapper[tomcat-docs:default]: Loading container servlet default
2008-09-07 00:10:57 StandardWrapper[tomcat-docs:invoker]: Loading container servlet invoker
2008-09-07 00:10:57 HostConfig[localhost]: Deploying web application directory webdav
2008-09-07 00:10:57 StandardHost[localhost]: Installing web application at context path /webdav from URL file:C:\apache-tomcat-4.1.37\webapps\webdav
2008-09-07 00:10:57 WebappLoader[webdav]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\webdav
2008-09-07 00:10:57 StandardManager[webdav]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:10:57 StandardManager[webdav]: Seeding of random number generator has been completed
2008-09-07 00:10:57 StandardWrapper[webdav:default]: Loading container servlet default
2008-09-07 00:10:57 StandardWrapper[webdav:invoker]: Loading container servlet invoker
2008-09-07 00:16:11 StandardHost[localhost]: Removing web application at context path /admin
2008-09-07 00:16:11 StandardHost[localhost]: Removing web application at context path /webdav
2008-09-07 00:16:11 StandardHost[localhost]: Removing web application at context path /examples
2008-09-07 00:16:11 StandardHost[localhost]: Removing web application at context path /springmvc
2008-09-07 00:16:11 StandardHost[localhost]: Removing web application at context path /tomcat-docs
2008-09-07 00:16:11 StandardHost[localhost]: Removing web application at context path
2008-09-07 00:16:11 StandardHost[localhost]: Removing web application at context path /manager
2008-09-07 00:16:20 HostConfig[localhost]: Deploying configuration descriptor admin.xml
2008-09-07 00:16:21 HostConfig[localhost]: Deploying configuration descriptor manager.xml
2008-09-07 00:16:21 WebappLoader[manager]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\manager
2008-09-07 00:16:21 ContextConfig[manager]: Configured an authenticator for method BASIC
2008-09-07 00:16:21 StandardManager[manager]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:16:21 StandardManager[manager]: Seeding of random number generator has been completed
2008-09-07 00:16:21 StandardWrapper[manager:default]: Loading container servlet default
2008-09-07 00:16:21 StandardWrapper[manager:invoker]: Loading container servlet invoker
2008-09-07 00:16:21 HostConfig[localhost]: Deploying web application directory ROOT
2008-09-07 00:16:21 StandardHost[localhost]: Installing web application at context path from URL file:C:\apache-tomcat-4.1.37\webapps\ROOT
2008-09-07 00:16:21 WebappLoader[]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\_
2008-09-07 00:16:21 StandardManager[]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:16:21 StandardManager[]: Seeding of random number generator has been completed
2008-09-07 00:16:21 StandardWrapper[:default]: Loading container servlet default
2008-09-07 00:16:21 StandardWrapper[:invoker]: Loading container servlet invoker
2008-09-07 00:16:21 HostConfig[localhost]: Deploying web application directory tomcat-docs
2008-09-07 00:16:21 StandardHost[localhost]: Installing web application at context path /tomcat-docs from URL file:C:\apache-tomcat-4.1.37\webapps\tomcat-docs
2008-09-07 00:16:21 WebappLoader[tomcat-docs]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\tomcat-docs
2008-09-07 00:16:21 StandardManager[tomcat-docs]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:16:21 StandardManager[tomcat-docs]: Seeding of random number generator has been completed
2008-09-07 00:16:21 StandardWrapper[tomcat-docs:default]: Loading container servlet default
2008-09-07 00:16:21 StandardWrapper[tomcat-docs:invoker]: Loading container servlet invoker
2008-09-07 00:16:22 HostConfig[localhost]: Deploying web application directory webdav
2008-09-07 00:16:22 StandardHost[localhost]: Installing web application at context path /webdav from URL file:C:\apache-tomcat-4.1.37\webapps\webdav
2008-09-07 00:16:22 WebappLoader[webdav]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\webdav
2008-09-07 00:16:22 StandardManager[webdav]: Seeding random number generator class java.security.SecureRandom
2008-09-07 00:16:22 StandardManager[webdav]: Seeding of random number generator has been completed
2008-09-07 00:16:22 StandardWrapper[webdav:default]: Loading container servlet default
2008-09-07 00:16:22 StandardWrapper[webdav:invoker]: Loading container servlet invoker
2008-09-07 00:16:43 StandardHost[localhost]: Removing web application at context path /admin
2008-09-07 00:16:43 StandardHost[localhost]: Removing web application at context path /webdav
2008-09-07 00:16:43 StandardHost[localhost]: Removing web application at context path /examples
2008-09-07 00:16:43 StandardHost[localhost]: Removing web application at context path /tomcat-docs
2008-09-07 00:16:43 StandardHost[localhost]: Removing web application at context path
2008-09-07 00:16:43 StandardHost[localhost]: Removing web application at context path /manager
2008-09-07 09:45:05 HostConfig[localhost]: Deploying configuration descriptor admin.xml
2008-09-07 09:45:07 HostConfig[localhost]: Deploying configuration descriptor manager.xml
2008-09-07 09:45:07 WebappLoader[manager]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\manager
2008-09-07 09:45:07 ContextConfig[manager]: Configured an authenticator for method BASIC
2008-09-07 09:45:07 StandardManager[manager]: Seeding random number generator class java.security.SecureRandom
2008-09-07 09:45:07 StandardManager[manager]: Seeding of random number generator has been completed
2008-09-07 09:45:07 StandardWrapper[manager:default]: Loading container servlet default
2008-09-07 09:45:07 StandardWrapper[manager:invoker]: Loading container servlet invoker
2008-09-07 09:45:07 HostConfig[localhost]: Deploying web application directory ROOT
2008-09-07 09:45:07 StandardHost[localhost]: Installing web application at context path from URL file:C:\apache-tomcat-4.1.37\webapps\ROOT
2008-09-07 09:45:07 WebappLoader[]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\_
2008-09-07 09:45:07 StandardManager[]: Seeding random number generator class java.security.SecureRandom
2008-09-07 09:45:07 StandardManager[]: Seeding of random number generator has been completed
2008-09-07 09:45:07 StandardWrapper[:default]: Loading container servlet default
2008-09-07 09:45:07 StandardWrapper[:invoker]: Loading container servlet invoker
2008-09-07 09:45:07 HostConfig[localhost]: Deploying web application directory tomcat-docs
2008-09-07 09:45:07 StandardHost[localhost]: Installing web application at context path /tomcat-docs from URL file:C:\apache-tomcat-4.1.37\webapps\tomcat-docs
2008-09-07 09:45:07 WebappLoader[tomcat-docs]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\tomcat-docs
2008-09-07 09:45:07 StandardManager[tomcat-docs]: Seeding random number generator class java.security.SecureRandom
2008-09-07 09:45:07 StandardManager[tomcat-docs]: Seeding of random number generator has been completed
2008-09-07 09:45:07 StandardWrapper[tomcat-docs:default]: Loading container servlet default
2008-09-07 09:45:07 StandardWrapper[tomcat-docs:invoker]: Loading container servlet invoker
2008-09-07 09:45:07 HostConfig[localhost]: Deploying web application directory webdav
2008-09-07 09:45:07 StandardHost[localhost]: Installing web application at context path /webdav from URL file:C:\apache-tomcat-4.1.37\webapps\webdav
2008-09-07 09:45:07 WebappLoader[webdav]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\webdav
2008-09-07 09:45:07 StandardManager[webdav]: Seeding random number generator class java.security.SecureRandom
2008-09-07 09:45:07 StandardManager[webdav]: Seeding of random number generator has been completed
2008-09-07 09:45:07 StandardWrapper[webdav:default]: Loading container servlet default
2008-09-07 09:45:07 StandardWrapper[webdav:invoker]: Loading container servlet invoker
2008-09-07 09:53:36 HostConfig[localhost]: Deploying web application directory springmvc
2008-09-07 09:53:36 StandardHost[localhost]: Installing web application at context path /springmvc from URL file:C:\apache-tomcat-4.1.37\webapps\springmvc
2008-09-07 09:53:36 WebappLoader[springmvc]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\springmvc
2008-09-07 09:53:36 WebappLoader[springmvc]: Deploy class files /WEB-INF/classes to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\classes
2008-09-07 09:53:36 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/commons-logging.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\commons-logging.jar
2008-09-07 09:53:36 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/jstl.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\jstl.jar
2008-09-07 09:53:36 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/servlet-api.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\servlet-api.jar
2008-09-07 09:53:36 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/spring-webmvc.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\spring-webmvc.jar
2008-09-07 09:53:36 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/spring.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\spring.jar
2008-09-07 09:53:36 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/standard.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\standard.jar
2008-09-07 09:53:37 StandardManager[springmvc]: Seeding random number generator class java.security.SecureRandom
2008-09-07 09:53:37 StandardManager[springmvc]: Seeding of random number generator has been completed
2008-09-07 09:53:37 StandardWrapper[springmvc:default]: Loading container servlet default
2008-09-07 09:53:37 Initializing Spring FrameworkServlet 'springmvc'
2008-09-07 09:53:37 StandardContext[springmvc]: Servlet /springmvc threw load() exception
javax.servlet.ServletException: Servlet.init() for servlet springmvc threw exception
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:908)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:777)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:760)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:538)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:265)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:731)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:379)
at org.apache.catalina.startup.HostConfig.run(HostConfig.java:941)
at java.lang.Thread.run(Thread.java:534)
----- Root Cause -----
org.springframework.beans.factory.CannotLoadBeanClassException: Error loading class [springmvc.web.HelloWorldController] for bean with name '/hello_world.html' defined in ServletContext resource [WEB-INF/springmvc-servlet.xml]: problem with class file or dependent class; nested exception is java.lang.UnsupportedClassVersionError: springmvc/web/HelloWorldController (Unsupported major.minor version 49.0)
at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1163)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.predictBeanType(AbstractAutowireCapableBeanFactory.java:581)
at org.springframework.beans.factory.support.AbstractBeanFactory.isFactoryBean(AbstractBeanFactory.java:1364)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:406)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:735)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369)
at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:332)
at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:266)
at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:236)
at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:126)
at javax.servlet.GenericServlet.init(GenericServlet.java:213)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:880)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:777)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:760)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:538)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:265)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:731)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:379)
at org.apache.catalina.startup.HostConfig.run(HostConfig.java:941)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.UnsupportedClassVersionError: springmvc/web/HelloWorldController (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:123)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1787)
at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1049)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1507)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386)
at org.springframework.util.ClassUtils.forName(ClassUtils.java:230)
at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:371)
at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1157)
... 23 more
2008-09-07 09:53:37 StandardWrapper[springmvc:invoker]: Loading container servlet invoker
2008-09-07 09:53:37 StandardHost[localhost]: Removing web application at context path /admin
2008-09-07 09:53:37 StandardHost[localhost]: Removing web application at context path /webdav
2008-09-07 09:53:37 StandardHost[localhost]: Removing web application at context path /examples
2008-09-07 09:53:37 StandardHost[localhost]: Removing web application at context path /springmvc
2008-09-07 09:53:37 StandardHost[localhost]: Removing web application at context path /tomcat-docs
2008-09-07 09:53:37 StandardHost[localhost]: Removing web application at context path
2008-09-07 09:53:37 StandardHost[localhost]: Removing web application at context path /manager
2008-09-07 09:53:44 HostConfig[localhost]: Deploying configuration descriptor admin.xml
2008-09-07 09:53:46 HostConfig[localhost]: Deploying configuration descriptor manager.xml
2008-09-07 09:53:46 WebappLoader[manager]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\manager
2008-09-07 09:53:46 ContextConfig[manager]: Configured an authenticator for method BASIC
2008-09-07 09:53:46 StandardManager[manager]: Seeding random number generator class java.security.SecureRandom
2008-09-07 09:53:46 StandardManager[manager]: Seeding of random number generator has been completed
2008-09-07 09:53:46 StandardWrapper[manager:default]: Loading container servlet default
2008-09-07 09:53:46 StandardWrapper[manager:invoker]: Loading container servlet invoker
2008-09-07 09:53:46 HostConfig[localhost]: Deploying web application directory ROOT
2008-09-07 09:53:46 StandardHost[localhost]: Installing web application at context path from URL file:C:\apache-tomcat-4.1.37\webapps\ROOT
2008-09-07 09:53:46 WebappLoader[]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\_
2008-09-07 09:53:46 StandardManager[]: Seeding random number generator class java.security.SecureRandom
2008-09-07 09:53:46 StandardManager[]: Seeding of random number generator has been completed
2008-09-07 09:53:46 StandardWrapper[:default]: Loading container servlet default
2008-09-07 09:53:46 StandardWrapper[:invoker]: Loading container servlet invoker
2008-09-07 09:53:46 HostConfig[localhost]: Deploying web application directory springmvc
2008-09-07 09:53:46 StandardHost[localhost]: Installing web application at context path /springmvc from URL file:C:\apache-tomcat-4.1.37\webapps\springmvc
2008-09-07 09:53:46 WebappLoader[springmvc]: Deploying class repositories to work directory C:\apache-tomcat-4.1.37\work\Standalone\localhost\springmvc
2008-09-07 09:53:46 WebappLoader[springmvc]: Deploy class files /WEB-INF/classes to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\classes
2008-09-07 09:53:46 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/commons-logging.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\commons-logging.jar
2008-09-07 09:53:46 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/jstl.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\jstl.jar
2008-09-07 09:53:46 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/servlet-api.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\servlet-api.jar
2008-09-07 09:53:46 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/spring-webmvc.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\spring-webmvc.jar
2008-09-07 09:53:46 WebappLoader[springmvc]: Deploy JAR /WEB-INF/lib/spring.jar to C:\apache-tomcat-4.1.37\webapps\springmvc\WEB-INF\lib\spring.jar
2008-09-07 09:53:46 WebappL -
Tomcat Context Initialized Event
Hi guys, I am having the following error while using a JNI code..
- Exception sending context initialized event to listener instance of class com.broadmediatechnology.licence.LicenceManagerContextListener
java.lang.UnsatisfiedLinkError: init
at com.broadmediatechnology.getmetvnative.NativeManager.init(Native Method)
at com.broadmediatechnology.getmetv.server.GetMeTVManager.init(GetMeTVManager.java:38)
at com.broadmediatechnology.getmetv.server.licence.LicenceManagerContextListener.contextInitialized(LicenceManagerContextListener.java:18)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3669)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4104)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:894)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:857)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:475)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1102)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)What I am trying to do is to load a C library on Tomcat startup event.. Here is my code snippet...
public final class LicenceManagerContextListener
implements ServletContextListener {
public void contextInitialized(ServletContextEvent event) {
SystemManager.init();
}And my init method is a native method in SYstem Manager class... It doesnt look like a Class loading problem..previously i was having library not found error, then I put these lines in Tomcat Start up script..
export CLASSPATH=$CLASSPATH:/etc/getmetv
export LD_LIBRARY_PATH=/etc/getmetv
export JAVA_OPTS=-Djava.library.path=/etc/getmetvCan anyone tell me what exactly is going wrong?
Thanks
Message was edited by:
mraheel
Message was edited by:
mraheelFor more information..my .SO file is placed in /etc/getmetv
The name of SO file is libgetmetv and i am loading the library as
static {
try {
System.loadLibrary("getmetv");
catch (Exception e) {
e.printStackTrace();
} -
Sysdeo/tomcat deployment problems in 10.1
I recently had to reinstall workshop and have upgraded to 10.1 at the same time.
I have a problem in that after starting the server, one of two things happen:
1) often the first start of the session works fine but subsequent starts do not complete - it seems to be getting stuck in the "create sysdeo" files. If I cancel this then the deploy continues, albeit that the app fails as it cannot find external libraries.
2) sometimes on starting a new session, I have noticed that the app rebuilds with errors. This seems to be because it "looses" any defined server runtimes so everything has to be redefined.
Note that this workspace was "converted" from an earlier version.
Has anyone else had similar problems?
Thanks in advance
Ianok well I reinstalled workshop with no plugins.
It asked to upgrade my existing projects and then once done I could successfully startup the server.
sysdeo did its job and the server process worked.
Then the ultimate test - restart the server.
Once again the server failed to restart. I left it for several minutes.
Looking at the outstanding tasks, it states them as
Starting Server Tomcat v5.5 @localhost
Building workspace (Waiting)
OK
Create Sysdeo DevLoader Files (Waiting)Again the system just hangs. In fact since there are no plugins, it now hangs first time in a session rather than second time.
At this point, there are no errors in the log files other than missing plugins (as I said in my last post I thought I would not install the plugins in case they were an issue.
In the wstudio log files the following error occurs every time
24-Jul-2007 16:51:24 com.m7.wide.eclipse.jstudio.Plugin activate
INFO: max mem: 748
24-Jul-2007 16:51:39 com.m7.wide.eclipse.jstudio.Plugin$3 actionPerformed
SEVERE: Plugin.startup
java.lang.NoSuchMethodException: java.lang.Object.getModalShell()
at java.lang.Class.getDeclaredMethod(Class.java:1909)
at com.m7.util.ReflectionUtil.findDeclaredMethod(Unknown Source)
at com.m7.util.ReflectionUtil.invoke(Unknown Source)
at com.m7.wide.eclipse.jstudio.Plugin$3.actionPerformed(Unknown Source)
at javax.swing.Timer.fireActionPerformed(Timer.java:271)
at javax.swing.Timer$DoPostEvent.run(Timer.java:201)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at com.m7.wide.eclipse.jstudio.Plugin$EventBridgeThread.flushQueue(Unknown Source)
at com.m7.wide.eclipse.jstudio.Plugin$EventBridgeThread$1.run(Unknown Source)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3157)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2859)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:339)
at org.eclipse.core.launcher.Main.basicRun(Main.java:283)
at org.eclipse.core.launcher.Main.run(Main.java:984)
at org.eclipse.core.launcher.Main.eclipse_main(Main.java:959)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.m7.installer.util.NitroxMain$1.run(NitroxMain.java:36)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:199)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)When I abort the sysdeo loader finally, the following occurs:
!ENTRY org.eclipse.core.jobs 4 2 2007-07-24 16:39:11.734
!MESSAGE An internal error occurred during: "Starting server - Tomcat v5.5 @ localhost".
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: 0
at com.bea.wstudio.debugger.WorkshopTomcatLaunchConfigurationDelegate.launch(WorkshopTomcatLaunchConfigurationDelegate.java:159)
at com.bea.wstudio.debugger.WebAppServerLaunchConfigurationDelegate.launch(WebAppServerLaunchConfigurationDelegate.java:74)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:639)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:565)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:558)
at org.eclipse.wst.server.core.internal.Server.start(Server.java:1239)
at org.eclipse.wst.server.core.internal.Server.synchronousStart(Server.java:1624)
at org.eclipse.wst.server.core.internal.StartServerJob.run(StartServerJob.java:34)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)This is recorded in the .log file and also is sent to bea as an error suggesting terminating the session.
I have also noticed that it has created a devloader_context.xml in META-INF. Though this was initially set to something, the starting of the session has reset it to an empty file simply containing <Context></Context>. If it is using this file I cannot see that Tomcat would be too pleased!
Don't know if any of this helps
Ian -
Tomcat restarting problem -plz help
hi,
Can anybody tell me why do i have to restart the server everytime i change my servlet.
Kindly help
Thanks and regards
nehaHi Neha,
This documentation is from JavaWebServicesDeveloperPack(Evaluation version)
You will get more details if you can download this pack/tutorial from Java site & install it.
http://java.sun.com/webservices/webservicespack.html
Hope this will help you.
Ajay.
Manager App HOW-TO
Introduction
In many production environments, it is very useful to have the capability to deploy a new web application, or undeploy an existing one, without having to shut down and restart the entire container. In addition, you can request an existing application to reload itself, even if you have not declared it to be reloadable in the Tomcat 4 server configuration file.
To support these capabilities, Tomcat 4 includes a web application (installed by default on context path /manager) that supports the following functions:
Deploy a new web application, on a specified context path, from the uploaded contents of a WAR file.
Install a new web application, which can be anywhere on the server's disks.
List the currently deployed web applications, as well as the sessions that are currently active for those web apps.
Reload an existing web application, to reflect changes in the contents of /WEB-INF/classes or /WEB-INF/lib.
Remove an installed web application.
Start a stopped application (thus making it available again).
Stop an existing application (so that it becomes unavailable), but do not undeploy it.
Undeploy a deployed web application and delete its document base directory.
Since Manager is itself a web application, it interacts with you using standard HTTP requests and responses. However, it's "user interface" is minimal, because it is intended to be accessed from scripts set up by the system administrator. For this reason, commands are given as part of the request URI, and responses are in the form of simple text that can be easily parsed and processed.
Future versions of Tomcat 4 will include administrative functionality that is presented in (at least) the following forms:
As web services, so that Tomcat administration can be easily integrated into remote and/or non-Java mnagement environments.
As a web application with a nice user interface (built on top of the web services processing layer) for easy Tomcat administration via a web browser.
In addition to executing Manager commands directly via HTTP, Tomcat 4 includes a convenient set of task definitions for the Ant (version 1.4 or later) build tool. See Executing Manager Commands With Ant for more information.
Configuring Manager Application Access
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 4, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 4 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
It would be quite unsafe to ship Tomcat with default settings that allowed anyone on the Internet to execute the Manager application on your server. Therefore, the Manager application is shipped with the requirement that anyone who attempts to use it must authenticate themselves, using a username and password that have the role manager associated with them. Further, there is no username in the default users file ($CATALINA_HOME/conf/tomcat-users.xml) that is assigned this role. Therefore, access to the Manager application is completely disabled by default.
To enable access to the Manager web application, you must either create a new username/password combination and associate the role name manager with it, or add the manager role to some existing username/password combination. Exactly where this is done depends on which Realm implementation you are using:
MemoryRealm - If you have not customized your $CATALINA_HOME/conf/server.xml to select a different one, Tomcat 4 defaults to an XML-format file stored at $CATALINA_HOME/conf/tomcat-users.xml, which can be edited with any text editor. This file contains an XML <user> for each individual user, which might look something like this:
<user name="craigmcc" password="secret" roles="standard,manager" />
which defines the username and password used by this individual to log on, and the role names he or she is associated with. You can add the manager role to the comma-delimited roles attriute for one or more existing users, and/or create new users with that assigned role.
JDBCRealm - Your user and role information is stored in a database accessed via JDBC. Add the manager role to one or more existing users, and/or create one or more new users with this role assigned, following the standard procedures for your environment.
JNDIRealm - Your user and role information is stored in a directory server accessed via LDAP. Add the manager role to one or more existing users, and/or create one or more new users with this role assigned, following the standard procedures for your environment.
The first time you attempt to issue one of the Manager commands described in the next section, you will be challenged to log on using BASIC authentication. The username and password you enter do not matter, as long as they identify a valid user in the users database who possesses the role manager.
Supported Manager Commands
All commands that the Manager application knows how to process are specified in a single request URI like this:
http://{host}:{port}/manager/{command}?{parameters}
where {host} and {port} represent the hostname and port number on which Tomcat is running, {command} represents the Manager command you wish to execute, and {parameters} represents the query parameters that are specific to that command. In the illustrations below, customize the host and port appropriately for your installation.
Most commands accept one or more of the following query parameters:
path - The context path (including the leading slash) of the web application you are dealing with. To select the ROOT web application, specify a zero-length string. NOTE - It is not possible to perform administrative commands on the Manager application itself.
war - URL of a web application archive (WAR) file, or pathname of a directory, that contains the web application. You can use URLs in any of the following formats:
file:/absolute/path/to/a/directory - The absolute path of a directory that contains the unpacked version of a web application. This directory will be attached to the context path you specify without any changes.
file:/absolute/path/to/a/webapp.war - The absolute path of a web application archive (WAR) file. This is valid only for the /deploy command, and is the only acceptable format to that command.
jar:file:/absolute/path/to/a/warfile.war!/ - The URL to a local web application archive (WAR) file. You can use any syntax that is valid for the JarURLConnection class for reference to an entire JAR file.
jar:http://hostname:port/path/to/a/warfile.war!/ - You can also deploy web applications from a remote JAR file. You can use any syntax that is valid for the JarURLConnection class for reference to an entire JAR file.
Each command will return a response in text/plain format (i.e. plain ASCII with no HTML markup), making it easy for both humans and programs to read). The first line of the response wil begin with either OK or FAIL, indicating whether the requested command was successful or not. In the case of failure, the rest of the first line will contain a description of the problem that was encountered. Some commands include additional lines of information as described below.
Internationalization Note - The Manager application looks up its message strings in resource bundles, so it is possible that the strings have been translated for your platform. The examples below show the English version of the messages.
Deploy A New Application
http://localhost:8080/manager/deploy?path=/foo
Upload the web application archive (WAR) file that is specified as the request data in this HTTP PUT request, install it into the appBase directory of our corresponding virtual host, and start it on the context path specified by the path request parameter. The application can later be undeployed (and the corresponding application directory removed) by use of the /undeploy.
NOTE - Since this command requires an HTTP PUT request, it is usable only from tools (such as the custom Ant tasks described below). To install a new web application without copying, consider the /install command described below. This command is the logical opposite of the /undeploy command.
If installation and startup is successful, you will receive a response like this:
OK - Deployed application at context path /foo
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Application already exists at path /foo
The context paths for all currently running web applications must be unique. Therefore, you must either remove or undeploy the existing web application using this context path, or choose a different context path for the new one.
Encountered exception
An exception was encountered trying to start the new web application. Check the Tomcat 4 logs for the details, but likely explanations include problems parsing your /WEB-INF/web.xml file, or missing classes encountered when initializing application event listeners and filters.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context path was specified
The path parameter is required.
Install A New Application
http://localhost:8080/manager/install?path=/foo&war=file:/path/to/foo
http://localhost:8080/manager/install?path=/bar&war=jar:file:/path/to/bar.war!/
Install and start a new web application, attached to the specified context path (which must not be in use by any other web application). The war parameter specifies a URL (including the file: scheme) for either a directory or a web application archive (WAR) file. The supported syntax for a URL referring to a WAR file is described on the Javadocs page for the java.net.JarURLConnection class. Use only URLs that refer to the entire WAR file. This command is the logical opposite of the /remove command.
If installation and startup is successful, you will receive a response like this:
OK - Installed application at context path /foo
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Application already exists at path /foo
The context paths for all currently running web applications must be unique. Therefore, you must either remove or undeploy the existing web application using this context path, or choose a different context path for the new one.
Document base does not exist or is not a readable directory
The URL specified by the war parameter must identify a directory on this server that contains the "unpacked" version of a web application, or the absolute URL of a web application archive (WAR) file that contains this application. Correct the value specified by the war parameter.
Encountered exception
An exception was encountered trying to start the new web application. Check the Tomcat 4 logs for the details, but likely explanations include problems parsing your /WEB-INF/web.xml file, or missing classes encountered when initializing application event listeners and filters.
Invalid application URL was specified
The URL for the directory or web application that you specified was not valid. Such URLs must start with file:, and URLs for a WAR file must end in ".war".
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context path was specified
The path parameter is required.
List Currently Deployed and Installed Applications
http://localhost:8080/manager/list
List the context paths, current status (running or stopped), and number of active sessions for all currently deployed and installed web applications. A typical response immediately after starting Tomcat might look like this:
OK - Listed applications for virtual host localhost
/webdav:running:0
/examples:running:0
/manager:running:0
/:running:0
Reload An Existing Application
http://localhost:8080/manager/reload?path=/examples
Signal an existing application to shut itself down and reload. This can be useful when you've recompiled classes on an application that is not configured with the reloadable="true" attribute in its <Context> entry in $CATALINA_HOME/conf/server.xml, or when you've made other changes (such as to conf/web.xml) that are not automatically recognized by Tomcat.
If this command succeeds, you will see a response like this:
OK - Reloaded application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to restart the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Reload note supported on WAR deployed at path /foo
Currently, application reloading (to pick up changes to the classes or web.xml file) is not supported when a web application is installed directly from a WAR file. It only works when the web application is installed from an unpacked directory. If you are using a WAR file, you should remove and then install the application again to pick up your changes.
Remove an Existing Application
http://localhost:8080/manager/remove?path=/examples
Signal an existing application to gracefully shut itself down, and then remove it from Tomcat (which also makes this context path available for reuse later). This command is the logical opposite of the /install command.
If this command succeeds, you will see a response like this:
OK - Removed application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to remove the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Session Statistics
http://localhost:8080/manager/sessions?path=/examples
Display the default session timeout for a web application, and the number of currently active sessions that fall within ten-minute ranges of their actual timeout times. For example, after restarting Tomcat and then executing one of the JSP samples in the /examples web app, you might get something like this:
OK - Session information for application at context path /examples
Default maximum session inactive interval 30 minutes
30 - <40 minutes:1 sessions
Start an Existing Application
http://localhost:8080/manager/start?path=/examples
Signal a stopped application to restart, and make itself available again. Stopping and starting is useful, for example, if the database required by your application becomes temporarily unavailable. It is usually better to stop the web application that relies on this database, rather than letting users continuously encounter database exceptions.
If this command succeeds, you will see a response like this:
OK - Started application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to start the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Stop an Existing Application
http://localhost:8080/manager/stop?path=/examples
Signal an existing application to make itself unavailable, but leave it deployed or installed. Any request that comes in while an application is stopped will see an HTTP error 404, and this application will show as "stopped" on a list applications command.
If this command succeeds, you will see a response like this:
OK - Stopped application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to stop the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Undeploy an Existing Application
http://localhost:8080/manager/undeploy?path=/examples
WARNING - This command will delete the contents of the web application directory if it exists within the appBase directory (typically "webapps") for this virtual host . If you simply want to take an application out of service, you should use the /remove command instead.
Signal an existing application to gracefully shut itself down, and remove it from Tomcat (which also makes this context path available for reuse later). In addition, the document root directory is removed, if it exists in the appBase directory (typically "webapps") for this virtual host. This command is the logical opposite of the /deploy command.
If this command succeeds, you will see a response like this:
OK - Undeployed application at context path /examples
Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
Encountered exception
An exception was encountered trying to undeploy the web application. Check the Tomcat 4 logs for the details.
Invalid context path was specified
The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
No context exists for path /foo
There is no deployed or installed application on the context path that you specified.
No context path was specified
The path parameter is required.
Executing Manager Commands With Ant
In addition to the ability to execute Manager commands via HTTP requests, as documented above, Tomcat 4 includes a convenient set of Task definitions for the Ant (version 1.4 or later) build tool. In order to use these commands, you must perform the following setup operations:
Download the binary distribution of Ant from http://jakarta.apache.org/ant. You must use version 1.4 or later.
Install the Ant distribution in a convenient directory (called ANT_HOME in the remainder of these instructions).
Copy the file server/lib/catalina-ant.jar from your Tomcat 4 installation into Ant's library directory ($ANT_HOME/lib).
Add the $ANT_HOME/bin directory to your PATH environment variable.
Configure at least one username/password combination in your Tomcat user database that includes the manager role.
To use custom tasks within Ant, you must declare them first with a <taskdef> element. Therefore, your build.xml file might look something like this:
<project name="My Application" default="compile" basedir=".">
<-- Configure the directory into which the web application is built -->
<property name="build" value="${basedir}/build"/>
<-- Configure the context path for this application -->
<property name="path" value="/myapp"/>
<-- Configure properties to access the Manager application -->
<property name="url" value="http://localhost:8080/manager"/>
<property name="username" value="myusername"/>
<property name="password" value="mypassword"/>
<-- Configure the custom Ant tasks for the Manager application -->
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/>
<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<taskdef name="list" classname="org.apache.catalina.ant.ListTask"/>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
<taskdef name="start" classname="org.apache.catalina.ant.StartTask"/>
<taskdef name="stop" classname="org.apache.catalina.ant.StopTask"/>
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask"/>
<-- Executable Targets -->
<target name="compile" description="Compile web application">
... construct web application in ${build} subdirectory ...
</target>
<target name="install" description="Install web application"
depends="compile">
<install url="${url}" username="${username}" password="${password}"
path="${path}" war="file://${build}"/>
</target>
<target name="reload" description="Reload web application"
depends="compile">
<reload url="${url}" username="${username}" password="${password}"
path="${path}"/>
</target>
<target name="remove" description="Remove web application">
<remove url="${url}" username="${username}" password="${password}"
path="${path}"/>
</target>
</project>
Now, you can execute commands like ant install to install th applcation to a running instance of Tomcat, or ant reload to tell Tomcat to reload it. Note also that most of the interesting values in this build.xml file are defined as replaceable properties, so you can override their values from the command line. For example, you might consider it a security risk to include the real manager password in your build.xml file's source code. To avoid this, omit the password property, and specify it from the command line:
ant -Dpassword=secret deploy -
Hello,
I have a problem in the context configure.
My app is in C:\myapp. so I added a line in the right place of tomcat/conf/server.xml with
<Context path="/myapp" docBase="c:\myapp" debug="0" reloadable="true">
But when I start tomcat (http://localhost:8080, works), http://localhost:8080/myapp says /myapp is not available.
I test another way, copy the examples from tomcat/webapps to C:\examplescp, and then added line in the server.xml with <Context path="/examplescp" docBase="C:\examplecp .....
I still get the same error, /examplescp is not available. I tried tomcat3.1, 4.3, and 5.5, all the same error.
Can someone help?
Thanks,
Wayne
--Thanks, I may messed up the server.xml file. Now I cleaned all and reinstall the tomcat . I just copy the example folder to c and test. It works now,
W
. -
I have a java servlet based project which I ma trying to run using tomcat 4.1.18 web server. But am facing some problems if somebody could guide me here I would be greatly obliged.
I have a jar file name TCP.jar I have placed that in directory
C:\jakarta-tomcat-4.1.18\webapps\TCP\webApp\WEB-INF\lib
The jsp files have been placed in
C:\jakarta-tomcat-4.1.18\webapps\TCP\webApp\Render
In the server.xml file I have added
<Context path="/mmcp"
docBase="webapps/TCP/webApp"
crossContext="false"
debug="0"
reloadable="true" >
</Context>
</Host>
</Engine>
</Service>
The web.xml file has been modified to
<servlet>
<servlet-name>getImage</servlet-name>
<servlet-class>com.app.TCP.rendering.getImage</servlet-class>
and
<servlet-mapping>
<servlet-name>getImage</servlet-name>
<url-pattern>/GetImage</url-pattern>
</servlet-mapping>
This setup used to work in Tomcat 3.2.4 but with 4.1.18 when I try to get to url
http://localhost:8080/TCP/GetImage
I get
[bold]
description The requested resource (/mmcp/Controller) is not available.
[bold]
Any body out there with any explanations
</servlet>There was a typo in my original post instead of
<Context path="/mmcp"
it is
<Context path="/TCP" -
Creator App Tomcat Deployment Problem
I am trying to connect to a datasource in Tomcat and then access that datasource with my webapp here is the entry in server.xml
SERVER.XML
<Context path="/Login" docBase="Login"
debug="5" reloadable="true" crossContext="true">
<!-- maxActive: Maximum number of dB connections in pool. Make sure you
configure your mysqld max_connections large enough to handle
all of your db connections. Set to 0 for no limit.
-->
<!-- maxIdle: Maximum number of idle dB connections to retain in pool.
Set to -1 for no limit. See also the DBCP documentation on this
and the minEvictableIdleTimeMillis configuration parameter.
-->
<!-- maxWait: Maximum time to wait for a dB connection to become available
in ms, in this example 10 seconds. An Exception is thrown if
this timeout is exceeded. Set to -1 to wait indefinitely.
-->
<!-- username and password: MySQL dB username and password for dB connections -->
<!-- driverClassName: Class name for the old mm.mysql JDBC driver is
org.gjt.mm.mysql.Driver - we recommend using Connector/J though.
Class name for the official MySQL Connector/J driver is com.mysql.jdbc.Driver.
-->
<!-- url: The JDBC connection url for connecting to your MySQL dB.
The autoReconnect=true argument to the url makes sure that the
mm.mysql JDBC Driver will automatically reconnect if mysqld closed the
connection. mysqld by default closes idle connections after 8 hours.
-->
<Resource name="jdbc/MySQL" auth="Container" type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000"
username="jasonwpalmer" password="788721" driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/ElegantMailing?autoReconnect=true"/>
</Context>JARS
I have uploaded the appropriate .jars to tomcat5/common/lib
Jakarta-Commons DBCP
Jakarta-Commons Collections
Jakarta-Commons Pool
Connector-J
(When I looked at the .properties file it looked like all .jars in this directory are automatically added to classpath so I don't think the problem is with the classpath.
Now here is where I thnik I might have the problem, here is the code in my app to make the connection...
private void _init() throws Exception {
loginRowSet.setDataSourceName("jdbc:mysql://localhost:3306/ElegantMailing");
loginRowSet.setCommand("SELECT * FROM login");
loginRowSet.setTableName("login");
loginDataProvider.setCachedRowSet((javax.sql.rowset.CachedRowSet)getValue("#{SessionBean1.loginRowSet}"));
}I'm thinking maybe I have the url wrong, but i really don't know. Here is the exception...
System Messages Cannot read LOGIN database: java.sql.SQLException: JdbcRowSetXImpl (connect): (JNDI) Unable to connect: Name jdbc:mysql: is not bound in this Context
Anybody Please Help I'll gladly give up 5 Duke Stars to the person that helps me out.No the name of the database is ElegantMailing and from what I have learned we need to set a database url, not a url leading to the MySQL server. But if you thought I named my database MySQL then that would make sense, but I was making the same mistake. I was having such a hard time hooking my app up to datasource in Tomcat and that was one route I tried, changing the url in my app 999 times, this is a mistake, Creator does it right by default and all you have to do is set the datasource up in Tomcat Admin.
Make sure that you have the right driver installed in...
<Tomcat Install Dir>/common/lib
I used latest Connector/J with DBCP Connection Pooling.
Then you need to deploy your app to Tomcat I used the Tomcat/manager/html to deploy (if you have a hosting company that doesn't give you your own VPS with your own instance of Tomcat to configure however you like then get one because your on your own with this one(Search Eapps Hosting they're awesome, they even went so far as to install a .jsp that connected to MySQL for me!!!!!!!)).
After you deploy, do not launch app. Launch Tomcat Admin and then go to the left hand menu bar click the little goofy looking thing next to Service (Catalina) (For 3 days I didn't even know that goofy thing opened up more options, I read a post that said install your datasource right under the app in Tomcat and it took me forever to figure out this is what they were talking about) then you'll see the goofy thing for Host (click the goofy thing) and then you'll hopefully see the context/ for your app - you'll know what I mean when you see it- then you'll see resources, datasources, etc., click datasources. Here's the getcha gotcha, if you see an entry in datasources JNDI Name and JDBC Driver Class both with the names of your datasource and driver, then you're in business, if you don't, then don't bother going any further, something you have done this far is wrong. But, if you see the datasource, then you can click on it and fill in the data here is an example for the latest connector J
Property Value
JNDI Name: jdbc/ElegantMailing
Data Source URL: jdbc:mysql://localhost:3306/ElegantMailing?autoReconnect=true
JDBC Driver Class:
User Name:
Password:
Max. Active Connections:
Max. Idle Connections:
Max. Wait for Connection:
Validation Query: select * from login
This is only an example and if you are not using connector j then the ?autoReconnect=true part will probably be omitted. Also you need to know that there are 3 supporting jars for the connection pooling for connector j they are:
Jakarta-Commons DBCP
Jakarta-Commons Collections
Jakarta-Commons Pool
It is important to mention that I read a post that said after you configure datasource go back out to main menu and do it again in the root menu datasources, I do not know if this is necessary, but I did it just in case. Make sure you use the same entries.
If you follow these directions it really should work, here is a Tomcat link that walks you through everything I just explained. This is really hard if you never did it before, but believe me the first time this works and it all comes together, you're gonna feel like a million bucks. Hope this helps!
Here is the link:
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html -
Oracle Tomcat Connection Problem
Dear all,
We have Oracle as the back end and Java-Jsp-Struts as the front end for our project.For the last few days we are facing a strange problem and although we tried a lot we were not able to find even the cause of the problem
We have Oracle server and Webserver running on seperate machine. As this is a webbased solution , clients can take the pages by putting the URL in the browser. The problem is that the connection to the database is lost sometimes and we need to restart our apache tomcat service to get the connection again. Once it is restarted the pages work fine for sometime and after sometime the problem comes again. Sometimes the problem occures frequently and sometimes rarely.
Please help us as we tried a lot to troubleshoot but failed.
Whenever we are loosing connection, the database or listener seem to have no problem as they are running perfectly fine. Is there something that should be done in Tomcat for oracle connections? Or if multiple users are accessing the database at the same time is there something to do sothat the webserver is able to handle these multiple connections and update operations?
The error messages that we get are:
The network adapter could not establish the connection
or The TNS Listener could not resolve the SID given in the connection descriptor
If the error is the second one then sometimes it will vanish after sometime even without restarting thr tomcat service . But for the first one we must restart the service
All suggessions are welcome.
Regards,
Cochu.Hi,
Thanks for your valuable suggession, but when I
tried to ping from webserver to db server, it was
pinging all the time and I am sure that the LAN
Connection is alright.
Regards,
Cochu.No, the fact that Oracle works at all says that your network connection between servers is not the problem.
When you say "connection to Oracle", it sounds like you literally mean a single connection to Oracle. You open the connection on startup, so if it's stale or lost or dropped you have to restart the web app. Is this true?
If it is, your solution is to use a database connection pool and rewrite the database code in such a way that you get a fresh connection out of the pool when request comes in, use it, and immediately close it in the same scope, returning it to the pool. Scope should be within a single transaction in a single method. You should keep a connection open only for as long as you need it for a request.
% -
Hi ,
I addEnviornment details to Context object as soon as user logons to the application .
The user is validated against Weblogic Integration Server
and then context is made and store in Session.
I pass this context object to make a lookup on a session bean provided by WLI.However the look is made but any method is called on it gives following error.
java.rmi.AccessException: Security Violation: User: '' has insufficient permission to access EJB: type=, application=exman, module=wlpi-ejb.jar, ejb=Admin, method=getInstanceTasks, methodInterface=Remote, signature={java.lang.String}.
Can any one suggest the reason for this asap.
Thanks
Ashi found the problem,
the reason being,
The security context is associated with the current request, not the object obtained from JNDI, so you have to create a new initial context every time you need to access the EJB.
Even when i was storing the context in session , it was not taking from session object but from the thread. -
PDF with Tomcat/Cocoon Problem !!!
Hi,
I am having problem with Tomcat/Cocoon combination for APEX PDF printing which I installed following Carl Backstrom instructions.
When a report is a region report it all works fine, but when I create a report based on a query from the reports section in Shared Components choosing report layout 'Use Generic Report Layout' I get the following error.
javax.xml.transform.TransformerException: attribute-set named #TEXT_ALIGN# does not exist
cocoon://fop_post/xsl - 148:58
Cocoon stacktrace[hide]
attribute-set named #TEXT_ALIGN# does not exist
cocoon://fop_post/xsl - 148:58
I will appreciate any feedback. I saw threads related to the same issue on this forum but they ended up covering something irrelevant.
Regards,
VadimVadim,
Report queries and report region use the same generic report layout. However the processing is handled by different engines. The underlying technical problem with your case is that the substitution string #TEXT_ALIGN# is not substituted in all cases for report queries. This usually does not cause any problems, but appears not to work when using Cocoon.
I'll see that we can this resolved with the next version of APEX, however when working with report layouts, you would typically use your own RTF or XSL-FO stylesheets, where this problem would not occur. The option to use the generic report layout is only included so the data can be tested independently from the layout and is not really intended to be used as the actual layout at runtime.
The generic report layout function is mainly designed to be used for report regions.
Regards,
Marc
Maybe you are looking for
-
Can i share the same iTunes Match account across my iMac and my MacBook?
I recently subscribed to iTunes Match and am in the process of uploading my entire collection of files from my home iMac into the Cloud. This works fine for my iPhone and iPad, but not for my MacBook (which I use at work). Every time I try to 'Turn o
-
Lack of support from Blackberry in Australia
I have been trying to get my hands on a BB Passport since it was released last year so I can see what it feels like in the hand before I part with my money and buy the phone but it has been near impossible. The only carrier to carry the Passport in A
-
I recently purchased a Mac Pro (one month old) since day one I have found that when trying to use Face Time the camera is very intermittant, originally I thought it was a problem with the software, but have since realized that if I place a slight pre
-
JBO-26032: Operation getRow is invalid... - selectOne*, backing bean
Hi, I'm wondering why the exception JBO-26032 occurs, I have the following code in backing bean, it executes on valueChangeEvent (on selectOneChoice, selectOne* - always the same problem). Auto-submit is set to true. DCIteratorBinding dc
-
Hi, I am writing SMTP server in java as final project in programming course, the server uses the state and command patterns. in each state the server can only process specific SMTP commands which are encapsulated in a Command object. (Not a code,rath