Weblogic.jspc outofmemory error while compiling jsps using ant in eclipse

Hi all,
I am trying to execute this target in my ant build:
     <target name="jspc">
          <java classname="weblogic.jspc" fork="yes">
               <arg line="-verbose -verboseJavac -compileAll -webapp ${project.jsp.dir} -d ${project.jsp.class.dir}" />
               <classpath>
                    <pathelement path="${classpath}" />
               </classpath>
     </java>
     </target>
I am getting the following error:
[java] Error: [jspc]: 0 file(s) failed:
[java] [Compilation errors : ]
[java] The system is out of resources.
[java] Consult the following stack trace for details.
[java] java.lang.OutOfMemoryError
[java] at weblogic.jspc.doCompile(jspc.java:861)
[java] at weblogic.jspc.runJspc(jspc.java:654)
[java] at weblogic.jspc.runBodyInternal(jspc.java:412)
[java] at weblogic.jspc.runBody(jspc.java:319)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:192)
I am using weblogic 8.1, eclipse3.1, java1.4.1.
Can some one please help me with this issue?
thanks in advance.

--> some error on posting please refer to the next post...
From the error logs we can trace it out to the web project's Build.xml file ....I was getting a similar error and by commenting out the following lines in the web project's Build.xml I am able to run the build script correctly and get a EAR file. The lines are
<!--
<assemble
moduleDir="${generated.module.root}"
moduleName="${project.name}"
srcOutputDir="${assembly.src}"
appRootDir="${ear.root}">
<assemblyContext factory="org.apache.beehive.controls.runtime.assembly.WebAppAssemblyContext$Factory" />
<assemblyContext factory="org.apache.beehive.controls.runtime.assembly.AppAssemblyContext$Factory" />
<classpath refid="assembly.classpath" />
<fileset dir="${project.dir}">
<include name="**/*.controls.properties" />
</fileset>
</assemble>
     -->
Please check it now, also if any one can let us know the function or role played by the above lines it would be great. Also if there would be any future or unseen problems by commenting out these lines please do let us know...
Thanks
-MiM
Edited by prodigymonish83 at 10/22/2007 5:56 AM

Similar Messages

  • "No tag library could be found with this URI" error while compiling jsp

    I am using WebLogic Server 9.2 MP1, JDK 1.5.0_09, Struts 1.3.5
              I am pre-compiling jsp pages with wlappc ant task. However, I got following errors when a jsp page contains ant taglib:
              No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
              The jsp page looks like:
              <%@ taglib uri="http://struts.apache.org/tags-html" prefix="html" %>
              wlappc complains taglib could not be retrieved from this uri. Actually, since Struts 1.3.5, those ".tld" files are contained in strust-taglib-1.3.5.jar, folder META-INF/tld/. And I don't need to set anything in web.xml <tag-lib> tab anymore.
              All the jsp pages can be successfully compiled while being deployed to Server. So what am I missing? My build.xml file looks like:
                   <target name="compile-jsp">
                        <wlappc source="${src.dir}" output="${out.dir}"
                             keepgenerated="true" optimize="true" classpathref="wl_classpath"/>
                   </target>
              where "wl_classpath" contains all the struts related jar files, e.g. struts-core-1.3.5.jar, struts-taglib-1.3.5.jar, ...., and weblogic related jars, e.g. weblogic.jar.....
              I checked "beehive" samples coming with weblogic92, and found it pretty much did the same thing regarding build script and jsp files. So I am totally lost!
              Please help me out. Many thanks.
              Edited by jqian at 02/02/2007 10:24 AM

    Yes sorry, you're correct. The uri I mentioned is just 1.0.
    Do you have the "Oracle WebLogic Web App Extension" Facet for your web project? If not, try adding that and making sure that there is a weblogic.xml file created in the WEB-INF dir. The weblogic.xml file allows you to deploy usig a shared lib for JSTL. It should contain a library-ref element something like the following, with a version of 1.1.
    <wls:library-ref>
    <wls:library-name>jstl</wls:library-name>
    <wls:specification-version>1.1</wls:specification-version>
    <wls:exact-match>true</wls:exact-match>
    </wls:library-ref>

  • NWDI - Runtime error while compiling JSPs (PAR DC)

    Hello
    I am creating a PAR DC that needs to use some in house developed
    ValueObjects (accessed through a J2EE server library).
    Though my developed JSPDynPage is able to access the ValueObjects, when I try to use it in a JSP, I get a runtime compilation error.
    According to my understanding, setting the PrivateSharingReference helps the controller (jspdynpage) find the classes it needs at runtime,
    But the JSP Compiler does not have access to those classes.
    Can anyone suggest a solution that does not include copying jar files
    manually?
    I have an open CSN about this, but no answer there yet...
    <a href="https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smp_custmsg/main.do?event=LOAD&smpsrv=h">CSN 0120025231 0001708061 2005</a>

    <a href="https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smp_custmsg/main.do?event=LOAD&smpsrv=h">updated link to CSN 0120025231 0001708061 2005</a>
    full stack trace:
    Exception ID:10:40_27/12/05_0011_2189050
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : pcd:portal_content/zachrefs/com.checkpoint.ReferencingIview
    Component class : com.cp.test.references.ReferencingIview
    User : Administrator
                at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
                at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
                at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
                at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
                at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
                at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
                at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
                at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
                at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
                at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
                at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
                at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
                at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
                at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
                at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
                at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
                at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
                at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:127)
                at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:279)
                at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:129)
                at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
                at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
                ... 38 more
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in executing a process for compilation, D:/usr/sap/ZAK/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/appl.test2.runtimereferencingpar/work/pagelet/_sapportalsjsp_referencingiview.java:18: package com.cp.test2.references.vo does not exist
    import com.cp.test2.references.vo.IMyValueObject;
                                      ^
    1 error
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.launchCompilerProcess(J2eeCompiler_6_30.java:562)
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compileExternal(J2eeCompiler_6_30.java:370)
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compile(J2eeCompiler_6_30.java:672)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2143)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:76)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:122)
                ... 43 more
    >>> JSPCompiler >>> error  [email protected]a27
    [EXCEPTION]
    com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in executing a process for compilation, D:/usr/sap/ZAK/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/appl.test2.runtimereferencingpar/work/pagelet/_sapportalsjsp_referencingiview.java:18: package com.cp.test2.references.vo does not exist
    import com.cp.test2.references.vo.IMyValueObject;
                                      ^
    1 error
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.launchCompilerProcess(J2eeCompiler_6_30.java:562)
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compileExternal(J2eeCompiler_6_30.java:370)
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compile(J2eeCompiler_6_30.java:672)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2143)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:76)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:122)
                at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:279)
                at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:129)
                at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
                at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
                at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
                at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
                at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
                at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
                at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
                at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
                at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
                at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
                at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
                at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
                at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
                at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
                at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
                at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
                at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
                at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
                at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    >>> JSPCompiler >>> ERROR in Compiling :JSPFileInfo :29823520
    JSP File : D:usrsap AKJC00j2eeclusterserver0appssap.comirjservlet_jspirj
    ootWEB-INFportalportalappsappl.test2.runtimereferencingparpageletReferencingIview.jsp
    Class Name: sapportalsjspReferencingIview
    Java File : D:usrsap AKJC00j2eeclusterserver0appssap.comirjservlet_jspirj
    ootWEB-INFportalportalappsappl.test2.runtimereferencingparworkpagelet\_sapportalsjsp_ReferencingIview.java
    Package Name : pagelet
    Class File : D:usrsap AKJC00j2eeclusterserver0appssap.comirjservlet_jspirj
    ootWEB-INFportalportalappsappl.test2.runtimereferencingparworkpagelet\_sapportalsjsp_ReferencingIview.class
    Is out dated : false [email protected]a27
    [EXCEPTION]
    com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in executing a process for compilation, D:/usr/sap/ZAK/JC00/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/appl.test2.runtimereferencingpar/work/pagelet/_sapportalsjsp_referencingiview.java:18: package com.cp.test2.references.vo does not exist
    import com.cp.test2.references.vo.IMyValueObject;
                                      ^
    1 error
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.launchCompilerProcess(J2eeCompiler_6_30.java:562)
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compileExternal(J2eeCompiler_6_30.java:370)
                at com.sapportals.portal.prt.servlets_jsp.server.compiler.impl.J2eeCompiler_6_30.compile(J2eeCompiler_6_30.java:672)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2143)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:76)
                at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:122)
                at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:279)
                at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:129)
                at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
                at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
                at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
                at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
                at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
                at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
                at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
                at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
                at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
                at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
                at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
                at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
                at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
                at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
                at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
                at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
                at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
                at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
                at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
                at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
                at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
                at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

  • Error while trying to use Ant and creating Jdbc Datasource

    I was following the documentation to auto-create my datasource in my weblogic server. I get an error while it is trying to link the datasource to the server. Does anybody have any ideas,it is almost like the query to get the server isn't working.
    Here is my ant task:
    <target name="setupJdbcDatasource">
         <wlconfig url="t3://localhost:7001" username="weblogic" password="weblogic">
         <query domain="MyDomain" type="Server" name="AdminServer" property="adminserver"/>
         <create type="JDBCConnectionPool" name="TestDatasource" property="DatasourceTest">
              <set attribute="CapacityIncrement" value="1"/>
              <set attribute="DriverName" value="weblogic.jdbcx.oracle.OracleDataSource"/>
              <set attribute="InitialCapacity" value="1"/>
              <set attribute="MaxCapacity" value="10"/>
              <set attribute="Password" value="cmuser"/>
              <set attribute="Properties" value="user=cmuser SID=ORCH serverName=10.13.5.144 portNumber=1521"/>
              <set attribute="RefreshMinutes" value="0"/>
              <set attribute="ShrinkPeriodMinutes" value="15"/>
              <set attribute="ShrinkingEnabled" value="true"/>
              <set attribute="TestConnectionsOnRelease" value="false"/>
              <set attribute="TestConnectionsOnReserve" value="false"/>
              <set attribute="URL" value="jdbc:bea:oracle://10.13.5.144:1521"/>
              <set attribute="Targets" value="${adminserver}"/>
         </create>
         </wlconfig>
    </target>
    My Domain is MyDomain, and server is AdminServer. The error I get is:
    [wlconfig] weblogic.management.DistributedManagementException : Distributed Management [1 exceptions]
    BUILD FAILED
    X:\ibutt_PCView\src\CM\build.xml:285: Error invoking MBean
    command: javax.management.MBeanException
    And in my server log:
    jdbcDataSourceBean=[MBeanServerInvocationHandler]com.bea:Name=CP-ConfigManagemen
    tTest,Type=weblogic.j2ee.descriptor.wl.JDBCDataSourceBean,Parent=[MyDomain]/JDBC
    SystemResources[CP-ConfigManagementTest],Path=JDBCResource
    <May 21, 2006 3:50:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "ConfigManagementTest": [BEA][Oracle JDBC Dri
    ver]Missing connection information: no serverName specified.>
    <May 21, 2006 3:50:58 PM EDT> <Error> <Deployer> <BEA-149265> <Failure occured i
    n the execution of deployment request with ID '1148241051441' for task 'weblogic
    .deploy.configChangeTask.2'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:

    Hi. This seems like an XML parsing problem.
    Could you please try changing the driver
    properties from:
    <set attribute="Properties" value="user=cmuser SID=ORCH serverName=10.13.5.144 portNumber=1521"/>
    to:
    <set attribute="Properties" value="user=cmuser SID=ORCH"/>
    The server and port are already in the URL
    thanks,
    Joe

  • Error while generating stub using ant generate-stubs

    I am getting error while running ant "generate-stubs" for generating stub.The details of errors as below:
    [exec] error: modeler error: expected root element "definitions" (in namesp
    ace "http://schemas.xmlsoap.org/wsdl/"), found element "html" (in namespace "nul
    l")
    Any help????

    Perhaps there is an error while you specified the namespaces. Chk them and try............Hope that helps...............ABHI

  • Error while generating ear using ant script in weblogic workshop 10

    In my application I have to create a ear file which should have the war file inside.
    I have created the build.xml for both ear application and web application, workshop.xml using weblogic workshop option
    File->export->WorkshopAntScripts
    I have been using the following command to execute the build.xml in EARApp(ear application)
    set the environment variables by running
    D:\bea\wlserver_10.0\common\bin\commEnv.cmd
    then
    D:\Source_Code\EARApp>ant clean build archive -Dworkspace="D:\Source_Code"
    I am getting the following error,
    Buildfile: build.xml
    init.env:
    check.versions:
    init.typedefs:
    init:
    clean:
    init.env:
    check.versions:
    init.typedefs:
    init:
    clean:
    [delete] Deleting 53 files from D:\Source_Code\WebApp\.apt_src
    [delete] Deleted 14 directories from D:\Source_Code\WebApp\.apt_src
    [delete] Deleting 218 files from D:\Source_Code\WebApp\build\classes
    [delete] Deleted 42 directories from D:\Source_Code\WebApp\build\classes
    [delete] Deleting directory D:\Source_Code\WebApp\build\assembly\.src
    [delete] Deleting directory D:\Source_Code\WebApp\build\weboutput
    [mkdir] Created dir: D:\Source_Code\WebApp\build\weboutput
    init.env:
    check.versions:
    init.typedefs:
    init:
    build:
    init.env:
    check.versions:
    init.typedefs:
    init:
    build:
    [apt] [web.content.root]|[D:\Source_Code\WebApp/\WebContent]
    [apt] [web.source.roots]|[D:\Source_Code\WebApp/src]
    [apt] Compiling 113 source files to D:\Source_Code\WebApp\build\classes
    [apt] warning: Annotation types without processors: [java.lang.SuppressWarnings, org.apache.be
    ehive.controls.system.jdbc.JdbcControl.ConnectionDataSource, org.apache.beehive.controls.system.jdbc
    .JdbcControl.SQL, com.bea.control.annotations.TransactionAttribute]
    [apt] 1 warning
    [apt] warning: Annotation types without processors: [java.lang.SuppressWarnings]
    [apt] 1 warning
    [apt] [web.content.root]|[D:\Source_Code\WebApp/\WebContent]
    [apt] [web.source.roots]|[D:\Source_Code\WebApp/src]
    [apt] Compiling 53 source files to D:\Source_Code\WebApp\build\classes
    [apt] warning: Annotation types without processors: [java.lang.SuppressWarnings]
    [apt] 1 warning
    [javac] Compiling 113 source files to D:\Source_Code\WebApp\build\classes
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] Compiling 53 source files to D:\Source_Code\WebApp\build\classes
    [delete] Deleting directory D:\Source_Code\WebApp\build\weboutput
    [mkdir] Created dir: D:\Source_Code\WebApp\build\weboutput
    [copy] Copying 1 file to D:\Source_Code\WebApp\build\weboutput\WEB-INF
    [copy] Copying 1 file to D:\Source_Code\WebApp\build\weboutput\WEB-INF
    init.env:
    check.versions:
    init.typedefs:
    init:
    stage:
    [delete] Deleting directory D:\Source_Code\EARApp\.staging
    [mkdir] Created dir: D:\Source_Code\EARApp\.staging
    [copy] Copying 7 files to D:\Source_Code\EARApp\.staging
    init.env:
    check.versions:
    init.typedefs:
    init:
    stage.to.ear:
    init.env:
    check.versions:
    init.typedefs:
    init:
    stage:
    init.env:
    check.versions:
    init.typedefs:
    init:
    generated.root.init:
    assembly:
    [mkdir] Created dir: D:\Source_Code\WebApp\build\assembly\.src
    [assemble] Assembly failed - Control Assembly process failed
    [assemble] Caused by: info
    BUILD FAILED
    D:\Source_Code\EARApp\build.xml:189: The following error occurred while executing t
    his line:
    jar:file:/D:/bea/WLSERV%7e1.0/workshop/lib/workshop-antlib.jar!/com/bea/workshop/cmdline/antlib/antl
    ib.xml:92: The following error occurred while executing this line:
    D:\Source_Code\EARApp\build.xml:201: The following error occurred while executing t
    his line:
    D:\Source_Code\WebApp\build.xml:351: The following error occurred while executing thi
    s line:
    D:\Source_Code\WebApp\build.xml:177: The following error occurred while executing thi
    s line:
    D:\Source_Code\WebApp\build.xml:424: Assembly failed.
    Some one help me solve this problem.
    Thanks in advance.

    --> some error on posting please refer to the next post...
    From the error logs we can trace it out to the web project's Build.xml file ....I was getting a similar error and by commenting out the following lines in the web project's Build.xml I am able to run the build script correctly and get a EAR file. The lines are
    <!--
    <assemble
    moduleDir="${generated.module.root}"
    moduleName="${project.name}"
    srcOutputDir="${assembly.src}"
    appRootDir="${ear.root}">
    <assemblyContext factory="org.apache.beehive.controls.runtime.assembly.WebAppAssemblyContext$Factory" />
    <assemblyContext factory="org.apache.beehive.controls.runtime.assembly.AppAssemblyContext$Factory" />
    <classpath refid="assembly.classpath" />
    <fileset dir="${project.dir}">
    <include name="**/*.controls.properties" />
    </fileset>
    </assemble>
         -->
    Please check it now, also if any one can let us know the function or role played by the above lines it would be great. Also if there would be any future or unseen problems by commenting out these lines please do let us know...
    Thanks
    -MiM
    Edited by prodigymonish83 at 10/22/2007 5:56 AM

  • Error while compiling JSP file from glassfish server

    Hello, I have created a single page with only one text box using Netbeans and Visual Web Pack and deployed it on to Glassfish Build44 server. Deployed okay. But when I try to open the page I get the following error. But the same project when I create on studio creator and deploy to Sun java App Server that comes with creator, it works fine. Any help would be really useful.
    Error:
    ApplicationDispatcher[MAReports] PWC1231: Servlet.service() for servlet jsp threw exception
    org.apache.jasper.JasperException: /Page1.jsp(5,60) PWC6341: According to the TLD, deferred-value is specified for the attribute id of the tag handler com.sun.webui.jsf.component.PageTag, but the argument for the setter method is not a javax.el.ValueExpression.
    I have tried 2 diff version of jdk1.5.0_06 and jdk1.5.0_12. No use. It is all running under win env. I saw couple google hits on this error. But no real solution that I could see.
    Thanks in Advance.

    Hi,
    I had the same problem i think:
    PWC1406: Servlet.service() for servlet Faces Servlet threw exception com.sun.rave.web.ui.appbase.ApplicationException: org.apache.jasper.JasperException: /login.jsp(5,60) PWC6341: According to the TLD, deferred-value is specified for the attribute id of the tag handler com.sun.webui.jsf.component.PageTag, but the argument for the setter method is not a javax.el.ValueExpression at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.cleanup(ViewHandlerImpl.java:559) at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:290) at .............
    I work on GlassFish v2 running on ubuntu server, I develop from netbeans 5.5.1 on windows xp.
    I resolved the problems in the war file of my application, the lib directory as some library missing, and some seem do not work correctely. I dont know precicely the problemes. but i resolve it copynig and past lib directory from another working project.
    The problemes seem to be in the war lib this what i can tell.
    sorry for my english
    Regards, and good job!!!

  • Jsp:useBean giving error while compiling JSP's in JDeveloper

    Hello,
    I am having another problem with JSP's in JDeveloper 10.1.3. jsp:useBean and jsp:setProperty are all giving problems. I am not sure what I need to do to get rid of this error
    Thanks,
    Lakshmisri

    Your original post mentions issues with jsp:useBean and jsp:setProperty, now you're talking about tag libraries and directives. Can you be more specific about what you're trying to do? Are you having problems getting JDev to recognize a tag library or are you having problems with the tag library when running the app? What directive are you trying to use that causes the termination error?

  • Error while compiling schema using JAXB 1.0.2 to

    Hi ,
    Please help ! i am trying to compile my schema using JAXB1.0.2 (bundled with Java Web Services Developer Pack 1.3 ) .I am getting a java.util.MissingResourceException . Can anyone help as to which portion of the schema i should look at.Here are the error details.
    thanks
    Rahul
    parsing a schema...
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: java.util.MissingResourceException: Can't find resource for bundle ja
    va.util.PropertyResourceBundle, key parser.cc.8
    at java.util.ResourceBundle.getObject(ResourceBundle.java:314)
    at java.util.ResourceBundle.getString(ResourceBundle.java:274)
    at com.sun.msv.datatype.xsd.regex.RegexParser.ex(RegexParser.java:138)
    at com.sun.msv.datatype.xsd.regex.ParserForXMLSchema.parseCharacterClass
    (ParserForXMLSchema.java:291)
    at com.sun.msv.datatype.xsd.regex.RegexParser.parseAtom(RegexParser.java
    :736)
    at com.sun.msv.datatype.xsd.regex.RegexParser.parseFactor(RegexParser.ja
    va:638)
    at com.sun.msv.datatype.xsd.regex.RegexParser.parseTerm(RegexParser.java
    :342)
    at com.sun.msv.datatype.xsd.regex.RegexParser.parseRegex(RegexParser.jav
    a:320)
    at com.sun.msv.datatype.xsd.regex.RegexParser.parse(RegexParser.java:158
    at com.sun.msv.datatype.xsd.regex.RegularExpression.setPattern(RegularEx
    pression.java:3040)
    at com.sun.msv.datatype.xsd.regex.RegularExpression.setPattern(RegularEx
    pression.java:3051)
    at com.sun.msv.datatype.xsd.regex.RegularExpression.<init>(RegularExpres
    sion.java:3017)
    at com.sun.msv.datatype.xsd.PatternFacet.compileRegExps(PatternFacet.jav
    a:79)
    at com.sun.msv.datatype.xsd.PatternFacet.<init>(PatternFacet.java:67)
    at com.sun.msv.datatype.xsd.TypeIncubator.derive(TypeIncubator.java:261)
    at com.sun.tools.xjc.reader.xmlschema.DatatypeBuilder.restrictionSimpleT
    ype(DatatypeBuilder.java:82)
    at com.sun.xml.xsom.impl.RestrictionSimpleTypeImpl.apply(RestrictionSimp
    leTypeImpl.java:66)
    at com.sun.tools.xjc.reader.xmlschema.DatatypeBuilder.build(DatatypeBuil
    der.java:65)
    at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.buildPrimitiveTy
    pe(SimpleTypeBuilder.java:161)
    at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.access$100(Simpl
    eTypeBuilder.java:50)
    at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder$Functor.checkCon
    version(SimpleTypeBuilder.java:201)
    at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder$Functor.restrict
    ionSimpleType(SimpleTypeBuilder.java:276)
    at com.sun.xml.xsom.impl.RestrictionSimpleTypeImpl.apply(RestrictionSimp
    leTypeImpl.java:66)
    at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.build(SimpleType
    Builder.java:93)
    at com.sun.tools.xjc.reader.xmlschema.cs.DefaultClassBinder.simpleType(D
    efaultClassBinder.java:130)
    at com.sun.xml.xsom.impl.SimpleTypeImpl.apply(SimpleTypeImpl.java:89)
    at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector._bindToClass(Clas
    sSelector.java:212)
    at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.bindToType(ClassS
    elector.java:177)
    at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.populate(BGMBuilder.jav
    a:254)
    at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.buildContents(BGMBuilde
    r.java:223)
    at com.sun.tools.xjc.reader.xmlschema.BGMBuilder._build(BGMBuilder.java:
    116)
    at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.build(BGMBuilder.java:8
    0)
    at com.sun.tools.xjc.GrammarLoader.annotateXMLSchema(GrammarLoader.java:
    424)
    at com.sun.tools.xjc.GrammarLoader.load(GrammarLoader.java:130)
    at com.sun.tools.xjc.GrammarLoader.load(GrammarLoader.java:79)
    at com.sun.tools.xjc.Driver.run(Driver.java:177)
    at com.sun.tools.xjc.Driver._main(Driver.java:80)
    at com.sun.tools.xjc.Driver.access$000(Driver.java:46)
    at com.sun.tools.xjc.Driver$1.run(Driver.java:60)

    Hi,
    A similar problem occur to me once.
    In that case it was that I copied the files from:
    JWSDP_HOME\jaxb\lib
    to
    JAVA_HOME\jre\lib\endorsed
    when I shouldn�t.
    I should take the files only from JWSDP_HOME\jwsdp-sahred\lib\endorsed
    So try taking the files:
    jaxb-api.jar
    jaxb-impl.jar
    jaxb-xjc.jar
    jaxb-libs.jar
    out of the JAVA_HOME\jre\lib\endorsed directory living them only in jaxb\lib where they should be.
    Try that, and let�s see if the compilation improves.

  • Error while Compiling Form using f60gen

    Hello All,
    I am trying to compile a customized form in apps middle tier using f60gen command.
    Actually the form is a customized version of FNDCPMCP.fmb(new form is in another name).
    f60gen throws the following error,
    Compiling package body CONC_PROG_PKG...
    Compilation error on package body CONC_PROG_PKG:
    PL/SQL ERROR 306 at line 4, column 3
    wrong number or types of arguments in call to 'INSERT_ROW'
    PL/SQL ERROR 0 at line 4, column 3
    Statement ignored
    PL/SQL ERROR 306 at line 59, column 7
    wrong number or types of arguments in call to 'LOCK_ROW'
    PL/SQL ERROR 0 at line 59, column 7
    Statement ignored
    PL/SQL ERROR 306 at line 109, column 3
    wrong number or types of arguments in call to 'UPDATE_ROW'
    PL/SQL ERROR 0 at line 109, column 3
    Statement ignored
    The form calls FND_CONCURRENT_PROGRAMS_PKG.
    What may be the issue.
    Thanks&Regards
    Kannan Balasubramanian

    Hello,
    It seems that you are trying to call Functions or Procedures with an incorrect argument list.
    Check the Function/Procedeure declaration.
    Francois

  • Error while compiling java file using J2SE 1.5.0

    Dear Sir,
    I'm getting the following error while compiling the java file.The code is also given.
    package test;
    public class TestRowSet {
    public TestRowSet() {
    "TestRowSet.java": cannot access java.lang.Object,bad class file: D:\Program Files\Java\jdk1.5.0\jre\lib\rt.jar\java\lang\Object.class,class file has wrong version 49.0, should be 48.0,Please remove or make sure it appears in the correct subdirectory of the classpath. at line 4, column 1
    Please help me out.
    --Suketu Naik.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    But I'm compiling within "Borland JBuilder 9.0". I've
    set the JDK path of the current project to point to
    the path of JDK 1.5.0 . I've also tried to compile at
    command prompt with "javac". I'm getting the same
    error of "Undefinedclassloader" with long StatckTrace.
    I don't know anything about JBuilder either. If you use the command prompt and enter the full path to the 1.5 javac.exe then that will prove whether the issue is using an older javac or not. For example "c:\j2sdk1.5.0_01\bin\javac HelloWorld.java"

  • Error while compiling SOA composite using Jdeveloper

    Hi,
    I am getting below given error while compiling the SOA composite using Jdeveloper..
    I m referring this PDF to develop a custom workflow.
    http://st-curriculum.oracle.com/obe/fmw/oim/oim_11g/developing_oim_custom_approval_process_for_self_registration/developing_oim_custom_approval_process_for_self_registration.pdf
    Error(45,34): Failed to compile bpel generated classes.
    failure to compile the generated BPEL classes for BPEL process "ApprovalProcess" of composite "default/SelfRegistrationApproval!1.0"
    The class path setting is incorrect.
    Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.
    Can u please let me know what am I missing here.
    Regards,
    Ab

    Hi,
    If u have any custom jars..make sure to add them at SCA-INF/lib directory.
    Thanks,

  • Running out of space while compiling JSPs

    Using WL7.0 on JDK1.3.1_06 on Solaris 8 we've run into an exception
    java.io.IOException: Not enough space(see below for full stack trace)
    while compiling JSPs. The problem is that we are running out of RAM
    because our WL7 process is quite large and when it tries to compile a
    JSP it forks itself which creates another large process. On our test
    machines since there might be several running instances of WL this can
    lead to the problem below. The natural fix for this would be to (1)
    precompile all the JSPS, (2) increase the RAM on the machine(s) in
    question, or (3) somehow force weblogic not to fork when doing page
    compilations.
    (1) In production we precompile our pages by running the weblogic.jspc
    class using arguments like -k -compileAll -depend -webapp $BRAND -d
    $DEST.
    Unfortunately this doesn't compile all of the pages probably because
    it doesn't execute cleanly due to the fact that we have some includes
    that aren't proper stand-alone JSPS (I don't know how to fix this
    other than changing all of our includes to dynamic includes which is
    undesirable at runtime). Any ideas here?
    (2) increasing the RAM isn't practical for all places where this
    problem occurs, in some cases we have maxed out the RAM on the
    machines we have.
    (3) Does anyone know if it is possible to tell WL not to fork when
    doing a JSP page compilation?
    Full compiler error(s):
    java.io.IOException: Not enough space
         at java.lang.UNIXProcess.forkAndExec(Native Method)
         at java.lang.UNIXProcess.<init>(UNIXProcess.java:54)
         at java.lang.Runtime.execInternal(Native Method)
         at java.lang.Runtime.exec(Runtime.java:546)
         at java.lang.Runtime.exec(Runtime.java:472)
         at java.lang.Runtime.exec(Runtime.java:438)
         at weblogic.utils.Executable.exec(Executable.java:208)
         at weblogic.utils.Executable.exec(Executable.java:133)
         at
    weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:545)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:354)
         at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:406)
         at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:206)
         at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:160)
         at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:447)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:287)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:376)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
         at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5360)
         at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
         at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3043)
         at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2468)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
    Thanks.
    Steven
    p.s. I did some searching on the forums before I posted this and was
    surprised that most of the posts on this subject were a) very old and
    b) didn't come to the conclusion that it was RAM space that the
    exception is referring to.

    As far as I remember, this error refers to the lack of swap space to
    fork the new process.
    In theory, you can specify compilerclass in weblogic.xml :
    weblogic-web-app
    jsp-descriptor
    param-name compilerclass
    param-value compilerclassname
    to compile in-process, but, for some reason, it doesn't work in 7.0
    (it did in 6.1 - probably a bug or something). When JSPServlet initializes
    in 7.0 it says:
    ... *.jsp: param compileCommand initialized to: compilerclassname>
    and forks javac anyway.
    Steven Samorodin <[email protected]> wrote:
    Using WL7.0 on JDK1.3.1_06 on Solaris 8 we've run into an exception
    java.io.IOException: Not enough space(see below for full stack trace)
    while compiling JSPs. The problem is that we are running out of RAM
    because our WL7 process is quite large and when it tries to compile a
    JSP it forks itself which creates another large process. On our test
    machines since there might be several running instances of WL this can
    lead to the problem below. The natural fix for this would be to (1)
    precompile all the JSPS, (2) increase the RAM on the machine(s) in
    question, or (3) somehow force weblogic not to fork when doing page
    compilations.
    (1) In production we precompile our pages by running the weblogic.jspc
    class using arguments like -k -compileAll -depend -webapp $BRAND -d
    $DEST.
    Unfortunately this doesn't compile all of the pages probably because
    it doesn't execute cleanly due to the fact that we have some includes
    that aren't proper stand-alone JSPS (I don't know how to fix this
    other than changing all of our includes to dynamic includes which is
    undesirable at runtime). Any ideas here?
    (2) increasing the RAM isn't practical for all places where this
    problem occurs, in some cases we have maxed out the RAM on the
    machines we have.
    (3) Does anyone know if it is possible to tell WL not to fork when
    doing a JSP page compilation?
    Full compiler error(s):
    java.io.IOException: Not enough space
         at java.lang.UNIXProcess.forkAndExec(Native Method)
         at java.lang.UNIXProcess.<init>(UNIXProcess.java:54)
         at java.lang.Runtime.execInternal(Native Method)
         at java.lang.Runtime.exec(Runtime.java:546)
         at java.lang.Runtime.exec(Runtime.java:472)
         at java.lang.Runtime.exec(Runtime.java:438)
         at weblogic.utils.Executable.exec(Executable.java:208)
         at weblogic.utils.Executable.exec(Executable.java:133)
         at
    weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:545)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:354)
         at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:406)
         at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:206)
         at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:160)
         at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:447)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:287)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:376)
         at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
         at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5360)
         at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
         at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3043)
         at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2468)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
    Thanks.
    Steven
    p.s. I did some searching on the forums before I posted this and was
    surprised that most of the posts on this subject were a) very old and
    b) didn't come to the conclusion that it was RAM space that the
    exception is referring to.--
    Dimitri

  • Getting error while publishing workflow using SP designer for SharePoint 2013

    Hi,
    I am try to setup Workflow manager for our sharepoint applications.
    WF manager set ran without any issue.
    I registered the SPWorkflow service which succeeded as well. The Workflow service application shows "Workflow is connected"
    I am creating a workflow using sharepoint designer using my credential (not Service account). I am able to save it but while publishing, its prompting with an error.
    The error says "Errors were found while compiling the workflow.The workflow files were saved but cannot run." Clicking advanced button show
    "Microsoft.SharePoint.SPException: We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
       at Microsoft.SharePoint.SPScaleOutDatabaseMap.CreateSqlSession(ISPScaleOutDatabaseMapProvider mapProvider, Byte[] compositeKey, Guid forceRefreshVersion, Guid& version)
       at Microsoft.SharePoint.SPScaleOutDatabaseCommandExecutor.Execute(ExecuteDelegate operation, ISPScaleOutDatabaseMapProvider mapProvide"
    Any help would be highly appreciated
    Thanks,

    Hi,
    According to your post, my understanding is that you got error while publishing workflow using SharePoint designer for SharePoint 2013.
    Please check whether the Central Admin > Manage Service Application-> “App Management Service” is started.
    Please check whether the “Configure service application associations”,  ”App Management Service” is already associated.
    Then please check whether the “Manage Services on server” and the “App Management Service” is started.
    In addition, please try to re-register Workflow Service.
    If the issues still exists, please follow the steps in the
    Steps to Verify that Server Is Correctly Set Up. After you verified that the server is correctly set up, follow the steps in the
    Steps to Troubleshoot Workflow Management Service and
    Troubleshooting the Service Bus for Windows Server then retry your action related to publishing workflows
    More information:
    http://wp.ahcheng.com/2013/03/23/error-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run/
    http://sp2013.pro/2013/04/solution-errors-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run-cannot-set-unknown-member/
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • Error while compiling the PO Item Category KFF

    Kindly help me. I am new and learning Purchasing module and now stuck because of an error while compiling the PO Item Category KFF. This is because a segment is saved in the database incompletely.
    Now the segment does not show in the Segments Summary form. But when I enter the same Number, I get the error APP-FND-00924: You chose a sement number that is used by another segment.
    When I freeze and compile the structure with different segments, I get the error
    APP-FND-00668: The data that defines the flexfield on this field may be inconsistent. Inform your system administrator that the function: FDFRKS could not find the structure definition for the flexfield specified by Application = &APPL, Code = MCAT and Structure number = 201 (APPID=401)
    APP-FND-00738: Error detected when attempting to load value set on Context: &CONTEXT for Segment: &SEGMENT in Routine: FDFBKS
    APP-FND-01564: ORACLE error 1403 in FDFAVS3
    Cause: FDFAVS3 failed due to ORA-01403: no data found.
    The SQL statement being executed at the time of the error was:  and was executed from the file &ERRFILE.
    Regards
    Reem

    Hi Sandeep
    Sorry that I am bothering with basic questions, but I am not able to run any Select queries. It gives error Table or View does not exist. I can see the table from ALL_TABLES view, but I cannot Select.
    I have logged in as oracle user. This is not Vision datbase. Can you let me know the default dba user and password or how to get the permission?
    Regards
    Reem

Maybe you are looking for