Sun Java System Application Server 7 Update 11 Release Notes

EJB Container

This section describes the known Enterprise JavaBeans™ (EJB™) container issues and associated solutions.

ID  

Summary  

4735835

Cannot properly handle null PKs returned from ejbFind methods.

The following container-managed persistence (CMP) examples might return one or more nulls from an ejbFind (assumed called from EmployeeEJB bean, as they must return the same instance type as the bean):

  1. find insurance.employee where insurance.id == 10

    This returns null if such insurance does not have an employee associated with it.

  2. find all insurance.employee where insurance.id > 10

    This returns a collection that might contain nulls for those insurances that do not have an employee.

    For the first occurrence of a null PC in the result set, the CMP client will get JDOFatalInternalException "param0 cannot be null".

    The BMP client will get EJBException "Null primary key returned from ejbFind method" for a single object finder, and (possibly) a NullPointerException for a multi object finder.

Solution

None. 

4744434

The Sun Java System Application Server occasionally throws Null Pointer Exception when using stateful session beans.

The EJB container in the Sun Java System Application Server caches stateful session beans to improve performance. When the cache overflows (that is, the number of beans in the cache exceeds max-cache-size) the container passivates beans to the disk. Occasionally the server throws NullPointerException. The problem occurs when the difference between max-cache-size and cache-resize-quantity is less than 8.

Solution

Ensure that the difference between max-cache-size and cache-resize-quantity is greater than eight, or use an unbounded cache by setting max-cache-size to zero.

4951476, 4967645

The exception javax.ejb.EJBException: org/dom4j/Element is thrown when using Java WSDP 1.2 or 1.3

NOTE: If your application does not use the Java Web Services Developer Pack (Java WSDP) 1.2 or 1.3, this problem does not apply to you.

When Java WSDP 1.2 or 1.3 is installed and configured to be used together with Sun Java System Application Server 7, a javax.ejb.EJBException: org/dom4j/Element could be thrown by the EJB Container.

Solution

Add the latest dom4j-full.jar to server-classpath in the server.xml file. It is available for download at http://dom4j.org and should precede the appserv-jstl.jar entry in server-classpath.

4994366

Error when deploying if ejb-local-ref is used without ejb-link.

Solution

ejb-local-ref requires ejb-link. When using ejb-local-ref, you must specify an ejb-link value.