top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

How Tomcat-6 access a remote directory on the network (NetApp)?

0 votes
61 views

I'm using Tomcat6 on my web application which is running on Windows Server 2003 Standard Edition. I want to access static files (PDF) in the remote directory on the disk server (NetApp) through http address from web browser. I tried to use Windows shortcut, but It didn't work. Seems that Tomcat recognize a shortcut as a common file (.lnk) instead of a soft link. How can I access it properly through http in the IE browser?

I can only access the files if the static files are put in the local disk. I tried to use hard link and junction, but they work only on the local disk (on the same computer). I tried to modify context.xml, but it didn't succeed.
Most of the solution in the internet is a soft link from local disk to local disk.

posted Aug 12, 2013 by Sumit Pokharna

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

1 Answer

+1 vote
 
Best answer

If you have installed Tomcat in the standard way, Tomcat will run as a Service, under a user-id "LocalSystem". In Windows, this special user-id has no access to Windows "network resources" such as network-mapped drives etc..
In order for Tomcat to be able to access such drives, you will need to use a "domain user" to run the Tomcat Service.

answer Aug 12, 2013 by Abhay Kulkarni
Yes, it's under "Local System".
I think you are right. It's because of the "access" problem. That's why all the errors are related to read/write access to the target directory. Thank you for your clues.
Similar Questions
+1 vote

I want to access the JNDI Directory context in Tomcat8. I've used DirContextURLStreamHandler class which was in Tomcat 7. But now that has been removed.

Can someone tell me how can I access the JNDI Directory Context in Tomcat 8?

+2 votes

Does anyone knows how-to disable SSL v3 in older tomcat version, I have tried to variety solution including sslProtocols or sslEnabledProtocols but it both did not work well, the Firefox I am using to test is only select TLS 1 and result is that I were not able to access the site.

Below is the server information:

Server version: Apache Tomcat/6.0.18
Server built: Jul 22 2008 02:00:36
Server number: 6.0.18.0
OS Name: Windows 2003
OS Version: 5.2
Architecture: x86
JVM Version: 1.6.0-b105
JVM Vendor: Sun Microsystems Inc

0 votes

Does heartbleeding bug impact on Tomcat 6.x, 7.x and 8.x ? I noticed that Tomcat native connector version 1.1.22 uses : OpenSSL 0.9.8 which doesn't have the heartbleeding bug, but 1.1.24 and 1.1.29 also include the buggy openssl.

How can I find which version of Tomcat uses which version of Tomcat native connector ? For example, how can I figure out which version of Tomcat native connector is used by Tomcat 7.0 build 47.

+1 vote

We have a context that includes an underscore and that is unfortunately causing problems w/ a load balancer and cookie paths. Our URLs resemble this:

https://example.com/the_context/login.jsp

Where we have deployed a war file named "the_context.war".

I'd like to somehow alias the context name so both of these urls would effectively be the same:

https://example.com/the_context/login.jsp
https://example.com/thecontext/login.jsp

Ideally this would be done w/o deploying the application twice. Is this possible in Tomcat 6 and/or 7 ?

0 votes

Upgrading from tomcat 6.0.35 to 6.0.36 causes a simple jsp page to require about 20 minutes to load.

We have two clients that are running in an IBM mainframe USS (Unix System Services) environment and when they upgraded from tomcat 6.0.35 to 6.0.36, the simple jsp page in our webapp takes up to 20 minutes to load into the web browser. We have other clients that are successfully running 6.0.36 in
the USS environment. So it is a somewhat isolated issue.

I looked over the 6.0.36 change log at
http://tomcat.apache.org/tomcat-6.0-doc/changelog.html#Tomcat%206.0.36%20%28jfclere%29,
but nothing jumped out at me as to which change may have caused the issue.

Since I am not a tomcat expert, I am asking for help on how to diagnose this issue.

Are there certain logging options that could be enabled?


Useful Links with Similar Problem
Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#470/147, 3rd Floor, 5th Main,
HSR Layout Sector 7,
Bangalore - 560102,
Karnataka INDIA.
QUERY HOME
...