Kevin Williams wrote:
I cant do a clean install on a production server. I did do this on a
development server and everything worked fine. It's strange that my change
to the server.xml caused logging to stop working completely. is there a
log4j properties file i should add someone to get loggin
I cant do a clean install on a production server. I did do this on a
development server and everything worked fine. It's strange that my change
to the server.xml caused logging to stop working completely. is there a
log4j properties file i should add someone to get logging working again?
On Fri
Kevin Williams wrote:
I think I may have a logging problem. All my logs are completely
empty. I get a log4j warning to stdout and that's it. How can I fix
the logging problem. This is a need problem.
Start with a clean install without your webapps. Logging will work out of
the box (assumin
I think I may have a logging problem. All my logs are completely
empty. I get a log4j warning to stdout and that's it. How can I fix
the logging problem. This is a need problem.
On 5/9/08, Mark Thomas <[EMAIL PROTECTED]> wrote:
> Kevin Williams wrote:
>> But when i try to connect to https://
Kevin Williams wrote:
But when i try to connect to https://host:8443, i get no response. i also
tried telneting to that port to see if it was at least open from the server
its running on (to eliminate a firewall problem) and i get connection
refused. I don't beleive the daemon is running on the
