Binding stateful EJB bean

Question

Hi,
I have a problem binding EJB bean (Stateful bean). Bean have two business methods:
SendPacketToTRSM and GetData
When I invoke SendPacketToTRSM method from process, application server create first instance of bean and invoke method SendPacketToTRSM
Next I invoke GetData method in process, application server create second instance of bean and invoke method GetData.
Every time, when I invoke method, application server create new instance of bean and don't remove it.
Application server after passivation remove instance of bean from container.
Environment: BPEL 10.0.2(OC4J), patch 4369818, 4406640, 4496111
EJB bean on JBoss 4.0.2
The following wsdl EJB binding:
<?xml version="1.0" ?>
<definitions targetNamespace="http://xmlns.unizeto.pl/TRSMBPEL"
xmlns:tns="http://xmlns.unizeto.pl/TRSMBPEL"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/"
xmlns:ejb="http://schemas.xmlsoap.org/wsdl/ejb/"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<!-- message declns -->
<message name="SendPacketToTRSMRequestMessage">
<part name="sender" type="xsd:int"/>
<part name="bufferToTRSM" type="xsd:string"/>
</message>
<message name="SendPacketToTRSMResponseMessage">
<part name="result" type="xsd:int"/>
</message>
<message name="GetDataRequestMessage">
</message>
<message name="GetDataResponseMessage">
<part name="result" type="xsd:string"/>
</message>
<message name="RemoveRequestMessage">
</message>
<message name="RemoveResponseMessage">
</message>
<message name="CreateRequestMessage">
</message>
<message name="CreateResponseMessage">
</message>
<!-- port type declns -->
<portType name="TRSMService">
<operation name="SendPacketToTRSM">
<input name="SendPacketToTRSMRequest" message="tns:SendPacketToTRSMRequestMessage"/>
<output name="SendPacketToTRSMResponse" message="tns:SendPacketToTRSMResponseMessage"/>
</operation>
<operation name="GetData">
<input name="GetDataRequest" message="tns:GetDataRequestMessage"/>
<output name="GetDataResponse" message="tns:GetDataResponseMessage"/>
</operation>
<operation name="Remove">
<input name="RemoveRequest" message="tns:RemoveRequestMessage"/>
<output name="RemoveResponse" message="tns:RemoveResponseMessage"/>
</operation>
<operation name="Create">
<input name="CreateRequest" message="tns:CreateRequestMessage"/>
<output name="CreateResponse" message="tns:CreateResponseMessage"/>
</operation>
<operation name="SSCDAuthorizedForget">
</portType>
<!-- binding declns -->
<binding name="EJBBinding" type="tns:TRSMService">
<ejb:binding/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap typeName="xsd:int" formatType="int"/>
<format:typeMap typeName="xsd:string" formatType="java.lang.String"/>
</format:typeMapping>
<operation name="SendPacketToTRSM">
<ejb:operation
methodName="SendBase64PacketToTRSM"
parameterOrder="sender bufferToTRSM"
interface="remote"
returnPart="result"/>
<input name="SendPacketToTRSMRequest"/>
<output name="SendPacketToTRSMResponse"/>
</operation>
<operation name="GetData">
<ejb:operation
methodName="GetBase64Data"
parameterOrder=""
interface="remote"
returnPart="result"/>
<input name="GetDataRequest"/>
<output name="GetDataResponse"/>
</operation>
<operation name="Remove">
<ejb:operation
methodName="remove"
interface="remote"/>
</operation>
<operation name="Create">
<ejb:operation
methodName="create"
interface="home"/>
</operation>
</binding>
<!-- service decln -->
<service name="TRSMService">
<port name="EJBPort" binding="tns:EJBBinding">
<ejb:address className="pl.unizeto.pki.des.ssp.trsmd.TRSMDRemoteHome"
jndiName="pl.unizeto.pki.des.ssp.trsmd.TRSMDBean"
initialContextFactory="org.jnp.interfaces.NamingContextFactory"
     jndiProviderURL="192.168.129.202:1999"/>
</port>
</service>
<!-- partner links -->
<plnk:partnerLinkType name="TRSMService">
<plnk:role name="TRSMServiceProvider">
<plnk:portType name="tns:TRSMService"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
and bpel source
<process name="TRSMBPEL" targetNamespace="http://xmlns.unizeto.pl/TRSMBPEL" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:tns="http://xmlns.unizeto.pl/TRSMBPEL" xmlns:ns1="http://www.w3.org/2001/XMLSchema" xmlns:trsm="http://xmlns.unizeto.pl/TRSMBPEL" xmlns:ctask="http://services.oracle.com/bpel/task" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:taskMgr="http://services.oracle.com/bpel/task" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"><!-- ================================================================= --><!-- PARTNERLINKS --><!-- List of services participating in this BPEL process --><!-- ================================================================= -->
<partnerLinks><!--
The 'client' role represents the requester of this service. It is
used for callback. The location and correlation information associated
with the client role are automatically set using WS-Addressing.
-->
<partnerLink name="client" partnerLinkType="tns:TRSMBPEL" myRole="TRSMBPELProvider"/>
<partnerLink name="TRSMService" partnerRole="TRSMServiceProvider" partnerLinkType="tns:TRSMService"/>
<partnerLink myRole="TaskManagerRequester" name="userTask" partnerRole="TaskManager" partnerLinkType="taskMgr:TaskManager"/>
</partnerLinks><!-- ================================================================= --><!-- VARIABLES --><!-- List of messages and XML documents used within this BPEL process --><!-- ================================================================= -->
<variables><!-- Reference to the message passed as input during initiation -->
<variable name="inputVariable" messageType="tns:TRSMBPELRequestMessage"/>
<variable name="outputVariable" messageType="tns:TRSMBPELResponseMessage"/>
<variable name="SendPacketToTRSM_SendPacketToTRSM_InputVariable" messageType="tns:SendPacketToTRSMRequestMessage"/>
<variable name="SendPacketToTRSM_SendPacketToTRSM_OutputVariable" messageType="tns:SendPacketToTRSMResponseMessage"/>
<variable name="GetData_GetData_InputVariable" messageType="tns:GetDataRequestMessage"/>
<variable name="GetData_GetData_OutputVariable" messageType="tns:GetDataResponseMessage"/>
<variable name="UserTask2.0Var1" element="ctask:task"/>
<variable name="Invoke_1_Create_InputVariable" messageType="tns:CreateRequestMessage"/>
<variable name="Invoke_1_Create_OutputVariable" messageType="tns:CreateResponseMessage"/>
<variable name="removeTRSMD_Remove_InputVariable" messageType="tns:RemoveRequestMessage"/>
<variable name="removeTRSMD_Remove_OutputVariable" messageType="tns:RemoveResponseMessage"/>
</variables><!-- ================================================================= --><!-- ORCHESTRATION LOGIC --><!-- Set of activities coordinating the flow of messages across the --><!-- services integrated within this business process --><!-- ================================================================= -->
<sequence name="main"><!-- Receive input from requestor.
Note: This maps to operation defined in TRSMBPEL.wsdl
-->
<receive name="receiveInput" partnerLink="client" portType="tns:TRSMBPEL" operation="process" variable="inputVariable" createInstance="yes"/>
<scope name="Scope_1">
<variables>
<variable name="Invoke_3_Create_InputVariable" messageType="tns:CreateRequestMessage"/>
<variable name="Invoke_3_Create_OutputVariable" messageType="tns:CreateResponseMessage"/>
<variable name="Invoke_1_Remove_InputVariable" messageType="tns:RemoveRequestMessage"/>
</variables>
<sequence name="Sequence_1">
<assign name="Init">
<copy>
<from variable="inputVariable" part="payload" query="/tns:TRSMBPELProcessRequest/tns:sender"/>
<to variable="SendPacketToTRSM_SendPacketToTRSM_InputVariable" part="sender"/>
</copy>
<copy>
<from variable="inputVariable" part="payload" query="/tns:TRSMBPELProcessRequest/tns:buffer"/>
<to variable="SendPacketToTRSM_SendPacketToTRSM_InputVariable" part="bufferToTRSM"/>
</copy>
</assign>
<invoke name="create" partnerLink="TRSMService" portType="tns:TRSMService" operation="Create" inputVariable="Invoke_3_Create_InputVariable" outputVariable="Invoke_3_Create_OutputVariable"/>
<invoke name="SendPacketToTRSM" partnerLink="TRSMService" portType="tns:TRSMService" operation="SendPacketToTRSM" inputVariable="SendPacketToTRSM_SendPacketToTRSM_InputVariable" outputVariable="SendPacketToTRSM_SendPacketToTRSM_OutputVariable"/>
<invoke name="GetData" partnerLink="TRSMService" portType="tns:TRSMService" operation="GetData" inputVariable="GetData_GetData_InputVariable" outputVariable="GetData_GetData_OutputVariable"/>
<invoke name="Remove" partnerLink="TRSMService" portType="tns:TRSMService" operation="Remove" inputVariable="Invoke_1_Remove_InputVariable"/>
</sequence>
</scope><!-- Generate reply to synchronous request -->
<assign name="Result">
<copy>
<from variable="GetData_GetData_OutputVariable" part="result"/>
<to variable="outputVariable" part="payload" query="/tns:TRSMBPELProcessResponse/tns:data"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="client" portType="tns:TRSMBPEL" operation="process" variable="outputVariable"/>
</sequence>
</process>
Could anyone explain, is it possible to binding stateful bean to process?
Thanks
Norbert

Answer 1

Did some additional investigations and concluded"
The (embedded) OTC uses default the empty to obtain the reference to a Session Bean (EJB). In my case I was using the Remote Interface and my Context was empty { }:
Hashtable ht = ic.getEnvironment();
System.out.println(ht.toString());
When I supply the missing information, obtained via the Test Client that functions correctly, a new Bean instance was created for each Client. My getInitialContext() method looks like the example below.
public InitialContext getInitialContext() throws NamingException {
Properties p =new Properties();
p.setProperty( "java.naming.factory.initial", "com.evermind.server.rmi.RMIInitialContextFactory");
p.setProperty( "java.naming.provider.url", "ormi://localhost:23892/current-workspace-app" );
I tried the ApplicationInitialContextFactory and again the same Bean instance was shared among all Clients. I did not try ApplicationClientInitialContextFactory, but I expect that the Remote interface will be used!
Is it a Bug that ApplicationInitialContextFactory does not create a new instance for my Stateful Session Bean? I can use the Remote interface, but that would decrease the performance and it is less elegant...
Michael