Thanks for sending us the updated jar. Initial tests show that it is working!

I'll post here if any other issues appear.

I'll spend some time moving the JCAPI.jar around and putting it in different locations to see if that helps.

We have had class loader issues with JAX-WS before. Initially we tried to deploy the JAX-WS libraries with each web service deployed to Tomcat, but we found this allowed only one web service to run on a server. We then moved those libraries into the shared lib area of Tomcat and the problem went away. Perhaps this sort of problem is affecting the operation of the JCAPI.jar?

At the moment JCAPI is being packaged with our Web Service. But we are also having some issues with simple java client which is calling the webservice.

So yeah, we'll do a bit more research today and see if we uncover any more information. If that goes nowhere, we may send you an e-mail and take you up on the offer for the non-eval version of JCAPI.

Thanks again for your assistance. We really appreciate it.

I also have that hs_err log file. Here's an excerpt from one of our client side crashes:

j java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/StringV+0
j java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/io/FileZ+300
j java.lang.ClassLoader.loadLibrary(Ljava/lang/Class;Ljava/lang/String;Z)V+48
j java.lang.Runtime.load0(Ljava/lang/Class;Ljava/lang/StringV+57
j java.lang.System.load(Ljava/lang/StringV+7
j com.pheox.jcapi.g.g()V+170
j com.pheox.jcapi.JCAPIProvider.init()V+16
j com.pheox.jcapi.JCAPIProvider.<clinit>()V+0
v ~StubRoutines::call_stub
V [jvm.dll+0x845a9]
V [jvm.dll+0xd9317]
V [jvm.dll+0x8447a]
V [jvm.dll+0x76f5d]
V [jvm.dll+0x75e58]
V [jvm.dll+0x7ef8b]
j testjcapi.envirohandler.ClientEnvironmentHandler$AutoPrivKeyFinder.findAutoPrivKey(Lcom/sun/xml/wss/impl/callback/SignatureKeyCallback$AliasPrivKeyCertRequestV+4
j testjcapi.envirohandler.ClientEnvironmentHandler.handle([Ljavax/security/auth/callback/CallbackV+176
j com.sun.xml.wss.impl.misc.DefaultSecurityEnvironmentImpl.getAliasPrivKeyCertRequest(Ljava/lang/StringLcom/sun/xml/wss/impl/callback/SignatureKeyCallback$AliasPrivKeyCertRequest;+34
j com.sun.xml.wss.impl.filter.SignatureFilter.process(Lcom/sun/xml/wss/impl/FilterProcessingContextV+349
j com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(Lcom/sun/xml/wss/impl/FilterProcessingContextV+16
j com.sun.xml.wss.impl.HarnessUtil.processDeep(Lcom/sun/xml/wss/impl/FilterProcessingContextV+11
j com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(Lcom/sun/xml/wss/impl/FilterProcessingContextV+70
j com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(Lcom/sun/xml/wss/ProcessingContextV+257
j com.sun.xml.xwss.XWSSClientPipe.secureRequest(Lcom/sun/xml/ws/api/message/PacketLcom/sun/xml/ws/api/message/Packet;+233
j com.sun.xml.xwss.XWSSClientPipe.process(Lcom/sun/xml/ws/api/message/PacketLcom/sun/xml/ws/api/message/Packet;+32
j com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(Lcom/sun/xml/ws/api/message/PacketLcom/sun/xml/ws/api/pipe/NextAction;+6
j com.sun.xml.ws.api.pipe.Fiber.__doRun(Lcom/sun/xml/ws/api/pipe/TubeLcom/sun/xml/ws/api/pipe/Tube;+206
j com.sun.xml.ws.api.pipe.Fiber._doRun(Lcom/sun/xml/ws/api/pipe/TubeLcom/sun/xml/ws/api/pipe/Tube;+31
j com.sun.xml.ws.api.pipe.Fiber.doRun(Lcom/sun/xml/ws/api/pipe/TubeLcom/sun/xml/ws/api/pipe/Tube;+84
j com.sun.xml.ws.api.pipe.Fiber.runSync(Lcom/sun/xml/ws/api/pipe/Tube;Lcom/sun/xml/ws/api/message/PacketLcom/sun/xml/ws/api/message/Packet;+48
j com.sun.xml.ws.client.Stub.process(Lcom/sun/xml/ws/api/message/Packet;Lcom/sun/xml/ws/client/RequestContext;Lcom/sun/xml/ws/client/ResponseContextReceiverLcom/sun/xml/ws/api/message/Packet;+140
j com.sun.xml.ws.client.sei.SEIStub.doProcess(Lcom/sun/xml/ws/api/message/Packet;Lcom/sun/xml/ws/client/RequestContext;Lcom/sun/xml/ws/client/ResponseContextReceiverLcom/sun/xml/ws/api/message/Packet;+4
j com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(Ljava/lang/Object;[Ljava/lang/Object;Lcom/sun/xml/ws/client/RequestContext;Lcom/sun/xml/ws/client/ResponseContextReceiverLjava/lang/Object;+64
j com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(Ljava/lang/Object;[Ljava/lang/ObjectLjava/lang/Object;+14
j com.sun.xml.ws.client.sei.SEIStub.invoke(Ljava/lang/Object;Ljava/lang/reflect/Method;[Ljava/lang/ObjectLjava/lang/Object;+24
j $Proxy28.helloWorld()Ljava/lang/String;+9
j testjcapi.client.TutorialClient.main([Ljava/lang/StringV+126

Hi,

We've been trying to set up JCAPI to use with JAX-WS.

However, when we try add the provider on the server side it crashes the virtual machine.

package testjcapi.service;

import javax.jws.WebService;

import com.pheox.jcapi.JCAPIProvider;

import testjcapi.TestJCAPIServiceSoap;



@WebService( endpointInterface="testjcapi.TestJCAPIServiceSoap")

public class TutorialService implements TestJCAPIServiceSoap {



  public TutorialService() {

    java.security.Security.insertProviderAt(new JCAPIProvider(), 2);

  }

	

  public String helloWorld() {

    return "Hello World";

  }

}

And we get this error back from Tomcat.

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_FLT_STACK_CHECK (0xc0000092) at pc=0x00a77a19, pid=3784, tid=3144
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# j java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/StringV+0
#
# An error report file with more information is saved as hs_err_pid3784.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

We do have some issues on the client side too, but the server side error is simpler to explain.

Any ideas?