EPMA Hanged during deployment 11.1.2.0

Hello all,
I have a EPMA deployed application in verison 11.1.2. I added metadata to my application & validated my application without any error. I tried deploying it & selected outline refresh option. I went to job console & in summary its showing:
Started Time : Monday, April 18, 2011 2:22:58 PM
Submitted Time : Monday, April 18, 2011 2:22:58 PM
Last Updated Time : Monday, April 18, 2011 2:23:40 PM
User Name : admin
Process Name :
Thread : 0
Server :
Detail : Initiating Product Action...
Generating Headers and Callback Information...
Generating Application Data...
Posting Product Request...
Waiting For Status Updates...
When i see status it shows me
Status : Running
Progress : 10%
I refreshed the screen multiple times & its been running for 5 hours now & i guess it is stuck. When i go to application library there are few menus including validate & deploy that are disabled as i think it is still processing my request. How can I kill this process ?
Thanks

Hello,
you cann't kill the deployment, there is a timeout setup for 480 min. After the deployment will be available you can change this timeout, and set in lower.
Look in the configuration file here %APP_SERVER_DEPLOYMENT_DIR%\EPMAWebServer\applications\EPMAWebServer\awb\WEB-INF\conf\AWBConfig.properties
the setting called DEPLOY_PENDING_TIMEOUT_MINUTES.
Regards,
Ilias

Similar Messages

  • SAP Netweaver 7.00 - JSPM hangs during deployment

    Hello community,
    we have an environment with SAP Netweaver 7.00 Java stack only
    We are trying to apply Support package stack SP20, starting from SP14, but JSPM remains hang after the start of the deploy.
    JSPM window becomes blank and we are not able to see what is going on, we can only look at the log files
    What can be done to solve the problem? I was not able to find relevant SAP notes
    Regards,
    Valerio

    Hello,
    JSPM window became visible and ready for input after the complete of the deploy step.
    there are no errors in the logs and the deploy step completed successfully, so it is difficult to provide more information
    We made this activity on a test server with little resources (particularly for memory) and we noticed that the use of cpu and memory was quite high during the deploy, so maybe this issue is related to low resources.
    Thanks everybody,
    Valerio

  • OWB R2 hangs during Deployment

    Hi OWB experts,
    Can anybody tell me why i am not able to deploy a mapping/table or any object in OWB rel 2 ( running on Windows ) .
    Appreciate if someone can reply.
    Thanks

    Is there any error message?
    Have you take a look at [OWB_HOME]\owb\log?
    Isn't there any error messages in database alert.log?
    Regards,
    Marcos

  • Server 2012 R2, EFI and vSphere 5.1 = Hang during OSD

    I'm currently testing Server 2012 R2 deployment via SCCM 2012, on a VMware Virtual Machine.
    I've run into an issue where if the VM firmware is set to EFI instead of Legacy BIOS the machine hangs during the Task Seqeunce - the OS image is downloaded and written to disk, the machine reboots to continue with the TS and then hangs at the blue
    Windows logo, never to progress any further - screenshot here, same issue with Windows 8:
    http://www.cb-net.co.uk/microsoft-articles/34-configmgr/2078-configmgr-windows-8-uefi-and-vmware-esxi-5
    ESXi platform is version 5.1, Virtual Machine Hardware Version is 9 - tested with version 8 as well.
    Has anyone got this working successfully?
    Thanks, Chris
    MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

    Hi,
    Have you checked the log file smsts.log ?
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • ClassCastException during deployment with more than one used entity

    Hi,
    i am still trying to get into NW development and got one more time stuck. I have a CE 7.1 SR5 project containing a dictionary, a bean module, an EAR project and a web dynpro project.
    With the following two classes everything runs fine:
    [AT]Entity
    [AT]Table(name="TMP_USER")
    [AT]NamedQueries(value={[AT]NamedQuery(name="doLogin", query="SELECT u FROM User u WHERE u.login = :login AND u.password = :password")})
    public class User implements Serializable {
         [AT]Id
         private int id;
         private String login;
         private String password;
         private static final long serialVersionUID = 1L;
         public User() {
              super();
    // Omitted Accessors
    [AT]Stateless(name="UserSessionBean")
    [AT]WebService
    public class UserSessionBean implements UserSessionLocal
         [AT]PersistenceContext(unitName="DBAccess")
         private EntityManager em;
         public User doLogin(String login, String password)
              Query query = em.createNamedQuery("doLogin");
              query.setParameter("login", login);
              query.setParameter("password", password);
              try
                   return (User) query.getSingleResult();               
              catch(NoResultException e)
                   return null;
    build, deploy, run in webservice navigator -> ok
    Then i created a new entity:
    [AT]Entity
    [AT]Table(name="TMP_PROJECT")
    [AT]NamedQueries(value={[AT]NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
    public class Project implements Serializable {
         [AT]Id
         private int id;
         private int ownerid;
         private String name;
         private Timestamp creationtime;
         private String description;
         private int number;
         private short subnumber;
         private static final long serialVersionUID = 1L;
         public Project() {
              super();
      Omitted Accessors
    build, deploy, run in webservice navigator -> no problem.
    Then i changed  the UserSessionBean to:
    [AT]Stateless(name="UserSessionBean")
    [AT]WebService
    public class UserSessionBean implements UserSessionLocal
         [AT]PersistenceContext(unitName="DBAccess")
         private EntityManager em;
         public User doLogin(String login, String password)
              Query query = em.createNamedQuery("doLogin");
              query.setParameter("login", login);
              query.setParameter("password", password);
              try
                   return (User) query.getSingleResult();               
              catch(NoResultException e)
                   return null;
         public Projecet testfunc()
              return null;
    And now during deployment there is an warning (in reality it´s an exception) and the bean does not work any more.
    The exception is
              1. Exception has been returned while the 'testproject.testcorp.de/testprojectear' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7707450:com.sap.engine.services.deploy.container.DeploymentException:
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:693)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
         at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
         at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Exception occured during web services deployment. Unable to generate serialization framework for web service UserSessionBeanService, application testproject.testcorp.de/testprojectear.
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:360)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:220)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.execute(WSInitialStartProcess.java:140)
         at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDProcess.makeProcess(WSBaseAbstractDProcess.java:316)
         at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.makeStartInitially(WebServicesDeployManager.java:688)
         ... 37 more
    Caused by: java.lang.ClassCastException: class com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$5:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive incompatible with class com.sun.xml.bind.v2.model.impl.ClassInfoImpl:library:jaxb20[AT]com.sap.engine.boot.loader.ResourceMultiParentClassLoader[AT]1489c06[AT]alive
         at com.sun.xml.bind.v2.model.impl.ClassInfoImpl.getBaseClass(ClassInfoImpl.java:170)
         at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:58)
         at com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getBaseClass(RuntimeClassInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:142)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
         at java.util.AbstractList$Itr.next(AbstractList.java:422)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.calcRef(TypeRefImpl.java:56)
         at com.sun.xml.bind.v2.model.impl.TypeRefImpl.getTarget(TypeRefImpl.java:33)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:22)
         at com.sun.xml.bind.v2.model.impl.RuntimeTypeRefImpl.getTarget(RuntimeTypeRefImpl.java:15)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:38)
         at com.sun.xml.bind.v2.model.impl.ElementPropertyInfoImpl$1.get(ElementPropertyInfoImpl.java:41)
         at java.util.AbstractList$Itr.next(AbstractList.java:422)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getClassInfo(ModelBuilder.java:139)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:48)
         at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.getClassInfo(RuntimeModelBuilder.java:40)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:189)
         at com.sun.xml.bind.v2.model.impl.ModelBuilder.getTypeInfo(ModelBuilder.java:204)
         at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:356)
         at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:217)
         at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
         at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
         at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
         at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
         at com.sap.engine.services.webservices.jaxws.j2w.JaxWsSchemaGenerator.genJaxbMappings(JaxWsSchemaGenerator.java:274)
         at com.sap.engine.services.webservices.jaxws.j2w.JaxWsIMappingGenerator.generateWSDL(JaxWsIMappingGenerator.java:103)
         at com.sap.engine.services.webservices.server.deploy.ws.WSInitialStartProcess.generateJAXWSFramework(WSInitialStartProcess.java:286)
         ... 41 more
    I already downgraded my Java JRE/JDK to 1.5.0_15 as it was hinted here in the forum, but the problem persists. Any idea what is wrong?

    Thanks for the answer, but i am not using this wizard. Some how this project class must be flawed.
    public User testfunc()
    return null;
    works, but changing to
    public Project testfunc()
    return null;
    immediately leads to the above deployment error.
    This is the offending class, it compiles without warning
    package de.testcorp.testproject.beans;
    import java.io.Serializable;
    import java.sql.Timestamp;
    import javax.persistence.*;
    @Entity
    @Table(name="TMP_PROJECT")
    @NamedQueries(value={@NamedQuery(name="findAllProjects", query="SELECT p FROM Project p")})
    public class Project implements Serializable {
         @Id
         private int id;
         private int ownerid;
         private String name;
         private Timestamp creationtime;
         private String description;
         private int number;
         private short subnumber;
         private static final long serialVersionUID = 1L;
         public Project() {
              super();
         public int getId() {
              return this.id;
         public void setId(int id) {
              this.id = id;
         public int getOwnerid() {
              return this.ownerid;
         public void setOwnerid(int ownerid) {
              this.ownerid = ownerid;
         public String getName() {
              return this.name;
         public void setName(String name) {
              this.name = name;
         public Timestamp getCreationtime() {
              return this.creationtime;
         public void setCreationtime(Timestamp creationtime) {
              this.creationtime = creationtime;
         public String getDescription() {
              return this.description;
         public void setDescription(String description) {
              this.description = description;
         public int getNumber() {
              return this.number;
         public void setNumber(int number) {
              this.number = number;
         public short getSubnumber() {
              return this.subnumber;
         public void setSubnumber(short subnumber) {
              this.subnumber = subnumber;

  • Error during deployment of Message Driven Bean

    Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
              I am getting some error (or perhaps warning) during deployment of Message
              Driven Bean. Any one seen this before?
              This error only comes on a machine with Dual Network card.
              Thanks.
              ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
              ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
              <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
              enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
              Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
              is of a non-final version of the appropriate specification. It is subject to
              change in future releases once the specification becomes finalized. This may
              cause application code developed for BEA WebLogic Server 6.1 that uses the
              new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
              supported in future releases of BEA WebLogic Server.>
              ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
              unable to connect to the JMS destination: CQM_MessageQueue. The EJB
              container will automatically attempt to re-establish the connection with the
              JMS server. This warning may occur during WebLogic Cluster start-up if the
              JMS destination is located on another server. When the JMS server connection
              is re-established, the Message-Driven EJB will again receive JMS messages.
              The Error was:
              Unable to create a JNDI InitialContext to lookup the JMS destination. The
              error was:
              javax.naming.CommunicationException. Root exception is
              java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
              nested exception is:
              java.net.ConnectException: Connection refused: connect; No available router
              to destination
              at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              at
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              textFactoryDelegate.java:307)
              at
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              textFactoryDelegate.java:211)
              at
              weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              ory.java:149)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              at javax.naming.InitialContext.init(InitialContext.java:217)
              at javax.naming.InitialContext.<init>(InitialContext.java:193)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
              rivenBeanInfoImpl.java:641)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
              nPoller.java:474)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
              .java:418)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
              nectionPoller.java:286)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
              foImpl.java:511)
              at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
              at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
              at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
              at weblogic.j2ee.Application.addComponent(Application.java:170)
              at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:360)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              Target.java:285)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              eploymentTarget.java:239)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              entTarget.java:199)
              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:6
              21)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy34.updateDeployments(Unknown Source)
              at
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              ServerMBean_CachingStub.java:2977)
              at
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              icationManager.java:372)
              at
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              r.java:160)
              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:6
              21)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy49.start(Unknown Source)
              at
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              ApplicationManagerMBean_CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              at weblogic.management.Admin.finish(Admin.java:644)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              at weblogic.Server.main(Server.java:35)
              >
              ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010009> <EJB Deployed EJB with JNDI name
              ASYNCMessageDrivenBean.>
              

    Hi Tom
              Yes we do have an URL provided in the descriptor. It's
              t3://jms.server.net:7001.
              and the jms.server.net is resolved via a hosts file in Win2K
              eg,
              192.168.100.200 jms.server.net
              You are right in saying that the loopback in a dual-net card is a problem.
              But our solution
              above solves the issue as long as your host file does not use 127.0.0.1 as
              the IP.
              We need the URL b/c depending on our client's deployment , the JMS Server
              may be remote or may be local.
              "Tom Barnes" <[email protected]> wrote in message
              news:[email protected]...
              > Hi x,
              >
              > Something to do with the loopback and dual-network cards is
              > messin' with WLS' mind. I do not know what the problem is,
              > but I can guess:
              >
              > You have specified an URL in the MDB descriptor when there
              > is no need for one. If t3://127.0.0.1:7001 is in the same
              > cluster the MDB is running in (I suspect this URL is
              > actually the same WL server), then don't specify the URL.
              > This URL is only useful for connecting an MDB to a JMS
              > server that is outside local server and outside the cluster.
              > The URL may be working on single-network card systems
              > as perhaps then WL has enough info to guess that you
              > actually mean the local WL server, and simply converts
              > the context to a local context.
              >
              > Note that the URL option in the MDB descriptor is actually
              > a WebLogic extension of J2EE.
              >
              > Tom
              >
              >
              >
              > x wrote:
              > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
              > >
              > > I am getting some error (or perhaps warning) during deployment of
              Message
              > > Driven Bean. Any one seen this before?
              > > This error only comes on a machine with Dual Network card.
              > >
              > > Thanks.
              > >
              > >
              > >
              > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
              > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
              <main>
              > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
              features
              > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
              1.2,
              > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
              6.1
              > > is of a non-final version of the appropriate specification. It is
              subject to
              > > change in future releases once the specification becomes finalized. This
              may
              > > cause application code developed for BEA WebLogic Server 6.1 that uses
              the
              > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
              > > supported in future releases of BEA WebLogic Server.>
              > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
              <main>
              > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
              > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
              > > container will automatically attempt to re-establish the connection with
              the
              > > JMS server. This warning may occur during WebLogic Cluster start-up if
              the
              > > JMS destination is located on another server. When the JMS server
              connection
              > > is re-established, the Message-Driven EJB will again receive JMS
              messages.
              > > The Error was:
              > > Unable to create a JNDI InitialContext to lookup the JMS destination.
              The
              > > error was:
              > > javax.naming.CommunicationException. Root exception is
              > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
              > > nested exception is:
              > > java.net.ConnectException: Connection refused: connect; No available
              router
              > > to destination
              > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:307)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:211)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              > > ory.java:149)
              > > at
              javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
              > > at
              javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              > > at javax.naming.InitialContext.init(InitialContext.java:217)
              > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
              > > at
              > >
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
              > > rivenBeanInfoImpl.java:641)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
              > > nPoller.java:474)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
              > > .java:418)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
              > > nectionPoller.java:286)
              > > at
              > >
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
              > > foImpl.java:511)
              > > at
              weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
              > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
              > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
              > > at weblogic.j2ee.Application.addComponent(Application.java:170)
              > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              > > arget.java:360)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              > > Target.java:285)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              > > eploymentTarget.java:239)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              > > entTarget.java:199)
              > > 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:6
              > > 21)
              > > at
              > >
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > > nImpl.java:360)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > > at $Proxy34.updateDeployments(Unknown Source)
              > > at
              > >
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              > > ServerMBean_CachingStub.java:2977)
              > > at
              > >
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              > > icationManager.java:372)
              > > at
              > >
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              > > r.java:160)
              > > 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:6
              > > 21)
              > > at
              > >
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > > nImpl.java:360)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > > at $Proxy49.start(Unknown Source)
              > > at
              > >
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              > > ApplicationManagerMBean_CachingStub.java:480)
              > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              > > at weblogic.management.Admin.finish(Admin.java:644)
              > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              > > at weblogic.Server.main(Server.java:35)
              > >
              > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              > > <system> <> <010009> <EJB Deployed EJB with JNDI name
              > > ASYNCMessageDrivenBean.>
              > >
              > >
              >
              

  • Error while deploying BPEL Process(Error during deployment: Deployment Fail

    Hi,
    when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] HTTP error code returned [500]
    [04:53:50 PM] Error message from server:
    Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    [04:53:50 PM] Check server log for more details.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] #### Deployment incomplete. ####
    [04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Please, any one can tell solution for this.
    Thanks In advance
    Amar.
    Edited by: 897448 on Dec 13, 2011 8:48 PM

    Hi,
    when i try to deploying 11.1.1.3 - bpel project with thirdpartyparty adapter from jdeveloper to weblogic server, I got the following error.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] HTTP error code returned [500]
    [04:53:50 PM] Error message from server:
    Error during deployment: Deployment Failed: [JCABinding] [TPASOAProject.Service1/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    [04:53:50 PM] Check server log for more details.
    [04:53:50 PM] Error deploying archive sca_TPASOAProject_rev1.0.jar to partition "default" on server soa_server1 [10.150.67.195:8001]
    [04:53:50 PM] #### Deployment incomplete. ####
    [04:53:50 PM] Error deploying archive file:/C:/JDeveloper/mywork/Application16/TPASOAProject/deploy/sca_TPASOAProject_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Please, any one can tell solution for this.
    Thanks In advance
    Amar.
    Edited by: 897448 on Dec 13, 2011 8:48 PM

  • Error during deploying the java patches.

    Hi gurus.
    error during deploying   jtechf patch.through SDM.when deploying SQL TRACE the probelm occured.

    SDM LOG
    Dec 8, 2008 5:09:21 PM   Info: Finished saving the repository
    Dec 8, 2008 5:09:24 PM   Info: Starting: Update: Selected software component 'SA
    P_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.15.0.20080216073957''/'9' updates curren
    tly deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.12.0.
    20070507085740''/'3'.
    Dec 8, 2008 5:09:24 PM   Error: Aborted: software component 'SAP_JTECHS'/'sap.co
    m'/'SAP AG'/'1000.7.00.15.0.20080216073957''/'9':
    Failed deployment of SDAs:
    development component 'SQLTrace'/'sap.com'/'SAP AG'/'7.0013.20070703111935.0000'
    /'9' : aborted

  • IPod recognized, but hangs during update

    So my iPod will show up in Finder and in iTunes, and automatic updating will begin. However, at random times during the update, sometimes 4 songs in, sometimes 65, the whole process will just hang. iTunes status screen gets stuck on flashing between "Updating iPod..." and Song 65 of 2054 and just flash between those two over and over.
    Meanwhile, the iPod screen itself is also stuck and no longer flashing "Do Not Disconnect" -- it's a steady screen with none of the normal flashing.
    Tried resetting, doesn't do anything.
    Tried restoring, and it hangs after Authenticate asks me for my password to Restore the iPod.
    I wind up having to just force disconnect and force quit everything and restart.
    Anybody else have this problem? Thanks for any help you can give.
    Oh btw, OS 10.3.9, iTunes 4.9, iBook G4.

    I am having the same issue where it hangs during update -- seems to always happen around the 1800th song. Here's more specifics:
    -I've got 7000 songs in my Library
    -my iTunes Music folder is located on an external FireWire HD
    My Mac has no problems mounting the iPod. No problems restoring with iPod Updater. No problems with erasing using Disk Utility.
    I have tried the following:
    1. Resetting and then restoring via iPod Updater.
    2. Erasing/reformatting via Disk Utility, including zeroing out all data, and then restoring via iPod Updater.
    3. Resetting into Disk Mode.
    4. Manually updating songs.
    5. Automatcially updating songs.
    Nothing works. I have been troubleshooting this for about 8 hours now with no luck. No matter what I do differently, it always hangs around song 1800. I even tried uninstalling/reinstalling iTunes -- and I have tried this with several different user accounts and on different partitions I have set up.
    When it "hangs," the iPod itself just makes a the "clicking" sound of a HD. I'm wondering if the HD is just bad -- but it came up with no errors when checking with Disk Utility.
    Any more suggestions?
    Johnny

  • Arch Live CD x64 hanging during boot at "triggering uevents"

    Hello!
    I recently was recommended Arch by a friend, and after I followed the 'Newbies Guide' and burning a live CD to install Arch with, it appears to hang during Live CD boot at "installing uevents."
    I am trying to install Arch as a dual boot on a late 2008 MacBook Pro which is currently running x64 Windows 7. I have plenty of HD space (100gb free and 100gb unallocated to install Arch onto).
    Here is a picture:
    http://i.imgur.com/Y8P41nf.jpg
    I get the same error weather I try to install x64 or i686 (I think that's what it's called). Is there any reason for this?
    Thank you!
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code --
    (Sorry, missed that. My bad!)
    Last edited by RalphORama (2013-09-07 03:09:13)

    frank604 wrote:
    You can try nomodeset.  Seems to be a failure in loading a driver for your hardware. To read more on similar issues, there's a few posts with more info and suggestions by googling it. 
    Google result: http://lmgtfy.com/?q=halt+at+triggering+uevent
    Results:
    https://bbs.archlinux.org/viewtopic.php?id=151259
    https://bbs.archlinux.org/viewtopic.php?id=140426
    Thanks! I tried googling it myself but got mostly answers that didn't work. I'll try this!

  • Disk utility hangs during disk verify

    Initially 'disk verify' registered errors on exit - minor error/issue it said,some kind of header problem, so I ran disk utility off the install disk. Now the machine's native version of disk utility hangs during disk verify, blue & white spirals forever.
    This coincidentally straight after my gmail/google address/account was hacked a couple of days ago.

    Have you tried booting in SafeBoot mode (shift key held on start
    until login screen appears) then launch Disk Utility and then run
    its 'repair disk permissions' item, selecting the Macintosh HD;
    and then note the repair window. It should fix something.
    And when Disk Utility is done, quit it, and restart the Mac normally.
    {...It is unlikely something from gmail affected your computer unless
    you open up unknown sourced emails or go to odd web sites where
    something may be downloaded from there, which you would almost
    have to install (as admin, etc) for malware to work. You can get and
    try ClamXAV for free to see if it sees any malware virus content.}
    If you use Gmail, and do not log in using the https:// (secure http)
    you should change the habit and bookmark the secure login site.
    And when booted from the Installer disk and running Disk Utility
    from there, see about running "repair disk" and not verify. The
    repair choice will verify; but verify will not repair. Could be if
    you cannot use the Utility to Repair the issues, and the other
    SafeBoot mode and the computer's Disk Utility to get it working
    you may need to further troubleshoot and/or get third-party tools.
    In any event...
    Good luck & happy computing!

  • PLEASE HELP ! While updating My Xperia Z1 , my pc hanged during the process and .

    While updating My Xperia Z1 , my pc hanged during the process ( so , installation of update was interrupted , guess it's same as getting your USB connection disconnected )and now the phone won't turn on .
    Its shows the Sony Xperia logo , then shows a black lit screen , and that's it , nothing else happens . I can only turn it off by pressing and holding the power+up volume button , but it turns on automatically if plugged in for charging or in PC only till it gets that black screen .
    I tried to flash it with a flashtool (Emma) , but it says phone locked , but since it can't even be turned on , i can't unlock it .
    It's a store bought phone and is not of any contracts with any mobile service provider or anything like that ....
    Funny you know ... my PC had to crash at the moment i was updating it .... my luck ....
    Anyways , now please can anyone tell me what i can do ? I'm sure there is a way i can fix it using my pc and other downloadable software , so please can some one help me how i can fix this problem ? I don't care if i lose all the data on it , i just want my phone back ....
    Solved!
    Go to Solution.

    Problem Solved ,Thank you  very much !! 
    For those who might face the problem and stumble upon this thread after googling  
    Read above mentioned comments 
    Now here's what I did :
    Turned the phone off by power+volume key method , then plugged it in to the pc via USB and opened sony pc companion , entered Support zone , then entered the Update device option , then I Unplugged my device , only after doing this a window pops up with  Repair my phone/tablet in blue text , then i clicked on that and followed the simple instructions ..
    It's basically what Thommo said , only i was so freaked out at that time that i failed to follow his instructions to the letter  
    So now my phone is back to normal , and , it got the latest lolipop update !
    Problem solved i guess  but Thommo , i need to disturb you again with  just one more  question ,  since at the very beginning , the update process was interrupted , and now i got lolipop after  the repair ,without needing to update again ,  so has the lollipop been installed properly on my phone or do i need to use any other flashtool to re-install lollipop ? 
    again , Thank you ... 

  • X200 hangs during restart or shut down when connected to ultrabase

    My X200 hangs during a Windows restart or shut down when I'm connected to my ultrabase.  The laptop appears to go through most of the processes to restart/shut down but eventually hangs at a blue screen with unmoveable cursor (note, not a Windows BSOD). I'm forced to perform a hard shut down to turn off the laptop.
    This hang at restart/shut down only occurs when I'm connected to the ultrabase.

    Just as a thing to try, and this is assuming that you all have an integrated camera, please try this camera driver and let the board know the results:
    http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70600

  • Error during deployment - SOA Suite 11.1.1.4.0

    Hi,
    When I try to deploy bpel flow in the SOA Suite 11.1.1.4.0 i receive the error below:
    The bpel flow deploy and works fine in the SOA Suite 11.1.1.3.0_ (Jdeveloper 11.1.1.3.0)
    #;There was an error deploying the composite on AdminServer: Deployment Failed: Error occurred during deployment of component: CllReceiveEmployeeFromPSFTEBS to service engine: implementation.bpel, for composite: cll_ReceiveEmployeeFromPSFT: ORABPEL-05250
    #;Error deploying BPEL suitcase.
    #;error while attempting to deploy the BPEL component file "/vol02/appsoa/product/11.1.0/user_projects/domains/base_domain/servers/AdminServer/dc/soa_5d9300f2-10a2-4784-8865-83f7159ee9ce"; the exception reported is: java.lang.Exception: BPEL 1.1 compilation failed
    #;This error contained an exception thrown by the underlying deployment module.
    #;Verify the exception trace in the log (with logging level set to debug mode).
    [04:07:33 PM] Check server log for more details.
    [04:07:33 PM] Error deploying archive sca_CllReceiveEmployeeFromPSFT_rev1_0.jar to partition "ebs_psft" on server AdminServer [brdell21.br.oracle.com:7001]
    [04:07:33 PM] #### Deployment incomplete. ####
    [04:07:33 PM] Error deploying archive file:/C:/jdev11g/mywork/EBS-PSFT/CllReceiveEmployeeFromPSFT/deploy/sca_CllReceiveEmployeeFromPSFT_rev1_0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Regards,
    Marcos Allonso

    Hi,
    I copied fle sca_cll_ReceiveEmployeeBankAccountFromPSFT_rev1_0.jar to C:\jdev11g\mywork\EBS-PSFT\CllReceiveEmployeeBankAccountFromPSFT\SCA-INF\lib , redeploy flow but the problem remain.
    *** I am using a Jdeveloper 11.1.1.3.0 to deploy flow in the SOA Suite 11.1.1.4.0
    Regars,
    Marcos

  • Sun J2EE SDK 1.3_01, java.lang.ClassCastException thrown during deployment

    I encountered a bug while using the deploytool to deploy
    an EAR file to the Sun J2EE 1.3_01 server.
    I submitted a bug report to Sun via the Sun Java Developer Connection.
    (Sorry, it has not been assigned a BugID yet)
    Question:
    Does anybody know if the web container in Sun's
    J2EE 1.3_01 server supports access to local enterprise beans?
    Screenshots of the bug are available at
    http://sync4j.sourceforge.net/deploymentbug/
    Full details below....
    -Sean
    category: j2ee
    subcategory: deployment
    release: 1.3_01
    hardware: x86
    OSversion: windows_2000
    synopsis: java.lang.ClassCastException thrown during deployment of Session bean
    java -version
    java version "1.3.1_01"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
    Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)
    C:\j2sdkee1.3\bin>j2ee -version
    Java 2 Enterprise Edition version 1.3_01, build 1.3_01-b01
    I built a EJB 2.0 compliant stateful session bean.
    The session bean has a remote interface (ISyncRemote),
    a remote home interface (ISyncHomeRemote),
    a local interface (ISyncLocal),
    and a local home interface (ISyncHomeLocal).
    I built an HTTP Servlet that is supposed to access
    the Stateful Session Bean using ISyncHomeLocal and
    ISyncLocal
    I run "deploytool.bat" in GUI mode to perform the deployment.
    During deployment, the deploytool GUI displays a message
    box which states:
    "There was a deployment error.
    java.rmi.ServerException: RemoteException occurred in server thread;
    nested exception is:
    java.rmi.RemoteException: An error was encountered while loading
    a web component.
    Please refer to
    <J2EE_HOME>/logs/<machine-name>/j2ee//j2ee/error.log
    for more information. Please verify your Application with the
    Verifier tool."
    The "error.log" file did not contain any useful information.
    I ran the J2EE "verifier.bat" tool to verify that my EAR archive is OK.
    The Sun J2EE server output this error string:
    "java.lang.ClassCastException:
    com.sun.enterprise.deployment.EjbExternalDescriptor"
    Here is the full output from the Sun J2EE server:
    C:\j2sdkee1.3\bin>j2ee -verbose
    J2EE server listen port: 1050
    Naming service started:1050
    Binding DataSource, name = jdbc/EstoreDB, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/Cloudscape, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/DB1, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/DB2, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/InventoryDB, url =
    jdbc:cloudscape:rmi:CloudscapeDB;create=true
    Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
    Binding DataSource, name = jdbc/XACloudscape__xa, dataSource =
    COM.cloudscape.core.RemoteXaDataSourc
    e@245536
    Starting JMS service...
    Initialization complete - waiting for client requests
    Binding: < JMS Destination : jms/Queue , javax.jms.Queue >
    Binding: < JMS Destination : jms/Topic , javax.jms.Topic >
    Binding: < JMS Cnx Factory : TopicConnectionFactory , Topic , No properties >
    Binding: < JMS Cnx Factory : jms/TopicConnectionFactory , Topic , No properties
    >
    Binding: < JMS Cnx Factory : QueueConnectionFactory , Queue , No properties >
    Binding: < JMS Cnx Factory : jms/QueueConnectionFactory , Queue , No properties
    >
    Starting web service at port: 8000
    Starting secure web service at port: 7000
    J2EE SDK/1.3
    Starting web service at port: 9191
    J2EE SDK/1.3
    J2EE server startup complete.
    Compiling c:\j2sdkee1.3\repository\rbi\gnrtrTMP\Sync4j Server enterprise
    application\sync4j\server\s
    yncbean\SyncBean_LocalHomeImpl.java ....
    Compiling c:\j2sdkee1.3\repository\rbi\gnrtrTMP\Sync4j Server enterprise
    application\sync4j\server\s
    yncbean\SyncBean_EJBLocalObjectImpl.java ....
    Compiling c:\j2sdkee1.3\repository\rbi\gnrtrTMP\Sync4j Server enterprise
    application\sync4j\server\s
    yncbean\SyncBean_RemoteHomeImpl.java ....
    Compiling c:\j2sdkee1.3\repository\rbi\gnrtrTMP\Sync4j Server enterprise
    application\sync4j\server\s
    yncbean\SyncBean_EJBObjectImpl.java ....
    rmic sync4j.server.syncbean.SyncBean_RemoteHomeImpl...
    rmic sync4j.server.syncbean.SyncBean_EJBObjectImpl...
    c:\j2sdkee1.3\repository\rbi\applications\Sync4j Server enterprise
    application1004172068449Server.ja
    r
    Binding name:`java:comp/env/ejb/ISyncHomeRemote`
    Binding name:`java:comp/env/ejb/ISyncHomeLocal`
    java.lang.ClassCastException:
    com.sun.enterprise.deployment.EjbExternalDescriptor
    at com.sun.enterprise.deployment.EjbReferenceDescriptor.getValue
    (EjbReferenceDescriptor.java
    :202)
    at com.sun.enterprise.naming.NamingManagerImpl.bindObjects
    (NamingManagerImpl.java:394)
    at com.sun.web.server.WebService.addContext(WebService.java:148)
    at com.sun.web.server.ServletDeployerImpl.loadWebComponents
    (ServletDeployerImpl.java:214)
    at
    com.sun.enterprise.tools.deployment.backend.JarInstallerImpl.deployWebComponent
    s
    (JarInsta
    llerImpl.java:791)
    at
    com.sun.enterprise.tools.deployment.backend.JarInstallerImpl.deployApplication
    (JarInstall
    erImpl.java:219)
    at
    org.omg.stub.com.sun.enterprise.tools.deployment.backend._JarInstallerImpl_Tie.
    invoke(Un
    known Source)
    at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch
    (ServerDelegate.java:355)
    at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:273)
    at com.sun.corba.ee.internal.iiop.RequestProcessor.process
    (RequestProcessor.java:84)
    at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run
    (ThreadPool.java:99)
    Does the Sun J2EE server implementation support the invocation
    of Session EJB's via a Local interface?
    Does the Sun J2EE server implementation allow a Servlet to invoke
    Session EJB's via the bean's Local interface?
    While researching this issue, I read the J2EE 1.3 final specification.
    The spec says:
    "The EJB container is required to access to local enterprise beans.
    We recommend that the web container also support access to local
    enterprise beans."
    Does the web container in Sun's J2EE server support access to local enterprise beans?

    I'm pretty much sure that you cannot access a
    local Session bean from outside the EJB container.Please read the J2EE 1.3 specification before posting messages about EJB and J2EE.
    According to the J2EE 1.3 specification:
    "The EJB container is required to support access to local enterprise beans. We recommend that the web container also support access to local enterprise beans.
    No support is provided for access to local enterprise beans from the application client container or the applet container."
    If you use local interfaces for your session bean,
    than your client must be local too. A local client is
    a client that is collocated in the same JVM with the
    session/entity that provides the local view and which
    can be tightly coupled to the bean.My client is running in the same JVM as my EJB. The client is a servlet. The servlet is running in the same JVM as the EJB.
    For what its worth, the error that I observed occurs during deployment. I haven't figured out why deployment is failing.

Maybe you are looking for