Hi Turk,
I forgot the wow64 entry. Now it is working. You are absolutely right. The
64-bit and 32-bit do behave the same. Now I don't know what to do any more. I
have a chatting application working well on windows 2003/IIS6(32-bit). The
chatting application enables person1 to talk to person2 using standard HTTP and
push technology. When I moved it to windows 2008/IIS7(64-bit), the person2 can
receive all messages from person1 but person1 cannot receive any messages back.
The difference is that person1 to person2 is HTTP post and person2 to person1
is push(Javascript push). I saw the ISAPI filter logged the javascript
statement and said it sent to client successfully but person1 does not receive
it. I used wireshark on the person1 machine and the web server machine. No such
info is logged in wireshark.. Here is the trace printed out in the isapi log:
For better readablity: the following is to transmit
"<script.language=JavaScript>parent.receiveText('TestMsg1')</script>
Under the windows 2003, the javascript will be received by person1's web
browser and execute it. but on windows 2008, this line is not even able to send
to person1. Do you have any idea how this could happen? I am desperate needing
help.
Thanks,
Jason
Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_isapi_plugin.c (1207):
Wrote 114 bytes of data successfully
[Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_ajp_common.c (1259):
received from ajp13 pos=0 len=72 max=8192
[Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_ajp_common.c (1259):
0000 03 00 44 3C 73 63 72 69 70 74 20 6C 61 6E 67 75 - ..D<script.langu
[Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_ajp_common.c (1259):
0010 61 67 65 3D 4A 61 76 61 53 63 72 69 70 74 3E 70 - age=JavaScript>p
[Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_ajp_common.c (1259):
0020 61 72 65 6E 74 2E 72 65 63 65 69 76 65 54 65 78 - arent.receiveTex
[Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_ajp_common.c (1259):
0030 74 28 27 54 65 73 74 4D 73 67 31 27 29 3B 3C 2F - t('TestMsg1');</
[Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_ajp_common.c (1259):
0040 73 63 72 69 70 74 3E 00 00 00 00 00 00 00 00 00 - script>.........
[Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_isapi_plugin.c (1194):
Writing 68 bytes of data to client
[Fri Mar 05 09:09:26.794 2010] [7040:11432] [debug] jk_isapi_plugin.c (1207):
Wrote 68 bytes of data successfully
> Date: Fri, 5 Mar 2010 10:10:56 +0100
> From: mt...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: IIS 7 is unable to load 32-bit Tomcat connector
>
> On 03/05/2010 09:22 AM, Jason Foy wrote:
> >
> > Hi guys,
> >
> > I have a need for IIS 7 to
> > load 32-bit Tomcat connector since for some reason our 64-bit Tomcat
> > connector works in some way but not completely behave same as IIS 6 / 32-bit
> > connector. I got following error
> > Calling LoadLibraryEx on ISAPI filter "D:\Tomcat\Jakarta Isapi
> > Redirector\bin\isapi_redirect.dll" failedAny suggestions are so
> > welcome since I am really desperate.
> >
>
> Couple of things.
> I presume you have created WOW64 registry keys for
> isapi_redirect, since there is where it'll look.
>
> OTOH isapi_redirect is both filter and extension.
> Seems to me that the given script only handles extensions
> not filters and is meant for legacy code that was not
> ported to 32 bits. So you would have to make sure
> that you load filter in 32 bit mode as well
> (I presume using 32-bit mode application pool)
>
> If you have some real reasons why the 32-bit behaves
> differently then 64-bit, I'll be interested.
>
>
> Regards
> --
> ^TM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/201469229/direct/01/
