Tim -

Thanks very much for the response and the project file.  Unfortunately,
this doesn't seem to get me any further.  The DLL that gets built
behaves the same as the one I was building before.  Are you referring to
the settings under project properties -> Configuration Properties ->
C/C++ -> Code Generation -> Runtime Library? It's set to "Multi-threaded
Debug DLL (/MDd)".  Is that right?  I also tried setting it to just
"Multi-threaded (/MT)", but then I see the following errors when I try
to build:

1>MSVCRTD.lib(MSVCR80D.dll) : error LNK2005: _memmove already defined in
LIBCMT.lib(memmove.obj)
1>MSVCRTD.lib(MSVCR80D.dll) : error LNK2005: _strncmp already defined in
LIBCMT.lib(strncmp.obj)

Also, not sure if this is related, but I also see the following warning
(even when the build succeeds):

3>LINK : warning LNK4098: defaultlib 'MSVCRTD' conflicts with use of
other libs; use /NODEFAULTLIB:library

I tried setting this via the project properties under Configuration
Properties -> Linker -> Input -> Ignore Specific Library = "library",
but I still see the warning.  The command line as shown in the
properties panel shows /NODEFAULTLIB:"library" (with the quotes).
Should that matter?

Would another course be to install the VC8 runtime you mentioned on the
IIS server machine?  How would I go about doing that?  I apologize in
advance if this is a dumb question.  I'm mostly a Java guy, and have
very little experience building things with Visual Studio.

Also, I've noticed that even with the release version of the DLL, even
though I'm setting the log level to 'debug' or 'trace', it only
generates a log file when it has a problem loading the
workers.properties file (e.g. when I intentionally point it to the wrong
path).  It doesn't generate a log file at all when things are running
normally.  It behaves this way whether I use the registry keys for the
bootstrap config or if I use the isapi_redirect.properties file.  I was
hoping I might be able to get some more info about what's going wrong
through the log, but my built version of the DLL doesn't log anything
regardless of the configuration.

Thanks again for any help,

-Dan

-----Original Message-----
From: Tim Whittington [mailto:[EMAIL PROTECTED] 
Sent: Saturday, October 27, 2007 01:38
To: 'Tomcat Developers List'
Subject: RE: Rebuilding isapi_redirect.dll

The errors sound like what you get when you build with VC2005 with the
DLL
C runtime, but don't install the VC8 runtime on the IIS server.
Changing your runtime settings (to Multithread) should fix that.

I've attached the project I use to build the ISAPI DLL - it might help.

tim

-----Original Message-----
From: Dan Burton [mailto:[EMAIL PROTECTED] 
Sent: Saturday, 27 October 2007 9:35 a.m.
To: dev@tomcat.apache.org
Subject: Rebuilding isapi_redirect.dll

Hi all,

 

We've run into the issue as described in this bug:
http://issues.apache.org/bugzilla/show_bug.cgi?id=42003  I'm trying to
rebuild the dll myself using Visual Studio to incorporate this change,
but
the dll I build doesn't seem to work at all when I use it in IIS (all
users just get a 500 error instead of actually making it through into
the
app hosted in Tomcat).  We've got the 1.2.25 release version of the dll
in
there now, and it works fine (except for this bug, which affects users
who
have inordinately many group memberships).

 

Also, I can't figure out how to get the Visual Studio project to build a
'release' version, as opposed to a 'debug' version, and as a result, my
dll is about twice the size of the latest release version.  I'm not sure
if that's causing the problem or not.  Is there anything else I should
need to do besides open up the isapi.dws workspace in Visual Studio and
build it?

 

Any help would be greatly appreciated.  If anyone has a built dll with
this fix in that you could share, that would be fantastic.

 

Thanks very much,

 

- Dan

 

Dan Burton
Solution Architect 

Information Access Solutions

tel.: 
fax: 
mobile: 

(512) 469-9300 x150
(512) 692-1958
(512) 657-1414 

[EMAIL PROTECTED] 

 

"committed to client elation"

 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to