Sigar binary make JVM crash on Windows10 & jdk11 - sigar

Hi i'm using sigar very usefully,
but some critical problem was occurred.
in Windows 10 & jdk11 sigar lib makes JVM crash(append logs below) at all method
but, It works fine when using jdk8 under same environment.
It seems to my sigar-amd64-winnt.dll isn't compatible with jdk11 on windows 10.
so i update my sigar binary to 1.6.4 download from https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/magelan/hyperic-sigar-1.6.4.zip
Unfortunately problem isn't resolved.
is any resolution about this problem?
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000010014ed4, pid=28016, tid=5076
#
# JRE version: Java(TM) SE Runtime Environment (11.0.6+8) (build 11.0.6+8-LTS)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0.6+8-LTS, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)
# Problematic frame:
# C [sigar-amd64-winnt.dll+0x14ed4]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- S U M M A R Y ------------
Command Line: org.ngrinder.NGrinderAgentStarter --mode=agent --command=run -o
Host: Intel(R) Core(TM) i7-7700 CPU # 3.60GHz, 8 cores, 15G, Windows 10 , 64 bit Build 17134 (10.0.17134.753)
Time: Thu Feb 13 18:15:10 2020 ¢¥eCN©öI¡¾©ö C¡ÍA¨ª¨öA elapsed time: 0 seconds (0d 0h 0m 0s)
--------------- T H R E A D ---------------
Current thread (0x00000219633f8800): JavaThread "main" [_thread_in_native, id=5076, stack(0x000000256b800000,0x000000256b900000)]
Stack: [0x000000256b800000,0x000000256b900000], sp=0x000000256b8fee50, free space=1019k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [sigar-amd64-winnt.dll+0x14ed4]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.hyperic.sigar.ProcState.gather(Lorg/hyperic/sigar/Sigar;J)V+0
j org.hyperic.sigar.ProcState.fetch(Lorg/hyperic/sigar/Sigar;J)Lorg/hyperic/sigar/ProcState;+11
j org.hyperic.sigar.Sigar.getProcState(J)Lorg/hyperic/sigar/ProcState;+2
j org.hyperic.sigar.Sigar.getProcState(Ljava/lang/String;)Lorg/hyperic/sigar/ProcState;+6
j org.ngrinder.NGrinderAgentStarter.checkDuplicatedRun(Ljava/lang/String;)V+26
j org.ngrinder.NGrinderAgentStarter.main([Ljava/lang/String;)V+227
v ~StubRoutines::call_stub
siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0x0000000009811d78
Register to memory mapping:
RIP=0x0000000010014ed4 sigar-amd64-winnt.dll
RAX=0x0000000009811c40 is an unknown value
RBX={method} {0x000002197fe1ab58} 'gather' '(Lorg/hyperic/sigar/Sigar;J)V' in 'org/hyperic/sigar/ProcState'
RCX=0x00000219633f8b40 points into unknown readable memory: 90 5d 23 16 ff 7f 00 00
RDX=0x000000256b8ff0b0 is pointing into the stack for thread: 0x00000219633f8800
RSP=0x000000256b8fee50 is pointing into the stack for thread: 0x00000219633f8800
RBP=0x000000256b8ff080 is pointing into the stack for thread: 0x00000219633f8800
RSI=0x0000000000200021 is an unknown value
RDI=0x0000000000000268 is an unknown value
R8 =0x0000000000000032 is an unknown value
R9 =0x00000007107f73c0 is an oop: org.hyperic.sigar.Sigar
{0x00000007107f73c0} - klass: 'org/hyperic/sigar/Sigar'
R10=0x0000000000000010 is an unknown value
R11=0x00007fff162b0188 jvm.dll
R12=0x0 is NULL
R13=0x000002197fe1ab48 is pointing into metadata
R14=0x000000256b8ff0b8 is pointing into the stack for thread: 0x00000219633f8800
R15=0x00000219633f8800 is a thread
Registers:
RAX=0x0000000009811c40, RBX=0x000002197fe1ab50, RCX=0x00000219633f8b40, RDX=0x000000256b8ff0b0
RSP=0x000000256b8fee50, RBP=0x000000256b8ff080, RSI=0x0000000000200021, RDI=0x0000000000000268
R8 =0x0000000000000032, R9 =0x00000007107f73c0, R10=0x0000000000000010, R11=0x00007fff162b0188
R12=0x0000000000000000, R13=0x000002197fe1ab48, R14=0x000000256b8ff0b8, R15=0x00000219633f8800
RIP=0x0000000010014ed4, EFLAGS=0x0000000000010202
Top of Stack: (sp=0x000000256b8fee50)
0x000000256b8fee50: 00000219633f8b40 000000256b8ff0b0
0x000000256b8fee60: 00000219633f8800 0000000000000000
0x000000256b8fee70: 0000000009811c40 0000000000000000
0x000000256b8fee80: 000000256b8ff0b8 000000001002113b
0x000000256b8fee90: 00000219633f8b40 000000256b8ff0b0
0x000000256b8feea0: 0000000000200021 0000000000000268
0x000000256b8feeb0: 0000000000000000 0000000000000000
0x000000256b8feec0: 0000000000000000 0000000000000000
0x000000256b8feed0: 0000000000000000 000002190875c9b0
0x000000256b8feee0: 00007fff160ce510 000002190860a550
0x000000256b8feef0: 000000037f73c000 00007fff15f009e5
0x000000256b8fef00: 000002197fe1ab50 00000219633f8800
0x000000256b8fef10: 0000000100000004 00007fff00000003
0x000000256b8fef20: 00000219633f9160 0000002800000003
0x000000256b8fef30: 00000219633f8800 000000256b8ff0b8
0x000000256b8fef40: 000002197fe1ab48 00007fff159c880f
Instructions: (pc=0x0000000010014ed4)
0x0000000010014eb4: 7c 24 20 00 75 15 48 8d 15 df 58 04 00 48 8b 4c
0x0000000010014ec4: 24 40 e8 45 00 00 00 33 c0 eb 32 48 8b 44 24 20
0x0000000010014ed4: 83 b8 38 01 00 00 00 74 1f 48 8b 44 24 20 44 8b
0x0000000010014ee4: 80 38 01 00 00 48 8b 54 24 20 48 8b 4c 24 40 e8
.
.
. (skip)
.
.
Stack slot to memory mapping:
stack at sp + 0 slots: 0x00000219633f8b40 points into unknown readable memory: 90 5d 23 16 ff 7f 00 00
stack at sp + 1 slots: 0x000000256b8ff0b0 is pointing into the stack for thread: 0x00000219633f8800
stack at sp + 2 slots: 0x00000219633f8800 is a thread
stack at sp + 3 slots: 0x0 is NULL
stack at sp + 4 slots: 0x0000000009811c40 is an unknown value
stack at sp + 5 slots: 0x0 is NULL
stack at sp + 6 slots: 0x000000256b8ff0b8 is pointing into the stack for thread: 0x00000219633f8800
stack at sp + 7 slots: 0x000000001002113b sigar-amd64-winnt.dll
--------------- S Y S T E M ---------------
OS: Windows 10 , 64 bit Build 17134 (10.0.17134.753)
CPU:total 8 (initial active 8) (4 cores per cpu, 2 threads per core) family 6 model 158 stepping 9, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, avx, avx2, aes, clmul, erms, rtm, 3dnowpref, lzcnt, ht, tsc, tscinvbit, bmi1, bmi2, adx, fma
Memory: 4k page, system-wide physical 16287M (6175M free)
TotalPageFile size 23455M (AvailPageFile size 6527M)
current process WorkingSet (physical memory assigned to process): 74M, peak: 74M
current process commit charge ("private bytes"): 355M, peak: 355M
vm_info: Java HotSpot(TM) 64-Bit Server VM (11.0.6+8-LTS) for windows-amd64 JRE (11.0.6+8-LTS), built on Dec 11 2019 09:17:57 by "mach5one" with MS VC++ 15.5 (VS2017)
END.

Related

libnfc fails to connect to PN532 via I2C with timeout error

I want to read NFC tags using a PN532 NFC reader, which is connected via I2C to a Raspberry Pi Zero. The Pi has I2C enabled via raspi-config.
When attempting to access the device using nfc-list or nfc-pull I get a timeout error:
$ nfc-list
debug libnfc.general log_level is set to 3
debug libnfc.general allow_autoscan is set to true
debug libnfc.general allow_intrusive_scan is set to false
debug libnfc.general 1 device(s) defined by user
debug libnfc.general #0 name: "PN532 over I2C", connstring: "pn532_i2c:/dev/i2c-1"
nfc-list uses libnfc 1.8.0
debug libnfc.general 0 device(s) found using acr122_usb driver
debug libnfc.general 0 device(s) found using pn53x_usb driver
debug libnfc.chip.pn53x Diagnose
debug libnfc.chip.pn53x Timeout value: 500
debug libnfc.chip.pn53x SAMConfiguration
debug libnfc.chip.pn53x Timeout value: 1000
debug libnfc.bus.i2c TX: 00 00 ff 03 fd d4 14 01 17 00
debug libnfc.bus.i2c wrote 10 bytes successfully.
debug libnfc.driver.pn532_i2c timeout reached with no READY frame.
pn53x_check_communication: Timeout
debug libnfc.chip.pn53x InRelease
debug libnfc.bus.i2c TX: 00 00 ff 03 fd d4 52 00 da 00
debug libnfc.bus.i2c wrote 10 bytes successfully.
debug libnfc.driver.pn532_i2c timeout reached with no READY frame.
debug libnfc.general Unable to open "pn532_i2c:/dev/i2c-1".
nfc-list: ERROR: Unable to open NFC device: pn532_i2c:/dev/i2c-1
It may be related that i2cdetect reports that there exists a device at every address once the PN532 is connected to the Pi:
$ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77
If the PN532 is disconnected from the Pi, i2cdetect only finds one device:
$ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- 67 -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
There are only two i2c interfaces in /dev and i2c-2 does not have any connected devices.
$ ls -la /dev/ | grep i2c
crw-rw---- 1 root i2c 89, 1 Jun 23 15:39 i2c-1
crw-rw---- 1 root i2c 89, 2 Jun 23 15:35 i2c-2
How do I fix the timeout error?

How to fire PCIe interrupt on Linux Intel Xeon

I am looking at a Linux-Intel-Xeon board which has a PCIe Switch (config Space shown below). On the the other side of the LinuxSwitch, via a CABLE there is a different OtherBoard running my software (non-Intel CPU, non-Linux-OS and BSP, which I understand quite well), and it has another switch and an endpoint/s (EP). From the OtherBoard I want to write to shared memory (e.g. on Linux addres 0xB000 0000), and inform LinuxBoardCpu via MSI.
Focusing on MSI (not general interrupts and not general enumeration). I have two main separate questions:
Q1 How does the SW on the OtherBoard cause an MSI to the LinuxBoard, does the OtherBoard perform a write to Linux 0xFEEE_0D38 (e.g. with data=0x0 or data=0x1)? Or does the OtherBoard write 0x1 to a register on the LinuxBoard's-Switch. I should be able to test this from the Linux side only by writing to 0xFEEE_0D38. How do I get a ptr to that address?
Q2 Just focusing on the LinuxBoard Switch-CPU-Memory: how do I effect the write to LinuxBoard's DRAM/DDR/memory address 0xB000_0000? It seems I need a translation of some some sort at the LinuxCPU. The LinuxSwitch will forward the write-address-data to the LinuxSwitch which forwards to the LinuxCPU, but do I need to setup the LinuxCpu to accept the access, or how does the memory-write access the 0xB000_0000?
I wrote a quick program to explore and dump the Linux PCIeBoard Switch's Config Space
04 10 BAR0 : 0x90800000
05 14 BAR1 : 0x00000000
08 20 MemLim, MemBase : 0x90509050 <<<<\b
09 24 PrefetchMems LnB : 0x90219001
10 28 PrefetchUpBaseAdd : 0x00000000
11 2C PrefecthLimAdd : 0x00000000
12 30 IoLimU16 IoBaseU16: 0x00000000
13 34 ......Cap : 0x00000040
14 38 reserved : 0x00000000
15 3C ....InLine : 0x001001ff
16 40 .... MSICapPtr : 0xc8034801
17 44 : 0x00000008
18 48 MSIintCtrl Nxt ID : 0x01876805
19 4C LowerMsgAddr : 0xfee003d8 <<<<
20 50 UpperMsgAddr : 0x00000000
21 54 .... MsgData : 0x00000000
26 68 Cap, Nxt ID : 0x0052a410
27 6C DevCap : 0x012c8003
28 70 DevStat DevCtrl : 0x00090830
29 74 LnkCap : 0x00416883
30 78 LnkStat ..LnkCtr : 0x10830040
31 7C : 0x00000000
32 80 : 0x00000000

pkcs11-tool does not see card which is identified by pcsc

I am using a REINER SCT cyberJack RFID standard card reader and an estonian ID card.
pcsc_scan correctly identifies the card:
$ pcsc_scan
PC/SC device scanner
V 1.5.2 (c) 2001-2017, Ludovic Rousseau <ludovic.rousseau#free.fr>
Using reader plug'n play mechanism
Scanning present readers...
0: REINER SCT cyberJack RFID standard (9084002233) 00 00
Wed Mar 13 14:02:39 2019
Reader 0: REINER SCT cyberJack RFID standard (9084002233) 00 00
Card state: Card inserted,
ATR: 3B DB 96 00 80 B1 FE 45 1F 83 00 12 23 3F 53 65 49 44 0F 90 00 F1
ATR: 3B DB 96 00 80 B1 FE 45 1F 83 00 12 23 3F 53 65 49 44 0F 90 00 F1
+ TS = 3B --> Direct Convention
+ T0 = DB, Y(1): 1101, K: 11 (historical bytes)
TA(1) = 96 --> Fi=512, Di=32, 16 cycles/ETU
250000 bits/s at 4 MHz, fMax for Fi = 5 MHz => 312500 bits/s
TC(1) = 00 --> Extra guard time: 0
TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0
-----
TD(2) = B1 --> Y(i+1) = 1011, Protocol T = 1
-----
TA(3) = FE --> IFSC: 254
TB(3) = 45 --> Block Waiting Integer: 4 - Character Waiting Integer: 5
TD(3) = 1F --> Y(i+1) = 0001, Protocol T = 15 - Global interface bytes following
-----
TA(4) = 83 --> Clock stop: state H - Class accepted by the card: (3G) A 5V B 3V
+ Historical bytes: 00 12 23 3F 53 65 49 44 0F 90 00
Category indicator byte: 00 (compact TLV data object)
Tag: 1, len: 2 (country code, ISO 3166-1)
Country code: 23 3F
Tag: 5, len: 3 (card issuer's data)
Card issuer data: 65 49 44
Mandatory status indicator (3 last bytes)
LCS (life card cycle): 0F (unknown)
SW: 9000 (Normal processing.)
+ TCK = F1 (correct checksum)
Possibly identified card (using /home/mag/.cache/smartcard_list.txt):
3B DB 96 00 80 B1 FE 45 1F 83 00 12 23 3F 53 65 49 44 0F 90 00 F1
Estonia ID-card (eID)
https://id.ee
however pkcs11-tool does not see the card:
$ pkcs11-tool --module /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so -L
Available slots:
Slot 0 (0x0): REINER SCT cyberJack RFID standard (9084002233) 00 00
(empty)
What can be the cause of the problem? What do I miss?
Apparently the toolchain of the estonian card is not compatible with pkcs-11. However the chrome-token-signing package contains the needed code at least for authentication to their service both for chromium and firefox, and the qdigidoc4 package contains a tool to create and check signed/encrypted documents.
Their repo is here:
deb https://installer.id.ee/media/ubuntu/ bionic main
Another issue I have encountered that my cert is said to be invalid. That was because the certificate won't get enabled right away when you receive your ID.

MMC crash in windows 10

On my Windows 10, mmc.exe crashes when I try to add the certificate snap-in. When I click "Ok" after having added the snap-in (computer account, local computer) the message: "Microsoft Management Console has stopped working" and I am offered a debug option.
There are no further error messages.
I have tried to run "sfc /scannow" and found nothing to repair.
The MMC is crashing because of the SqlManager.dll from SQLServer 2014 RTM (2014.0120.2000.08 ((SQL14_RTM).140220-1924 ))
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
DUMP_CLASS: 2
DUMP_QUALIFIER: 400
CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000072f3df90 rcx=000000000000000a
rdx=0000000072f3df90 rsi=0000000000000000 rdi=0000000080000010
rip=00007ffcb524a030 rsp=000000000f13ec18 rbp=000000001339d408
r8=000000000f13eb78 r9=000000001339d408 r10=0000000000000000
r11=000000000f13ebe0 r12=0000000000220a5e r13=0000000000000090
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
ntdll!RtlFailFast2:
00007ffc`b524a030 cd29 int 29h
Resetting default scope
FAULTING_IP:
ntdll!RtlFailFast2+0
00007ffc`b524a030 cd29 int 29h
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffcb524a030 (ntdll!RtlFailFast2)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 000000000000000a
Subcode: 0xa FAST_FAIL_GUARD_ICALL_CHECK_FAILURE
PROBLEM_CLASSES:
ID: [0n262]
Type: [FAIL_FAST]
Class: Primary
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Add
Data: Omit
PID: [Unspecified]
TID: [Unspecified]
Frame: [0]
ID: [0n256]
Type: [GUARD_ICALL_CHECK_FAILURE]
Class: Addendum
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Add
Data: Omit
PID: [Unspecified]
TID: [Unspecified]
Frame: [0]
ID: [0n92]
Type: [AVRF]
Class: Addendum
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Add
Data: Omit
PID: [0x3be8]
TID: [0x3cf0]
Frame: [0] : ntdll!RtlFailFast2
BUGCHECK_STR: FAIL_FAST_GUARD_ICALL_CHECK_FAILURE_AVRF
DEFAULT_BUCKET_ID: FAIL_FAST_GUARD_ICALL_CHECK_FAILURE_AVRF
PRIMARY_PROBLEM_CLASS: FAIL_FAST
STACK_TEXT:
00 ntdll!RtlFailFast2
01 ntdll!RtlpHandleInvalidUserCallTarget
02 ntdll!LdrpHandleInvalidUserCallTarget
03 user32!UserCallWinProcCheckWow
04 user32!DispatchClientMessage
05 user32!_fnDWORD
06 ntdll!KiUserCallbackDispatcherContinue
07 win32u!NtUserDestroyWindow
08 SqlManager_72c70000!CEventRegWnd::~CEventRegWnd
09 SqlManager_72c70000!CRT_INIT
0a SqlManager_72c70000!CRT_INIT
0b verifier!AVrfpStandardDllEntryPointRoutine
0c ntdll!LdrpCallInitRoutine
0d ntdll!LdrpProcessDetachNode
0e ntdll!LdrpUnloadNode
0f ntdll!LdrpDecrementModuleLoadCountEx
10 ntdll!LdrUnloadDll
11 KERNELBASE!FreeLibrary
12 combase!CClassCache::CDllPathEntry::CFinishObject::Finish
13 combase!CClassCache::CFinishComposite::Finish
14 combase!CClassCache::CleanUpDllsForApartment
15 combase!CCCleanUpDllsForApartment
16 combase!FinishShutdown::__l2::<lambda_ac39365968346bea08de70a73a47183a>::operator()
17 combase!ObjectMethodExceptionHandlingAction<<lambda_ac39365968346bea08de70a73a47183a> >
18 combase!FinishShutdown
19 combase!ApartmentUninitialize
1a combase!wCoUninitialize
1b combase!CoUninitialize
1c verifier!AVrfpCoUninitialize
1d mmcndmgr!MMC21ADDREMOVEUI::CAboutInfoThread::ThreadProc
1e msvcrt!_callthreadstartex
1f msvcrt!_threadstartex
20 verifier!AVrfpStandardThreadFunction
21 kernel32!BaseThreadInitThunk
22 ntdll!RtlUserThreadStart
So update the SQL Server to latest Service Pack and Update Hotfix Rollup. Import the uninstall .reg to disable dump creation and app verifier.

JVM Crash due to `EXCEPTION_ACCESS_VIOLATION` in org.infinispan.util.concurrent.jdk8backported.LongAdder

This is happening on JBoss EAP 6.1, for single user it works fine, But as soon as 2 or 3 concurrent user start interacting with the application, JVM gets crashed.
The JVM is crashing with EXCEPTION_ACCESS_VIOLATION; the full trace is below:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x024c8266, pid=5136, tid=8736
#
# JRE version: 6.0_45-b06
# Java VM: Java HotSpot(TM) Client VM (20.45-b01 mixed mode windows-x86 )
# Problematic frame:
# J org.infinispan.util.concurrent.jdk8backported.LongAdder.add(J)V
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x6602dc00): JavaThread "http-ds-7071bc90200f..corp.in/10.112.70.75:8080-6" daemon [_thread_in_Java, id=8736, stack(0x663a0000,0x663f0000)]
siginfo: ExceptionCode=0xc0000005, reading address 0x8ddb6987
Registers:
EAX=0x00000002, EBX=0xffffffff, ECX=0x00000001, EDX=0x0ddb6988
ESP=0x663ee3c0, EBP=0x663eea58, ESI=0x0ddb60a0, EDI=0xffffffff
EIP=0x024c8266, EFLAGS=0x00010293
Top of Stack: (sp=0x663ee3c0)
0x663ee3c0: 0ddb4830 00000000 663eea58 024d2b44
0x663ee3d0: 0ddb1610 0ddb1610 663eea58 024d7368
0x663ee3e0: 0ddb4830 00000000 0ddb1610 0ddb6be0
0x663ee3f0: 22239910 0ddb1610 2223aff0 22239910
0x663ee400: 0ddb60a0 2223c338 2127c660 24bb6ca8
0x663ee410: 24c1f6e0 0ddb6070 00000002 0ddb6988
0x663ee420: 4ac892b3 0ddb1610 663eea58 024d5bf4
0x663ee430: 00000000 00000000 663eea58 024c5a0c
Instructions: (pc=0x024c8266)
0x024c8246: 0c 00 00 00 b8 01 00 00 00 8b f7 e9 5b 00 00 00
0x024c8256: 8b bc 24 80 00 00 00 8b 9c 24 84 00 00 00 3b 02
0x024c8266: f2 0f 10 82 ff ff ff 7f 66 0f 7e c6 66 0f 73 d0
0x024c8276: 20 66 0f 7e c0 8b d6 8b c8 03 d7 13 cb 89 34 24
Register to memory mapping:
EAX=0x00000002 is an unknown value
EBX=0xffffffff is an unknown value
ECX=0x00000001 is an unknown value
EDX=
[error occurred during error reporting (printing register info), id 0xc0000005]
Stack: [0x663a0000,0x663f0000], sp=0x663ee3c0, free space=312k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
J org.infinispan.util.concurrent.jdk8backported.LongAdder.add(J)V
j org.infinispan.CacheImpl.put(Ljava/lang/Object;Ljava/lang/Object;JLjava/util/concurrent/TimeUnit;JLjava/util/concurrent/TimeUnit;Ljava/util/EnumSet;Ljava/lang/ClassLoader;)Ljava/lang/Object;+24
j org.infinispan.CacheImpl.put(Ljava/lang/Object;Ljava/lang/Object;JLjava/util/concurrent/TimeUnit;JLjava/util/concurrent/TimeUnit;)Ljava/lang/Object;+12
j org.infinispan.CacheSupport.put(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;+17
j org.infinispan.AbstractDelegatingCache.put(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;+6
j org.infinispan.spring.provider.SpringCache.put(Ljava/lang/Object;Ljava/lang/Object;)V+6
j com.hmtp.security.server.util.SessionTokenValidator.refreshAccessTime(Ljava/lang/String;)V+25
j com.hmtp.security.server.util.SessionTokenValidator.checkAndRenewToken([Ljava/lang/String;)Lorg/springframework/security/web/authentication/rememberme/PersistentRememberMeToken;+174
j com.hmtp.security.server.auth.MultiTenantRememberMeServices.processAutoLoginCookie([Ljava/lang/String;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)Lorg/springframework/security/core/userdetails/UserDetails;+5
j org.springframework.security.web.authentication.rememberme.AbstractRememberMeServices.autoLogin(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)Lorg/springframework/security/core/Authentication;+64
j com.hmtp.common.security.server.BrownstoneRememberMeAuthenticationFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V+20
J org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
J org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
J org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
J org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
J org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
J org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
J org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
j org.springframework.security.web.FilterChainProxy.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V+40
j org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(Ljavax/servlet/Filter;Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V+5
j org.springframework.web.filter.DelegatingFilterProxy.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V+71
J org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
J org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V
j org.apache.catalina.core.StandardContextValve.invoke(Lorg/apache/catalina/connector/Request;Lorg/apache/catalina/connector/Response;)V+200
j org.jboss.as.web.session.ClusteredSessionValve.handleRequest(Lorg/apache/catalina/connector/Request;Lorg/apache/catalina/connector/Response;Lorg/jboss/servlet/http/HttpEvent;Z)V+61
j org.jboss.as.web.session.ClusteredSessionValve.invoke(Lorg/apache/catalina/connector/Request;Lorg/apache/catalina/connector/Response;)V+26
j org.jboss.as.web.session.JvmRouteValve.invoke(Lorg/apache/catalina/connector/Request;Lorg/apache/catalina/connector/Response;)V+33
j org.jboss.as.web.session.LockingValve.invoke(Lorg/apache/catalina/connector/Request;Lorg/apache/catalina/connector/Response;)V+43
j org.jboss.as.web.security.SecurityContextAssociationValve.invoke(Lorg/apache/catalina/connector/Request;Lorg/apache/catalina/connector/Response;)V+402
J org.apache.catalina.core.StandardHostValve.invoke(Lorg/apache/catalina/connector/Request;Lorg/apache/catalina/connector/Response;)V
j org.apache.catalina.core.StandardEngineValve.invoke(Lorg/apache/catalina/connector/Request;Lorg/apache/catalina/connector/Response;)V+42
j org.apache.catalina.connector.CoyoteAdapter.service(Lorg/apache/coyote/Request;Lorg/apache/coyote/Response;)V+188
j org.apache.coyote.http11.Http11Processor.process(Ljava/net/Socket;)Lorg/apache/tomcat/util/net/JIoEndpoint$Handler$SocketState;+349
j org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Ljava/net/Socket;)Lorg/apache/tomcat/util/net/JIoEndpoint$Handler$SocketState;+65
j org.apache.tomcat.util.net.JIoEndpoint$Worker.run()V+128
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub
V [jvm.dll+0xfb88b]
V [jvm.dll+0x18d551]
V [jvm.dll+0xfba31]
V [jvm.dll+0xfba8b]
V [jvm.dll+0xb5e89]
V [jvm.dll+0x119b74]
V [jvm.dll+0x14217c]
C [msvcr71.dll+0x9565] endthreadex+0xa0
C [kernel32.dll+0x4ee6c] BaseThreadInitThunk+0x12
C [ntdll.dll+0x6399b] RtlInitializeExceptionChain+0xef
C [ntdll.dll+0x6396e] RtlInitializeExceptionChain+0xc2
VM state:synchronizing (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x00dd8360] Safepoint_lock - owner thread: 0x01a68c00
[0x00dd83c8] Threads_lock - owner thread: 0x01a68c00
Heap
def new generation total 400384K, used 175418K [0x03ae0000, 0x1ed50000, 0x1ed80000)
eden space 355904K, 47% used [0x03ae0000, 0x0df2c4f0, 0x19670000)
from space 44480K, 16% used [0x1c1e0000, 0x1c8e2540, 0x1ed50000)
to space 44480K, 0% used [0x19670000, 0x19670000, 0x1c1e0000)
tenured generation total 889536K, used 111605K [0x1ed80000, 0x55230000, 0x552e0000)
the space 889536K, 12% used [0x1ed80000, 0x25a7d7f0, 0x25a7d800, 0x55230000)
compacting perm gen total 102144K, used 102123K [0x552e0000, 0x5b6a0000, 0x652e0000)
the space 102144K, 99% used [0x552e0000, 0x5b69ad60, 0x5b69ae00, 0x5b6a0000)
No shared spaces configured.
Code Cache [0x01ae0000, 0x02cb8000, 0x03ae0000)
total_blobs=9369 nmethods=9146 adapters=163 free_code_cache=14876096 largest_free_block=384
VM Arguments:
jvm_args: -Dprogram.name=standalone.bat -Xms1303M -Xmx1303M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -Dorg.jboss.boot.log.file=C:\jboss-eap-6.1\standalone\log\server.log -Dlogging.configuration=file:C:\jboss-eap-6.1\standalone/configuration/logging.properties
java_command: C:\jboss-eap-6.1\jboss-modules.jar -mp C:\jboss-eap-6.1\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=C:\jboss-eap-6.1
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=C:\Program Files\Java\jdk1.6.0_45
PATH=C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Java\jdk1.6.0_45\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\apache-maven-3.2.2\bin;C:\Program Files\TortoiseSVN\bin;D:\apache-ant-1.9.4\bin
USERNAME=neeraj.ar
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 6 Model 23 Stepping 10, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows 7 Build 7601 Service Pack 1
CPU:total 2 (2 cores per cpu, 1 threads per core) family 6 model 23 stepping 10, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1
Memory: 4k page, physical 3338764k(929876k free), swap 15625020k(11901304k free)
vm_info: Java HotSpot(TM) Client VM (20.45-b01) for windows-x86 JRE (1.6.0_45-b06), built on Mar 26 2013 13:40:03 by "java_re" with MS VC++ 7.1 (VS2003)
time: Thu Jul 23 18:41:10 2015
elapsed time: 256 seconds
The crash happens in C1-compiled code on the instruction
f20f1082ffffff7f movsd xmm0, qword ptr [edx+0x7fffffff]
which represents a volatile long load that has not been patched.
I believe this is a JVM bug JDK-6965570 or its duplicate JDK-7004258.
It has been fixed a long ago in JDK 6u60, but you seem to use very old version of JDK.