Re: Strange behavior of Tooltip when used with JComponent with in Applet

2005-08-11 Thread Brian Bonner

This doesn't sound like a tomcat question--or am I missing something?

Brian



[EMAIL PROTECTED] wrote:


I have a problem with a JComboBox placed in an applet which is having a
ToolTip text set on it. While moving the mouse over the ComboBox I am
getting the following error stack in the Java Console. 






java.lang.Error: Destination component not connected to component tree
hierarchy

at javax.swing.SwingUtilities.convertPoint(Unknown Source)

at javax.swing.ToolTipManager.mouseExited(Unknown Source)

at java.awt.AWTEventMulticaster.mouseExited(Unknown Source)

at java.awt.Component.processMouseEvent(Unknown Source)

at java.awt.Component.processEvent(Unknown Source)

at java.awt.Container.processEvent(Unknown Source)

at java.awt.Component.dispatchEventImpl(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)

at java.awt.LightweightDispatcher.trackMouseEnterExit(Unknown Source)

at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)

at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)

at java.awt.Container.dispatchEventImpl(Unknown Source)

at java.awt.Component.dispatchEvent(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at

java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source



This is not happening regularly. Is it a bug with Java?




JDK used: J2SDK 1.4.2_02

Servlet Engine: Tomcat 4.1.29

Web Server:  Apache 2.0.43




Please help me out with your suggestions / comments.




Thanks in Advance.

Ajith














Confidentiality Notice


The information contained in this electronic message and any attachments to 
this message are intended
for the exclusive use of the addressee(s) and may contain confidential or 
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL 
PROTECTED] immediately
and destroy all copies of this message and any attachments.
 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange redirects with Apache 2.0, mod_jk and Tomcat 5.5

2005-08-10 Thread Sven Köhler
 often, Firefox tellst me, that the redirect limit is execeeded when
 surfing one of my pages.
 
 So i tried wget, and look at the result:
 
 [strange result]
 
 That's no joke! (www.mysite.com is a replacement for the real-website).
 Look at the redirects! he's even jumping to /html/index.jsp - and for
 some reason, tomcat redirects back to / - and than back again to
 /html/index.jsp. That absolutly makes no sense! /index.jsp contains a
 simple redirect - and /html/index.jsp is a simple page.

Well, i recompiled apache, but didn't recompile mod_jk - well, the
result was the one i described. After recompiling mod_jk, everything is
fine again!


signature.asc
Description: OpenPGP digital signature


Re: strange cache behavior in Tomcat 5.5.9?

2005-08-01 Thread Seth Ladd

Gabriel Belingueres wrote:

Hi,
In my JSP pages I put the following tags to avoid the browser cache the pages.

head
meta http-equiv=Expires content=0 /
meta http-equiv=Pragma content=no-cache /
meta http-equiv=Cache-Control content=no-cache /


I wouldn't trust this way.  I would always use the below method for 
manipulating any cache control or general HTTP headers.




%
response.setHeader(Cache-Control,no-store);
response.setHeader(Pragma,no-cache);
response.setDateHeader (Expires, 0);
%


This is the way to do it.  Also, it's backwares compatible.  This sends 
actual HTTP headers back to the client in the response.


Seth

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange error

2005-05-11 Thread Mark Thomas
You need to look at line 125 of WebApplicationListener in the 
org.objectstyle.cayenne.conf package and see which object might be null 
that you have assumed isn't.

Mark
Fredrik Liden wrote:
Does anyone have any idea what this error means?
I'm using jdk 1.5, tomcat 5.5.9 and intellij.
Thanks!
Connected to server
ERROR [/]: Session event listener threw exception
java.lang.NullPointerException
 at
org.objectstyle.cayenne.conf.WebApplicationListener.sessionCreated(WebAp
plicationListener.java:125)
 at
org.apache.catalina.session.StandardSession.tellNew(StandardSession.java
:379)
 at
org.apache.catalina.session.StandardSession.setId(StandardSession.java:3
51)
 at
org.apache.catalina.session.ManagerBase.createSession(ManagerBase.java:7
87)
 at
org.apache.catalina.session.StandardManager.createSession(StandardManage
r.java:290)
 at
org.apache.catalina.connector.Request.doGetSession(Request.java:2206)
 at org.apache.catalina.connector.Request.getSession(Request.java:2017)
 at
org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.jav
a:822)
 at
org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.jav
a:833)
 at
org.apache.jasper.runtime.PageContextImpl._initialize(PageContextImpl.ja
va:148)
 at
org.apache.jasper.runtime.PageContextImpl.initialize(PageContextImpl.jav
a:123)
 at
org.apache.jasper.runtime.JspFactoryImpl.internalGetPageContext(JspFacto
ryImpl.java:104)
 at
org.apache.jasper.runtime.JspFactoryImpl.getPageContext(JspFactoryImpl.j
ava:61)
 at org.apache.jsp.Login_jsp._jspService(org.apache.jsp.Login_jsp:35)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.ja
va:322)
 at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:252)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
 at irf.filters.FrontFilter.doFilter(FrontFilter.java:51)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:202)
 at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:173)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:213)
 at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:178)
 at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:126)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:107)
 at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:1
48)
 at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:85
6)
 at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:744)
 at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint
.java:527)
 at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollow
erWorkerThread.java:80)
 at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:684)
 at java.lang.Thread.run(Thread.java:595)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: strange exception - need advise

2005-05-05 Thread Igor
Hello!

I think, that when exception occurs, something has already been written to
output stream. Tomcat tries to redirect to error page, but it cannot do it,
because something was written.

Thank you,
Igor

- Original Message -
From: Guy Katz [EMAIL PROTECTED]
To: Tomcat Users List tomcat-user@jakarta.apache.org
Sent: Sunday, May 01, 2005 8:44 AM
Subject: strange exception - need advise


hi;
i keep getting this exception below (tomcat 5.0.30).
can anybody shed some light on this?
my error page configuration is as follows:
   error-page
exception-typejava.lang.Exception/exception-type
location/faces/error.jsp/location
   /error-page
error-page
error-code404/error-code
location/faces/error.jsp/location
/error-page
!-- Forbidden --
error-page
error-code403/error-code
location/faces/error.jsp/location
/error-page
error-page
error-code500/error-code
location/faces/error.jsp/location
/error-page
thanks in advance.

[EMAIL PROTECTED]: Exception Processing
ErrorPage[exceptionType=java.lang.Exception, location=/faces/error.jsp]
java.lang.IllegalStateException
at org.apache.coyote.Response.reset(Response.java:296)
at org.apache.coyote.tomcat5.CoyoteResponse.reset(CoyoteResponse.java:646)
at org.apache.coyote.tomcat5.CoyoteResponse.reset(CoyoteResponse.java:912)
at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:389
)
at
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:
225)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
at java.lang.Thread.run(Thread.java:534)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: strange exception - need advise

2005-05-05 Thread Guy Katz
thanks.
so what should i look for to solve this?

-Original Message-
From: Igor [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 05, 2005 11:41 AM
To: tomcat-user@jakarta.apache.org
Subject: Re: strange exception - need advise


Hello!

I think, that when exception occurs, something has already been written to
output stream. Tomcat tries to redirect to error page, but it cannot do it,
because something was written.

Thank you,
Igor

- Original Message -
From: Guy Katz [EMAIL PROTECTED]
To: Tomcat Users List tomcat-user@jakarta.apache.org
Sent: Sunday, May 01, 2005 8:44 AM
Subject: strange exception - need advise


hi;
i keep getting this exception below (tomcat 5.0.30).
can anybody shed some light on this?
my error page configuration is as follows:
   error-page
exception-typejava.lang.Exception/exception-type
location/faces/error.jsp/location
   /error-page
error-page
error-code404/error-code
location/faces/error.jsp/location
/error-page
!-- Forbidden --
error-page
error-code403/error-code
location/faces/error.jsp/location
/error-page
error-page
error-code500/error-code
location/faces/error.jsp/location
/error-page
thanks in advance.

[EMAIL PROTECTED]: Exception Processing
ErrorPage[exceptionType=java.lang.Exception, location=/faces/error.jsp]
java.lang.IllegalStateException
at org.apache.coyote.Response.reset(Response.java:296)
at org.apache.coyote.tomcat5.CoyoteResponse.reset(CoyoteResponse.java:646)
at org.apache.coyote.tomcat5.CoyoteResponse.reset(CoyoteResponse.java:912)
at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:389
)
at
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:
225)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
at java.lang.Thread.run(Thread.java:534)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange exception - need advise

2005-05-05 Thread Igor
Hello!

If you want to locate line which causes this error, you can insert loggers
on your page. This way you could determine, which line is the reason of
error, and what should be fixed.

The other possible solution is to set response.setBufferSize(... large
number ...); for example, response.setBufferSize(10); in the beggining
of the page. Then error page will work properly with this modification, so
you will be able to see exception in log.

Thank you,
Igor


- Original Message -
From: Guy Katz [EMAIL PROTECTED]
To: Tomcat Users List tomcat-user@jakarta.apache.org
Sent: Thursday, May 05, 2005 11:45 AM
Subject: RE: strange exception - need advise


thanks.
so what should i look for to solve this?

-Original Message-
From: Igor [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 05, 2005 11:41 AM
To: tomcat-user@jakarta.apache.org
Subject: Re: strange exception - need advise


Hello!

I think, that when exception occurs, something has already been written to
output stream. Tomcat tries to redirect to error page, but it cannot do it,
because something was written.

Thank you,
Igor

- Original Message -
From: Guy Katz [EMAIL PROTECTED]
To: Tomcat Users List tomcat-user@jakarta.apache.org
Sent: Sunday, May 01, 2005 8:44 AM
Subject: strange exception - need advise


hi;
i keep getting this exception below (tomcat 5.0.30).
can anybody shed some light on this?
my error page configuration is as follows:
   error-page
exception-typejava.lang.Exception/exception-type
location/faces/error.jsp/location
   /error-page
error-page
error-code404/error-code
location/faces/error.jsp/location
/error-page
!-- Forbidden --
error-page
error-code403/error-code
location/faces/error.jsp/location
/error-page
error-page
error-code500/error-code
location/faces/error.jsp/location
/error-page
thanks in advance.

[EMAIL PROTECTED]: Exception Processing
ErrorPage[exceptionType=java.lang.Exception, location=/faces/error.jsp]
java.lang.IllegalStateException
at org.apache.coyote.Response.reset(Response.java:296)
at org.apache.coyote.tomcat5.CoyoteResponse.reset(CoyoteResponse.java:646)
at org.apache.coyote.tomcat5.CoyoteResponse.reset(CoyoteResponse.java:912)
at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:389
)
at
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:
225)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
at java.lang.Thread.run(Thread.java:534)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange Jasper2 + JSTL behavior after upgrading from TC 5.0.29 to TC 5.5.7 [SOLVED]

2005-03-24 Thread Thomas Chille
http://issues.apache.org/bugzilla/show_bug.cgi?id=33373


On Wed, 23 Mar 2005 19:32:00 +0100, Thomas Chille
[EMAIL PROTECTED] wrote:
 Hi,
 
 i declared an anttask which precompiles my JSPs. All works fine with TC 
 5.0.29.
 
 After upgrading to TC 5.5.7 i got this error:
 
 BUILD FAILED: C:\eclipse3\eclipse\workspace\ecs2\build.xml:134:
 org.apache.jasper.JasperException: The absolute uri:
 http://java.sun.com/jsp/jstl/fmt cannot be resolved in either web.xml
 or the jar files deployed with this application
 
 Only one JSP would be precompiled. This was the first page (error.jsp)
 in my JSP-hierarchy  and makes no use of JSTL.
 
 After simply changing my TOMCAT_HOME environment variable back to TC
 5.0.29's home it works again for all JSPs.
 
 Now i tried to localize the root of this behavior by simply adding
 this taglib directive to  my error.jsp:
 
 %@ taglib prefix=fmt uri=http://java.sun.com/jsp/jstl/fmt; %
 
 I would excpect that now error.jsp could not be precompiled too. But
 oh wonder after this all JSPs could be precompiled correct.
 
 I think this behavior is not correct or did i something wrong?
 
 regards and thanks in advance,
 thomas
 
  build.xml fragment 
 
 path id=build.classpath
  pathelement path=${build.dir}/
  fileset dir=${lib.dir}
include name=*.jar/
  /fileset
  fileset dir=${shared.lib.dir}
include name=*.jar/
  /fileset
  fileset dir=${env.TOMCAT_HOME}/bin
include name=*.jar/
  /fileset
  fileset dir=${env.TOMCAT_HOME}/server/lib
include name=*.jar/
  /fileset
  fileset dir=${env.TOMCAT_HOME}/common/endorsed
include name=*.jar/
  /fileset
  fileset dir=${env.TOMCAT_HOME}/common/lib
include name=*.jar/
  /fileset
 /path
 
 taskdef name=jasper2 classname=org.apache.jasper.JspC 
  classpath refid=build.classpath/
 /taskdef
 
 jasper2
  validateXml=false
  uriroot=${basedir}/web
  webXmlFragment=${basedir}/jspc/generated_web.xml
  addWebXmlMappings=true
  outputDir=${basedir}/jspc /
 


-- 
Thomas Chille
Kastanienallee 5 - 10435 Berlin
mob +49 179-5 90 72 57
fon +49 30-81 79 87 65
work + 49 30-27 90 72 04
mail [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange tomcat Behavior need urgent help.

2004-12-20 Thread Eric Rotick
This is a MySql problem. It shuts down connections if they have been
idle for too long. You need a pool manager that takes care of this.
Something like c3p0 will do the job.


On Sun, 19 Dec 2004 12:28:09 + (GMT), Krishnakant Mane
[EMAIL PROTECTED] wrote:
 
 
 hello all,
 I am Krishnakant Mane from India.  I own a software
 firm and we generally implement our systems on linux
 and all open source servers like jakarta tomcat and
 apache server in particular.  of late I have been
 facing a strange problem with tomcat.
 I am a tomcat 5 aka 5.0.25 user.  I have deployed an
 database based application using mysql as the
 back-end.  I use mysql jdbc driver to connect to the
 database.
 the application runs fine for a long time.  I check it
 personally for the entire day.  since our developers
 work on the server the entire day, I am sure there is
 that it works.  but when we shut our office and come
 next day morning, the application does not respond.
 what could be the problem.
 it is strange to see that when the server is under
 some kind of a small work load it works absolutely
 fine.  but when we don't touch it for the entire night
 the thing sympally does not work.  does tomcat also
 require warm-up?  haha.
 by the way, I have kept the jdbc (jar) library in the
 common/lib directory as all my applications are
 database based.  is it the right thing to do?
 and lastly what steps should I take to avoid the above
 mentioned problem.  one thing I will like to mention.
 when the application give problem in the morning, it
 responds with just the title and when it comes to the
 database connection it gets stuck I believe.  but when
 I run some console app with the same jdbc driver it
 properly connects to the same database/table.  and the
 application works fine when I reload again.
 Please provide some valuable feedback
 thanks
 Krishnakant.
 
 
 ___
 Win a castle for NYE with your mates and Yahoo! Messenger
 http://uk.messenger.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange tomcat Behavior need urgent help.

2004-12-20 Thread Parsons Technical Services
The pool manager built into Tomcat handles this just fine. Also ensure you 
have the latest drivers.

Doug
- Original Message - 
From: Eric Rotick [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, December 20, 2004 7:39 AM
Subject: Re: strange tomcat Behavior need urgent help.


This is a MySql problem. It shuts down connections if they have been
idle for too long. You need a pool manager that takes care of this.
Something like c3p0 will do the job.
On Sun, 19 Dec 2004 12:28:09 + (GMT), Krishnakant Mane
[EMAIL PROTECTED] wrote:

hello all,
I am Krishnakant Mane from India.  I own a software
firm and we generally implement our systems on linux
and all open source servers like jakarta tomcat and
apache server in particular.  of late I have been
facing a strange problem with tomcat.
I am a tomcat 5 aka 5.0.25 user.  I have deployed an
database based application using mysql as the
back-end.  I use mysql jdbc driver to connect to the
database.
the application runs fine for a long time.  I check it
personally for the entire day.  since our developers
work on the server the entire day, I am sure there is
that it works.  but when we shut our office and come
next day morning, the application does not respond.
what could be the problem.
it is strange to see that when the server is under
some kind of a small work load it works absolutely
fine.  but when we don't touch it for the entire night
the thing sympally does not work.  does tomcat also
require warm-up?  haha.
by the way, I have kept the jdbc (jar) library in the
common/lib directory as all my applications are
database based.  is it the right thing to do?
and lastly what steps should I take to avoid the above
mentioned problem.  one thing I will like to mention.
when the application give problem in the morning, it
responds with just the title and when it comes to the
database connection it gets stuck I believe.  but when
I run some console app with the same jdbc driver it
properly connects to the same database/table.  and the
application works fine when I reload again.
Please provide some valuable feedback
thanks
Krishnakant.
___
Win a castle for NYE with your mates and Yahoo! Messenger
http://uk.messenger.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: strange tomcat Behavior need urgent help.

2004-12-19 Thread Jan Behrens
Hi Krishnakant,

I think there was a problem with MySQL connections after a certain amount of
time. I am assume that you have defined a Datasource within TC and are using
a connection pool for the connection. If not, I would highly recommend doing
so, especially since your problem could be related to not having a
connection pool. If you do have all of the above I would try adding the
following parameters to your ressource


 

 -Original Message-
 From: Krishnakant Mane [mailto:[EMAIL PROTECTED] 
 Sent: Sunday, December 19, 2004 1:28 PM
 To: [EMAIL PROTECTED]
 Subject: strange tomcat Behavior need urgent help.
 
 
 
 
 hello all,
 I am Krishnakant Mane from India.  I own a software
 firm and we generally implement our systems on linux
 and all open source servers like jakarta tomcat and
 apache server in particular.  of late I have been
 facing a strange problem with tomcat.
 I am a tomcat 5 aka 5.0.25 user.  I have deployed an
 database based application using mysql as the
 back-end.  I use mysql jdbc driver to connect to the
 database.
 the application runs fine for a long time.  I check it 
 personally for the entire day.  since our developers work on 
 the server the entire day, I am sure there is that it works.  
 but when we shut our office and come next day morning, the 
 application does not respond. what could be the problem. it 
 is strange to see that when the server is under some kind of 
 a small work load it works absolutely fine.  but when we 
 don't touch it for the entire night the thing sympally does 
 not work.  does tomcat also require warm-up?  haha. by the 
 way, I have kept the jdbc (jar) library in the common/lib 
 directory as all my applications are database based.  is it 
 the right thing to do? and lastly what steps should I take to 
 avoid the above mentioned problem.  one thing I will like to 
 mention. when the application give problem in the morning, it 
 responds with just the title and when it comes to the 
 database connection it gets stuck I believe.  but when I run 
 some console app with the same jdbc driver it properly 
 connects to the same database/table.  and the application 
 works fine when I reload again. Please provide some valuable 
 feedback thanks Krishnakant.
 
 
   
 ___ 
 Win a castle for NYE with your mates and Yahoo! Messenger 
 http://uk.messenger.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: strange tomcat Behavior need urgent help.

2004-12-19 Thread Jan Behrens
SORRY, HERE IS THE FULL MAIL

Hi Krishnakant,

I think there was a problem with MySQL connections after a certain amount of
time. I am assume that you have defined a Datasource within TC and are using
a connection pool for the connection. If not, I would highly recommend doing
so, especially since your problem could be related to not having a
connection pool. If you do have all of the above I would try adding the
following parameters to your ressource (within your applicationName.xml
file)

ResourceParams name=jdbc/yourJNDIname
parameter
  nameurl/name
 
valuejdbc:mysql://nameOfServer:port/databaseName?autoReconnect=true/value

/parameter
parameter
  namemaxIdle/name
  value15/value
/parameter
parameter
  namemaxActive/name
  value50/value
/parameter
parameter
  namedriverClassName/name
  valuecom.mysql.jdbc.Driver/value
/parameter
parameter
  namemaxWait/name
  value1/value
/parameter
parameter
  nameremoveAbandoned/name
  valuetrue/value
/parameter

/ResourceParams

You will have to play around with the values provided above but these have
worked for me so they might be a reasonable starting point. If this doesn't
help, I would suggest searching -- http://lists.mysql.com/java. I think
there must be plenty of posts related to your problem.

HTH, Jan


 

 -Original Message-
 From: Krishnakant Mane [mailto:[EMAIL PROTECTED]
 Sent: Sunday, December 19, 2004 1:28 PM
 To: [EMAIL PROTECTED]
 Subject: strange tomcat Behavior need urgent help.
 
 
 
 
 hello all,
 I am Krishnakant Mane from India.  I own a software
 firm and we generally implement our systems on linux
 and all open source servers like jakarta tomcat and
 apache server in particular.  of late I have been
 facing a strange problem with tomcat.
 I am a tomcat 5 aka 5.0.25 user.  I have deployed an
 database based application using mysql as the
 back-end.  I use mysql jdbc driver to connect to the database.
 the application runs fine for a long time.  I check it 
 personally for the entire day.  since our developers work on 
 the server the entire day, I am sure there is that it works.  
 but when we shut our office and come next day morning, the 
 application does not respond. what could be the problem. it 
 is strange to see that when the server is under some kind of 
 a small work load it works absolutely fine.  but when we 
 don't touch it for the entire night the thing sympally does 
 not work.  does tomcat also require warm-up?  haha. by the 
 way, I have kept the jdbc (jar) library in the common/lib 
 directory as all my applications are database based.  is it 
 the right thing to do? and lastly what steps should I take to 
 avoid the above mentioned problem.  one thing I will like to 
 mention. when the application give problem in the morning, it 
 responds with just the title and when it comes to the 
 database connection it gets stuck I believe.  but when I run 
 some console app with the same jdbc driver it properly 
 connects to the same database/table.  and the application 
 works fine when I reload again. Please provide some valuable 
 feedback thanks Krishnakant.
 
 
   
 ___
 Win a castle for NYE with your mates and Yahoo! Messenger 
 http://uk.messenger.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange memory behavior in tomcat-5.0.27

2004-12-15 Thread QM
On Wed, Dec 15, 2004 at 10:22:15AM +0100, Zsolt Koppany wrote:
: Our application based on Tomcat has a strange memory behavior on Linux (SuSe
: 8.1 kernel: 2.4.20 #1 SMP). The utility top shows RSS between 132-160MB
: but SIZE is increasing. After one or two weeks SIZE is approx. 180M and than
: we get an OutOfMemory exception and SIZE drops to 159M.
: 
: I have tested the application with Borland's optimizeit but found no memory
: leak. Any ideas?

If there's no resource leak, then your app just needs more memory.  What
happens if you increase the heap and do a load test?


-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange memory behavior in tomcat-5.0.27

2004-12-15 Thread Zsolt Koppany
How can I do a load test?

Zsolt

 -Original Message-
 From: QM [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, December 15, 2004 1:01 PM
 To: Tomcat Users List
 Subject: Re: Strange memory behavior in tomcat-5.0.27
 
 On Wed, Dec 15, 2004 at 10:22:15AM +0100, Zsolt Koppany wrote:
 : Our application based on Tomcat has a strange memory behavior on Linux
 (SuSe
 : 8.1 kernel: 2.4.20 #1 SMP). The utility top shows RSS between 132-
 160MB
 : but SIZE is increasing. After one or two weeks SIZE is approx. 180M and
 than
 : we get an OutOfMemory exception and SIZE drops to 159M.
 :
 : I have tested the application with Borland's optimizeit but found no
 memory
 : leak. Any ideas?
 
 If there's no resource leak, then your app just needs more memory.  What
 happens if you increase the heap and do a load test?
 
 
 -QM
 
 --
 
 software  -- http://www.brandxdev.net
 tech news -- http://www.RoarNetworX.com
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange memory behavior in tomcat-5.0.27

2004-12-15 Thread Daniel Watrous
I have used Apache Jmeter (http://jakarta.apache.org/jmeter/).  This is a 
great tool, but sometimes a bit slow at sending the concurrent requests.  I 
think they have a networking option to send many concurrent requests from 
different hosts.  Hope this helps...

Daniel
- Original Message - 
From: Zsolt Koppany [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Wednesday, December 15, 2004 5:20 AM
Subject: RE: Strange memory behavior in tomcat-5.0.27


How can I do a load test?
Zsolt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange problem

2004-12-13 Thread Shapira, Yoav

Hi,

 I'm running Tomcat 5.0.30 on FC2 with SUN 1.4.1_02

Try JDK 1.4.2.

2. If I recall correctly, you'll need a copy of
tools.jar in $CATALINA_HOME/common/lib

No.

Yoav Shapira http://www.yoavshapira.com





This e-mail, including any attachments, is a confidential business 
communication, and may contain information that is confidential, proprietary 
and/or privileged.  This e-mail is intended only for the individual(s) to whom 
it is addressed, and may not be saved, copied, printed, disclosed or used by 
anyone else.  If you are not the(an) intended recipient, please immediately 
delete this e-mail from your computer system and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange problem

2004-12-10 Thread Laconia Data Systems
We're going to have to get low level on this
In other words we need to know whats wrong before offering diagnosis
We can diagnose this problem with tcpdump available at
http://www.tcpdump.org/
example:

tcpdump src host YangXiao.com and port 80

this will give you every incoming/outgoing packet from/to Port 80 on
webserver YangXiao.com

Report back what you find..

Martin-

- Original Message - 
From: Parsons Technical Services [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]; Yang Xiao
[EMAIL PROTECTED]
Sent: Friday, December 10, 2004 6:24 PM
Subject: Re: Strange problem


 Yang,

 Give us some history. Is this a new build? Did it work before? With
another
 app? Are the default components working? Can you get to static content?

 Doug


 - Original Message - 
 From: Yang Xiao [EMAIL PROTECTED]
 To: Tomcat Users List [EMAIL PROTECTED]
 Sent: Friday, December 10, 2004 6:00 PM
 Subject: Strange problem


  Hi all,
  I'm running Tomcat 5.0.30 on FC2 with SUN 1.4.1_02 jdk
  I'm having this strange problem, I can not access any jsp or servlet
  pages using a browser, it seems to be  timing out, but telnet to the
  port tomcat is listening then type GET ... works. I can see the
  directory structure and regular html pages works fine, any ideas?
  Also, there were no error messages in the log either, a tcpdump
  indicates the server terminates the connection right after the  http
  requst was sent from the browsers (I tried both IE and firefox)
 
  Many thanks!!
 
  Yang
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange problem

2004-12-10 Thread Mark Eggers
 I'm running Tomcat 5.0.30 on FC2 with SUN 1.4.1_02 
 jdk I'm having this strange problem, I can not
access
 any jsp or servlet pages using a browser, it seems 
 to be timing out, but telnet to the port tomcat is 
 listening then type GET ... works. I can see the 
 directory structure and regular html pages works 
 fine, any ideas?

I have a couple of thoughts.

1. Make sure that Tomcat is using Sun's jdk and not
GJC.  You can do that by setting JAVA_HOME in
/etc/profile, and making sure that whereever you
installed the jdk is before /usr/bin in the path.  Or,
you can move all of the GJC stuff out of the path.

2. If I recall correctly, you'll need a copy of
tools.jar in $CATALINA_HOME/common/lib

3. Depending on which kernel you have, (later FC 2
kernels and all FC 3 2.6 kernels), there is a problem
with the new threading model and j2sdk 1.4.1.  The
best bet is to upgrade your j2sdk to j2skd1.4.2_06.

I currently run Tomcat 5.028 on Fedora Core 3 with
j2sdk 1.4.2_06 and have no problems.  I have jdk1.5,
but I've not upgraded my Tomcat to 5.54 and recompiled
my applications yet.

Hope this helps

/mde/
. . . . just my two cents



__ 
Do you Yahoo!? 
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange problem

2004-12-10 Thread Parsons Technical Services
Yang,
Give us some history. Is this a new build? Did it work before? With another 
app? Are the default components working? Can you get to static content?

Doug
- Original Message - 
From: Yang Xiao [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Friday, December 10, 2004 6:00 PM
Subject: Strange problem


Hi all,
I'm running Tomcat 5.0.30 on FC2 with SUN 1.4.1_02 jdk
I'm having this strange problem, I can not access any jsp or servlet
pages using a browser, it seems to be  timing out, but telnet to the
port tomcat is listening then type GET ... works. I can see the
directory structure and regular html pages works fine, any ideas?
Also, there were no error messages in the log either, a tcpdump
indicates the server terminates the connection right after the  http
requst was sent from the browsers (I tried both IE and firefox)
Many thanks!!
Yang
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Strange Authentication Behavior

2004-11-30 Thread Nikola Milutinovic
Peter Neu wrote:
Hello all,
does anyone know what I means when I get this error message:
The requested resource (/favicon.ico) is not available.
when I try to log in via form authentication. This error occurs
when I use Firefox.
/favicon.ico is a semi-supported feature, introduced by IE5, if I'm not 
mistaken, but now dropped by IE6. It allows a web designer to associate 
an icon with the web site. This icon usually apperas in your location 
par of the browser, usually on the left of the URL.

I don't think it has anything to do with FORM authentication.
Nix.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Strange Problem!: Connection time out while using URLConnection connect method

2004-11-18 Thread Sailing Cai
I think you may check you IP setting.
You run tomcat in command prompt ,jvm binging your ip;but in windows
service it may binding 127.0.0.1 or localhost.

I guess it^_^


On Thu, 18 Nov 2004 09:36:32 GMT, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Hi All,
 
 I am posting this again. Please help.
 
 Thanks.
 
 --Forwarded message --
 References: [EMAIL PROTECTED]
 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Strange Problem!: Connection time out while using URLConnection 
 connect method
 Date: Wed, 17 Nov 2004 09:30:17 GMT
 Mime-Version: 1.0
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Hi All,
 
 I am facing a very strange problem. When I run tomcat4.1.27 in command 
 prompt, I am able to connect and call a servlet deployed in it from another 
 java program running on another machine using using URLConnection connect 
 method.
 
 But when I run tomcat server from windows services, the client program is not 
 able to call the deployed servlet and throws the below exception at the line 
 where connect method is invoked.
 
 java.net.ConnectException: Connection timed out: connect
 
 Has anyone else faced this strange problem. The only difference is in the way 
 tomcat server has been started. When started in command prompt there are no 
 problems in connecting to the server and calling the servlet deployed in it! 
 I need to badly get this working when tomcat is started as a windows service.
 
 Thanks in Advance.
 
 Vignesh.
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange Problem!: Connection time out while using URLConnection connect method

2004-11-18 Thread birendar . waldiya

Is this somthing related to external Ip and Internal ip 
if you are behind the firewall...

Birendar Singh Waldiya
Tata Consultancy Services Limited
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com



[EMAIL PROTECTED] 
11/18/2004 03:06 PM

Please respond to
Tomcat Users List [EMAIL PROTECTED]


To
[EMAIL PROTECTED]
cc

Subject
Strange Problem!: Connection time out while using URLConnection connect 
method






Hi All,

I am posting this again. Please help.

Thanks.


--Forwarded message --
References: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Strange Problem!: Connection time out while using URLConnection 
connect method
Date: Wed, 17 Nov 2004 09:30:17 GMT
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi All,
 
I am facing a very strange problem. When I run tomcat4.1.27 in command 
prompt, I am able to connect and call a servlet deployed in it from 
another java program running on another machine using using URLConnection 
connect method.
 
But when I run tomcat server from windows services, the client program is 
not able to call the deployed servlet and throws the below exception at 
the line where connect method is invoked.
 
java.net.ConnectException: Connection timed out: connect
 
 
Has anyone else faced this strange problem. The only difference is in the 
way tomcat server has been started. When started in command prompt there 
are no problems in connecting to the server and calling the servlet 
deployed in it! I need to badly get this working when tomcat is started as 
a windows service.
 
Thanks in Advance.
 
Vignesh.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


ForwardSourceID:NT4412 


DISCLAIMER: The information contained in this message is intended only and 
solely for the addressed individual or entity indicated in this message and for 
the exclusive use of the said addressed individual or entity indicated in this 
message (or responsible for delivery of the message to such person) and may 
contain legally privileged and confidential information belonging to Tata 
Consultancy Services Limited. It must not be printed, read, copied, disclosed, 
forwarded, distributed or used (in whatsoever manner) by any person other than 
the addressee. Unauthorized use, disclosure or copying is strictly prohibited 
and may constitute unlawful act and can possibly attract legal action, civil 
and/or criminal. The contents of this message need not necessarily reflect or 
endorse the views of Tata Consultancy Services limited on any subject matter.
  Any action taken or omitted to be taken based on this message is entirely at 
your risk and neither the originator of this message nor Tata Consultancy 
Services Limited takes any responsibility or liability towards the same. 
Opinions, conclusions and any other information contained in this message that 
do not relate to the official business of Tata Consultancy Services limited 
shall be understood as neither given nor endorsed by Tata Consultancy Services 
Limited or any affiliate of Tata Consultancy Services Limited. If you have 
received this message in error,  you should destroy this message and may please 
notify the sender by e-mail. 
 Thank you.

Re: Strange Problem!: Connection time out while using URLConnection connect method

2004-11-18 Thread vignesh
Hi,

Thanks. Thinking that could be the problem, I had already tried binding it with 
the specific IP address of the machine by setting the address attribute for 
HTTP connector in server.xml but that too didn't work.


-- Original Message --

On 18 Nov 2004, 06:06:06 PM, Sailing Cai writes:

 I think you may check you IP setting.
 You run tomcat in command prompt ,jvm binging your ip;but in windows
 service it may binding 127.0.0.1 or localhost.
 
 I guess it^_^
 
 
 On Thu, 18 Nov 2004 09:36:32 GMT, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
  Hi All,
  
  I am posting this again. Please help.
  
  Thanks.
  
  --Forwarded message --
  References: [EMAIL PROTECTED]
  From: [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Subject: Strange Problem!: Connection time out while using URLConnection 
  connect method
  Date: Wed, 17 Nov 2004 09:30:17 GMT
  Mime-Version: 1.0
  Content-Type: text/plain; charset=us-ascii
  Content-Transfer-Encoding: 7bit
  
  Hi All,
  
  I am facing a very strange problem. When I run tomcat4.1.27 in command 
  prompt, I am able to connect and call a servlet deployed in it from another 
  java program running on another machine using using URLConnection connect 
  method.
  
  But when I run tomcat server from windows services, the client program is 
  not able to call the deployed servlet and throws the below exception at the 
  line where connect method is invoked.
  
  java.net.ConnectException: Connection timed out: connect
  
  Has anyone else faced this strange problem. The only difference is in the 
  way tomcat server has been started. When started in command prompt there 
  are no problems in connecting to the server and calling the servlet 
  deployed in it! I need to badly get this working when tomcat is started as 
  a windows service.
  
  Thanks in Advance.
  
  Vignesh.
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange Problem!: Connection time out while using URLConnection connect method

2004-11-18 Thread vignesh
Hi,

The I am running tomcat and the client program in the same subnet and so there 
is no such issue.

Thanks.

-- Original Message --

On 18 Nov 2004, 06:12:54 PM, [EMAIL PROTECTED] writes:

 
 Is this somthing related to external Ip and Internal ip 
 if you are behind the firewall...
 
 Birendar Singh Waldiya
 Tata Consultancy Services Limited
 Mailto: [EMAIL PROTECTED]
 Website: http://www.tcs.com
 
 
 
 [EMAIL PROTECTED] 
 11/18/2004 03:06 PM
 
 Please respond to
 Tomcat Users List [EMAIL PROTECTED]
 
 
 To
 [EMAIL PROTECTED]
 cc
 
 Subject
 Strange Problem!: Connection time out while using URLConnection connect 
 method
 
 
 
 
 
 
 Hi All,
 
 I am posting this again. Please help.
 
 Thanks.
 
 
 --Forwarded message --
 References: [EMAIL PROTECTED]
 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Strange Problem!: Connection time out while using URLConnection 
 connect method
 Date: Wed, 17 Nov 2004 09:30:17 GMT
 Mime-Version: 1.0
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Hi All,
  
 I am facing a very strange problem. When I run tomcat4.1.27 in command 
 prompt, I am able to connect and call a servlet deployed in it from 
 another java program running on another machine using using URLConnection 
 connect method.
  
 But when I run tomcat server from windows services, the client program is 
 not able to call the deployed servlet and throws the below exception at 
 the line where connect method is invoked.
  
 java.net.ConnectException: Connection timed out: connect
  
  
 Has anyone else faced this strange problem. The only difference is in the 
 way tomcat server has been started. When started in command prompt there 
 are no problems in connecting to the server and calling the servlet 
 deployed in it! I need to badly get this working when tomcat is started as 
 a windows service.
  
 Thanks in Advance.
  
 Vignesh.
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 ForwardSourceID:NT4412 
 
 
 DISCLAIMER: The information contained in this message is intended only and 
 solely for the addressed individual or entity indicated in this message and 
 for the exclusive use of the said addressed individual or entity indicated in 
 this message (or responsible for delivery of the message to such person) and 
 may contain legally privileged and confidential information belonging to Tata 
 Consultancy Services Limited. It must not be printed, read, copied, 
 disclosed, forwarded, distributed or used (in whatsoever manner) by any 
 person other than the addressee. Unauthorized use, disclosure or copying is 
 strictly prohibited and may constitute unlawful act and can possibly attract 
 legal action, civil and/or criminal. The contents of this message need not 
 necessarily reflect or endorse the views of Tata Consultancy Services limited 
 on any subject matter.
   Any action taken or omitted to be taken based on this message is entirely 
 at your risk and neither the originator of this message nor Tata Consultancy 
 Services Limited takes any responsibility or liability towards the same. 
 Opinions, conclusions and any other information contained in this message 
 that do not relate to the official business of Tata Consultancy Services 
 limited shall be understood as neither given nor endorsed by Tata Consultancy 
 Services Limited or any affiliate of Tata Consultancy Services Limited. If 
 you have received this message in error,  you should destroy this message and 
 may please notify the sender by e-mail. 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: strange Tomcat message - PANIC

2004-09-24 Thread Shapira, Yoav

Hi,
This message seems to originate from your JDBC driver.
sql_env_t::get_connection_handle acquire is the giveaway.  Are you
using a type 4 driver?

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Radek Liebzeit [mailto:[EMAIL PROTECTED]
Sent: Friday, September 24, 2004 4:36 AM
To: [EMAIL PROTECTED]
Subject: strange Tomcat message - PANIC

Hi,
our Tomcat server crashed. Last message that we received in
catalina.out
was this:

:  )STATUS -  - TPL error 0 errno 4
:  PANIC - TPEUTIL sql_env_t::get_connection_handle acquire
coninfo_mutex_lock failed PID 15987

Before it, we were receiving only standard messages.

Thank You for any ideas.

Radek





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: strange Tomcat message - PANIC

2004-09-24 Thread Radek Liebzeit
Hi,
I see. We are using two JDBC drivers. One for MySQL and one for
Progress. How can I recognize one that is source of this message? I
think that problem is with the Progress driver because of previous
experience with this driver. It causes Tomcat crash sometimes but with
full message to the catalina out. This short message is new for me and
I'm not sure about its source. 

Radek


 -Original Message-
 From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
 Sent: Friday, September 24, 2004 2:47 PM
 To: Tomcat Users List
 Subject: RE: strange Tomcat message - PANIC
 
 
 Hi,
 This message seems to originate from your JDBC driver.
 sql_env_t::get_connection_handle acquire is the giveaway.  Are you
 using a type 4 driver?
 
 Yoav Shapira
 Millennium Research Informatics
 
 
 -Original Message-
 From: Radek Liebzeit [mailto:[EMAIL PROTECTED]
 Sent: Friday, September 24, 2004 4:36 AM
 To: [EMAIL PROTECTED]
 Subject: strange Tomcat message - PANIC
 
 Hi,
 our Tomcat server crashed. Last message that we received in
 catalina.out
 was this:
 
 :)STATUS -  - TPL error 0 errno 4
 :PANIC - TPEUTIL sql_env_t::get_connection_handle acquire
 coninfo_mutex_lock failed PID 15987
 
 Before it, we were receiving only standard messages.
 
 Thank You for any ideas.
 
 Radek
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 This e-mail, including any attachments, is a confidential business
 communication, and may contain information that is confidential,
 proprietary and/or privileged.  This e-mail is intended only for the
 individual(s) to whom it is addressed, and may not be saved, copied,
 printed, disclosed or used by anyone else.  If you are not the(an)
 intended recipient, please immediately delete this e-mail from your
 computer system and notify the sender.  Thank you.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: strange Tomcat message - PANIC

2004-09-24 Thread Caldarale, Charles R
 From: Radek Liebzeit [mailto:[EMAIL PROTECTED]
 Subject: RE: strange Tomcat message - PANIC
 
:  )STATUS -  - TPL error 0 errno 4
:  PANIC - TPEUTIL sql_env_t::get_connection_handle acquire
 coninfo_mutex_lock failed PID 15987

What JDK level and platform are you running on?

I suspect the message is coming from native code that's part of your Progress driver; 
is that possible? Just to check, I scanned the JVM 1.4.2 source, but couldn't find any 
message of this form within the JVM itself.

Can't think of any reason for a mutex failure other than deadlock detection or 
possibly some resource limitation imposed by the platform.

 - 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange errorq

2004-09-07 Thread Sjoerd van Leent
Bedrijven.nl wrote:
Hello all,
I posted a message that our production server is slower than our development
server. The thing that happens is that one application (jsp) causes tomcat
stops and starts. Below the case:
I have a search.jsp. On this page a user can search on 4 different manners.
Each manner is programmed in a block. If a user toggles an option the jsp
is submitted to our form/actionbean and reloads the page. I.e. the uses
wants to do an extended search, he click on the item extended search. The
Jsp submits to the struts framework, and reload the page (and doing some
checks and retrieve some data). Now a parameter tells the jsp to show the
extended search block. This is working ok, until a certain moment. After
switching between the option quick search and extended search (and everytime
reloading the page) for several times Tomcat stops and restarts. In the log
I can't see any error. The last thing I can found is that Tomcat is looking
for an instance of the actionbean (that is related to the search.jsp). I
think he can found or create an instance of the actionbean. But WHY It
works several times ok and than on a certain moment he can't found it
anymore. Anyone any idea???
Please help me (it's critical)
Thx in advanced
Maarten
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This looks like a memory leak, which in Java should be nearly impossible 
to have, that causes Tomcat to restart. In your actionbean (or JSP pages 
and other related resources), do you use any native resources that might 
not be disposed properly? I can't think of anything else (or at least, 
if you're not running a beta version of Tomcat).

Regards,
Sjoerd
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange errorq

2004-09-07 Thread Bedrijven.nl
Hello sjoerd,

On our development server it's no problem at all. I was also thinking at
memory leak but why should this only happen on our prodcution server??

Maarten

-Oorspronkelijk bericht-
Van: Sjoerd van Leent [mailto:[EMAIL PROTECTED]
Verzonden: Tuesday, September 07, 2004 10:46 AM
Aan: Tomcat Users List
Onderwerp: Re: Strange errorq


Bedrijven.nl wrote:

Hello all,

I posted a message that our production server is slower than our
development
server. The thing that happens is that one application (jsp) causes tomcat
stops and starts. Below the case:

I have a search.jsp. On this page a user can search on 4 different manners.
Each manner is programmed in a block. If a user toggles an option the jsp
is submitted to our form/actionbean and reloads the page. I.e. the uses
wants to do an extended search, he click on the item extended search. The
Jsp submits to the struts framework, and reload the page (and doing some
checks and retrieve some data). Now a parameter tells the jsp to show the
extended search block. This is working ok, until a certain moment. After
switching between the option quick search and extended search (and
everytime
reloading the page) for several times Tomcat stops and restarts. In the log
I can't see any error. The last thing I can found is that Tomcat is looking
for an instance of the actionbean (that is related to the search.jsp). I
think he can found or create an instance of the actionbean. But WHY It
works several times ok and than on a certain moment he can't found it
anymore. Anyone any idea???

Please help me (it's critical)

Thx in advanced

Maarten





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

This looks like a memory leak, which in Java should be nearly impossible
to have, that causes Tomcat to restart. In your actionbean (or JSP pages
and other related resources), do you use any native resources that might
not be disposed properly? I can't think of anything else (or at least,
if you're not running a beta version of Tomcat).

Regards,
Sjoerd


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange errorq

2004-09-07 Thread Shapira, Yoav

Hi,
Get a profiler as Senor Crosley suggested.  Knowing when and how to use
a profiler is both a basic and a priceless developer skill.  If you
can't run the profiler on your production Tomcat instance, setup another
instance on the production box (or an identical box if you have one) and
run the profiler on that instance.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Bedrijven.nl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 07, 2004 4:25 AM
To: 'Tomcat Users List'
Subject: Strange errorq

Hello all,

I posted a message that our production server is slower than our
development
server. The thing that happens is that one application (jsp) causes
tomcat
stops and starts. Below the case:

I have a search.jsp. On this page a user can search on 4 different
manners.
Each manner is programmed in a block. If a user toggles an option the
jsp
is submitted to our form/actionbean and reloads the page. I.e. the uses
wants to do an extended search, he click on the item extended search.
The
Jsp submits to the struts framework, and reload the page (and doing
some
checks and retrieve some data). Now a parameter tells the jsp to show
the
extended search block. This is working ok, until a certain moment.
After
switching between the option quick search and extended search (and
everytime
reloading the page) for several times Tomcat stops and restarts. In the
log
I can't see any error. The last thing I can found is that Tomcat is
looking
for an instance of the actionbean (that is related to the search.jsp).
I
think he can found or create an instance of the actionbean. But WHY
It
works several times ok and than on a certain moment he can't found it
anymore. Anyone any idea???

Please help me (it's critical)

Thx in advanced

Maarten




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange problem with Apache2/Tomcat4 part II

2004-08-02 Thread Harold Pritchett
Harold Pritchett wrote:
OK, i gave up on the mod_jk version 1.2 connector.  I downloaded the
version 2 connector and built it with:
Thnaks to everyone here, I got it to work.  I ended up downloading the
mod_JK2 source, built it (after editing the makefile to add in all the
missing libs) and installed it.  Started tomcat and it started fine and
built the unix socket file.  Started httpd, and it could display the
http://localhost/jkstatus page just fine, but barfed on localhost/examples.
The page not available message.  Poked around a bit and found that
the httpd.conf file as distributed was starting with user and group equal
to nobody.  Fixed this to point to the actual user/group, and all is
well.
That bit about the default user/group for apache httpd seems to have
escaped me.
Thanks again for all the help.  At some point, I'll post my complete
notes for putting this together.
Harold
--
Harold Pritchett
[EMAIL PROTECTED]+1.706.546.0692
pgp public key: http://www.arches.uga.edu/~harold/pgpkey.html
They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety.
   Benjamin Franklin, Historical Review of Pennsylvania, 1759.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange OutOfMemory Error in TcpWorkerThread

2004-07-30 Thread Shapira, Yoav

Hi,
It's not likely a memory problem, but a resources problem for creating threads.  If 
you're running on unix, look at the ulimit command.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED]
Sent: Friday, July 30, 2004 4:00 AM
To: Tomcat Users List
Subject: Strange OutOfMemory Error in TcpWorkerThread

Hi all, I have this strange error :
SEVERE: Caught exception (java.lang.OutOfMemoryError: unable to create new
native thread) executing
[EMAIL PROTECTED],
terminating thread

I use those parameters :

-verbose:gc -Xms756m -Xmx1024m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC

And the ParNew before and after the error gives me :
Before : [ParNew 299307K-285970K(774080K), 0.0632930 secs]
After :  [ParNew 302226K-290481K(774080K), 0.0777970 secs]

So, there is a LOT of memory available. I probably have to change some Jvm
parameters. Note that the dev is out for holidays, so it will be difficult
for me to look for a memory leak somewhere. Note that if I give more memory
(say -Xms=1024m -Xmx=1536m, for example), the error arrives sooner. There
are
800 connectors configured. I was also unable to increase the number of
tomcat5.CoyoteConnector threads.

Any help appreciated,

François.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange problem with Apache2/Tomcat4

2004-07-30 Thread Cox, Charlie
Have you enabled the Connector in server.xml for port 8009?

 -Original Message-
 From: Harold Pritchett [mailto:[EMAIL PROTECTED]
 Sent: Thursday, July 29, 2004 8:27 PM
 To: Tomcat Users List
 Subject: Strange problem with Apache2/Tomcat4
 
 Help!
 
 I'm trying to install Apache HTTPD and Jakarta Tomcat and get them
 to play nice together.  I've done this before with different
 releases of the software, so I can't figure out what I'm doing wrong.
 
 First, the releases of the software I'm using:
 
 SuSE Linux Standard Server 8, done as a basic install.  The default
 Apache 1.3 server was removed with rpm before any of this was done.
 
 openssl-0.9.7d
 httpd-2.0.50
 jakarta-tomcat-4.1.30
 jakarta-tomcat-connectors-jk-1.2.5
 
 Sun Java J2SE:  j2sdk-1_4_2_05
 
 Apache is installed in /usr/local/apache2
 Tomcat is installed in /usr/local/jakarta-tomcat-4.1.30
   and then linked to /usr/local/tomcat
 Java is installed in /opt/j2sdk1.4.2_05
   and then linked to /usr/lib/java
 
 Some environment variables (some lines wrapped for readability):
 
  JRE_HOME=/usr/lib/java/jre
  PATH=/usr/lib/java/bin:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:
   /usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:
   /opt/gnome2/bin:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/java/bin:
   /opt/gnome/bin
  JAVA_BINDIR=/usr/lib/java/bin
  JAVA_HOME=/usr/lib/java
  SDK_HOME=/usr/lib/java
  JDK_HOME=/usr/lib/java
  CLASSPATH=/usr/local/tomcat/bin/bootstrap.jar:
   /usr/lib/java/lib/tools.jar:
   /usr/local/tomcat/common/lib/servlet.jar:.
  JAVA_ROOT=/usr/lib/java
  CATALINA_HOME=/usr/local/tomcat
 
 Finally, here's what I did:
 
 1.  Install SSL in /usr/local/ssl
 2.  Install Apache HTTPD.  Used:
 
  ./configure --prefix=/usr/local/apache2 \
   --enable-so --enable-rewrite --enable-ssl \
   --with-ssl=/usr/local/ssl --enable-proxy
  make
  su -
  make install
  cd /usr/local/apache2/bin
  ./apachectl start
 
  Started up a web browser and connected to http://localhost.
  Got the standard You have installed apache httpd page.
  The httpd server works fine.
 
  ./apachectl stop
 
 3.  Install tomcat server.  Used:
 
  Created user and group tomcat4
  Downloaded tomcat 4.1.30 binary distribution to /download/bin
  cd /usr/local
  tar zxf /download/bin/jakarta-tomcat-4.1.30.tar.gz
  ln -s jakarta-tomcat-4.1.30/ tomcat
  chown -R tomcat4.tomcat4 /usr/local/tomcat
  /usr/local/tomcat/bin/startup.sh
 
  check to see if tomcat is running with ps ax
  Started up a web browser and connected to http://localhost:8080.
  Got the standard Tomcat home page.  Clicked on the JSP Examples
  link.  Got the JSP Examples page.  I then clicked on EVERY
  SINGLE EXAMPLE and made sure it worked.  Ditto for the Servlet
  examples.  Everything works fine!  stopped the server with
 
  /usr/local/tomcat/bin/shutdown.sh
 
  OK, httpd works fine and tomcat works fine, independently.  Next,
  make them work togehter.
 
 4.  Install the Mod_JK connector.
 
  download the source for the connector from jakarta.apache.org.
 
  unpack into a temp directory, configure, and make.
 
  cd /tmp
  tar zxf
/download/src/jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz
  cd jakarta-tomcat-connectors-jk-1.2.5-src/jk/native
  ./buildconf.sh
  ./configure --with-apxs=/usr/local/apache2/bin/apxs
  make
  cd apache-2.0/
  cp mod_jk.so /usr/local/apache2/modules
 
  now, build the workers.properties file in /usr/local/tomcat/conf/jd
 
  cd /usr/local/tomcat/conf
  mkdir jk
  cd jk
  vi workers.properties
  cat workers.properties
   worker.list=ajp13
   worker.ajp13.port=8009
   worker.ajp13.host=localhost
   worker.ajp13.type=ajp1
  cd ..
 
 
  Edit the server.xml file and make the following changes
 
  Following the line beginning Server port=8005 shutdown=SHUTDOWN
  insert the lines:
 
   Listener className=org.apache.ajp.tomcat4.config.ApacheConfig
   modJk=/usr/local/apache2/modules/mod_jk.so /
 
  and following the lines:
 
!-- Define the default virtual host --
Host name=localhost debug=0 appBase=webapps
 unpackWARs=true autoDeploy=true
 
  insert the lines
 
Listener className=org.apache.ajp.tomcat4.config.ApacheConfig
   append=true forwardAll=false
   modJk=/usr/local/apache2/modules/mod_jk.so /
 
  and finally, edit the /usr/local/apache2/conf/httpd.conf and place
  a line at the very end which says:
 
   Include /usr/local/tomcat/conf/auto/mod_jk.conf
 
 Start Tomcat, wait 30 seconds and start apache
 
 Use a browser and connect to http://localhost.  Get the Apache default
 screen.  Connect to http://localhost/examples.  Since this is only
 defined as a directory, we get the usual apache display of a directory
 with 

Re: Strange problem with Apache2/Tomcat4

2004-07-30 Thread Harold Pritchett
Cox, Charlie wrote:
Have you enabled the Connector in server.xml for port 8009?
I think so...  I'm using the mod_jk connector version 1.2.5 and
NOT version 2.  Here's my  workers.properties and server.xml files...
workers.properties
worker.list=ajp13
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13
server.xml
!-- Example Server Configuration File --
!-- Note that component elements are nested corresponding to their
 parent-child relationships with each other --
!-- A Server is a singleton element that represents the entire JVM,
 which may contain one or more Service instances.  The Server
 listens for a shutdown command on the indicated port.
 Note:  A Server is not itself a Container, so you may not
 define subcomponents such as Valves or Loggers at this level.
 --
Server port=8005 shutdown=SHUTDOWN debug=0
  Listener className=org.apache.ajp.tomcat4.config.ApacheConfig
   modJk=/usr/local/apache2/modules/mod_jk.so /
  !-- Comment these entries out to disable JMX MBeans support --
  !-- You may also configure custom components (e.g. Valves/Realms) by
   including your own mbean-descriptor file(s), and setting the
   descriptors attribute to point to a ';' seperated list of paths
   (in the ClassLoader sense) of files to add to the default list.
   e.g. descriptors=/com/myfirm/mypackage/mbean-descriptor.xml
  --
  Listener className=org.apache.catalina.mbeans.ServerLifecycleListener
debug=0/
  Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener
debug=0/
  !-- Global JNDI resources --
  GlobalNamingResources
!-- Test entry for demonstration purposes --
Environment name=simpleValue type=java.lang.Integer value=30/
!-- Editable user database that can also be used by
 UserDatabaseRealm to authenticate users --
Resource name=UserDatabase auth=Container
  type=org.apache.catalina.UserDatabase
   description=User database that can be updated and saved
/Resource
ResourceParams name=UserDatabase
  parameter
namefactory/name
valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value
  /parameter
  parameter
namepathname/name
valueconf/tomcat-users.xml/value
  /parameter
/ResourceParams
  /GlobalNamingResources
  !-- A Service is a collection of one or more Connectors that share
   a single Container (and therefore the web applications visible
   within that Container).  Normally, that Container is an Engine,
   but this is not required.
   Note:  A Service is not itself a Container, so you may not
   define subcomponents such as Valves or Loggers at this level.
   --
  !-- Define the Tomcat Stand-Alone Service --
  Service name=Tomcat-Standalone
!-- A Connector represents an endpoint by which requests are received
 and responses are returned.  Each Connector passes requests on to the
 associated Container (normally an Engine) for processing.
 By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
 You can also enable an SSL HTTP/1.1 Connector on port 8443 by
 following the instructions below and uncommenting the second Connector
 entry.  SSL support requires the following steps (see the SSL Config
 HOWTO in the Tomcat 4.0 documentation bundle for more detailed
 instructions):
 * Download and install JSSE 1.0.2 or later, and put the JAR files
   into $JAVA_HOME/jre/lib/ext.
 * Execute:
 %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
 $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
   with a password value of changeit for both the certificate and
   the keystore itself.
 By default, DNS lookups are enabled when a web application calls
 request.getRemoteHost().  This can have an adverse impact on
 performance, so you can disable it by setting the
 enableLookups attribute to false.  When DNS lookups are disabled,
 request.getRemoteHost() will return the String version of the
 IP address of the remote client.
--
!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
   port=8080 minProcessors=5 maxProcessors=75
   enableLookups=true redirectPort=8443
   acceptCount=100 debug=0 connectionTimeout=2
   useURIValidationHack=false disableUploadTimeout=true /
!-- Note : To disable connection timeouts, set connectionTimeout value
 to 0 --
!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 --
!--
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
   port=8443 minProcessors=5 maxProcessors=75
   enableLookups=true
   acceptCount=100 debug=0 scheme=https secure=true
 

Re: Strange problem with Apache2/Tomcat4 part II

2004-07-30 Thread Mark Eggers
I think that this has been discussed on the list before.

You might want to check the archives.

If I remember correctly, this happens on a Redhat 9 system where the SSL
libraries have been installed via RPMs.

Before running your configure commmand, setting an environment variable
via the following:

export LDFLAGS=-L/usr/kerberos/lib

You may also run into gdm issues as well, but given your location of
Apache, I'm guessing that you compiled httpd on your own.

If this doesn't solve your problem, check out the marcs.theaimsgroup.com
archives and look for md5.

HTH

/mde/
just my two cents . . . .



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange error when processing stylesheets: tomcat, jdk1.4, windows, xalan

2004-07-01 Thread Martin Monsorno
Martin Monsorno [EMAIL PROTECTED] writes:

 Hi *,

 I get the following error when trying to transform a xml document with
 a XSLT stylesheet:

 ; SystemID: jndi:/localhost/ipas/xsl/minutes_pdf.xsl; Line#: 298; Column#: 66
 javax.xml.transform.TransformerException: Unknown error in XPath
 at org.apache.xpath.XPath.bool(XPath.java:411)
 at org.apache.xalan.templates.ElemIf.execute(ElemIf.java:198)
 ...

 In the stylesheet, I test for an empty string:

 xsl:if test=not(string(./title))

 The error occurs:

 - with ANY test condition that tests for an empty string
   (e.g. with string-length(./entry) = 0
 - with having xalan.jar, xml-apis.jar and xercesImpl.jar in my
   WEB-INF/lib from any xalan versions of 2.5.0, 2.5.2, 2.6.0
 - with Tomcat 4.1.29 on Windows 2000 and JDK 1.4x
 - NOT with JDK 1.3
 - NOT on Linux
 - NOT with resin

Ah, yes, and it does NOT occur when running the transforming by
directly calling xalan from the command line and not via TomCat!


-- 
Martin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange error when processing stylesheets: tomcat, jdk1.4, windows, xalan

2004-07-01 Thread Dan Barron
Have you tried just testing (title) instead of (./title)?  The added ./ 
seems unneceassry.

At 02:25 AM 7/1/2004, you wrote:
Hi *,
I get the following error when trying to transform a xml document with
a XSLT stylesheet:
; SystemID: jndi:/localhost/ipas/xsl/minutes_pdf.xsl; Line#: 298; 
Column#: 66
javax.xml.transform.TransformerException: Unknown error in XPath
at org.apache.xpath.XPath.bool(XPath.java:411)
at org.apache.xalan.templates.ElemIf.execute(ElemIf.java:198)
...

In the stylesheet, I test for an empty string:
xsl:if test=not(string(./title))
The error occurs:
- with ANY test condition that tests for an empty string
  (e.g. with string-length(./entry) = 0
- with having xalan.jar, xml-apis.jar and xercesImpl.jar in my
  WEB-INF/lib from any xalan versions of 2.5.0, 2.5.2, 2.6.0
- with Tomcat 4.1.29 on Windows 2000 and JDK 1.4x
- NOT with JDK 1.3
- NOT on Linux
- NOT with resin
It's these kind of errors that makes being a programmer a real fun!
Does anyone have a tip on what to do?
--
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: strange error when processing stylesheets: tomcat, jdk1.4, windows, xalan

2004-07-01 Thread Jacob Kjome
Quoting Martin Monsorno [EMAIL PROTECTED]:

 Martin Monsorno [EMAIL PROTECTED] writes:
 
  Hi *,
 
  I get the following error when trying to transform a xml document with
  a XSLT stylesheet:
 
  ; SystemID: jndi:/localhost/ipas/xsl/minutes_pdf.xsl; Line#: 298;
 Column#: 66
  javax.xml.transform.TransformerException: Unknown error in XPath
  at org.apache.xpath.XPath.bool(XPath.java:411)
  at org.apache.xalan.templates.ElemIf.execute(ElemIf.java:198)
  ...
 
  In the stylesheet, I test for an empty string:
 
  xsl:if test=not(string(./title))
 
  The error occurs:
 
  - with ANY test condition that tests for an empty string
(e.g. with string-length(./entry) = 0
  - with having xalan.jar, xml-apis.jar and xercesImpl.jar in my
WEB-INF/lib from any xalan versions of 2.5.0, 2.5.2, 2.6.0
  - with Tomcat 4.1.29 on Windows 2000 and JDK 1.4x
  - NOT with JDK 1.3

Well, this should be obvious by now.  JDK1.4+ ships with Xalan.  As such, it is
an endorsed library.  You shouldn't be putting endorsed libraries in
WEB-INF/lib.  Since Tomcat adds Xerces and xml-apis to common/endorsed, they
become endorsed libraries as well.  Tomcat classloaders will actively ignore
endorsed libraries sitting in WEB-INF/lib.  As such, your own versions of the
libraries are doing nothing whatsoever being there.  If you want to update
Tomcat with the latest Xerces and xml-apis, delete the existing ones from
common/endorsed and add yours there.  You can also add Xalan there, but probably
should add it to JAVA_HOME/jre/lib/endorsed (create the directory if it doesn't
already exist).  I suggest you use the 2jars release to avoid making BCel
(which Xalan ships with... and old version at that) an endorsed library.  If
things don't work after this, then I'm at a loss.

  - NOT on Linux
  - NOT with resin
 
 Ah, yes, and it does NOT occur when running the transforming by
 directly calling xalan from the command line and not via TomCat!
 


Jake


 
 --
 Martin
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange behavious with session creation on http and https

2004-06-08 Thread John Sidney-Woollett
Ismael Blesa Part said:

 I have set two connectors http and https. I have my webapp that is
 served by these two connectors.

[snip]

 However, If I connect first to https and then I change to http, I will
 have two sessions, one for https and the other one to http.

I believe that this is normal.

If you ensure that the session is created using a non secure page first
(you can always redirect from a non-secure to a secure page after creating
the session), then the problem will go away.

John Sidney-Woollett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange behavious with session creation on http and https

2004-06-08 Thread Ismael Blesa Part
I have reviewed the mailing list and I have found that the normal 
behaviour in tomcat is

You enter in http and then change to https (session is shared)
You enter in https and then in http (you have two different sessions)
I would like to have different sessions for different schemas, that is, 
If you connect to http and then to https then TWO DIFFERENT sessions are 
created.
But I have not found how to do this.

My fear is that on different application servers the behaviour is 
different.

Ismael
John Sidney-Woollett wrote:
Ismael Blesa Part said:
 

I have set two connectors http and https. I have my webapp that is
served by these two connectors.
   

[snip]
 

However, If I connect first to https and then I change to http, I will
have two sessions, one for https and the other one to http.
   

I believe that this is normal.
If you ensure that the session is created using a non secure page first
(you can always redirect from a non-secure to a secure page after creating
the session), then the problem will go away.
John Sidney-Woollett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Strange behavious with session creation on http and https

2004-06-08 Thread John Sidney-Woollett
Ismael Blesa Part said:
 I would like to have different sessions for different schemas, that is,
 If you connect to http and then to https then TWO DIFFERENT sessions are
 created.
 But I have not found how to do this.

 My fear is that on different application servers the behaviour is
 different.

If this is the behaviour that you want, then you only have to worry about
the case when the user goes from http to https (because you want a new
session instead of the old one).

One way to do this would be to record the type of connection (secure or
not) in the session when it is created, and then when you go to a secure
connection, check the value you stored (in the session).

If it indicates that the session was not originally created by a secure
requested, invalidate that session, and create a new one.

I think that will probably work.

John Sidney-Woollett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange behaviour with buffers

2004-05-19 Thread Shapira, Yoav

Hi,
So BEA is telling you that if you say page buffer=64kb and they give
you 12kb, that's the spec? ;)

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Jason Irwin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 5:23 AM
To: '[EMAIL PROTECTED]'
Subject: Strange behaviour with buffers

Apologies if this is in the wrong group, I think that User is the
right
one.

I have noted a difference between how Tomcat (4.0.6 and 4.1.127) and
WebLogic (7.0 and 8.1) assign buffers, and I'm trying to figure out
which
one is correct.  I have an outer page that does not define any
buffer,
and
an inner page that does, e.g.:
outer.jsp
html
body
Outer buffer is %=out.getBufferSize()%BR
Outer remaining is %=out.getRemaining()%BR
jsp:include page=inner.jsp /BR
Outer buffer is now %=out.getBufferSize()%BR
Outer remaining is now %=out.getRemaining()%
/body
html

inner.jsp
%@ page buffer=64kb %
Inner buffer is %=out.getBufferSize()%BR
Inner remaining is %=out.getRemaining()%

Tomcat reports 8kb for outer.jsp and then 64kb for inner.jsp.  The
remaining buffer sizes are unrelated.  WebLogic reports 12kb for both
and
the remaining buffer are related.  It's as if Tomcat creates new
JspWriter
for each dynamic include, but WebLogic keeps using the same JspWriter.
BEA
have confirmed that this is their expected behaviour.

Is anyone able to confirm if BEA are correct in their interpretation of
the
JSP Specification and, if so, why Tomcat is behaving the way it does?
Is
this just a case of a differing opinion on the same spec?  I've had a
look
through the documentation and drawn a blank.

Thanks in advance,

Jason.

___
_
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
___
_

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange behaviour with buffers

2004-05-19 Thread Jason Irwin
No, they are saying the page buffer declaration in the child include in
invalid as it is not supported in the spec.  What they quoted at me was:
http://java.sun.com/products/jsp/tags/syntaxref.fm7.html
It is stated that  Note that the page directive does not apply to any
dynamic included files;.

If I move the directive to the parent, it works (as you'd expect).  But what
should the behaviour be if the directive appears in the child?  BEA claim it
will be ignored.  And should the parent and child have separate JspWriters,
or the same one?

J.

-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 19 May 2004 13:54
To: Tomcat Users List
Subject: RE: Strange behaviour with buffers



Hi,
So BEA is telling you that if you say page buffer=64kb and they give
you 12kb, that's the spec? ;)

Yoav Shapira
Millennium Research Informatics


This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange behaviour with buffers

2004-05-19 Thread Shapira, Yoav

Hi,
Ahh, I see what you mean.  That's an interesting question, and I'm not a
JSP expert (nor am I a huge fan of these low-level buffering directives
in the presentation layer in the first place, but that's another story),
so I'll let Kin-Man or another expert answer if they feel like it ;)

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Jason Irwin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 9:00 AM
To: 'Tomcat Users List'
Subject: RE: Strange behaviour with buffers

No, they are saying the page buffer declaration in the child include in
invalid as it is not supported in the spec.  What they quoted at me
was:
http://java.sun.com/products/jsp/tags/syntaxref.fm7.html
It is stated that  Note that the page directive does not apply to any
dynamic included files;.

If I move the directive to the parent, it works (as you'd expect).  But
what
should the behaviour be if the directive appears in the child?  BEA
claim
it
will be ignored.  And should the parent and child have separate
JspWriters,
or the same one?

J.

-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 19 May 2004 13:54
To: Tomcat Users List
Subject: RE: Strange behaviour with buffers



Hi,
So BEA is telling you that if you say page buffer=64kb and they give
you 12kb, that's the spec? ;)

Yoav Shapira
Millennium Research Informatics

___
_
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
___
_

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange behaviour with buffers

2004-05-19 Thread Ralph Einfeldt

That statement from the site is wrong in at least one case:

page import

May be it's wrong in the other cases too.

AFAIK the spec doesn't mention such restriction.
(At least I couldn't find it)

 -Original Message-
 From: Jason Irwin [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, May 19, 2004 3:00 PM
 To: 'Tomcat Users List'
 Subject: RE: Strange behaviour with buffers
 
 
 Note that the page directive does not apply to any
 dynamic included files;.
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange behaviour with buffers

2004-05-19 Thread Jason Irwin
That statement from the site is wrong in at least one case:
   page import
May be it's wrong in the other cases too.

Indeed, that did puzzle me.  But I am not a Java or JSP expert by any means
and BEA's stance is Our behaviour meets the spec, our behaviour is
correct.

One big problem I had (have!) was finding the official JSP Spec.  This link
is (I think) to the spec and it seems to refute BEA's stance.  But I cannot
be sure.

http://sunsdlctemp2-vhost1.cambma1-dc1.cscehub.com/servlet/EComFileServlet//
ESD6/JSCDL/jsp/2.0-fr/jsp-2_0-fr-spec.pdf?ActionId=verifyTicketId=2aPxkVSIO
RtaTicketServerUrl=LxU7fwxQLugy%2BErpKYcvIWlUfSBzPG60JI8nt3z9f3UsBDtcUw13tW
6%2BGroupName=EedEWQ%3D%3D
[JSP.1.10.1, 1-43, page 79] A translation unit (JSP source file and any
files included via the include directive) can contain more than one instance
of the page directive, all the attributes will apply to the complete
translation unit (i.e. page directives are position independent).

My head is beginning to hurt.

Jason Dazed and confused Irwin


This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange behaviour with buffers

2004-05-19 Thread Shapira, Yoav

Hi,

Indeed, that did puzzle me.  But I am not a Java or JSP expert by any
means
and BEA's stance is Our behaviour meets the spec, our behaviour is
correct.

BEA's stance has been like that (and wrong) in the past.  That's not a
knock on them.

One big problem I had (have!) was finding the official JSP Spec.  This
link

Finding the spec is easy: go to
http://java.sun.com/products/jsp/reference/api/index.html and scroll
down to the Specifications section, click on the Download link next to
2.0-final.  It's hard to bookmark the actual download link because it
contains session data.

My head is beginning to hurt.

Jason Dazed and confused Irwin

Skip the buffering and skip the headache.  Why are you using these
include buffering directives in the first place?

Yoav Shapira




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange behaviour with buffers

2004-05-19 Thread Jason Irwin
Skip the buffering and skip the headache.  Why are you using
these include buffering directives in the first place?
Legacy.  Don't worry.  As soon as I have the time to get rid of them, I
will!  I know what needs to be done, I just need the time to do it.

J.


This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: strange memory problem

2004-05-12 Thread Shapira, Yoav

Hi,
That's a good theory.  Another question is are you compiling JSPs
frequently at runtime?

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Joseph Shraibman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 12:17 AM
To: Tomcat Users List
Subject: Re: strange memory problem

java.lang.OutOfMemoryError is also thrown when java can't start up a
thread because it reached the system limit.  Could that be your
problem?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange memory problem

2004-05-11 Thread Joseph Shraibman
java.lang.OutOfMemoryError is also thrown when java can't start up a 
thread because it reached the system limit.  Could that be your problem?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange error

2004-05-07 Thread Yansheng Lin
What event listeners?

-Original Message-
From: Nathan Maves [mailto:[EMAIL PROTECTED] 
Sent: May 5, 2004 08:15
To: Tomcat Users List
Subject: Re: Strange error


The object is a custom object.  The only difference I can find is that  
this object has some event listeners attached to it.  It is an  
implementation of a Tree object.  The only java objects that it uses  
are Map, TreeMap and few other util classes.

Nathan

On May 5, 2004, at 7:18 AM, QM wrote:

 On Tue, May 04, 2004 at 02:30:16PM -0600, Nathan Maves wrote:
 : What could cause this error in Tomcat 5.0.19.
 :
 : 2004-05-04 14:21:02 StandardContext[/manager]HTMLManager:
 : ManagerServlet.reload[/ReportViewer]
 : java.lang.ThreadDeath
 : at
 :  
 org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoade 
 r
 : .java:1270)
 : [snip]
 : It happens when I place an object in the session and then click  
 reload
 : from the webapp manager.


 Any object, or a particular object?
 (especially a custom object)

 Does said object do anything with threads, such as calling ::stop()?

 -QM

 -- 

 software  -- http://www.brandxdev.net
 tech news -- http://www.RoarNetworX.com


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange error

2004-05-05 Thread QM
On Tue, May 04, 2004 at 02:30:16PM -0600, Nathan Maves wrote:
: What could cause this error in Tomcat 5.0.19.
: 
: 2004-05-04 14:21:02 StandardContext[/manager]HTMLManager:  
: ManagerServlet.reload[/ReportViewer]
: java.lang.ThreadDeath
: at  
: org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader 
: .java:1270)
: [snip]
: It happens when I place an object in the session and then click reload  
: from the webapp manager.


Any object, or a particular object?
(especially a custom object)

Does said object do anything with threads, such as calling ::stop()?

-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange error

2004-05-05 Thread Nathan Maves
The object is a custom object.  The only difference I can find is that  
this object has some event listeners attached to it.  It is an  
implementation of a Tree object.  The only java objects that it uses  
are Map, TreeMap and few other util classes.

Nathan

On May 5, 2004, at 7:18 AM, QM wrote:

On Tue, May 04, 2004 at 02:30:16PM -0600, Nathan Maves wrote:
: What could cause this error in Tomcat 5.0.19.
:
: 2004-05-04 14:21:02 StandardContext[/manager]HTMLManager:
: ManagerServlet.reload[/ReportViewer]
: java.lang.ThreadDeath
: at
:  
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoade 
r
: .java:1270)
: [snip]
: It happens when I place an object in the session and then click  
reload
: from the webapp manager.

Any object, or a particular object?
(especially a custom object)
Does said object do anything with threads, such as calling ::stop()?

-QM

--

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Strange message : [Fatal Error] :2:1: Content is not allowed in prolog.

2004-05-04 Thread Parsons Technical Services
Raymond,

I don't know the meaning, sorry. But:

If I were in your shoes I would replace the server.xml and web.xml with
default. And I would do it one at a time. If it fixes it then add your
changes a section at a time and continue until you find it.

Also a trick is to use a xml viewer like Internet Explorer to colorize the
file and help you pick up on any format errors.

Doug
www.parsonstechnical.com


- Original Message - 
From: STOCKHOLM, Raymond [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 3:03 AM
Subject: Strange message : [Fatal Error] :2:1: Content is not allowed in
prolog.


I am having this strange message when starting my tomcat :
Apache Tomcat/4.1.30
[Fatal Error] :2:1: Content is not allowed in prolog.

Everything else works fine.

I read that it was related to a SAXParseException,
and it seems to be related to tomcat itself,
and not any of my webapps (I removed them and I still have the message).

I have been customizing server.xml, web.xml, but they seem OK.

Does anybody knows what it means.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange message : [Fatal Error] :2:1: Content is not allowed in prolog.

2004-05-04 Thread STOCKHOLM, Raymond
Thanks for the tip Doug,
I will try to do like this,
and I guess I will eventually find out what's wrong.

Raymond

-Message d'origine-
De : Parsons Technical Services [mailto:[EMAIL PROTECTED]
Envoyé : mardi 4 mai 2004 09:19
À : Tomcat Users List
Objet : Re: Strange message : [Fatal Error] :2:1: Content is not allowed
in prolog.


Raymond,

I don't know the meaning, sorry. But:

If I were in your shoes I would replace the server.xml and web.xml with
default. And I would do it one at a time. If it fixes it then add your
changes a section at a time and continue until you find it.

Also a trick is to use a xml viewer like Internet Explorer to colorize the
file and help you pick up on any format errors.

Doug
www.parsonstechnical.com


- Original Message - 
From: STOCKHOLM, Raymond [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 3:03 AM
Subject: Strange message : [Fatal Error] :2:1: Content is not allowed in
prolog.


I am having this strange message when starting my tomcat :
Apache Tomcat/4.1.30
[Fatal Error] :2:1: Content is not allowed in prolog.

Everything else works fine.

I read that it was related to a SAXParseException,
and it seems to be related to tomcat itself,
and not any of my webapps (I removed them and I still have the message).

I have been customizing server.xml, web.xml, but they seem OK.

Does anybody knows what it means.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange message : [Fatal Error] :2:1: Content is not allowed in prolog.

2004-05-04 Thread Benjamin Armintor
This usually means that there's character content before the root
element in a document SAX is trying to parse.  Make sure you haven't
accidentally deleted any comment delimiting characters as you modified
files.

Benjamin J. Armintor
Systems Analyst
ITS-Systems: Mainframe Group
University of Texas - Austin
tele: (512) 232-6562
email: [EMAIL PROTECTED]
 


-Original Message-
From: STOCKHOLM, Raymond [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 04, 2004 2:03 AM
To: Tomcat Users List
Subject: Strange message : [Fatal Error] :2:1: Content is not allowed in
prolog.


I am having this strange message when starting my tomcat : Apache
Tomcat/4.1.30 [Fatal Error] :2:1: Content is not allowed in prolog.

Everything else works fine.

I read that it was related to a SAXParseException,
and it seems to be related to tomcat itself,
and not any of my webapps (I removed them and I still have the message).

I have been customizing server.xml, web.xml, but they seem OK.

Does anybody knows what it means.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange message : [Fatal Error] :2:1: Content is not allowed in prolog.

2004-05-04 Thread STOCKHOLM, Raymond
Thanks for your reply.

I am examining thoroughly the different xml files used by tomcat,
but haven't found anything wrong yet.
I'll keep searching...


-Message d'origine-
De : Benjamin Armintor [mailto:[EMAIL PROTECTED]
Envoyé : mardi 4 mai 2004 15:20
À : Tomcat Users List
Objet : RE: Strange message : [Fatal Error] :2:1: Content is not allowed
in prolog.


This usually means that there's character content before the root
element in a document SAX is trying to parse.  Make sure you haven't
accidentally deleted any comment delimiting characters as you modified
files.

Benjamin J. Armintor
Systems Analyst
ITS-Systems: Mainframe Group
University of Texas - Austin
tele: (512) 232-6562
email: [EMAIL PROTECTED]
 


-Original Message-
From: STOCKHOLM, Raymond [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 04, 2004 2:03 AM
To: Tomcat Users List
Subject: Strange message : [Fatal Error] :2:1: Content is not allowed in
prolog.


I am having this strange message when starting my tomcat : Apache
Tomcat/4.1.30 [Fatal Error] :2:1: Content is not allowed in prolog.

Everything else works fine.

I read that it was related to a SAXParseException,
and it seems to be related to tomcat itself,
and not any of my webapps (I removed them and I still have the message).

I have been customizing server.xml, web.xml, but they seem OK.

Does anybody knows what it means.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange message : [Fatal Error] :2:1: Content is not allowed in prolog.

2004-05-04 Thread Wade Chandler
STOCKHOLM, Raymond wrote:

Thanks for the tip Doug,
I will try to do like this,
and I guess I will eventually find out what's wrong.
Raymond

-Message d'origine-
De : Parsons Technical Services [mailto:[EMAIL PROTECTED]
Envoyé : mardi 4 mai 2004 09:19
À : Tomcat Users List
Objet : Re: Strange message : [Fatal Error] :2:1: Content is not allowed
in prolog.
Raymond,

I don't know the meaning, sorry. But:

If I were in your shoes I would replace the server.xml and web.xml with
default. And I would do it one at a time. If it fixes it then add your
changes a section at a time and continue until you find it.
Also a trick is to use a xml viewer like Internet Explorer to colorize the
file and help you pick up on any format errors.
Doug
www.parsonstechnical.com
- Original Message - 
From: STOCKHOLM, Raymond [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 3:03 AM
Subject: Strange message : [Fatal Error] :2:1: Content is not allowed in
prolog.

I am having this strange message when starting my tomcat :
Apache Tomcat/4.1.30
[Fatal Error] :2:1: Content is not allowed in prolog.
Everything else works fine.

I read that it was related to a SAXParseException,
and it seems to be related to tomcat itself,
and not any of my webapps (I removed them and I still have the message).
I have been customizing server.xml, web.xml, but they seem OK.

Does anybody knows what it means.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This is an error in your xml file.  Sometimes I get the error when I 
accidentally hit a key in the top of my file and put a character outside 
of my xml.  Just go to the top of the file and start looking for 
characters outside of the tags.  Hope that helps.

Wade



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange exception at tomcat 4.1.29 startup

2004-03-12 Thread Francois JEANMOUGIN


 I think they are, because it finds the commons-digester.jar! In fact I use
 both CATALINA_BASE and CATALINA_HOME, but Catalina.jar is in the same
 directory with the same permissions as commons-digester.jar, which is
 used, clearly.
 
 'can't understand.

For those interested, someone added old (very old) tomcat classes (3.3a) to the 
jre/lib/ext directory of the SDK installation for another application. So, those 
classes were loaded first, and made a conflict.

Just wait a minute, I have someone to kill, 'will be back later.

François (bofh).


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange exception at tomcat 4.1.29 startup

2004-03-12 Thread Shapira, Yoav

Hi,

For those interested, someone added old (very old) tomcat classes
(3.3a)
to the jre/lib/ext directory of the SDK installation for another
application. So, those classes were loaded first, and made a conflict.

Just wait a minute, I have someone to kill, 'will be back later.

Evil indeed.  Please report on how the killing went! ;)

And a good weekend to all,

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange exception at tomcat 4.1.29 startup

2004-03-11 Thread Edson Alves Pereira
Maybe path, libraries or environment variables are different.

 --
 De:   Francois JEANMOUGIN[SMTP:[EMAIL PROTECTED]
 Responder:Tomcat Users List
 Enviada:  quinta-feira, 11 de março de 2004 8:32
 Para: Tomcat Users List
 Assunto:  Strange exception at tomcat 4.1.29 startup
 
 Hi all,
 
 I really can't find what I've done wrong in copying the tomcat
 environement from one machine to another. I have this exception (with
 standard server.xml) :
 
 Mar 11, 2004 12:29:36 PM org.apache.commons.digester.Digester startElement
 SEVERE: Begin event threw exception
 java.lang.ClassNotFoundException: org.apache.catalina.core.StandardServer
 at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
 at
 org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java:2
 52)
 at org.apache.commons.digester.Rule.begin(Rule.java:200)
 at
 org.apache.commons.digester.Digester.startElement(Digester.java:1273)
 at
 org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
 at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
 Source)
 at
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unk
 nown Source)
 at
 org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootEl
 ementHook(Unknown Source)
 at
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispa
 tcher.dispatch(Unknown Source)
 at
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
 Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
 Source)
 at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
 Source)
 at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
 at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
 Source)
 at org.apache.commons.digester.Digester.parse(Digester.java:1548)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:449)
 at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
 at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
 39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
 pl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
 
 Any help appreciated.
 
 François.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


RE: Strange exception at tomcat 4.1.29 startup

2004-03-11 Thread FRANCOIS Dufour
java.lang.ClassNotFoundException class not found  java_home path  maybee!


[EMAIL PROTECTED]
administrateur http://entre-nous.qc.tc




From: Edson Alves Pereira [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Subject: RE: Strange exception at tomcat 4.1.29 startup
Date: Thu, 11 Mar 2004 10:23:18 -0300
	Maybe path, libraries or environment variables are different.

 --
 De: 	Francois JEANMOUGIN[SMTP:[EMAIL PROTECTED]
 Responder: 	Tomcat Users List
 Enviada: 	quinta-feira, 11 de março de 2004 8:32
 Para: 	Tomcat Users List
 Assunto: 	Strange exception at tomcat 4.1.29 startup

 Hi all,

 I really can't find what I've done wrong in copying the tomcat
 environement from one machine to another. I have this exception (with
 standard server.xml) :

 Mar 11, 2004 12:29:36 PM org.apache.commons.digester.Digester 
startElement
 SEVERE: Begin event threw exception
 java.lang.ClassNotFoundException: 
org.apache.catalina.core.StandardServer
 at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
 at
 
org.apache.commons.digester.ObjectCreateRule.begin(ObjectCreateRule.java:2
 52)
 at org.apache.commons.digester.Rule.begin(Rule.java:200)
 at
 org.apache.commons.digester.Digester.startElement(Digester.java:1273)
 at
 org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
 at 
org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown
 Source)
 at
 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unk
 nown Source)
 at
 
org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootEl
 ementHook(Unknown Source)
 at
 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispa
 tcher.dispatch(Unknown Source)
 at
 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
 Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
 Source)
 at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown
 Source)
 at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
 at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
 Source)
 at 
org.apache.commons.digester.Digester.parse(Digester.java:1548)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:449)
 at 
org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
 at 
org.apache.catalina.startup.Catalina.process(Catalina.java:180)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
 39)
 at
 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
 pl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at 
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)

 Any help appreciated.

 François.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

_
MSN Search, le moteur de recherche qui pense comme vous !  
http://fr.ca.search.msn.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange exception at tomcat 4.1.29 startup

2004-03-11 Thread Francois JEANMOUGIN


 -Original Message-
 From: Edson Alves Pereira [mailto:[EMAIL PROTECTED]
 Sent: Thursday, March 11, 2004 2:23 PM
 To: 'Tomcat Users List'
 Subject: RE: Strange exception at tomcat 4.1.29 startup
 
   Maybe path, libraries or environment variables are different.

Well, maybe, but it clearly find most of the classes (common digesters and so on). So, 
what is the jar I need for this StandardServer to work ?

François.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange exception at tomcat 4.1.29 startup

2004-03-11 Thread Francois JEANMOUGIN
To be clear, in the beginning of the exception, you see that 
org.apache.commons.digester.Digester is loaded. It is in the file :
server/lib/commons-digester.jar

StandardServer is in the file :
server/lib/catalina.jar
(unzip tells me everything is fine in this jar :
testing: org/apache/catalina/core/StandardServer.class   OK)

So why the hell isn't it loaded at startup ? It is in the same directory  and should 
known by the tomcat classloader, no ?

François.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange exception at tomcat 4.1.29 startup

2004-03-11 Thread Mike Curwen
did you copy the startup scripts as well, from the old machine, and did
you alter those scripts at all on the old machine (so perhaps now, a
path has changed). Have you double checked that CATALINA_HOME, JAVA_HOME
etc. are all appropriate ?  

 -Original Message-
 From: Francois JEANMOUGIN 
 [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, March 11, 2004 8:42 AM
 To: Tomcat Users List
 Subject: RE: Strange exception at tomcat 4.1.29 startup
 
 
 To be clear, in the beginning of the exception, you see that 
 org.apache.commons.digester.Digester is loaded. It is in the 
 file : server/lib/commons-digester.jar
 
 StandardServer is in the file :
 server/lib/catalina.jar
 (unzip tells me everything is fine in this jar :
 testing: org/apache/catalina/core/StandardServer.class   OK)
 
 So why the hell isn't it loaded at startup ? It is in the 
 same directory  and should known by the tomcat classloader, no ?
 
 François.
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange exception at tomcat 4.1.29 startup

2004-03-11 Thread Francois JEANMOUGIN


 -Original Message-
 From: Mike Curwen [mailto:[EMAIL PROTECTED]
 Sent: Thursday, March 11, 2004 4:10 PM
 To: 'Tomcat Users List'
 Subject: RE: Strange exception at tomcat 4.1.29 startup
 
 did you copy the startup scripts as well, from the old machine, and did
 you alter those scripts at all on the old machine (so perhaps now, a
 path has changed). Have you double checked that CATALINA_HOME, JAVA_HOME
 etc. are all appropriate ?

I think they are, because it finds the commons-digester.jar! In fact I use both 
CATALINA_BASE and CATALINA_HOME, but Catalina.jar is in the same directory with the 
same permissions as commons-digester.jar, which is used, clearly.

'can't understand.

François.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange Session id behavior

2004-01-30 Thread Remy Maucherat
Gretar Simonarson wrote:
I'm maintaining a JSP/servlet web using SSL, running on Apache 2.0.48 
and Tomcat
5.0.18.
Cookies are used for session identifier communication (not url rewriting).

Some users using the web are experiencing very strange session id 
behaviour, the
behaviour is like this:
When these users make their first request to the web, they already have an
session id that is invalid, i.e. request.getRequestedSessionId() is not 
null and
the id is not a session id that has been recently created by Tomcat (I've a
session listener in Tomcat that logs session creation and destruction).
As expected, Tomcat creates a new session id for the users (because the 
session
id is invalid) but the next requests from the users do not use that 
session id
but instead continue to use the session id that they used in the first 
request.
So Tomcat continues to create new session ids for each request, example:

request.getRequestedSessionId() - request.getSession(false).getId() 
request.getRequestURI()
01A960C22480CE9F445CDE48DE333F31 - 451BA13F85AE631148022C93DFDD2811 - 
/first_request.jsp

01A960C22480CE9F445CDE48DE333F31 - CBF44C3C065502D6397BC44A7AB659F9 - 
/second_request.jsp

01A960C22480CE9F445CDE48DE333F31 - 6453C03AF5DD2B9EA1F27D225589E8B2 - 
/third_request.jsp

01A960C22480CE9F445CDE48DE333F31 - 93F173966F28A972A2E70C32CC8E848B - 
/fourth_request.jsp

If the users close their browser and try again - they (most often) 
continue to
have the same problem but request.getRequestedSessionId() is not the 
same as it
was at last time...

What could be the reason for this behaviour?
I already answered to your bug report, I think.

--
x
Rémy Maucherat
Developer  Consultant
JBoss Group (Europe) SàRL
x
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Strange Problem

2004-01-28 Thread pavan . k

this is not the list to post this question...
pls avoid cross posting

Pavan Kumar
Tata Consultancy Services
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.comDISCLAIMER: The information contained in this message is intended only and solely for 
the addressed individual or entity indicated in this message and for the exclusive use 
of the said addressed individual or entity indicated in this message (or responsible 
for delivery
of the message to such person) and may contain legally privileged and confidential 
information belonging to Tata Consultancy Services. It must not be printed, read, 
copied, disclosed, forwarded, distributed or used (in whatsoever manner) by any person 
other than the addressee. 
Unauthorized use, disclosure or copying is strictly prohibited and may constitute 
unlawful act and can possibly attract legal action, civil and/or criminal. The 
contents of this message need not necessarily reflect or endorse the views of Tata 
Consultancy Services on any subject matter.
Any action taken or omitted to be taken based on this message is entirely at your risk 
and neither the originator of this message nor Tata Consultancy Services takes any 
responsibility or liability towards the same. Opinions, conclusions and any other 
information contained in this message
that do not relate to the official business of Tata Consultancy Services shall be 
understood as neither given nor endorsed by Tata Consultancy Services or any affiliate 
of Tata Consultancy Services. If you have received this message in error, you should 
destroy this message and may please notify the sender by e-mail. Thank you.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: strange error messages in tomcat log and mod_jk2 log

2003-12-16 Thread Altankov Peter
My production server setup is Apache/1.3.19 (built on HP-UX)mod_ssl/mod_jk/tomcat 
4.1.29 on a separate machine
I have a moderate loads of 5-10 hits per second and no really big responses (no more 
than 300k)
What I know so far is that this is caused by an attempt by the coyote connector to 
write in a already closed by the mod_jk socked.
The hints I have so far:
1. some proxy servers in the middle might explicitly close lenghty collections
2. lotso ppl blame users pressing stop button in browser!?
3. I follwed some forum thread somewhere (cant remember now) where the guys had 
observed as a weird bahaviour of Windows IE. They had narrowed the log entry 
appearances to a hit to a page where the request was submited like this:
a href=blah/blah.html onclick=if (boolean_exp) some_form.submit()
They were saying that the IE evaluates the onclick and submits the form, at the same 
time requests the blah/blah.html document, and THEN decides that the blah/blah.html 
document is not needed and just closes the socket. The guys also were saying that such 
a behaviour was not observed while tested with Mozzila and Opera browsers. They have 
been able to avoid it just by making the onclick event handler return false:
a href=blah/blah.html onclick=if (boolean_exp) some_form.submit(); return 
false
Though, I have not tested it myself.


-Original Message-
From: Chris Joelly [mailto:[EMAIL PROTECTED] 
Sent: 15  2003 . 10:31
To: Tomcat Users List
Subject: Re: strange error messages in tomcat log and mod_jk2 log


Hi!

thanx for your reply. hm. it's a very strange thing.

some questions:

are you running your application under heavy load?
are the responses very big in size?
do you use the apache2/mod_jk2/tomcat4 config on a windows nt4 box? does a dialogbox 
appear on the server with an error message stateing that the apache.exe caused an 
internal error, and after pressing Ok the apache2 server continues to run?

maybe we can find some similarities.

we have no idea what direction to look for, and the problem is very critical because a 
very big application is crashing every few minutes, so a production environment 
couldn't be setup... :-((

thx, Chris

Am Fri, Dec 12, 2003 at 01:46:13PM +0200, Altankov Peter meinte:
 Hi!
 Im gettting a similar traces in catalina.out:
 
 Dec 11, 2003 8:00:03 PM org.apache.jk.server.JkCoyoteHandler action
 SEVERE: Error in action code
 java.net.SocketException: Broken pipe
 at java.net.SocketOutputStream.socketWrite0(Native Method)
 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
 at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457)
 at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654)
 at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:435)
 at org.apache.coyote.Response.action(Response.java:222)
 at org.apache.coyote.Response.finish(Response.java:343)
 at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:314)
 at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387)
 at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673)
 at 
 org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615)
 at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
 at 
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
 at java.lang.Thread.run(Thread.java:536)
 
 Acompanied with this in mod_jk.log:
 [Thu Dec 11 20:38:39 2003]  [jk_ajp13_worker.c (381)]: Error 
 ajp13_process_callback - write failed (in my config they run on 
 separate UNIX boxes and unfortunately the one is 38 minutes ahead in 
 time )
 
 I have no clue what might be causing it. Posted it coupleof times but 
 got no comments. Although my tomcat don?t seem to crash, I don?t 
 consider it?s a normal situation.
 
 Any ideas someone?
 Thanks in advance!

-- 
mit freundlichen Gren / with kind regards
 
Ing. Christian Jlly @ Solutions
unycom  Information Technology Services GmbH
A-8042 Graz | Schmiedlstrae 1 / III

Tel: ++43 (0)316 / 818 828 - 30
Fax: ++43 (0)316 / 818 828 - 38
[EMAIL PROTECTED]
http://www.unycom.com

Ein Physiker, ein Mathematiker und ein Windows-Programmierer fahren in einem Auto, als 
dieses pltzlich der Geist aufgibt. Der Physiker schlgt vor, mal das Benzin zu 
kontrollieren.  Der Mathematiker sagt, er verstehe nicht viel von Autos, aber man 
solle mal das Khlwasser berprfen. Der Windows-Programmierer meint, er wrde 
zuerst alle Fenster schlieen, aussteigen, erneut einsteigen und dann alle Fenster 
wieder ffnen.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: strange error messages in tomcat log and mod_jk2 log

2003-12-15 Thread Chris Joelly
Hi!

thanx for your reply. hm. it's a very strange thing.

some questions:

are you running your application under heavy load?
are the responses very big in size?
do you use the apache2/mod_jk2/tomcat4 config on a windows nt4 box?
does a dialogbox appear on the server with an error message stateing
that the apache.exe caused an internal error, and after pressing Ok the
apache2 server continues to run?

maybe we can find some similarities.

we have no idea what direction to look for, and the problem is very
critical because a very big application is crashing every few minutes,
so a production environment couldn't be setup... :-((

thx, Chris

Am Fri, Dec 12, 2003 at 01:46:13PM +0200, Altankov Peter meinte:
 Hi!
 Im gettting a similar traces in catalina.out:
 
 Dec 11, 2003 8:00:03 PM org.apache.jk.server.JkCoyoteHandler action
 SEVERE: Error in action code
 java.net.SocketException: Broken pipe
 at java.net.SocketOutputStream.socketWrite0(Native Method)
 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
 at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457)
 at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654)
 at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:435)
 at org.apache.coyote.Response.action(Response.java:222)
 at org.apache.coyote.Response.finish(Response.java:343)
 at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:314)
 at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387)
 at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673)
 at 
 org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615)
 at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
 at 
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
 at java.lang.Thread.run(Thread.java:536)
 
 Acompanied with this in mod_jk.log:
 [Thu Dec 11 20:38:39 2003]  [jk_ajp13_worker.c (381)]: Error ajp13_process_callback 
 - write failed
 (in my config they run on separate UNIX boxes and unfortunately the one is 38 
 minutes ahead in time )
 
 I have no clue what might be causing it. Posted it coupleof times but got no 
 comments.
 Although my tomcat don?t seem to crash, I don?t consider it?s a normal situation.
 
 Any ideas someone?
 Thanks in advance!

-- 
mit freundlichen Grüßen / with kind regards
 
Ing. Christian Jölly @ Solutions
unycom  Information Technology Services GmbH
A-8042 Graz | Schmiedlstraße 1 / III

Tel: ++43 (0)316 / 818 828 - 30
Fax: ++43 (0)316 / 818 828 - 38
[EMAIL PROTECTED]
http://www.unycom.com

Ein Physiker, ein Mathematiker und ein Windows-Programmierer fahren in
einem Auto, als dieses plötzlich der Geist aufgibt. Der Physiker
schlägt vor, mal das Benzin zu kontrollieren.  Der Mathematiker sagt,
er verstehe nicht viel von Autos, aber man solle mal das Kühlwasser
überprüfen. Der Windows-Programmierer meint, er würde zuerst alle
Fenster schließen, aussteigen, erneut einsteigen und dann alle
Fenster wieder öffnen.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange error messages in tomcat log and mod_jk2 log

2003-12-12 Thread Chris Joelly
Hello again!

has anybody expirienced the same error messages in his log files? i
can't figure out whats going on and need help soon, because the server
crashes very often :-| 

thxalot, Chris

-- 
mit freundlichen Grüßen / with kind regards
 
Ing. Christian Jölly @ Solutions
unycom  Information Technology Services GmbH
A-8042 Graz | Schmiedlstraße 1 / III

Tel: ++43 (0)316 / 818 828 - 30
Fax: ++43 (0)316 / 818 828 - 38
[EMAIL PROTECTED]
http://www.unycom.com

Wie man sein Kind nicht nennen sollte: 
  Otto Motor 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: strange error messages in tomcat log and mod_jk2 log

2003-12-12 Thread Altankov Peter
Hi!
Im gettting a similar traces in catalina.out:

Dec 11, 2003 8:00:03 PM org.apache.jk.server.JkCoyoteHandler action
SEVERE: Error in action code
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:457)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:654)
at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:435)
at org.apache.coyote.Response.action(Response.java:222)
at org.apache.coyote.Response.finish(Response.java:343)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:314)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
at java.lang.Thread.run(Thread.java:536)

Acompanied with this in mod_jk.log:
[Thu Dec 11 20:38:39 2003]  [jk_ajp13_worker.c (381)]: Error ajp13_process_callback - 
write failed
(in my config they run on separate UNIX boxes and unfortunately the one is 38 minutes 
ahead in time )

I have no clue what might be causing it. Posted it coupleof times but got no comments.
Although my tomcat dont seem to crash, I dont consider its a normal situation.

Any ideas someone?
Thanks in advance!


-Original Message-
From: Chris Joelly [mailto:[EMAIL PROTECTED] 
Sent: 11  2003 . 12:30
To: [EMAIL PROTECTED]
Subject: strange error messages in tomcat log and mod_jk2 log


Hello!

i found some strange error messages in both tomcat log and mod_jk2 log and i can't 
figure out whats going on:

tomcat log:

Dec 10, 2003 11:40:58 AM org.apache.jk.server.JkCoyoteHandler action

SEVERE: Error in action code

java.net.SocketException: Software caused connection abort: socket write error

 at java.net.SocketOutputStream.socketWrite0(Native Method)
 at java.net.SocketOutputStream.socketWrite (SocketOutputStream.java:92)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
 at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407)
 at org.apache.jk.common.ChannelSocket.invoke (ChannelSocket.java:599)
 at org.apache.jk.server.JkCoyoteHandler.action (JkCoyoteHandler.java:385)
 at org.apache.coyote.Response.action(Response.java:222)
 at org.apache.coyote.Response.finish(Response.java:343)
 at org.apache.coyote.tomcat4.OutputBuffer.close (OutputBuffer.java:326)
 at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse 
(CoyoteResponse.java:500)
 at org.apache.coyote.tomcat4.CoyoteAdapter.service 
(CoyoteAdapter.java:224)
 at org.apache.jk.server.JkCoyoteHandler.invoke (JkCoyoteHandler.java:263)
 at org.apache.jk.common.HandlerRequest.invoke (HandlerRequest.java:360)
 at org.apache.jk.common.ChannelSocket.invoke (ChannelSocket.java:604)
 at org.apache.jk.common.ChannelSocket.processConnection 
(ChannelSocket.java:562)
 at org.apache.jk.common.SocketConnection.runIt (ChannelSocket.java:679)
 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run 
(ThreadPool.java:619)
 at java.lang.Thread.run(Thread.java:536)

Dec 10, 2003 11:40:58 AM org.apache.jk.server.JkCoyoteHandler action

SEVERE: Error in action code

java.net.SocketException: Software caused connection abort: socket write error

 at java.net.SocketOutputStream.socketWrite0(Native Method)
 at java.net.SocketOutputStream.socketWrite (SocketOutputStream.java:92)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
 at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407)
 at org.apache.jk.common.ChannelSocket.invoke (ChannelSocket.java:599)
 at org.apache.jk.server.JkCoyoteHandler.action (JkCoyoteHandler.java:385)
 at org.apache.coyote.Response.action(Response.java:222)
 at org.apache.coyote.Response.finish(Response.java:343)
 at org.apache.jk.server.JkCoyoteHandler.invoke (JkCoyoteHandler.java:268)
 at org.apache.jk.common.HandlerRequest.invoke (HandlerRequest.java:360)
 at org.apache.jk.common.ChannelSocket.invoke (ChannelSocket.java:604)
 at org.apache.jk.common.ChannelSocket.processConnection 
(ChannelSocket.java:562)
 at org.apache.jk.common.SocketConnection.runIt (ChannelSocket.java:679)
 

RE: Strange number of processes....

2003-12-10 Thread Ralph Einfeldt
First of all keep in mind that it aren't processes, they are 
threads. As the threads share the same memory they do not 
use much additionals memory (some memory for the thread local
objects and the thread stack and so on)

I can't explain all your numbers.

- Even the simplest java program has more than one thread.
  Depending on the vendor and the vm version you may have 
  several threads. (Mine has 'Finalizer', 'Reference Handler',
  'Suspend Checker Thread', 'VM Periodic Task Thread', 
  'VM Thread', 'Signal Dispatcher' and 'main')

- Tomcat uses some threads as monitors. The number of monitors 
  depends on the tomcat version and the services you enable/disable

- There might be no relation between minProcessors and the number
  of threads, as it's tomcat's choice if and when additional threads
  are created (which may be stored in a thread pool for later reuse).

- If you set minProcessors = maxProcessors this might give a better 
  relation to the number of threads but there is no contract that
  enforces tomcat (or any other servlet container) to limit it self
  to a certain amount of threads.

- If you want to know what the threads are doing, you can issue a 
  'kill -QUIT jvm-pid' and look at the stacktrace in catalina.out. 
  (the thread names give a good hint about purpose)

 -Original Message-
 From: Scott Queen [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, December 10, 2003 2:12 AM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Strange number of processes
 
 
 Ok I'm running Tomcat 4.1.18 as a standalone server on a Linux box.
 I've configured 6 virtual hosts in the Tomcat-Standalone 
 server having a
 non-SSL Coyote HTTP/1.1 Connector (probably obvious) and a Coyote/JK2
 AJP 1.3 Connector (I don't think this is used, but I'm not
 sureunfortunately reveals my lack of experise!).
 
 I'm confused with the number of java processes spawned when I start
 Tomcat.  Here is what I see:
  # of initial
 minProcessors |  maxProcessors |  java processes | comments
1   |  1   | 25
   | can't
 get a page
1   |  2   | 27
   | pages
 served to 1 session
2   |  4   | 31
4   |  4   | 31  | slow
 response, 1 session at a time
4   |  7   | 31  | 3
 sessions respond, 4 add'l java procs created
5   |  7   | 31  | same
 as above
4   | 20  | 31  | 5
 sessions respond (all tested), 9 add'l java procs 
 
 So. First question:  why are there so many java processes when I
 specify only a few minProcessors (i.e. 1 minProc, 1 maxProc, 6 virtual
 hosts - I would expect 6 java sessions)?  Second question: 
 why isn't the
 number of initial java processes a linear relationship relative to the
 number of minProcessors specified?
 
 I'm concerned about this because in the end, only about half the
 processes are ever used, but they all take up a significant amount of
 memory.  How do I reduce the memory utilization?
 
 Thanks,
 Scott Queen
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: strange output in localhost_log

2003-12-10 Thread Jeanfrancois Arcand
You probably have some left over from an unsucessful deployment. This 
exception means the Context(your app) wasn't started properly and Tomcat 
is now trying to stop it.

-- Jeanfrancois

Luc Foisy wrote:

First, what would cause this output in my localhost_log file? Is this a tomcat shutdown?

2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/admin
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/webdav
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/qbsottweblive2
2003-12-09 21:09:36 StandardHost[localhost]: ContainerBase.removeChild: stop:
LifecycleException:  Container StandardContext[/qbsottweblive2] has not been started
   at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
   at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
   at 
org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.java:420)
   at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
   at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919)
   at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:899)
   at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:370)
   at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
   at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221)
   at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
   at org.apache.catalina.core.StandardService.stop(StandardService.java:554)
   at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224)
   at 
org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:624)
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/qbsottweblive
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/tomcat-docs
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/quicktrack
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/quick
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/portalbackup
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/manager
Second, what would cause this output in my localhost_log file?

2003-12-07 12:55:26 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-07 14:06:26 StandardHost[localhost]: MAPPING configuration error for request 
URI /mstshash=cmpherson
2003-12-07 19:39:57 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-07 20:09:48 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-09 00:48:25 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-09 04:38:39 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-09 07:44:43 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 07:44:43 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 10:18:06 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 11:05:12 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 13:23:20 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 13:26:35 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 13:26:35 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 14:15:17 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 14:15:17 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 14:43:52 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-10 07:54:12 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-10 07:54:12 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-10 09:00:28 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: strange output in localhost_log

2003-12-10 Thread Luc Foisy
It wasn't actually the exception I was concerned about. It was the fact that it 
appears that tomcat is shuting down (is that what it looks like?) when its completely 
not expected to.

As well I was concerned over the second set of log entries, what is this MAPPING 
thing, and why would it be refering to those things, none of those files exist. Can 
this be indication that someone is trying to get to those things some how, or are they 
 normal tomcat log entries for some strange reason?

-Original Message-
From: Jeanfrancois Arcand [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 9:33 AM
To: Tomcat Users List
Subject: Re: strange output in localhost_log


You probably have some left over from an unsucessful deployment. This 
exception means the Context(your app) wasn't started properly and Tomcat 
is now trying to stop it.

-- Jeanfrancois

Luc Foisy wrote:

First, what would cause this output in my localhost_log file? Is this a tomcat 
shutdown?

2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/admin
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/webdav
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/qbsottweblive2
2003-12-09 21:09:36 StandardHost[localhost]: ContainerBase.removeChild: stop:
LifecycleException:  Container StandardContext[/qbsottweblive2] has not been started
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
at 
 org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.java:420)
at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:899)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:370)
at 
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
at org.apache.catalina.core.StandardService.stop(StandardService.java:554)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224)
at 
 org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:624)

2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/qbsottweblive
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/tomcat-docs
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/quicktrack
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/quick
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/portalbackup
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/manager

Second, what would cause this output in my localhost_log file?

2003-12-07 12:55:26 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-07 14:06:26 StandardHost[localhost]: MAPPING configuration error for request 
URI /mstshash=cmpherson
2003-12-07 19:39:57 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-07 20:09:48 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt

2003-12-09 00:48:25 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-09 04:38:39 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-09 07:44:43 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 07:44:43 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 10:18:06 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 11:05:12 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 13:23:20 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 13:26:35 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 13:26:35 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 14:15:17 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 14:15:17 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 14:43:52 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt

2003-12-10 07:54:12 StandardHost[localhost]: MAPPING configuration error for request 
URI

Re: strange output in localhost_log

2003-12-10 Thread Jeanfrancois Arcand


Luc Foisy wrote:

It wasn't actually the exception I was concerned about. It was the fact that it appears that tomcat is shuting down (is that what it looks like?) when its completely not expected to.
 

Are you running with a security manager? Tomcat die or shutdown properly?

As well I was concerned over the second set of log entries, what is this MAPPING thing, and why would it be refering to those things, none of those files exist. 

Yes, but it seems you receiving request for thoses.

Can this be indication that someone is trying to get to those things some how, or are they  normal tomcat log entries for some strange reason?
 

Like that.

-- Jeanfrancois

-Original Message-
From: Jeanfrancois Arcand [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 9:33 AM
To: Tomcat Users List
Subject: Re: strange output in localhost_log
You probably have some left over from an unsucessful deployment. This 
exception means the Context(your app) wasn't started properly and Tomcat 
is now trying to stop it.

-- Jeanfrancois

Luc Foisy wrote:

 

First, what would cause this output in my localhost_log file? Is this a tomcat shutdown?

2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/admin
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/webdav
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/qbsottweblive2
2003-12-09 21:09:36 StandardHost[localhost]: ContainerBase.removeChild: stop:
LifecycleException:  Container StandardContext[/qbsottweblive2] has not been started
  at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
  at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
  at 
org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.java:420)
  at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
  at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919)
  at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:899)
  at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:370)
  at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
  at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1221)
  at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1233)
  at org.apache.catalina.core.StandardService.stop(StandardService.java:554)
  at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2224)
  at 
org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:624)
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/qbsottweblive
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/tomcat-docs
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/quicktrack
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/quick
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/portalbackup
2003-12-09 21:09:36 StandardHost[localhost]: Removing web application at context path 
/manager
Second, what would cause this output in my localhost_log file?

2003-12-07 12:55:26 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-07 14:06:26 StandardHost[localhost]: MAPPING configuration error for request 
URI /mstshash=cmpherson
2003-12-07 19:39:57 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-07 20:09:48 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-09 00:48:25 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-09 04:38:39 StandardHost[localhost]: MAPPING configuration error for request 
URI /robots.txt
2003-12-09 07:44:43 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 07:44:43 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 10:18:06 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 11:05:12 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 13:23:20 StandardHost[localhost]: MAPPING configuration error for request 
URI /favicon.ico
2003-12-09 13:26:35 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 13:26:35 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 14:15:17 StandardHost[localhost]: MAPPING configuration error for request 
URI /_vti_bin/owssvr.dll
2003-12-09 14:15:17 StandardHost[localhost]: MAPPING configuration error for request 
URI /MSOffice/cltreq.asp
2003-12-09 14:43:52 StandardHost[localhost

RE: Strange GET error with recent linux upgrade.

2003-12-01 Thread Brian Menke
I didn't get a response on this, but I did solve the problem and thought I
would pass it on just in case someone else runs into something similar.

I found out that the web.xml file was an older version that used an older
DTD (2.2). It was tied to an older version of tomcat. I think around tomcat
2.something. 

When they upgraded to the latest red hat enterprise linux, they were using
tomcat 4.1.29. The 2.3 DTD that is used by 4.1.29 includes the
servlet-mapping/servlet-mapping tags that let you specify the
url-pattern for your servlets. As soon as I upgraded the web.xml file to the
new version, and included the servlet-mapping, everything worked perfectly. 

I still don't understand why I got the original error message:

HTTP Status 405 - HTTP method GET is not supported by this URL

I would have expected a servlet not available message if tomcat couldn't
find it because the web.xml file was wrong?

-Brian 

-Original Message-
From: Brian Menke [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, November 26, 2003 10:47 AM
To: 'Tomcat Users List'
Subject: Strange GET error with recent linux upgrade.

Hi Everyone,

I have a client that just upgraded their Linux to the latest redhat
enterprise linux. They had a bunch of servlets that all worked with the
previous version just fine. Those servlets handled both post and get
request. After the update, all the servlets now display the following
message:

HTTP Status 405 - HTTP method GET is not supported by this URL

I think they just used what ever versions of java, tomcat etc. that came
with linux. I'm not real familiar with linux, or if this is even a linux
problem. Just wonder if there is something obvious that may have caused this
that someone may be aware of? Any insight is greatly appreciated.

Happy Thanksgiving everyone.

-Brian


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange file explorer errors since 4.1.29 installed.

2003-11-25 Thread Charles Gardner
  I have been developing with tomcat 3.3.1 running on both windows 2000
(professional (but not server version)) and solaris for close to a year now.
I have had no problems most likely because the stuff I am doing is
relatively simple types of things at the present.  I installed 4.1.29 last
weekend mostly because I dont like to get too far behind and I was picking
up strange socket error on unix.  Someone suggested I move to the newer
version.  When I installed and ran it sunday night and monday all of a
sudden my file explorer would get an error and exit about every 10-15
minutes.  I thought, virus or disk error so I scanned by disk for errors and
viruses.  It found nothing.  I reset my environment back to the 3.3.1 and
ran the rest of the day and this morning with out any file explorer errors.
Later today I plan to set my environment back to 4.x and see if the errors
start happening again.

   Has anyone else had any experience with this type of problem?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange behavior of runtime.exec(...)

2003-11-10 Thread Stefan Frank
I tried to tweak the security manager of tomcat(using no restrictions at 
all) - with no effect. And I have absolutely no idea how to set the 
security-settings for the Webapp: And if i knew, does anyone know if 
there is a level of control below the reight to call runtime.exec()?! I 
mean, if the webapp is allowed to spawn a process, can i restrict the 
abilities of this spawned process?! And in a platform independent 
matter?! Or is there a bug somwehere else?!
Patrick Willart wrote:

I suspect the problem to be that no external task that is started by Tomcat
is allowed to open any connections.
I had a similar problem with cgi and a windows executable. The executable
tried to open a socket connection. The same setup had worked on a different
server but not on Tomcat. I ended up rewritting the program as a java
servlet. This worked.
If you setup a Security Manager for Tomcat then you can control what the
java code of your applications is allowed to do.
Grts,

Patrick
-Original Message-
From: Stefan Frank [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 08, 2003 6:52 AM
To: [EMAIL PROTECTED]
Subject: Strange behaviour of runtime.exec(...)
Hi,

we are trying to make some calls to scripts from within tomcat, so we
are using runtime.exec() inside a Servlet: The script (it submits a Job
to teh Sun Grid Engine, http://gridengine.sunsource.net/) runs fine from
the command line, and also the java-class, which is called from the
servlet for the submit, runs fine outside of tomcat: When the Class is
called from inside tomcat, the job is submitted, but never reaches the
scheduler:  It looks like the spawned process is not allowed to make up
sockets to the outside world - are there any restrictions on using
Runtime.exec() from within tomcat?! And if there is, is there a way
around these restrictions?!
Greetingsthx in advance for any help
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Strange behavior of runtime.exec(...)

2003-11-10 Thread Kwok Peng Tuck
If I'm not mistaken, the security manager is turned off by default.

Stefan Frank wrote:

I tried to tweak the security manager of tomcat(using no restrictions 
at all) - with no effect. And I have absolutely no idea how to set the 
security-settings for the Webapp: And if i knew, does anyone know if 
there is a level of control below the reight to call runtime.exec()?! 
I mean, if the webapp is allowed to spawn a process, can i restrict 
the abilities of this spawned process?! And in a platform independent 
matter?! Or is there a bug somwehere else?!
Patrick Willart wrote:

I suspect the problem to be that no external task that is started by 
Tomcat
is allowed to open any connections.

I had a similar problem with cgi and a windows executable. The 
executable
tried to open a socket connection. The same setup had worked on a 
different
server but not on Tomcat. I ended up rewritting the program as a java
servlet. This worked.

If you setup a Security Manager for Tomcat then you can control what the
java code of your applications is allowed to do.
Grts,

Patrick
-Original Message-
From: Stefan Frank [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 08, 2003 6:52 AM
To: [EMAIL PROTECTED]
Subject: Strange behaviour of runtime.exec(...)
Hi,

we are trying to make some calls to scripts from within tomcat, so we
are using runtime.exec() inside a Servlet: The script (it submits a Job
to teh Sun Grid Engine, http://gridengine.sunsource.net/) runs fine from
the command line, and also the java-class, which is called from the
servlet for the submit, runs fine outside of tomcat: When the Class is
called from inside tomcat, the job is submitted, but never reaches the
scheduler:  It looks like the spawned process is not allowed to make up
sockets to the outside world - are there any restrictions on using
Runtime.exec() from within tomcat?! And if there is, is there a way
around these restrictions?!
Greetingsthx in advance for any help
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange behavior of runtime.exec(...)

2003-11-10 Thread Patrick Willart
Stefan,

The security manager is disabled per default. In your specific case it has
nothing to do with the security manager either. The problem is that the
program/script you started with runtime.exec() doesn't have permission to
open a socket. The security manager, if enabled, could control the
permission to use .exec() and .exit() methods in your java code. Not in
external scripts/programs you execute.

As I told you, I worked around this by rewriting the program in as a
servlet. I never got the original CGI program to open a socket. I think
external programs launched by Tomcat always have this restriction. Maybe one
of developers can confirm this behavior?

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/security-manager-howto.html

grts,

Patrick

-Original Message-
From: Kwok Peng Tuck [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 12:26 AM
To: Tomcat Users List
Subject: Re: Strange behavior of runtime.exec(...)


If I'm not mistaken, the security manager is turned off by default.


Stefan Frank wrote:

 I tried to tweak the security manager of tomcat(using no restrictions
 at all) - with no effect. And I have absolutely no idea how to set the
 security-settings for the Webapp: And if i knew, does anyone know if
 there is a level of control below the reight to call runtime.exec()?!
 I mean, if the webapp is allowed to spawn a process, can i restrict
 the abilities of this spawned process?! And in a platform independent
 matter?! Or is there a bug somwehere else?!
 Patrick Willart wrote:

 I suspect the problem to be that no external task that is started by
 Tomcat
 is allowed to open any connections.

 I had a similar problem with cgi and a windows executable. The
 executable
 tried to open a socket connection. The same setup had worked on a
 different
 server but not on Tomcat. I ended up rewritting the program as a java
 servlet. This worked.

 If you setup a Security Manager for Tomcat then you can control what the
 java code of your applications is allowed to do.

 Grts,

 Patrick
 -Original Message-
 From: Stefan Frank [mailto:[EMAIL PROTECTED]
 Sent: Saturday, November 08, 2003 6:52 AM
 To: [EMAIL PROTECTED]
 Subject: Strange behaviour of runtime.exec(...)


 Hi,

 we are trying to make some calls to scripts from within tomcat, so we
 are using runtime.exec() inside a Servlet: The script (it submits a Job
 to teh Sun Grid Engine, http://gridengine.sunsource.net/) runs fine from
 the command line, and also the java-class, which is called from the
 servlet for the submit, runs fine outside of tomcat: When the Class is
 called from inside tomcat, the job is submitted, but never reaches the
 scheduler:  It looks like the spawned process is not allowed to make up
 sockets to the outside world - are there any restrictions on using
 Runtime.exec() from within tomcat?! And if there is, is there a way
 around these restrictions?!

 Greetingsthx in advance for any help
 Stefan


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]







 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange behavior of runtime.exec(...)

2003-11-10 Thread Stefan Frank
Thank you Patrick,
after opening up all permissions for the web-app following your advice 
we finally found the reason in a bug in the ypbind of the machine 
running tomcat: so my guess, that spawned processes are restricted in 
any way were obviously wrong - especially there does not seem to be a 
way of restricting spawned processes. Either you are granted permission 
to exec  or not, but nothing in between (this is fine by me, we are just 
happy to have our exec's run smooth again...)
thx for the help
stf



Patrick Willart wrote:

Stefan,

The security manager is disabled per default. In your specific case it has
nothing to do with the security manager either. The problem is that the
program/script you started with runtime.exec() doesn't have permission to
open a socket. The security manager, if enabled, could control the
permission to use .exec() and .exit() methods in your java code. Not in
external scripts/programs you execute.
As I told you, I worked around this by rewriting the program in as a
servlet. I never got the original CGI program to open a socket. I think
external programs launched by Tomcat always have this restriction. Maybe one
of developers can confirm this behavior?
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/security-manager-howto.html

grts,

Patrick

-Original Message-
From: Kwok Peng Tuck [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 12:26 AM
To: Tomcat Users List
Subject: Re: Strange behavior of runtime.exec(...)
If I'm not mistaken, the security manager is turned off by default.

Stefan Frank wrote:

 

I tried to tweak the security manager of tomcat(using no restrictions
at all) - with no effect. And I have absolutely no idea how to set the
security-settings for the Webapp: And if i knew, does anyone know if
there is a level of control below the reight to call runtime.exec()?!
I mean, if the webapp is allowed to spawn a process, can i restrict
the abilities of this spawned process?! And in a platform independent
matter?! Or is there a bug somwehere else?!
Patrick Willart wrote:
   

I suspect the problem to be that no external task that is started by
Tomcat
is allowed to open any connections.
I had a similar problem with cgi and a windows executable. The
executable
tried to open a socket connection. The same setup had worked on a
different
server but not on Tomcat. I ended up rewritting the program as a java
servlet. This worked.
If you setup a Security Manager for Tomcat then you can control what the
java code of your applications is allowed to do.
Grts,

Patrick
-Original Message-
From: Stefan Frank [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 08, 2003 6:52 AM
To: [EMAIL PROTECTED]
Subject: Strange behaviour of runtime.exec(...)
Hi,

we are trying to make some calls to scripts from within tomcat, so we
are using runtime.exec() inside a Servlet: The script (it submits a Job
to teh Sun Grid Engine, http://gridengine.sunsource.net/) runs fine from
the command line, and also the java-class, which is called from the
servlet for the submit, runs fine outside of tomcat: When the Class is
called from inside tomcat, the job is submitted, but never reaches the
scheduler:  It looks like the spawned process is not allowed to make up
sockets to the outside world - are there any restrictions on using
Runtime.exec() from within tomcat?! And if there is, is there a way
around these restrictions?!
Greetingsthx in advance for any help
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange behavior of runtime.exec(...)

2003-11-08 Thread Patrick Willart
I suspect the problem to be that no external task that is started by Tomcat
is allowed to open any connections.

I had a similar problem with cgi and a windows executable. The executable
tried to open a socket connection. The same setup had worked on a different
server but not on Tomcat. I ended up rewritting the program as a java
servlet. This worked.

If you setup a Security Manager for Tomcat then you can control what the
java code of your applications is allowed to do.

Grts,

Patrick
-Original Message-
From: Stefan Frank [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 08, 2003 6:52 AM
To: [EMAIL PROTECTED]
Subject: Strange behaviour of runtime.exec(...)


Hi,

we are trying to make some calls to scripts from within tomcat, so we
are using runtime.exec() inside a Servlet: The script (it submits a Job
to teh Sun Grid Engine, http://gridengine.sunsource.net/) runs fine from
the command line, and also the java-class, which is called from the
servlet for the submit, runs fine outside of tomcat: When the Class is
called from inside tomcat, the job is submitted, but never reaches the
scheduler:  It looks like the spawned process is not allowed to make up
sockets to the outside world - are there any restrictions on using
Runtime.exec() from within tomcat?! And if there is, is there a way
around these restrictions?!

Greetingsthx in advance for any help
Stefan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange behavior of runtime.exec(...)

2003-11-08 Thread Stefan Frank
uuh, this sounds not too good - do you have any ideas where to start 
with setting up the security manager for the Web-App?! Is this a problem 
of tomcat and setting another securitymanager for the bootstrap-process 
will help or do I have to tell it to the Web-App?! Are there any 
examples for this somewhere - alas i think we cannot re-write this 
sge-stuff, so i have to fix it in another way...
Patrick Willart wrote:

I suspect the problem to be that no external task that is started by Tomcat
is allowed to open any connections.
I had a similar problem with cgi and a windows executable. The executable
tried to open a socket connection. The same setup had worked on a different
server but not on Tomcat. I ended up rewritting the program as a java
servlet. This worked.
If you setup a Security Manager for Tomcat then you can control what the
java code of your applications is allowed to do.
Grts,

Patrick
-Original Message-
From: Stefan Frank [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 08, 2003 6:52 AM
To: [EMAIL PROTECTED]
Subject: Strange behaviour of runtime.exec(...)
Hi,

we are trying to make some calls to scripts from within tomcat, so we
are using runtime.exec() inside a Servlet: The script (it submits a Job
to teh Sun Grid Engine, http://gridengine.sunsource.net/) runs fine from
the command line, and also the java-class, which is called from the
servlet for the submit, runs fine outside of tomcat: When the Class is
called from inside tomcat, the job is submitted, but never reaches the
scheduler:  It looks like the spawned process is not allowed to make up
sockets to the outside world - are there any restrictions on using
Runtime.exec() from within tomcat?! And if there is, is there a way
around these restrictions?!
Greetingsthx in advance for any help
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange behaviour with Tomcat 4.x running as a service

2003-10-16 Thread Shapira, Yoav

Howdy,
Do you have different JVM options (or JVMs altogether) between the
service and the console startup scripts?

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Michael Schuldt [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 16, 2003 2:04 PM
To: [EMAIL PROTECTED]
Subject: Strange behaviour with Tomcat 4.x running as a service

Hi,



I've got running Tomcat 4.x running as a service under Win2k. In my
application there are some threads doing some database-requests through
Objectstyle-Cayenne. Every Thread doing database requests will get a
null-pointer exception after several hundred requests. I discussed this
behaviour with the guys from objectstyle but they don't have an idea.
We
looked in the code and there is an object used. It's not null and
nothing
will be done with it. In the next row, the object should be used again
and
the it's null. Several hundred times before the code works in the right
way
and then it crashes suddenly.



I thought about an error in Cayenne. But when I'm runnig Tomcat as a
console
application everything works fine!



Am I doing something wrong?



Michael Schuldt




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange behaviour with Tomcat 4.x running as a service

2003-10-16 Thread Shapira, Yoav

Howdy,
Then perhaps the writers of the Tomcat Service Manager can help you.  As
you said, it's running fine via the console.  So the problem is with the
invocation and process control of the service.

Why -Xrs?

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Michael Schuldt [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 16, 2003 2:39 PM
To: Tomcat Users List
Subject: AW: Strange behaviour with Tomcat 4.x running as a service

I dont't set any JVM options when starting tomcat as a console app.

For starting as a service I'm using Tomcat Service Manager (3rd Party
Tool).
The only option set is -Xrs.



-Ursprungliche Nachricht-
Von: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 16. Oktober 2003 20:07
An: Tomcat Users List
Betreff: RE: Strange behaviour with Tomcat 4.x running as a service



Howdy,
Do you have different JVM options (or JVMs altogether) between the
service and the console startup scripts?

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Michael Schuldt [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 16, 2003 2:04 PM
To: [EMAIL PROTECTED]
Subject: Strange behaviour with Tomcat 4.x running as a service

Hi,



I've got running Tomcat 4.x running as a service under Win2k. In my
application there are some threads doing some database-requests
through
Objectstyle-Cayenne. Every Thread doing database requests will get a
null-pointer exception after several hundred requests. I discussed
this
behaviour with the guys from objectstyle but they don't have an idea.
We
looked in the code and there is an object used. It's not null and
nothing
will be done with it. In the next row, the object should be used again
and
the it's null. Several hundred times before the code works in the
right
way
and then it crashes suddenly.



I thought about an error in Cayenne. But when I'm runnig Tomcat as a
console
application everything works fine!



Am I doing something wrong?



Michael Schuldt




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary
and/or privileged.  This e-mail is intended only for the individual(s)
to
whom it is addressed, and may not be saved, copied, printed, disclosed
or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange behaviour with Tomcat 4.x running as a service

2003-10-16 Thread Bill Barker

Michael Schuldt [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
 I dont't set any JVM options when starting tomcat as a console app.

 For starting as a service I'm using Tomcat Service Manager (3rd Party
Tool).
 The only option set is -Xrs.


You might want to try procrun from Jakarta/commons/daemon.  I've been very
happy using it (as apposed to JavaService :).  Also, this is the Windows
service wrapper that ships by default with Tomcat 5.


 -Ursprungliche Nachricht-
 Von: Shapira, Yoav [mailto:[EMAIL PROTECTED]
 Gesendet: Donnerstag, 16. Oktober 2003 20:07
 An: Tomcat Users List
 Betreff: RE: Strange behaviour with Tomcat 4.x running as a service



 Howdy,
 Do you have different JVM options (or JVMs altogether) between the
 service and the console startup scripts?

 Yoav Shapira
 Millennium ChemInformatics


 -Original Message-
 From: Michael Schuldt [mailto:[EMAIL PROTECTED]
 Sent: Thursday, October 16, 2003 2:04 PM
 To: [EMAIL PROTECTED]
 Subject: Strange behaviour with Tomcat 4.x running as a service
 
 Hi,
 
 
 
 I've got running Tomcat 4.x running as a service under Win2k. In my
 application there are some threads doing some database-requests through
 Objectstyle-Cayenne. Every Thread doing database requests will get a
 null-pointer exception after several hundred requests. I discussed this
 behaviour with the guys from objectstyle but they don't have an idea.
 We
 looked in the code and there is an object used. It's not null and
 nothing
 will be done with it. In the next row, the object should be used again
 and
 the it's null. Several hundred times before the code works in the right
 way
 and then it crashes suddenly.
 
 
 
 I thought about an error in Cayenne. But when I'm runnig Tomcat as a
 console
 application everything works fine!
 
 
 
 Am I doing something wrong?
 
 
 
 Michael Schuldt
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 This e-mail, including any attachments, is a confidential business
 communication, and may contain information that is confidential,
proprietary
 and/or privileged.  This e-mail is intended only for the individual(s) to
 whom it is addressed, and may not be saved, copied, printed, disclosed or
 used by anyone else.  If you are not the(an) intended recipient, please
 immediately delete this e-mail from your computer system and notify the
 sender.  Thank you.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange tomcat behavior

2003-10-09 Thread Remy Maucherat
[EMAIL PROTECTED] wrote:
Hi everybody on the list!

We observed a strange tomcat behavior (tomcat 4.1.24) while running a servlet: Everything works fine some days or even weeks. Suddenly (and at random time) tomcat throws the following exceptions:

2003-10-08 11:44:48 CoyoteAdapter An exception or error occurred in the container 
during the request processing
java.lang.NullPointerException
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:164)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:484)
This exception occurs some times. Suddenly tomcat throws another exception:

2003-10-08 11:46:44 CoyoteAdapter An exception or error occurred in the container 
during the request processing
java.lang.NullPointerException
at java.lang.String.charAt(String.java:509)
at org.apache.tomcat.util.buf.ByteChunk.indexOf(ByteChunk.java:669)
at org.apache.coyote.tomcat4.CoyoteAdapter.normalize(CoyoteAdapter.java:578)
at 
org.apache.coyote.tomcat4.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:280)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:221)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:484)
Note that there are no user defined classes in the stacktrace.  What's the reason of this behavior?
The second one was weirder, so I looked into it:

For the TC 4.1.24 source:

CoyoteAdapter.java:578: index = uriBC.indexOf(/../, 0, 4, index);
For reference: ByteChunk.java:668: public int indexOf( String src, int 
srcOff, int srcLen, int myOff ) {
ByteChunk.java:669: char first=src.charAt( srcOff );

If you get a NPE inside charAt on a constant String, I think it means 
your VM has issues.

For the first one, the engine associated with the engine valve is null, 
which can't happen either, but I can't demonstrate as easily that it's 
not a Tomcat bug.

--
x
Rémy Maucherat
Senior Developer  Consultant
JBoss Group (Europe) SàRL
x
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange tomcat behavior

2003-10-09 Thread Shapira, Yoav

Howdy,
I recall having the charAt NPE -- it went away during an upgrade of the JDK (to 1.4.2) 
and tomcat (to 4.1.27).  At that time I also had them update all the Solaris OS 
patches required by the JDK.  So I don't know which was the deciding factor in the 
charAt NPE you're getting, but doing all the updates should work ;)

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 10:24 AM
To: Tomcat Users List
Subject: Re: Strange tomcat behavior

[EMAIL PROTECTED] wrote:
 Hi everybody on the list!

 We observed a strange tomcat behavior (tomcat 4.1.24) while running a
servlet: Everything works fine some days or even weeks. Suddenly (and at
random time) tomcat throws the following exceptions:

 2003-10-08 11:44:48 CoyoteAdapter An exception or error occurred in the
container during the request processing
 java.lang.NullPointerException
  at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.jav
a:164)
  at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invo
keNext(StandardPipeline.java:643)
  at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
  at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
  at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
  at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
  at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConn
ection(Http11Protocol.java:392)
  at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
  at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.ja
va:619)
  at java.lang.Thread.run(Thread.java:484)

 This exception occurs some times. Suddenly tomcat throws another
exception:

 2003-10-08 11:46:44 CoyoteAdapter An exception or error occurred in the
container during the request processing
 java.lang.NullPointerException
  at java.lang.String.charAt(String.java:509)
  at org.apache.tomcat.util.buf.ByteChunk.indexOf(ByteChunk.java:669)
  at
org.apache.coyote.tomcat4.CoyoteAdapter.normalize(CoyoteAdapter.java:578)
  at
org.apache.coyote.tomcat4.CoyoteAdapter.postParseRequest(CoyoteAdapter.java
:280)
  at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:221)
  at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
  at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConn
ection(Http11Protocol.java:392)
  at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
  at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.ja
va:619)
  at java.lang.Thread.run(Thread.java:484)

 Note that there are no user defined classes in the stacktrace.  What's
the reason of this behavior?

The second one was weirder, so I looked into it:

For the TC 4.1.24 source:

CoyoteAdapter.java:578: index = uriBC.indexOf(/../, 0, 4, index);
For reference: ByteChunk.java:668: public int indexOf( String src, int
srcOff, int srcLen, int myOff ) {
ByteChunk.java:669: char first=src.charAt( srcOff );

If you get a NPE inside charAt on a constant String, I think it means
your VM has issues.

For the first one, the engine associated with the engine valve is null,
which can't happen either, but I can't demonstrate as easily that it's
not a Tomcat bug.

--
x
Rémy Maucherat
Senior Developer  Consultant
JBoss Group (Europe) SàRL
x


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange exceptions ...

2003-10-08 Thread Shapira, Yoav

Howdy,
Most likely cause is user making a request to the server and then
closing their browser before the request is complete.  As you can see,
these are INFO (not ERROR or even WARN) message.  They can be removed by
modifying the logging configuration.

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Aleksandr Shneyderman [mailto:[EMAIL PROTECTED]
Sent: Monday, October 06, 2003 7:46 PM
To: Tomcat User List
Subject: Strange exceptions ...


We are getting some really strange exceptions like the ones below.
can someone explain what they mean and how do I fix it?
I am getting them in my logs and I am not sure if they are affecting
the users, since they do not complain for some reason, but my gut
feeling
is that there are problems, I just can not catch them

We are using Apache SSL fornt and Tomcat 4.1.27 on the back, all on
solaris
2.8
jvm sun 1.4.1

INFO: server has been restarted or reset this connection
Oct 6, 2003 7:12:51 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: server has been restarted or reset this connection
Oct 6, 2003 7:16:32 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: server has been restarted or reset this connection
Oct 6, 2003 7:16:42 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: server has been restarted or reset this connection
Oct 6, 2003 7:16:56 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: server has been restarted or reset this connection
Oct 6, 2003 7:25:45 PM org.apache.jk.server.JkCoyoteHandler action
SEVERE: Error in action code
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at
java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407)
at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599)
at
org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:385)
at org.apache.coyote.Response.action(Response.java:222)
at org.apache.coyote.Response.finish(Response.java:343)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:268)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360)
at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java
:562
)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo
l.ja
v
a:619)
at java.lang.Thread.run(Thread.java:536)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange exceptions ...

2003-10-08 Thread Aleksandr Shneyderman
Actually I figured out what is happening and why the error
is there. It was something along the lines that you described
except user does not stop anything but for some reason images
do not get served correctly. I am not sure why. I read somewhere
on either this list or the struts list that for some unknown 
reasons in exactly the configuration  that we have (ApacheSSL-Tomcat)
the images do not get served correctly (between the mod_jk and coyote 
I guess), and I noticed that they get cut off or do not get to the client,
when I get the info message. The broken pipe happens inconsistently,
so I can not make much sence of it, but I suspect it has something to do 
with the sme problem 

It is no bigy for now since the refresh or consequent requests do 
serve the images correctly and once it is there browser does cache it,
but I would like to solve it one day, any ideas of where to start my 
complains or maybe it has been alread y solved and I am just wasting
my breath here ...

Thanks,
Alex.

 -Original Message-
 From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, October 08, 2003 8:00 AM
 To: Tomcat Users List
 Subject: RE: Strange exceptions ...
 
 
 
 Howdy,
 Most likely cause is user making a request to the server and then
 closing their browser before the request is complete.  As you can see,
 these are INFO (not ERROR or even WARN) message.  They can be removed by
 modifying the logging configuration.
 
 Yoav Shapira
 Millennium ChemInformatics
 
 
 -Original Message-
 From: Aleksandr Shneyderman [mailto:[EMAIL PROTECTED]
 Sent: Monday, October 06, 2003 7:46 PM
 To: Tomcat User List
 Subject: Strange exceptions ...
 
 
 We are getting some really strange exceptions like the ones below.
 can someone explain what they mean and how do I fix it?
 I am getting them in my logs and I am not sure if they are affecting
 the users, since they do not complain for some reason, but my gut
 feeling
 is that there are problems, I just can not catch them
 
 We are using Apache SSL fornt and Tomcat 4.1.27 on the back, all on
 solaris
 2.8
 jvm sun 1.4.1
 
 INFO: server has been restarted or reset this connection
 Oct 6, 2003 7:12:51 PM org.apache.jk.common.ChannelSocket
 processConnection
 INFO: server has been restarted or reset this connection
 Oct 6, 2003 7:16:32 PM org.apache.jk.common.ChannelSocket
 processConnection
 INFO: server has been restarted or reset this connection
 Oct 6, 2003 7:16:42 PM org.apache.jk.common.ChannelSocket
 processConnection
 INFO: server has been restarted or reset this connection
 Oct 6, 2003 7:16:56 PM org.apache.jk.common.ChannelSocket
 processConnection
 INFO: server has been restarted or reset this connection
 Oct 6, 2003 7:25:45 PM org.apache.jk.server.JkCoyoteHandler action
 SEVERE: Error in action code
 java.net.SocketException: Broken pipe
 at java.net.SocketOutputStream.socketWrite0(Native Method)
 at
 java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
 at
 java.net.SocketOutputStream.write(SocketOutputStream.java:136)
 at
 org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407)
 at
 org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599)
 at
 org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:385)
 at org.apache.coyote.Response.action(Response.java:222)
 at org.apache.coyote.Response.finish(Response.java:343)
 at
 org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:268)
 at
 org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360)
 at
 org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604)
 at
 org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java
 :562
 )
 at
 org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679)
 at
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo
 l.ja
 v
 a:619)
 at java.lang.Thread.run(Thread.java:536)
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 This e-mail, including any attachments, is a confidential 
 business communication, and may contain information that is 
 confidential, proprietary and/or privileged.  This e-mail is 
 intended only for the individual(s) to whom it is addressed, and 
 may not be saved, copied, printed, disclosed or used by anyone 
 else.  If you are not the(an) intended recipient, please 
 immediately delete this e-mail from your computer system and 
 notify the sender.  Thank you.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange exceptions ...

2003-10-08 Thread Shapira, Yoav

Howdy,

I guess), and I noticed that they get cut off or do not get to the
client,
when I get the info message. The broken pipe happens inconsistently,
so I can not make much sence of it, but I suspect it has something to
do
with the sme problem

It is no bigy for now since the refresh or consequent requests do
serve the images correctly and once it is there browser does cache it,
but I would like to solve it one day, any ideas of where to start my
complains or maybe it has been alread y solved and I am just wasting
my breath here ...

Maybe play with the request timeouts on the tomcat and mod_jk side to
prevent broken pipes.  Other than that, I don't know since I've never
actually had this error happen.

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange Perfomance Issue, Tomcat more than 10 times slower than Jetty

2003-09-30 Thread Shapira, Yoav

Howdy,
Can you please open a Bugzilla issue for this, attaching your tested and
test class source code?  Thanks,

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Christoph Gaffga [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 8:44 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Strange Perfomance Issue, Tomcat more than 10 times slower
than
Jetty

hi,

i posted this issue before, and decided to run my test with another
servlet
container, before saying: it a problem with tomcat.
(I'm running tomcat 4.1.27 with JDK 1.4.2 on RH8)

I have a small test class, that
- Lookup an Entity EJB
- get a property from the Bean
- serialize the bean using betwixt

I runned the classes main-method form different environments, but all
with
the same jvm parameters (-server -Xms1200m -Xmx1200m).
In tomcat it slowes down dramaticly:

  |Command Line | from Servlet | from Servlet
  | | in Tomcat| in Jetty
--+-+--+---
Lookup|  144 ms |  2490 ms |   143 ms
Getter|   17 ms |  2843 ms |21 ms
Serialize |  708 ms | 64147 ms |   947 ms

Has anybody an idea what causes this slowdown, or anybody seen
something
similar before? What am I doing wrong?
Any help would be apriciated.

Thanks a lot,

regards
Christoph Gaffga
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange error message

2003-09-29 Thread Shapira, Yoav

Howdy,
Is there a full stack trace or other messages in the log?  Could it
simply be a class not found exception for that interface, which is being
used by a 3rd party library your webapp relies upon?

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Josh G [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 2:36 AM
To: [EMAIL PROTECTED]
Subject: Strange error message

What does this mean?

javax.servlet.ServletException: org/mozilla/javascript/Scriptable

It's somehow getting out of a block of code encased in a try-catch of
Exception, but of course doesn't give me a line number or any actual
information, and com.mozilla.javascript.Scriptable isn't even a class,
it's
an interface.

Anyway, I've got no idea what's going on, and in a fair hurry to get it
fixed. Any pointers much appreciated.

Cheers,
-Josh

--
[ Josh 'G' McDonald ][ 0415 784 825 ][ http://www.gfunk007.com/ ]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Strange Perfomance decrease with Servlets

2003-09-29 Thread Shapira, Yoav

Howdy,

I call the main-method from my test class the command line.
- The method does lookup an Entity EJB on JBoss server.
- Get a Property from the Bean
- Serialize the Bean using Betwixt

Then I tested the same by calling the same method from an servlet, it
slowes down dramatically:

  |Command Line | from Servlet
--+-+-
Lookup|  144 ms |  2490 ms
Getter|   17 ms |  2843 ms
Serialize |  708 ms | 64147 ms

Has anybody an idea what causes this slowdown, or anybody seen
something
similar before?
Any help would be apriciated.

Strange.  How is your test set up, that is:
- Is the command-line class on the same server as JBoss?
- Is the test class in the same jar as the bean class?
- Are you sure the Getter isn't doing another lookup?
- I have no clue why serialization is two orders of magnitude slower...

Post the tested class and the test class.

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Strange Perfomance decrease with Servlets

2003-09-29 Thread Christoph Gaffga
 I call the main-method from my test class the command line.
 - The method does lookup an Entity EJB on JBoss server.
 - Get a Property from the Bean
 - Serialize the Bean using Betwixt
 
 Then I tested the same by calling the same method from an servlet, it
 slowes down dramatically:
 
   |Command Line | from Servlet
 --+-+-
 Lookup|  144 ms |  2490 ms
 Getter|   17 ms |  2843 ms
 Serialize |  708 ms | 64147 ms
 
 Has anybody an idea what causes this slowdown, or anybody
 seen something similar before?
 Any help would be apriciated.

 Strange.  How is your test set up, that is:
 - Is the command-line class on the same server as JBoss?

yes, it's on the same server, but in another jvm, the tomcat-instance also.

 - Is the test class in the same jar as the bean class?

i didn't package the jar. just plain .class-files-directory in the
classpath.

 - Are you sure the Getter isn't doing another lookup?

I'm sure, the getter getId() only return an Integer. Should be fast.

 - I have no clue why serialization is two orders of magnitude slower...
:(

I was first thinking it's a problem with all the jars in the classpath and
reflection, but it I run my commandline test with the same classpath and the
same jvm options like tomcat, it slows down only about 5 to 10%


 Post the tested class and the test class.

The Source is below:

The TestClient-Class (I call this from command line or from the servlet)

package com.triplemind.samples;

import java.io.IOException;
import java.io.StringWriter;
import java.lang.reflect.Proxy;
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;

import org.apache.commons.betwixt.XMLIntrospector;
import org.apache.commons.betwixt.io.BeanWriter;
import org.apache.commons.betwixt.strategy.ClassNormalizer;
import org.apache.commons.logging.impl.SimpleLog;
import com.triplemind.accommodation.AccommodationRemote;
import com.triplemind.accommodation.AccommodationRemoteHome;

public class TestClient {
  public static void main(String[] args) throws IOException {
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,
org.jnp.interfaces.NamingContextFactory);
env.put(Context.PROVIDER_URL, localhost:1099);
env.put(java.naming.factory.url.pkgs,
org.jboss.naming:org.jnp.interfaces);
try {

  Context ctx = new InitialContext(env);
  Object obj = ctx.lookup(Accommodation);

  System.out.print(Lookuped: );
  System.out.println(obj);

  AccommodationRemoteHome home = (AccommodationRemoteHome)
javax.rmi.PortableRemoteObject.
  narrow(
  obj, AccommodationRemoteHome.class);

  long time = System.currentTimeMillis();

  AccommodationRemote acco = home.findByPrimaryKey(new Integer(2157));

  long time2 = System.currentTimeMillis();

  System.out.println(acco.getId());

  long time3 = System.currentTimeMillis();

  System.out.println(acco.getLocation());
  System.out.println(IsProxy:  +

Boolean.toString(java.lang.reflect.Proxy.isProxyClass(acco.getClass(;

  System.out.println(acco.getClass().toString() +  implements:);
  Class[] interf = acco.getClass().getInterfaces();
  for (int i = 0; i  interf.length; i++) {
System.out.println( -  + interf[i].toString());
  }

  SimpleLog log = new SimpleLog(Logger);
  log.setLevel(log.LOG_LEVEL_ALL);

  StringWriter outputWriter = new StringWriter();
  BeanWriter beanWriter = new BeanWriter(outputWriter);

  XMLIntrospector ispec = beanWriter.getXMLIntrospector();

  ispec.setAttributesForPrimitives(false);
  ispec.setLog(log);
  ispec.setClassNormalizer(new ClassNormalizer() {
public Class normalize(Class clazz) {
  if (Proxy.isProxyClass(clazz)  clazz.getInterfaces().length  0)
{
return clazz.getInterfaces()[0];
  }
  return clazz;
}
  });

  beanWriter.getBindingConfiguration().setMapIDs(true);
  beanWriter.enablePrettyPrint();
  beanWriter.writeXmlDeclaration(?xml version='1.0' ?);

  System.out.println(write Bean...);
  beanWriter.write(acco);

  System.out.println(outputWriter.toString());

  System.out.println(Duration 1st EJB:  + Long.toString(time2 - time)
+ ms);
  System.out.println(Duration 1st getId:  + Long.toString(time3 -
time2) + ms);
  System.out.println(Duration 1st XML:  +
Long.toString(System.currentTimeMillis() - time3) +
 ms);

  log.setLevel(log.LOG_LEVEL_OFF);
  time = System.currentTimeMillis();
  for (int i = 0; i  1000; i++) {
beanWriter.write(acco);
  }
  System.out.println(Duration:  +
Long.toString(System.currentTimeMillis() - time) + us);

} catch (Exception e) {
  e.printStackTrace();
  System.out.println(Exception:  + 

Re: Strange error message

2003-09-29 Thread Jon Wingfield
Are you using Batik?

If so:
org.mozilla.javascript.Scriptable.class is found in the js.jar of the 
Batik 1.5 distribution. Have you deployed that jar?

HTH,

Jon

Josh G wrote:

What does this mean?

javax.servlet.ServletException: org/mozilla/javascript/Scriptable

It's somehow getting out of a block of code encased in a try-catch of 
Exception, but of course doesn't give me a line number or any actual 
information, and com.mozilla.javascript.Scriptable isn't even a class, 
it's an interface.

Anyway, I've got no idea what's going on, and in a fair hurry to get it 
fixed. Any pointers much appreciated.

Cheers,
-Josh




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Strange error message

2003-09-29 Thread Josh G
Jon Wingfield wrote:

Are you using Batik?

If so:
org.mozilla.javascript.Scriptable.class is found in the js.jar of the 
Batik 1.5 distribution. Have you deployed that jar?

HTH,

Jon
Yeah we eventually figured out it was a noclassdeffound error, of course 
if tomcat had actually told me it could have saved me half a day of 
tracking down queer errors (well there's one i tracked down, the other 
is too strange and I'm working around it).

Cheers,
-Josh
--
[ Josh 'G' McDonald ][ 0415 784 825 ][ http://www.gfunk007.com/ ]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Strange request.setAttribute() problem

2003-07-28 Thread Tim Funk
This is the correct behavior. In this scenario, you are operating on the 
request, not the session.

request.getParameter -- Get stuff from the query string (or input stream if 
post) - a per request thing

request.setAttribute -- Set an attribute in the life of this particular request

-Tim

Charles So wrote:
Hello, I come across a problem with TC4.1.24 and hope fellow list users 
can help me...



I set a variable in a servlet by calling:

request.setAttribute(itemnumber, 
Integer.valueOf(Integer.toString(itemnumber)));



A JSP will then detect if this variable exists or not by:

if ( request.getParameter(itemnumber) != null ) {
try {
itemnumber = 
Integer.parseInt((String)request.getParameter(itemnumber));
} catch (NumberFormatException ex) {
System.out.println(No);
}
}



I have two different web browsers opened (say, one IE and one Opera), 
and both eventually will come to the page containing the code above.

The strange thing is that if the variable itemnumber is set via IE, 
the same itemnumber will be seen at Opera!

This shouldn't happen as both have different session ID, and are 
completely unrelated.



Who has come across this problem? How can I work around this?

Thanks!




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Strange request.setAttribute() problem

2003-07-28 Thread Moraes, Fabio

he meant:
use:

HttpSession session = request.getSession( );
session.setAttribute( itemnumber,
Integer.valueOf(Integer.toString(itemnumber)));

and then:

session.getAttribute( itemnumber );

---
 Fabio Moraes
 [EMAIL PROTECTED]
 System Engineer
 Work Force Management System
 +55 21 3088 9548


-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2003 07:53
To: Tomcat Users List
Subject: Re: Strange request.setAttribute() problem


This is the correct behavior. In this scenario, you are operating on the 
request, not the session.

request.getParameter -- Get stuff from the query string (or input stream if

post) - a per request thing

request.setAttribute -- Set an attribute in the life of this particular
request

-Tim

Charles So wrote:
 Hello, I come across a problem with TC4.1.24 and hope fellow list users 
 can help me...
 
 
 
 I set a variable in a servlet by calling:
 
 request.setAttribute(itemnumber, 
 Integer.valueOf(Integer.toString(itemnumber)));
 
 
 
 A JSP will then detect if this variable exists or not by:
 
 if ( request.getParameter(itemnumber) != null ) {
 try {
 itemnumber = 
 Integer.parseInt((String)request.getParameter(itemnumber));
 } catch (NumberFormatException ex) {
 System.out.println(No);
 }
 }
 
 
 
 
 I have two different web browsers opened (say, one IE and one Opera), 
 and both eventually will come to the page containing the code above.
 
 The strange thing is that if the variable itemnumber is set via IE, 
 the same itemnumber will be seen at Opera!
 
 This shouldn't happen as both have different session ID, and are 
 completely unrelated.
 
 
 
 Who has come across this problem? How can I work around this?
 
 Thanks!
 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



  1   2   3   >