Unable to deploy pre-compiled archive

Hi All. I am trying to precompile my application ear file. It seems to compile fine. albeit with a few jsp errors, but it doesnt not deploy to OAS. I am using 10.1.3
I get
Redeploy error: Redeploy failed: null
when trying to redeploy through the command line
OR
Archive Location - Failed in uploading archive. Invalid archive file: Unsupported archive type. unknown
when trying to deploy using the web console.
I'll try a few more things and let you know.
Andrew
C:\product\10.1.3\OracleAS_1\j2ee\home\jsp>bin\ojspc.bat -ignoreErrors c:\devl\r
mt_publish_dir\fp442\dist\FP442-WLS.EAR
Detected archive, now processing contents of c:\devl\rmt_publish_dir\fp442\dist\
FP442-WLS.EAR...
Setting up temp area...
Expanding archive in temp area...
Detected archive, now processing contents of C:\Documents and Settings\andrewg.R
MTP\Local Settings\Temp\tmp39285\FP442-WLS.war...
Setting up temp area...
Expanding archive in temp area...
C:\DOCUME~1\ANDREW~1.RMT\LOCALS~1\Temp\tmp39286\_exportSearchResults.java:55: ca
nnot access javax.ejb.EJBObject
file javax\ejb\EJBObject.class not found
request.setAttribute("fileAttachment", PersistenceHelper.getSearchBean(
).retrieveExportResults((SearchToken)((HashMap)session.getAttribute(FPConstants.
SESSION_MAP_KEY)).get(SearchConstants.SEARCH_TOKEN_KEY)) );
^
Note: C:\DOCUME~1\ANDREW~1.RMT\LOCALS~1\Temp\tmp39286\_auditTemplateProperties.j
ava uses or overrides a deprecated API.
Note: Recompile with -deprecation for details.
1 error
com.evermind.compiler.CompilationException: compilation error occurred
Removing temp area...
Creating c:\devl\rmt_publish_dir\fp442\dist\FP442-WLS.EAR ...
Removing temp area...
C:\product\10.1.3\OracleAS_1\j2ee\home\jsp>cd ..
C:\product\10.1.3\OracleAS_1\j2ee\home>java -jar admin_client.jar deployer:oc4j:
opmn://sunsvr1/home oc4jadmin R1skmgmt -redeploy -file c:\devl\rmt_publish_dir\F
P442\dist\FP442-WLS.ear -deploymentName FPe442 -keepSettings
Redeploy error: Redeploy failed: null
C:\product\10.1.3\OracleAS_1\j2ee\home>

Andrew, thanks for sharing your experience.
I am under the impression that it should be ok to compiling on XP and then deploying on Solaris if the same jdk version is used, although it does sound better to do compile and deploy on the same server.

Similar Messages

Auto deploy pre-compiled JSP

Hello
In the post of gadegaard in november 2002, there was a problem to au deploy pre-compiled JSP. Is this problem has been fix in the 9.0.4 OC4J version ?
If yes, is it sufficient to create a "_pages" directory in the war (the war is contained in an ear) and auto deploy it ? Because my pre-compiled JSP are not deployed.
Tanks in advance for your answer
Emmanuelle

Emmanuelle:
There are two ways to use the precomiled JSP files.
Method one: You can just copy the generated JSP page implementation classes to the directory application-deployments/yourApp/yourWebApp/persistence/_pages. If the init-param "main_mode" of jsp servlet of your web app is reload, then these classes will be used without stopping the server. This is the fastest way in development.
Method two: You can packaged the generated JSP page implementation classes into a jar just like any other java class libraries. Then create your war with that jar inside WEB-INF/lib. Make sure the init-param "main_mode" of jsp servlet in your web.xml is justrun. Now you have a deployable war file. You can deploy the war file (within an ear file) to oc4j and access the JSP page.
Please tell me if either of thse methods works for you
Please note since oc4j 10.1.3, ojspc will package the generated classes into a jar under WEB-INF/lib if given an war or ear file.

Deploying pre-compiled jsp

hi everyone,
I want to know to do we deploy pre-compilied jsp on the application servers. And would it the same procedure for all the servers.
thanks

Hi Ian,
Add this jar file to classpath...use either web interface or directly edit jvm12.conf to modify classpath..
Raj

Deploying pre-compiled 10g Forms to a server.

Is it acceptable to compile all forms, reports and libraries against a development environment and simply release/deploy the executable files to a separate application server and database or should the binaries always be compiled against the target database on the targe server. The assumption is that the production server and databases and development databases are identical in structure.
What are the risks, if any?
What is the official line?

If you're 100% sure that your development database's structure is exactly the same as the production then yes, you can compile on the first and deploy on the second as long as the product and OS versions are the same.
But most of the time the DBs are not the same, so it will be a better practice if you check the structure before you deploy the executables or at least if it's possible connect to the prod. db and compile you source.
Tony

Deploy pre-compiled client proxy with a web service

When a web service is deployed on an OAS server, the page at the endpoint URL includes a link to a proxy jar file (<endpoint url>?proxy_jar). I have a proxy jar that I've built and I'd like to be able to include it in my war file so that the proxy jar URL will download it instead of the server-generated one. Is there a way to do that?
I did something similar with the wsdl file: I included it in the war file in the same folder and filename as the web service interface class, but that didn't work for the proxy jar file.
-Peter

Hi Peter,
You cannot replace the proxy jar generated by the Oracle Web Services runtime with your own version. If you want to provide your own version, you will have to handle it as a classic resource in your .ear file, and advertize the location of this resource using some other mechanism.
-Eric

Unable to Deploy a Webservice.

Hello All,
I created a java bean and put the implemented code in some of the methods etc. ( By the way the code is generated using a WSDL using the SAP Netweaver libraries )
Now when I attempt to actually create the webservice out of the implemented Java Bean.
( By right click - > Webservice -> Create webservice.)
It create the EJB Jar and also create EJB EAR file but I am unable to deploy this EAR archive.
It throws following exception trace :
Can any of you please throw some light on this . ?
I am using NWDS Ce 7.1 SP05 .
Can we get this problem if the NWDS and NWDI are not in Same version and same patch ?
IWAB0014E Unexpected exception occurred.
Client "com.sap.ide.jee.ws.jee5.core.provider.commands.AddWsdlToInfo" threw an exception.
      java.lang.IllegalArgumentException: Client "com.sap.ide.jee.ws.jee5.core.provider.commands.AddWsdlToInfo" threw an exception.
      at org.eclipse.wst.command.internal.env.core.data.DataFlowManager.invokeMethod(DataFlowManager.java:275)
      at org.eclipse.wst.command.internal.env.core.data.DataFlowManager.process(DataFlowManager.java:124)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:411)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:358)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:253)
      at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:252)
      at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
      at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
      at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
      at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:222)
      at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:96)
      at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:147)
      at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
      at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813)
      at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
      at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
      at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
      at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
      at org.eclipse.jface.window.Window.open(Window.java:796)
      at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
      at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
      at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
      at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
      at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
      at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
      at org.eclipse.equinox.launcher.Main.main(Main.java:1144)

Hi Ravi,
can you please indicate the NWDS and NWDI versions and JDK being used?
Regards,
Désiré

Pre-Compiling JSPs while deploying a .war file in OC4J instance

Hi,
Is there any way to inform the OC4J instance to pre-compile the jsps in a .war file, while deploying..
Thanks for your responses,
Eshwar

Click on the project.
Open the context menu (right mouse button).
Expand the General item in the left list.
Select the Deployment Profiles item.
Select the deployment profile you need from the right.
Follow the wizard.
--olaf

Pre-compiled JSPs when deploying an EAR under WebLogic 6.1 SP4

Hello,
We have sucessfully pre-compiled JSP pages when working with and
deploying WAR files (WebLogic 6.1 SP4, Windows).
However, we can't seem to make it work when deploying EAR files.
Examing the "secret" unpacked directories after deployment doesn't
seem to help.
If we extract the WAR from the EAR and deploy it, everything is perfect.
Any ideas? Anyone able to make this work? If so, could you share the
output of
jar -tf yourCoolEarFileThatWorks.ear
as well as the same for the embedded WAR file?
Thank you,
Mike Leo

Some followup information.
We've changed the place where it looks for JSP classes using the
"workingDir" parameter in weblogic.xml.
And we also set "pageCheckSeconds" (also in weblogic.xml) to "-1".
Now, everything in the base directory comes up without being recompiled.
However, nothing in subfolders of the base directory is "picked up". Those
pages are still being compiled when they are accessed.
Any ideas welcome.
Mike Leo
On Tue, 05 Aug 2003 18:43:41 -0500, Michael Leo <[email protected]>
wrote:
Hello,
We have sucessfully pre-compiled JSP pages when working with and
deploying WAR files (WebLogic 6.1 SP4, Windows).
However, we can't seem to make it work when deploying EAR files.
Examing the "secret" unpacked directories after deployment doesn't
seem to help.
If we extract the WAR from the EAR and deploy it, everything is perfect.
Any ideas? Anyone able to make this work? If so, could you share the
output of
jar -tf yourCoolEarFileThatWorks.ear
as well as the same for the embedded WAR file?
Thank you,
Mike Leo

How to pre-compile jsp and deploy to tomcat

Hi All,
I wuld like to know how to pre-compile JSPs and deploy to tomcat. I am using ANT tool to build and deploy the war file.
Thanks in Advance.
Regards,
--Nagesh.

for Tomcat 5.0 (You'll need to edit to fit your needs)
    <path id="jsp.classpath">
        
        <fileset dir="C:\tomcat\common\lib">
            <include name="**/*.jar"/>
        </fileset>
        <fileset dir="C:/tomcat/common/endorsed">
            <include name="**/*.jar"/>
        </fileset>
    </path>
    <target name="jsp" >
    
    <taskdef name="jspc50" classname="org.apache.jasper.JspC">
        <classpath>
                <path refid="jsp.classpath"/>
        </classpath>
    </taskdef>
    <jspc50 outputDir="${build.classes}"
            package="jsp"
            uriroot="${project.dir}/web/webApp"
            webXmlFragment="c:/web.xml"
            verbose="9"
            validateXml="false">
    </jspc50>
    <javac srcdir="${build.classes}/jsp"
           destdir="${build.classes}"
           debug="true"
           optimize="false"
           includes="**/*.java"
           source="1.4">
            <classpath>
                <path refid="classpath"/>
                <path refid="jsp.classpath"/>
            </classpath>
    </javac>
</target>    More information can be found here :
http://www.onjava.com/pub/a/onjava/excerpt/AntTDG_chap8/index1.html?page=last

Pre-compile JSPs before deploying

Hi All,
what is the best way to pre-compile my JSPs and then bundle them together into
a .war file, then deploying it ???
I have like 100 jsps that i wanted to precompile and wanted to package them together
into a abc.war file, which i can further deploy to my WLS6.1 server ?
I have another instance of WLS8.1 that i wanted to do the same thing ?
can somebody please advise me something and how to do this ?
This is on Production environment.
-steve

Steve, you're correct, the output jsp .classes are insterted into the war
file if compilation is successful.
"steve" <[email protected]> wrote in message
news:404f7e99$[email protected]..
>
Hi Raja,
Thanks for your reply. does this ant task wlappc compiles the .war fileand then
repackage into the same .war file ?
am i correct ?
please advise .....thx, steve
"Raja" <[email protected]> wrote:
Both option are will work. I am using wlappc ant task to compile my war
file prior
to deployment.
<target name="appc">
<wlappc
source="C:\abc\abc.war"
/>
</target>
Coming to deployment you can either write ant task to deploy using
console.
Example
of ant task for deploying from a windows dev machine into remoteproduction
box.
Admin server need to be running for deploy to be successful.
<target name="sun-deploy">
<wldeploy action="deploy"
source="C:\projects\abc\abc.war"
name="myapp"
user="weblogic"
password="weblogic"
verbose="true"
adminurl="http://xyz:7001"
debug="true"
targets="myserver"
upload="true"
/>
</target>
"steve" <[email protected]> wrote:
Hi All,
what is the best way to pre-compile my JSPs and then bundle them
together
into
a .war file, then deploying it ???
I have like 100 jsps that i wanted to precompile and wanted to package
them together
into a abc.war file, which i can further deploy to my WLS6.1 server?
I have another instance of WLS8.1 that i wanted to do the same thing
can somebody please advise me something and how to do this ?
This is on Production environment.
-steve

Pre-compiled JSPs getting re-compiled by the server

For our project we are using wlappc to pre-compile JSPs and generate EJB classes. We are using the split directory format, so this is what the task looks like -
<target name="appCompile" depends="init" >
<delete dir="${ear.dist}" />
<mkdir dir="${ear.dist}" />
<wlpackage srcdir="${ear.src}" destdir="${ear.build}"
toDir="${ear.dist}" />
     <wlappc source="${ear.dist}" verbose="true" classpath="${classpath}" />
</target>
After this, we are using wldeploy to deploy the application to another server.
This is how the task looks like -
     <target name="beadeploy" depends="init" >
     <wldeploy action="deploy"
          source="${src.dir}/dist/myapp.ear"
          name="myApplication" remote="true"
          user="${deploy.username}" password="${deploy.password}"
          verbose="true" adminurl="t3://${deploy.host}:${deploy.port}"
          upload="true"
          debug="true" targets="${deploy.target}"/>
     </target>
The problem that I am facing is that, even after re-compiling the JSPs, they get compiled again by the server when accessed for the first time !
We using Weblogic 8.1.2.0. Can you please provide a soplution for this ?

Hi,
The following steps help you troubleshoot why you may be having problems with JSPs recompiling:
1. When invoking jspc, your classpath must contain the same release, service-pack, and any temporary patches as the servers you wish to deploy on. Otherwise, the Server will read the JSPs as being compiled on a different version of the WebLogic, and will recompile them all.
2. You should invoke jspc from the root directory of your open-directory exploded) WebApp or specify -webapp) and use the -d option to deploy the generated classes to the WEB-INF/classes directory. You can then archive these JSP classes into a JAR if you wish from the WEB-INF/classes directory.
3. The JSPs should then be deployed either individually to the WEB-INF/classes/jsp_servlet directory or in a JAR file under the WEB-INF/lib directory.
4. One other thing that could cause JSPs to be recompiled is if the timestamp of the class is different from that of the source.
Also, if your ant classpath is different from whatever WLS-related classpath entries you use to run WLS, this may cause problems, too.
-- Prasanna
Prasanna Yalam

Unable to deploy a jar on WEBLOGIC 8

Hi everybody,
I have a problem to deploy a jar file on my server IOException ....
Informations :
Solaris 8
WEBLOGIC 8 SP1
ORACLE 9.0.2
Best regards,
Alain.
The time this task was completed.
Exception: Exception:weblogic.management.ApplicationException: prepare failed
for ReferenceDataEJB.jar Module: ReferenceDataEJB.jar Error: Exception preparing
module: EJBModule(ReferenceDataEJB.jar,status=NEW) Unable to deploy EJB: ReferenceDataEJB.jar
from ReferenceDataEJB.jar: Compiler failed executable.exec at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468) 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) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
java.io.IOException: Compiler failed executable.exec at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:505)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:364) at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:372) at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468) 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) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

Hello,
Thanks a lot for your answer
This step alone work very well. So i have supected and bad domaine configuration
because I have deployed the same application onto another machine and everything
was good (and the OS is the same).
On the production machine (where there is a problem), i have check BEA_HOME, WL_HOME,
JAVA_HOME and everything is good.
Have you another tip for me ?
Regards,
Alain.
"Deepak Vohra" <[email protected]> wrote:
>
Compile ReferenceDataEJB.jar with ejbc before deploying the jar file.
"Compiler failed executable.exec at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)"
is a ejbc error.
thanks,
Deepak
"GREGOIRE Alain" <[email protected]> wrote:
Hi everybody,
I have a problem to deploy a jar file on my server IOException ....
Informations :
Solaris 8
WEBLOGIC 8 SP1
ORACLE 9.0.2
Best regards,
Alain.
The time this task was completed.
Exception: Exception:weblogic.management.ApplicationException: prepare
failed
for ReferenceDataEJB.jar Module: ReferenceDataEJB.jar Error: Exception
preparing
module: EJBModule(ReferenceDataEJB.jar,status=NEW) Unable to deployEJB:
ReferenceDataEJB.jar
from ReferenceDataEJB.jar: Compiler failed executable.exec at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468)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) atweblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
java.io.IOException: Compiler failed executable.exec at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:505)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:364)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:372)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468)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) atweblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

Unable to deploy EJB application

Hi iam getting the following exception while deploying an EJB application in WebLogic 8.1
Exception:weblogic.management.ApplicationException: prepare failed for Addition
Module: Addition Error: Exception preparing module: EJBModule(Addition,status=NEW)
Unable to deploy EJB: Addition.jar from Addition.jar:
Compiler failed executable.exec
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468)
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)
what might be the reason for this exception ????

This problem is caused by the way WebLogic calls javac to compile the generated classes for the EJBs deployment. This became a big problem for our project with 50 Entity EJBs 2.0 with CMP/CMR, about 15 EJB-QL statements, 3 MDB and 8 Session EJB. I think that these numbers are limits, so exceeding any of these numbers cause javac to exhaust the memory it allocates by default. Even the WebLogic 8.1.Server's administarion console allows you to supply additional parameters for RMI and EJB compilers, it does not allow to supply the -J-Xmx256M (or more) option needed to increase the memory javac allocates.
Thus:
1. In the active $JAVA_HOME/bin of the Server create the file:
Windows:
javac1.cmd Containing:
javac -J-Xmx256M %*
Linux:
javac1.sh Containing:
#!/bin/bash
javac -J-Xmx256M $*
make it "executable"
NOTE: startWeblogic script sets it own JAVA_HOME, so check it first.
2. In the administraitve console of WebLogic 8.1 Server select the server in the left frame under the
<Domain> / Servers branch. In the right frame select the General tab.
3. In the Java Compiler box change javac to javac1.cmd or javac1.sh respectively. No restart is needed.
This solved our problem.
I could not find any solution published, hopefully this will help other colleagues.
Rusi Popov

The file '/foo.aspx' has not been pre-compiled, and cannot be requested

Hi All
I am using odp .net to access oracle data. I have also added oracle.dataaccess in my asp .net references. Everything works fine in my development and when I run the code through debugger. However, when I deploy the project in IIS, it gave me following error...
"The file '/foo.aspx' has not been pre-compiled, and cannot be requested
This is pretty generic error and I found out this is related to .Net assemblies.
By further investigation, I found that oracle.dataacess.dll is not present in the bin directory of a deployed web site. I am not sure why .net is dropping that dll in the deployment wizard.
Did anyone encounter this problem before?
I got a workaround for now that manually copting dll into the bin directory of deplyed web site. However, I am looking for more robust and technical answer..
The strange thing is I have been deploying the web site the same way for last 8 months and never encountered this problem.
thanks a lot..
Message was edited by:
amazon

If you add a reference to Oracle.DataAccess at design time it will be added as an assembly definition to web.config. Then you don't need a copy in your bin dir and it will be found in the GAC.
Eric

What is the Advantage and Disadvantage of Pre-Compiled JSP

Hi All,
What is the advantage and disadvantage of using pre-compiled JSP

Pro:
By pre-compiling your JSPs you don't need a java compiler on the server - just a jre.
The result? No java compiler on the server means a potential security hole patched - people can't just write and deploy jsp's willy nilly on the server.
You KNOW that all your JSPs compile before you visit them - because you have compiled them all :-). It won't fail because of a stupid spelling miskate that prevents compilation. That doesn't mean they will run without error of course...
Con:
Compiling the JSPs ties them to a particular server - unless you take the runtime along with them.

Unable to deploy pre-compiled archive

Similar Messages

Maybe you are looking for