Agent service not running as 32 bit?

Windows Server 2003 R2 Standard x64 Edition
TeamCity Enterprise 4.0.2 (build 8222)

Shouldn't the agent service TeamCityAgentService-windows-x86-32, which is a 32 bit application, run under WOW64 context?

We had a problem with this agent reporting PROCESSOR_ARCHITECTURE as AMD64(agent's native architecture) instead of x86(WOW64 context architecture). http://blogs.msdn.com/david.wang/archive/2006/03/26/HOWTO-Detect-Process-Bitness.aspx

I looked at the Windows Task Manager, and I was very surprised to find that the service wasn't running as a 32 bit application.
Is this even possible? Please look at the attachment and notice how *32 is missing after the .exe name.

Can someone tell me if this is correct?

Thank you,
Calvin



Attachment(s):
32vs64.jpg
3 comments

Java Service Wrapper process is 32 bit process. I've checked it bitness with Process Explorer.
It seems there is an issue of Java Service Wrapper that turns out to have wrong value set to that environment variable.

You may workaroud it be setting env.PROCESS_ARCHITECTURE=x86 in the buildAgent.properties file.

Please watch/vote for http://youtrack.jetbrains.net/issue/TW-5645

0

Please sign in to leave a comment.