Unable to deploy MDM_ENRICHMENT_CONTROLLER_02_59.sca

Hello SDN Experts, 
We are getting deploy exception while trying to deploye the MDM Enrichment Controller for MDM 7.1 SP02 on the CE Web AS server (7.1 SP 05). 
Please suggest a fix to deploy the Enrichment Controller successfully. 
 Below is the detailed exception log:
 
 
Details message(s):
Software component MDM_ENRICHMENT_CONTROLLER deployment messages:
Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca for component sap.com/MDM_ENRICHMENT_CONTROLLER aborted Detailed message: 1. Contains Aborted deployment component: sdu id: sap.com_tc~mdm~enrichment~ui sdu file path: D:\usr\sap\CE7\J04\j2ee\cluster\server0\.\temp\tc~bl~deploy_controller\archives\163\MDM_ENRICHMENT_CONTROLLER_02_59_sca1292490917366\DEPLOYARCHIVES\tc~mdm~enrichment~ui.sda version status: NEW deployment status: Aborted description: 1. [ERROR CODE DPL.DS.6193] Error while ; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application sap.com/tc~mdm~enrichment~ui. No one of the [developmentserver, com.sap.security.login-modules] containers, which processed it, returned deployed component names. The registered containers in this moment were [CTCContainer, com.sap.security.ume, developmentserver, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, SAP-EU-GP, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container]. Possible reasons : 1.An AS Java service, which is providing a container, is stopped or not deployed. 2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info. Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca --> tc~mdm~enrichment~controller.sda for component sap.com/tc~mdm~enrichment~controller is rejected because deployment of other component it depends on is rejected Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~mdm~enrichment~ui contained in software archive: sdu id: sap.com_MDM_ENRICHMENT_CONTROLLER Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca --> tc~mdm~enrichment~ui.sda for component sap.com/tc~mdm~enrichment~ui aborted Detailed message: 1. [ERROR CODE DPL.DS.6193] Error while ; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application sap.com/tc~mdm~enrichment~ui. No one of the [developmentserver, com.sap.security.login-modules] containers, which processed it, returned deployed component names. The registered containers in this moment were [CTCContainer, com.sap.security.ume, developmentserver, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, SAP-EU-GP, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container]. Possible reasons : 1.An AS Java service, which is providing a container, is stopped or not deployed. 2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info. Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca --> tc~mdm~enrichment~simulator~adapter.sda for component sap.com/tc~mdm~enrichment~simulator~adapter is rejected because deployment of other component it depends on is rejected Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~mdm~enrichment~ui contained in software archive: sdu id: sap.com_MDM_ENRICHMENT_CONTROLLER Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca --> tc~mdm~enrichment~ws.sda for component sap.com/tc~mdm~enrichment~ws is rejected because deployment of other component it depends on is rejected Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~mdm~enrichment~ui contained in software archive: sdu id: sap.com_MDM_ENRICHMENT_CONTROLLER Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca --> tc~mdm~enrichment~simulator~srvc.sda for component sap.com/tc~mdm~enrichment~simulator~srvc is rejected because deployment of other component it depends on is rejected Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~mdm~enrichment~ui contained in software archive: sdu id: sap.com_MDM_ENRICHMENT_CONTROLLER Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca --> tc~mdm~enrichment~ejb~ear.sda for component sap.com/tc~mdm~enrichment~ejb~ear is rejected because deployment of other component it depends on is rejected Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~mdm~enrichment~ui contained in software archive: sdu id: sap.com_MDM_ENRICHMENT_CONTROLLER Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca --> tc~mdm~enrichment~ws~proxy.sda for component sap.com/tc~mdm~enrichment~ws~proxy is rejected because deployment of other component it depends on is rejected Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~mdm~enrichment~ui contained in software archive: sdu id: sap.com_MDM_ENRICHMENT_CONTROLLER Deployment of archive \\CTSINSAPNW7\sapmnt\trans\EPS\in\MDM_ENRICHMENT_CONTROLLER_02_59.sca --> tc~mdm~enrichment~simulator~srvc_proxy.sda for component sap.com/tc~mdm~enrichment~simulator~srvc_proxy is rejected because deployment of other component it depends on is rejected Detailed message: 1. Aborted deployment archive: sdu id: sap.com_tc~mdm~enrichment~ui contained in software archive: sdu id: sap.com_MDM_ENRICHMENT_CONTROLLER See Deploy Controller log D:\usr\sap\CE7\J04\j2ee\JSPM\log\log_2010_12_16_14_43_32\deploy_2010-12-16_14-45-14.log for details.
Overall deployment messages: Deployment finished with error.

Thank you John for your reply.
We are deplying the SCA file that came with the MDM 7.1 installables.
To be on the safe side could you provide us a link on the service market place where we can download the SCA for the MDM Enrichment Controller ?
Appreciate your help.
Thanks

Similar Messages

Unable to deploy the .sca file for the Change tracker.

Hi all,
We can not able to deploy the change tracker through SDM as it is asking for the dependencies are missing.
Portal version EP 7.0 EHP1
MDM version 7.1 sp 5.
we have followed the below link for deploying
MDM change tracking with MDM 7.1 SP06 & EP version u2013 CE 7.2 SP01? but after downloading the MDM_WEB_UI from market place it is asking for 24+ dependencies for change tracker.
so please suggest.
regards,
Manohar.

Hello,
The version and the patch level should be same for MDM as well as EP.
Since this is an EP issue, for quick replies, post this in [Portal Forum|http://forums.sdn.sap.com/index.jspa?categoryID=1#2]
Regards,
Abhishek

Unable to deploy SCA file for MII 12.1

Hi,
We are trying to install the SAP MII 12.1. But through JSPM we are unable to deploy the SCA file. When we ry to deploy we are getting an error "AS JAVA is Not Running". Before starting the deployment we chckd that AS JAVA was running, but when we satrt deployment within two minutes the AS JAVA is stopped.If anybody come across the sam issue please let me know about this.
We have NW 7.1 CE EHP1 SP03 for MII 12.1.
The Log of the deployment is as below. I am unable to copy the entire log file because it is too big,so copied the last lines of the log file.Plz check below the log:
Deploy Result Description: Deployment exception occurred during deploy online data. Reason :An error occurred while deploying the deployment item 'sap.com_xappsxmiijraapp'.; nested exception is:
     com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.com_xappsxmiijraapp. Cannot deploy it.
[ deployerId=2 ]
Dec 1, 2009 4:26:14 PM   [Info ]:+++ Deployment finished with status 'Error' +++.[ deployerId=2 ][#10: 344.156 sec]
Dec 1, 2009 4:26:14 PM   [Path ]:+++++ End D E P L O Y action +++++[ deployerId=2 ]. Total time:[#9: 344.172 sec]
Dec 1, 2009 4:26:14 PM   [Debug ]:Incorrect client ID. The stub is not connected yet.
-Suresh

Hi,
We suceessfully got installed the MII 12.1.
The problem was with our NW installation. We have taken NW CE 7.1 EHP1 then it is worked.
-Suresh

Unable to deploy single SERVERCORE component using telnet?

Hi,
As continued to the discussion of "
Undeploying .SCA/ .SDA / .EAR / .WAR files on J2EE servers on Netweaver release 7.1 and higher"
I am trying to deploy one of the CORE component "SERVERCORE" using "TELNET" on my SAP NW7.3 EHP1 System but getting error that " SCA's aborted"
and unable to deploy the component. Please help me to get out of this.

Hi Chandra,
Sorry i did not understand your last reply. When you load all the core SCAs (put them into and folder) and then trigger the telnet option, the tool itself will take care of the dependencies and deploy the SCAs in the correct manner.
What was the error you were getting when you tried this?
You mentioned:
Did same using telnet as mentioned you and didn't update SPS to latest.
still they showing same as previous.
Does that mean that the deployment went fine, but still system info etc. shows old values? This is VERY strange. You can get the latest list from the configtool. Just check the attached screenshot for an example.
If this still shows old version, please run the force bootstrap once:
1)
Stop the j2ee server. Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files. Do not rename the bootstrap folder as this is needed for the sync process.
2)
Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.
3)
Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be syched with the DB content.
4)
Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.
Regards,
Hemanth

Unable to deploy from Eclipse - Runner class cannot be initialized

Hello
two days ago, I installed the newest versions of Glassfish Tools together with the newest Eclipse Luna SR1
when trying to deploy, I am getting the following error message:
org.glassfish.tools.ide.admin.CommandException: Cannot initialize Runner class
at org.glassfish.tools.ide.admin.AdminFactory.newRunner(AdminFactory.java:180)
at org.glassfish.tools.ide.admin.AdminFactoryHttp.getRunner(AdminFactoryHttp.java:110)
at org.glassfish.tools.ide.admin.ServerAdmin.exec(ServerAdmin.java:75)
at oracle.eclipse.tools.glassfish.GlassfishServerBehaviourDelegate.publishDeployedDirectory(GlassfishServerBehaviourDelegate.java:608)
at oracle.eclipse.tools.glassfish.GlassfishV4ServerBehavior.publishModuleForGlassFishV3(GlassfishV4ServerBehavior.java:96)
at oracle.eclipse.tools.glassfish.GlassfishV4ServerBehavior.publishModule(GlassfishV4ServerBehavior.java:56)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
the same application works if deployed directly to the glassfish server
I did all the suggestions as mentioned in Unable to deploy app form Eclipse Luna on Glassfish 4.0 or 4.1 with JDK8 but without success.
Does anybody has an idea what the problem could be and how to track it down?
Thanks a lot!

Hello Kostas
Thanks a lot for your help and hints! I am running Windows 7 64 Bit
I had Java 8, once with Release 20 and once with Release 25, installed - and thought that I pointed all to the newest version.
What helped in the end was to
- deinstall all Javas
- reboot
- installed newest JDK, without the "Public JRE"
- reboot
- set JAVA_HOME and appended the Java-bin-dir to the path-Variable
- reboot
- installed a fresh version of Glassfish
- configured a new Glassfish-Server on Eclipse
-> and now it runs perfectly!
Thanks again for your work and hints!

Unable to deploy Web App in Exploded format

Using WLS 6.1 sp2, I am unable to deploy a web application successfully using the
web app "ora" from http://www.thejspbook.com/examples.jspbook.zip. I've moved
the /ora directory under the /WEB-INF/applications directory.
The error I am getting is:
java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException:
Distributed Management [1 exceptions]
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:543)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
     at $Proxy18.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Distributed update exception
- remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
- actionName: addDeployment
- params: [Ljava.lang.Object;@10c03e
- signature: [Ljava.lang.String;@3d4a20
Distributed update exception
- remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
     at java.lang.String.substring(String.java:1525)
     at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:476)
     at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:232)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3415)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3384)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
     at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:815)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy34.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
     at $Proxy18.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.j2ee.DeploymentException: Could not load ora - with nested exception:
[java.lang.StringIndexOutOfBoundsException: String index out of range: -1]
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:431)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy34.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.--------------- nested within: ------------------
weblogic.management.console.utils.SetException: An error occurred while updating
Targets-Server on Proxy for efs-developer3:Application=ora,Name=ora,Type=WebAppComponent
- with nested exception:
[java.lang.reflect.InvocationTargetException - with target exception:
[weblogic.management.DistributedManagementException: Distributed Management [1
exceptions]]]
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help is appreciated.
Thanks,
Dennis

you are probably using a older version of 6.1. please use the latest service pack. Service Packs are mostly bug fix releases and they are safe to be upgraded even on production systems. Please note - we always recommend using the latest service pack
http://www.sun.com/download/products.xml?id=47d5d3eb

Error while deploying WC application: Unable to deploy EJB

Hi All,
we are getting the below error quite frequently, whenever we deploy the application to server:
[03:35:14 AM] Weblogic Server Exception: weblogic.application.ModuleException: Exception preparing module: EJBModule(CAWrapperEJB.jar)
Unable to deploy EJB: CAService from CAWrapperEJB.jar:
[EJB:011055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
[03:35:14 AM] Caused by: java.lang.Throwable: Substituted for missing class [EJB - 11055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAnService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
[03:35:14 AM] See server logs or server console for more details.
-to solve this issue we just delete the cache and restart the Managed server.
Please tell me what is the cause of this error and how can we fix it permanently, as restarting the server everytime is not very convenient.
TIA,
Bob

The content of "weblogic-ejb-jar.xml" present in code is:
<?xml version = '1.0' encoding = 'windows-1252'?>
<weblogic-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd"
xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar">
</weblogic-ejb-jar>

Unable to deploy EJB 3.0 on JBoss 4.0.4GA - no home interface

I am stuck in that my EJB3.0 project (one entity bean, one session bean and one client test bean) builds OK but somehow Eclipse Europa is unable to deploy it to JBoss (4.0.4 GA and 5 Beta) -- something to do with JNDI error as it involves javax.naming exceptions.
My Eclipse directory structure is :-
Titan (project name)
|
ejb - com.titan (package name)
| |
| domain -> Cabin.java (my entity bean)
| |
| travelagent -> TravelAgentBean.java
| -> TravelAgentRemote.java
|
META_INF -> ejb-jar.xml
-> MANIFEST.MF
-> persistence.xml
My ejb-jar.xml is :
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>Titan</display-name>
<enterprise-beans>

<session >
<display-name>TravelAgentBean</display-name>
<ejb-name>com/titan/travelagent/ejb/TravelAgentBean</ejb-name>
<remote>com.titan.travelagent.ejb.TravelAgentRemote</remote>
<ejb-class>com.titan.travelagent.ejb.TravelAgentBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
And my persistence.xml is :
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="Titan">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<class>com.titan.domain.Cabin</class>
<properties>
<property name="hibernate.connection.driver_class" value="oracle.jdbc.OracleDriver" />
<property name="hibernate.connection.url"
value="jdbc:oracle:thin:@localhost:1521:XE" />
<property name="hibernate.connection.username" value="SYSTEM" />
<property name="hibernate.connection.password" value="Swordfish1" />
</properties>
</persistence-unit>
</persistence>
I right-click on the Titan project name and choose Build Project. I get the following error message :-
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.2
Warning: A Session bean must implement, directly or indirectly, the javax.ejb.SessionBean interface.
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.3
Warning: A Session bean must define at least one ejbCreate method.
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.1
Warning: The session bean must implement either a remote home and remote, or a local home and a local interface or a service endpoint interface.
13:01:06,062 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.0.4.GA/server/default/deploy/Titan.jar
I don't understand, because as of EJB 3.0, you don't really need a home or local-home interface anymore...

Using @SecurityDomain("exemplo1") in my EJB and NOT providing jboss.xml, it works.
@SecurityDomain("exemplo1")
@RolesAllowed("yyy")
@Stateless(name="UserManagement")
public class UserManagementBean implements UserManagement {
public void add(User user) {
}Damn! This is some serious shit... I don�t want to configure this in every single EJB.
EJB 3.0 is nice, but some small trivial details like this and others, that was forgotten by Sun, piss me off!

Unable to deploy a form on the Web!!

Hi,
I am unable to deploy my form onto the web.
The following is the error message :
Oracle Forms Web CGI: Error detected
Your request cannot be serviced at this time due to the following error:
ERROR: Cannot open baseHTML file %FORMS60%\server\tester.htm.
Pls help me out in solving the problem.
Thanks in advance
Vishant

<BLOCKQUOTE>quote:<HR>Originally posted by Vishant Shenoy ([email protected]):
Hi,
I am unable to deploy my form onto the web.
The following is the error message :
Oracle Forms Web CGI: Error detected
Your request cannot be serviced at this time due to the following error:
ERROR: Cannot open baseHTML file %FORMS60%\server\tester.htm.
Pls help me out in solving the problem.
Thanks in advance
Vishant<HR></BLOCKQUOTE>
The most likely thing is that the file tester.htm is not in the directory %FORMS60%\server\
null

Unable to deploy a cmp 2.0 ejb to wls 8.1

windows Xp professional
IBM DB2
JBuilder 9.0
i build a ejb jar with jb9.0 wizard, then deploy it to wls.
but ...
D:\servers\bea\jdk141_03\bin\javaw -classpath
D:\servers\bea\weblogic81\server\lib\weblogic_sp.jar;D:\servers\bea\weblogic81\server\lib\weblogic.jar;D:\servers\bea\weblogic81\server\lib\webservices.jar;
weblogic.Deployer -user jerez -adminurl http://kame_house:7001
-password kinchin4587 -activate -name water -upload -source
D:/workspace/jbproject/water/water.jar -targets jerez
Initiated Task: [4] [Deployer:149026]Deploy application water on jerez.
Task 4 failed: [Deployer:149026]Deploy application water on jerez.
Deployment failed on Server jerez
weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: activate failed for
water
     Module: water     Error: Exception activating module:
EJBModule(water,status=PREPARED)
Unable to deploy EJB: Angle from water.jar:
java.lang.AbstractMethodError:
weblogic.jdbc.wrapper.DatabaseMetaData_COM_ibm_db2_jdbc_app_DB2DatabaseMetaData.supportsBatchUpdates()Z
     at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyBatchUpdatesSupported(RDBMSPersistenceManager.java:2081)
     at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:200)
     at
weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
     at
weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
     at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164)
     at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1004)
     at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1322)
     at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
     at
weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3012)
     at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2076)
     at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2057)
     at
weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2624)
     at
weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2547)
     at
weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2349)
     at
weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2431)
     at
weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2343)
     at
weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2511)
     at
weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
     at
weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
     at
weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at
weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Hi,
How did you uninstall the graphics drvier? From Devices manager or Programs and Features?
Please open Control Panel\All Control Panel Items\Programs and Features
And then, search for "NVIDIA Graphics Driver" and then select the "Change/Remove" button to begin the uninstall process.
Next, once the uninstall has completed, reboot Windows so that the other NVIDIA components can be removed as well.
If the issue still persists, since this driver that you recently installed caused problems with your PC, you can restore Windows back to an earlier point in time.
http://windows.microsoft.com/en-us/windows-8/restore-refresh-reset-pc
Regards,
Kelvin Xu
TechNet Community Support

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é

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 Applications: "process is not defined in the descriptor"

All
I'm having a fairly serious issue here trying to take an LCA from one environment and get it in another environment. Both the source and destination environments are LCES 2.5 (LCES 2 with SP2). I have roughly 6 applications and there are some far dependencies (one application referencing an asset of another application) therein. I've taken an LCA of all these applicaitons from the source environment and the LCA imports just fine in the destination environment but I am unable to deploy any of the applications that have far dependencies. The error I consistently get when I attempt to deploy any application that has a far dependency is:
[Some process name].process is not defined in the descriptor.
I have tried all of the following:
1) Taking 1 LCA of all applications together
2) Taking multiple LCAs where each LCA contains only one application
3) Taking multiple LCAs where each LCA includes an application as well as all far dependencies for that application
Regardless of what I try, they won't deploy. I can import the LCA and I can get the applications in Workbench and play around with them but they simply won't deploy. I've also attempted to manually fix all depencies within the processes themselves but that doesn't work either.
Any help would be appreciated.

Just wanted to follow up on the solution to my issue.
It appears the issue centers around circular far dependencies. In general, it seems LiveCycle chokes when two applications each reference one another. Note that I'm not talkinng about true circular referencing here wherein one process within application A references a process in application B while that same process refers back to the original process in application A. In fact, although I haven't tested recently, I believe LiveCycle may actually catch this kind of issue. The circular far dependencies I'm talking about is simply where a process in application A (call it a1) references a process in application B (call it b1) while a process in application B (call it b2) references a process in applicatoin A (call it a2). Apparently this kind of circular referencing causes the deployment of said applications to choke.
The fix was tedious as I had to manually delete all of the far dependencies from both application, deploy those two applications to get them into the runtime, and then implement those dependencies again.
Going forward it seems like a best practice to only ever have 1 direction for dependencies for any application.

Error while deploying BPMDMTECHN06_3.sca

Hi all
I'm getting the following deployment exception while trying to import the MDM Portal Content BPMDMTECHN06_3.sca file.
Starting Deployment of com.sap.pct.mdm.tech.packages.mdm_550
Aborted: development component 'com.sap.pct.mdm.tech.packages.mdm_550'/'sap.com'/'SAP AG'/'5.50.20090211152127.0000'/'0', grouped by software component 'BP_MDM_TECHNOLOGY'/'sap.com'/'SAP AG'/'1000.5.50.6.3.20090211152635''/'0':
Caught exception during module deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.pct.mdm.tech.packages.mdm_550.. Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: The archive .\temp\deploy\work\deploying\com.sap.pct.mdm.tech.packages.mdm_550.epa could not be deployed completely. Import failed for 1 of 6 objects. [PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.]
com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive .\temp\deploy\work\deploying\com.sap.pct.mdm.tech.packages.mdm_550.epa could not be deployed completely. Import failed for 1 of 6 objects. [PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.]
 at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:279)
 at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchives(PackageDeployServiceImpl.java:363)
 at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:163)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception during deploy: The archive .\temp\deploy\work\deploying\com.sap.pct.mdm.tech.packages.mdm_550.epa could not be deployed completely. Import failed for 1 of 6 objects. [PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.]
com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive .\temp\deploy\work\deploying\com.sap.pct.mdm.tech.packages.mdm_550.epa could not be deployed completely. Import failed for 1 of 6 objects. [PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.]
 at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:279)
 at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchives(PackageDeployServiceImpl.java:363)
 at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:163)
; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: The archive .\temp\deploy\work\deploying\com.sap.pct.mdm.tech.packages.mdm_550.epa could not be deployed completely. Import failed for 1 of 6 objects. [PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.]
com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive .\temp\deploy\work\deploying\com.sap.pct.mdm.tech.packages.mdm_550.epa could not be deployed completely. Import failed for 1 of 6 objects. [PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.]
 at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:279)
 at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchives(PackageDeployServiceImpl.java:363)
 at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:163)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception during deploy: The archive .\temp\deploy\work\deploying\com.sap.pct.mdm.tech.packages.mdm_550.epa could not be deployed completely. Import failed for 1 of 6 objects. [PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.]
com.sap.portal.transport.deploy.IncompleteDeploymentException: The archive .\temp\deploy\work\deploying\com.sap.pct.mdm.tech.packages.mdm_550.epa could not be deployed completely. Import failed for 1 of 6 objects. [PcdGlTransportManager.importObject(): cannot import an object in transport mode all that has been exported with transport mode data.]
 at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchive(PackageDeployServiceImpl.java:279)
 at com.sap.portal.transport.deploy.PackageDeployServiceImpl.deployArchives(PackageDeployServiceImpl.java:363)
 at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:163)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineSingleModuleOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEX C)
Deployment of com.sap.pct.mdm.tech.packages.mdm_550 finished with Error (Duration 9641 ms)
Starting Deployment of BP_MDM_TECHNOLOGY
Aborted: software component 'BP_MDM_TECHNOLOGY'/'sap.com'/'SAP AG'/'1000.5.50.6.3.20090211152635''/'0':
Failed deployment of SDAs:
development component 'com.sap.pct.mdm.tech.packages.mdm_550'/'sap.com'/'SAP AG'/'5.50.20090211152127.0000'/'0' : aborted
Please, look at error logs above for more information!
Deployment of BP_MDM_TECHNOLOGY finished with Error (Duration 2688 ms )
The problem occurs specifically while deploying com.sap.pct.mdm.tech.packages.mdm_550 EPA file.
I tried the solution given in the the link /thread/119921 [original link is broken]
but it didnt work.
Has anyone faced this before? Would appreciate useful responses.
Thanks
Swarna

Hi Swarna,
Could be the reason that the SCA file might get corrupted, it would be better if you download the SCA files again and try to deploy. Also if you already deployed the SCA files earlier then you first need to undeploy them manually and restart the portal server then try to deploy the SCAs again.
Atleast try restarting portal server and then deploy.
Regards,
Jitesh Talreja

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

Unable to deploy MDM_ENRICHMENT_CONTROLLER_02_59.sca

Similar Messages

Maybe you are looking for