Unable to deploy target module

Hi,
if I open Control Center Manager and try to deploy a module it fails.
Looking at logs i find
2008/01/06-23:46:34-CET [15D17D7][OWB1.OWB1] Attempting to create adapter 'class.Oracle Database.11.1.DDLDeployment'
2008/01/06-23:46:37-CET [15D17D7][OWB1.OWB1] java.sql.SQLException: Eccezione IO: The Network Adapter could not establish the connection
I have no idea why.
I can log on directly to the target schema.
If I edit the location and press "test connection" it works.
Oracle 11 running on Windows Vista on a single developement machine .
Kind regards,
Corrado

Hi Oleg,
that's OK, but I'm currently using an all-in-one developement machine.
I've Oracle 11 server with OWB on a single Vista computer.
So I should have a single tnsnames.ora.
Anyhow I noticed there's a second tnsnames.ora.
Despite the "good one" in ORACLE_HOME\network\admin there's a second one in ORACLE_HOME\owb\network\admin, filled with references to what seems oracle developement machines.
Here it is
# TNSNAMES.ORA Network Configuration File: d:\oracle\905228\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
dwlin165.us.oracle.com =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dwlin165.us.oracle.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ora1010.us.oracle.com)
DWSUN42 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = dwsun42)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = dev920.us.oracle.com)
dwlin12 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = dwlin12)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = iasdb.dwlin12.us.oracle.com)
ORA1010 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = stadq33.us.oracle.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ora1010.us.oracle.com)
Hope OWB isn't using this... :(
Kind regards,
Corrado

Similar Messages

  • Unable to deploy a module into XI Server

    Hi together,
    I developed a new module within the J2ee Development Studio. Compiling and building is ok. The ear-File is build... everything is fine... execpt the following.
    I connected the Development Studio to our XI Server. The connection is stable and working.
    Now, i try to deploy my development into the Server through the J2EE Explorer. I get the following result:
    10.04.2008 19:31:52 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : srv06007
    SDM port : 57018
    URL to deploy : file:/C:/DOKUME1/000282/LOKALE1/Temp/temp41484XI_Adapter_Module_Edifact_Parser.ear
    Result
    => deployment aborted : file:/C:/DOKUME1/000282/LOKALE1/Temp/temp41484XI_Adapter_Module_Edifact_Parser.ear
    Aborted: development component 'XI_Adapter_Module_Edifact_Parser'/'sap.com'/'localhost'/'2008.04.08.13.05.54'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/XI_Adapter_Module_Edifact_Parser.. Reason: Incorrect application sap.com/XI_Adapter_Module_Edifact_Parser:Bean EDIFACT_TO_XML: the ejb-class must implement, directly or indirectly, the javax.ejb.SessionBean interface. EJB specification 7.10.2.Error in the bean class: There is no public constructor with no parameters defined within bean de.regioit.xi.adapter.module.EDIFACT_TO_XML. Bean classes must have a public constructor with no parameters.Error in the bean class: The bean class de.regioit.xi.adapter.module.EDIFACT_TO_XML was found, but was declared as abstract. It must not be abstract.Bean EDIFACT_TO_XML: can not find method ejbCreate()  in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean EDIFACT_TO_XML: can not find method ejbCreate()  in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.Error in the local interface com.sap.aii.af.mp.module.ModuleLocal of bean EDIFACT_TO_XML: No corresponding business method in the bean class was found for method process.Error in the bean class: There is no public constructor with no parameters defined within bean com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl. Bean classes must have a public constructor with no parameters.Bean HmisBeanImpl: Cannot find home or component interfaces.; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/XI_Adapter_Module_Edifact_Parser:Bean EDIFACT_TO_XML: the ejb-class must implement, directly or indirectly, the javax.ejb.SessionBean interface. EJB specification 7.10.2.Error in the bean class: There is no public constructor with no parameters defined within bean de.regioit.xi.adapter.module.EDIFACT_TO_XML. Bean classes must have a public constructor with no parameters.Error in the bean class: The bean class de.regioit.xi.adapter.module.EDIFACT_TO_XML was found, but was declared as abstract. It must not be abstract.Bean EDIFACT_TO_XML: can not find method ejbCreate()  in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean EDIFACT_TO_XML: can not find method ejbCreate()  in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.Error in the local interface com.sap.aii.af.mp.module.ModuleLocal of bean EDIFACT_TO_XML: No corresponding business method in the bean class was found for method process.Error in the bean class: There is no public constructor with no parameters defined within bean com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl. Bean classes must have a public constructor with no parameters.Bean HmisBeanImpl: Cannot find home or component interfaces.
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
         at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
         at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/XI_Adapter_Module_Edifact_Parser:Bean EDIFACT_TO_XML: the ejb-class must implement, directly or indirectly, the javax.ejb.SessionBean interface. EJB specification 7.10.2.Error in the bean class: There is no public constructor with no parameters defined within bean de.regioit.xi.adapter.module.EDIFACT_TO_XML. Bean classes must have a public constructor with no parameters.Error in the bean class: The bean class de.regioit.xi.adapter.module.EDIFACT_TO_XML was found, but was declared as abstract. It must not be abstract.Bean EDIFACT_TO_XML: can not find method ejbCreate()  in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.6.Bean EDIFACT_TO_XML: can not find method ejbCreate()  in ejb-class de.regioit.xi.adapter.module.EDIFACT_TO_XML. Each create method must be named create<METHOD>, and it must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. EJB Specification 7.10.8.Error in the local interface com.sap.aii.af.mp.module.ModuleLocal of bean EDIFACT_TO_XML: No corresponding business method in the bean class was found for method process.Error in the bean class: There is no public constructor with no parameters defined within bean com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl. Bean classes must have a public constructor with no parameters.Bean HmisBeanImpl: Cannot find home or component interfaces.
         at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
         at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
         at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
         at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
         at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    I already copied the needed jar Files in the lib path of the server... I tried out nearly everything. On my workstation everything is OK - I guess, that a library is missing... What can I do, so that the XI is recocnising the jar files? Is there an other reason for that failure?
    Since I'm trying to figure out what is happening for one week now, you are my last chance :-).
    Thanks & Regards
        Thomas

    Hi,
    Like Stefan said..
    Reason: Incorrect application sap.com/XI_Adapter_Module_Edifact_Parser:Bean EDIFACT_TO_XML: the ejb-class must implement, directly or indirectly, the javax.ejb.SessionBean interface. EJB specification 7.10.2.Error in the bean class: There is no public constructor with no parameters defined within bean de.regioit.xi.adapter.module.EDIFACT_TO_XML. Bean classes must have a public constructor with no parameters.Error in the bean class: The bean class de.regioit.xi.adapter.module.EDIFACT_TO_XML was found, but was declared as abstract. It must not be abstract.
    Change the bean class EDIFACT_TO_XML in package..de.regioit.xi.adapter.module and change it from
    Abstract to public, save rebuild and re-deploy......
    Regards
    Ravi Raman

  • Error Exception activating module: EJBModule(p13n_ejb.jar) Unable to deploy

    Dears ,
    i'm facing this exception when try to activate changes after portal Ear deployment please help ???
    Message icon - Error An error occurred during activation of changes, please see the log for details.
    Message icon - Error Exception activating module: EJBModule(p13n_ejb.jar) Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar: Internal error: Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds. A typical test has been taking 1209 at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1540) at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:375) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:433) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61) at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1584) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1357) at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:438) at weblogic.jdbc.jta.DataSource.connect(DataSource.java:395) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:4028) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.verifyDatabaseType(RDBMSPersistenceManager.java:4250) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:261) at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300) at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249) at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172) at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166) at weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:238) at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324) at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Message icon - Error Substituted for missing class Internal error - Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds. A typical test has been taking 1209

    Hi
    As per the below stack trace, looks like the root cause is for some reasons, portal framework Datasources (connection pools) are not able to connect to the Database having portal schema. Make sure that before you deploy, if possible test all the Datasources from weblogic admin console to make sure they are able to communicate with backend portal db schema. There should be a TestConnection for each portal datasource. Or may be there is some network issue preventing access to this database. Once db is connected properly and connection pool testing is fine, then deploy your portal EAR.
    "...Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds..."
    HTH
    Ravi Jegga

  • Unable to deploy custom adapter module in PI 7.31

    Hi pros,
    I created a custom adapter module to split some complex input files to multiple messages. We use a SAP PO 7.31 java-only installation. I followed this document to create my adapter module:
    How to Create Modules for the JEE Adapter Engine
    I know it is for PI 7.1 but a colleague of mine said that he was able to create a running adapter module for PI 7.3 following the guide. I created the following projects:
    EAR project references the EJB project:
    Project facet of the EJBproject:
    ejb-jar.xml config:
    application-j2ee-engine.xml (in EAR project):
    When I try to deploy my module, I get the following error:
    Java version:
    NWDS version:
    Any hint is appreciated! What can be wrong? What can I check again?
    THANKS!
    Message was edited by: Stefan Münchow

    I am not sure if the version is the problem. We have PI 7.31, support package 14, patch level 0 and NWDS 7.31 support package 12, patch level 4. The version of NWDS is lower than the version of the PI. According to Note 1599298 the error occurs when the NWDS is higher than the one of PI. Besides, we are able to deploy BPMN processes with the same NWDS to the same server.
    This is the exact exception trace shown in NWDS:
    com.sap.ide.eclipse.sdm.deploy.DeploymentException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
    at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:110)
    ------------- Nested exception -------------------
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
    at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
    at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
    at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:80)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
    at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
    at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
    at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
    at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
    at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:167)
    at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
    at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
    at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
    ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/DP2/J64/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/213/SplitArticleFileModule_EAR.ear] failed
    at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:315)
    at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
    ... 11 more
    Caused by: com.sap.engine.services.deploy.container.rtgen.GenerationException: Open failed for '/usr/sap/DP2/J64/j2ee/cluster/server0/temp/deploy/SplitArticleFileModule_EAR.ear1422275742985/com.sap.aii.utilxi.server.jar' with fd 218 returning message 'couldn't find 'END' tag' and errno 0 after trying cache.
    at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.createSingleModule(WebServicesGenerator.java:100)
    at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.generate(WebServicesGenerator.java:54)
    at com.sap.engine.services.deploy.container.rtgen.AnnotationsSupportingGenerator.generate(AnnotationsSupportingGenerator.java:27)
    at com.sap.engine.services.deploy.ear.jar.moduledetect.GeneratorWrapper.generate(GeneratorWrapper.java:43)
    at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generate(ModuleGeneratorTool.java:110)
    at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generateOverExistingModules(ModuleGeneratorTool.java:97)
    at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generateModules(ModuleGeneratorTool.java:80)
    at com.sap.engine.services.deploy.ear.jar.EARReader.read(EARReader.java:240)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.prepareNewDeploymentInfo(DeployUtilTransaction.java:217)
    at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:199)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
    ... 12 more
    Caused by: java.util.zip.ZipException: Open failed for '/usr/sap/DP2/J64/j2ee/cluster/server0/temp/deploy/SplitArticleFileModule_EAR.ear1422275742985/com.sap.aii.utilxi.server.jar' with fd 218 returning message 'couldn't find 'END' tag' and errno 0 after trying cache.
    at java.util.zip.ZipFile.open(Native Method)
    at java.util.zip.ZipFile.<init>(ZipFile.java:154)
    at java.util.jar.JarFile.<init>(JarFile.java:141)
    at java.util.jar.JarFile.<init>(JarFile.java:105)
    at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesSupportHandlerImpl.generateWebSupport(WebServicesSupportHandlerImpl.java:79)
    at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.createSingleModule(WebServicesGenerator.java:69)
    ... 26 more
    Maybe the used jar files could be the problem?

  • 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 EJB: TrackedAnonymous from p13n_ejb.jar:

    Hi,
    I installed the weblogic portal 10.3.2 and configured the domain to use oracle express edition 11g. After configuring the domain, i got the error saying the weblogic server could not start because of tables does not exist. so i changed the database.properties and executed the create_db.cmd to create the tables and the server is started now.
    when i tried to deploy the weblogic portal application, i got the following error,
    <Aug 10, 2010 12:35:57 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Aug 10, 2010 12:37:44 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1281424006937' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
    Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
    [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
    weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
    Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
    [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
         Truncated. see log file for complete stacktrace
    Caused By: [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:251)
         at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300)
         at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249)
         at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
         at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166)
         Truncated. see log file for complete stacktrace
    >
    <Aug 10, 2010 12:37:44 PM IST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'MyPortalEAR'.>
    <Aug 10, 2010 12:37:44 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'MyPortalEAR'.>
    <Aug 10, 2010 12:37:44 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
    Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
    [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
         Truncated. see log file for complete stacktrace
    Caused By: [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:251)
         at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300)
         at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249)
         at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
         at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166)
         Truncated. see log file for complete stacktrace
    >
    <Aug 10, 2010 12:37:56 PM IST> <Warning> <Deployer> <BEA-149252> <No deployment 'MyPortalEAR' found for Operation stop.>
    Please guide me to resolve this issue.
    Thanks a lot,
    Suresh
    Edited by: user5701346 on Aug 10, 2010 10:34 PM

    I changed target for DataSource from AdminServer to my managed Server. That solved the problem.

  • Unable to deploy Mapping in OWB

    I am using OWB 10.1.0.4.0 for development purposes.
    I created a source module and a target module and then created a mapping.
    The mapping references 2 tables from the source and one table from the target itself.
    2 grant statements were executed from the source schema granting select on these 2 tables to the target schema.
    A database link was created in the target schema using the CREATE DATABASE LINK statement.
    A connector was deployed and successfully created in the target module in OWB.
    When I deploy the mapping, I get the error – table or view does not exist
    I checked the script that was generated as a result of the mapping deployment.
    All three tables are available in the select query. But the tables referenced from the source schema do not have
    the source schema name attached to them.
    i.e., if EMP table is referenced from the source schema SRC, the query should have SRC.EMP in the FROM
    clause. But this is not the case. Only EMP is referenced.
    I tried everything I could think of , but I am unable to deploy the mapping.
    Any suggestions are greatly appreciated

    In your map, does the source table reside in the OWB src module, and the target table reside in the target module? And the modules are configured correctly, so src module uses src location and tgt module uses tgt location. If OWB thinks these are in the same database instance schema.table references should be generated in the code, db link will not be used. The way this same locality is determined is by comparing the host, port,service names for example. Did you create your map like this? Or did you just add unbound tables representing the source and target in the map? So with OWB you can build bottom up or top down.
    Cheers
    DAvid

  • 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 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 create application module.  JNID/RMI problem?

    Hi forum,
    I've got an ADF/OC4J application deployed and running successfully but sometimes the following error comes up:
    JBO-30003: The application pool (com.miempresa.AppModuleLocal) failed to checkout an application module due to the following exception:
    oracle.jbo.JboException: JBO-29000: Unexpected exception caught:
    oracle.jbo.JboException, msg=JBO-29000: Unexpected exception caught: oracle.jbo.JboException, msg=JBO-25222: Unable to create application module.     at
    oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:2002)     
    In stack trace details we can found:
    java.lang.Thread.run(Thread.java:595)## Detail 0 ##javax.naming.NameNotFoundException: com.miempresa.AppModule not found          
    at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)          at
    com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:255)          at
    com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:195)          at
    javax.naming.InitialContext.lookup(InitialContext.java:351)          at
    oracle.jbo.common.ampool.DefaultConnectionStrategy.createApplicationModule(DefaultConnectionStrategy.java:136)
    Due to "NameNotFoundException", it seems to be reasonable to say that it's a JNDI problem. When application module is looked up through JNDI it's not found, so exeception is thrown. However, this doesn't happen frequently but occasionally. Why? What am I doing wrong?
    Thanks in advance for your help.
    Luis Serrano.

    Any ideas?

  • 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 EJB - weblogic,management.ApplicationException

    I am getting the following error when i deploy an ear file in WL 7.0 with MySQL
    at the backend
    There is one entity bean and one servlet in the application.
    can any body tell what mistake i could be making ?
    thanks in advance
    -vasanth
    error log
    =====
    weblogic.management.ApplicationException: Prepare failed. Task Id = null
    Module Name: titan_ejbs.jar, Error: Exception preparing module: EJBModule(titan_ejbs.jar,status=NEW)
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
    TargetException:
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)

    Add a <persistence-use> element to weblogic-ejb-jar.xml deployment descriptor.
    <persistence>
    <persistence-use>     
    <type-identifier>WebLogic_CMP_RDBMS</type-identifier>     
    <type-version>5.1.0</type-version>     
    <type-storage>META-INF/weblogic-cmp-jar.xml</type-storage>
    </persistence-use>
    </persistence>
    "vasanth" <[email protected]> wrote:
    >
    I am getting the following error when i deploy an ear file in WL 7.0
    with MySQL
    at the backend
    There is one entity bean and one servlet in the application.
    can any body tell what mistake i could be making ?
    thanks in advance
    -vasanth
    error log
    =====
    weblogic.management.ApplicationException: Prepare failed. Task Id = null
    Module Name: titan_ejbs.jar, Error: Exception preparing module: EJBModule(titan_ejbs.jar,status=NEW)
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
    TargetException:
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)

  • Unable to deploy EJB

    Hello, I'm try to runing an aplication on weblogic and now I stuck on this issue.
    Could anyone help me to solve this?
    Exception activating module: EJBModule(ejb.jar) Unable to deploy EJB: DrawingPhaseSessionEJB from ejb.jar: [EJB:011008]Unable to bind EJB Home Interface to the JNDI name: DrawingPhaseSessionEJB. javax.naming.NameAlreadyBoundException: Failed to bind remote object (ClusterableRemoteRef(-4455390609100261740S::contract_manager:AdminServer null)/1434 [com.primavera.exponline.server.drawing.DrawingPhaseSessionHome+javax.ejb.EJBHome+weblogic.ejb20.interfaces.RemoteHome]) to replica aware stub at DrawingPhaseSessionEJB(ClusterableRemoteRef(-4455390609100261740S::contract_manager:AdminServer [-4455390609100261740S::contract_manager:AdminServer/1269])/1269 [com.primavera.exponline.server.drawing.DrawingPhaseSessionHome+javax.ejb.EJBHome+weblogic.ejb20.interfaces.RemoteHome]); remaining name '' at weblogic.rmi.cluster.ClusterableRemoteObject.onBind(ClusterableRemoteObject.java:201) at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:371) at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:140) at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317) at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277) at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:439) at weblogic.ejb.container.deployer.EjbJndiService.bind(EjbJndiService.java:54) at weblogic.ejb.container.deployer.EjbJndiService.replicatedBind(EjbJndiService.java:38) at weblogic.ejb.container.deployer.Ejb2JndiBinder.bindHome(Ejb2JndiBinder.java:35) at weblogic.ejb.container.deployer.Ejb2JndiBinder.bindToJNDI(Ejb2JndiBinder.java:91) at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1229) at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1321) at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:495) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:542) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:168) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:637) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Thanks

    Hi Radhika,
    I'm guessing (if it's not a typo) that you need to change your directory
    name. You should create the following directory:
    employee\META-INF
    (Yes, case is important :-)
    And you should use that directory, instead of "employee\meta-inf".
    Hope this helps you!
    Good Luck,
    Avi.

  • JMS sub-deployment targeted to cluster

    Hello,
    I have read at the Oracle documentation that we can use a sub-deployment within a JMS module targeted only to a single JMS Server. But I have an application that create JMS resources with deploy descriptors (Application modules) and target the sub-deployment to a cluster with two machines, each machine has a JMSServer. It seems to work (I see them on the JNDI tree on both machines). This is the jms.xml:
    Do you also use sub-deployment targeted to a cluster or I shouldn't? Thank you in advance ;)
    I am using webLogic version 10.3.4.0
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-jms xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-jms"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
         <wls:quota name="InboundMessageQuota">
              <wls:bytes-maximum>1000000</wls:bytes-maximum>
              <wls:messages-maximum>10000</wls:messages-maximum>
         </wls:quota>
         <!-- Factories -->
         <wls:connection-factory name="InboundMessageConnectionFactory">
              <wls:sub-deployment-name>InboundMessage</wls:sub-deployment-name>
              <wls:jndi-name>jms.InboundMessageConnectionFactory</wls:jndi-name>
              <wls:security-params>
                   <wls:attach-jmsx-user-id>false</wls:attach-jmsx-user-id>
              </wls:security-params>
         </wls:connection-factory>
         <!-- Queue's -->
         <wls:uniform-distributed-queue name="InboundMessageQueue">
              <wls:sub-deployment-name>InboundMessage</wls:sub-deployment-name>
    <wls:delivery-params-overrides>
    <wls:delivery-mode>Non-Persistent</wls:delivery-mode>
    </wls:delivery-params-overrides>
    <wls:delivery-failure-params>
    <wls:redelivery-limit>0</wls:redelivery-limit>
    </wls:delivery-failure-params>
              <wls:jndi-name>jms.InboundMessageQueue</wls:jndi-name>
         </wls:uniform-distributed-queue>
    </wls:weblogic-jms>

    Technically, cluster targeting a distributed destination is supported, and it'll work as long as your can be absolutely assured that the cluster will never host additional JMS servers - perhaps from future projects, or due to integrating third party products. Otherwise, your distributed destinations will end up creating instances on JMS servers where they don't belong - a common mistake that can be tough to diagnose and untangle. I highly recommend staying with the best practice of using a subdeployment that references exactly the intended JMS servers. Note that a subdeployment can reference more than one JMS server.
    See [url  http://download.oracle.com/docs/cd/E17904_01/web.1111/e13738/best_practice.htm#JMSAD455] WL JMS Configuration Best Practices
    Hope this helps,
    Tom

Maybe you are looking for

  • Firewire Video Out

    This is so maddening. Its happened before. I sit down to FCE and its been open on the computer. I click on a sequence, and want to see it on external video monitor that was operating fine earlier in the day. It always works fine. Suddenly, no output.

  • Automatically fill free space with songs

    When I am syncing music to my iphone, and I check the box that says "Automatically fill free space with songs," how does itunes determine which songs it puts on my phone? Can I prevent it from placing unchecked songs in my library on my phone?

  • Simple things seem hard to figure out

    OK --- must admit I've not been a serious Logic user (mostly experienced with DP) but now that 9 has shown up and I'm trying MainStage again, I thought I'd try and use Logic for a new project to see if it's gotten any easier. But I'm getting stuck on

  • ABAP code to enhance a standard data source

    Hi BW experts, I am a novice in BW and I need to append a standard datasource <b>0DAT_SRC</b> with a field <b>FLD1</b> from table <b>TABL1</b>.Extract structure: <b>EX0001</b>. Can anybody please suggest how this can be done?I guess it requires some

  • Question mark for few seconds on startup..

    Hi, A question mark appears for few seconds on startup, and then the apple logo shows up. It looks like the system is not found in the beginning, but then it loads ok. Any thoughts on that? Thanks!