Service resource, together with an SSL enabled HTTP Connection resource in "HttpComponent" mode, throws java.lang.IllegalArgumentException exception.
Article ID: KB0085451
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Description:
If a Service resource, together with an SSL enabled HTTP Connection resource in "HttpComponent” is invoked, SOAP Request-reply fails with java.lang.IllegalArgumentException: SSL Engine may not be null.
Symptoms:
Exception::Not yet implemented!
java.lang.IllegalArgumentException: SSL Engine may not be null
at com.tibco.bw.service.binding.bwhttp.httpcomponents.BWSSLIOSession.<init>(Unknown Source)
at com.tibco.bw.service.binding.bwhttp.httpcomponents.BWSSLServerIOEventDispatch.connected(Unknown Source)
at org.apache.http.impl.nio.reactor.BaseIOReactor.keyCreated(BaseIOReactor.java:182)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processNewChannels(AbstractIOReactor.java:246)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:153)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:70)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:324)
at java.lang.Thread.run(Unknown Source)
error: SSL Engine may not be null
Cause:
Entrust is the default security vendor used by TIBCO BusinessWorks which is very strict, hence the service invocation failed with the error.
Resolution
========================================
java.property.TIBCO_SECURITY_VENDOR=j2se
========================================
Restart Designer after adding the property. If this is in a deployed application, you can try adding this into the deployed BW application TRA file.
Issue/Introduction
Feedback
