Weblogic.Admin utility !!!

Hi All,
Will weblogic.Admin utility cause any load on the servers (performance issue), if used extensively to get the below runtime data of a domain
--> server state using GETSTATE
--> ExecuteQueueRuntime
--> JMSDestinationRuntime
--> MessagingBridgeRuntime
weblogic version : 8.1 sp5
Cheers,
Thalla.

Hi Thalla,
One of our Production Env is setup to fetch Thread Dumps and Many kind of Runtime Details of <b>WLS 9.2 MP2</b> using "weblogic.Admin" utility Over SSL ...<b>At regular Interval of 6-Minutes</b> From past 2-3 Years we never saw any Performance related issue because of this utility...
I hope the same behaviour we will find in WLS8.1 SP5 as well.. as we have already tested it in WLS9.2 MP2 ..so i can assure you that In WLS9.2 MP2...It works with Charm without any performance impact...And I expect that It will Just work Extremely great in WLS8.1 SP5 as well..
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com/2009/12/31/debugging-runtime-informations-at-a-glance/

Similar Messages

  • Returncode of weblogic.Admin Utility

    i try to check my WLS server with the following command:
    "java -cp $CLASSPATH weblogic.Admin t3://myserver:7001 PING 3 100 system
    weblogic"
    i doesn't matter if the command fails or was successfull i allways get
    returncode 0 when typing "echo $?" as the screenshot shows:
    # java -cp $CLASSPATH weblogic.Admin t3://myserver:7895 PING 3 100 system
    weblogic
    Failed to connect to t3://myserver:7895 due to: [java.net.ConnectException:
    No server found at T3://myserver:7895]
    # echo $?
    0
    Anybody any idea how to manage this?
    alexander

    Alexander,
    Currently, there is not a plan in place to backport the requested
    functionallity to WLS 5.1.
    Thanks,
    Simon Nunn
    Developer Relations Engineer
    BEA Technical Support
    Alexander von Alkier wrote:
    "Glenn Dougherty" <[email protected]> schrieb im Newsbeitrag
    news:[email protected]..
    Alexander,
    This is a known issue with the weblogic.Admin utility. BEA is planning tofix
    this and provide proper return codes in the next major release (probablywithin
    6 months).
    Regards,
    Glenn Dougherty
    Developer Relations Engineer
    BEA Technical Support
    Alexander von Alkier wrote:
    i try to check my WLS server with the following command:
    "java -cp $CLASSPATH weblogic.Admin t3://myserver:7001 PING 3 100 system
    weblogic"
    i doesn't matter if the command fails or was successfull i allways get
    returncode 0 when typing "echo $?" as the screenshot shows:
    # java -cp $CLASSPATH weblogic.Admin t3://myserver:7895 PING 3 100
    system
    weblogic
    Failed to connect to t3://myserver:7895 due to:[java.net.ConnectException:
    No server found at T3://myserver:7895]
    # echo $?
    0
    Anybody any idea how to manage this?
    alexanderso i have no chance to do this with WLS 5.1?
    alexander

  • Unable to start Admin server by using weblogic.admin utility

    Hi,
    I stoped the admin server by using weblogic.admin utility command as bellow.
    java weblogic.Admin -url http://server1:8008 -username adminuser -password weblogic SHUTDOWN myserver
    It stopped successfully. But while starting as below i am getting error. Kindly help me out.
    java weblogic.Admin -url http://172.27.72.70:8008 -username adminuser -password weblogic START myserver
    <Warning> <Net> <BEA-000905> <Could not open connection with host: server1 and port: 8008.>
    Failed to connect to http://172.27.72.70:8008: Destination unreachable; nested exception is:
    java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'star', port: '8008'; No available router to destination
    Any suggestion is appreciated.
    Thanks,

    Hi,
    Thanks for your reply.
    Yes, Node Manager has configured on Managed Server's host machine.
    So can't we start admin server by using weblogic.admin utility if admin server is stopped?
    Thanks,

  • Using weblogic.Admin utility with Weblogic 10.0

    I am trying to write a script which perform PING server to ensure weblogic servers are up before moving on to start another server (the script starts all managed and admin servers), i used to be able to PING server on weblogic 8.1 using weblogic.Admin utility but on weblogic 10.3 i am getting the following exception:
    java.lang.NoClassDefFoundError: weblogic/transaction/internal/TransactionHelperImpl
    at weblogic.jndi.spi.EnvironmentManager$DefaultFactoryMaker.<clinit>(EnvironmentManager.java:26)
    at weblogic.jndi.spi.EnvironmentManager.getInstance(EnvironmentManager.java:48)
    at weblogic.jndi.Environment.getContext(Environment.java:307)
    at weblogic.jndi.Environment.getContext(Environment.java:277)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
    at weblogic.management.commandline.tools.AdminToolHelper.getMBeanHome(AdminToolHelper.java:559)
    at weblogic.management.commandline.tools.ServerInfoCommandLineInvoker.doCommandline(ServerInfoCommandLineInvoker.java:920)
    at weblogic.management.commandline.tools.ServerInfoCommandLineInvoker.<init>(ServerInfoCommandLineInvoker.java:116)
    at weblogic.management.commandline.AdminMain.main(AdminMain.java:132)
    at weblogic.Admin.useAdminMain(Admin.java:43)
    at weblogic.Admin.main(Admin.java:22)
    java.lang.NoClassDefFoundError: weblogic/transaction/internal/TransactionHelperImpl
    at weblogic.jndi.spi.EnvironmentManager$DefaultFactoryMaker.<clinit>(EnvironmentManager.java:26)
    at weblogic.jndi.spi.EnvironmentManager.getInstance(EnvironmentManager.java:48)
    at weblogic.jndi.Environment.getContext(Environment.java:307)
    at weblogic.jndi.Environment.getContext(Environment.java:277)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
    at weblogic.management.commandline.tools.AdminToolHelper.getMBeanHome(AdminToolHelper.java:559)
    at weblogic.management.commandline.tools.ServerInfoCommandLineInvoker.doCommandline(ServerInfoCommandLineInvoker.java:920)
    at weblogic.management.commandline.tools.ServerInfoCommandLineInvoker.<init>(ServerInfoCommandLineInvoker.java:116)
    at weblogic.management.commandline.AdminMain.main(AdminMain.java:132)
    at weblogic.Admin.useAdminMain(Admin.java:43)
    at weblogic.Admin.main(Admin.java:22)
    The Classpath i am using:
    /ascddata3/olcppads-dev01/weblogic10/server/lib/weblogic.jar:/ascddata3/olcppads-dev01/weblogic10/user_projects/autosc_pss/lib:/ascddata3/olcppads-dev01/weblogic10/server/lib/xmlx.jar:/ascddata3/olcppads-dev01/weblogic10/server/lib/wls-api.jar:/ascddata3/olcppads-dev01/weblogic10/server/lib/wlclient.jar:/ascddata3/olcppads-dev01/weblogic10/server/lib/wljmsclient.jar
    The command i am using is:
    java weblogic.Admin -url ins2d.med.ge.com:9010 -username USERNAME -password PASSWORD PING -verbose
    In weblogic 8.1 the class weblogic/transaction/internal/TransactionHelperImpl used to be present in wljtaclient.jar but i can't locate the class anywhere in weblogic 10.3/server/lib. Kindly let me know how to use weblogic.Admin utility on weblogic 10.3

    Hi,
    First I ran the setDomainEnv.cmd script to set the environment and then executed the weblogic.Admin command and it worked for me.
    D:\wls103\user_projects\domains\816532Local>java weblogic.Admin -adminurl t3://localhost:7010 -username weblogic -password weblogic PING
    Sending 1 ping of 100 bytes.
    RTT = ~16 milliseconds, or ~16 milliseconds/packet
    D:\wls103\user_projects\domains\816532Local>
    Regards.

  • Java weblogic.Admin Utility

    Hi All,
    Im using java weblogic.Admin utility to monitor the Weblogic Resources,in local it is working fine .....but when i move the code to production environment im getting the error message "NO Mbeans Found".....please help me to resolve this issue
    Note: im using weblogic 10.3
    commands im using
    java weblogic.Admin -url t3://IP:PORT -username USRNAME -password PWD GET -pretty -type JVMRuntime -property HeapSizeCurrent
    java weblogic.Admin -url t3://IP:PORT -username USRNAME -password PWD GET -pretty -type JVMRuntime -property HeapFreeCurrent
    java weblogic.Admin -url t3://IP:PORT -username USRNAME -password PWD GET -pretty -type JDBCConnectionPoolRuntime -property Name -property State -property ActiveConnectionsHighCount -property CurrCapacity -property MaxCapacity
    java weblogic.Admin -url t3://IP:PORT -username USRNAME -password PWD GET -pretty -type JMSServerRuntime -property Name -property MessagesCurrentCount -property MessagesPendingCount -property MessagesReceivedCount
    java weblogic.Admin -url t3://IP:PORT -username USRNAME -password PWD GET -pretty -type JMSDestinationRuntime -property Name -property MessagesCurrentCount -property MessagesPendingCount -property MessagesReceivedCount

    Hi Ashwin,
    If you do "GET -pretty -type JVMRuntime" then definately u shouldnot get the "No MBeans Found" because every WLS Server binds the JVMRuntime Object.
    But for others "JMSDestinationRuntime" and "JMSServerRuntime" and "JDBCConnectionPoolRuntime" MBeans it is possible that u may get "No MBeans Found" if you try to run the weblogic.Admin utility by passing the URL of a Server which is not a target of any JDBC/JMS systems.
    It means if we haven't targeted any DataSource or JMSServer/Resources to any WebLogic Server then in that case there will be no MBean registry inside that Server. In that case u will find *"No MBeans Found"*
    Example
    <h3><font color=maroon>Secnario-A</font></h3> Suppose I have created a DataSource (DS1) and targeted it to ManagedServer (MS1) but while executing "weblogic.Admin" utility if i will pass the URL of ManagedServer (MS2) or AdminServer then I will get "No MBeans Found" Because that JDBCConnectionPoolRuntime is not available on MS2 or in AdminServer.
    <h3><font color=maroon>Secnario-B</font></h3>
    <font color=red>
    Even if u are passing the Correct Target Server URL to the weblogic.Admin utility .... though there is also another Possible Reason in which u will get *"No MBeans Found"*.....When the JDBCPool is in Disabled State. It Means as soon as a Module JMS/JDBC/...etc gets Disabled...It's MBean Object gets destroyed (Unregistered). SO Please make sure that all your JDBC or JMS resources are Active and Running properly....
    </font>
    Please refer to : http://weblogic-wonders.com/weblogic/2009/12/31/debugging-runtime-informations-at-a-glance/#comment-356 as well.
    Thanks
    Jay SenSharma

  • Unable  to start weblogic.admin utility

    Hi,
    I am getting "Can't find class weblogic.Admin" error When I were running the command
    "java weblogic.Admin t3://<ip>:7005 version".
    The version of weblogic server I am runnng is 5.1 SP6.
    Please help.
    Thanks
    Yxu

    you have to set your environment before running the following command.
    There's a setEnv.cmd in your weblogic-home
    Kumar
    "Yxu" <[email protected]> wrote in message
    news:3c977e17$[email protected]..
    >
    Hi,
    I am getting "Can't find class weblogic.Admin" error When I were runningthe command
    "java weblogic.Admin t3://<ip>:7005 version".
    The version of weblogic server I am runnng is 5.1 SP6.
    Please help.
    Thanks
    Yxu

  • Setting timeout in weblogic.admin command

    Hello:
    I run a script that checks the state of several thing in my platform. One of the commands I use in this script
    is
    java -cp .. weblogic.Admin localhost:7001 ..... GETSTATE
    IS there anyway to set a timeout in this command for the case weblogic server is hang and doesn´t answer anything. I have tried using sun properties for connect timeout and readTimeout but they haven´t worked(I suppose that it is because weblogic.admin uses t3 instead http). I have thought to make the following
    sleep 10|ps -efx| grep -i GETSTATE|grep -v grep|awk '{ print $2 }'|xargs kill -9 &
    java -cp .. weblogic.Admin localhost:7001 ..... GETSTATE
    but I don´t like at all this solution
    Regards,
    Mario.

    hi sir,
    I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
    If u want to use WLST for starting managed servers and clusters
    check the follwing steps.
    1. java weblogic.WLST
    2. startNodeManager()
    3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
    4. TAKE ANOTHER COMMAND PROMPT
    java weblogic.WLST
    5. start('man1','Server') or start('man1','Server','localhost:7003')
    6. start('mycluster','Cluster')
    7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
    8.shutdown('mycluster','Cluster')
    regards
    abhi
    Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

  • Weblogic.Admin command for stopping all Managed Servers in cluster

    Hello All,
    I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
    I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
    I am looking for a way to do that using java weblogic.Admin utility
    Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
    Thanks
    Weblogic Consultant

    hi sir,
    I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
    If u want to use WLST for starting managed servers and clusters
    check the follwing steps.
    1. java weblogic.WLST
    2. startNodeManager()
    3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
    4. TAKE ANOTHER COMMAND PROMPT
    java weblogic.WLST
    5. start('man1','Server') or start('man1','Server','localhost:7003')
    6. start('mycluster','Cluster')
    7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
    8.shutdown('mycluster','Cluster')
    regards
    abhi
    Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

  • Weblogic.admin script to alert server status

    Hi,
    Can anybody share a weblogic.admin utility script for alerting the server status in unix ?

    Below is the solaris shell script integrated with weblogic.admin utility....
    If the server status is other than running it will sends a alert mail to you.
    Sometime your server may be in shutdown mode and if you execute the below script, it says destination not reachable on specified port and then also it sends a alert mail.
    Change it according to ur env and execute...
    set -x
    export CLASSPATH=”/wl_home/server/lib/weblogic.jar”
    declare -a Port=( 8003 7072 8201 )
    declare -a ServerState[]
    declare -a ServerName[]
    declare -a ObjectName[]
    i=”0″
    IP=Weblogic host address
    while [ $i -lt 5 ]
    do
    ServerState[$i]=`java weblogic.Admin -url $IP:${Port[$i]} -username weblogic -password weblogic GET -pretty -type ServerRuntime -property State |grep -i State |awk ‘{print $2}’`
    ObjectName[$i]=`java weblogic.Admin -url $IP:${Port[$i]} -username weblogic -password password GET -pretty -type JVMRuntime -property ObjectName |grep -i ObjectName |awk ‘{print $2}’`
    if [ "${ServerState[$i]}” != “RUNNING” ] ;
    then
    mailx -s ” Weblogic Server Staus- $IP ” [email protected]<<EOF
    Weblogic Managed server ${Port[$i]} is in SHUTDOWN state
    EOF
    fi
    i=`expr $i + 1`
    done
    Thanks,
    Kartheek
    Troubleshooting in weblogic gives thrilling experience .......

  • Weblogic.Admin - get Servlet Runtimes

    Hi!
    I want to grab with an application the servlet runtimes of my web application. I know that I have to use the weblogic.Admin utility (Am I right???). Also, I try to find the syntax to access to the property of the runtimes.
    For example: I want to know the "Execution Time Average" of the servlet path "/jsp/app/buyer/defaults.jsp/". My Application is "Maxtest". How can I invoke weblogic.Admin to get the value of the property?
    Thanks a lot!
    Yann

    can't understand why, but a reinstall solved my problem :((
    Joseph

  • Weblogic.Admin command

    After I ran setEnv.sh, I used Java weblogic.Admin command for THREAD_DUMP, it produced error "Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Admin
    ". What would be the best way to run a THREAD_DUMP, kill -3 PID or a java command?

    hi sir,
    I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
    java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
    If u want to use WLST for starting managed servers and clusters
    check the follwing steps.
    1. java weblogic.WLST
    2. startNodeManager()
    3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
    4. TAKE ANOTHER COMMAND PROMPT
    java weblogic.WLST
    5. start('man1','Server') or start('man1','Server','localhost:7003')
    6. start('mycluster','Cluster')
    7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
    8.shutdown('mycluster','Cluster')
    regards
    abhi
    Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

  • Weblogic Admin server restart issue

    While restarting Oracle Weblogic Admin server, it is not running after below log.
    INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
    Mar 12, 2015 7:33:07 PM oracle.security.jps.internal.idstore.util.LibOvdUtil pushLdapNamesToLibOvd
    INFO: Pushed ldap name and types info to libOvd. Ldaps : DefaultAuthenticator:idstore.ldap.provideridstore.ldap.

    Hi,
    These messages are Info Message Can you please post the complete Error stack for the same
    Check the below threads which have similar issue reported
    Integrated JDeveloper Weblogic 12C issues
    Weblogic server not starting due to OutOfMemory
    SOA Suite 12c Integrated Weblogic / Coherence Issue
    Unable to run my application
    Hope it helps

  • WebLogic Admin server fails to start after reboot

    Hi Gurus,
    Weblogic Admin server won't start up after a server reboot. Note that weblogic was gracefully shutdown before the restart.
    Also note that the following files were accidentally deleted after the reboot (but I don't think that should cause an issue..):
    /opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
    /opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
    Looking at the AdminServer.log:
    *####<Oct 11, 2012 11:27:53 AM EDT> <Critical> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969273846> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: weblogic.management.provider.EditFailedException:*
    java.lang.AssertionError: weblogic.management.provider.EditFailedException:
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:79)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
         at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
         at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
         at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
         at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused By: weblogic.management.provider.EditFailedException:
         at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1754)
         at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
         at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
         at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
         at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
         at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused By: org.xml.sax.SAXParseException: Premature end of file.
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
         at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
         at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
         at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
         at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
         at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
         at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
         at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
         at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
         at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
         at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:70)
         at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:64)
         at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1917)
         at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1807)
         at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1740)
         at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
         at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
         at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:81)
         at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
         at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:232)
         at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:154)
         at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:26)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    ####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274051> <BEA-000365> <Server state changed to FAILED>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Error> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274053> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274069> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274138> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.domainruntime .>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274140> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.edit .>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274141> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.runtime .>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274146> <BEA-220028> <Web Service reliable agents are suspended.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274153> <BEA-220029> <Web Service reliable agents are shut down.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <MessagingBridge> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274318> <BEA-200001> <The messaging bridge service has successfully shut down.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274426> <BEA-040308> <JMS service is suspending.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274506> <BEA-040107> <Undeployed 8 default connection factories.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274510> <BEA-040015> <JMS shutdown is complete.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274530> <BEA-001144> <Force Suspending the JDBC service.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274536> <BEA-001146> <Force suspend of the JDBC service completed.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274538> <BEA-001147> <Shutting down the JDBC service.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274552> <BEA-001149> <Shutdown of the JDBC service completed.>
    ####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274694> <BEA-000236> <Stopping execute threads.>
    Kindly guide me with this. Thanks!
    Edited by: Kent Pawar. on Oct 11, 2012 8:51 AM

    Issue is :
    Caused By: weblogic.management.provider.EditFailedException:
    One probable reason can be some change made to the config.xml file . If you have previous backup for the config.xml file then try to replace the config.xml file and restart the server .
    Another reason for this exception may be that there were some changes made to configuration through the Admin Console which were not activated completely and Admin Server was restarted . under this scenario weblogic will create a /pendig dir and have a config.xml file created there with the un-activated changes .
    some workaround you can try to restore the Admin Server :
    Under domain dir ,
    \pending directory -- take backup and delete the dir .
    Under Admin Server Dir :
    data\store --- take backup and delete the dir .
    thanks,
    Sandeep

  • Weblogic Admin Server not starting after Virtual Server move

    Hi, we've migrated a VMware virtual server, and our Weblogic Admin (and managed IRM server) no longer start. The associated log files don't get updated and only the following info is present in the Command window, which I can only see if I use the /k switch, otherwise the windows shut immediately.
    WLS Start Mode=Development
    CLASSPATH=C:\Oracle\MIDDLE~3\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar
    ;C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\sys_manifest_classpath\weblog
    ic_patch.jar;C:\Oracle\MIDDLE~3\patch_oepe1033\profiles\default\sys_manifest_cla
    sspath\weblogic_patch.jar;C:\Oracle\MIDDLE~3\patch_ocp353\profiles\default\sys_m
    anifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~3\JDK160~1\lib\tools.jar;C
    :\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~3\WLSER
    V~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~3\modules\features\weblogic.serve
    r.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\webservices.jar;
    C:\Oracle\MIDDLE~3\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~3\modules
    \NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~3\ORACLE~1\soa\modules\common
    s-cli-1.1.jar;C:\Oracle\MIDDLE~3\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa
    -infra-mgmt.jar;C:\Oracle\MIDDLE~3\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:
    \Oracle\MIDDLE~3\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~3\
    WLSERV~1.3\server\lib\xqrl.jar
    PATH=C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\native;C:\Oracle\MIDDLE~3
    \patch_oepe1033\profiles\default\native;C:\Oracle\MIDDLE~3\patch_ocp353\profiles
    \default\native;C:\Oracle\MIDDLE~3\WLSERV~1.3\server\native\win\32;C:\Oracle\MID
    DLE~3\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~3\modules\ORGAPA~1.1\bin;C:\Oracle\
    MIDDLE~3\JDK160~1\jre\bin;C:\Oracle\MIDDLE~3\JDK160~1\bin;C:\oraclexe\app\oracle
    \product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wb
    em;C:\Program Files\Java\jdk1.6.0_20\bin;C:\Program Files\Apache Software Founda
    tion\Apache2.2\modules;C:\Oracle\MIDDLE~3\WLSERV~1.3\server\native\win\32\oci920
    _8
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    java version "1.6.0_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
    Starting WLS with line:
    C:\Oracle\MIDDLE~3\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThre
    shold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -
    Djava.security.policy=C:\Oracle\MIDDLE~3\WLSERV~1.3\server\lib\weblogic.policy
    -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~3\WLSERV~1.3 -Dwls.home=C:\O
    racle\MIDDLE~3\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~3\WLSERV~1.3\s
    erver -Ddomain.home=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1 -Dcommon.compo
    nents.home=C:\Oracle\MIDDLE~3\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons
    .logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Or
    acle\MIDDLE~3\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.do
    main.config.dir=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1\config\FMWCON~1 -Do
    racle.server.config.dir=C:\Oracle\MIDDLE~3\USER_P~1\domains\IRM_DO~1\config\FMWC
    ON~1\servers\AdminServer -Doracle.security.jps.config=C:\Oracle\MIDDLE~3\USER_P~
    1\domains\IRM_DO~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=
    oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~3\USER_P~1\
    domains\IRM_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~
    3\USER_P~1\domains\IRM_DO~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateT
    ypesDirectory=C:\Oracle\MIDDLE~3\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracl
    e\MIDDLE~3\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEna
    bled=false -Dirm.oracle.home=C:\Oracle\MiddlewareNew\Oracle_ECM1 -Dem.oracle.ho
    me=C:\Oracle\MiddlewareNew\oracle_common -Djava.awt.headless=true -Dweblogic.man
    agement.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToC
    onsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~3\patch_wls1033\profiles\default\sy
    sext_manifest_classpath;C:\Oracle\MIDDLE~3\patch_oepe1033\profiles\default\sysex
    t_manifest_classpath;C:\Oracle\MIDDLE~3\patch_ocp353\profiles\default\sysext_man
    ifest_classpath weblogic.Server
    Is there another log file I could look at to get more info? None of the domain log files are updated.
    Thanks

    Thanks for the reply, this looks fine (I think)..the below is the output
    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.
    C:\Users\Administrator.SEALEDINFO-PROD>cd C:\Oracle\MiddlewareNew\user_projects\
    domains\irm_domain\bin
    C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain\bin>setdomainenv.cmd
    C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>java -version
    java version "1.6.0_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
    C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>java weblogic.version
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401
    Use 'weblogic.version -verbose' to get subsystem information
    Use 'weblogic.utils.Versions' to get version information for all modules
    C:\Oracle\MiddlewareNew\user_projects\domains\irm_domain>

  • WebLogic admin server not starting.

    Hi all,
    I have a problem with my WebLogic Admin server not starting. Following a VM reboot last week our admin servers are no longer starting. On this particular server we have 3 admin servers serving 3 separate environments.
    Theserver seems to be getting stuck right at the very start. I have tried removing tmp, cache and ldap directories. Searched for and removed all .lok files. I have manually turned on full debug to try and flush some extra information through standard out but no luck. It is very peculiar. When we have exported the domain to another box and started the admin server it has come up successfully.
    This is the output from the logs - this is literally as far as it get before it hangs and does nothing. As far as I know the next thing WebLogic is doing is checking the version. Has anyone any ideas what the problem could be? It is server wide as all 3 admin servers on the same box are suffering the same problem.
    This is Weblogic 10.3.2 on a Solaris vm
    JAVA Memory arguments: -Xms256m -Xmx512m
    WLS Start Mode=Development
    CLASSPATH=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/lib/tools.jar:/apps/Oracle/Middleware64/utils/config/10.3/config-launch.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic_sp.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.jar:/apps/Oracle/Middleware64/modules/features/weblogic.server.modules_10.3.2.0.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/webservices.jar:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/apps/Oracle/Middleware64/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/apps/Oracle/Middleware64/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/apps/Oracle/Middleware64/wlserver_10.3/server/lib/xqrl.jar
    PATH=/apps/Oracle/Middleware64/wlserver_10.3/server/bin:/apps/Oracle/Middleware64/modules/org.apache.ant_1.7.0/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/jre/bin:/apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin:/usr/bin:/usr/sfw/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    Starting WLS with line:
    /apps/Oracle/jrt/jrmc-4.0.1-1.6.0/bin/java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=/apps/Oracle/Middleware64/wlserver_10.3/server/lib/weblogic.policy -Xverify:none -da -Dplatform.home=/apps/Oracle/Middleware64/wlserver_10.3 -Dwls.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.home=/apps/Oracle/Middleware64/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/apps/Oracle/Middleware64/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
    <09-Jan-2013 18:32:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.1-21-133393-1.6.0_20-20100512-2127-solaris-sparcv9 from Oracle Corporation>

    Just a wild guess (as you have restarted the physical servers), it could be related to the entropy of the machine.
    What you can try to do is edit the java.security file in the $JAVA_HOME/jre/lib/security directory.
    Find the entry securerandom.source and edit the value to file:/dev/./urandom (instead of file:/dev/urandom)

Maybe you are looking for