Forum Discussion
AlexKaras
Champion Level 1
12 years agoHi Hugo,
I have extremely limited experience with dealing with java errors, so the following is my wild guess, but my suggestion will be (especially, considering the os.arch: 'x86' string in the extended log messages) to ensure that all components that you use for your tests are of same 'bitness'. I even would recommend to ensure that all of them are 32-bit applications. Under components I mean: TestComplete (it is 32-bit application that can control 64-bit applications), JVM, WebDriver, FireFox and anything else that is used by the tests.
Hope, this might help...
I have extremely limited experience with dealing with java errors, so the following is my wild guess, but my suggestion will be (especially, considering the os.arch: 'x86' string in the extended log messages) to ensure that all components that you use for your tests are of same 'bitness'. I even would recommend to ensure that all of them are 32-bit applications. Under components I mean: TestComplete (it is 32-bit application that can control 64-bit applications), JVM, WebDriver, FireFox and anything else that is used by the tests.
Hope, this might help...