6502888

In Application Server 7.1, when you deploy an application to server instance that is running as non-root user, the files of <server-instance>/generated is owned by root user.

Solution

You need to change the permissions manually. 

6078271

Deployment of an EAR fails on Windows due to file length issue.

Windows running on non-NTFS file systems will face file name and path limitation of that file system. 

Solution

Run Windows on an NTFS file system. 

6223279

ejb-ref-name to the jndi-name mapping incorrect if the jndi-name is missing.

When deploying ejb applications, the XML Deployment Descriptor (sun-ejb-jar.xml) should have a jndi-name entry for each EJB reference. For example:

<ejb-ref>

<ejb-ref-name>ejb/package_name.ejb_name</ejb-ref-name>

<jndi-name>ejb/package_name.ejb_name</jndi-name>

</ejb-ref>

If the jndi-name entry is missing, it will deploy without error, but the application will not work correctly as JNDI lookup will fail to find an EJB.

Solution

Ensure that JNDI names are present in the deployment descriptors. To ensure that your application does not have this problem, select the Run Verifier check box before deploying as this will highlight problems with missing JNDI names.

4725147

Cannot choose a particular virtual server for deployment.

In this case, two virtual servers are configured with exactly the same host and listener. If an application is deployed only for second virtual server, it cannot be reached because combination host:port leads to the first virtual server. 

Solution

The virtual server hostname should not be the same as the original hostname, especially when the same HTTP listener is used. 

4994366

Deploy error with ejb-local-ref and ejb-link.

Solution

ejb-local-ref requires ejb-link. Therefore, when dealing with ejb-local-ref, you must specify an ejb-link value.