The problem described in 17904 is if your EAR contains a large component JAR
file (such as a large WAR or a large EJB JAR). If your app does not
contain a large compnent JAR then you might have a different problem.
If you *do* have a large component JAR in the EAR, then using autodeploy
will not work around the problem.
One workaround you can use for 3.1.1 is to deploy your app using directory
deployment, written up here:
http://download.oracle.com/docs/cd/E18930_01/html/821-2417/gilfm.html#gilcn
Basically, you expand your EAR into a directory. Any submodules such as
myWebApp.war or myEJBs.jar need to be expanded into subdirectories named
myWebApp_war and myEJBs_jar (for example). Then you can use the asadmin
deploy command or the admin console to deploy the top-level EAR directory
instead of the EAR file itself.
Please try that and if it does not help we will need to look further.
- Tim
--
[Message sent by forum member 'tjquinn']
View Post: http://forums.java.net/node/863767