Mule › Mule - Issues

[mule-jira] (MULE-8615) Regression found on proxy scenario with the new http module.

Classic

List

Threaded

1 message

JIRA no-reply@mulesource.com

[mule-jira] (MULE-8615) Regression found on proxy scenario with the new http module.

Message Title

Luciano Gandini commented on

MULE-8615

between those builds the ahc library was upgraded from 1.9.19 to 1.9.21, this change introduced a contention in:

Stacks at 10:51:54 AM (uptime 7m 54 sec)

[http_module_proxy].http.requester.requestConfig(18) SelectorRunner [BLOCKED]
org.glassfish.grizzly.connectionpool.SingleEndpointPool.release0(ConnectionInfo)
org.glassfish.grizzly.connectionpool.MultiEndpointPool.release(Connection)
com.ning.http.client.providers.grizzly.ConnectionManager.returnConnection(Connection)
com.ning.http.client.providers.grizzly.AhcEventFilter.cleanup(HttpContext)
com.ning.http.client.providers.grizzly.AhcEventFilter.onHttpPacketParsed(HttpHeader, FilterChainContext)
org.glassfish.grizzly.http.HttpCodecFilter.decodeWithTransferEncoding(FilterChainContext, HttpHeader, Buffer, boolean)
org.glassfish.grizzly.http.HttpCodecFilter.handleRead(FilterChainContext, HttpHeader)
org.glassfish.grizzly.http.HttpClientFilter.handleRead(FilterChainContext)
org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(Filter, FilterChainContext)
org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(FilterExecutor, Filter, FilterChainContext)
org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(FilterChainContext, FilterExecutor, int, int, DefaultFilterChain$FiltersState)
org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(FilterChainContext)
org.glassfish.grizzly.filterchain.DefaultFilterChain.process(Context)
org.glassfish.grizzly.ProcessorExecutor.execute(Context)
org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(IOEvent, Connection, IOEventLifeCycleListener)
org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(Connection, IOEvent, IOEventLifeCycleListener, Logger)
org.glassfish.grizzly.strategies.SameThreadIOStrategy.executeIoEvent(Connection, IOEvent, boolean)
org.glassfish.grizzly.strategies.AbstractIOStrategy.executeIoEvent(Connection, IOEvent)
org.glassfish.grizzly.nio.SelectorRunner.iterateKeyEvents()
org.glassfish.grizzly.nio.SelectorRunner.iterateKeys()
org.glassfish.grizzly.nio.SelectorRunner.doSelect()
org.glassfish.grizzly.nio.SelectorRunner.run()
org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork()
org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run()
java.lang.Thread.run()

possible solutions:
a) revert the changes and downgrade to 1.9.19 (the greeater changes of 1.9.21 where introduced in 1.9.20)
b) customize thread-pool creation
c) define custom thread-pool

Add Comment

This message was sent by Atlassian JIRA