Otmane Malih wrote:
When you enter www.domain.com it's like you type xx.yy.zz.aa:8080/Portal
Ove Lindström wrote:
If you use the command:
does it give you the same ip as xx.yy.zz.aa?
Ove Lindström wrote:
You might also have an entry in your host-file that overrides the DNS.
Ove Lindström wrote:
If you type http://xx.yy.zz.aa:8080/Portal does that to give you a "404: Page not found"?
Ove Lindström wrote:
Otmane Malih wrote:
When you enter www.domain.com it's like you type xx.yy.zz.aa:8080/Portal
Well... No.... there are no such thing a port resolving in a DNS entry. You can do it if you have a proxy that receives all the calls on www.domain.com and forwards them to xx.yy.zz.aa:8080. In Apache HTTPD it is done using the mod_proxy. (http://httpd.apache.org/docs/2.2/mod/mod_proxy.html)
Otmane Malih wrote:
For now i think it's a problem of permission. I think when the application tries to write the file to the temp directory, an exception is thrown, so when it tries to log it to the log file an other exception is thrown since the application can't write to the log file
Ove Lindström wrote:
Otmane Malih wrote:
For now i think it's a problem of permission. I think when the application tries to write the file to the temp directory, an exception is thrown, so when it tries to log it to the log file an other exception is thrown since the application can't write to the log file
No, I think it is because you don't really know your server setup...
I would think that when you enter http://www.domain.com/ it calls server with ip aa.aa.aa.aa that looks at the call and think "Lets forward this to xx.yy.zz.aa:8080/Portal".
The Tomcat at xx.yy.zz.aa then receives the call and tries to interpret it, but can't resolve any mapping that matches.
How does you servlet mapping look like?