RE: Performance issue of web application using slide

2003-12-15 Thread Wong, Priscilla
Thanks, Ingo. 

We have set the JAVA_OPTs to set the Java VM memory, but it seems doesn't
work.  As you said the problem might depend on the store implementation we
are using. Would you mind to tell me what does it mean of store
implementation?  I am sorry that i am quite new to Slide.  Thanks.  

Also i have tried to print out the stack trace as follows, do you have any
ideas on it?   Regards, Priscilla

Thread-32 daemon prio=5 tid=0x4AB80D10 nid=0x54c runnable
[4cdfe000..4cdffdbc]

at java.lang.Throwable.getStackTraceElement(Native Method)
at java.lang.Throwable.getOurStackTrace(Throwable.java:591)
- locked 03DB1150 (a java.lang.Throwable)
at java.lang.Throwable.getStackTrace(Throwable.java:582)
at
org.apache.commons.logging.impl.Jdk14Logger.log(Jdk14Logger.java:115)

at
org.apache.commons.logging.impl.Jdk14Logger.trace(Jdk14Logger.java:25
6)
at
org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:80)

at
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.
java:878)
at
org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMetho
dBase.java:1907)
at
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodB
ase.java:1713)
at
org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMetho
dBase.java:2313)
at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.j
ava:957)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.jav
a:564)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.jav
a:476)
at
org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.ja
va:2994)
at
org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.ja
va:2964)
at
org.apache.webdav.lib.WebdavResource.setNamedProp(WebdavResource.java
:840)
at
org.apache.webdav.lib.WebdavResource.setBasicProperties(WebdavResourc
e.java:789)
at
org.apache.webdav.lib.WebdavResource.setProperties(WebdavResource.jav
a:1670)
at
org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1
110)
at
org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1
129)
at
org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1
208)
at
org.apache.webdav.lib.WebdavResource.setPath(WebdavResource.java:1266
)
at jspclient.Session.changeCollection(Session.java:158)
at org.apache.jsp.dirlist_jsp._jspService(dirlist_jsp.java:253)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:204)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2
95)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)

at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
torBase.java:550)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)

at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:
2415)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
rValve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContex
t.invokeNext(StandardPipeline.java:641)
at

Performance issue of web application using slide

2003-12-14 Thread Wong, Priscilla
Hi, all. 

I am developing an web application which is using Tomcat 4.1.18 to connect
to the Slide server.  Everything work fine in development stage. But after i
published it to the production environment, the web application seems
continue to hold the memory of the server.  At last, i need to restart the
slide. 

In my webapp, every user login to the slide server will a session value
containing a WebdavResource.  Would it be a problem to the performance of
the server?  And in my slide server, it contains several hundreds files and
they will be accessd by about 50 users. 

Regards,
Priscilla


Problem when opening pdf file in webfolder

2003-12-09 Thread Wong, Priscilla
Hi All.  

I am using Jakarta Slide Webdav server under Tomcat.  The Slide verion is
the nightly-build version.  We have successfully set up the webdav server
and we can upload the files to the server via Web Folder.   But the problem
is that when we double clicked to open a pdf file in the webfolder, Internet
Explorer is opened and prompted Internet Explorer cannot download
filename from server_name.  If we open the file via WebdavServlet, it
works fine.   Moreover, I have tried to copy the link of the file in
WebdavServlet and directly access it from IE.  It also failed with the same
error message, however, i can open it in Netscape.   Do anyone encounter the
same problem before or can give some hints to me? 

Thanks a lot. 

Best Regards,
Priscilla 



RE: Problem when opening pdf file in webfolder

2003-12-09 Thread Wong, Priscilla
Thanks, Mike.  I think your assumption of my problem is right.  In our
application, we have set LDAP Realm to authenticate Slide by LDAP server.
But how can we set the Cache-Control as you mentioned? Because we can't
change the setting of Web Folder.  Or do I need to customize the Slide
server source to handle the case for IE? 

Best Regards,
Priscilla


-Original Message-
From: Michael Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 2:33 PM
To: Slide Users Mailing List
Subject: Re: Problem when opening pdf file in webfolder


Wong, Priscilla wrote:
 Hi All.  
 
 I am using Jakarta Slide Webdav server under Tomcat.  The Slide verion is
 the nightly-build version.  We have successfully set up the webdav server
 and we can upload the files to the server via Web Folder.   But the
problem
 is that when we double clicked to open a pdf file in the webfolder,
Internet
 Explorer is opened and prompted Internet Explorer cannot download
 filename from server_name.  If we open the file via WebdavServlet, it
 works fine.   Moreover, I have tried to copy the link of the file in
 WebdavServlet and directly access it from IE.  It also failed with the
same
 error message, however, i can open it in Netscape.   Do anyone encounter
the
 same problem before or can give some hints to me? 
 
 Thanks a lot. 
 
 Best Regards,
 Priscilla 
 

IE and/or the adobe reader plugin have a series of major bugs that make 
it very difficult to get PDF files to open reliably in the plugin.

There are four criteria that must be met:
1) The content type must be application/pdf (easy, this is probably 
working fine, and is correct behaviour, not a bug)
2) The URL must end with .pdf (also easy in this sort of case, but

this is a bug), for dynamic sites I've occasionally had to use a dummy 
URL-parameter for this, like ?dummy=file.pdf
3) The response must have an accurate Content-Length set (the slide 
webdav server does this). Using HTTP/1.1 chunking or closing the 
connection to indicate end-of-content do NOT work. This is also a bug.
4) (This one is probably your problem) IE must think the content is 
cacheable. If you have authentication set up with slide, IE will not 
think this. You may need to set one or more of the Cache-Control, 
Expires, and Pragma headers, our application takes the conservative 
approach and sets all three. This is a result of how IE invokes the 
plugin, and isn't neccesarily a bug (though it might be, I'm not sure).


Mike


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