One other comment. It appears that this executable is explicitly setting
the access flags so that registry entries are created in the
HKLM\Software\Wow6432Node. I don't see any good reason for this.
I notice that the ISAPI redirector does not set this flag, so it depends
upon the appropriate k
George Sexton wrote:
George Sexton wrote:
When I looked at the Commons-Daemon one, all of the entries were 3 or
more years old, so I didn't think it was in use.
At least the change log didn't have anything more current than 3 years...
I will try to check the JIRA's of commons=daemon and
George Sexton wrote:
When I looked at the Commons-Daemon one, all of the entries were 3 or
more years old, so I didn't think it was in use.
At least the change log didn't have anything more current than 3 years...
--
George Sexton
MH Software, Inc.
Voice: +1 303 438 9585
URL: http://www.
When I looked at the Commons-Daemon one, all of the entries were 3 or
more years old, so I didn't think it was in use.
Mark Thomas wrote:
George Sexton wrote:
Before I get flamed, I looked at a way to report this bug through
bugzilla/jira and couldn't seem to find the right project...
Common
George Sexton wrote:
> Before I get flamed, I looked at a way to report this bug through
> bugzilla/jira and couldn't seem to find the right project...
Commons daemon - it is in JIRA although it really is a Sun bug and a
commons-daemon enhancement request.
Mark
>
> I just went through a troubl
Before I get flamed, I looked at a way to report this bug through
bugzilla/jira and couldn't seem to find the right project...
I just went through a troubleshooting session getting tomcat5.exe to
work on Windows 2008 x64 with x64 jre 1.6.0 Update 11. I was using the
tomcat5.exe x64 binaries th
