Hi all,
As promised, the solution to the core issue we've been having with 32-bit WebSphere Application Server Network Deployment v6.1.0.27 running on 64-bit Windows Server 2008 SP1 with IBM's old bridge2java.dll file (not supported since 2004). My colleague found the fix which was ridiculously...
Hi there,
Just to give ye the official IBM word, straight from the horses mouth on WebSphere Application Server instances registered as Windows services. This is peripheral but perhaps relevant to my problem above.
When setting up a WebSphere Application Server Network Deployment environment...
@ kmcferrin - after trying to test the above with Sun's JDK 1.5.0_11 64-bit - recompiled the classes and jar'd them up. After trying to run the app - it fell over as the bridge2java.dll is 32-bit which gives me the following exception:
Exception in thread "main" java.lang.UnsatisfiedLinkError...
Thank you TonHu and kmcferrin for your responses...
@ TonHu - regarding "the old executable" - are you talking about the Java Service Wrapper?
@ kmcferrin - alas, we can't use 64-bit Java as we must use the 32-bit IBM JDK that comes with WebSphere (for our customer). I'll test it on the 64-bit...
Hi there,
I'm having a problem running a Windows Server 2008 service. The strange thing is that it works fine via the command prompt.
I'm running 64-bit Windows Server 2008 SP2 as an VMware image on a EM64T ESX Server. On this server, I'm running 32-bit Java5 from IBM and 32-bit MS Word 2007...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.