NoSuchMethodError:weblogic.management.MBeanHome.getMBeansByType

Hello,
I am trying to support legacy code which uses the MBeanHome API.
With WLS 9 MBeanHome is deprecated but according to the WLS 9 docs it is supported if the domains compatibility server is enabled - which it is by default.
On WLS 9.2 I am getting :
NoSuchMethodError:weblogic.management.MBeanHome.getMBeansByType
Can anyone help? this may be something obvious but I'm a newbie. Thank you very much.
Mary-Jo

Hi,
Like you said "The version of getMBeansByType used was deprecated in WLS 6.1 and removed in WLS 9. I changed the code to use the newer api"
Can you please provide me somw example of using new API.
In my application, MBeanHome.getMBeansByType methd has been used to get "Cluster" and "ServerRuntime" and my job is to change that using newer API as application has to be moved to WLS 9.2.
So if u can provide some example it would be really appreciated.
-Abi

Similar Messages

  • JNDI lookup for weblogic.management.MBeanHome

    Tried to do JNDI lookup for MBeanHome. It could resolve
    weblogic.management, but not MBeanHome.
    Any idea? Thank you
    T. Pei
    PS
    The statement and the error message:
    MBeanHome mBeanHome = (MBeanHome) initialContext.lookup
    ("weblogic.management.MBeanHome.JNDI_NAME.MyServer");
    javax.naming.NameNotFoundException:
    Unable to resolve weblogic.management.MBeanHome.JNDI_NAME.MyServer
    Resolved: 'weblogic.management'
    Unresolved:'MBeanHome' ; remaining name 'JNDI_NAME.MyServer'

    I answered this in my last post, but to clarify your attempt below.
    you can access MBeanHome through JNDI in any of three ways that I
    currently know...
    MBeanHome mBeanHome =
    (MBeanHome)ctx.lookup("weblogic.management.adminhome");
    MBeanHome mBeanHome =
    (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
    MBeanHome mBeanHome =
    (MBeanHome)ctx.lookup(MBeanHome.JNDI_NAME+"."+yourservername);
    typically yourservername = "myserver"
    when I print MBeanHome.ADMIN_JNDI_NAME I get
    "weblogic.management.adminhome"
    when I print MBeanHome.JNDI_NAME I get
    "weblogic.management.home"
    so using MBeanHome.JNDI_NAME+"."+yourservername is the same as
    "weblogic.management.home.myserver", if the server you are trying to access
    is called myserver.
    may be more information than you want.
    "T. Pei" <[email protected]> wrote in message
    news:3a7a1562$[email protected]..
    >
    Tried to do JNDI lookup for MBeanHome. It could resolve
    weblogic.management, but not MBeanHome.
    Any idea? Thank you
    T. Pei
    PS
    The statement and the error message:
    MBeanHome mBeanHome = (MBeanHome) initialContext.lookup
    ("weblogic.management.MBeanHome.JNDI_NAME.MyServer");
    javax.naming.NameNotFoundException:
    Unable to resolve weblogic.management.MBeanHome.JNDI_NAME.MyServer
    Resolved: 'weblogic.management'
    Unresolved:'MBeanHome' ; remaining name 'JNDI_NAME.MyServer'

  • Example to access weblogic's MBeanHome interface using javax.management.MBeanServer

    Hi All
    I am new to the JMX world and newer at accessing Weblogic MBeans. I don't
    want to use the weblogic specific classes like Environment and Helper
    because then my code won't be appserver neutral.
    Can you please provide me with an example to access weblogoc MBeans using a
    fully JMX compliant code. I tried this code, but here I don't know what
    service name should I supply and how do supply the credentials and to which
    MBean. here is the test code that I wrote and ofcourse it doesn't work but
    any help from you guys will be apperecitated.
    import javax.management.*;
    public class WeblogicJMX {
    public static void main(String[] args) {
    try {
    MBeanServer mBeanServer =
    MBeanServerFactory.createMBeanServer("http://localhost:7001/");
    System.out.println(mBeanServer.getClass().getName());
    ObjectName objectName = new
    ObjectName("mydomain:service=WebLogicServer,server=myserver");
    ObjectInstance objectInstance =
    mBeanServer.createMBean("weblogic.management.MBeanHome.class", objectName);
    String className = objectInstance.getClassName();
    System.out.println("className = " + className);
    } catch (MalformedObjectNameException e) {
    e.printStackTrace();
    } catch (ReflectionException e) {
    e.printStackTrace();
    } catch (InstanceAlreadyExistsException e) {
    e.printStackTrace();
    } catch (MBeanException e) {
    e.printStackTrace();
    } catch (NotCompliantMBeanException e) {
    e.printStackTrace();
    Any help is greately appreciated.
    thanx in advance
    Daya Sharma

    sorry I think I missed my email address here it is
    [email protected]
    "bea news groups" <newsgroups.bea.com> wrote in message
    news:[email protected]..
    Hi All
    I am new to the JMX world and newer at accessing Weblogic MBeans. I don't
    want to use the weblogic specific classes like Environment and Helper
    because then my code won't be appserver neutral.
    Can you please provide me with an example to access weblogoc MBeans usinga
    fully JMX compliant code. I tried this code, but here I don't know what
    service name should I supply and how do supply the credentials and towhich
    MBean. here is the test code that I wrote and ofcourse it doesn't work but
    any help from you guys will be apperecitated.
    import javax.management.*;
    public class WeblogicJMX {
    public static void main(String[] args) {
    try {
    MBeanServer mBeanServer =
    MBeanServerFactory.createMBeanServer("http://localhost:7001/");
    System.out.println(mBeanServer.getClass().getName());
    ObjectName objectName = new
    ObjectName("mydomain:service=WebLogicServer,server=myserver");
    ObjectInstance objectInstance =
    mBeanServer.createMBean("weblogic.management.MBeanHome.class",objectName);
    String className = objectInstance.getClassName();
    System.out.println("className = " + className);
    } catch (MalformedObjectNameException e) {
    e.printStackTrace();
    } catch (ReflectionException e) {
    e.printStackTrace();
    } catch (InstanceAlreadyExistsException e) {
    e.printStackTrace();
    } catch (MBeanException e) {
    e.printStackTrace();
    } catch (NotCompliantMBeanException e) {
    e.printStackTrace();
    Any help is greately appreciated.
    thanx in advance
    Daya Sharma

  • Weblogic.management.ManagementRuntimeException, managing MBeans in Weblogic

    Exception caught: weblogic.management.ManagementRuntimeException: java.lang.NoSuchMethodError: javax.management.MBeanInfo.getAttributesI()[Ljavax/management/MBeanAttributeInfo[/b]
    [b]I have deployed the stateful ejb into the weblogic server 8.1 through the administration console and able to view it through the administration console. I am using the small program to get the information of the ejb i.e Managed bean through the program given in the
    http://edocs.bea.com/wls/docs81/jmx/basics.html#1121065
    The Program is as follows:import javax.naming.Context;
    import java.util.Set;
    import java.util.Iterator;
    import weblogic.jndi.Environment;
    import weblogic.management.MBeanHome;
    import weblogic.management.WebLogicMBean;
    import weblogic.management.WebLogicObjectName;
    public class ListAllMBeansInfo{
    ListAllMBeansInfo(){};
    public static void main(String args[]) {
    String url = "t3://localhost:7001";
    String username = "weblogic";
    String password = "weblogic";
    try {
    //Obtaining an MBeanHome Using JNDI
    System.setProperty("jmx.serial.form","1.0");
    Environment env = new Environment();
    env.setProviderUrl(url);
    env.setSecurityPrincipal(username);
    env.setSecurityCredentials(password);
    Context ctx = env.getInitialContext();
    MBeanHome home = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
    Set allMBeans = home.getAllMBeans();
    System.out.println("Size: "
    + allMBeans.size());
    for (Iterator itr = allMBeans.iterator(); itr.hasNext(); ) {
    WebLogicMBean mbean
    = (WebLogicMBean)itr.next();
    WebLogicObjectName objectName
    = mbean.getObjectName();
    System.out.println(
    objectName.getName() + " is a(n) " +
    mbean.getType());
    }catch(Exception e){
    System.out.println(e);
    I am getting the following error
    C:\Program Files\Java\jdk1.5.0_06\bin\javaw.exe -classpath C:\Program Files\Java\jdk1.5.0_06\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\deploy.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\javaws.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\jce.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\plugin.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\rt.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\ext\dnsns.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\ext\localedata.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\ext\sunjce_provider.jar;C:\Program Files\Java\jdk1.5.0_06\jre\lib\ext\sunpkcs11.jar;C:\dev\classes;C:\bea\weblogic81\server\lib\xqrl.jar;C:\bea\weblogic81\server\lib\xmlx.jar;C:\bea\weblogic81\server\lib\xbean.jar;C:\bea\weblogic81\server\lib\wlclient.jar;C:\bea\weblogic81\server\lib\certificate.war;C:\bea\weblogic81\server\lib\weblogic.jar;C:\bea\weblogic81\server\lib\jConnect.jar ListAllMBeansInfo
    Size: 617
    weblogic.management.ManagementRuntimeException: java.lang.NoSuchMethodError: javax.management.MBeanInfo.getAttributesI()[Ljavax/management/MBeanAttributeInfo;
    Process terminated with exit code 0It would be great if some one can help me
    Thanks In Advance,
    Durga Prasad.

    Hi,
    You could use cascading/MBeanServer federation to federate all your MBeans in
    a single MBeanServer. See for instance:
    http://blogs.sun.com/jmxetc/entry/federating_mbeanservers_with_opendmk
    [Note: if the MBeanServers are remote, rather than local, you will be able to use the
    CascadingServiceMBean and things will be easier].
    See also:
    http://weblogs.java.net/blog/emcmanus/archive/2007/08/combining_casca.html
    and:
    http://weblogs.java.net/blog/emcmanus/archive/2007/02/cascading_its_a_1.html
    Hope this helps,
    -- daniel
    JMX, SNMP, Java,etc...
    http://blogs.sun.com/jmxetc

  • Where to find weblogic.management package

    serverConfigInfo.java:3: package weblogic.management does not exist
    import weblogic.management.MBeanHome;
    I am getting the above error while excuting the code. from where should i import weblogic.management package?

    you should include the library that contains this package in your class path.
    search weblogic.jar or something like that in the weblogic library directories.
    in order to know whether the package needed is included in a jar file, open this latter with winzip and look for MBeanHome (in weblogic/management directory)
    hope that helps

  • Usage of weblogic.management.runtime.ServerRuntimeMBean

    Hi all,
    Does anyone knows how to use this mbean? How to
    use MBeanHome to get hold of this mbean, and use it to
    shutdown the server?
    My code segment is like following, and an InstanceNotFoundException is
    always thrown back. Any suggestion?
    Context ctx = new InitialContext();
    MBeanHome home = (MBeanHome)
    ctx.lookup("weblogic.management.adminhome");
    ServerRuntimeMBean server = (ServerRuntimeMBean) home.getMBean(new
    ObjectName("truetel:Type=ServerRuntime,Location=sleesvr,Name=sleesvr"));
    Any help will be appreciated,
    Lynch
    p.s. The code is within a timer class to shutdown itself in the proper time.
    The domain is "truetel" and the server name is "sleesvr".

    Please ignore the previous post. I've found the way anyway.
    Use home.getRuntimeMBean("sleesvr", "ServerRuntime");
    "Lynch" <[email protected]> ¼¶¼g©ó¶l¥ó
    news:[email protected]..
    Hi all,
    My code segment is like following, and an InstanceNotFoundException is
    always thrown back. Any suggestion?
    Context ctx = new InitialContext();
    MBeanHome home = (MBeanHome)
    ctx.lookup("weblogic.management.adminhome");
    ServerRuntimeMBean server = (ServerRuntimeMBean) home.getMBean(new
    ObjectName("truetel:Type=ServerRuntime,Location=sleesvr,Name=sleesvr"));

  • Error while starting weblogic Managed Server

    Hi ,
    I am new to SOA 11g. I installled the latest version(11.1.1.4) of all the components.I started web logic and able to login into Admin Console but I have a problem
    while starting Managed Server.It gives me an error saying
    <Feb 2, 2011 2:01:29 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 17.0-b17
    from Sun Microsystems Inc.>
    <Feb 2, 2011 2:01:30 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: Unable to obtain lock on C:\Oracle\Middleware\user_projects\domains\fmw_domain\servers\AdminServer\tmp\AdminServer.lok.
    Server may already be running
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)
    at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
    at weblogic.Server.main(Server.java:71)>
    <Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Feb 2, 2011 2:01:30 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Can anyone help ?
    Regards,
    Vikas Manchanda
    Edited by: 829347 on Feb 2, 2011 12:48 AM

    How are you starting the managed server? Is it a new install? The error suggests that the managed server is already running. You could check the windows task manager to see if there is a Java process running (or two if managed and admin server is on the same machine)
    Damien

  • The Oracle MapViewer brings the WebLogic Managed Server to crash

    Problem Description: The Oracle MapViewer brings the WebLogic Managed Server to crash, when we call a GetMap-Request with wrong Coordinates.
    This was found out for the SRS=EPSG:25833. Example:
    http://igdb-qm-svra1.blva.bayern.de:8080/mapviewer/wms?
    REQUEST=getMap&
    Version=1.1.1&
    LAYERS=&
    FORMAT=image/png&
    TRANSPARENT=false&
    STYLES=&
    Datasource=igvert_alkis_wms&
    basemap=AT_WMS_TN-KOMPLETT&
    SRS=EPSG:25833&
    BBOX=3.32358690717E7,5529425.0143,3.32369088846E7,5530464.8272&
    WIDTH=500&
    HEIGHT=500&
    With the Enterprise Manager was also evaluated during and after a crash of Server the SQL-Statements.
    If the SQL statements executed on the database itself, it takes a few seconds after a correct answer returns.
    I know that have the look for the EPSG coordinate as follows:
    BBOX=235869.071700,5529425.014300,236908.884600,5530464.827200&
    My question therefore: Why are these coordinates by the Oracle MapViewer approved and not caught? An Request with incorrect
    coordinates goes into a StuckThreads and then the ManagedServer crashed.
    In the appendix you will find the evaluation of the Enterprise Manager.
    I have tested the request with two different versions of Oracle MapViewer (Ver11_1_1_5_B110527 and Ver11_B100426). In both the same problem occurs on.
    I have also filed an SR.
    Best Regards
    Kerstin

    Hi,
    Can you confirm that you're trying to setup a managed server on another machine using the pack/unpack commands ?
    You might to want to take a look at that post.
    Clustering of 2 Physical server
    Hope that helps !
    Regards

  • Weblogic.management.server bound more than once?

    Sorry if I already posted this in cluster, but I realized that it should belong here instead....
    I have an admin server that does not belong in any cluster. I set up 2 managed server (app01,
    app02) targetted to "app cluster". I can start up app01 or app02 by itself, when when I start both
    up, I get the following message on both managed servers; the admin server, on the other hand, does
    not display any errors. Why are the managed servers trying to bind weblogic.management.server to
    jndi????
    <Apr 3, 2001 11:07:37 AM PDT> <Info> <Cluster> <Adding
    server -4094822875006454559S:fortran-1:[10085,10085,7002,7002,10085,7002,-1] to cluster view>
    <Apr 3, 2001 11:07:37 AM PDT> <Info> <Cluster>
    <Adding -4094822875006454559S:fortran-1:[10085,10085,7002,7002,10085,7002,-1] to the cluster>
    <Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
    the name weblogic.management.server in the jndi tree. The object you have bound
    weblogic.management.internal.RemoteMBeanServerImpl from fortran is non clusterable and you have
    tried to bind more than once from two or more servers. Such objects can only deployed from one
    server.>
    <Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
    the name weblogic.management.server in the jndi tree. The object you have bound
    weblogic.management.internal.RemoteMBeanServerImpl_WLStub from fortran-1 is non clusterable and you
    have tried to bind more than once from two or more servers. Such objects can only deployed from one
    server.>
    <Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
    the name weblogic.management.adminhome in the jndi tree. The object you have bound
    weblogic.management.internal.AdminMBeanHomeImpl from fortran is non clusterable and you have tried
    to bind more than once from two or more servers. Such objects can only deployed from one server.>
    <Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
    the name weblogic.management.adminhome in the jndi tree. The object you have bound
    weblogic.management.internal.AdminMBeanHomeImpl_WLStub from fortran-1 is non clusterable and you
    have tried to bind more than once from two or more servers. Such objects can only deployed from one
    server.>
    Gene

    Prasad diagnosed the problem. Look in clustering under the same title if you're interested!
    Gene
    "Gene Chuang" <[email protected]> wrote in message news:[email protected]...
    Sorry if I already posted this in cluster, but I realized that it should belong here instead....
    I have an admin server that does not belong in any cluster. I set up 2 managed server (app01,
    app02) targetted to "app cluster". I can start up app01 or app02 by itself, when when I startboth
    up, I get the following message on both managed servers; the admin server, on the other hand,does
    not display any errors. Why are the managed servers trying to bind weblogic.management.server to
    jndi????
    <Apr 3, 2001 11:07:37 AM PDT> <Info> <Cluster> <Adding
    server -4094822875006454559S:fortran-1:[10085,10085,7002,7002,10085,7002,-1] to cluster view>
    <Apr 3, 2001 11:07:37 AM PDT> <Info> <Cluster>
    <Adding -4094822875006454559S:fortran-1:[10085,10085,7002,7002,10085,7002,-1] to the cluster>
    <Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
    the name weblogic.management.server in the jndi tree. The object you have bound
    weblogic.management.internal.RemoteMBeanServerImpl from fortran is non clusterable and you have
    tried to bind more than once from two or more servers. Such objects can only deployed from one
    server.>
    <Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
    the name weblogic.management.server in the jndi tree. The object you have bound
    weblogic.management.internal.RemoteMBeanServerImpl_WLStub from fortran-1 is non clusterable andyou
    have tried to bind more than once from two or more servers. Such objects can only deployed fromone
    server.>
    <Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
    the name weblogic.management.adminhome in the jndi tree. The object you have bound
    weblogic.management.internal.AdminMBeanHomeImpl from fortran is non clusterable and you have tried
    to bind more than once from two or more servers. Such objects can only deployed from one server.>
    <Apr 3, 2001 11:07:38 AM PDT> <Error> <Cluster> <Conflict start: You tried to bind an object under
    the name weblogic.management.adminhome in the jndi tree. The object you have bound
    weblogic.management.internal.AdminMBeanHomeImpl_WLStub from fortran-1 is non clusterable and you
    have tried to bind more than once from two or more servers. Such objects can only deployed fromone
    server.>
    Gene

  • Weblogic.management.DeploymentException: Unmarshaller failed

    Hi,
    I'm facing an error when I deploy an EAR project to Oracle Weblogic Server 10gR3 in Eclipse (server view).
    I get the error message (as a popup):
    'Publishing to Oracle Server 10gR3 failed at localhost...' has encountered a problem.
    Module named 'xxxEAR' failed to deploy. See Errpr Log for more detail.
    Module named 'AvgiftshanteringEAR' failed to deploy. See Error Log view for more detail.
    weblogic.management.DeploymentException: Unmarshaller failed
    Exception received from deployment driver. See Error Log view for more detail.
    And the error in the Error Log view:
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1558)
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1338)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:795)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:615)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:508)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
    at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
    at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: weblogic.management.DeploymentException: Unmarshaller failed
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
    at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
    at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
    at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
    at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
    at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
    at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:88)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    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)
    Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
    at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
    at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:174)
    And this in the Console View:
    <2010-apr-23 kl 9:08 CEST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\Utveckling\svnProd\.metadata\.plugins\org.eclipse.core.resources\.projects\xxxEAR\beadep\EVis\xxxEAR/META-INF/application.xml of module xxxEAR. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
         at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
         at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:174)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
         at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:88)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         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)
    Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
         ... 27 more
    .>
    <2010-apr-23 kl 9:08 CEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean xxxEAR. Error - weblogic.management.DeploymentException: Unmarshaller failed.
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    <2010-apr-23 kl 9:08 CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1272006514452' for task '6'. Error is: 'weblogic.management.DeploymentException: Unmarshaller failed'
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    <2010-apr-23 kl 9:08 CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxEAR'.>
    <2010-apr-23 kl 9:08 CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    2010-apr-23 09:09:18 com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    2010-apr-23 09:09:18 com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    <2010-apr-23 kl 9:09 CEST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    This however does not occur when I deploy the EAR from the Weblogic Server Administration Console.
    Any ideas?
    //Luc
    Edited by: user13028996 on 2010-apr-23 00:15

    Maybe Eclipse is building/packaging application.xml with the wrong header.
    As soon as I build the EAR project, the changes I made are lost.
    That is why the Stacktrace seems to be the same as earlier.
    <2010-apr-23 kl 14:12 CEST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\Utveckling\svnProd\.metadata\.plugins\org.eclipse.core.resources\.projects\xxxEAR\beadep\EVis\AvgiftshanteringEAR/META-INF/application.xml of module xxxEAR. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
         at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
         at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:174)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
         at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:88)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         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)
    Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
         ... 27 more
    .>
    <2010-apr-23 kl 14:12 CEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean xxxEAR. Error - weblogic.management.DeploymentException: Unmarshaller failed.
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    <2010-apr-23 kl 14:12 CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1272024728473' for task '2'. Error is: 'weblogic.management.DeploymentException: Unmarshaller failed'
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    <2010-apr-23 kl 14:12 CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxEAR'.>
    <2010-apr-23 kl 14:12 CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.management.DeploymentException: Unmarshaller failed
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         Truncated. see log file for complete stacktrace
    com.bea.xml.XmlException: failed to load java type corresponding to e=application@http://java.sun.com/xml/ns/javaee/application_5.xsd
         at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
         at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
         Truncated. see log file for complete stacktrace
    >
    //Luc

  • EJB 3.0, BC4J and weblogic managed server

    Hi, I've got a problem using EJB 3.0 with a BC4J Application module in a weblogic managed server.
    My bean is a stateless session bean that use BC4J for database transaction.
    When I call the bean the first time, It returns de values I need, without problem. If I do the same call again, I always get "null". I deployed the same bean on the AdminServer, linking to the same DataSource, It works fine and I never got a null result.
    My application module is created insid my EJB abstract class by :
    _am = (BaseServiceImpl)Configuration.createRootApplicationModule(adfModel, adfConfiguration);*
    Where adfModel and adfConfiguration are configured through annotations in my EJB Implementation.
    In my abstract EJB, I have a methode with a +@PreDestroy+ method like that :
    +@PreDestroy+
    *protected void releaseModele() {*
    *if (_am != null) {*
    Configuration.releaseRootApplicationModule(_am, false);
    _am = null;*
    My Data Source on the server is defined as Supporting Global Transaction, one-phase commit. I activated the BC4J Logs on the server to see what was going on and I see that the JDBC seems to close after the first call :
    *** closing jdbc connection now **** (weblogic.jdbc.wrapper.JTSConnection_oracle_jdbc_driver_T4CConnection@0)
    And that is when I've got the error on the server :
    oracle.jbo.InvalidObjAccessException: JBO-25036: An invalid object operation was invoked on type View Object with name AppModAD
    So, my JDBC connection seems to close somewhere beetween the first and the second call, but only on a managed server... Someone has ever encountered a problem like that?
    Maybe there is something with the configuration of a datasource on a managed server? Or with the lifecycle of an

    The solution was to NOT have glabal transaction checked in the configuration of the data-source and "Failover Transaction State Upon Managed Release" uncked in the configuration of the Business component configuration.

  • Weblogic managed server crash and automatic restart on Solaris SPARC platform

    hi Everyone,
    We are facing a problem a problem with Weblogic managed server where the managed server crashes and automatically restarts (via nodemanager) on Solaris SPARC platform.
    The system info is as below:
    OS:                            Oracle Solaris 11.1 SPARC
      Copyright (c) 1983, 2012, Oracle and/or its affiliates.  All rights reserved.
                               Assembled 19 September 2012
    uname:SunOS 5.11 11.1 sun4v
      (T2 libthread)
    rlimit: STACK 8192k, CORE infinity, NOFILE 65536, AS infinity
    load average:1.04 0.52 0.32
    CPU:total 4 v9, popc, vis1, vis2, vis3, blk_init, cbcond, sun4v, niagara_plus
    Memory: 8k page, physical 16777216k(5930008k free)
    vm_info: Java HotSpot(TM) 64-Bit Server VM (23.25-b01) for solaris-sparc JRE (1.7.0_25-b11), built on May 15 2013 04:30:17 by "" with Sun Studio 12u1
    The pstack output of analyzing the core file is as below (for the particular thread, I can attach the entire output of pstack if required):
    --- called from signal handler with signal 11 (SIGSEGV) ---
    ffffffff7ec1a7c4 memcpy%sun4v-hwcap3 (103d34720, 10a7e7710, 108ae1060, 6300, 0, ffffffff5f66394b) + 990
    ffffffff36102fa4 ZIP_GetEntry (103d34720, ffffffff636f66a4, bd, 103d347f0, a26f1c, 2f) + e4
    ffffffff36103440 Java_java_util_zip_ZipFile_getEntry (2b, ffffffff636f66a4, 103d34720, ffffffff636f6b70, 2b, 1) + a8
    ffffffff7586ac1c * *java/util/zip/ZipFile.getEntry(J[BZ)J [compiled]
    ffffffff75b61b58 * *java/util/zip/ZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; [compiled] +39 (line 606)
    ffffffff75b61b58 * *java/util/jar/JarFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry;+3 (line 452)
    ffffffff75b61b58 * *weblogic/utils/classloaders/ZipClassFinder.getSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source;+36 (line 75)
    ffffffff75b6eb84 * *weblogic/utils/classloaders/JarClassFinder.getSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +6 (line 100)
    ffffffff75a40938 * *weblogic/utils/classloaders/AbstractClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +74 (line 58)
    ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
    ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
    ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
    ffffffff75806d10 * weblogic/application/utils/CompositeWebAppFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source;+5 (line 176)
    ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
    ffffffff75976c88 * *weblogic/utils/classloaders/MultiClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source; [compiled] +30 (line 114)
    ffffffff75806d10 * weblogic/utils/classloaders/CodeGenClassFinder.getClassSource(Ljava/lang/String;)Lweblogic/utils/classloaders/Source;+43 (line 48)
    ffffffff75806d10 * weblogic/utils/classloaders/GenericClassLoader.findLocalClass(Ljava/lang/String;)Ljava/lang/Class;+87 (line 571)
    ffffffff75806d10 * weblogic/utils/classloaders/GenericClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;+117 (line 515)
    ffffffff75806d10 * weblogic/utils/classloaders/ChangeAwareClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class;+60 (line 121)
    ffffffff75a465c8 * *java/lang/ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class; [compiled] +71 (line 836)
    ffffffff75db42c0 * *java/lang/ClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class; [compiled] +4 (line 714)
    ffffffff75806d10 * weblogic/utils/classloaders/GenericClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class;+2 (line 358)
    ffffffff75806d10 * weblogic/utils/classloaders/ChangeAwareClassLoader.loadClass(Ljava/lang/String;)Ljava/lang/Class;+27 (line 83)
    ffffffff7580024c * StubRoutines (1)
    ffffffff3691f44c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (ffffffff636f7f98, 10234f000, 2, c, 2, 10) + 2f4
    ffffffff36e546c0 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_pnGSymbol_63pnGThread__v_ (ffffffff636f7f98, 1013e7748, 10234f000, 10011bf30, 100119ec0, 772d4ec08) + 1b8
    ffffffff3725bf0c __1cQSystemDictionaryTload_instance_class6FpnGSymbol_nGHandle_pnGThread__nTinstanceKlassHandle__ (105cb6100, 1013e7978, 10234f000, 102b6e500, 0, 1013e7748) + 494
    ffffffff3725a028 __1cQSystemDictionarybEresolve_instance_class_or_null6FpnGSymbol_nGHandle_3pnGThread__pnMklassOopDesc__ (105cb6100, 19dc00, 70, 10234f000, 70, 1013e7700) + ae0
    ffffffff37257800 __1cQSystemDictionaryPresolve_or_fail6FpnGSymbol_nGHandle_3bpnGThread__pnMklassOopDesc__ (105cb6100, 1013e76f0, 1013e76f8, 1, 10234f000, 1) + 290
    ffffffff368ba9dc __1cTconstantPoolOopDescNklass_at_impl6FnSconstantPoolHandle_ipnGThread__pnMklassOopDesc__ (10201b6e0, 1013e7978, 10234f000, 10201b6e0, 783cfb098, ffffffff37588000) + 264
    ffffffff36937380 __1cSInterpreterRuntimeE_new6FpnKJavaThread_pnTconstantPoolOopDesc_i_v_ (10234f000, 77548b730, 49, 10201b6e0, 1013e76e8, 10234f000) + b8
    ffffffff7581ab58 * com/jdedwards/base/logging/log4j/JdeLogger.warn(ILjava/lang/String;Ljava/lang/String;Ljava/lang/Object;Ljava/lang/Throwable;)V+14
    ffffffff75807bcc * com/jdedwards/system/security/proxy/SecurityServerProxyImpl.install(Ljava/util/Hashtable;)Lcom/jdedwards/system/security/proxy/SecurityServerProxyImpl;+30
    ffffffff75806d10 * com/jdedwards/system/security/proxy/SecurityServerProxyFactory.create(Ljava/util/Hashtable;)Lcom/jdedwards/system/security/SecurityServer;+1
    ffffffff75807898 * com/jdedwards/system/security/SecurityServerInstance.getInstance()Lcom/jdedwards/system/security/SecurityServer;+27
    ffffffff75806d10 * com/jdedwards/mgmt/security/UserManager.checkPassword(Ljava/lang/String;Ljava/lang/String;)Z+59
    ffffffff75806b24 * com/jdedwards/mgmt/security/UserManagerImpl.checkPassword(Ljava/lang/String;Ljava/lang/String;)Z+5
    ffffffff75806b24 * com/jdedwards/mgmt/security/SCFLoginModule.login()Z+481
    The output of the hs_err_pid1127.log file is as below:
    # A fatal error has been detected by the Java Runtime Environment:
    #  SIGSEGV (0xb) at pc=0xffffffff7ec1a544, pid=1127, tid=20
    # JRE version: 7.0_25-b11
    # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode solaris-sparc compressed oops)
    # Problematic frame:
    # C  [libc.so.1+0x11a544]  memcpy%sun4v-hwcap3+0x710
    # Core dump written. Default location: /slot/ems9437/appmgr/Oracle/Middleware/user_projects/domains/smc_domain/core or core.1127
    # If you would like to submit a bug report, please visit:
    #   http://bugreport.sun.com/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    ---------------  T H R E A D  ---------------
    Current thread (0x000000010294d000):  JavaThread "[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon [_thread_in_native, id=20, stack(0xffffffff62f00000,0xffffffff63000000)]
    siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0xffffffff5f6ce000
    I ran the suspect code which i believed was causing the issue as a standalone Java program using the same Java executable and it worked fine without any crash.
    Appreciate any inputs / discussion / feedback / thoughts on this topic.
    Good day.

    I just wanted to throw in one more thought.  I have also seen that there is a restart=true parameter.  Maybe if we set this to true, and just issue the command to shut down the server in the script, the managed server will restart on its own. 
    Would greatly appreciate any advice!

  • Having problems starting Weblogic Managed Server

    Hi,
    I am new to WebLogic and I was looking at the webservices examples in samples dir and I took the example and just moved it to one of my currently deployed Web Application folder and changed the dir strutcure instead of the samples dir strutcure, compiled and deployed as standalone Application(not as part of my currently deployed Web App). It worked fine.
    Then since there would be a need for reuse of lot of the current Web App. in the web services we are trying to implement, I tried to put the ear that got created in the WEB-INF/lib of the currently deployed exploded dir. It was pretty dumb to put the ear there, just thought, worst case it wont work, I thought I could pull the ear out of there. But seems like this changed the entire config.xml and ever since that my admin server got changed to myserver, I corrected all the problems with the admin server and admin server and node server they come up just fine. When trying to bring up Managed server, I get the following excpetion
    Jul 16, 2004 4:00:37 PM EDT> <Debug> <HTTP> <BEA-101158> <Exception thrown while loading epic_dev: java.lang.NullPointerException
    java.lang.NullPointerException
         at weblogic.utils.enumerations.FileEnumeration.getNextFile(FileEnumeration.java:155)
         at weblogic.utils.enumerations.FileEnumeration.hasMoreFiles(FileEnumeration.java:102)
         at weblogic.utils.enumerations.FileEnumeration.hasMoreElements(FileEnumeration.java:134)
         at weblogic.utils.jars.ExplodedJarFile$1.hasNext(ExplodedJarFile.java:112)
         at weblogic.utils.classloaders.ExtractionHelper.extractClassFiles(ExtractionHelper.java:117)
         at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5119)
         at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:4991)
         at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:560)
         at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:511)
         at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:594)
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:623)
         at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:2896)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1532)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
         at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
         at weblogic.Server.main(Server.java:32)
    >
    <Jul 16, 2004 4:00:37 PM EDT> <Info> <Deployer> <BEA-149061> <Module epic_dev of application appsdirepic_dev_dir failed to transition from unprepared to prepared on server betsy_dev.>
    <Jul 16, 2004 4:00:37 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application appsdirepic_dev_dir due to error weblogic.management.ApplicationException: prepare failed for epic_dev
    Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
    weblogic.management.ApplicationException: prepare failed for epic_dev
    Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
         at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
         at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
         at weblogic.Server.main(Server.java:32)
    >
    Could someone help me with resolving this.(This is only the dev machine, I played thannkfully!).
    And also would like to get suggestions on setting up the new webserverces that we are trying to do. If I need to reuse lot of class files from current appl., how do i go about implementing this webservice? Should this be part of the existing application? or Web service could be a separate application and somehow we could look at the web app which is in the same domain.
    Any help is appreciated.
    Thanks
    Anna

    There was an access problem in the application I was trying to deploy and it had nothing to do with EAR file, once the access problem is taken care of, I could deploy the app just fine.

  • Oracle WebLogic Server 10.3.6: weblogic.management.ManagementException

    Error:
    There are 1 nested errors:
    weblogic.management.ManagementException: Unable to obtain lock on /export/home/oracle/mdw4/user_projects/domains/base_domain/servers/AdminServer/tmp/AdminServer.lok. Server may already be running at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:206)
      at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:67)
      at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
      at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
      at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
      at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
      at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
      at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
      at weblogic.Server.main(Server.java:71)
    >
    <Jan 2, 2014 4:20:35 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jan 2, 2014 4:20:35 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jan 2, 2014 4:20:35 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Solution:
    1.Delete file:
    /export/home/oracle/mdw4/user_projects/domains/base_domain/servers/AdminServer/tmp/AdminServer.lok, and re-start weblogic.
    2.Restart test machine(reboot) and re-start weblogic.

    Hi,
    If you have a back then restore the below file back and then try to start weblogic:
    \Oracle\Middleware\user_projects\domains\<domain_name>\config\config.lok
    Thanks,
    Sharmela

  • Weblogic Managed Server Error- JavaEE agent test failed in ODI

    Hi All,
    Please help wit the issue below !!
    Versions: ODI 11.1.1 and Weblogic 11g Release1 10.3.3.
    Server : Windows 2003 server ,32-bit OS.
    ->Able to connect the Standalone agent succesfully .
    Issue : In Weblogic ,the admin server is connecting without error . But when i start the Managed server"odi_server1" we found the major error occuring while connecting to the Master Repository . Pasted below the Error log .
    Please help!!
    ####<Mar 23, 2011 3:58:16 PM IST> <Error> <Deployer> <admin-3fqjbc1oo> <odi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1300876096336> <BEA-149231> <Unable to set the activation state to true for the application 'oraclediagent'.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
    ODI-1404: Agent OracleDIAgent start failure: an authentication error occurred while connecting to the master repository,
    at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    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.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1514)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    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.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: ODI-1404: Agent OracleDIAgent start failure: an authentication error occurred while connecting to the master repository,
    at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    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.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Thanks
    Kenny

    Hi Kenny,
    This error seems to indicate the credentials you've specified for the master repo are not working. Either ensure the login works at the repo, or rerun the installer and specify a set of known good credentials there.
    Regards,
    Robb Salzmann

Maybe you are looking for

  • Lightroom 5.7 Installer Fails on Win 8.1 - Windows compatibility reports incompatible

    Have had a case open since 15.2 and getting nowhere (0186366824). Was wondering if anybody here has encountered this issue and resolved? New PC, clean install of Windows 8.1. My old 3.6 version of LR returned an installer failure and was advised it w

  • What is the change occured by using the package in select statement

    Hi all, Can some one please tell me using the following package in the select statement of the view does it restricts the data or fetches the data what is the change occurred using the package for fetching the date column hr_discoverer.check_end_date

  • Batch split in Idoc DESADV.DELVRY01

    Hi, my scenario is non-SAP --> xi --> SAP for dispatch notifications. The sender system provides batch information on line item level, sometimes with batch split. I am looking for a possibility to post the dispatch advice in R/3 with batch split. I a

  • VLD-1111

    Has anyone else received this message? VLD-1111 The mapping cannot be generated due to operators requiring different code languages. For mapping code generation, the generated language needs to be the same for every operator in the mapping. Check the

  • Photoshop CS3 and illustrator won't let me save

    I have photoshop and illistrator cs3 for Windows XP.  Both of the programs were running fine for over 1-2 years, but last week when I try to save something, the save dialog pops up for less than 1/2 a second, disappears and then freezes the program.