<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent posts to Discussion</title><link>https://sourceforge.net/p/jpalo/discussion/</link><description>Recent posts to Discussion</description><atom:link href="https://sourceforge.net/p/jpalo/discussion/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 13 Mar 2017 07:00:22 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/jpalo/discussion/feed.rss" rel="self" type="application/rss+xml"/><item><title>Welcome to Open Discussion</title><link>https://sourceforge.net/p/jpalo/discussion/752944/thread/cc6dd2ef/?limit=25#0e73</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;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.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Manoj Mokashi</dc:creator><pubDate>Mon, 13 Mar 2017 07:00:22 -0000</pubDate><guid>https://sourceforge.netc2e4e53f73dbd901c8ddcc059a4771d47f6c0572</guid></item></channel></rss>