When you invoke a Stateless Session Bean using the home interface, you acquire the references by invoking the create method of the home interface. However, when the invocation of the Session Bean is complete, you must release the references by invoking the remove method. If you do not release the references, the memory on the J2EE server will remain occupied.

Furthermore, by specifying the option that makes the invocation of the remove method unnecessary, the invocation of the remove method for the EJB objects of the Stateless Session Bean will become unnecessary. If you enable this option, you can invoke the business method after invoking the remove method.

If this option is disabled, you must invoke the remove method. Furthermore, when you invoke the business method after invoking the remove method, the java.rmi.NoSuchObjectException exception will be returned to the invocation source.

In the ejbserver.rmi.stateless.unique_id.enabled key of usrconf.properties, you specify the option that makes the invocation of the remove method unnecessary and define the option for the J2EE servers. For details on the key, see 2.4 usrconf.properties (User property file for J2EE servers) in the uCosminexus Application Server Definition Reference Guide.

According to the EJB specifications, accessing the resource manager with the ejbCreate method or with a method in which the @PostConstruct annotation is specified is not allowed.

Do not use the same Session Bean as a Stateful Session Bean and Stateless Session Bean in the same J2EE application.

The begin method of javax.transaction.UserTransaction might be invoked either with the ejbRemove method of the Stateless Session Bean or with a method in which the @PreDestroy annotation is specified. However, according to the EJB specifications, you cannot use this method after invocation. Do not invoke the begin method of javax.transaction.UserTransaction.