Alejandro Revilla
Alejandro Revilla
Add ability to handle SystemErrors in the same way we handle AbortParticipants.
Class needs full review and upgrade to java time. (Thanks Sebastien for the heads-up on this).
https://www2.cs.duke.edu/csed/java/jdk1.7/technotes/guides/security/jsse/FIPS.html
On one-shot connections, the peer-disconnect message can become annoying. We should have the ability to prevent logging them.
When finding the PAN, CardHolder defaults to DE35 first, an Card to DE2 first. https://github.com/jpos/jPOS/blob/master/jpos/src/main/java/org/jpos/core/CardHolder.java#L111 take pan from DE35 first, but https://github.com/jpos/jPOS/blob/master/jpos/src/main/java/org/jpos/core/Card.java#L193 takes it first from DE2 For consistency and...
From PR197 ``` org.jpos.gl.AccountLockTest > executionError FAILED org.hibernate.HibernateException: Detected concurrent management of connection resources. This might indicate a multi-threaded use of Hibernate in combination with managed resources, which is not...
Probably we don't need both.
_ditto_, the OneShotChannelAdaptor should expose a `ready` indicator. If a connection is refused, indicator should be removed, and an emergency thread should regularly check the remote host in order to...