Upgrading to Tomcat 5

Has anyone managed to upgrade to Tomcat 5 under OS X Server 10.4. while maintaining full functionality of the Server Admin app?
Just placing the new Tomcat install to /Library/Tomcat doesn't do the trick.

Not a solution, but it might help... (I've been wrestling with this problem for about 2 weeks now).
The issue I've been having is putting Tomcat 5 in /Library/Tomcat breaks my ability to use the Server Admin's web setting.
What I did was create a new folder in /Library called Tomcat_5. I placed the Tomcat 5 files there.
I do have to manually start Tomcat each time I start the server, but Tomcat 5 is running and I have full functionality of the web settings in Server Admin.

Similar Messages

Upgraded from Tomcat 3.3.1 to Tomcat 4.0.4 receiving Stack

I moved my war file into my new Tomcat 4.0.4 webapps directory since I
need to upgrade in order to use some 'other' tags and I'm receiving
the following stacktrace when I try to hit the first page in my
application....
Any ideas as to why this is occurring?
StackTrace Below:
Application Error
javax.servlet.ServletException: Invalid request - request handler
"VoyagerLogin"
not found
at
com.iplanet.jato.ApplicationServletBase.onRequestHandlerNotFound(Appl
icationServletBase.java:1153)
at
com.iplanet.jato.ApplicationServletBase.fireRequestHandlerNotFoundEve
nt(ApplicationServletBase.java:977)
at
com.iplanet.jato.ApplicationServletBase.getViewBeanInstance(Applicati
onServletBase.java:717)
at
com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationSer
vletBase.java:429)
at
com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase
.java:312)
at
com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.
java:282)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.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.jav
a: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.j
ava:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava: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.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcesso
r.java:1027)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.ja
va:1125)
at java.lang.Thread.run(Thread.java:536)

There's definitely something wrong with my application directory or
the .war file because I can run the JatoSample and the JatoTutorial
applications fine from within Tomcat-4.0.4.....
--- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
wrote:
Send me the war file with source. I'll see if I can run it on mymachine
or figure out what the issue is.
send to: craig.conover@s...
craig
chubbykidd wrote:
Total disaster. My application will not work. I've closed all
instances of Netscape and even logged off the SunRay I'm working on
and I still get the same error. I then took your advice and
downloaded
Resin and installed it. Now when I hit the following URL...
http://localhost:8080/Voyager/voyagermodule/VoyagerLogin I receivean
'Application Error' page which states "Invalid request - request
handler VoyagerLogin not found"
I don't know what to do, I'm running out of possiblities...
Help :-/
--- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
wrote:
This will happen if the browser was already running, but you say
you
closed your browsers first. Make sure all instances of the browser
are
closed. For IE, when you launch one IE instance from another
(Ctrl-N),
they share the same process space.
For Netscape, all instances always share the same process space.
This
includes the Mail client, so be sure all of them have been closed.
I might suggest test running in Resin from Caucho (www.caucho.com)
to
make sure it's not a Tomcat bug or setup/install issue. Resin
installs
with just an unzip, and drop the war file in the webapps dir, and
start
the server.
c
chubbykidd wrote:
I deleted my jakarta-tomcat-3.3.1 directory and now I'm getting a
different error when I try to hit the first page in my
application:
>>>>
The URL of my app is:
http://localhost:8080/Voyager/voyagermodule/VoyagerLogin
StackTrace below.... I've restarted tomcat after this stack was
thrown
and I've also closed my browsers and started over and I keep
getting
the same outcome....
javax.servlet.ServletException: This session has timed out
at
com.iplanet.jato.ApplicationServletBase.onSessionTimeout(ApplicationServletBas\
e.java:1075)
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.fireSessionTimeoutEvent(ApplicationSer\
vletBase.java:941)
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.fireSessionEvents(ApplicationServletBa\
se.java:649)
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.\
java:427)
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:312\
>>>
>>>
at
com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.java:282)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFi\
lterChain.java:247)
>>>
>>>
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChai\
n.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.ja\
va: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:1\
74)
>>>
>>>
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:10\
27)
>>>
>>>
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)
at java.lang.Thread.run(Thread.java:536)
[85] wb138834@s...:
--- In SunONE-JATO@y..., Todd Fast <Todd.Fast@S...> wrote:
This error means the page/ViewBean you requested was not found.
What is the
URL you are using? Also make sure everything is compiled.
Todd
----- Original Message -----
From: "chubbykidd" <bacon33@o...>
Sent: Thursday, August 29, 2002 11:13 AM
Subject: [SunONE-JATO] Upgraded from Tomcat 3.3.1 to Tomcat
4.0.4
>>>>>
>>>>>
>>>>>
>>>>>
receiving
Stack
I moved my war file into my new Tomcat 4.0.4 webapps directory
since I
need to upgrade in order to use some 'other' tags and I'm
receiving
the following stacktrace when I try to hit the first page in my
application....
Any ideas as to why this is occurring?
StackTrace Below:
Application Error
javax.servlet.ServletException: Invalid request - request
handler
"VoyagerLogin"
not found
at
com.iplanet.jato.ApplicationServletBase.onRequestHandlerNotFound(Appl
icationServletBase.java:1153)
at
com.iplanet.jato.ApplicationServletBase.fireRequestHandlerNotFoundEve
nt(ApplicationServletBase.java:977)
at
com.iplanet.jato.ApplicationServletBase.getViewBeanInstance(Applicati
onServletBase.java:717)
at
com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationSer
vletBase.java:429)
at
com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase
.java:312)
at
com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.
java:282)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.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.jav
a: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.j
ava:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava: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.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcesso
r.java:1027)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.ja
va:1125)
at java.lang.Thread.run(Thread.java:536)
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp

Upgrade Apache Tomcat 7.52 to 7.63

We have a Windows 2008R2 server with Tomcat 7.52 installed. I installed the O/S and our vendor installed their software, Tomcat and Java. I have never touched Tomcat, but due to vulnerabilities, I need to update Tomcat and Java. Java should be straightforward. I have downloaded their recommended version and can just uninstall the old version and run the installer for the new version. The vendor will provide no support or documentation for the Tomcat upgrade. All they will tell me is to stay within the same major version. I have been to apache.org and many other websites, but can't find step by step instructions to update Tomcat in place without losing configuration files/settings.
I would appreciate any info to point me in the right direction.
Thanks for reading.
This topic first appeared in the Spiceworks Community

Hi Donna,
You can refer SAP KBA 1769495. The KBA contains steps to upgrade to Tomcat 7.0.29, however the steps will remain same for Tomcat 7.0.50 except you will need to download Tomcat 7 from
http://archive.apache.org/dist/tomcat/tomcat-7/v7.0.50/bin/apache-tomcat-7.0.50-windows-x64.zip
The remaining steps will remain same for this version of Tomcat as well.
Regards,
Hrishikesh

New error with upgrade jboss/tomcat: "Connection handle has been closed and is unusable"

Hi,
This error suddenly appeared when we upgraded from jboss3/tomcat5.0 to jboss4.2/tomcat5.5.
here's the usecase:
1) User clicks on report link
2) Crystal reports web componnent displays screen to fill in report parameters.
3) user enters parameters and clicks submit
4) System throws Exception
The same reports worked fine with jboss 3.2.6/tomcat 5.0. We haven't touched anything in this realm.
Log Excerpt:
09:42:18,842 INFO [datasource] Openning rowset
09:42:18,904 ERROR [reportdefinition] com.crystaldecisions.reports.queryengine.driverImpl.m: JDBC Error: Connection handle has been closed and is unusable
09:42:18,905 ERROR [datasource] Failed to open rowset: the query failed to open rowset
com.crystaldecisions.reports.reportdefinition.datainterface.g: JDBC Error: Connection handle has been closed and is unusable
 at com.crystaldecisions.reports.reportdefinition.datainterface.d.a(Unknown Source)
To try to narrow down the problem, I've updated the jdbc configuration to
 <track-statements>true</track-statements>
here's a recap:
This Boolean element specifies whether to check for unclosed statements when a connection is returned to the pool. If it is true, a warning message is issued for each unclosed statement. If the log4j category org.jboss.resource.adapter.jdbc.WrappedConnection has trace level enabled, a stack trace of the connection close call is logged as well. This is a debug feature that can be turned off in production.
Interestingly enough, this error appears slightly upstream:
(CachedConnectionManager.java:526) - Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@c76003
java.lang.Throwable: STACKTRACE
 at
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
 at com.crystaldecisions.reports.queryengine.driverImpl.k.a(Unknown Source)
 at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
 at com.crystaldecisions.reports.queryengine.av.new(Unknown Source)
 at com.crystaldecisions.reports.queryengine.av.byte(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.j.a(Unknown Source)
 at com.crystaldecisions.reports.dataengine.ba.try(Unknown Source)
 at com.crystaldecisions.reports.common.av.a(Unknown Source)
 at com.crystaldecisions.reports.common.ag.a(Unknown Source)
 at com.businessobjects.reports.sdk.b.e.a(Unknown Source)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown
So the question arises:
1) Is the jboss datasource overly/aggressively closing result sets?
2) or is there a coding error in CRXIR2?
thanks,
bill
Full stack trace:
[2008-03-13 17:26:18,905] [INFO ] org.jboss.resource.connectionmanager.CachedConnectionManager (CachedConnectionManager.java:526) - Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@c76003
java.lang.Throwable: STACKTRACE
 at org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:290)
 at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:417)
 at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
 at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
 at com.crystaldecisions.reports.queryengine.driverImpl.k.a(Unknown Source)
 at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
 at com.crystaldecisions.reports.queryengine.av.new(Unknown Source)
 at com.crystaldecisions.reports.queryengine.av.byte(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.b.a(Unknown Source)
 at com.crystaldecisions.reports.reportdefinition.datainterface.j.a(Unknown Source)
 at com.crystaldecisions.reports.dataengine.ba.try(Unknown Source)
 at com.crystaldecisions.reports.common.av.a(Unknown Source)
 at com.crystaldecisions.reports.common.ag.a(Unknown Source)
 at com.businessobjects.reports.sdk.b.e.a(Unknown Source)
 at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
 at com.crystaldecisions.proxy.remoteagent.y.a(Unknown Source)
 at com.crystaldecisions.proxy.remoteagent.r.a(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.cf.a(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.z.a(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.ak.if(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.ad.int(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.bk.for(Unknown Source)
 at com.crystaldecisions.proxy.remoteagent.v.a(Unknown Source)
 at com.crystaldecisions.proxy.remoteagent.v.if(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(Unknown Source)
 at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setTableLocation(Unknown Source)
 at com.crystaldecisions.reports.sdk.DatabaseController.setTableLocation(Unknown Source)
 at org.apache.jsp.reports.processreport_jsp.switchTables(processreport_jsp.java:131)
 at org.apache.jsp.reports.processreport_jsp.loadReport(processreport_jsp.java:68)
 at org.apache.jsp.reports.processreport_jsp._jspService(processreport_jsp.java:227)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:387)
 at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.shared.pagecache.client.PageCacheFilter.doFilter(PageCacheFilter.java:760)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.util.servlet.ExpiredPasswordFilter.doFilter(ExpiredPasswordFilter.java:92)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.pe.channels.client.servlet.ChannelUrlFilter.processUrl(ChannelUrlFilter.java:168)
 at com.participate.pe.channels.client.servlet.ChannelUrlFilter.doFilter(ChannelUrlFilter.java:100)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.util.servlet.BlockIpAddressFilter.doFilter(BlockIpAddressFilter.java:224)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.outstart.multiapp.filters.KeepOtherSessionsAliveFilter.doFilter(KeepOtherSessionsAliveFilter.java:88)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at com.participate.util.servlet.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:151)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
 at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
 at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
 at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
 at java.lang.Thread.run(Thread.java:619)


OK. I found the problem along with a workaround.


The problem:


a programming practice clashes with a new jboss 'safety check'.


Programming practice:


crystal reports gets a database connection in one jsp page, then tries to use it on another jsp/servlet


Jboss safety check:
Jboss/tomcat new comes configured out-of-the-box with a 'cached connection
manager', which


"Check[s] for unclosed connections and transaction terminated checks in servlets/jsps."


 Summary


In short, if a servlet/jsp ends and it leaves a database connection open, Jboss will automatically close it.




Workaround: 
Comment out two entries in these two files:


1) conf/jboss4/pe/deploy/jboss-web.deployer/server.xml


2) conf/jboss4/pe/deploy/jboss-web.deployer/META-INF/jboss-service.xml


The two entries:




1)


 <Valve className="org.jboss.web.tomcat.service.jca.CachedConnectionValve" 
 cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager" 
 transactionManagerObjectName="jboss:service=TransactionManager" /> 


2)


 <depends>jboss.jca:service=CachedConnectionManager</depends> 




Comments on the workaround


The 'cached connection manager' basically makes sure that the application cleans up after bad programmers. It seems most helpful in development, load testing, or trouble shooting.


In production, you can likely comment them out with minimal
impact on the application.

Upgrad to Tomcat 4.0 with JBuilder 5

Hi all
Has anyone tried to upgrad the web server to Tomcat 4.0 with JBuilder 5? I have followed the instruction in the documentation (which said I only need to specify to use Tomcat 4.0 and locate the installation path), however, I still couldn't start the web server.
I got the following msg when starting web server:
StandardManager[LiteWeb]: Seeding of random number generator has been completed
ERROR reading java.io.ByteArrayInputStream@504653
At Line 11 /web-app/servlet/
ContextConfig[LiteWeb]: Configuration error in application web.xml
java.lang.IllegalArgumentException: addChild: Child name 'jsp' is not unique
java.lang.IllegalArgumentException: addChild: Child name 'jsp' is not unique
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
     at org.apache.catalina.core.StandardContext.addChild(StandardContext.java:1276)
     at java.lang.reflect.Method.invoke(Native Method)
     at org.apache.catalina.util.xml.AddChild.end(XmlMapper.java:811)
     at org.apache.catalina.util.xml.XmlMapper.matchEnd(XmlMapper.java:419)
     at org.apache.catalina.util.xml.XmlMapper.endElement(XmlMapper.java:119)
     at com.sun.xml.parser.Parser.maybeElement(Parser.java:1413)
     at com.sun.xml.parser.Parser.content(Parser.java:1499)
     at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400)
     at com.sun.xml.parser.Parser.parseInternal(Parser.java:492)
     at com.sun.xml.parser.Parser.parse(Parser.java:284)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:155)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:77)
     at org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:275)
     at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:256)
     at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:824)
     at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:224)
     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:155)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1131)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:3345)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:614)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:343)
     at org.apache.catalina.core.StandardService.start(StandardService.java:388)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:506)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:781)
     at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
     at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
     at java.lang.reflect.Method.invoke(Native Method)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
ContextConfig[LiteWeb]: Marking this application unavailable due to previous error(s)
StandardContext[LiteWeb]: Error initializing naming context for context /LiteWeb
StandardContext[LiteWeb]: Context startup failed due to previous errors
StandardContext[LiteWeb]: Error initializing naming context for context /LiteWeb
WebappLoader[]: Deploying class repositories to work directory D:\myWorkPad_ProTel2\CRMLite\work
StandardManager[]: Seeding random number generator class java.security.SecureRandom
StandardManager[]: Seeding of random number generator has been completed
ERROR reading java.io.ByteArrayInputStream@31aa65
At Line 11 /web-app/servlet/
ContextConfig[]: Configuration error in application web.xml
java.lang.IllegalArgumentException: addChild: Child name 'jsp' is not unique
java.lang.IllegalArgumentException: addChild: Child name 'jsp' is not unique
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
     at org.apache.catalina.core.StandardContext.addChild(StandardContext.java:1276)
     at java.lang.reflect.Method.invoke(Native Method)
     at org.apache.catalina.util.xml.AddChild.end(XmlMapper.java:811)
     at org.apache.catalina.util.xml.XmlMapper.matchEnd(XmlMapper.java:419)
     at org.apache.catalina.util.xml.XmlMapper.endElement(XmlMapper.java:119)
     at com.sun.xml.parser.Parser.maybeElement(Parser.java:1413)
     at com.sun.xml.parser.Parser.content(Parser.java:1499)
     at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400)
     at com.sun.xml.parser.Parser.parseInternal(Parser.java:492)
     at com.sun.xml.parser.Parser.parse(Parser.java:284)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:155)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:77)
     at org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:275)
     at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:256)
     at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:824)
     at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:224)
     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:155)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1131)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:3345)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:614)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:343)
     at org.apache.catalina.core.StandardService.start(StandardService.java:388)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:506)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:781)
     at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
     at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
     at java.lang.reflect.Method.invoke(Native Method)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
ContextConfig[]: Marking this application unavailable due to previous error(s)
StandardContext[]: Error initializing naming context for context
StandardContext[]: Context startup failed due to previous errors
StandardContext[]: Error initializing naming context for context
HttpConnector[8082] Starting background thread

Solved it. I ran into this problem too, and had to look all over the place to find the solution.
In the end it's a matter of binning your current JBuilder project and starting a new one with the same files. For some reason JBuilder5 hates switching Tomcat installations within projects. From there it seems to ignore changes to your web.xml, and insists on yu_hung's error.
Switch it all into a new project with Tomcat 4 as its default server, and it becomes happy again.
Hope that helps!
Martin Hughes

NB upgrade - from tomcat to glassfish

I upgraded NetBeans from 5.5b to 6.1. There is no longer a bundled tomcat, instead there is glassfish.
My old web projects (written against tomcat) build correctly but they no longer run under glassfish. I get a 404 when I try to access them. I do not know glassfish well enough to troubleshoot via gf log messages whey they are not running under gf.
Should these old tomcat projects run orrectly in glassfish or do i have to configure a file like web.xml in order to get them to run under glassfsh?

duffymo wrote:
qt4x11 wrote:
I upgraded NetBeans from 5.5b to 6.1. There is no longer a bundled tomcat, instead there is glassfish.
My old web projects (written against tomcat) build correctly but they no longer run under glassfish. I get a 404 when I try to access them. I do not know glassfish well enough to troubleshoot via gf log messages whey they are not running under gf.404 suggests that you just have a deployment or URL issue. What URL do you use to invoke the web app? Do you package it in a WAR file? Tomcat's default port is 8080; what port is Glassfish listening to for HTTP requests?
I hit 'run main project' - the main project builds, then glassfish is started, and a browser window starts up with the web app.
I am new to glassfish - I checked Services/Servers/GlassfishV2/Properties - it says
Location: localhost:8484
is that the port you are asking about?
duffymo wrote:
qt4x11 wrote:
Should these old tomcat projects run orrectly in glassfish or do i have to configure a file like web.xml in order to get them to run under glassfsh?%

Upgrading JDK Tomcat Zip Exception

Thanks in advance for any help.
I have a web application that is running on tomcat 5.5.12. It was using JDK 1.4.2_10. I updated my linux machine for the new time changes that started this year. I then tried to update the JDK to 1.4.2_16 so that it would also adhere to the new rules. When I went to startup tomcat again I got the following exception.
INFO: XML validation disabled
Nov 2, 2007 2:53:17 PM org.apache.catalina.core.StandardContext start
SEVERE: Error in dependencyCheck
java.util.zip.ZipException: invalid entry CRC (expected 0x0 but got 0xe6b54ce)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:164)
at java.util.jar.JarInputStream.read(JarInputStream.java:159)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
at java.util.jar.JarInputStream.getBytes(JarInputStream.java:88)
at java.util.jar.JarInputStream.<init>(JarInputStream.java:65)
at java.util.jar.JarInputStream.<init>(JarInputStream.java:43)
at org.apache.catalina.util.ExtensionValidator.getManifest(ExtensionValidator.java:368)
at org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:187)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3998)
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:910)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:873)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
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:680)
at org.apache.catalina.startup.Catalina.start(Catalina.java:536)
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:275)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Nov 2, 2007 2:53:17 PM org.apache.catalina.core.StandardContext start
SEVERE: Error getConfigured
I am not sure where to start debugging this, so like I said any help would be appreciated.
Thanks

Hello,
we `re facing a similar or the same problem.
While upgrading our machines from 1.5.0_10 t9 1.5.0_13 (JDK) we got this error:
+19.11.2007 14:24:13 org.apache.catalina.core.StandardContext start+
SCHWERWIEGEND: Error in dependencyCheck
java.util.zip.ZipException: invalid entry CRC (expected 0x0 but got 0xfc0d5d73)
+ at java.util.zip.ZipInputStream.read(Unknown Source)+
Workaround:
We unzip the war-file and recommpress these files with 7-zip (or else) to bla.war - the new war file is deployable.
But:
Has anyone an idea the changes from *.10 to *.13 which provoke this error OR
has war files to be created in another way as "jar cvf filename.war *" in *.13..?

Upgradation of tomcat from 3.2 to tomcat 5.5

Hello,
Does anybody knows how to upgrade the web application running in tomcat 3.2 to tomcat 5.5.
Thanks

Hi,
Sorry but that isn't related to Java programming, and it's a question that is specific to Tomcat. I would google for a Tomcat forum or mailing list.
Kaj

Trouble upgrading from tomcat 3.1 to 4.1

Hi,
I have this jsp application running fine with Tomcat 3.1 under W2K and i'm now having trouble having them run on Tomcat 4.1 on the same PC.
Basically i just renamed the Tomcat 3.1 directory, installed Tomcat 4.1, modified the server.xml file to let it know my application context. which means i did not change any environment variables.
I get this message when trying to run my application:
org.apache.jasper.JasperException: Impossible de compiler la classe pour JSP
E:\tomcat\work\localhost\MPREPORT\Bcplogon$jsp.java:5: Class or interface declaration expected.
import javax.servlet.*;
^
E:\tomcat\work\localhost\MPREPORT\Bcplogon$jsp.java:11: Superclass org.apache.jsp.HttpJspBase of class org.apache.jsp.Bcplogon$jsp not found.
public class Bcplogon$jsp extends HttpJspBase {
^
2 errors
Any hints welcome.
Christophe

yes the samples are running OK. I just don't see why i have compile problems since i did not modify the Classpath and JDK setup.
Also this 'import javax.servlet.*;' that can be seen in the error message: i use some import in my code, but not this one. Could that lead to some explanations ?

Upgrading to Tomcat 5.5

I am finally getting to work on Tomcat 5.5 container after years of working on Tomcat 4.1.27. Please advise what already comes with Tomcat 5.5? I think it has Generics and Expression Language (EL) with the standard install? Any other major features? I assume it doesnt come with Struts and JSTL?

florida41 wrote:
I am finally getting to work on Tomcat 5.5 container after years of working on Tomcat 4.1.27. Please advise what already comes with Tomcat 5.5? new servlet and jsp specs; jstl 1.1.
%

Upgrade from tomcat to OC4J 10.1.3 jsp parser exception in tag lib

i have problem in oc4j jsp parser
but it work ok on tomcat as tomcat using jasper-compiler.jar
when run on oc4j it give me the exception
OracleJSP: oracle.jsp.parse.JspParseException: /jsp/layouts/elec/pageheading.jsp: Line # 3, <aa:h1 wrapped="true" labelKey="${heading1BundleKey}"/>
Error: Errors parsing tag :h1 oracle.jsp.parse.JspParseException: /jsp/layouts/elec/pageheading.jsp: Line # 3, <aa:h1 wrapped="true" labelKey="${heading1BundleKey}"/>
Error: oracle.jsp.provider.JspCompileException: <H3>Errors compiling:E:\oc4j\j2ee\home\application-deployments\default\sc40\persistence\_tagfiles\_oracle\_jsp\_tag\_aacom\_h1_2e_tag.java</H3><TABLE BORDER=1 WIDTH=100%><TR><TH ALIGN=CENTER>Line #</TH><TH ALIGN=CENTER>Error</TH></TR><TR><TD WIDTH=7% VALIGN=TOP>191</TD><TD> non-static variable _jspFragWriter cannot be referenced from a static context
_jspFragWriter = null;
-------------------------------------------------------->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
and i have problem in web.xml
as i using jsp servlet in jasper-compiler.jar in tomcat package
<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
------------------------------------>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
i try to use this package in oc4j but i can not
i put this servlet in global-web-application.xml instead of
<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class>
------------------>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
to make oc4j depend on tomcat parser it give me
classnotfound mean that (oc4j can not found package) this printed in global-application.log
i make
<library path="E:/oc4j/j2ee/home/applib/jasper-compiler.jar"/>
and still have problem
any 1 have idea using tomcat parser in oc4j
or have idea solve this problem
thanx
Message was edited by:
[email protected]
Message was edited by:
[email protected]
Message was edited by:
[email protected]
Message was edited by:
[email protected]

OC4J 10.1.3 does support JSP 2.0, as well as custom tag libraries (including JSTL 1.1).
There are two approaches to configuring a custom tag library for use in JSPs served by OC4J:
1) Package the JSTL or custom tag library with your application:
i. include the necessary JAR file in your web app's /WEB-INF/lib folder
ii. include the relevant Tag Library Descriptor (TLD) file(s) in your web app's /WEB-INF folder
iii. for each TLD, add a <tag-lib> element to web.xml referencing the TLD file's location and taglib URI
2) Place the JSTL or custom tag library in an Application Server instance-level directory ($ORACLE_HOME/j2ee/home/jsp/lib/taglib) to make them available to multiple applications (in all OC4Js installed in the Oracle Home)
For example, if you'd like to use the JSTL 1.1 Core and Internationalization Tag Libraries, do one of the following:
1) Package the JSTL or custom tag library with your application:
i. Obtain an implementation of JSTL (e.g. Jakarta Taglibs) and include the standard.jar and jstl.jar files in your web module's /WEB-INF/lib directory
ii. From the JSTL implementation you're using, also copy the c.tld and fmt.tld Tag Library Descriptors to your web module's /WEB-INF/lib directory
iii. Add the following elements to your web module's web.xml file:
<jsp-config>
<taglib>
<taglib-uri>http://java.sun.com/jsp/jstl/core</taglib-uri>
<taglib-location>/WEB-INF/c.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>http://java.sun.com/jsp/jstl/fmt</taglib-uri>
<taglib-location>/WEB-INF/fmt.tld</taglib-location>
</taglib>
</jsp-config>
OR
2) Copy the standard.jar and jstl.jar libraries from the JSTL implementation you're using to $ORACLE_HOME/j2ee/home/jsp/lib/taglib

SQL Exception after upgraded to Tomcat 5

I used to develop JSP in SunOne Studio 4 Update 1, which comes with Tomcat 4.0
My database is Microsoft Access Database. My JDK is 1.4.2
My JSP applications work in SunONE studio's Tomcat environment.
However, I tried to run the application in Tomcat 5.0 without SunONE studio. It is not working for all the pages related with Database connection.
The error says: "java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
But it DO works using the same code under SunONE's environment.
Following is my connection.
String url = application.getInitParameter("dBURL");
String username = application.getInitParameter("dBUserName");
String password = application.getInitParameter("dBUserPassword");
Connection conn = null;
String classPath = "sun.jdbc.odbc.JdbcOdbcDriver";
try {
    Class.forName(classPath);
    conn = DriverManager.getConnection(url,username,password);
} catch (Exception exc){
    out.println(exc.toString());
Statement stm = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
String query;
ResultSet rst=null;I have tested using out.println(application.getInitParameter("dBURL")); that the parameters are retrieved successfully.
conn = DriverManager.getConnection(url,username,password); is actually the place where the error occurs.
Any body knows about this error?

This sounds like it might answer your question... probably SunONE does some of this for you, that you might have to do manually without it.
http://java.sun.com/webservices/docs/1.1/tutorial/doc/Admintool5.html

Unable to resolve Apache-Tomcat after 5.0.2 Upgrade / Content Server Install

I recently upgraded from 5.0.1 to 5.0.2. With 5.0.1, I was able to resolve to http://<apache-tomcat.domain.com>:8080 as well as http://<apache-tomcat.domain.com>:8080/ptcsand http://<apache-tomcat.domain.com>:8080/ptcs/diagnosticsTest.jsp. However, after upgrading to 5.0.2, I am unable to resolve to any of these URLs. The 'Content Server' admin. folder shows up within the admin. ui and all necessary objects are there. Other than the upgrade, no other changes were made to the server. Any suggestions? Thanks.

Did you upgrade to Tomcat 4.1.27LE version ?

Tomcat 4.1.12 upgrade error...

Can someone interpret the following error?
"WebappClassLoader: validateJarFile(D:\Work_Files\jakarta-tomcat-4.1.12\webapps\IfaxSend\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, section9.7.2. Offending class:javax/servlet/Servlet.class"
I was upgrading from Tomcat 4.0.2 standalone on windows 2k to Tomcat 4.1.12 standalone, installed fine, however when I went to migrate a couple of apps (servlets only) that I have been running on 4.0.2, I get this error - I tried both the servlet.jar from JDK1.3.1_02 that I used before, and the currently installed jdsk1.4.1_01 versions - no different.
Any suggestions? The servlet spec section referred to tells me absolutely nothing that I can understand....
Thanks, Geoff

I think there is a conflict between to two servlet versions. The lastest release of tomcat supports servlet 2.3 and you don't have to include any servlet jar files in tomcat's classpath.

Upgrading Tomcat to 5.5?

I have a very rudimentary knowledge of how to use os x server and even less knowledge in upgrading os x server. I was wondering if anyone had any kind of simple documentation out there on upgrading the default instillation on os x server (Tomcat 4.1.x) to Tomcat 5.5? I searched the internet and couldn’t come up with anything.
Thanks!
Nikita

I upgraded to Tomcat 6.0 and here are the following things I did. They may be of use.
I copied /Library/Tomcat to /Library/Tomcat4
Installed Tomcat6 in /Library/Tomcat
Copied Tomcat/conf/server.xml to Tomcat/conf/server.xml.orig
Copied Tomcat4/conf/server.xml to Tomcat/conf/server.xml
Edited tomcat-users.xml to remove the comments enabling those users (although looking back I don't think this was necessary)
Edited the new server.xml file and copied the Global JNDI Settings from server.xml.orig. (And then also added the Listeners that weren't in the v4)
In Tomcat/bin I did a chmod ug+x *.sh
From Tomcat I did a chown -R appserver *
From Tomcat I did a chgrp -R appserverusr *
Then the big gotcha... The Coyote Connectors were coming up as HTTP 1.1 Connectors so the AJP connections just spun. You need to add the value protocol="AJP/1.3" to the Connector tags. Then WebServer can see the JBoss1 AJP again.
Good luck!

Upgrading to Tomcat 5

Similar Messages

Maybe you are looking for