I am trying to use shared boss pool (netty Producer) using the below registry
entries.

URI:
<to
                                        
uri="netty:tcp://localhost:5001?bossPool=#sharedPool&amp;encoding={{tcpEncoding}}&amp;clientPipelineFactory=#customClientPipelineFactory&amp;sync=true&amp;requestTimeout={{tcpResponseTimeOut}}"
/>
                                

Registry Entries:
        
        <bean id="bosspoolBuilder"
class="org.apache.camel.component.netty.NettyClientBossPoolBuilder">
                        <property name="bossCount" value="10" />
        
        </bean>

        
        <bean id="sharedPool" 
class="org.jboss.netty.channel.socket.nio.BossPool"
                factory-bean="bosspoolBuilder" factory-method="build"
destroy-method="shutdown">
        </bean>


Nov 16, 2015 11:27:09 PM
org.jboss.netty.channel.socket.nio.AbstractNioSelector
WARNING: Unexpected exception in the selector loop.
java.lang.NullPointerException
        at
org.jboss.netty.channel.socket.nio.NioClientBoss$RegisterTask.run(NioClientBoss.java:185)
        at
org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)
        at
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)
        at
org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)
        at
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
        at
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)


Anyone came across this error? 

My Camel Version: 2.14.0
Netty Version: 3.9.4





--
View this message in context: 
http://camel.465427.n5.nabble.com/Shared-BossPool-Configuration-in-Netty-throws-Unexpected-Exception-tp5773959.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to