Hi Dominique,
I suspect the problem comes from:
Pipeline: com.sun.jbi.httpsoapbc.embedded.LinkedListThrottlePipeline
JBI replaces Glassfish thread-pool by its own.
Can you pls. try to find the java implementation of the mentioned pipeline? In theory you can just change its code to use SSLWorkerThreadImpl as a thread-pool thread type and it should fix the problem.
Thanks.
WBR,
Alexey.
On 08/26/2011 12:18 AM, dominique.bessette_at_gdit.com wrote:
> Hi
>
> I get an error when I deploy a BPEL Composite Application in a
> servicemix war and i try to hit the WSDL using two-way SSL. When I use
> one-way or no SSL , I can hit the WSDL. Here's the error:
>
> 2011-08-25 15:08:35,005 INFO [STDOUT] Using SSLEngineImpl.
> 2011-08-25 15:08:35,021 DEBUG [GRIZZLY] workerThread.httpException
> java.lang.ClassCastException:
> com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl cannot be
> cast to com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread
> at
> com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTask.doTask(SSLRead
> Task.java:213)
> at
> com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:269
> )
> at
> com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThr
> eadImpl.java:122)
>
>
> I updated grizzly to use v1.0.40.
>
> 2011-08-25 15:08:02,599 INFO [GRIZZLY]
> Grizzly 1.0.40 running on Windows XP-5.1 under JDK version:
> 1.6.0_26-Sun Microsystems Inc.
> port: 8443
> socket-tcp-no-delay-enabled: true
> socket-keep-alive-enabled: false
> socket-linger: -1
> socket-oob-inline-enabled: false
> default-write-timeout-millis: 30000
> maxThreads: 5
> ByteBuffer size: 8192
> useDirectByteBuffer: 8192
> maxKeepAliveRequests: 256
> keepAliveTimeoutInSeconds: 30
> Static File Cache enabled: true
> Pipeline :
> com.sun.jbi.httpsoapbc.embedded.LinkedListThrottlePipeline
> Round Robin Selector Algorithm enabled: false
> Round Robin Selector pool size: 0
> Asynchronous Request Processing enabled: true
>
> Any insight would be very helpful.
>
> Thank You