There is an issue using this api with multiple palo connections, because the handlers like HeaderHandler are all singletons. So if multiple connections are performing operations in parallel, they use the same handler instance, which switches the connection it is using. This leads to deadlocks, and hangs, because a handler sent a request on one connection, , which got switched to another in between, and now is expects response from another connection, which already finished processing. A simple fix is to change the getInstance() method of the handlers to return a new instance instead of the static singleton.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Welcome to Open Discussion
I am using jpalo, where is the good place for discuss jpalo?
There is an issue using this api with multiple palo connections, because the handlers like HeaderHandler are all singletons. So if multiple connections are performing operations in parallel, they use the same handler instance, which switches the connection it is using. This leads to deadlocks, and hangs, because a handler sent a request on one connection, , which got switched to another in between, and now is expects response from another connection, which already finished processing. A simple fix is to change the getInstance() method of the handlers to return a new instance instead of the static singleton.