Re: async problem ; Illegal State Exception

2015-12-30 Thread Sergey Beryozkin
Hi Benson Does it happen only when org.jolokia.osgi.security.BasicAuthenticationHttpContext.handleSecurity deals with the wrong user credentials, i.e, does it call HttpServletResponseWrapper.sendError ? May be that can explain it because that would probably bypass the async response channel

Re: async problem ; Illegal State Exception

2015-12-30 Thread Benson Margulies
On Wed, Dec 30, 2015 at 6:28 AM, Sergey Beryozkin wrote: > Hi Benson > > Does it happen only when > > org.jolokia.osgi.security.BasicAuthenticationHttpContext.handleSecurity Sergey, there are no credentials anywhere that I know of. I'm invoking my endpoint, not jolokia, and

Re: async problem ; Illegal State Exception

2015-12-30 Thread Sergey Beryozkin
Hi On 30/12/15 13:13, Benson Margulies wrote: On Wed, Dec 30, 2015 at 6:28 AM, Sergey Beryozkin wrote: Hi Benson Does it happen only when org.jolokia.osgi.security.BasicAuthenticationHttpContext.handleSecurity Sergey, there are no credentials anywhere that I know of.

async problem ; Illegal State Exception

2015-12-29 Thread Benson Margulies
I switched some code of mine to use AsyncRequest, and I get some scary backtraces even though everything seems to be working just fine. Note the presence of org.jolokia.osgi.security.BasicAuthenticationHttpContext.handleSecurity in the backtrace. Now, I am running in Karaf with the jolokia

Re: async problem ; Illegal State Exception

2015-12-29 Thread Benson Margulies
Removing jolokia made this disappear, so I don't think it belongs here, however odd it is that it only appeared with the use of CXF async. On Tue, Dec 29, 2015 at 2:38 PM, Benson Margulies wrote: > I switched some code of mine to use AsyncRequest, and I get some scary >