search

bigdata4u / spymemcached

Automatically exported from code.google.com/p/spymemcached
0 stars 0 forks source link

jboss server crashes #227

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Currently using 2.7.1 vesrsion of spymemcached, memcached server is on Linux. 
Development env is windows.

While getting objects from cache my application server (jboss 4.2.2) crashes 
with following errors

---------------  T H R E A D  ---------------

Current thread (0x53fde670):  JavaThread "CompilerThread1" daemon 
[_thread_in_native, id=2024]

siginfo: ExceptionCode=0xc0000005, reading address 0x00000004

Registers:
EAX=0x00000000, EBX=0x56cef010, ECX=0x543cf360, EDX=0x00000000
ESP=0x543cf0a4, EBP=0x00000000, ESI=0x543cf370, EDI=0x543cf360
EIP=0x6dad0c8e, EFLAGS=0x00010202

Top of Stack: (sp=0x543cf0a4)
0x543cf0a4:   543cf370 6dad2b9f 56cef010 56d952ac
0x543cf0b4:   543cf124 58762218 543cf134 5be3c778
0x543cf0c4:   56cef010 5be3f0ec 6dad294d 58762218
0x543cf0d4:   00000000 543cf360 56cef058 00000000
0x543cf0e4:   00000001 0000001d 0000001d 543cf360
0x543cf0f4:   000000bc 6dad11f9 543cf134 543cf124
0x543cf104:   543cf144 00000000 0000002b 543cf7d0
0x543cf114:   543cf684 00000000 58768e90 53fde800 

Instructions: (pc=0x6dad0c8e)
0x6dad0c7e:   90 90 8b 44 24 04 56 8b 50 1c 8b 41 58 8b 04 90
0x6dad0c8e:   8b 50 04 83 3a 00 75 1e 8b 51 14 8b 40 1c 3b c2 

Stack: [0x54390000,0x543d0000),  sp=0x543cf0a4,  free space=252k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [jvm.dll+0x1f0c8e]

[error occurred during error reporting, step 120, id 0xc0000005]

Current CompileTask:
opto: 66% !   
com.xyz.base.cache.LoadCache.getList(Lcom/xyz/ID;)Ljava/util/List; @ 90 (174 
bytes)

Original issue reported on code.google.com by cbin...@gmail.com on 27 Dec 2011 at 9:32

GoogleCodeExporter commented 8 years ago 
The operation which I am calling is getBulk() on MemcachedClient

Original comment by cbin...@gmail.com on 27 Dec 2011 at 9:41

GoogleCodeExporter commented 8 years ago 
Which JVM is this?  That really doesn't look very familiar.  A compiler crash 
while fetching items doesn't make much sense to me initially.

Are you dealing with serialized Java objects by chance?  I don't think it'd 
look like this, but perhaps possibly something is not serializing/deserializing 
properly?

Original comment by ingen...@cep.net on 27 Dec 2011 at 9:50

GoogleCodeExporter commented 8 years ago

Original comment by ingen...@gmail.com on 27 Dec 2011 at 9:52

GoogleCodeExporter commented 8 years ago 
yes we have serialized Java objects, I didn't try to find out if this is 
happening when getting serialized java objects or primitive java types.

I am using jdk 1.5

Original comment by cbin...@gmail.com on 28 Dec 2011 at 7:06