EJB archive passes ejbc compilation but fails deploy on WLS7

Question

I'm attempting to migrate several functional
EJBs from WLS6.1 to WLS7.0. I've made the
deployment descriptor changes and created an
archive containing the EJBs. The ejbc compilation
tool successfully processes the archive so long
as I don't specify the -iiop option.
However, the WLS7.0 server fails to deploy
the archive. No messages or exceptions are
provided. I've tried deployment both as an ear and jar file. Any clues or suggestions?

Answer 1

Rob Woollen <[email protected]> wrote:
ken wallis wrote:
Rob Woollen <[email protected]> wrote:
ken wallis wrote:
I'm attempting to migrate several functional
EJBs from WLS6.1 to WLS7.0. I've made the
deployment descriptor changes and created an
archive containing the EJBs. You actually don't need to change any descriptors to migrate from 6.x
(or even 5.1) to 7.0. Just deploy the ejbs in the new server.
Of course, many people will upgrade their descriptors to take advantage
of new 7.0 options, but I'd first ensure your beans work without
changing anything.I tried deploying the same archive on WLS 7.0 that I've already deployedto WLS
6.1. It faired exactly the same as the previous version.
The ejbc compilation
tool successfully processes the archive so long
as I don't specify the -iiop option.
However, the WLS7.0 server fails to deploy
the archive. No messages or exceptions are
provided. I've tried deployment both as an ear and jar file. Anyclues or suggestions?
Hmmm. That's odd. How are you deploying it, and how do you know it
didn't deploy?
I've copied the archive into the mydomain directory then used the Adminpages
to select it for deployment. It works its way to a page stating thatits 'Activating'
the archive and reports the start time. However, this process neverdisplays
the end time or returns. Instead, the WLS server merely exits andthe Admin console
suddenly displays the imfamous 'page not found' page.WLS should never just exit. It sounds like the JVM crashed. Are you
using the JVM bundled with WLS? What platform are you on? Is there
a
core file or any *.log files left over from the jvm?Win 2000 w/ JDK 1.3.1_03 but I've not altered the WLS basic configuration so it
should still be using its own.
I attempted to redirect out and err to log files, but nothing gets captured and
WLS leaves nothing that I've found. I even placed a 'pause' at the bottom of
the start command file; the WLS window exitted without waiting for it.
>
You might also try just copying the jar/ear to the server's applications
directory. I'd be interested to see if this works.
I tried. The Admin server never starts.
>
>
>>
I've located the following error message in the mydomain\logs\wl-domain.log,although
it provides no real information.
<Sep 13, 2002 5:56:59 PM CDT> <Error> <Deployer> <CI069311> <myserver><ExecuteThread:
'10' for queue: 'default'> <kernel identity> <> <149233> <Unexpectederror was
encountered during the deployment process.>
Incidentally, before I can attempt to restart the WLS, I have to manuallyremove
the archive from the config.xml.