Re: Problem with JSTL on W2k

2003-01-17 Thread Holger Brozio
Hi,

i have found the reason for my problems. The main exception, which is thrown
has the following stacktrace:

java.io.IOException: Access is denied
 at java.io.Win32FileSystem.createFileExclusively(Native Method)
 at java.io.File.checkAndCreate(File.java:1162)
 at java.io.File.createTempFile(File.java:1247)
 at java.io.File.createTempFile(File.java:1284)
 at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:143)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:138)
 at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:43)
 at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:61)
 at
sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:88)
 at
sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:7
2)
 at
org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:906)
 at
org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868)
 at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647)
 at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:
243)
 at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:166)
 at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3567)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347)
 at org.apache.catalina.startup.Embedded.start(Embedded.java:994)

I have started an embedded tomcat 4.1.18 instance with my own NT Service. In
the ContextConfig class
tomcat tries to take a look inside of the jar files in /WEB-INF/lib. For
this issue tomcat needs a temporary
folder. This seems to be c:\winnt in the case of a service. The temp dir is
defined by the java property "java.io.tmpdir".
Because i have started the service as a generic user, i got the exception
access denied.
I have now set the property "java.io.tmpdir" to a directory within the
tomcat installation and now everything works
fine. Maybe this should be done by default?!

Cheers

Holger
- Original Message -
From: "Holger Brozio" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Cc: "Tomcat Development" <[EMAIL PROTECTED]>
Sent: Thursday, January 16, 2003 12:07 PM
Subject: Problem with JSTL on W2k


> Hello,
>
> i have a problem with the JSTL on W2k. If i start tomcat i get the
follwoing
> exception:
>
> javax.servlet.ServletException: Exception processing JAR at resource path
> /WEB-INF/lib/jaxen-full.jar
>  at
>
org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:930)
>  at
> org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868)
>  at
org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647)
>  at
>
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:
> 243)
>  at
>
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
> t.java:166)
>  at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
>  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
>  at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
>  at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
>  at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347)
>  at org.apache.catalina.startup.Embedded.start(Embedded.java:994)
>  at
>
com.intershop.beehive.core.internal.startup.EmbeddedTomcatMgr.startTomcat(Em
> beddedTomcatMgr.java:393)
>  at
>
com.intershop.beehive.core.internal.startup.EmbeddedTomcatMgr.onReadyHook(Em
> beddedTomcatMgr.java:333)
>  at
>
com.intershop.beehive.core.internal.startup.AdminServer.start(AdminServer.ja
> va:70)
>  at
>
com.intershop.beehive.core.internal.startup.AdminServer.main(AdminServer.jav
> a:264)
>
> I have debugged the ContextConfig class and found out, that an exception
is
> thrown at the line 930, which has "Access is denied" as description. It
> seems that tomcat tries to open an URLConnection with the url
> "jndi:/ /WEB-INF/lib/jaxen-full.jar!/".
> My user on W2k is a normal user. If i add the user to the administrators
or
> power user group, there are no problems. I have also tried
> to change the file permissions of the jar file without an effect.
> So it seems to be a permission problem. Does anybody know, which
permission
> on W2k is missing for my user or group, which doesn't allow a normal user
to
> get the jar informations?
>
> Thanx in advance.
>
> Holger
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
>


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




Problem with JSTL on W2k

2003-01-16 Thread Holger Brozio
Hello,

i have a problem with the JSTL on W2k. If i start tomcat i get the follwoing
exception:

javax.servlet.ServletException: Exception processing JAR at resource path
/WEB-INF/lib/jaxen-full.jar
 at
org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java:930)
 at
org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:868)
 at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:647)
 at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:
243)
 at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:166)
 at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347)
 at org.apache.catalina.startup.Embedded.start(Embedded.java:994)
 at
com.intershop.beehive.core.internal.startup.EmbeddedTomcatMgr.startTomcat(Em
beddedTomcatMgr.java:393)
 at
com.intershop.beehive.core.internal.startup.EmbeddedTomcatMgr.onReadyHook(Em
beddedTomcatMgr.java:333)
 at
com.intershop.beehive.core.internal.startup.AdminServer.start(AdminServer.ja
va:70)
 at
com.intershop.beehive.core.internal.startup.AdminServer.main(AdminServer.jav
a:264)

I have debugged the ContextConfig class and found out, that an exception is
thrown at the line 930, which has "Access is denied" as description. It
seems that tomcat tries to open an URLConnection with the url
"jndi:/ /WEB-INF/lib/jaxen-full.jar!/".
My user on W2k is a normal user. If i add the user to the administrators or
power user group, there are no problems. I have also tried
to change the file permissions of the jar file without an effect.
So it seems to be a permission problem. Does anybody know, which permission
on W2k is missing for my user or group, which doesn't allow a normal user to
get the jar informations?

Thanx in advance.

Holger


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




Re: tomcat 4.1.12 just stopped working, help !

2003-01-07 Thread Holger Brozio
Whats about using a tool like XML Spy. With this one you can check, if the
web.xml files are well formed and valid.
Valid means, that they match the rules defined in the web-app_2_3.dtd, which
seems to be the problem in that case.

HTH

Holger
- Original Message -
From: "Peng Tuck Kwok" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 9:53 AM
Subject: Re: tomcat 4.1.12 just stopped working, help !


> Hmm, it looks like an error in the web.xml of a certain app. Did you by
> any chance change the web.xml of any of your web applications ?
>
> [EMAIL PROTECTED] wrote:
> > Hi all
> > Some time during christmas Tomcat 4.1.12 stopped working for me, I don´t
know why, thought anyone here might have a clue.
> > This is what I know:
> > If I start tomcat with ".../bin/startup.sh" and then run a portscan I
can see:
> > 8009/tcp   openajp13
> > 8080/tcp   openhttp-proxy
> > So evidently something happens ;)
> >
> > But if I try to access http://my.ip:8080/index.wml (or just
http://my.ip:8080) I don´t get any answer at all, it seems totally dead.
> >
> > If I then stop Tomcat (.../bin/shutdown.sh) and run a portscan the
services on ports 8009 and 8080 are gone.
> >
> > But if I directly run ".../bin/catalina.sh run" I get this: (if someone
can get any clue from this)
> >
> > [root@star bin]# ./catalina.sh run
> > Using CATALINA_BASE:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_HOME:   /etc/jakarta-tomcat-4.1.12
> > Using CATALINA_TMPDIR: /etc/jakarta-tomcat-4.1.12/temp
> > Using JAVA_HOME:   /usr/java/j2sdk1.4.1
> > Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry loadRegistry
> > INFO: Loading registry information
> > Jan 7, 2003 9:40:58 AM org.apache.commons.modeler.Registry getRegistry
> > INFO: Creating new Registry instance
> > Jan 7, 2003 9:41:03 AM org.apache.commons.modeler.Registry getServer
> > INFO: Creating MBeanServer
> >
> > Starting service Tomcat-Standalone
> > Apache Tomcat/4.1.12
> > Jan 7, 2003 9:47:29 AM org.apache.commons.digester.Digester error
> > SEVERE: Parse Error at line 114 column 15: The content of element type
"servlet" must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> > org.xml.sax.SAXParseException: The content of element type "servlet"
must match
"(icon?,servlet-name,display-name?,description?,(servlet-class|jsp-file),ini
t-param*,load-on-startup?,run-as?,security-role-ref*)".
> > at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand
lerWrapper.java:232)
> > at
org.apache.xerces.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:17
3)
> > at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:36
2)
> > at
org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:29
6)
> > at
org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.
java:1953)
> > at
org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:8
78)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(XMLDo
cumentFragmentScannerImpl.java:1144)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu
mentFragmentScannerImpl.java:987)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
her.dispatch(XMLDocumentFragmentScannerImpl.java:1445)
> > at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume
ntFragmentScannerImpl.java:333)
> > at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:524)
> > at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:580)
> > at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
> > at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:116
9)
> > at
org.apache.commons.digester.Digester.parse(Digester.java:1495)
> > at
org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.ja
va:282)
> > at
org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639)
> > at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:
243)
> > at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:166)
> > at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3493)
> > at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
> > at
org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
> > at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
> > at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347)
> > at
org.apache.catalina.core.StandardService.start(StandardService.java:497)
> > at
or

largefile option in 4.1.12

2002-10-30 Thread Holger Brozio
Hello,

has anybody tested the largefile option with Tomcat 4.1.12?
In my opinion it seems to be without effect. No .dat file are
generated like in 4.0.x. I have also scanned the jasper code
for this option. The option is set at the EmbededServletOptions
class, but nobody seems to use this value inside of the jasper package?

Thanks in advamce.

Holger Brozio

--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>




Charsets and RequestDispatcher

2002-10-29 Thread Holger Brozio
Hello,

i have made the following observation:

I am using Tomcat 4.1.12 on Windows NT.

If i display the jsp page with charset "windows-1253" by invoking the page
the direct way,
the characters are displayed correct.

e.g. http://localhost/jsp/enc_test/ch1253.jsp

After that i wrote a small servlet, which uses the
RequestDispatcher.include()
mechanism to dispaly the same page inside of this servlet:

e.g.

public class RequestDispatcherTest extends HttpServlet
{
public void doGet(HttpServletRequest request,
   HttpServletResponse response)
throws IOException, ServletException
{
// Acquire request parameters we need
String incPage = request.getParameter("incpage");
if (incPage != null)
{
RequestDispatcher rd =
getServletContext().getRequestDispatcher(incPage);
rd.include(request, response);
return;
}

System.out.println("No parameter incpage given!");
}
}

I have invoked the execution of the page by:

http://localhost/servlet/RequestDispatcherTest?incpage=/jsp/enc_test/ch1253.
jsp

To my surprise, all the characters are now displayed as question marks:

?? ?

24 ?? 1997

8 Mbps ??? ? ??? ??? 1998

??? ??? ?? ?? ?? ?? ??? ?? ???  2 Mbps, ???
??  ??  ???  ?? ??? ??? ??? 4 Mbps ,
? FORTHnet A.E. ??? ???  ??? ?? ?? ?? ??? ??? ???
? ??? ? ?, ? ??? ??? ?? ??
??? ?, ? ? 8 Mbps. ? ?? , 
??? ? ??  Internet ??? ??? ??? ??  ,
? ?? ?  ???   ??? ?? ???, ??
? ?o FORTHnet ?? ??? ?  ??? ? ? ??? ?.

? ?? ??? ?? ??? ??  ??? ? ??? ,   ???
??? ???  MCI, ??? ???  ??? ? ? ? ???
??? ??? ??,  ??? ?? ? ??
?? ??. ? ???  ? ??? ?
? ???  ??,  ??? ??? ???  ? ???
? ??? ??? ?  ??? ??, ? ??? ?? ?? ?? ??
?? ??? ??? ? ??? ??? ??? 1998, ? ??? ?? ? ??
? ??.

?: ??? 

: 7295100

FAX: 7258520
-

My question now is:
Is this the normal (correct) behaviour or is this a bug?
Does the servlet spec 2.3 prohibit to change the character set of an
included page somehow?

Thanks in advance

Holger


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




Re: Tomcat 4.1.12 memory leak

2002-09-26 Thread Holger Brozio

Hi,

some time ago i had extreme problems with RedHat 7.2.
Even if no big applications are running, the whole available
memory size seems to decrease all the time.

Have you tried to verify the problem with the same Tomcat
version and a different environment like Solaris or W2K or
a different Linux distribution like Debian or SuSE?

Cheers

Holger

- Original Message -
From: "Ing. Damiano Bolla" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 26, 2002 3:17 PM
Subject: Tomcat 4.1.12 memory leak


> System: Linux redhat 7.2
> Java: /usr/local/j2sdk1.3.1
> Tomcat 4.1.12
>
> To reproduce the behaviour you install the 4.1.12 distribution, set the
> JAVA_HOME run startup.sh and then keep refreshing the homepage
> http://localhost:8080/
>
> If you monitor the memory usage using top and switching it into display
> memory usage (Capital M) you sull see tipically something like
>
> 22824
> 22832
> 22840
> 23576
> 23676
> 23684
> 23904
> 23908
> 23934
> 23938
> .
>
> This is the SIZE field of the top command.
> The point is that it never goes down and eventually you run very slowly.
>
> Any idea ?
>
> Ah, the same behaviour is with jdk 1.4.1
>
> Damiano
>
>
> --
> To unsubscribe, e-mail:

> For additional commands, e-mail:

>
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




jspCompilerPlugin in Tomcat 4.1.x

2002-08-16 Thread Holger Brozio

Hi,

is the jspCompilerPlugin init parameter still available in tomcat 4.1.x?
It is still described in the global web.xml file as init parameterof the
jspServlet.
But when i take a look in the jasper compiler package, the interface
org.apache.jasper.compiler.JavaCompiler
and the classes
org.apache.jasper.compiler.JikesJavaCompiler and
org.apache.jasper.compiler.SunJavaCompiler
are gone in Tomcat 4.1.x.
However, is there a way to use jikes as jsp page compiler in Tomcat 4.1.x
with the jspServlet
(without using an ant task to precompile the jsp pages at deployment time)?

Thanks in advance.

regards

Holger Brozio




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