Hi jPOS team,
First of all, thanks for the great work, jPOS is wonderful when dealing with ISO8583 :x
Second, I am building a HSM Gateway using jPOS.
Client -----> HSM-REST-API
-----> HSM-GATEWAY
-----> HSM
- HSM-GATEWAY is configured as a QServer to listen on a specific port, using MuxPool to forward command to selected HSM.
- We used HSM BP-Tools to send command to the port and successfully got response.
- HSM-REST-API uses FSDChannel to send HSM command to HSM-GATEWAY
- HSM-REST-API successfully sent commands to HSM IP/PORT
- But when sending the same to HSM-GATEWAY, we faced "Software caused connection abort: recv failed" when initiating request from HSM-REST-API to HSM-GATEWAY
Here are the logs:
HSM-REST-API
<log realm="com.xxx.resthsm.jpos.HThalesAdaptor" at="2021-11-15T11:03:49.067">
<warn>
channel-sender-hthales-api-send
Software caused connection abort: recv failed
</warn>
</log>
<log realm="com.xxx.resthsm.jpos.HThalesAdaptor" at="2021-11-15T11:03:50.072">
<warn>
checkConnection HThalesAdaptor 2
</warn>
</log>
HSM-GATEWAY
<log realm="server-8001.server.session/
127.0.0.1:58602" at="2021-11-15T11:03:50.073">
<session-start>
access granted, ip=127.0.0.1
</session-start>
</log>
<log realm="channel/
127.0.0.1:58602" at="2021-11-15T11:04:00.088" lifespan="10013ms">
<receive>
<io-timeout/>
</receive>
</log>
I resume the situation, those folow are OK:
- Client -----> HSM-REST-API -----> HSM
- BP Tools HSM -----> HSM-GATEWAY -----> HSM
Got "Software caused connection abort: recv failed" when doing::
- Client -----> HSM-REST-API -----> HSM-GATEWAY -----> HSM
- HSM-REST-API caused a connection abort just after trying to send command to HSM-GATEWAY.
- HSM-GATEWAY somewhat grants access for HSM-REST-API, but it seems nothing happened, so it raise io-timeout after 10s (configured value)
Anyone in the group having the same Software caused connection abort: recv failed" issue?
Or is there any tools (debug filter) so we can investigate on socket level of JPOS to troubleshoot the root cause?
Any help is appreciated :x