# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x7729e39e, pid=4432,
tid=4588 ...
Except for the actual pid etc numbers I am experiencing the same problem
about once a day.
I believe this is an important piece of informatio
On 5/23/2012 6:05 PM, Konstantin Kolinko wrote:
2012/5/24 David kerber:
Stack: [0x0cb0,0x0cc0], sp=0x0cbfea10,
free space=1018k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
code)
C [ntdll.dll+0x532d0] RtlFreeHeap+0xd0
[error oc
On 5/23/2012 5:39 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 5/23/12 5:17 PM, David kerber wrote:
On 5/23/2012 4:57 PM, Mark Thomas wrote:
On 23/05/2012 21:53, David kerber wrote:
Any suggestions as to where to start looking for this error?
Ditch
2012/5/24 David kerber :
> Any suggestions as to where to start looking for this error?
>
> This is TC 7.0.22 32-bit running on Windows Server 2008R2, on a Dell
> Dual-processor 4-core hyperthreaded (total 16 cores according to the OS) box
> with 16GB RAM. Overall memory usage is approx 26% accord
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 5/23/12 5:17 PM, David kerber wrote:
> On 5/23/2012 4:57 PM, Mark Thomas wrote:
>> On 23/05/2012 21:53, David kerber wrote:
>>> Any suggestions as to where to start looking for this error?
>>
>> Ditch the ODBC-JDBC bridge driver and get a J
On 5/23/2012 4:57 PM, Mark Thomas wrote:
On 23/05/2012 21:53, David kerber wrote:
Any suggestions as to where to start looking for this error?
Ditch the ODBC-JDBC bridge driver and get a JDBC driver for the database
you are using. The ODBC-JDBC bridge is not recommended for production use.
I
On 23/05/2012 21:53, David kerber wrote:
> Any suggestions as to where to start looking for this error?
Ditch the ODBC-JDBC bridge driver and get a JDBC driver for the database
you are using. The ODBC-JDBC bridge is not recommended for production use.
Mark
---
