Errors WLS-WLE

Hello, i have wls5.1 as client and wle5.1 as server through rmi over iiop.
There are client side jsp and class java and server side ejb.
I've problems with the return on client
Have you any ideas?
I think it is a serialization problem
The log which i received is:
java.rmi.UnmarshalException: Weblogic RemoteException
(weblogic.rmi.UnmarshalException)
remapped from:weblogic.rmi.UnmarshalException: Unmarshalling return
- with nested exception:
[java.io.InvalidClassException: weblogic.rmi.extensions.Stub;
Local class not compatible:
stream classdesc serialVersionUID=4411472764545809308
local class serialVersionUID=7984764149773708117];
nested exception is:
     weblogic.rmi.UnmarshalException: Unmarshalling return
     - with nested exception:
[java.io.InvalidClassException: weblogic.rmi.extensions.Stub;
Local class not compatible: stream classdesc
serialVersionUID=4411472764545809308 local class
serialVersionUID=7984764149773708117]
java.io.InvalidClassException: weblogic.rmi.extensions.Stub;
Local class not compatible: stream classdesc serialVersionUID=4411472764545809308
local class serialVersionUID=7984764149773708117
at java.io.ObjectStreamClass.validateLocalClass
(ObjectStreamClass.java:438)
at java.io.ObjectStreamClass.setClass(ObjectStreamClass.java:482)
at java.io.ObjectInputStream.inputClassDescriptor
(ObjectInputStream.java:785)

Hello, i have wls5.1 as client and wle5.1 as server through rmi over iiop.
There are client side jsp and class java and server side ejb.
I've problems with the return on client
Have you any ideas?
I think it is a serialization problem
The log which i received is:
java.rmi.UnmarshalException: Weblogic RemoteException
(weblogic.rmi.UnmarshalException)
remapped from:weblogic.rmi.UnmarshalException: Unmarshalling return
- with nested exception:
[java.io.InvalidClassException: weblogic.rmi.extensions.Stub;
Local class not compatible:
stream classdesc serialVersionUID=4411472764545809308
local class serialVersionUID=7984764149773708117];
nested exception is:
     weblogic.rmi.UnmarshalException: Unmarshalling return
     - with nested exception:
[java.io.InvalidClassException: weblogic.rmi.extensions.Stub;
Local class not compatible: stream classdesc
serialVersionUID=4411472764545809308 local class
serialVersionUID=7984764149773708117]
java.io.InvalidClassException: weblogic.rmi.extensions.Stub;
Local class not compatible: stream classdesc serialVersionUID=4411472764545809308
local class serialVersionUID=7984764149773708117
at java.io.ObjectStreamClass.validateLocalClass
(ObjectStreamClass.java:438)
at java.io.ObjectStreamClass.setClass(ObjectStreamClass.java:482)
at java.io.ObjectInputStream.inputClassDescriptor
(ObjectInputStream.java:785)

Similar Messages

  • Error WLS 10901 - when I add prompt in query from SAP in QAAWS

    Hello,
    I am accessing a Universe who's source is SAP -BEX Query. When I add a charecteristics and key figure I get data, however when I add a prompt or filter condition to my query in QAAWS - I get an error. I tried the same in Live Office and get the same error when I add the prompt  in the query.
    Error: WLS 10901 - getdocument information- A database error occurred - Error in MDData - Get_Leading_Column_data(see long text) --
    Why does this happen when I add a prompt to the query?

    HI Abhi,
    The Issue seem to be not from BO Universe. Can you please go and check the data at Bex report and to apply same condition over there.
    This might help us to track where exactly the error is happening.
    Since the flow is from Cubes to Bex Queries to Universe to QaaWS or Weni Reports.
    So its always better to track the data flow from source. In our scenario its Bex.
    Hope this may help you now and in future.
    Regards,
    AnjaniKumar C.A.

  • WLS - WLE Connections and Transactions in multithreaded

    Hi .
    We have a legacy system which was based on Tuxedo and now move to WLE
    (4.0)
    For our Internet applications we use WLS (4.03) as application server in
    top of the legacy system.
    We have problems trying to run more than one transaction on the WLS
    which propagate to the WLE .
    Looking at documentation we didn't understood how should we deal with
    more than one client on the WLS . Each client should have its own
    transaction and they should run simulstanly .
    We only succeded when we synchronize the threads (Run just one thread
    which get the transaction use it and then uses bt.destroy_current()
    before activating the next thread to do the same)
    It seems that the documantation in the WLE and WLS don't fit together .
    Has someone use WLS-WLE connectivity with multiple clients/threads.
    Can someone tell me how to use the Bootstrap object(destroy current?)
    and the Transaction Control (begin , suspend, resume, commit) in order
    to make it works.
    Regards

    I would strongly suggest that you not use WLE 4.0 which is rather old (4.2,
    5.0.1 and 5.1 have all since been released), but move to the newest version
    of WLE which is WLE 5.1.
    WLS 4.0 is also an old release.
    I am not sure how long these 2 releases will be supported, so the customer
    should upgrade to the latest of both WLE and WLS.
    Shlomo Rothschild wrote:
    Hi .
    We have a legacy system which was based on Tuxedo and now move to WLE
    (4.0)
    For our Internet applications we use WLS (4.03) as application server in
    top of the legacy system.
    We have problems trying to run more than one transaction on the WLS
    which propagate to the WLE .
    Looking at documentation we didn't understood how should we deal with
    more than one client on the WLS . Each client should have its own
    transaction and they should run simulstanly .
    We only succeded when we synchronize the threads (Run just one thread
    which get the transaction use it and then uses bt.destroy_current()
    before activating the next thread to do the same)
    It seems that the documantation in the WLE and WLS don't fit together .
    Has someone use WLS-WLE connectivity with multiple clients/threads.
    Can someone tell me how to use the Bootstrap object(destroy current?)
    and the Transaction Control (begin , suspend, resume, commit) in order
    to make it works.
    Regards

  • ORA-00060: deadlock detected - false error in WLE

    Hi,
    We are experiencing intermittent ORA-00060 errors at commit phase of XA
    global transactions in WLE 5.1 (patch 63). Essentially, we tracked this to
    an Oracle issue which was supposed to be fixed in Oracle 8.1.7. However, it
    appears to still happen. The problem only occurs when two or more XA
    participants attempt to commit around the same time. The two transactions
    are totally separate but somehow, things get mixed up. I am wondering if
    anyone has seen this before and if so, what workarounds have been put in
    place.
    Thanks
    Dermot

    The first thing IMO is to look at the isolation level ... Oracle has to
    manage a much larger amount of data per tx if the isolation level is
    serializable for example.
    Peae,
    Cameron Purdy
    Tangosol, Inc.
    Clustering Weblogic? You're either using Coherence, or you should be!
    Download a Tangosol Coherence eval today at http://www.tangosol.com/
    "Dermot Reynolds" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    We are experiencing intermittent ORA-00060 errors at commit phase of XA
    global transactions in WLE 5.1 (patch 63). Essentially, we tracked this to
    an Oracle issue which was supposed to be fixed in Oracle 8.1.7. However,it
    appears to still happen. The problem only occurs when two or more XA
    participants attempt to commit around the same time. The two transactions
    are totally separate but somehow, things get mixed up. I am wondering if
    anyone has seen this before and if so, what workarounds have been put in
    place.
    Thanks
    Dermot

  • "timeout value is negative" error, WLS 6.1 on W2K

    I temporarily bumped the JTA TimeoutSeconds in the config.xml to 600000000 to handle a huge transaction, and ended up with the following (see below). I understand the upper limit for this property is much higher than this, but the error went away when I put the TimeoutSeconds value back down to 600. I'm running WLS 6.1 SP 5 on a single-processor W2K machine. Any ideas? Thanks in advance.
    <Exception received while handling message in XmlListener 0000000000000134.QueryQueue:268.
    java.lang.IllegalArgumentException: timeout value is negative
    at java.lang.Object.wait(Native Method)
    at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManager.java:501)
    at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258)
    at weblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEntityManager.java:165)
    at weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:220)
    at weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:199)
    at weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:117)
    at weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at

    I temporarily bumped the JTA TimeoutSeconds in the config.xml to 600000000 to handle a huge transaction, and ended up with the following (see below). I understand the upper limit for this property is much higher than this, but the error went away when I put the TimeoutSeconds value back down to 600. I'm running WLS 6.1 SP 5 on a single-processor W2K machine. Any ideas? Thanks in advance.
    <Exception received while handling message in XmlListener 0000000000000134.QueryQueue:268.
    java.lang.IllegalArgumentException: timeout value is negative
    at java.lang.Object.wait(Native Method)
    at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManager.java:501)
    at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258)
    at weblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEntityManager.java:165)
    at weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:220)
    at weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:199)
    at weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:117)
    at weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at

  • EJB in WLS - CORBA and EJB on WLE

    I have a client who is looking to attach a C++ client to their WLE
    system, and, since
    they now have WLS and WLE thanks to v. 5.1, they want to start moving
    EJBs to the
    WLS platform. The issue is this.
    What if any are the issues regarding communicating between CORBA objects
    on WLE
    TO EJBs on WLS? I noticed that the illustrations always show the
    communication coming
    from the WLS side to the WLE side, but this client will be connected
    directly to the WLE
    platform, and wanting to access services on WLS.
    Any issues, directions to documentation, or other advice regarding this
    issue?
    Thanks in advance,
    Maffy
    [maffy.vcf]

    can anyone give code example for accessing WLS-EJB from WLE corba client.
    louc wrote:
    Interesting how things can be interpreted. What we need is direct input
    from engineering on this.
    In studying the only direct source of information we have... (the docs...
    and ass-u-me'ing that the docs are correct) it appears that we can have a
    CORBA object in WLE access a EJB in WLS through RMI/IIOP as long as the
    parameter passing is kept to primitive data types. Any attempt to use the
    'Object-by-Value' feature of CORBA 2.3 will result in a error because WLE
    5.1 does not support passing 'Object-by-Value' at this time.
    So to answer Maffy's question... yes a WLE CORBA client can access a WLS EJB
    service through RMI over IIOP.
    -- Lou Caraballo
    Sr. Systems Engineer
    BEA Systems Inc., Denver Telco Group
    719-332-0818 (cell)
    720-528-6073 (denver)
    Robert Patrick <[email protected]> wrote in message
    news:[email protected]...
    The issue is that WLE does not yet support the RMI/IIOP standard (since itdoes not yet support
    Objects by Value) not that the RMI/IIOP support in WLS 5.1 (as of SP3)does not support
    bi-directional communication.
    Papaya Head wrote:
    so, you are saying bi-directional communication is not supported... can
    you tell me what
    rmi/iiop is for?
    Thanks.
    Maffy Finnerty wrote:
    Okay, found a work around thanks to Deepak Sharma (THANK YOU,
    DEEPAK!!) in the BEA
    East office.
    What my customer is going to have to do for now - until, as Will Lyonspointed out, the
    bi-directional
    communication is supported - is to build a Java "client" process onWLE that communicates
    with the
    RMI/EJB/Servlet process on WLS.
    Deepak suggested that the best way, since they are a CORBA shop tryingto move to Java,
    would be to have the C++ client talking to a CORBA/C++ object on WLEthat calls
    a CORBA/Java object on WLE that acts as a client to WLS and accessesthe services of the
    Java object on that server.
    Another option would be to have the CORBA/C++ object on WLE use theJNI API to call a Java
    object
    on WLE that acts as a client to WLS and accesses the Java servicerunning there. There may
    be better
    performance from CORBA/C++ to CORBA/Java, though, so that was Deepak'sfirst choice.
    Maffy
    Papaya Head wrote:
    you can also find an example in the WLS5.1 docs that includes a code
    segment from C++
    client of the RMI-IIOP hello example.
    Will Lyons wrote:
    The example application with C++ CORBA objects calling EJBs on a
    Java Server refers
    to C++ CORBA objects on the WLE T-Engine calling EJBs on the WLET-Engine. That
    interoperability capability is supported, but it is not possibleto call the J-Engine
    from the T-Engine in WLE 5.1. The primary usage model assumed inWLE 5.1 is calling
    the WLE T-Engine from the J-Engine (or from WLS).
    Will
    Papaya Head wrote:
    my understanding of your question is: you want some feature that
    allows CORBA
    objects to talk to EJB objects on WLS.
    WLS5.1 has a new feature: RMI/IIOP, it's probably the featureyou want.
    before WLS5.1, CORBA components couldn't talk to EJB componentsdirectly, but you
    could make it happen by building a bridge from CORBA objects toEJB components on
    WLS. that's probably what the references you read are talkingabout...
    Maffy Finnerty wrote:
    We haven't even gotten that far yet, re: transactions. Right
    now the issue is
    having an
    in-house client (C++) connected to WLE but accessing services(EJBs) on WLS.
    No talk
    of transactions has occurred, yet.
    However, I just found some conflicting information. I found areference to
    building the
    simpapp application to connect C++ objects on a CORBA serverto EJBs on a Java
    Server,
    which, if I'm reading it correctly, translates to WLE to WLS.However, I also
    found a
    reference to bidirectional interoperability that said that,for now, the
    T-Engine could not
    (WLE) could NOT invoke services on the J-Engine (WLS) but thatservices on the
    T-Engine
    (WLE) could BE invoked from requesters on the J-Engine (WLS).So, color me
    confused.
    maffy
    Papaya Head wrote:
    the first question that comes to my mind is:
    can transaction run across components on WLE and components
    on WLS? I don't
    think it can...
    Maffy Finnerty wrote:
    I have a client who is looking to attach a C++ client to
    their WLE
    system, and, since
    they now have WLS and WLE thanks to v. 5.1, they want tostart moving
    EJBs to the
    WLS platform. The issue is this.
    What if any are the issues regarding communicating betweenCORBA objects
    on WLE
    TO EJBs on WLS? I noticed that the illustrations alwaysshow the
    communication coming
    from the WLS side to the WLE side, but this client will beconnected
    directly to the WLE
    platform, and wanting to access services on WLS.
    Any issues, directions to documentation, or other adviceregarding this
    issue?
    Thanks in advance,
    Maffy

  • Getting error while starting Managed server in clustered environment

    Hi All,
    I created a cluster in weblogic 9.2 and two manged servers under that cluster through WLST scripts.
    I started Node manager through connecting WLST and now when i am starting the managed servers its giving the following error :
    wls:/Dist_3/serverConfig> start('managed1','Server')
    Starting server managed1 ....NMProcess: <Jan 30, 2009 2:57:27 PM> <Warning> <I/O
    error while reading domain directory: java.io.FileNotFoundException: Domain dir
    ectory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)>
    NMProcess: java.io.FileNotFoundException: Domain directory 'C:\bea\weblogic92\co
    mmon\bin' invalid (domain salt file not found)
    NMProcess: at weblogic.nodemanager.server.DomainManager.initialize(DomainMa
    nager.java:80)
    NMProcess: at weblogic.nodemanager.server.DomainManager.<init>(DomainManage
    r.java:52)
    NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServe
    r.java:242)
    NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java
    :212)
    NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.jav
    a:105)
    NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
    NMProcess: at java.lang.Thread.run(Thread.java:595)
    NMProcess:
    I/O error while reading domain directory: java.io.FileNotFoundException: Domain
    directory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1250, in start
    WLSTException: 'Error occured while performing start : Error starting the server
    Error occured while performing start : Server with name managed1 failed to be st
    arted Use dumpStack() to view the full stacktrace'
    wls:/Dist_3/serverConfig> start('managed2','Server')
    Starting server managed2 ....NMProcess: <Jan 30, 2009 3:05:51 PM> <Warning> <I/O
    error while reading domain directory: java.io.FileNotFoundException: Domain dir
    ectory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)>
    NMProcess: java.io.FileNotFoundException: Domain directory 'C:\bea\weblogic92\co
    mmon\bin' invalid (domain salt file not found)
    NMProcess: at weblogic.nodemanager.server.DomainManager.initialize(DomainMa
    nager.java:80)
    NMProcess: at weblogic.nodemanager.server.DomainManager.<init>(DomainManage
    r.java:52)
    NMProcess: at weblogic.nodemanager.server.NMServer.getDomainManager(NMServe
    r.java:242)
    NMProcess: at weblogic.nodemanager.server.Handler.handleDomain(Handler.java
    :212)
    NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.jav
    a:105)
    NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:66)
    NMProcess: at java.lang.Thread.run(Thread.java:595)
    NMProcess:
    I/O error while reading domain directory: java.io.FileNotFoundException: Domain
    directory 'C:\bea\weblogic92\common\bin' invalid (domain salt file not found)
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1250, in start
    WLSTException: 'Error occured while performing start : Error starting the server
    Error occured while performing start : Server with name managed2 failed to be st
    arted Use dumpStack() to view the full stacktrace'
    wls:/Dist_3/serverConfig>

    hi kartheek,
    i think u just missed some of steps while starting managed server using nodemanager in WLST.
    If u dont mind i'm sending some of steps just check it out. Once u try the same steps.
    1.start the ADMIN SERVER
    2.start the WLST
    java weblogic.WLST
    3.Connect to AdminServer
    connect('username',password','t3://adminhost:listenport')
    example: connect('weblogic','weblogic','t3://localhost:7001')
    4.start the nodemanager in WLST
    startNodeManager()
    5.connect to nodemanager
    nmConnect('username','password','nodemanagerhost',
    'nodemanagerlistenport','domainname','path to domain')
    example: nmConnect('weblogic','weblogic','localhost','5556','base_domain'
    'C:/bea/user_projects/domains/base_domain')
    6.start the managed server in WLST
    start('managedservername','Type','t3://managedhost:listenport')
    example:start('man1','Server','t3://localhost:7003')
    7.If u want to start cluster in WLST
    start('clustername','Type')
    example: start('cluster1','Cluster')
    If u want to start managed in Cluster u follow STEP-6 only
    regards
    abhi

  • Error while executing 'cloneDeployment() command in WLST

    getting error in ‘cloneDeployments’ command ( please find below error details)
    Syntax for the command,
    wls:/offline> cloneDeployments( '/my_path/user_templates/domains/my_domain', 'sourceServer','destinationServer', 'false')
    cloneDeployments('C:/Oracle/Middleware/user_projects/domains/soa_domain','Manage21','Manage31','false')
    ##cloneDeployments(r.'/C:\Oracle\Middleware\user_projects\domains\soa_domain','AdminServer','Manage42','false')
    Error :
    wls:/offline> cloneDeployments('C:/Oracle/Middleware/user_projects/domains/soa_domain','Manage21','Manage31','False')
    Traceback (innermost last):
    File "<console>", line 1, in ?
    NameError: cloneDeployments
    when user r'./ option..
    wls:/soa_domain/serverConfig> cloneDeployments(r.'/C:\Oracle\Middleware\user_projects\domains\soa_domain','Manage21','Manage31','false')
    Traceback (innermost last):
    (no code object) at line 0
    File "<console>", line 1
    cloneDeployments(r.'/C:\Oracle\Middleware\user_projects\domains\soa_doma
    in','Manage21','Manage31','false')
    ^
    SyntaxError: invalid syntax
    Please reply if you know the solution.

    Do:
    configToScript('YOU_WLS_DOMAIN_DIR','/export/third-party/etsbea/home/etsbea/tests/wlst/')

  • Error when running configToScript command in WLST

    Hi,
    I'm trying to get a WLST script for my existing server. I read about the configToScript command, but when I run it, I get an error
    wls:/nps_pt_92/serverConfig> configToScript('/export/third-party/etsbea/home/etsbea/tests/wlst/')
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 1547, in configToScript
    WLSTException: 'Error occured while performing configToScript : File not found: /export/third-party/etsbea/home/etsbea/tests/wlst/config/config.xml/export/third-party/etsbea/home/etsbea/tests/wlst/config/config.xml (No such file or directory) Use dumpStack() to view the full stacktrace'
    This is odd because I created a directory named "config" within "/export/third-party/etsbea/home/etsbea/tests/wlst/" but still no love. Any ideas what is going on?
    Thanks, - Dave

    Do:
    configToScript('YOU_WLS_DOMAIN_DIR','/export/third-party/etsbea/home/etsbea/tests/wlst/')

  • ConfigToScript() error

    Good day,
    I am trying to use the configToScript() function in WLS 9.2.1 and I keep hitting issues with it not reading the configuration. I want to use it with WLP, WLI and ALSB domains but even when I hit a vanilla WLP domain (just created it, nothing deployed) I get the following error:
    wls:/offline> configToScript('C:/bea/user_projects/domains/wlp1_domain','D:/dev/
    test/wlst/wli',createDeploymentScript='true')
    configToScript is loading configuration from C:\bea\user_projects\domains\wlp1_d
    omain\config\config.xml ...
    <15-Aug-2007 11:40:43 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : WseeJmsModule.>
    <15-Aug-2007 11:40:43 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : pf-proliferation-jms.>
    <15-Aug-2007 11:40:43 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : cgDataSource.>
    <15-Aug-2007 11:40:43 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : cgDataSource-nonXA.>
    <15-Aug-2007 11:40:43 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : samplesDataSource.>
    <15-Aug-2007 11:40:44 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : p13nDataSource.>
    <15-Aug-2007 11:40:44 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : portalDataSource.>
    <15-Aug-2007 11:40:44 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : portalDataSourceAlwaysXA.>
    <15-Aug-2007 11:40:44 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : portalDataSourceNeverXA.>
    Completed configuration load, now converting resources to wlst script...
    <15-Aug-2007 11:40:44 o'clock AM ADT> <Warning> <Management> <BEA-141230> <Could
    Not locate descriptor file for System Resource : WseeJmsModule.>
    weblogic.management.scripting.ScriptException: Error occured while performing co
    nfigToScript : Error getting the name for bean null Use dumpStack() to view the
    full stacktrace
            at weblogic.management.scripting.ExceptionHandler.handleException(Except
    ionHandler.java:51)
            at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.
    java:221)
            at weblogic.management.scripting.ConfigToScript.getName(ConfigToScript.j
    ava:863)
            at weblogic.management.scripting.ConfigToScript.walkTheTree(ConfigToScri
    pt.java:435)
            at weblogic.management.scripting.ConfigToScript.walkTheTree(ConfigToScri
    pt.java:397)
            at weblogic.management.scripting.ConfigToScript.convert(ConfigToScript.j
    ava:198)
            at weblogic.management.scripting.WLScriptContext.callc2s(WLScriptContext
    .java:183)
            at weblogic.management.scripting.WLScriptContext.config2Py(WLScriptConte
    xt.java:134)
            at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[
    Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
            at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;
    I)Ljava.lang.Object;(Unknown Source)
            at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java
    :160)
            at org.python.core.PyMethod.__call__(PyMethod.java:96)
            at org.python.core.PyObject.__call__(PyObject.java:248)
            at org.python.core.PyObject.invoke(PyObject.java:2016)
            at org.python.pycode._pyx4.configToScript$94(<iostream>:1537)
            at org.python.pycode._pyx4.call_function(ILorg.python.core.PyFrame;)Lorg
    .python.core.PyObject;(<iostream>:???)
            at org.python.core.PyTableCode.call(PyTableCode.java:208)
            at org.python.core.PyTableCode.call(PyTableCode.java:404)
            at org.python.core.PyFunction.__call__(PyFunction.java:184)
            at org.python.pycode._pyx59.f$0(<console>:1)
            at org.python.pycode._pyx59.call_function(ILorg.python.core.PyFrame;)Lor
    g.python.core.PyObject;(<console>:???)
            at org.python.core.PyTableCode.call(PyTableCode.java:208)
            at org.python.core.PyCode.call(PyCode.java:14)
            at org.python.core.Py.runCode(Py.java:1135)
            at org.python.core.Py.exec(Py.java:1157)
            at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
            at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter
    .java:89)
            at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpret
    er.java:70)
            at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpret
    er.java:44)dumpStack() does not give me anything more than this. Is this a known issue with WLST? I cannot find anything related to it in the known issues list.
    Thanks,
    Sean

    I think I am getting the same error, is there a resolution to this yet? Just to run down what I did, I started the WebLogic Scripting Tool w/ the following command: 'java weblogic.WLST'. I then placed the config.xml that I wanted converted to c:\config\config.xml and executed the following command at the wls:/offline> prompt: 'configToScript()'. I then get the following error:
    This Exception occured at Fri Sep 28 13:07:55 CDT 2007.
    weblogic.management.scripting.ScriptException: Error occured while performing co
    nfigToScript : Exception occurred while walking the tree.Error occured while per
    forming configToScript : Exception occurred while walking the tree.Error occured
    while performing configToScript : Error getting the name for bean null Use dump
    Stack() to view the full stacktrace Use dumpStack() to view the full stacktrace
    Use dumpStack() to view the full stacktrace
    at weblogic.management.scripting.ExceptionHandler.handleException(Except
    ionHandler.java:51)
    at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.
    java:221)
    at weblogic.management.scripting.ConfigToScript.walkTheTree(ConfigToScri
    pt.java:540)
    at weblogic.management.scripting.ConfigToScript.convert(ConfigToScript.j
    ava:198)
    at weblogic.management.scripting.WLScriptContext.callc2s(WLScriptContext
    .java:183)
    at weblogic.management.scripting.WLScriptContext.config2Py(WLScriptConte
    xt.java:134)
    at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[
    Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
    at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;
    I)Ljava.lang.Object;(Unknown Source)
    at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java
    :160)
    at org.python.core.PyMethod.__call__(PyMethod.java:96)
    at org.python.core.PyObject.__call__(PyObject.java:248)
    at org.python.core.PyObject.invoke(PyObject.java:2016)
    at org.python.pycode._pyx4.configToScript$94(<iostream>:1537)
    at org.python.pycode._pyx4.call_function(ILorg.python.core.PyFrame;)Lorg
    .python.core.PyObject;(<iostream>:???)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyTableCode.call(PyTableCode.java:404)
    at org.python.core.PyTableCode.call(PyTableCode.java:253)
    at org.python.core.PyFunction.__call__(PyFunction.java:169)
    at org.python.pycode._pyx27.f$0(<console>:1)
    at org.python.pycode._pyx27.call_function(ILorg.python.core.PyFrame;)Lor
    g.python.core.PyObject;(<console>:???)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyCode.call(PyCode.java:14)
    at org.python.core.Py.runCode(Py.java:1135)
    at org.python.core.Py.exec(Py.java:1157)
    at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
    at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter
    .java:89)
    at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpret
    er.java:70)
    at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpret
    er.java:44)
    at weblogic.management.scripting.WLST.main(WLST.java:157)
    weblogic.management.scripting.ScriptException: Error occured while performing co
    nfigToScript : Exception occurred while walking the tree.Error occured while per
    forming configToScript : Exception occurred while walking the tree.Error occured
    while performing configToScript : Error getting the name for bean null Use dump
    Stack() to view the full stacktrace Use dumpStack() to view the full stacktrace
    Use dumpStack() to view the full stacktrace
    Any ideas?!!?

  • User weblogic is not permitted to boot the server

    Hi,
    I am new to OES and after running the configtool, creating the ASIAuthorizationProvider and ASIRoleMapperProvider (both has Defaul Identity Directory: wls_dir and Application Deployment Parent: //app/policy/wls_app), binding the SSM, i get this error when starting the WLS admin server:
    15:33:26.312 EVENT Starting Jetty/4.2.25
    15:33:26.859 WARN!! Delete existing temp dir C:\BEA_HOME_10\ales32-ssm\wls-ssm\i
    nstance\wls_ssm\work\jar_temp\Jetty__8000__ for WebApplicationContext[/,jar:file
    :/C:/BEA_HOME_10/ales32-ssm/wls-ssm/webapp/arme.war!/]
    15:33:30.515 EVENT Started WebApplicationContext[,ARMEService]
    15:33:32.562 EVENT Started SocketListener on 0.0.0.0:8000
    15:33:32.562 EVENT Started org.mortbay.jetty.Server@176bf9e
    ARME is started now
    <Mar 5, 2010 3:33:33 PM SGT> <Notice> <Security> <BEA-090082> <Security initiali
    zing using security realm wls.>
    <Mar 5, 2010 3:33:34 PM SGT> <Critical> <Security> <BEA-090404> <User weblogic i
    s not permitted to boot the server; The server policy may have changed in such a
    way that the user is no longer able to boot the server.Reboot the server with t
    he administrative user account or contact the system administrator to update the
    server policy definitions.>
    <Mar 5, 2010 3:33:34 PM SGT> <Critical> <WebLogicServer> <BEA-000386> <Server su
    bsystem failed. Reason: weblogic.security.SecurityInitializationException: User
    weblogic is not permitted to boot the server; The server policy may have changed
    in such a way that the user is no longer able to boot the server.Reboot the ser
    ver with the administrative user account or contact the system administrator to
    update the server policy definitions.
    weblogic.security.SecurityInitializationException: User weblogic is not permitte
    d to boot the server; The server policy may have changed in such a way that the
    user is no longer able to boot the server.Reboot the server with the administrat
    ive user account or contact the system administrator to update the server policy
    definitions.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
    BootAuthorization(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
    itialize(Unknown Source)
    at weblogic.security.service.SecurityServiceManager.initialize(Unknown S
    ource)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    >
    <Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
    e changed to FAILED>
    <Mar 5, 2010 3:33:34 PM SGT> <Error> <WebLogicServer> <BEA-000383> <A critical s
    ervice failed. The server will shut itself down>
    <Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server stat
    e changed to FORCE_SHUTTING_DOWN>
    Stopping PointBase server...
    PointBase server stopped.
    from the WLS AdminServer.log:
    ####<Mar 5, 2010 3:33:05 PM SGT> <Info> <Socket> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774385687> <BEA-000436> <Allocating 3 reader threads.>
    ####<Mar 5, 2010 3:33:05 PM SGT> <Info> <Socket> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774385687> <BEA-000446> <Native IO Enabled.>
    ####<Mar 5, 2010 3:33:06 PM SGT> <Info> <IIOP> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774386531> <BEA-002014> <IIOP subsystem enabled.>
    ####<Mar 5, 2010 3:33:11 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774391656> <BEA-000000> <Starting OpenJPA 1.0.0.1>
    ####<Mar 5, 2010 3:33:17 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774397171> <BEA-090516> <The Authenticator provider has preexisting LDAP data.>
    ####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413421> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
    ####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413500> <BEA-090663> <The DeployableRoleMapper "com.bea.security.providers.authorization.asi.RoleProviderStub" implements the deprecated DeployableRoleProvider interface.>
    ####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413531> <BEA-090662> <The DeployableAuthorizer "com.bea.security.providers.authorization.asi.AuthorizationProviderStub" implements the deprecated DeployableAuthorizationProvider interface.>
    ####<Mar 5, 2010 3:33:33 PM SGT> <Info> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413796> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server AdminServer for security realm wls.>
    ####<Mar 5, 2010 3:33:33 PM SGT> <Notice> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774413796> <BEA-090082> <Security initializing using security realm wls.>
    ####<Mar 5, 2010 3:33:34 PM SGT> <Critical> <Security> <SGBLM010> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1267774414234> <BEA-090404> <User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.>
    ####<Mar 5, 2010 3:33:34 PM SGT> <Critical> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414234> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
    weblogic.security.SecurityInitializationException: User weblogic is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
         at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000365> <Server state changed to FAILED>
    ####<Mar 5, 2010 3:33:34 PM SGT> <Error> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Mar 5, 2010 3:33:34 PM SGT> <Notice> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414328> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Mar 5, 2010 3:33:34 PM SGT> <Info> <WebLogicServer> <SGBLM010> <AdminServer> <main> <<WLS Kernel>> <> <> <1267774414359> <BEA-000236> <Stopping execute threads.>
    also, i just noticed that when staring OES admin server i get the following from the logs:
    system_console.log:
    2010-03-05 15:19:04,218 [JettySSLListener1-1] ERROR com.wles.soap.BLM.BlmBindingImpl - getUndistributedAttributeChanges has not been implemented properly.
    2010-03-05 15:27:17,656 [Thread-31] WARN com.bea.security.ssl.axis.AxisClientSocketFactory - Error during SSL handshake; host: SGBLM010, port: 8,000.
    2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.Distributor - unable to bind unbound arme
    Communication Error:; nested exception is:
         javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
    2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.ARMEGroup - arme group '//bind/wls' error report, policyno = 52:
    2010-03-05 15:27:17,687 [Thread-31] ERROR com.bea.security.pdws.ARMEGroup - arme 'asi.null.ARME.wls_ssm.asi.SGBLM010':
    2010-03-05 15:27:33,015 [Thread-32] WARN com.bea.security.ssl.axis.AxisClientSocketFactory - Error during SSL handshake; host: SGBLM010, port: 8,000.
    2010-03-05 15:27:33,015 [Thread-32] ERROR com.bea.security.pdws.Distributor - unable to bind unbound arme
    Communication Error:; nested exception is:
         javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
    WLESWebLogic.wrapper.log:
    INFO | jvm 1 | 2010/03/05 15:27:17 | Processing AxisFault, cause: javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
    INFO | jvm 1 | 2010/03/05 15:27:17 | Re-throwing the fault...
    INFO | jvm 1 | 2010/03/05 15:27:18 | error.jsp: Client has closed the connection, error not reported to client.
    INFO | jvm 1 | 2010/03/05 15:27:18 | error.jsp: The exception is: com.bea.wles.management.console.utils.NestedJspException: Connection reset by peer: socket write error
    INFO | jvm 1 | 2010/03/05 15:27:33 | Processing AxisFault, cause: javax.net.ssl.SSLHandshakeException: Error during SSL handshake; host: SGBLM010, port: 8,000.
    INFO | jvm 1 | 2010/03/05 15:27:33 | Re-throwing the fault...
    although, it seems that the OES admin server is up since i am able to access the OES admin console.
    i have tried playing around the policies to grant the "weblogic" the priviliges for an Admin but is still get the same issue. Although, when i try to distribute the changes in the policy, "ASI ( Policy for entire Oracle Entitlements Server system ) " still appears in the list of changes.
    any thoughts on what the problem is? is there a way to force the distribution of the policy? maybe through the command prompt or other console?
    Edited by: user9056644 on Mar 5, 2010 12:02 AM

    Have you applied CP2 or CP3 to OES? There were enhancements that allows these policies to be scoped within an organization. I only ask to help guide you on distributing policies for the runtime WLS domain. The ASI domain is only for the admin. There should have been a set of resources and policies created as a result of running ConfigTool for your new instance (looks like you named it 'wls'). If no CP, it will be in DefaultApp next to ASI.
    You have to distribute policies for 'wls' immediately following running ConfigTool before starting WebLogic or you will put it into a state where it can't be started. The corrective action is to remove the state.ck file under C:\BEA_HOME_10/ales32-ssm/wls-ssm/instance/wls_ssm/work/runtime, distribute policies, restart WebLogic.
    If you need to re-run ConfigTool (after installing CP for instance), revert the following files:
    <domain>/config/config.xml
    <domain>/bin/startWebLogic.sh | .cmd
    Revert from the no-ales backups created. Remove the instance folder under C:\BEA_HOME_10\ales32-ssm/wls-ssm/instance. You can then re-run ConfigTool if you have to.

  • Creation of domain issues - migration from weblogic 10.3.0 to 10.3.5 versio

    Hello,
    i would like to kindly ask for a help with following issue:
    Basically we are migrating from the 10.3.0 to the 10.3.5 version. We are building the domain using the template in "silent mode". And when i try to create the domain with new weblogic 10.3.5 im getting some errors.
    The command to run the creation of the domain is following:
    ${WL_HOME}/common/bin/config.sh -mode=silent -silent_script=${SILENT_SCRIPT} -log=${WLLOGFILE} >> ${LOGFILE} 2>&1
    returnCode=$?
    SILENT_SCRIPT contains following commands:
    read template from "/local/wg372/BM/appl/config/NEW_DOMAIN_CONFIGURED.jar";
    write domain to "/local/wg372/BM/appl/BmDomain";
    set OverwriteDomain "true";
    close template;
    When i setup new env(solaris) with weblogic 10.3.5 im getting following error when the silent_script command (*write domain to "/local/wg372/BM/appl/BmDomain";*) is executed:
    2011-07-18 16:53:00,427 INFO [runScript] com.oracle.cie.domain.script.ScriptExecutor - succeed: read template from "/local/wg372/BM/appl/config/NEW_DOMAIN_CONFIGURED.jar"
    2011-07-18 16:53:00,427 INFO [runScript] com.oracle.cie.domain.script.ScriptExecutor - write Domain to "/local/wg372/BM/appl/BmDomain"
    2011-07-18 16:53:00,505 ERROR [runScript] com.oracle.cie.wizard.domain.silent.tasks.RunScriptTask - There was an error executing the script: /local/wg372/BM/appl/installer/silent_script
    java.lang.NullPointerException
         at com.oracle.cie.domain.security.SecurityGenerateLDIFT.buildSecurityInfo(SecurityGenerateLDIFT.java:460)
         at com.oracle.cie.domain.security.SecurityGenerateLDIFT.<init>(SecurityGenerateLDIFT.java:119)
         at com.oracle.cie.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:718)
         at com.oracle.cie.domain.script.ScriptParserClassic$StateMachine.processWrite(ScriptParserClassic.java:573)
         at com.oracle.cie.domain.script.ScriptParserClassic$StateMachine.execute(ScriptParserClassic.java:429)
         at com.oracle.cie.domain.script.ScriptParserClassic.parseAndRun(ScriptParserClassic.java:148)
         at com.oracle.cie.domain.script.ScriptParserClassic.doExecute(ScriptParserClassic.java:110)
         at com.oracle.cie.domain.script.ScriptParser.execute(ScriptParser.java:72)
         at com.oracle.cie.domain.script.ScriptParser.execute(ScriptParser.java:35)
         at com.oracle.cie.wizard.domain.helpers.Executor.runSilentScript(Executor.java:68)
         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:597)
         at com.oracle.cie.wizard.domain.silent.tasks.RunScriptTask.runScriptWithExecutor(RunScriptTask.java:551)
         at com.oracle.cie.wizard.domain.silent.tasks.RunScriptTask.execute(RunScriptTask.java:335)
         at com.oracle.cie.wizard.silent.tasks.AbstractSilentTask.run(AbstractSilentTask.java:28)
         at java.lang.Thread.run(Thread.java:662)
    In Windows env im getting following error:
    create.domain:
    [exec] -mode="silent" -silent_script=J:/_dev/build/installer/silent_script
    [exec] << read template from "J:/_dev/build/config/NEW_DOMAIN_CONFIGURED.jar"
    [exec] >> succeed: read template from "J:/_dev/build/config/NEW_DOMAIN_CONFIGURED.jar"
    [exec] << write Domain to "J:/_dev/build/BmDomain"
    [exec] CFGFWK-60550: Script execution aborted. The script may contain an error.
    [exec] null
    CFGFWK-60550: - doc says
    CFGFWK-60550: Script execution aborted. The script may contain an error.
    Cause:
    Action:
    Level: 1
    Type: ERROR
    Impact: Configuration
    I tried to google for this issue, look into the weblogic documentation but with no luck.
    So i would like to kindly ask, if anyone of you perhaps could give me a hint/advise with this problem.
    Thanks in advance.

    Hi,
    thanks for the reply but im not sure if we are talking about the same thing. What i need is to upgrade the weblogic "DOMAIN" not the weblogic installation itself.
    Anyway,
    after some googling and testing im again stucked with another issue:
    1. First i have created the old doman (10.3.0)
    2. Then i have tested the domain with the new weblogic version 10.3.5 - as it should be (and is) compatible within those 2 versions
    ---> worked fine
    3. Then via offline WLST(of weblogic 10.3.5) i have managed to create new template with command writeTemplate(nameOfTemplate.jar)
    4. But when i try to create the new domain with the new template via WLST(of weblogic 10.3.5) im again stucked (im able to read the template in wlst but not able to writeDomain ) - error:
    wls:/offline> readTemplate('/home/wg372/tmp/new_template.jar')
    wls:/offline/BmDomain>writeDomain('/home/wg372/tmp/new_domain')
    Error: writeDomain() failed. Do dumpStack() to see details.
    wls:/offline/BmDomain>dumpStack()
    com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.ScriptException: The application location must have write permission.
    at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)
    at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1538)
    at com.oracle.cie.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:803)
    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:597)
    at org.python.core.PyReflectedFunction.__call__(Unknown Source)
    at org.python.core.PyMethod.__call__(Unknown Source)
    at org.python.core.PyObject.__call__(Unknown Source)
    at org.python.core.PyInstance.invoke(Unknown Source)
    at org.python.pycode._pyx3.writeDomain$15(/var/tmp/WLSTOfflineIni6651397525640719781.py:71)
    at org.python.pycode._pyx3.call_function(/var/tmp/WLSTOfflineIni6651397525640719781.py)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyFunction.__call__(Unknown Source)
    at org.python.pycode._pyx24.f$0(<console>:1)
    at org.python.pycode._pyx24.call_function(<console>)
    at org.python.core.PyTableCode.call(Unknown Source)
    at org.python.core.PyCode.call(Unknown Source)
    at org.python.core.Py.runCode(Unknown Source)
    at org.python.core.Py.exec(Unknown Source)
    at org.python.util.PythonInterpreter.exec(Unknown Source)
    at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
    at weblogic.management.scripting.WLST.main(WLST.java:173)
    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:597)
    at weblogic.WLST.main(WLST.java:29)
    Caused by: com.oracle.cie.domain.script.ScriptException: The application location must have write permission.
    at com.oracle.cie.domain.script.ScriptExecutor.writeDomain(ScriptExecutor.java:757)
    at com.oracle.cie.domain.script.jython.WLScriptContext.writeDomain(WLScriptContext.java:795)
    ... 29 more
    I tried to have a look around for the "The application location must have write permission." problem but again with no luck.
    Furthemore when i try to do the same with old domain template, with old version of WLST (of weblogic 10.3.0), i have no problems with creating of the domain.
    Any ideas?
    Ill keep you updated :-)

  • WLST command line utility "storeUserConfig()"  is not working for 12c OHS

    Hi All,
    I am facing issue with WLST command line utility with "*storeUserConfig()*" command.
    I have installed Standalone OHS 12c (Not managed OHS with WLS), configure and start the Node Manager.
    I start the WLST command line utility from : <MW_HOME>/ohs/common/bin/wlst.sh
    I connect node manager with : nmConnect('weblogic', 'welcome1', nmType='plain', domainName='base_domain')
    wls:/offline> nmConnect('weblogic', 'welcome1', nmType='plain', domainName='base_domain')
    Connecting to Node Manager ...
    Successfully Connected to Node Manager.
    wls:/nm/base_domain> nmStart(serverName='ohs10', serverType='OHS')
    Starting server ohs10 ...
    Successfully started server ohs10 ...
    Now When I am running storeUserConfig(), it's giving me below error :
    wls:/nm/base_domain> storeUserConfig()
    Traceback (innermost last):
    File "<console>", line 1, in ?
    NameError: storeUserConfig
    I also try with storeUserConfig('/scratch/12cORC/security/myuserconfigfile.secure', '/scratch/12cORC/security/myuserkeyfile.secure') which also give same error.
    I am not able to recognize this error. What should I need to do to create the User config file ?
    Please suggest me the solution.
    I am referring this doc : http://docs.oracle.com/cd/E15586_01/web.1111/e13813/reference.htm#
    Thanks,
    Amit Nagar

    It's probably a little late for the original poster, but in case anybody else stumbles on this thread (like me today), I found a workable solution to this problem:
    For a Standalone HTTP Server there exists in $domain_home/bin a command startComponent.sh or (on Windows) startComponent.cmd. This accepts as parameter the ComponentName which will typically be ohs1 and as second parameter storeUserConfig. Documentation on this can be found here:
    http://docs.oracle.com/middleware/1212/webtier/HSADM/getstart.htm#CHDJGIII (scroll down to
    4.3.2.3 Starting Oracle HTTP Server Instances from the Command Line).
    startComponent.sh ohs1 storeUserConfig
    Unfortunately this doesn't tell you where you'll find the config and key-File. However, on a second invocation I found that - at least on windows where I tested this - they get written into c:\users\<username>\.wlst so I'd expect them in the home directory on unix. After copying the files to a more common location, I was able to reference them the usual way (formatted for better readability):
    wls:/offline> nmConnect(userConfigFile='C:/app/Middleware/Oracle_Home/user_projects/domains/base_domain/nodemanager/security/nm-cfg-base_domain.props',
    userKeyFile='C:/app/Middleware/Oracle_Home/user_projects/domains/base_domain/nodemanager/security/nm-key-base_domain.props',
    host='localhost',
    port='5556',
    domainName='base_domain')
    Connecting to Node Manager ...
    Successfully Connected to Node Manager.
    Best Regards
    Holger

  • Export metadata

    I am using the web center portal framework. I have added portals during runtime. I have deployed this application on a standalone server and I donot see the portals I created during runtime.
    As far as my knowledge is concerned, these portals are saved in an MDS repository, which have to be exported via web logic scripting tool.
    So, after logging in wlst using the integrated server ip address, i tried to use the "exportmetadata" command and I am getting the following error.
    wls:/DefaultDomain/serverConfig> exportMetadata(application='FDNYPortal', server
    ='DefaultServer', toLocation='/tmp/myrepos/mypartition')
    Traceback (innermost last):
      File "<console>", line 1, in ?
    NameError: exportMetadata
    This is how I logged in:
    wls:/offline> connect()
    Please enter your username :weblogic
    Please enter your password : weblogic1
    Please enter your server URL [t3://localhost:7001] :t3://10.237.20.85:7101
    Connecting to t3://10.237.20.85:7101 with userid weblogic ...
    Successfully connected to Admin Server 'DefaultServer' that belongs to domain 'D
    efaultDomain'.
    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.
    I want to know what is going wrong in exportmetadata.
    Thanks,
    RChavan

    Hi RChavan,
    Typically the errors occur,when you are using  wlst.cmd/sh command from wrong directory.
    In the below discussion the resolution is given  by PierluigiVernetto-
    https://forums.oracle.com/message/9192749
    NameError: exportMetadata
    run wlst.cmd from
    C:\Oracle1\Middleware\Oracle_SOA1\common\bin
    it's written in the manual that you should use the right version of WLST.... :o)
    What I get is:
    wls:/offline> exportMetadata(application='soa-infra',server='AdminServer',toLoca
    tion='C:/MDS',docs='/soa/shared/rules/**')
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "C:\Oracle1\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", line 134,
    in exportMetadata
    File "C:\Oracle1\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", line 558,
    in executeAppRuntimeMBeanOperation
    File "C:\Oracle1\MIDDLE~1\ORACLE~1\common\wlst\mdsWLSTCommands.py", line 513,
    in isConnectedToWLS
    UserWarning: MDS-91005: No connection to a Weblogic server exists. The operation
    +"exportMetadata" can be executed only in the online mode.+
    wls:/offline> exit()
    after this I do
    connect('weblogic', 'welcome1', 't3://localhost:7001')
    exportMetadata(application='soa-infra',server='AdminServer',toLocation='C:/MDS',docs='/soa/shared/rules/**')
    and it magically works :o)
    Executing operation: exportMetadata.
    Operation "exportMetadata" completed. Summary of "exportMetadata" operation is:
    List of documents successfully transferred:
    +/soa/shared/rules/BpelProcess.xsd+
    +/soa/shared/rules/DecisionService.xsd+
    +/soa/shared/rules/DecisionServiceMessages.xsd+
    +/soa/shared/rules/common.xsd+
    +/soa/shared/rules/rpi.xsd+
    +5 documents successfully transferred.+
    Hope it helps you.
    Regards,
    Hoque

  • Unable to start Manager server using Node Manager

    Hi,
    I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
    Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
    but not able to start Managed server using node manager
    its giving exception as below;
    error:- wls:/nm/webdomain> nmStart('ms1')
    Starting server ms1 ...
    Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
    Managed server log: -
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    [root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    Nodemanager log:
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
    <Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
    <Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)

    You can start a managed server as follows:
    print 'START NODE MANAGER';
    startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
    print 'CONNECT TO NODE MANAGER';
    nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
    print 'START ADMIN SERVER';
    nmStart('AdminServer');
    nmServerStatus('AdminServer');
    print 'CONNECT TO ADMIN SERVER';
    connect(adminusername, adminpassword);
    print 'START MANAGED SERVER';
    start('VideotheekWebServer','Server');
    nmServerStatus('VideotheekWebServer');
    print 'START CLUSTER';
    start('VideotheekCluster','Cluster');
    nmServerStatus('VideotheekServer1');
    nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
    The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

Maybe you are looking for