weblogic.utils.compiler.ToolFailureException

ERROR: The classes which ejbc generated from your home and remote interfaces cannot be loaded. Please ensure that you have set the -d option to a writeable directory.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web101

  • via Oracle Community by 3004, 1 year ago
    ERROR: The classes which ejbc generated from your home and remote interfaces cannot be loaded. Please ensure that you have set the -d option to a writeable directory.
  • via Oracle Community by 707501, 1 year ago
    ERROR: The classes which ejbc generated from your home and remote interfaces cannot be loaded. Ple ase ensure that you have set the -d option to a writeable directory. [java]
  • [J2EE:160111]ERROR: Appc can not write to the working directory, '/usr/home/weblogic/wli_10.3/lib/console/worklistconsoleEar'. Please ensure that you have write permission for this directory and try again.
  • Stack trace

    • weblogic.utils.compiler.ToolFailureException: ERROR: The classes which ejbc generated from your home and remote interfaces cannot be loaded. Please ensure that you have set the -d option to a writeable directory. at weblogic.ejb20.ejbc.EJBCompiler.runRmic(EJBCompiler.java:919) at weblogic.ejb20.ejbc.EJBCompiler.doRmic(EJBCompiler.java:351) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:483) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401) 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:1275) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:473) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2842) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1529) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1183) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1026) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2568) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2520) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2450) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.