RE: Question about upgrading tomcat-embed-core from 10.1.20 to 10.1.25

[KARR, DAVID]

Thanks for that. Could you give me more info on those problems in 10.1.24-29, 
like links to the issues?

From: Mark Thomas 
Sent: Sunday, September 15, 2024 9:14 AM
To: users@tomcat.apache.org
Subject: Re: Question about upgrading tomcat-embed-core from 10.1.20 to 10.1.25

On 15/09/2024 00: 37, KARR, DAVID wrote: > We build SpringBoot applications 
that reference "tomcat-embed-core" from "spring-boot-starter-jersey". We 
currently end up with version 10. 1. 20 of tomcat-embed-core, using spring-boot 
3. 2. 5. There






On 15/09/2024 00:37, KARR, DAVID wrote:

> We build SpringBoot applications that reference "tomcat-embed-core" from 
> "spring-boot-starter-jersey". We currently end up with version 10.1.20 of 
> tomcat-embed-core, using spring-boot 3.2.5.  There is apparently a CVE for 
> that version of tomcat-embed-core (I don't have the CVE handy right now).  
> The resolution is to replace it with version 10.1.25.  That, being a patch 
> version, seems like a safe upgrade from a functionality point of view. Are 
> there any known issues from performing that upgrade?



There is a known issue with non-blocking reads and chunked encoding in

10.1.24 to 10.1.29.



I'd wait for 10.1.30 in a few days (HTTP/2 is broken in 10.1.29).



Mark





-

To unsubscribe, e-mail: 
users-unsubscr...@tomcat.apache.org<mailto:users-unsubscr...@tomcat.apache.org>

For additional commands, e-mail: 
users-h...@tomcat.apache.org<mailto:users-h...@tomcat.apache.org>

Question about upgrading tomcat-embed-core from 10.1.20 to 10.1.25

[KARR, DAVID]

We build SpringBoot applications that reference "tomcat-embed-core" from 
"spring-boot-starter-jersey". We currently end up with version 10.1.20 of 
tomcat-embed-core, using spring-boot 3.2.5.  There is apparently a CVE for that 
version of tomcat-embed-core (I don't have the CVE handy right now).  The 
resolution is to replace it with version 10.1.25.  That, being a patch version, 
seems like a safe upgrade from a functionality point of view. Are there any 
known issues from performing that upgrade?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Diagnose why Tomcat doesn't appear to deploy webapp module

[KARR, DAVID]

> -Original Message-
> From: KARR, DAVID
> Sent: Monday, April 17, 2017 5:01 PM
> To: Tomcat Users List 
> Subject: Diagnose why Tomcat doesn't appear to deploy webapp module
> 
> I'm trying to set up an existing Spring webapp that ran on a different
> container before (weblogic), to run on Tomcat.  Working on it in
> Eclipse, I've gotten all of the compile errors out, and I was able to
> add the webapp to my Tomcat server instance in the "Servers" view.  I
> started the server instance, and I didn't see any errors in the console
> log, but I also didn't see lines that looked like it was deploying my
> web module.
> 
> As expected, trying to access
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__localhst-
> 3A8080_appname_&d=DwIFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=OsTemSXEn-
> xy2uk0vYF_EA&m=oyQ_NBiOh5rBgq1V_M0QCtZ8cB6gRkV45Yuz7uyvVV4&s=PKa2NzMo1KW
> l9mLgyHSf5lChZHZZ9WvoTGSN97vDrZM&e= > (and also trying various
> "index.html" variations) just gets a 404.  It just seems like Tomcat is
> silently ignoring my webapp.
> 
> What information can I get to determine why this might be happening?
> 

I've gotten past this.  Somehow a directory named "WEB_INF" (underscore) works 
in WebLogic, but it's ignored in Tomcat (naturally).

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Diagnose why Tomcat doesn't appear to deploy webapp module

[KARR, DAVID]

I'm trying to set up an existing Spring webapp that ran on a different 
container before (weblogic), to run on Tomcat.  Working on it in Eclipse, I've 
gotten all of the compile errors out, and I was able to add the webapp to my 
Tomcat server instance in the "Servers" view.  I started the server instance, 
and I didn't see any errors in the console log, but I also didn't see lines 
that looked like it was deploying my web module.

As expected, trying to access  (and also trying 
various "index.html" variations) just gets a 404.  It just seems like Tomcat is 
silently ignoring my webapp.

What information can I get to determine why this might be happening?



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: When do I actually need to add JNDI references to web.xml?

[KARR, DAVID]

> -Original Message-
> From: KARR, DAVID
> Sent: Tuesday, March 14, 2017 1:20 PM
> To: Tomcat Users List 
> Subject: When do I actually need to add JNDI references to web.xml?
> 
> I have a small CXF/REST/Spring/JDBC app that I've run on TomEE and
> Tomcat.  I define datasources and environment entries and retrieve those
> from the application code using JNDI interfaces.  This all works fine.
> 
> What confuses me is that whenever I read in various unrelated docs about
> setting and using JNDI entries, even in applications running in Tomcat,
> it says that I also have to put resource reference elements into my
> application's "web.xml" file.  I don't think I've EVER added those
> elements to a web.xml file, and I've defined and used JNDI resources in
> many applications, including the current one.
> 
> As I'm getting these resources through Spring, does that somehow make it
> unnecessary to add those elements?
> 
> When are they actually required?

I suppose I can self-answer this somewhat, but I'd still appreciate another POV.

>From what I understand, I can see two reasons why the resource reference might 
>be required:
* If the application code needs to reference it with a different name than is 
in JNDI
* If an application framework needs to inspect the configuration model of an 
application, to see those declared references, to perform background 
infrastructure actions associated with those references

The first is pretty obvious, but I just read about a large framework that looks 
for these declared references to perform automated actions.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

When do I actually need to add JNDI references to web.xml?

[KARR, DAVID]

I have a small CXF/REST/Spring/JDBC app that I've run on TomEE and Tomcat.  I 
define datasources and environment entries and retrieve those from the 
application code using JNDI interfaces.  This all works fine.

What confuses me is that whenever I read in various unrelated docs about 
setting and using JNDI entries, even in applications running in Tomcat, it says 
that I also have to put resource reference elements into my application's 
"web.xml" file.  I don't think I've EVER added those elements to a web.xml 
file, and I've defined and used JNDI resources in many applications, including 
the current one.

As I'm getting these resources through Spring, does that somehow make it 
unnecessary to add those elements?

When are they actually required?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Moved app from TomEE to Tomcat, now getting Spring errors failing to go through proxy for XML validation

[KARR, DAVID]

> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Friday, March 10, 2017 10:32 AM
> To: Tomcat Users List 
> Subject: Re: Moved app from TomEE to Tomcat, now getting Spring errors
> failing to go through proxy for XML validation
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> David,
> 
> On 3/10/17 1:07 PM, KARR, DAVID wrote:
> > I have an app using CXF/REST/Spring/JDBC that is working pretty well
> > in TomEE (7.0.1).  I'm trying to move it to Tomcat (8.5.11) because it
> > doesn't need to be in TomEE, and I'm having problems adding additional
> > features due to aspects of TomEE.
> >
> > I'm first testing the port by running Tomcat in Eclipse.  I had
> > previously verified that the app works fine in the same environment
> > when running in TomEE.
> >
> > I moved all of my Resource and Environment entries to the Tomcat
> > context.xml file.
> >
> > When I start it up, I'm seeing errors like the following:
> > ---
> > org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> >
> >
> Line 1 in XML document from ServletContext resource
> > [/WEB-INF/applicationContext.xml] is invalid; nested exception is
> > org.xml.sax.SAXParseException; systemId:
> > http://.../ProxyWarning.html; lineNumber: 1; columnNumber: 3; The
> > markup in the document preceding the root element must be well-formed.
> > at
> > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBe
> anDefinitions(XmlBeanDefinitionReader.java:399)
> >
> >
> >
> ...
> > Caused by: org.xml.sax.SAXParseException; systemId:
> > http://.../ProxyWarning.html; lineNumber: 1; columnNumber: 3; The
> > markup in the document preceding the root element must be well-formed.
> > at
> > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXP
> arseException(ErrorHandlerWrapper.java:203)
> >
> >
> >
> - ---
> >
> > That URL that I've elided is the page we see in our enterprise when we
> > try to reach the internet without going through our proxy.
> >
> > So, this app that was working fine in TomEE now is getting this proxy
> > error when it runs in Tomcat.  Any ideas what I might be missing?
> 
> That error seems to be that the markup is bad. Are you saying that the
> markup is bad because the resource you are requesting ends up being an
> HTTP BAD REQUEST or other response rather than the XML document you are
> expecting?

The former, as it fails to get through the proxy.

> How did you have TomEE configured for a proxy before? Generally, proxies
> are configured for the whole JVM.

Curiously, I can't find any evidence that I had configured a proxy for TomEE.  
I never saw this error when running the app in TomEE.

> In Tomcat, you generally do this in one of two ways:
> 
> 1. For a standard command-line launch (e.g. testing, *NIX systems,
> etc.) create/edit CATALINA_BASE/bin/setenv.sh and add the following line
> :
> 
> CATALINA_OPTS="$CATALINA_OPTS -Dhttp.proxyHost=... ..."

That worked, thanks.

> 2. For Windows Service-based services, open the Tomcat Service Manager
> (tomcatXw.exe //ES//) and add the appropriate system properties to the
> "system properties" tab.
> 
> FYI There will be a few presentations at TomcatCon/ApacheCon in Miami in
> May. that might interest you, including a presentation by Romain on
> TomEE and Meecrowave.
> 
> http://events.linuxfoundation.org/events/apachecon-north-america/attend/
> register-

Thanks.  Hopefully those will be recorded.

RE: get NPE from NamingContextListener in app moved from TomEE to Tomcat

[KARR, DAVID]

> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Friday, March 10, 2017 9:42 AM
> To: Tomcat Users List 
> Subject: Re: get NPE from NamingContextListener in app moved from TomEE
> to Tomcat
> 
> On 10/03/2017 17:39, KARR, DAVID wrote:
> > I have a CXF/REST/Spring/JDBC app running in TomEE (7.0.1).  I've
> decided to try to move it to Tomcat (8.5.11) because of some classloader
> conflicts (CXF classes) I'm now seeing in trying to add some new code to
> the app.
> >
> > Initially, I'm just running the server in Eclipse.
> >
> > When I add the apps to Tomcat and start it up, without changing the
> server conf, it starts up, but it fails to find my JNDI resources
> (obviously).
> >
> > I have the following DataSource definition in the "tomee.xml" file in
> TomEE, which is working fine:
> > --
> >   
> > testOnBorrow = true
> > testOnReturn = true
> > testWhileIdle = true
> > logValidationErrors = true
> > validationQuery = select 1 from dual
> > JdbcDriver = oracle.jdbc.OracleDriver
> > InitialSize = 2
> > MaxActive = 2
> > MinIdle = 2
> > MaxIdle = 2
> > JdbcUrl = ...
> > UserName = ...
> > Password = ...
> >   
> > -
> >
> > When I attempt to add this Resource definition to the "context.xml"
> file in Tomcat 8.5.11, I see errors like the following, and Tomcat fails
> to start up:
> > 
> > Caused by: java.lang.NullPointerException
> > at java.util.StringTokenizer.(StringTokenizer.java:199)
> > at java.util.StringTokenizer.(StringTokenizer.java:221)
> > at
> org.apache.catalina.core.NamingContextListener.createSubcontexts(NamingC
> ontextListener.java:1300)
> > at
> org.apache.catalina.core.NamingContextListener.addResource(NamingContext
> Listener.java:1081)
> > at
> org.apache.catalina.core.NamingContextListener.createNamingContext(Namin
> gContextListener.java:661)
> > at
> org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingCont
> extListener.java:249)
> > -
> >
> > I've tried converting the Resource definition to look more "normal",
> but nothing I've tried makes any difference.  This is the current state
> of it:
> > --
> >  auth="Container"
> 
> name="jdbc/tst36" not id=...

That was it, thanks.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Moved app from TomEE to Tomcat, now getting Spring errors failing to go through proxy for XML validation

[KARR, DAVID]

I have an app using CXF/REST/Spring/JDBC that is working pretty well in TomEE 
(7.0.1).  I'm trying to move it to Tomcat (8.5.11) because it doesn't need to 
be in TomEE, and I'm having problems adding additional features due to aspects 
of TomEE.

I'm first testing the port by running Tomcat in Eclipse.  I had previously 
verified that the app works fine in the same environment when running in TomEE.

I moved all of my Resource and Environment entries to the Tomcat context.xml 
file.

When I start it up, I'm seeing errors like the following:
---
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 
in XML document from ServletContext resource [/WEB-INF/applicationContext.xml] 
is invalid; nested exception is org.xml.sax.SAXParseException; systemId: 
http://.../ProxyWarning.html; lineNumber: 1; columnNumber: 3; The markup in the 
document preceding the root element must be well-formed.
at 
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399)
...
Caused by: org.xml.sax.SAXParseException; systemId: 
http://.../ProxyWarning.html; lineNumber: 1; columnNumber: 3; The markup in the 
document preceding the root element must be well-formed.
at 
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
---

That URL that I've elided is the page we see in our enterprise when we try to 
reach the internet without going through our proxy.

So, this app that was working fine in TomEE now is getting this proxy error 
when it runs in Tomcat.  Any ideas what I might be missing?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

get NPE from NamingContextListener in app moved from TomEE to Tomcat

[KARR, DAVID]

I have a CXF/REST/Spring/JDBC app running in TomEE (7.0.1).  I've decided to 
try to move it to Tomcat (8.5.11) because of some classloader conflicts (CXF 
classes) I'm now seeing in trying to add some new code to the app.

Initially, I'm just running the server in Eclipse.

When I add the apps to Tomcat and start it up, without changing the server 
conf, it starts up, but it fails to find my JNDI resources (obviously).

I have the following DataSource definition in the "tomee.xml" file in TomEE, 
which is working fine:
--
  
testOnBorrow = true
testOnReturn = true
testWhileIdle = true
logValidationErrors = true
validationQuery = select 1 from dual
JdbcDriver = oracle.jdbc.OracleDriver
InitialSize = 2
MaxActive = 2
MinIdle = 2
MaxIdle = 2 
JdbcUrl = ...
UserName = ...
Password = ...
  
-

When I attempt to add this Resource definition to the "context.xml" file in 
Tomcat 8.5.11, I see errors like the following, and Tomcat fails to start up:

Caused by: java.lang.NullPointerException
at java.util.StringTokenizer.(StringTokenizer.java:199)
at java.util.StringTokenizer.(StringTokenizer.java:221)
at 
org.apache.catalina.core.NamingContextListener.createSubcontexts(NamingContextListener.java:1300)
at 
org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1081)
at 
org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:661)
at 
org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:249)
-

I've tried converting the Resource definition to look more "normal", but 
nothing I've tried makes any difference.  This is the current state of it:
--


--

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Required changes to move an app from TomEE 7.0.1 to Tomcat 8.5.11

[KARR, DAVID]

I'm currently running a somewhat simple CXF/REST/Spring app in TomEE 7.0.1.  It 
uses the CXF libraries in WEB-INF/lib, not in the container.  It uses a couple 
of Environment strings, and some DataSource resources, all of which it gets 
from JNDI.

I'm considering moving this app from TomEE to Tomcat, because as far as I can 
see, I don't need anything that TomEE provides over Tomcat, and I'm also 
running into classloader conflicts now that I've added more code using CXF 
pieces that I haven't used before.  I'm pursuing those issues with the TomEE 
team (ok, Romain), as I'd like to get these issues resolved now that I've run 
into them, but I have to consider alternative strategies if it's going to take 
too long to get them resolved.

If I attempt to port this to Tomcat, I'm guessing all of the required changes 
will be in "conf".  It appears that in TomEE, I define DataSource Resources in 
"tomee.xml" and environment strings (and other things) in "Context.xml", but in 
Tomcat I define all of those in "Context.xml".  I assume that's correct?

I also need to understand if there are any syntax differences between the 
"Resource" entries I define in "tomee.xml" and the similar ones I define in 
"Context.xml" in Tomcat.

For instance, in my DataSource Resources in TomEE, I set the "type" to 
"DataSource", although I see in the Tomcat example it uses 
"javax.sql.DataSource".  Will both of these work in Tomcat?  In my current app, 
I also define the other DataSource properties in the "body" of the "Resource" 
element, like "key = value", one on each line.  In the Tomcat example, they are 
set as traditional XML attributes.  I would also guess that both of these 
strategies would work in Tomcat, correct?

I also have to determine what the required "JNDI prefix" is for Tomcat.  
Presently, in my TomEE app, I don't need a prefix for the environment entries, 
but I need to prefix my datasource JNDI names with "openejb:Resource/".  What 
will I need to prefix my JNDI references with in Tomcat?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Practical to write code in webapp that can return metadata from current access log?

[KARR, DAVID]

I'm considering writing a secondary diagnostics service for my CXF REST app 
running in Tomcat (TomEE) that can return some information about the number of 
calls to the main service in a particular time period.  Is there an API I can 
use in Java that will give me access to the current access log information?  I 
know that I could always hack something together with a fully qualified path to 
the file and manual code to parse it, but it seems like this is something that 
would have been done before, so perhaps there's an easier to use API for this.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Any way to configure a javascript/html war with deployment-time properties?

[KARR, DAVID]

I'm using TomEE, but I think this question is Tomcat-specific, if there's any 
solution at all.

I have a WAR that is a "pure" webapp, with only javascript, css, and html.  The 
javascript connects to a REST service at a defined host:port.  The host:port is 
currently hardcoded in a javascript variable.

I really need to be able to configure this host:port at deployment time.  I 
know how to do this sort of thing with Java apps, but I'm at a loss to see how 
to do this conveniently for a non-Java war.

How can I rearrange this solution so that I can change the host:port the WAR 
uses at deployment time?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Define datasource, reference JDBC driver, and see init in console

[KARR, DAVID]

I'm attempting to use Tomcat(tomee) to run a REST service that will return some 
data from some SQL queries (Oracle).  I've installed Tomee 7.0.1, which uses 
Tomcat 8.5.3.

The JDBC driver is available from a private enterprise maven repo.  I'd prefer 
to get it from there, as opposed to storing it locally.  I noticed at 
http://tomee.apache.org/configuring-datasources.html , there is the possible 
notation of "mvn:g:a:v" for the "classpath" attribute.  However, I don't see 
any way to configure the Maven repositories this will reference.  How do I tell 
it to look in a particular repo for this?

My Resource definition in "conf/tomee.xml" looks something like this:
---
  


Does this look correct?  I find the Tomcat docs confusing, with respect to the 
required syntax for this.  It's not clear whether a pure XML syntax is 
required, or a mixed XML/property syntax.

I haven't written the code to reference this datasource yet, but if I start the 
instance, should I see any default output that will show Tomcat connecting to 
this datasource?  If it doesn't show this by default, is there a way to turn 
this on?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Is error with Bamboo Sonar plugin because of Tomcat 6 instead of Tomcat 7?

[KARR, DAVID]

> -Original Message-
> From: David kerber [mailto:dcker...@verizon.net]
> Sent: Wednesday, January 16, 2013 11:42 AM
> To: Tomcat Users List
> Subject: Re: Is error with Bamboo Sonar plugin because of Tomcat 6 instead of
> Tomcat 7?
> 
> On 1/16/2013 2:38 PM, KARR, DAVID wrote:
> >> -Original Message-
> >> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> >> Sent: Wednesday, January 16, 2013 10:58 AM
> >> To: Tomcat Users List
> >> Subject: RE: Is error with Bamboo Sonar plugin because of Tomcat 6 instead
> of
> >> Tomcat 7?
> >>
> >>> From: KARR, DAVID [mailto:dk0...@att.com]
> >>> Subject: RE: Is error with Bamboo Sonar plugin because of
> >>> Tomcat 6 instead of Tomcat 7?
> >>
> >>>>> We're running Bamboo 3.4.3 in Tomcat 6.0.20.  It mostly apparently
> >> works
> >>>>> fine, but yesterday I tried to get the Bamboo Sonar plugin working,
> >>>>
> >>>> Did you leave out "in Tomcat 7" at the end there?
> >>
> >>> I don't know what you mean.  Our Bamboo is running in Tomcat 6.  I'm
> >> wondering
> >>> whether the error is due to a change in the Tomcat API between Tomcat 6
> and
> >> 7.
> >>
> >> You're not explaining your problem.  First you say you have Bamboo running
> in
> >> Tomcat 6.0.20, then you say it's not running, you're getting an exception.
> >> (Remember that very few - if any - people on this list have any idea what
> >> Bamboo is, let alone how it works with Tomcat.)  Since your subject line
> >> refers to Tomcat 7, I assumed (bad idea) that you were having problems
> >> migrating to Tomcat 7.  So what's really going on (be precise)?
> >
> > We're running Bamboo with Tomcat 6.  We're trying to add the Sonar plugin.
> When we try to configure it, we get this exception when it tries to call that
> specific Tomcat API.  The theory that I'm exploring is that the plugin
> requires Bamboo to be running with Tomcat 7, not Tomcat 6.  I don't want to
> try moving to Tomcat 7 unless we have some assurance that that will resolve
> the problem.
> 
> Why don't you check with the Bamboo people?  As Chuck said, there
> probably aren't very many people here who know anything about Bamboo.  I
> certainly have never heard of it.

That was the first thing I did.  Bamboo is a commercial product, and they don't 
support the Sonar plugin.  I'm also asking the group that built the Sonar 
plugin, but replies to that are slow.  I also asked on the Sonar mailing list.  
Checking with tomcat-users was only the last step.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Is error with Bamboo Sonar plugin because of Tomcat 6 instead of Tomcat 7?

[KARR, DAVID]

> -Original Message-
> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> Sent: Wednesday, January 16, 2013 10:58 AM
> To: Tomcat Users List
> Subject: RE: Is error with Bamboo Sonar plugin because of Tomcat 6 instead of
> Tomcat 7?
> 
> > From: KARR, DAVID [mailto:dk0...@att.com]
> > Subject: RE: Is error with Bamboo Sonar plugin because of
> > Tomcat 6 instead of Tomcat 7?
> 
> > > > We're running Bamboo 3.4.3 in Tomcat 6.0.20.  It mostly apparently
> works
> > > > fine, but yesterday I tried to get the Bamboo Sonar plugin working,
> > >
> > > Did you leave out "in Tomcat 7" at the end there?
> 
> > I don't know what you mean.  Our Bamboo is running in Tomcat 6.  I'm
> wondering
> > whether the error is due to a change in the Tomcat API between Tomcat 6 and
> 7.
> 
> You're not explaining your problem.  First you say you have Bamboo running in
> Tomcat 6.0.20, then you say it's not running, you're getting an exception.
> (Remember that very few - if any - people on this list have any idea what
> Bamboo is, let alone how it works with Tomcat.)  Since your subject line
> refers to Tomcat 7, I assumed (bad idea) that you were having problems
> migrating to Tomcat 7.  So what's really going on (be precise)?

We're running Bamboo with Tomcat 6.  We're trying to add the Sonar plugin.  
When we try to configure it, we get this exception when it tries to call that 
specific Tomcat API.  The theory that I'm exploring is that the plugin requires 
Bamboo to be running with Tomcat 7, not Tomcat 6.  I don't want to try moving 
to Tomcat 7 unless we have some assurance that that will resolve the problem.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Is error with Bamboo Sonar plugin because of Tomcat 6 instead of Tomcat 7?

[KARR, DAVID]

> -Original Message-
> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> Sent: Wednesday, January 16, 2013 10:10 AM
> To: Tomcat Users List
> Subject: RE: Is error with Bamboo Sonar plugin because of Tomcat 6 instead of
> Tomcat 7?
> 
> > From: KARR, DAVID [mailto:dk0...@att.com]
> > Subject: Is error with Bamboo Sonar plugin because of Tomcat 6 instead of
> Tomcat 7?
> 
> > We're running Bamboo 3.4.3 in Tomcat 6.0.20.  It mostly apparently works
> > fine, but yesterday I tried to get the Bamboo Sonar plugin working,
> 
> Did you leave out "in Tomcat 7" at the end there?

I don't know what you mean.  Our Bamboo is running in Tomcat 6.  I'm wondering 
whether the error is due to a change in the Tomcat API between Tomcat 6 and 7.  
I might ask someone here to try moving to Tomcat 7, but that's potentially a 
big change, and I want to be sure it will make a difference before I ask for 
that.

> > I notice that it's trying to access something in the
> "org.apache.tomcat.dbcp.*"
> > package.  I'm pursuing this on the Sonar users list, but I'm wondering
> whether
> > this might be an issue with Tomcat 6 vs. Tomcat 7.
> 
> I haven't looked at the API differences in that package between Tomcat 6 and
> 7, but changing the APIs for internal packages between major revisions is
> quite common.  Likely Bamboo will need a separate plugin for each major
> Tomcat level, since there's no guarantee of upward compatibility for internal
> interfaces.
> 
>  - Chuck
> 
> 
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Is error with Bamboo Sonar plugin because of Tomcat 6 instead of Tomcat 7?

[KARR, DAVID]

We're running Bamboo 3.4.3 in Tomcat 6.0.20.  It mostly apparently works fine, 
but yesterday I tried to get the Bamboo Sonar plugin working, and when I tried 
to add a server connection, I got the following stack trace:

Caused by: java.lang.IllegalAccessException: Class 
com.atlassian.activeobjects.bamboo.ConnectionHandler can not access a member of 
class org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper 
with modifiers "public"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
at java.lang.reflect.Method.invoke(Method.java:588)
at 
com.atlassian.activeobjects.bamboo.ConnectionHandler.delegate(ConnectionHandler.java:43)
at 
com.atlassian.activeobjects.bamboo.ConnectionHandler.invoke(ConnectionHandler.java:38)
... 239 more

I notice that it's trying to access something in the "org.apache.tomcat.dbcp.*" 
package.  I'm pursuing this on the Sonar users list, but I'm wondering whether 
this might be an issue with Tomcat 6 vs. Tomcat 7.  Is this symptom familiar to 
anyone?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Any way to make tomcat send the "disable caching" headers on all responses?

[Karr, David]

Just in case someone wants more info about this, I just noticed (from a
Firebug presentation) that I can interactively turn off the
"browser.cache.disk.enable" and "network.http.use-cache" flags in
"about:config" which will probably make this a little easier to deal
with.

> -----Original Message-
> From: Karr, David 
> Sent: Sunday, March 16, 2008 10:27 AM
> To: Tomcat Users List
> Subject: Any way to make tomcat send the "disable caching" 
> headers on all responses?
> 
> When I'm debugging javavascript code, it's really annoying 
> when Firefox caches the javascript file (even when I've 
> modified it).  I'm familiar with the headers for disabling 
> caching, but it's a little more annoying to emit those 
> headers on javascript files.  Unless I'm missing something, 
> is there an easy way to make Tomcat send the disable cache 
> headers for all responses, perhaps for a single application?

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Any way to make tomcat send the "disable caching" headers on all responses?

[Karr, David]

When I'm debugging javavascript code, it's really annoying when Firefox
caches the javascript file (even when I've modified it).  I'm familiar
with the headers for disabling caching, but it's a little more annoying
to emit those headers on javascript files.  Unless I'm missing
something, is there an easy way to make Tomcat send the disable cache
headers for all responses, perhaps for a single application?

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Sometimes have to completely remove app from webapps for it to update

[Karr, David]

Tomcat 6.0.14, JDK 1.5.0_06, WinXPSP2.

I sometimes run Tomcat from "startup.bat", and I sometimes run it from
Eclipse.  Several times I've seen a situation where I will change my app
and restart the server, and my test indicates that my change didn't get
deployed.  This isn't an HTML caching issue, as the pieces I change are
all on the server side (like my "struts.xml" file).  I find that I end
up having to remove the war and exploded dir from the webapps dir, and
then copy my war back in, and then restart Tomcat.  At that point, it
sees the changed functionality.  I've seen similar behavior while
running Tomcat in Eclipse, but I didn't try doing the manual removal of
the app from the webapps dir.  I've tried cleaning the project,
restarting the server, removing and readding the project from the
server, all to no avail.

The particular "persistent" behavior I was seeing was that I had a
Struts2 action that referenced an Action class, and then I tried
removing the "class" attribute and redeploying.  After redeploying, it
was still calling the method in the Action class, even though it wasn't
referenced anymore.

I ended up just creating another action element with a slightly
different name and then using that.  That behaved as I expected.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Problems installing Tomcat 6 along existing Tomcat 5, and JAVA_HOME points to 1.4.2

[Karr, David]

That worked fine, thanks. I had assumed it would be that simple, but the
response I was getting here made me think it was more complicated than
that. 

> -Original Message-
> From: David Smith [mailto:[EMAIL PROTECTED] 
> Sent: Monday, January 28, 2008 7:07 AM
> To: Tomcat Users List
> Subject: Re: Problems installing Tomcat 6 along existing 
> Tomcat 5, and JAVA_HOME points to 1.4.2
> 
> You could edit the startup/shutdown scripts to locally define 
> a JAVA_HOME or JRE_HOME environment variable for the tomcat 
> instance only.  It's not pretty, but it works :-).
> 
> --David
> 
> Karr, David wrote:
> 
> >>-Original Message-
> >>From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
> >>Sent: Monday, January 28, 2008 4:56 AM
> >>To: Tomcat Users List
> >>Subject: RE: Problems installing Tomcat 6 along existing 
> Tomcat 5, and 
> >>JAVA_HOME points to 1.4.2
> >>
> >>
> >>
> >>>From: Karr, David [mailto:[EMAIL PROTECTED]
> >>>Subject: RE: Problems installing Tomcat 6 along existing
> >>>  
> >>>
> >>Tomcat 5, and
> >>
> >>
> >>>JAVA_HOME points to 1.4.2
> >>>
> >>>When I tried to run "tomcat6.exe" from the Tomcat6 zip file
> >>>  
> >>>
> >>Why are you trying to run tomcat6.exe?  That's for use *only* when 
> >>Tomcat is installed as a service, which you claim you don't want.
> >>
> >>
> >>
> >>>So, how do I configure Tomcat 6 (and Tomcat 5, I guess) to use an 
> >>>alternative JVM besides JAVA_HOME?
> >>>  
> >>>
> >>You can't.  The whole point of JAVA_HOME (or JRE_HOME) is to tell 
> >>Tomcat where to find the desired JVM installation.  Fix your 
> >>environment variable.
> >>
> >>
> >
> >I cannot.  This is just research.  My current work requires 
> JDK 1.4.2.
> >I find it hard to believe Tomcat is unable to be configured to allow 
> >this.
> >
> >-
> >To start a new topic, e-mail: users@tomcat.apache.org To 
> unsubscribe, 
> >e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >  
> >
> 
> 
> -
> To start a new topic, e-mail: users@tomcat.apache.org To 
> unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Problems installing Tomcat 6 along existing Tomcat 5, and JAVA_HOME points to 1.4.2

[Karr, David]

> -Original Message-
> From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] 
> Sent: Monday, January 28, 2008 4:56 AM
> To: Tomcat Users List
> Subject: RE: Problems installing Tomcat 6 along existing 
> Tomcat 5, and JAVA_HOME points to 1.4.2
> 
> > From: Karr, David [mailto:[EMAIL PROTECTED]
> > Subject: RE: Problems installing Tomcat 6 along existing 
> Tomcat 5, and 
> > JAVA_HOME points to 1.4.2
> > 
> > When I tried to run "tomcat6.exe" from the Tomcat6 zip file
> 
> Why are you trying to run tomcat6.exe?  That's for use *only* 
> when Tomcat is installed as a service, which you claim you don't want.
> 
> > So, how do I configure Tomcat 6 (and Tomcat 5, I guess) to use an 
> > alternative JVM besides JAVA_HOME?
> 
> You can't.  The whole point of JAVA_HOME (or JRE_HOME) is to 
> tell Tomcat where to find the desired JVM installation.  Fix 
> your environment variable.

I cannot.  This is just research.  My current work requires JDK 1.4.2.
I find it hard to believe Tomcat is unable to be configured to allow
this.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Problems installing Tomcat 6 along existing Tomcat 5, and JAVA_HOME points to 1.4.2

[Karr, David]

Ok, so I redownloaded both Tomcat 5 and Tomcat 6.  Tomcat 5 was working
before, even though I had installed it from the service installer (and
never using it as a service).  After reinstalling it from the zip, it is
still working just fine.  When I tried to run "tomcat6.exe" from the
Tomcat6 zip file, it failed exactly the same way the service installer
did:

[2008-01-27 19:51:03] [420  prunsrv.c] [error]
The system cannot find the file specified.
[2008-01-27 19:51:03] [1327 prunsrv.c] [error]
Load configuration failed

There are NO log files in the "logs" directory.

When I try to run "startup.bat", it also appears to fail pretty quickly,
but doing this makes it clear it's trying to use my JDK 1.4.2 JAVA_HOME,
so perhaps that's why "tomcat6.exe" failed.

So, how do I configure Tomcat 6 (and Tomcat 5, I guess) to use an
alternative JVM besides JAVA_HOME?

> -Original Message-
> From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, January 27, 2008 5:29 PM
> To: Tomcat Users List
> Subject: RE: Problems installing Tomcat 6 along existing 
> Tomcat 5, and JAVA_HOME points to 1.4.2
> 
> > From: Karr, David [mailto:[EMAIL PROTECTED]
> > Subject: Problems installing Tomcat 6 along existing Tomcat 5, and 
> > JAVA_HOME points to 1.4.2
> > 
> > This is ironic, as I have no intention of using the Windows 
> service, I 
> > just used the installed because it's more convenient than the zip 
> > file.
> 
> ??? How are you starting Tomcat, if you used the .exe 
> download?  It can only be used to run Tomcat as a service, 
> unless you conjure up your own startup/shutdown scripts.
> 
> You really do need to download the .zip versions, since they 
> come with the proper scripts, and only install Tomcat as a 
> service if you run the appropriate script.  If you do choose 
> to run the service installation script, you may then specify 
> whatever display name you want for the service.
> 
>  - Chuck
> 
> 
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE 
> PROPRIETARY MATERIAL and is thus for use only by the intended 
> recipient. If you received this in error, please contact the 
> sender and delete the e-mail and its attachments from all computers.
> 
> -
> To start a new topic, e-mail: users@tomcat.apache.org To 
> unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problems installing Tomcat 6 along existing Tomcat 5, and JAVA_HOME points to 1.4.2

[Karr, David]

Due to constraints on my current work, my JAVA_HOME points to a JDK
1.4.2 distro.  When I installed Tomcat 5.5.25, I pointed it to a Java 5
JDK that I have installed.  It appears to be working relatively well.

I wanted to try installing Tomcat 6, to take a look at JSF 1.2.  When I
installed it, I pointed it to the same JDK that I'm using for Tomcat 5.
When I start it, it fails almost immediately.  I believe it's failing
because the Tomcat 5 installation used the same display name for the
service that Tomcat 6 tries to use.  This is ironic, as I have no
intention of using the Windows service, I just used the installed
because it's more convenient than the zip file.

The console output is:

[2008-01-27 17:13:10] [420  prunsrv.c] [error]
The system cannot find the file specified.
[2008-01-27 17:13:10] [1327 prunsrv.c] [error]
Load configuration failed

The "logs" directory only has "jakarta_service_20080127.log", which has:

[2008-01-27 17:01:37] [info] Procrun (2.0.3.0) started
[2008-01-27 17:01:37] [info] Service Tomcat6 name Apache Tomcat
[2008-01-27 17:01:37] [420  service.c] [error] The name is already in
use as either a service name or a service display name. [2008-01-27
17:01:37] [606  prunsrv.c] [error] Failed installing Tomcat6 service
[2008-01-27 17:01:37] [info] Procrun finished.
[2008-01-27 17:01:42] [info] Procrun (2.0.3.0) started
[2008-01-27 17:01:42] [info] Service Tomcat6 name Apache Tomcat
[2008-01-27 17:01:42] [420  service.c] [error] The name is already in
use as either a service name or a service display name. [2008-01-27
17:01:42] [606  prunsrv.c] [error] Failed installing Tomcat6 service
[2008-01-27 17:01:42] [info] Procrun finished.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat blew up (stack overflow error) deploying an app with MyFaces/RichFaces

[Karr, David]

Tomcat 5.5.25, JDK 1.5.0_11, WinXPSP2.

I copied a war file to webapps and it auto-deployed it, but it failed
autodeploy, which I expected.  I then copied in several jars into the
exploded WEB-INF/lib directory.  At that point, in a fraction of a
second the log file was filled up with a stack overflow error.

The original WAR file uses RichFaces, but it was originally deployed to
WebLogic, which implicitly uses its own JSF implementation, so the JSF
implementation isn't in WEB-INF/lib.  When I copied it into Tomcat's
webapps dir, it failed because of the missing JSF implementation.  I
then copied in all the jars from the MyFaces 1.1.5 distro, as an attempt
to provide the JSF implementation.  That's when it blew up.

In the log file, there were two exceptions.  The first one had a
"normal" stack trace, and the second one was the big one.  I'll paste
some of both of them here.  For the second one, the two stack entries
there repeated forever.

SEVERE: Exception starting filter richfaces
java.lang.NoClassDefFoundError: javax/faces/FacesException
at org.ajax4jsf.webapp.BaseFilter.init(BaseFilter.java:146)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFi
lterConfig.java:221)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(Applicatio
nFilterConfig.java:302)
at
org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilte
rConfig.java:78)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.jav
a:3635)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4222
)
  ... More

SEVERE: Servlet.service() for servlet Faces Servlet threw exception
java.lang.StackOverflowError
at
javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletReque
stWrapper.java:216)
at
org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHt
tpRequest.java:545)
at
javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletReque
stWrapper.java:216)
at
org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHt
tpRequest.java:545)
  ... More

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat 5.5 won't start up anymore after adding/removing webapps

[Karr, David]

There weren't any files corresponding to those apps in the conf tree.  However, 
when I just tried grepping for that class name in the entire tree, I found it 
in the following files:

 ./work/Catalina/localhost/jsp-examples/tldCache.ser
 ./work/Catalina/localhost/servlets-examples/tldCache.ser
 ./work/Catalina/localhost/tomcat-docs/tldCache.ser
 ./work/Catalina/localhost/webdav/tldCache.ser
 ./work/Catalina/localhost/_/tldCache.ser 

> -Original Message-
> From: david delbecq [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, January 22, 2008 10:08 AM
> To: Tomcat Users List
> Subject: Re: Tomcat 5.5 won't start up anymore after 
> adding/removing webapps
> 
> To manually undeploy a webapp, when tomcat is stopped, remove 
> webapps/* remove work/Catalina/localhost/
> remove conf/Catalina/localhost/.xml
> 
> Karr, David a écrit :
> > I installed v5.5.25.  I installed the "admin" app (although the 
> > instructions on doing this seem uncertain).  I used it for a few 
> > hours, deploying and undeploying some experimental apps 
> using MyFaces 
> > and RichFaces.  Now, for some reason, I'm finding that Tomcat won't 
> > start up at all, and I've undeployed all the apps (except the admin 
> > app) that I had deployed.  I first only removed the war and 
> exploded 
> > dir from the webapps dir, but then I tried removing them from the 
> > "work/Catalina/localhost" directory also.
> >
> > The error I'm seeing in the localhost log is this:
> >
> > java.lang.ClassNotFoundException:
> > org.apache.myfaces.webapp.StartupServletContextListener
> > at
> > 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoad
> > er
> > java:1362)
> > at
> > 
> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoad
> > er
> > java:1208)
> > at
> > 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext
> > .j
> > ava:3712)
> > at
> > 
> org.apache.catalina.core.StandardContext.start(StandardContext.java:42
> > 16
> > )
> >
> > Obviously, since something is still trying to reference MyFaces, 
> > there's some remnant of one of my deployed apps lying around in a 
> > place that I'm not aware of.
> >
> > 
> -
> > To start a new topic, e-mail: users@tomcat.apache.org To 
> unsubscribe, 
> > e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >   
> 
> 
> -
> To start a new topic, e-mail: users@tomcat.apache.org To 
> unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 5.5 won't start up anymore after adding/removing webapps

[Karr, David]

I installed v5.5.25.  I installed the "admin" app (although the
instructions on doing this seem uncertain).  I used it for a few hours,
deploying and undeploying some experimental apps using MyFaces and
RichFaces.  Now, for some reason, I'm finding that Tomcat won't start up
at all, and I've undeployed all the apps (except the admin app) that I
had deployed.  I first only removed the war and exploded dir from the
webapps dir, but then I tried removing them from the
"work/Catalina/localhost" directory also.

The error I'm seeing in the localhost log is this:

java.lang.ClassNotFoundException:
org.apache.myfaces.webapp.StartupServletContextListener
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader
.java:1362)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader
.java:1208)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.j
ava:3712)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4216
)

Obviously, since something is still trying to reference MyFaces, there's
some remnant of one of my deployed apps lying around in a place that I'm
not aware of.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Need help diagnosing 500 error in 5.0.28

[Karr, David]

I'm trying to deploy a simple SOAP service handler (written by someone
else) to an ancient version of Tomcat (5.0.28).  This app is also
running on a production server with the same Tomcat version.

I have a command-line tool that I use to send a test message to the
server.  When I send it, it says that it got a 500 error.  There is no
indication in the Tomcat console or any of its logs of any error, or
even that a request was received.

I set a breakpoint in
org.apache.coyote.http11.Http11Processor.process(InputStream,OutputStrea
m), and when I ran my request, it did hit this breakpoint.  I stepped
through it, but I didn't see anything out of the ordinary.  I also set a
breakpoint in my service handler, and it does NOT get there.

What can I do to get more information about what's going wrong here?  Is
there another place that would be useful to set a breakpoint at?

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]