How to connect to WbLogic JMS queue using t3s via full client with two way SSL authentication? -

i have struggled on 1 several days now. using weblogic 11g (10.3.4.0) on windows (linux behaves same). have setup 2 way ssl authentication following details http://emo.sourceforge.net/cert-login-howto.html , http://middlewareforum.com/weblogic/?p=312. used jmeter client following jvm parameters. standalone java client behaves same.

-djavax.net.ssl.keystoretype=pkcs12 -djavax.net.ssl.truststoretype=jks -djavax.net.ssl.keystore=c:/users/sli/keys/browser.p12 -djavax.net.debug=ssl -djavax.net.ssl.keystorepassword=password-djavax.net.ssl.truststorepassword=changeit -dweblogic.security.ssl.ignorehostnameverification=true

it works fine t3 thin client (wlthint3client.jar), not work when switch full client (wlfullclient.jar). 1 of applications somehow stuck full client. different problem own. btw, full client not full needs webserviceclient+ssl.jar , cryptoj.jar ssl. complains following @ client.

javax.naming.communicationexception [root exception java.net.connectexception: t3s://localhost:7503: destination unreachable; nested exception is: com.bea.sslplus.twowaysslhandshakestagesocketexception: socketexception during 2 way handshake; check client certificate or network connection; no available router destination]

here server side log.

<39146459 ssl version 2 no padding> <39149058 ssl3/tls mac> <39149058 received ssl_20_record> <39149058 ssl3/tls mac> <39149058 received handshake> (unknown source) @ com.certicom.tls.record.handshake.handshakehandler.firealert(unknown source) @ com.certicom.tls.record.handshake.serverstatesenthellodone.handle(unknown source) @ com.certicom.tls.record.handshake.handshakehandler.handlehandshakemessage(unknown source) @ com.certicom.tls.record.handshake.handshakehandler.handlehandshakemessages(unknown source) @ com.certicom.tls.record.messageinterpreter.interpretcontent(unknown source) @ com.certicom.tls.record.messageinterpreter.decryptmessage(unknown source) @ com.certicom.tls.record.readhandler.processrecord(unknown source) @ com.certicom.tls.record.readhandler.readrecord(unknown source) @ com.certicom.tls.record.readhandler.readuntilhandshakecomplete(unknown source) @ com.certicom.tls.interfaceimpl.tlsconnectionimpl.completehandshake(unknown source) @ javax.net.ssl.impl.sslsocketimpl.starthandshake(unknown source) @ weblogic.server.channels.dynamicssllistenthread$1.run(dynamicssllistenthread.java:130) @ weblogic.work.executethread.execute(executethread.java:207) @ weblogic.work.executethread.run(executethread.java:176) > <37447543 ssl version 2 no padding> <37447552 ssl3/tls mac> <37447552 received ssl_20_record> <37447552 ssl3/tls mac> <37447552 received handshake> (unknown source) @ com.certicom.tls.record.handshake.handshakehandler.firealert(unknown source) @ com.certicom.tls.record.handshake.serverstatesenthellodone.handle(unknown source) @ com.certicom.tls.record.handshake.handshakehandler.handlehandshakemessage(unknown source) @ com.certicom.tls.record.handshake.handshakehandler.handlehandshakemessages(unknown source) @ com.certicom.tls.record.messageinterpreter.interpretcontent(unknown source) @ com.certicom.tls.record.messageinterpreter.decryptmessage(unknown source) @ com.certicom.tls.record.readhandler.processrecord(unknown source) @ com.certicom.tls.record.readhandler.readrecord(unknown source) @ com.certicom.tls.record.readhandler.readuntilhandshakecomplete(unknown source) @ com.certicom.tls.interfaceimpl.tlsconnectionimpl.completehandshake(unknown source) @ javax.net.ssl.impl.sslsocketimpl.starthandshake(unknown source) @ weblogic.server.channels.dynamicssllistenthread$1.run(dynamicssllistenthread.java:130) @ weblogic.work.executethread.execute(executethread.java:207) @ weblogic.work.executethread.run(executethread.java:176) >

i have done research , found (http://stackoverflow.com/questions/2047732/solaris-jms-client-connect-to-weblogic-11g-t3s-security-problem) has gotten working using full client on t3s 2 way ssl authentication, link not provide how. have tried use weblogic security option mentioned there , still not work me.

thank of help.

you'll have use properties these when setting ssl wlfullclient:

-dweblogic.security.trustkeystore=customtrust -dweblogic.security.customtrustkeystorefilename=.... 

do search weblogic.security.trustkeystore find relevant settings.