JNDI question/problem

2008-02-18 Thread Mindaugas Žakšauskas
Hi, I'm using Tomcat v5.5.25 with two webbaps deployed as plain files (not wars). Both of them use JNDI and do some initial binding upon webapp (context) startup. The "startup" event is determined by implementing a listener (javax.servlet.ServletContextListener's contextInitialized method) and pla

Re: JNDI question/problem

2008-02-18 Thread Mindaugas Žakšauskas
Hi Charles, ...and thanks for your reply. > You appear to be trying to define two default contexts (path=""), which is > obviously incorrect <..> Just to be more precise and address your point: - I am running Tomcat without its default apps (manager, root), only my own apps are set up; - when

Re: Tomcat Locking Up?

2008-02-20 Thread Mindaugas Žakšauskas
Hi, I think you need to make sure this is Tomcat's fault first. The best way to do this is to set up JMX console and keep monitoring it so you can see how much memory is allocated/used, same for CPU, threads, sockets, etc. Maybe you're running out of resources? We run 5.5 Tomcat on websites havin

Semicolon URI encoding and RFC

2011-05-09 Thread Mindaugas Žakšauskas
Hi, I was trying to read RFCs 3986 and 2396 to understand some subtleties about URI encoding. In particular I am interested about whether semicolon (;) needs to be percent escaped as, e.g. http://site/some;path VS http://site/some%3Bpath when outputting e.g. HTML href element. Just for interest,

Re: Semicolon URI encoding and RFC

2011-05-09 Thread Mindaugas Žakšauskas
On Mon, May 9, 2011 at 2:03 PM, Konstantin Kolinko wrote: <..> > If ";" is part of the actual path, it must be escaped. > > If ";" starts a "path parameter" it must be unescaped. One well-known > example is ";jsessionid" path parameter. Thanks for your answer. Is this rule is just "de facto" rule

Re: Semicolon URI encoding and RFC

2011-05-10 Thread Mindaugas Žakšauskas
Hi, Thanks very much for your answers. Just for a reference, I will sum up what I've managed to get out of this discussion. Please correct me if I am wrong. My problem wasn't charset incompatibility between client and server as it is the same party which produces URLs and consumes them (and yes,

Re: Semicolon URI encoding and RFC

2011-05-11 Thread Mindaugas Žakšauskas
On Tue, May 10, 2011 at 7:31 PM, Christopher Schultz wrote: > <..> > What about http://site/test1%28test2/ > > Does that give you "/test1)test2/"? Closing bracket is %29 but yes, it does. > If so, Tomcat is probably following SOP with regard to standards which > is to be conservative in what you

Re: Semicolon URI encoding and RFC

2011-05-11 Thread Mindaugas Žakšauskas
Christopher Schultz> So, you want to /only/ escape those entities that are /absolutely Christopher Schultz> required/ to be escaped? Yes. Christopher Schultz> I'm not sure anyone really cares what URLs look like, do they? Konstantin Kolinko> readability? nobody reads the HTML source Search engin