Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Compiler failed executable.exec

4 views
Skip to first unread message

Joey

unread,
Jan 5, 2004, 8:54:40 PM1/5/04
to

I'm using Weblogic 8 and Sybase. I have an entity bean and a session bean which
map to a table view in my database. When i tried to deploy the EJB, the following
errors appeared:


Compiler failed executable.exec

at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)

Does anybody know the cause of the error?? How to solve this problem?

Thanks in advance.

Regards,
Joey

thorick

unread,
Jan 6, 2004, 12:45:58 AM1/6/04
to

That's odd. Not a lot to go on. Could you try compiling the EJB jar standalone
using 'appc', and seeing what error messages may pop up ?

-thorick


Rob Woollen

unread,
Jan 6, 2004, 2:21:57 PM1/6/04
to
Typically this happens when you don't have javac in your $PATH.
Otherwise, can you show us the full error message?

-- Rob

Jyothi K

unread,
Jan 12, 2004, 10:58:07 AM1/12/04
to

I looked at the previous messages regarding the same problem. Even after making
sure that $JAVA_HOME/bin is in the $PATH, I am still seeing this problem. I am
using weblogic 8.1 SP1. Any ideas?

thanks,
Jyothi


[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for com.sybase.ep.security.manage
ment.jar
Module: com.sybase.ep.security.management.jar Error: Exception preparing
module: EJBModule
(com.sybase.ep.security.management.jar,status=NEW)


Unable to deploy EJB: com.sybase.ep.security.management.jar from com.sybase.ep.security.management.j
ar:


Compiler failed executable.exec

at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1277)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(Sla
veDeployer.java:2634)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer
.java:2584)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:25
06)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

java.io.IOException: Compiler failed executable.exec
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:470)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:329)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:337)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1277)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(Sla
veDeployer.java:2634)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer
.java:2584)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:25
06)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)


]
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:25
23)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Slava Imeshev

unread,
Jan 13, 2004, 1:59:07 AM1/13/04
to
Hi Jyothi,

Though what I'm going to say doesn't answer your question directly,
it may help you to solve this problem in short term.

In your case weblogic calls ejbc because it has detected that
appc/ejbc was not called for the ejb-jar(s) you deploy.

To avoid this, you need explicitly call appc on your ejb-jars before
deployment.

As for availability of javac to the server - you can validate it
by deploying a small servlet that has load-on-startup set to 1
in its web.xml. In servlet's init method you make a call
to Runtime.exec("javac"); If javac is available to the server, the
method will exit normally. Keep in mind that is not correct use
for the exec method and your task is to identify that javac is
available. If it's not, exec will throw an IOException.

Hope this helps.

Regards,

Slava Imeshev

"Jyothi K" <jyo...@email.com> wrote in message news:4002c40f$1...@newsgroups.bea.com...

Jin Mun

unread,
Sep 16, 2004, 7:47:21 PM9/16/04
to
Jyoti...

Try to specify Java compiler path that will be used to compile the EJB module (like "C:\bea\jrockit81sp3_142_04\bin\javac.exe" as aJava Compiler) under Compiler Options in the Configuration.

I had a similar issue and could able to resolve it by doing that...

Go FirmSoft...

0 new messages