WLST undeploy BUG??

We use WLST to undeploy applications from specified targets.
Per the documentation undeploy command is undeploy('appname',targets)
However when we specify target, it undeploys from all managed servers the application is deployed to.
undeploy('Tapplication','Server1')
Undeploying application Tapplication
<Oct 2, 2006 8:40:33 PM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating undeploy operation for application, Tapplication [archive: null], to Server1 Server2 .>
Completed the undeployment of Application with status completed
Current Status of your Deployment:
Deployment command type: undeploy
Deployment State : completed
Is this a bug?

This does look like a bug, you need to file a support case.
-satya
BEA Blog:
http://dev2dev.bea.com/blog/sghattu/
Get Involved in CodeShare:
https://wls-console-extensions.projects.dev2dev.bea.com/
https://wlnav.projects.dev2dev.bea.com/
https://eclipse-wlst.projects.dev2dev.bea.com/
https://wlst.projects.dev2dev.bea.com/

Similar Messages

  • WLST deploy bug

    There seems to be a bug in the deploy method in the WebLogic scripting tool (WLST) on WebLogic Server 9.2.
    When deploying to a remote server using an upload parameter of "false", the path parameter indicates a path on the remote server. The deploy method erroneously checks to see if the path is valid on the local system before proceeding.
    A workaround is to create a file having that path on the local system before calling the deploy method. It can be empty as it is not used for the deployment.
    Example:
    open(path, "w").close()
    deploy(appName=myApplication, path=path, upload="false")
    Edited by crogers at 04/24/2007 3:23 PM

    This does look like a bug, you need to file a support case.
    -satya
    BEA Blog:
    http://dev2dev.bea.com/blog/sghattu/
    Get Involved in CodeShare:
    https://wls-console-extensions.projects.dev2dev.bea.com/
    https://wlnav.projects.dev2dev.bea.com/
    https://eclipse-wlst.projects.dev2dev.bea.com/
    https://wlst.projects.dev2dev.bea.com/

  • WLST create bug for JDBCDataSourceParams

    using WLST 9.2 with MP2 patch (allows for catch of WLSTExceptions)....
    why is the WLST create statement not applying a name to the MBean obejct only with JDBCDataSourceParams? instead NO_NAME_0 is created (ie. JDBCDataSourceParams/NO_NAME_0).
    what is really insane is that Bea has published a script (http://edocs.bea.com/wlp/docs92/db/appx_oracle_rac_scripts.html) showing the creation of JDBCDataSourceParams with a specific name then they path through the NO_NAME_0. this isn't documented in the WLST Command & Variable Reference as a special case and thus ought to be a bug.

    WLST creates a directory hierarchy for displaying MBeans. I.e.
    wls:/mydomain/serverConfig/Servers/myserver>
    There are two parts, the first is the attribute name (Servers), and the
    second is the name (myserver).
    This works for the majority of MBeans as most have a Name attribute
    (Servers, JDBCSystemResources, etc.). However, some MBeans do not have a
    name attribute (i.e.
    JDBCDataSourceParams). In this case, WLST can not store the MBean name as
    there is no attribute called Name. It allows the MBean to be created and use
    the NO_NAME_0 notation to keep the attribute name / name display consistent.
    At this point, it may be difficult to add a Name and maintain backwards
    compatibility with existing scripts. But, I will forward this to the JDBC
    folks to see what they think.
    <Matthew Young> wrote in message news:[email protected]..
    using WLST 9.2 with MP2 patch (allows for catch of WLSTExceptions)....
    why is the WLST create statement not applying a name to the MBean obejct
    only with JDBCDataSourceParams? instead NO_NAME_0 is created (ie.
    JDBCDataSourceParams/NO_NAME_0).
    what is really insane is that Bea has published a script
    (http://edocs.bea.com/wlp/docs92/db/appx_oracle_rac_scripts.html) showing
    the creation of JDBCDataSourceParams with a specific name then they path
    through the NO_NAME_0. this isn't documented in the WLST Command & Variable
    Reference as a special case and thus ought to be a bug.

  • Can't figure out why I can't undeploy an application using WLST

    Hi,
    I have WebLogic 9.2.2 installed locally on my WinXP machine. I am running a WLST script (through Ant 1.6) to attempt to undeploy my application. This line
    undeploy("RoutingEngine (v1.0)")
    is causing this error,
    [wlst] Undeploying application RoutingEngine (v1.0) ...
    [wlst] <Mar 4, 2009 1:04:40 PM MST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating undeploy operation for application, RoutingEngine (v1.0) [archive: null], to AdminServer .>
    [wlst] Failed to undeploy the application with status failed
    [wlst] Current Status of your Deployment:
    [wlst] Deployment command type: undeploy
    [wlst] Deployment State : failed
    [wlst] Deployment Message : weblogic.management.ManagementException: [Deployer:149001]No application named 'RoutingEngine (v1.0)' exists for operation undeploy
    If I log in to my WebLogic admin console under "Deployments", there is an application named "RoutingEngine (v1.0)" listed. Should I be naming this something else or referencing it under another name?
    Thanks, - Dave

    Hi, something similar has happened in an oracle weblogic 10.3.5, when i tried to delete an application deployed as library, the adminserver responded with error “[Deployer:149001]No application named ‘my-web-9(9.2.1)’ exists for operation undeploy”.
    I solved this problem, using weblogic.Deployer but specifying the appversion like this:
    java weblogic.Deployer -verbose -noexit -name my-web-9 -appversion 9.2.1 -adminurl t3://192.168.40.66:7000 -user weblogic -undeploy

  • Problem to create EG for WLI

    I followed up the PO example, but my env is a cluster and I get some exections.I was trying to deploy File EG on one of a managed server. could anyone help me out. Thanks very much.
    py script:
    # Jython script to create, deploy & configure event generator
    from java.lang import Boolean
    from java.lang import Integer
    import weblogic.Deployer
    import com.bea.wli.mbconnector.file as eggen
    import com.bea.wli.management.configuration as wlicfg
    import jarray
    import sys
    sys.path.append("lib/wlst.jar/Jython-Lib")
    import getopt
    # The wlst file needs to be generated by starting wlst in interactive mode and doing writeIniFile("wlst.py")
    import wlst
    from org.xml.sax import *
    from java.io import IOException
    from org.w3c.dom import *
    from java.io import FileInputStream
    from javax.xml.transform.stream import StreamSource
    from javax.xml.transform.stream import StreamResult
    from javax.xml.parsers import DocumentBuilderFactory
    propertyFile="EG.xml"
    # globals
    domaindir = None
    username = None
    password = None
    url = None
    domaindir = None
    target="wlidev1-0"
    #     Create the EG
    def createEG( egName, egType):
         print "Creating EG ", egName
         eggen.FileConnGenerator.main([
              "-inName", egName,
              "-outfile", domaindir + "/" + "WLI" + egType + "EG_" + egName + ".jar"])
    # deploy the EG
    # egType has to be "File", "Jms", "Email" or "Timer"
    # (that's the convention the console uses)
    def deployEG( egName, egType ):
         print "Deploying ", egName
         try:
              wlst.deploy( "WLI" + egType + "EG_" + egName, domaindir + "/" + "WLI" + egType + "EG_" + egName + ".jar", target )
         except Exception,e:
              wlst.dumpStack()     
    def undeployEG( egName ):
         print "Undeploying ", egName
         try:
              wlst.undeploy( domaindir + "/" + egName + ".jar",target )
         except Exception, e:
              print "No such app name " + egName + " on " +str(target)
    #     Deploy the rules
    def deployRules( egName, d ):
         print "Creating rules for ", egName
         egCfgMBean = wlst.getTarget("FileEventGenerators/FileEventGenerators")
         egMBean = egCfgMBean.newFileEventGenConfigurationMBean( egName )
         cData = jarray.zeros( 1, wlicfg.FileEventGenChannelConfiguration )
         cData[0] = wlicfg.FileEventGenChannelConfiguration()
         if d.has_key('Channel'):
              cData[0].setChannel( d['Channel'] )
         if d.has_key('ChannelType'):
              cData[0].setChannelType(d['ChannelType'])
         if d.has_key('encoding'):
              cData[0].setEncoding(d['encoding'])
         if d.has_key('FtpHostName'):
              cData[0].setFtpHostName(d['FtpHostName'])
         if d.has_key('FtpUserName'):
              cData[0].setFtpUserName(d['FtpUserName'])
         if d.has_key('FtpPassword'):
              cData[0].setFtpPassword(d['FtpPassword'])
         if d.has_key('FtpPasswordAlias'):
              cData[0].setFtpPasswordAlias(d['FtpPasswordAlias'])
         if d.has_key('FtpLocalDirectory'):
              cData[0].setFtpLocalDirectory(d['FtpLocalDirectory'])
         if d.has_key('FileDirectory'):
              cData[0].setFileDirectory(d['FileDirectory'])
         if d.has_key('ScanSubdirs'):
              cData[0].setScanSubdirs(Boolean(d['ScanSubdirs']))
         if d.has_key('FilePattern'):
              cData[0].setFilePattern(d['FilePattern'])
         if d.has_key('SortByArrival'):
              cData[0].setSortByArrival(Boolean(d['SortByArrival']))
         if d.has_key('ReadLimit'):
              cData[0].setReadLimit(Integer.parseInt((d['ReadLimit'])))
         if d.has_key('PostRead'):
              cData[0].setPostRead(d['PostRead'])
         if d.has_key('ArchiveDirectory'):
              cData[0].setArchiveDirectory(d['ArchiveDirectory'])
         if d.has_key('ErrorDirectory'):
              cData[0].setErrorDirectory(d['ErrorDirectory'])
         if d.has_key('Comment'):
              cData[0].setComment(d['Comment'])
         if d.has_key('PassByFileName'):
              cData[0].setPassByFileName(Boolean(d['PassByFileName']))
         if d.has_key('PollingInterval'):
              cData[0].setPollingInterval(Integer.parseInt(d['PollingInterval']))     
         if d.has_key('PublishAsUser'):
              cData[0].setPublishAsUser(d['PublishAsUser'])               
         print cData     
         try:
              egMBean.setChannels(cData)
         except Exception ,e:
              wlst.dumpStack()     
         wlst.saveDomain()
    # main
    def main():
         global domaindir, username, password, url
         try:
              opts, args = getopt.getopt( sys.argv[1:], "n:p:u:d:", "" )
         except getopt.GetoptError:
              print "invalid option"
              sys.exit(2)
         for o, a in opts:
              if o == "-n":
                   username = a
              if o == "-p":
                   password = a
              if o == "-u":
                   url = a
              if o == "-d":
                   domaindir = a
         print domaindir          
         if ((username == None) or (password == None) or (url == None) or (domaindir == None)):
              print "Bad or Missing parameters"
              sys.exit(2)
         print 'Connecting .... '
         wlst.connect( username, password, url )
         #     wlst.debug()
         factory = DocumentBuilderFactory.newInstance();
         try :
              factory = DocumentBuilderFactory.newInstance()
              builder = factory.newDocumentBuilder()
              inputx = FileInputStream(propertyFile)
              document = builder.parse(inputx)
         except Exception, e:
                   e.printStackTrace()
         eglist = document.getElementsByTagName("FileEG")
         for eg in range(eglist.getLength()):
              egElement = eglist.item(eg)
              nnp = egElement.getAttributes()
              egName=nnp.item(0).getNodeValue()
              print egName
              undeployEG(egName)
              createEG(egName,"File")
              #deploy EGs for     each FileEG node          
              try:
                   deployEG( egName, "File" )
              except Exception ,e:
                   wlst.dumpStack()     
              #get ChannelRule Node attributes
              nl=egElement.getElementsByTagName("ChannelRule")
              for p in range(nl.getLength()):
                   nnm=nl.item(p).getAttributes()
                   d={}
                   for q in range(nnm.getLength()):
                        node=nnm.item(q)
                        d[node.getNodeName()]=node.getNodeValue()
                   #there might be server ChannelRules for one fileEG
                   deployRules( egName, d )
    # invoke main
    if __name__ == "__main__":
    main()
    logs:
    (wlsuser) wlidev1> ./create_eg.wli WLI-DEV
    Buildfile: build.xml
    clean:
    [delete] Deleting directory /export/home/wli-auto/temp
    init:
    [mkdir] Created dir: /export/home/wli-auto/temp
    deploy_egs:
    [java] Welcome to Weblogic Server Administration Scripting Shell
    [java] Type help() for help on available commands
    [java] /data/WLI/user_projects/domains/WLI-DEV
    [java] Connecting ....
    [java] Connecting to weblogic server instance running at t3://wlidevadmin:7001 as username system ...
    [java] Successfully connected to Admin Server 'wlidevadmin' that belongs to domain 'WLI-DEV'.
    [java] StatusUpdateInterface_bs_ifp
    [java] Undeploying StatusUpdateInterface_bs_ifp
    [java] No such app name StatusUpdateInterface_bs_ifp on wlidev1-0
    [java] Creating EG StatusUpdateInterface_bs_ifp
    [java] Deploying StatusUpdateInterface_bs_ifp
    [java] Deploying WLIFileEG_StatusUpdateInterface_bs_ifp from /data/WLI/user_projects/domains/WLI-DEV/WLIFileEG_StatusUpdateInterface_bs_ifp.jar ...
    [java] ...Deployment Failed: weblogic.management.DeploymentException:
    [java] Exception:weblogic.management.ApplicationException: start() failed.
    [java] Module: WLIFileEG_StatusUpdateInterface_bs_ifp Error: Exception starting module: EJBModule(WLIFileEG_StatusUpdateInterface_bs_ifp,status=ACTIVATED)
    [java] Unable to deploy EJB: WLIFileEG_StatusUpdateInterface_bs_ifp.jar from WLIFileEG_StatusUpdateInterface_bs_ifp.jar:
    [java] weblogic.cluster.migration.MigrationException: nulljava.lang.reflect.InvocationTargetException
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:324)
    [java] at weblogic.ejb20.internal.MessageDrivenEJBHome.createBean(MessageDrivenEJBHome.java:232)
    [java] at weblogic.ejb20.pool.MessageDrivenPool.createBean(MessageDrivenPool.java:116)
    [java] at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:254)
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:253)
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.migratableActivate(MessageDrivenBeanPoolInfoImpl.java:286)
    [java] at weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
    [java] at weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
    [java] at weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
    [java] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1748)
    [java] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1580)
    [java] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:687)
    [java] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2181)
    [java] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2222)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2521)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2439)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2156)
    [java] at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:682)
    [java] at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    [java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    [java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    [java] Caused by: javax.ejb.CreateException: Config could not be obtained java.lang.NullPointerException
    [java] at com.bea.wli.mbconnector.file.FileConnMDB.ejbCreate(FileConnMDB.java:186)
    [java] ... 24 more
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.migratableActivate(MessageDrivenBeanPoolInfoImpl.java:288)
    [java] at weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
    [java] at weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
    [java] at weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
    [java] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1748)
    [java] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1580)
    [java] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:687)
    [java] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2181)
    [java] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2222)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2521)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2439)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2156)
    [java] at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:682)
    [java] at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    [java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    [java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    [java] Creating rules for StatusUpdateInterface_bs_ifp
    com.bea.wli.management.configuration.FileEventGenChannelConfiguration)
    [java] StatusUpdateInterface_bs_st
    [java] Undeploying StatusUpdateInterface_bs_st
    [java] No such app name StatusUpdateInterface_bs_st on wlidev1-0
    [java] Creating EG StatusUpdateInterface_bs_st
    [java] Deploying StatusUpdateInterface_bs_st
    [java] Deploying WLIFileEG_StatusUpdateInterface_bs_st from /data/WLI/user_projects/domains/WLI-DEV/WLIFileEG_StatusUpdateInterface_bs_st.jar ...
    [java] .Deployment Failed: weblogic.management.DeploymentException:
    [java] Exception:weblogic.management.ApplicationException: start() failed.
    [java] Module: WLIFileEG_StatusUpdateInterface_bs_st Error: Exception starting module: EJBModule(WLIFileEG_StatusUpdateInterface_bs_st,status=ACTIVATED)
    [java] Unable to deploy EJB: WLIFileEG_StatusUpdateInterface_bs_st.jar from WLIFileEG_StatusUpdateInterface_bs_st.jar:
    [java] weblogic.cluster.migration.MigrationException: nulljava.lang.reflect.InvocationTargetException
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:324)
    [java] at weblogic.ejb20.internal.MessageDrivenEJBHome.createBean(MessageDrivenEJBHome.java:232)
    [java] at weblogic.ejb20.pool.MessageDrivenPool.createBean(MessageDrivenPool.java:116)
    [java] at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:254)
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:253)
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.migratableActivate(MessageDrivenBeanPoolInfoImpl.java:286)
    [java] at weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
    [java] at weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
    [java] at weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
    [java] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1748)
    [java] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1580)
    [java] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:687)
    [java] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2181)
    [java] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2222)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2521)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2439)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2156)
    [java] at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:682)
    [java] at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    [java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    [java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    [java] Caused by: javax.ejb.CreateException: Config could not be obtained java.lang.NullPointerException
    [java] at com.bea.wli.mbconnector.file.FileConnMDB.ejbCreate(FileConnMDB.java:186)
    [java] ... 24 more
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.migratableActivate(MessageDrivenBeanPoolInfoImpl.java:288)
    [java] at weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
    [java] at weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
    [java] at weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
    [java] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1748)
    [java] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1580)
    [java] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:687)
    [java] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2181)
    [java] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2222)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2521)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2439)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2156)
    [java] at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:682)
    [java] at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    [java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    [java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    com.bea.wli.management.configuration.FileEventGenChannelConfiguration)
    [java] StatusUpdateInterface_hnca_ifp
    [java] Undeploying StatusUpdateInterface_hnca_ifp
    [java] No such app name StatusUpdateInterface_hnca_ifp on wlidev1-0
    [java] Creating EG StatusUpdateInterface_hnca_ifp
    [java] Deploying StatusUpdateInterface_hnca_ifp
    [java] Deploying WLIFileEG_StatusUpdateInterface_hnca_ifp from /data/WLI/user_projects/domains/WLI-DEV/WLIFileEG_StatusUpdateInterface_hnca_ifp.jar ...
    [java] .Deployment Failed: weblogic.management.DeploymentException:
    [java] Exception:weblogic.management.ApplicationException: start() failed.
    [java] Module: WLIFileEG_StatusUpdateInterface_hnca_ifp Error: Exception starting module: EJBModule(WLIFileEG_StatusUpdateInterface_hnca_ifp,status=ACTIVATED)
    [java] Unable to deploy EJB: WLIFileEG_StatusUpdateInterface_hnca_ifp.jar from WLIFileEG_StatusUpdateInterface_hnca_ifp.jar:
    [java] weblogic.cluster.migration.MigrationException: nulljava.lang.reflect.InvocationTargetException
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:324)
    [java] at weblogic.ejb20.internal.MessageDrivenEJBHome.createBean(MessageDrivenEJBHome.java:232)
    [java] at weblogic.ejb20.pool.MessageDrivenPool.createBean(MessageDrivenPool.java:116)
    [java] at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:254)
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:253)
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.migratableActivate(MessageDrivenBeanPoolInfoImpl.java:286)
    [java] at weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
    [java] at weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
    [java] at weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
    [java] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1748)
    [java] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1580)
    [java] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:687)
    [java] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2181)
    [java] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2222)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2521)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2439)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2156)
    [java] at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:682)
    [java] at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    [java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    [java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    [java] Caused by: javax.ejb.CreateException: Config could not be obtained java.lang.NullPointerException
    [java] at com.bea.wli.mbconnector.file.FileConnMDB.ejbCreate(FileConnMDB.java:186)
    [java] ... 24 more
    [java] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.migratableActivate(MessageDrivenBeanPoolInfoImpl.java:288)
    [java] at weblogic.cluster.migration.MigratableGroup.add(MigratableGroup.java:107)
    [java] at weblogic.cluster.migration.MigrationManager.privateRegister(MigrationManager.java:180)
    [java] at weblogic.cluster.migration.MigrationManager.register(MigrationManager.java:127)
    [java] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1748)
    [java] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1580)
    [java] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:687)
    [java] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2181)
    [java] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2222)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2521)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2439)
    [java] at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2156)
    [java] at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:682)
    [java] at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    [java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    [java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    BUILD SUCCESSFUL
    Total time: 29 seconds

    Hi,
    In MRP2 view the "Procurrement type" should be "F" for creation of PO for any material and Purchasing view also should be extended for that.
    First you extend the MRP views in MM50 if views are not available and maintain the procurement type indicator as F
    If MRP views are available definitely it will show you the "procurement type" field.
    If the above solution is not useful to you please let me know what is the exact error message you are getting in creation of PO.
    regards,
    KN

  • JNDI Exception on re-deployment to a cluster

    I'm getting an error that I have not seen in the newsgroups so far. It
              happens when I deploy what I believe to be a properly configured clusterable
              application (.ear file) to my cluster.
              Here's my setup:
              WebLogic 6.0 sp1, three instances across 2 machines. The admin server (wl1)
              is running on Stimpy (win2kAS) on 10.10.10.21 (it is not part of the
              cluster). The 1st managed server (app1) is also on Stimpy bound to
              10.10.10.22 (a virtual IP). The second managed server (app3) is on Ren
              (also win2kAS) at 10.10.10.23. Auto-deploy is off. I am using the console
              to deploy the app. (I turned auto-deploy off because the app was getting
              deployed to the admin server automatically and throwing an error because of
              the clustered HTTP session state)
              Here's what happens.
              I start up all of the instances with no apps deployed. Everything appears
              to be running fine. No errors. I then use the console to deploy my
              application (sample1.0.ear). I select only the cluster as the target for
              the EJB and the webapp. If I try to access the app at this point I just get
              404's. I then restart all of the servers and the app gets deployed across
              the cluster with no errors. I can access everything JSPs, servlets, and an
              EJB without issue.
              My problem comes when I try to re-deploy the application. I have tried this
              using the console, and by copying the new .ear file to the applications
              directory on the admin server. I always get the same error, and it only
              shows up on "app1" the first managed server in the cluster. Below is the
              output form the log:
              Undeploying EJB Component HelloWorldEJB
              <Apr 16, 2001 10:24:52 PM EDT> <Info> <J2EE> <Undeployed : sample1.0>
              <Apr 16, 2001 10:24:53 PM EDT> <Info> <EJB> <EJB Deploying file:
              HelloWorldEJB.j
              ar>
              <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying EJB Component
              : H
              elloWorldEJB
              weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested
              exc
              eption is:
              javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              repl
              ica-aware stub to a name that is currently bound to a replica-aware stub;
              remain
              ing name ''
              javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              replica-awar
              e stub to a name that is currently bound to a replica-aware stub; remaining
              name
              <<no stack trace available>>
              >
              <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying application
              sampl
              e1.0: Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
              >
              <Apr 16, 2001 10:24:53 PM EDT> <Error> <Management>
              <InvocationTargetException s
              etting attribute Deployed on MBean
              me:Name=sample1.0,Location=app3,Type=Applicat
              ionConfig to value true. Method: public void
              weblogic.management.mbeans.custom.A
              pplication.setDeployed(boolean) throws
              weblogic.management.DeploymentException,w
              eblogic.management.UndeploymentException
              weblogic.management.DeploymentException: Could not deploy:
              'HelloWorldEJB.jar':
              JNDI name in use
              at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
              at weblogic.j2ee.Application.deploy(Application.java:167)
              at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
              at
              weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
              ation.java:217)
              at
              weblogic.management.mbeans.custom.Application.setDeployed(Application
              .java:187)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
              anImpl.java:1136)
              at
              weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
              anImpl.java:773)
              at
              weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
              anImpl.java:750)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
              igurationMBeanImpl.java:256)
              at
              com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
              ava:1356)
              at
              com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
              ava:1331)
              at
              weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Remo
              teMBeanServerImpl_WLSkel.java:1075)
              at
              weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:373)
              at
              weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:237)
              at
              weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
              andler.java:118)
              at
              weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:17)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
              to b
              ind an object under the name HelloWorldHome_EO in the jndi tree. The object
              you
              have bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 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 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
              to b
              ind an object under the name HelloWorldHome in the jndi tree. The object you
              hav
              e bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is non
              clu
              sterable and you have tried to bind more than once from two or more servers.
              Suc
              h objects can only deployed from one server.>
              Here's a question. Why am I seeing "weblogic.ejb20.EJBDeploymentException"?
              As far as I know, I have not installed the EJB2.0 container. Does this get
              installed by default with sp1? Also, I quite sure that my deployment
              descriptors are correct. Here's my weblogic-ejb-jar.xml for the HelloWorld
              EJB:
              <?xml version="1.0"?>
              <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0
              EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>HelloWorld</ejb-name>
              <caching-descriptor>
              <max-beans-in-free-pool>100</max-beans-in-free-pool>
              </caching-descriptor>
              <clustering-descriptor>
              <home-is-clusterable>true</home-is-clusterable>
              <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
              <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
              potent>
              </clustering-descriptor>
              <jndi-name>HelloWorldHome</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              Who needs clustering anyway, damn it?! (Well...I do) Any one know what's
              going on here?
              

    This seems like potential redeploy/undeploy bugs. COuld you follow up with
              [email protected]
              Viresh Garg
              Principal Developer Relations Engineer
              BEA Systems
              Paul Citarella wrote:
              > I'm getting an error that I have not seen in the newsgroups so far. It
              > happens when I deploy what I believe to be a properly configured clusterable
              > application (.ear file) to my cluster.
              >
              > Here's my setup:
              > WebLogic 6.0 sp1, three instances across 2 machines. The admin server (wl1)
              > is running on Stimpy (win2kAS) on 10.10.10.21 (it is not part of the
              > cluster). The 1st managed server (app1) is also on Stimpy bound to
              > 10.10.10.22 (a virtual IP). The second managed server (app3) is on Ren
              > (also win2kAS) at 10.10.10.23. Auto-deploy is off. I am using the console
              > to deploy the app. (I turned auto-deploy off because the app was getting
              > deployed to the admin server automatically and throwing an error because of
              > the clustered HTTP session state)
              >
              > Here's what happens.
              >
              > I start up all of the instances with no apps deployed. Everything appears
              > to be running fine. No errors. I then use the console to deploy my
              > application (sample1.0.ear). I select only the cluster as the target for
              > the EJB and the webapp. If I try to access the app at this point I just get
              > 404's. I then restart all of the servers and the app gets deployed across
              > the cluster with no errors. I can access everything JSPs, servlets, and an
              > EJB without issue.
              >
              > My problem comes when I try to re-deploy the application. I have tried this
              > using the console, and by copying the new .ear file to the applications
              > directory on the admin server. I always get the same error, and it only
              > shows up on "app1" the first managed server in the cluster. Below is the
              > output form the log:
              >
              > Undeploying EJB Component HelloWorldEJB
              > <Apr 16, 2001 10:24:52 PM EDT> <Info> <J2EE> <Undeployed : sample1.0>
              > <Apr 16, 2001 10:24:53 PM EDT> <Info> <EJB> <EJB Deploying file:
              > HelloWorldEJB.j
              > ar>
              > <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying EJB Component
              > : H
              > elloWorldEJB
              > weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested
              > exc
              > eption is:
              > javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              > repl
              > ica-aware stub to a name that is currently bound to a replica-aware stub;
              > remain
              > ing name ''
              > javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              > replica-awar
              > e stub to a name that is currently bound to a replica-aware stub; remaining
              > name
              > ''
              > <<no stack trace available>>
              > >
              > <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying application
              > sampl
              > e1.0: Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
              > >
              > <Apr 16, 2001 10:24:53 PM EDT> <Error> <Management>
              > <InvocationTargetException s
              > etting attribute Deployed on MBean
              > me:Name=sample1.0,Location=app3,Type=Applicat
              > ionConfig to value true. Method: public void
              > weblogic.management.mbeans.custom.A
              > pplication.setDeployed(boolean) throws
              > weblogic.management.DeploymentException,w
              > eblogic.management.UndeploymentException
              > weblogic.management.DeploymentException: Could not deploy:
              > 'HelloWorldEJB.jar':
              > JNDI name in use
              >
              > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
              > at weblogic.j2ee.Application.deploy(Application.java:167)
              > at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
              > at
              > weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
              > ation.java:217)
              > at
              > weblogic.management.mbeans.custom.Application.setDeployed(Application
              > .java:187)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
              > anImpl.java:1136)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
              > anImpl.java:773)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
              > anImpl.java:750)
              > at
              > weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
              > igurationMBeanImpl.java:256)
              > at
              > com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
              > ava:1356)
              > at
              > com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
              > ava:1331)
              > at
              > weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Remo
              > teMBeanServerImpl_WLSkel.java:1075)
              > at
              > weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              > va:373)
              > at
              > weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              > va:237)
              > at
              > weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
              > andler.java:118)
              > at
              > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > .java:17)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > >
              > <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
              > to b
              > ind an object under the name HelloWorldHome_EO in the jndi tree. The object
              > you
              > have bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 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 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
              > to b
              > ind an object under the name HelloWorldHome in the jndi tree. The object you
              > hav
              > e bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is non
              > clu
              > sterable and you have tried to bind more than once from two or more servers.
              > Suc
              > h objects can only deployed from one server.>
              >
              > Here's a question. Why am I seeing "weblogic.ejb20.EJBDeploymentException"?
              > As far as I know, I have not installed the EJB2.0 container. Does this get
              > installed by default with sp1? Also, I quite sure that my deployment
              > descriptors are correct. Here's my weblogic-ejb-jar.xml for the HelloWorld
              > EJB:
              >
              > <?xml version="1.0"?>
              > <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0
              > EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
              > <weblogic-ejb-jar>
              > <weblogic-enterprise-bean>
              > <ejb-name>HelloWorld</ejb-name>
              > <caching-descriptor>
              > <max-beans-in-free-pool>100</max-beans-in-free-pool>
              > </caching-descriptor>
              > <clustering-descriptor>
              > <home-is-clusterable>true</home-is-clusterable>
              > <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
              > <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
              > potent>
              > </clustering-descriptor>
              > <jndi-name>HelloWorldHome</jndi-name>
              > </weblogic-enterprise-bean>
              > </weblogic-ejb-jar>
              >
              > Who needs clustering anyway, damn it?! (Well...I do) Any one know what's
              > going on here?
              

  • WLST - bug? - undeploy command

    Hi,
    We're using WebLogic 10.0 MP1. Environment is Red Hat Linux. We've got an application deployed to a cluster of two managed severs. I'm attempting to write a WLST script to which, in part, undeploys the application from each server one at a time. I referred to the documentation on the "undeploy" command which states the "targets" parameter specifies which managed servers to undeploy the application from. However, the WLST tool seems to ignore the "targets" parameter altogether and just undeploys from all managed servers it is deployed on regardless. The setup looks something like this:
    undeploy(appName='myapp', targets='my-server-1')
    Undeploying application myapp ...
    <Sep 28, 2009 3:07:19 PM PDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating undeploy operation for application, myapp [archive: null], to my-server-1 my-server-2 .>
    Can somebody tell me what I'm doing wrong here? Or if it is a bug as i suspect what is the fix/workaround.
    Thanks,
    -Jordan
    Edited by: user10342668 on Sep 28, 2009 4:20 PM

    Hi,
    I used the below command to undeploy an application from a managed node.
    undeploy(appName, targets='myserver01')
    But I get the below message:
    <12-May-2011 15:30:11 o'clock BST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating undeploy operation for application, myBusinessApp[archive: null], to AdminServer .>
    Failed to undeploy the application with status failed
    Current Status of your Deployment:
    Deployment command type: undeploy
    Deployment State : failed
    Deployment Message : weblogic.management.ManagementException: [Deployer:149118]'myBusinessApp' is not targeted to 'AdminServer'.
    In spite of explicitly mentioning the target, it still looks for admin server.
    Can you pls help me in fixing this.
    Regards,
    Naveen
    Edited by: 858498 on 12-May-2011 22:31

  • Wlst bug ??

    I created a class in Python (Cluster) that has the properties name, and servers ( a list of Server classes). The server class has appropriate properties as well (name, port, etc.)
    when i loop through the class and call the
    create(_cluster.name, "Cluster") my cluster is created but i cannot access it using the wlst gui mode. in fact it displays as an infinite loop of clusters:
    Cluster
    |
    Cluster1
    |
    Cluster1
    and so on. However, it looks just fine in wlshell and in the normal server console. also i don't see this if i create the cluster by looping over a list of strings (only as a class). Can anyone make any sense out of this one?

    resolved...
    looks like I had some special characters (\n) in my string that were not properly stripped when parsing my properties file that cause this strange behavior. still might be a bug but is only related to invalid string data (presumably)

  • "assign" bug in wlst 9

    Hi all, we are using wlst offline to configure domain and its resources. While doing it, we came across interesting situation.
    For one of our applications, we needed to configure JMS resources and mail session in a domain. This combination produced interesting situation. While assigning target(s) to mail session mbean using "assign", it would re-assign the target(s) of jms sub deploy module from jms server(s) to list of target for mail session. We were using "assign" for setting up target.
    I spent considerable to time to figure it out and resolved it by using "setTarget" for mail session instead of "assign".
    Is it a bug or lack of documentation on wlst? A little insight on this would really help us and others in future.
    Thanks much,
    hardeep
    Edited by reehalhs at 07/24/2007 10:07 AM
    Edited by reehalhs at 07/24/2007 10:08 AM

    See this -> Don’t Panic
    "Yesterday (09/09/09, by the way) Apple released iTunes 9. Unfortunately it has a nasty bug that prevents iVolume from analyzing songs that have been imported from a file. All other songs – that is purchased, ripped or converted songs – will still be processed fine by iVolume.
    We put highest priority on this issue. All other projects have been interrupted in order to restore full compatibility with iTunes 9 as soon as possible. We already found a solution and are currently busy implementing it. Things look good so far.
    So please be patient, a new version of iVolume will be released very soon"

  • [Patch 정보] TRACKING BUG FOR CUMULATIVE MLR#6 ON TOP OF BPEL PM 10.1.3.3.1

    최근에 출시된 BPEL PM 10.1.3.3.1의 통합패치입니다.
    아래는 readme.txt에 포함된 patch list입니다.
    # WARNING: Failure to carefully read and understand these requirements may
    # result in your applying a patch that can cause your Oracle Server to
    # malfunction, including interruption of service and/or loss of data.
    # If you do not meet all of the following requirements, please log an
    # iTAR, so that an Oracle Support Analyst may review your situation. The
    # Oracle analyst will help you determine if this patch is suitable for you
    # to apply to your system. We recommend that you avoid applying any
    # temporary patch unless directed by an Oracle Support Analyst who has
    # reviewed your system and determined that it is applicable.
    # Requirements:
    # - You must have located this patch via a Bug Database entry
    # and have the exact symptoms described in the bug entry.
    # - Your system configuration (Oracle Server version and patch
    # level, OS Version) must exactly match those in the bug
    # database entry - You must have NO OTHER PATCHES installed on
    # your Oracle Server since the latest patch set (or base release
    # x.y.z if you have no patch sets installed).
    # - [Oracle 9.0.4.1 & above] You must have Perl 5.00503 (or later)
    # installed under the ORACLE_HOME, or elsewhere within the host
    # environment.
    # Refer to the following link for details on Perl and OPatch:
    # http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=189489.1
    # If you do NOT meet these requirements, or are not certain that you meet
    # these requirements, please log an iTAR requesting assistance with this
    # patch and Support will make a determination about whether you should
    # apply this patch.
    # 10.1.3.3.1 Bundle Patch 6823628
    # DATE: March 14, 2008
    # Platform Patch for : Generic
    # Product Version # : 10.1.3.3.1
    # Product Patched : Oracle(R) SOA
    # Bugs Fixed by 10.1.3.3.1 Initial patch 6492514 :
    # Bug 5473225 - PATCH01GENESIS HOT UNABLE TO CATCH AN EXCEPTION DURING A
    # TRANSFORM
    # Bug 5699423 - PARTNERLINK PROPERTY THAT SET BPELXPROPERTY FUNCTION DOESN'T
    # WORK
    # Bug 5848272 - STATEFUL WEBSERVICES DEMO ON OTN DOES NOT WORK 10.1.3.1
    # Bug 5872799 - ANT DEPLOY BPEL TEST FAILS/RUNS ON DEFAULT DOMAIN NOT
    # SPECIFIED TARGET DOMAIN
    # Bug 5883401 - ALLOW A WAY TO CREATE EMPTY NODES - AND USE FOR REQUIRED
    # NODES
    # Bug 5919412 - SAMPLE DEMO BPEL PROCESSES MIMESERVICE MIMEREQUESTER AXIS
    # JAVA EXAMPLE ERROR
    # Bug 5924483 - ESB SHOULD SUPPORT SOAP EDNPOINT LOCATION DYNAMIC UDDI LOOKUP
    # Bug 5926809 - ORAPARSEESCAPEDXML XPATH EXPRESSION FAILED TO EXECUTE
    # FOTY0001 TYPE ERROR
    # Bug 5937320 - STRANGE BEHAVIOUR CALLING FROM BPEL TO BPEL GETTING
    # NULLPOINTEREXCEPTION.
    # Bug 5944641 - BPA BLUEPRINT NOT AVAIALBLE IN JDEVELOPER
    # Bug 5945059 - JAVA.LANG.NULLPOINTEREXCEPTION SENDING EMAILS WITH PAYLOADS
    # LARGER THAT 1MB
    # Bug 5962677 - WS RESPONSE IS EMPTY SOAP BODY IN ONE-WAY CALL
    # Bug 5963425 - WHEN THE OUTCOMES FOR A HT CHANGED & IMPORTED - UPDATE
    # CONNECTION ROLES IN BPEL
    # Bug 5964097 - AQ ADAPTER DEPLOYMENT CAUSES OPMN TO PERFORM A FORCEFUL
    # SHUTDOWN IN SOA
    # Bug 5971534 - CANNOT GRANT USER TASK VIEWS TO GROUPS, ONLY TO USERS.
    # Bug 5989367 - REFER TO SR 6252219.993 BPEL 10.1.3 ONLY COPIES IN ASSIGN,
    # IN 10.1.2 IT CREATES
    # Bug 5989527 - ENHANCEMENT WARNING SHOULD BE GIVEN UPON UPLOAD IF BPEL
    # PROCESS IS OPEN IN ARIS
    # Bug 5997936 - ESB FAULT DOES NOT GET PROPAGATED TO BPEL
    # Bug 6000575 - PERF NEED ESB PURGE SCRIPT TO PURGE BY DATE AND PROCESS
    # Bug 6001796 - POSTING OF DATE RECEIVED FROM XML GATEWAY TO BPEL FAILED IN
    # ESB
    # Bug 6005407 - BPEL PROCESS DOESN'T PROPOGATE FAULT THROWN BY BPEL
    # SUB-PROCESS
    # Bug 6017846 - MIMETYPE OF EMAIL NOTIFICATION IS NOT SET THROUGH HUMAN TASK
    # Bug 6027734 - DECISION SERVICE IMPORT - LOCATING DECISION SERVICE IN .DECS
    # FILE IMPROPER
    # Bug 6028985 - EXCEEDED MAXIMUM NUMBER OF SUBSCRIBERS FOR QUEUE
    # ORAESB.ESB_CONTROL
    # Bug 6041508 - CREATING/UPDATING DVM CAUSE EXCEPTION
    # Bug 6053708 - FTP ADAPTER DOES NOT SUPPORT ENCRYPTED PASSWORD IN
    # OC4J-RA.XML
    # Bug 6054034 - INDEX4,INDEX5 AND INDEX6 CANNOT BE USED IN BPEL CONSOLE
    # Bug 6068801 - BACKPORT OF BPEL ON WEBLOGIC - VERSION 10.1.3.3
    # Bug 6070991 - HT EXPORT DOES NOT EXPORT PARAMETERS, ALLOW PARTICIPANTS TO
    # INVITE OTHERS
    # Bug 6071001 - WSIF HTTP BINDING NOT WORKING FROM ESB
    # Bug 6073311 - STRESS SCOPE NOT FOUND ON CALLBACK - WRONG (DUPE)
    # SUBSCRIPTION IN TABLE
    # Bug 6081070 - JMS ADAPTER REJECTION HANDLER CREATE 0 BYTE FILES
    # Bug 6083419 - DECISION SERVICE SCOPE NEED TO HAVE A SPECIAL INDICATOR
    # Bug 6085799 - HUMAN TASK ADDED IN SCOPE IN JDEV IS NOT UPDATED TO BPA
    # SERVER
    # Bug 6085933 - EXPORT AND EXPLORE SHOULD USE USER LANGUAGE AND NOT ENGLISH
    # ALWAYS
    # Bug 6086281 - STRING INDEX OUT OF RANGE ERROR FOR COBOL COPYBOOK WITH PIC
    # CLAUSE HAVING S
    # Bug 6086453 - DOMAINS CREATED IN A CLUSTER GETS NOT PROPAGATED TO NEW OR
    # EXISTING NODES
    # Bug 6087484 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
    # Bug 6087645 - ESB SHOULD ALLOW USER PICK RUNTIME PROTOCOL (HTTP/HTTPS)
    # Bug 6110231 - TRANSLATION NOT BASED ON MQ CCSID CHARSET
    # Bug 6120226 - BPEL IS NOT SETTING THE APPS CONTEXT CORRECTLY
    # Bug 6120323 - COMPLETIONPERSISTPOLICY ON DOMAIN LEVEL HAS DISAPPEARED
    # Bug 6125184 - ESB JMS SESSION ROLLBACK ORACLE.JMS.AQJMSEXCEPTION
    # Bug 6127824 - [AIA2.0] CURRENT XREF IMPLEMENTATION IS MISSING REQUIRED
    # INDEXES ON XREF SCHEMA
    # Bug 6128247 - HTTPCONNECTOR POST() METHOD SHOULD RAISE EXCEPTION FOR ALL
    # STATUS CODES EXCEPT 2
    # Bug 6131159 - ENABLE USERS TO CHOOSE XSD WHEN CREATING A BPEL PROCESS FROM
    # BLUE PRINT
    # Bug 6132141 - PROCESS_DEFAULT TABLE STILL CONTAINS INFORMATION FROM
    # UNDEPLOYED PROCESSES
    # Bug 6133190 - ENABLING ESB CONSOLE HTTP/S IS MAKING THE CONSOLE TO COME UP
    # BLANK.
    # Bug 6139681 - BPEL WSDL LINK IN CLUSTERED RUNTIME POINTS TO A SINGLE NODE
    # Bug 6141259 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
    # BINDING IN BPEL
    # Bug 6148021 - BPEL NATIVE SCHEMA FOR COBOL COPYBOOK WITH IMPLIED DECIMAL
    # LOSES DIGIT IN OUTPUT
    # Bug 6149672 - XOR DATA - CONDITION EXPRESSION SPECIFICATION IS NOT
    # INTUITIVE IN BPMN MODELS
    # Bug 6152830 - LOSING CONDITIONAL EXPRESSIONS CREATED IN JDEV UPON MERGE
    # Bug 6158128 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
    # BINDING
    # Bug 6166991 - WHEN STARTING SOA SUITE,, PROCESSES FAIL DUE TO UNDEFINED
    # WSDL
    # Bug 6168226 - LOCATION-RESOLVER EXCEPTION THROWN IN OPMN LOGS
    # Bug 6187883 - CHANGES FOR BPEL RELEASE ON JBOSS- VERSION 10.1.3.3
    # Bug 6206148 - [AIA2.0] NEW FUNCTION REQUEST, XREFLOOKUPPOPULATEDCOLUMNS()
    # Bug 6210481 - BPEL PROCESS WORKS INCORRECTLY WHEN AN ACTIVITY HAS MULTIPLE
    # TRANSITIONCONDITION
    # Bug 6240028 - WEBSERVICE THAT DOES NOT CHALLENGE FOR BASIC CREDENTIALS
    # CANNOT BE INVOKED
    # Bug 6257116 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
    # Bug 6258925 - MESSAGE RECEIVED BY THE TARGET ENDPOINT VIA HTTP POST IS
    # MISSING THE XML HEADER
    # Bug 6259686 - TOO MANY UNNECESSARY WORKFLOW E-MAIL NOTIFICATIONS GENERATED
    # Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
    # BUSINESS EVENT
    # Bug 6272427 - WEBSPHERE BPEL FAILS FOR DATA RETRIEVAL OF SIZE 500+ KB
    # Bug 6276995 - MERGE SCOPE NAME IS NOT UPDATED WHEN CHANGED IN THE SERVER
    # Bug 6280570 - XPATH EXPRESSION ERROR IN MEDIATOR FOR ASSIGNING USER-DEFINED
    # CONTEXT VALUES
    # Bug 6282339 - RETRYCOUNT DOES NOT WORK PROPERLY
    # Bug 6311039 - ONE RECORD IS INSERTED TO SYNC_STORE IF
    # COMPLETIONPERSISTPOLICY SET TO FAULTED
    # Bug 6311809 - [AIA2.0] NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR
    # TOPIC
    # Bug 6314784 - THE PRIORITY DEFINED IN THE BPA SUITE IS NOT TRANSFERRED TO
    # THE JDEV CORRECTLY
    # Bug 6314982 - THREADPOOL RACE CONDITION IN ADAPTER INITIALIZATION MESSAGES
    # NOT PROCESSED
    # Bug 6315104 - (SET)CLASSNAME MISSING IN TSENSOR JAXB OBJECTS
    # Bug 6316554 - CONSUME FUNCTIONALITY OF JMS ADAPTER FOR BEA WEBLOGIC DOES
    # NOT WORK
    # Bug 6316950 - FILEADAPTER HARPER ENHANCEMENTS SYNC WRITE AND CHUNKED
    # INTERACTION SPEC
    # Bug 6317398 - THE ICON FOR COMPUTING DIFFERENCE IS MISSING IN JDEV REFRESH
    # FROM SERVER DIALOG
    # Bug 6320506 - IMPORT FAILS WHEN THERE IS AN UNNAMED CASE
    # Bug 6321011 - CANNOT PROCESS 0 BYTE FILE USING FTP ADAPTER
    # Bug 6325749 - TRACKING BUG FOR TRACKING ADDITIONAL CHANGES TO BUG #6032044
    # Bug 6328584 - NEED A NEW XPATH EXPRESSION TO GET ATTACHMENT CONTENT VIA
    # SOAP INVOKATION
    # Bug 6333788 - COLLAPSING OF CONSECUTIVE ASSIGN TASKS BREAKS BAM SENSOR
    # Bug 6335773 - BUILD.XML CONTAINS DO NOT EDIT .. - WHILE <CUSTOMIZE> TASK
    # MUST BE IN <BPELC>
    # Bug 6335805 - AQ ADAPTER OUTBOUND DOESN'T RECONNECT AFTER FAILURE
    # Bug 6335822 - [AIA2.0] PSRPERFESB - RUNTIME DVM PERFORMANCE OVERHEAD IN ABS
    # USE CASE
    # Bug 6339126 - CHECKPOINT BPEL JAVA METHOD DOESN'T WORK IN BPEL 10.1.3.3
    # Bug 6342899 - OUTLINECHANGE.XML NOT UPDATE WITH ACTIVITY FROM NEW BRANCH
    # Bug 6343299 - ESB CONCRETE WSDL NAMESPACE SHOULD BE DIFFERENT FROM IMPORTED
    # WSDL NAMESPACE
    # Bug 6372741 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3
    # Bug 6401295 - NXSD SHOULD SUPPORT ESCAPING THE TERMINATED/QUOTED/SURROUNDED
    # DELIMITERS
    # Bug 6458691 - DIST DIRECTORY FOR 10.1.3.3.1 NEEDS UPDATE
    # Bug 6461516 - BPEL CONSOLE CHANGES FOR DISPLAYING RELEASE 10.1.3.3.1
    # Bug 6470742 - CHANGE THE VERSION NUMBER AND BUILD INFO IN ABOUT DIALOG IN
    # ESB
    # BUG ADDED IN MLR#1, 6671813 :
    # Bug 6494921 - ORABPEL-02154 IF LONG DOMAIN AND SUITECASE NAMES IN USE
    # BUGS ADDED IN MLR#2, 6671831 :
    # Bug 6456519 - ERROR IN BPEL CONSOLE THREADS TAB:SERVLETEXCEPTION CANNOT GET
    # DISPATCHER TRACE
    # Bug 6354719 - WHICH JGROUP CONFIGURATION PARAMETER IMPACTS BPEL CLUSTER
    # ACTIVITY
    # Bug 6216169 - SCOPE NOT FOUND ERROR WHILE DELIVERING EXPIRATION MESSAGE OF
    # ONALARM
    # Bug 6395060 - ORA-01704 ON INSERTING A FAULTED INVOKE ACTIVITY_SENSOR
    # Bug 6501312 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3 #2
    # Bug 6601020 - SEARCHBASE WHICH INCLUDES PARENTHESIS IN THE NAMES DOES NOT
    # WORK
    # Bug 6182023 - WAIT ACTIVITY FAILS TO CONTINUE IN CLUSTER WHEN PROCESSING
    # NODE GOES DOWN
    # BUGS ADDED IN MLR#3, 6723162 :
    # Bug 6725374 - INSTANCE NOT FOUND IN DATASOURCE
    # Bug 4964824 - TIMED OUT IF SET CORRELATIONSET INITIATE YES IN REPLY
    # ACTIVITY
    # Bug 6443218 - [AIA2.0]BPEL PROCESS THAT REPLIES A CAUGHT FAULT AND THEN
    # RETHROWS IT IS STUCK
    # Bug 6235180 - BPPEL XPATH FUNCTION XP20 CURRENT-DATETIME() IS RETURNING AN
    # INCORRET TIME
    # Bug 6011665 - BPEL RESTART CAUSES ORABPEL-08003 FAILED TO READ WSDL
    # Bug 6731179 - INCREASED REQUESTS CAUSE OUTOFMEMORY ERRORS IN OC4J_SOA WHICH
    # REQUIRES A RESTART
    # Bug 6745591 - SYNC PROCESS <REPLY> FOLLOWED BY <THROW> CASE CAUSING
    # OUTOFMEMORY ERRORS
    # Bug 6396308 - UNABLE TO SEARCH FOR HUMAN TASK THAT INCLUDES TASK HISTORY
    # FROM PREVIOUS TASK
    # Bug 6455812 - DIRECT INVOCATION FROM ESB ROUTING SERVICE FAILS WHEN CALLED
    # BPEL PROCESS
    # Bug 6273370 - ESBLISTENERIMPL.ONFATALERROR GENERATING NPE ON CUSTOM ADAPTER
    # Bug 6030243 - WORKFLOW NOTIFICATIONS FAILING WITHOUT BPELADMIN USER
    # Bug 6473280 - INVOKING A .NET 3.0 SOAP SERVICE EXPOSED BY A ESB ENDPOINT
    # GIVES A NPE
    # BUGS ADDED IN MLR#4, 6748706 :
    # Bug 6336442 - RESETTING ESB REPOSITORY DOES NOT CLEAR DB SLIDE REPOSITORY
    # Bug 6316613 - MIDPROCESS ACTIVATION AGENT DOES NOT ACTIVATED FOR RETIRED
    # BPEL PROCESS
    # Bug 6368420 - SYSTEM IS NOT ASSIGNING TASK FOR REAPPROVAL AFTER REQUEST
    # MORE INFO SUBMITTED
    # Bug 6133670 - JDEV: UNABLE TO CREATE AN INTEGRATION SERVER CONNETION WHEN
    # ESB IS ON HTTPS
    # Bug 6681055 - TEXT ATTACHMENT CONTENT IS CORRUPTED
    # Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
    # Bug 5521385 - [HA]PATCH01:ESB WILL LOSE TRACKING DATA WHEN JMS PROVIDER IS
    # DOWN
    # Bug 6759068 - WORKLIST APPLICATION PERFORMANCE DEGRADATION W/ SSL ENABLED
    # FOR BPEL TO OVD
    # BUGS ADDED IN MLR#5, 6782254 :
    # Bug 6502310 - AUTOMATED RETRY ON FAILED INVOKE WITH CORRELATIONSET INIT
    # FAILS
    # Bug 6454795 - FAULT POLICY CHANGE NEEDS RESTART OF BPEL SERVER
    # Bug 6732064 - FAILED TO READ WSDL ERROR ON THE CALLBACK ON RESTARTING BPEL
    # OC4J CONTAINER
    # Bug 6694313 - ZERO BYTE FILE WHEN REJECTEDMESSAGEHANDLERS FAILS
    # Bug 6686528 - LINK IN APPLICATION.XML FILES CHANGED TO HARD LINKS WHEN MORE
    # THAN 1 HT PRESENT
    # Bug 6083024 - TEXT AND HTML DOC THAT RECEIVED AS ATTACHMENTS WERE EITHER
    # BLANK OR GARBLED
    # Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
    # Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
    # BUSINESS EVENT
    # Bug 6774981 - NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR TOPIC
    # Bug 6789177 - SFTP ADAPTER DOES NOT SUPPORT RENAMING FILES
    # Bug 6809593 - BPEL UPGRADE TO 10.1.3.3.1 WITH ESB CALLS FAILS DUE TO
    # CACHING OF PLNK - SERVICE
    # BUGS ADDED IN MLR#6, 6823628 :
    # Bug 6412909 - <BPELX:RENAME> DOES NOT ADD XMLNS DECLARATION AUTOMATICALLY
    # Bug 6753116 - OUTPUT FROM HUMAN TASK IS NOT IS NOT CONSISTENT WITH
    # SCHEMA
    # ORDERING
    # Bug 6832205 - BAD VERIFICATIONSERVICE PERFORMANCE IF LDAP SERVICE HAS HUGE
    # DATA
    # Bug 6189268 - CALLING BPEL PROCESS VIA SOAP FROM ESB FAILS WITH
    # NAMENOTFOUNDEXCEPTION
    # Bug 6834402 - JMS ADAPTER IMPROPERLY CASTS XAQUEUESESSION TO QUEUESESSION
    # Bug 6073117 - TASK SERVICE DOESN'T RENDER THE TASK ACTIONS
    # Bug 6054263 - REUSING SOAP WSDL IN RS CAUSES SOAP ACTION'S NS TO BE
    # STRIPPED
    # AWAY
    # Bug 6489703 - ESB: NUMBER OF LISTENERS > 1 GIVES JMS EXCEPTION UNDER STRESS
    # Bug 5679542 - FTP ADAPTER: COULD NOT PARSE TIME:
    # JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION
    # Bug 6770198 - AQ ACTIVATIONINSTANCES >1 DOESN'T WORK IN ESB
    # Bug 6798779 - ESB ROUTING RULES CORRUPTED ON RE-REGISTERING WITH ROUTING
    # ORDER
    # IN WSDL CHANGED
    # Bug 6617974 - BACKPORT REQUEST FOR MOVING FILES FUNCTION OF FTP ADAPTER
    # Bug 6705707 - VALIDATION ON ESB CAN'T HANDLE NESTED SCHEMAS
    # Bug 6414848 - FTP ADAPTER ARCHIVE FILENAME FOR BPEL IS BEING SCRAMBLED
    # AFTER
    # THE 10.1.3.3 UPGR
    # Bug 5990764 - INFORMATION ARE LOST WHEN BPEL PROCESS IS POLLING FOR MAILS
    # WITH
    # ATTACHEMENTS
    # Bug 6802070 - ORA-12899 SUBSCRIBER_ID/RES_SUBSCRIBER COLUMN SMALL FOR LONG
    # DOMAIN AND PROCESS
    # Bug 6753524 - WRONG SERVICE ENDPOINT OPEN WHEN TEST WEB SERVICE OF ESB
    # Bug 6086434 - PROBLEM IN BPEL FILE ADAPTER WHILE READING A FIXED LENGTH
    # FILE
    # Bug 6823374 - BPEL 10.1.3.3.1 BAM SENSOR ACTION FAILS WITH BAM 11
    # Bug 6819677 - HTTS STATUS 202 RETURNED INSTEAD OF SOAP FAULT
    # Bug 6853301 - MQ ADAPTER REJECTED MESSAGES IS NOT REMOVED FROM THE RECOVERY
    # QUEUE
    # Bug 6847200 - 10.1.3.3.1 PATCH (#6748706) HAS STOPPED FTP ADAPTER POLLING
    # IN
    # SFTP MODE
    # Bug 6895795 - AQ OUTBOUND DOESN'T WORK WITH MLR#6
    업무에 참고하시기 바랍니다.

    David,
    You are right, theer are some changes incorporated in the latest MLR # 16 on the configurations files and on the dehydration store metrics(such as performance, fields,..).
    However, I would not suggest to continue working on olite, even for Development/Test purposes as you might get stuck with strange errors...and the only solution would be to re-install SOA Suite if your olite gets corrupted. There might be ways to gets your olite back to position, but trust me..its not so simple.
    Also, when you develop and stress test all your testcase scenarios in an TEST Adv installation, its simple to mimic the same in actual production box, as you exactly know its behavior.
    So, go for a brand new SOA 10.1.3.4 MLR # 5 (or) 10.1.3.3.1 MLR # 16 SOA Suite Advanced installation with Oracle DB 10.2.0.3 as its dehydration store.
    Hope this helps!
    Cheers
    Anirudh Pucha

  • How do you use WLST to get a deployed Apps name?

    I am writing an application update script to make updating our environments quicker/easier with the following code from an ant build file:
    <wlst debug="true" failOnError="true">
    <script>
    connect('login','pwd','t3://...')
    updateApplication('${app.name}',block='true')
    </script>
    </wlst>
    However, b/c our application has a version in the manifest file, our application name looks like this:
    AppName-BuildNumber-TimeOfBuild
    Since the TimeOfBuild is always different from build to build it is impossible to hard code this value. Is there a way to get the application's name using WLST?
    connect(...)
    cd('AppDeployments')
    This shows me all applications deployed on the server, but inorder to go any farther I need the name of a specific app. I'm sure I am just overlooking an mbean somewhere, but I can't seem to find it! Any ideas??
    Thanks.
    Message was edited by:
    bftanner

    Ok, so I figured out how to get an applications name but I can't get the following script to work from an ant build file:
    <wlst debug="true" failonerror="false">
    <script>
    connect('system','weblogic','t3://...')
    apps=cmo.getAppDeployments()
    for app in apps:
    if app.getName().startswith("4X"):
    stopApplication(app,block='true')
    undeploy(app.getName(),targets='MS1,MS2',block='true')
    deploy('4X','//box/domains/applications/4X.ear',targets='MS1,MS2',stageMode='stage',block='true')
    apps=cmo.getAppDeployments()
    for app in apps:
    if app.getName().startswith("4X"):
         startApplication(app.getName(),block='true')
    </script>
    </wlst>
    When this is run I get the following error:
    BUILD FAILED
    C:\docume~1\dtanner\desktop\RELupdate.xml:134: Error executing the script snippe
    t
    connect('system','weblogic','t3://192.168.0.250:
    7001')
    apps=cmo.getAppDeployments()
    for app in apps:
    if app.getName().startswith("reporting-r
    eport"):
    stopApplication(app,block='true'
    undeploy(app,targets='MS1,MS2',b
    lock='true')
    deploy('reporting-report-server','//bfediapp3/do
    mains/applications/reporting-report-server.war',targets='MS1,MS2',stageMode='sta
    ge',block='true')
    apps=cmo.getAppDeployments()
    for app in apps:
    if app.getName().startswith("reporting-r
    eport"):
    startApplication(app,block='true
    due to:
    Traceback (innermost last):
    (no code object) at line 0
    SyntaxError: ('invalid syntax', ('<string>', 2, 33, '\t\t\t\tapps=cmo.getAppDepl
    oyments()'))
    Any Ideas??? Also, how can you keep the format i.e. tabs and spaces at the front of a line in these forums???
    Thanks.

  • OIM Installn :java.lang.RuntimeException: Could not find OffLine WLST class

    Installation of OIM On weblogic.
    oracle/oim/xellerate/setup/setup.xml:443: The following error occurred while executing this line:
    /oracle/oim/xellerate/setup/weblogic-setup.xml:196: java.lang.RuntimeException: Could not find the OffLine WLST class
         at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539)
         at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
         at org.apache.tools.ant.Task.perform(Task.java:364)
         at org.apache.tools.ant.Target.execute(Target.java:341)
         at org.apache.tools.ant.Target.performTasks(Target.java:369)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
         at org.apache.tools.ant.Main.runBuild(Main.java:668)
         at org.apache.tools.ant.Main.startAnt(Main.java:187)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
    Tried to run this command ./wlst.sh
    shows
    CLASSPATH=/home/oracle/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/jdk/lib/tools.jar:/oracle/weblogic/server/server/lib/weblogic_sp.jar:/oracle/weblogic/server/server/lib/weblogic.jar:/home/oracle/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/oracle/weblogic/server/server/lib/webservices.jar:/home/oracle/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/oracle/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:
    PATH=/oracle/weblogic/server/server/bin:/home/oracle/bea/modules/org.apache.ant_1.6.5/bin:/oracle/jdk/jre/bin:/oracle/jdk/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/oracle/bin:/home/oracle/bin:/oracle/jdk/bin
    Your environment has been set.
    CLASSPATH=/home/oracle/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/jdk/lib/tools.jar:/oracle/weblogic/server/server/lib/weblogic_sp.jar:/oracle/weblogic/server/server/lib/weblogic.jar:/home/oracle/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/oracle/weblogic/server/server/lib/webservices.jar:/home/oracle/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/oracle/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/oracle/weblogic/server/common/eval/pointbase/lib/pbembedded57.jar:/oracle/weblogic/server/common/eval/pointbase/lib/pbtools57.jar:/oracle/weblogic/server/common/eval/pointbase/lib/pbclient57.jar
    Initializing WebLogic Scripting Tool (WLST) ...
    Problem invoking WLST - java.lang.RuntimeException: Could not find the OffLine WLST class
    Edited by: user10213645 on Mar 9, 2010 3:37 PM

    There is an existing Bug 8431390 - WLST NOT WORKING IF WE USE NON-DEFAULT INSTALLATION (WL_HOME OUTSIDE BEA_HOME)
    As per this bug, the issue can be reproduced as follows:
    Steps to reproduce:
    1. Install WLS 10.3GA (essex) kit in a non-default fashion (WL_HOME outside BEA_HOME)
    2. Go to ur $WL_HOME/common/bin directory and execute wlst.cmd
    3. It exits with the following exception:
    java.lang.RuntimeException:could not find the OffLine WLST class
    Hope this helps.
    For more details, refer: http://idm-oracle.blogspot.com/2010/03/javalangruntimeexception-could-not-find.html

  • Problem setting the PoolList attribute in a WLST script

    Hello !
    I ran the configToScript command over config.xml which has a JDBCMultipool composed of two JDBCpools. It threw the next script to create the JDBC Multipool:
    print 'configuring resource: JDBCMultiPool/MyJDBC MultiPool '
    try:
    myResource = create("MyJDBC MultiPool","JDBCMultiPool")
    except Exception:
    # print 'This resource JDBCMultiPool with name MyJDBC MultiPool failed to be created. The script will try to get it anyways.'
    myResource = (getTarget("JDBCMultiPool/MyJDBC MultiPool"))
    myResource.setPoolList("poolCatalogos01,poolCatalogos02")
    #cmo.addTarget(clusterTarget2)
    # If this fails you will have to add this target manually from the console
    from java.lang import Exception
    from java.lang import Throwable
    try:
    myResource.addTarget(clusterTarget2)
    except Throwable, th:
    print 'Problem in adding target '+clusterTarget2+ ' due to '+th.toString()
    However when the script is executed it fails at the line:
    myResource.setPoolList("poolCatalogos01,poolCatalogos02")
    and shows this error message:
    TypeError: setPoolList(): 1st arg can't be coerced to weblogic.management.configuration.JDBCConnectionPoolMBean[]
    I have tried some other ways to set this attribute, however I hadn't had any success. If some one can provide some advice, I will be grateful.
    By the way:
    I am using a WLST version downloaded last April, of 2004.
    Thanks !

    There is a bug in configToScript that is not generating the right script for setting the Pool list. This will be fixed in the next version of wlst. Here's a workaround.
    try:
    myResource = create("MyJDBC MultiPool","JDBCMultiPool")
    except Exception:
    # print 'This resource JDBCMultiPool with name MyJDBC MultiPool failed to be created. The script will try to get it anyways.'
    myResource = (getTarget("JDBCMultiPool/MyJDBC MultiPool"))
    p1 = getTarget("JDBCConnectionPool/poolCatalogos02")
    p2 = getTarget("JDBCConnectionPool/poolCatalogos02_BEA")
    plist = jarray.array([p1,p2], weblogic.management.configuration.JDBCConnectionPoolMBean)
    myResource.setPoolList(plist)
    let me know if u see any other problems, thanks,
    -satya

  • File seek in wlst fails for lines longer than 8091 characters

    For a CSV file generated in WLST i want to update the header, the first line of the output file, when new metrics have been detected. This works fine by using seek to go to the first line and overwriting the line. But it fails when the number of characters of the first line exceeds 8091 characters.
    I made simplified script which does reproduce the issue i am facing here.
        #!/usr/bin/python
        import sys
        global maxheaderlength
        global initheader
        maxheaderlength=8092
        logFilename = "test.csv"
        # Create (overwrite existing) file
        logfileAppender = open(logFilename,"w",0)
        logfileAppender.write("." * maxheaderlength)
        logfileAppender.write("\n")
        logfileAppender.close()
        # Append some lines
        logfileAppender = open(logFilename,"a",0)
        logfileAppender.write("2nd line\n")
        logfileAppender.write("3rd line\n")
        logfileAppender.write("4th line\n")
        logfileAppender.write("5th line\n")
        logfileAppender.close()
        # Seek back to beginning of file and add data
        logfileAppender = open(logFilename,"r+",0)
        logfileAppender.seek(0) ;
        header = "New Header Line" + "." * maxheaderlength
        header = header[:maxheaderlength]
        logfileAppender.write(header)
        logfileAppender.close()
    When maxheaderlength is 8091 or lower i do get the results as expected. The file test.csv starts with “New Header Line" followed by 8076 dots and followed by the lines 2nd line 3rd line 4th line 5th line
    When maxheaderlength is 8092> the test.csv results as a file starting with 8092 dots followed by "New Header Line" and then followed by 8077 dots. The 2nd ... 5th line are now show, probably overwritten by the dots.
    Any idea how to work around or fix this ?

    For the benefit of others, i got a workaround from Jeremy Gosling on a crosspost on stackoverflow.
    I too was able to reproduce this extremely odd behaviour and indeed it works correctly in Jython 2.5.3 so I think we can safely say this is a bug in 2.2.1 (which unfortunately you're stuck with for WLST).
    My usual recourse in these circumstances is to fall back to using native Java methods. Changing the last block of code as follows seems to work as expected :-
    # Seek back to beginning of file and add data
    from java.io import RandomAccessFile
    logfileAppender = RandomAccessFile(logFilename, "rw")
    logfileAppender.seek(0) ;
    header = "New Header Line" + "." * maxheaderlength
    header = header[:maxheaderlength]
    logfileAppender.writeBytes(header)
    logfileAppender.close()

  • Beginner can't undeploy auto-deployed web app

    Hi.
    (I am brand new to WLS 10. I am testing it for a possible upgrade from WLS 8.)
    I auto-deployed a web application Weblogic Server 10.0. Now I am trying to undeploy it, but I just can't seem to make it go away. I first tried the delete button in the admin console, but that says "The application _appsdir_ch1_war was autodeployed and may only be deleted by removing the file(s) from the domain autodeploy directory."
    So then I deleted the file from the autodeploy directory and restarting the server.
    But it's still there.
    I'm about to edit the config.xml manually, which I'm SURE will work, but that can't be the proper way to get rid of autodeployed apps, surely. So, before I do that, I ask here how one removes autodeployed applciations from a WLS 10 server.
    Thanks for your help in advance!!!
    John

    The docs are here:
    http://edocs.bea.com/wls/docs100/deployment/autodeploy.html#wp1021620
    Once you delete the file in the autodeploy directory, I think you have several options:
    1) Use the console to remove it
    2) weblogic.Deployer command line http://edocs.bea.com/wls/docs100/deployment/wldeployer.html
    3) WLST - http://blogs.oracle.com/jamesbayer/2007/10/automate_wls_console_tasks_wit.html
    4) Delete from the config file (not recommended)
    You're easiest option is probably either 1 or 2 if you're just getting started.

Maybe you are looking for