aspose file tools*
The moose likes Servlets and the fly likes Filter problem - jar file not downloading Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "Filter problem - jar file not downloading" Watch "Filter problem - jar file not downloading" New topic
Author

Filter problem - jar file not downloading

Mark Vedder
Ranch Hand

Joined: Dec 17, 2003
Posts: 624

My team and I are running into an interesting problem that I was hoping someone might have some insight on solving.

We are using a filter in our Web App that is mapped to all requests:


This is running on a Sun ONE Web Server v6.1 (which is Servlet 2.3 / JSP 1.2 compliant) on Solaris 8.
Client is a company standard configuration of Windows XP with IE 6, Sun JRE 1.4.2_xx.

Our solution leverages five separate MiddleWare Applets saved in separate jars:
One.jar - 20KB
Two.jar - 518KB
Three.jar - 297 KB
Four.jar - 94KB
Five.jar - 1,111KB

All the applets load and execute properly, with one exception, the applet in Five.jar. Further investigation shows that the problem applet�s jar file is not being downloaded. If we change the filter mapping�s URL to hard-coded URL patterns (and thus the filter is not implemented for the request of jar file), the jar is downloaded and the applet executes properly. If we then turn the filter back to "/*" (without clearing the client�s JRE cache) the applet works fine (since the jar file is cached in the JRE and does not need to be downloaded again). If we clear the JRE�s cache (leaving the filter "on"), the jar file is not downloaded and the applet fails.

We even set up a dummy filter that does nothing but calls the filter chain (in which there are no other filters mapped).


Using a "/*" URL pattern on this dummy filter also causes issues in that the problematic jar file (Five.jar) is not downloaded - the other four download fine. Therefore we can rule out that our specific filter is the issue.

Since the primary difference we see with the problematic jar file is its size, we are leaning towards that being the issue.

Based on what the filter does, we need to use a wild character url-pattern; so we really need to find a solution around this problem.

My questions are:
1) I am fairly certain there is no way to map an "exclude" URL in the filter mapping. Am I correct on this?
2) Does any one have any ideas as to what might be causing this? And does our "size of the jar file" theory make any sense? Any suggestions on solving?

Thanks very much in advance for any input and suggestions.
[ July 01, 2004: Message edited by: Mark Vedder ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Filter problem - jar file not downloading