Schedule to restart a managed server

Hi
Is there anyway we can make a managed server restart on a specified day in a
week.
I am using the AS/400 as the backend and after we IPL the AS400 during the weekend
, the application stops working.
If I restart the server , it will work .
So i was wondering if I could make it shutdown and restart on a specified day
Thanks in advance
K

Please see:
http://edocs.bea.com/wls/docs81/adminguide/nodemgr.html
K wrote:
Hi
Thanks for the answer , I am new to WLS .
Where do I find the node manager settings /configuration
"Arvind" <[email protected]> wrote:
K,
Unfortunately there is no way to do scheduled restarting in WLS.. however
the
good news is that you can use NodeManager to auto-start the managed servers.
check
the node manager configurations.. in particular node manager could be
used to
start a particular managed server after a specified time interval (though
it might
defeat yr purpose as u may want scheduled not time delayed restars),
u can also
configure to auto-start managed servers upon crash etc.,
Use AS400 commands to schedule jobs.. i believe the command "wrkjobscde"
to
schedule a job in AS400 (Im not an AS400 expert.. only had a few days
of experience
with it.. i have to admit AS400 is weird)
+arvind
"K" <[email protected]> wrote:
Hi
Is there anyway we can make a managed server restart on a specified
day in a
week.
I am using the AS/400 as the backend and after we IPL the AS400 during
the weekend
, the application stops working.
If I restart the server , it will work .
So i was wondering if I could make it shutdown and restart on a specified
day
Thanks in advance
K

Similar Messages

  • Schedule recycle of Weblogic managed server

    Hello everyone,
    We are having issues with gradual degradation of response time with our BI Publisher application.  Until the issue is solved, we would like to schedule a daily automatic recycle of the managed server that it runs on.  I have seen documentation for configuring node manager to recycle the server based on health status, but we would actually like to recycle this managed server daily at a specific time in the evening.  We have scripts that we call from the Linux command line to shutdown and restart a managed server.  I assume I could write a script that calls both of these with a sleep command in between the two to give the managed server time to shut down completely before calling the startup script.  Does anyone have any recommendations on the best approach for a task like this, or could a shutdown/restart at a specific time every day be configured with the l Admin console?
    We are running WebLogic Server Version 10.3.5.0 in Java 1.6 Runtime environment on JRockit R 28.1.4.   Bi Publisher application is Release 10.1.3.4.

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

  • Schedule NetWare Restart using Dist Server Policy?

    Can anybody tell me the best way to schedule a one-time NetWare server restart? Seems that a Distributed Server Package would be the logical tool. I've used them to schedule restarts on Windows servers, but it's not obvious to me how to do that for a NetWare server.

    hnewman said on 8/26/2008,
    >But extending the question out, I might want to schedule a weekly
    >reboot on a handful of NetWare servers. I could push out a cron job the
    >same way, but isn't that the purpose of a Distributed Server policy? It
    >certainly is for Windows servers. Isn't there a way to do a 'restart
    >server' using that mechanism?
    I do not have a setup in front of me at the moment, but the documentation
    for the policy object shows that there is a schedule and you can set the
    schedule as you please. I haven't actually used the policy just for a
    reboot, but this should work just fine.
    HOw about these to links
    http://www.novell.com/documentation/...4.html#a2oekkc
    http://www.novell.com/documentation/...a/a332qh4.html
    Jared Jennings - Data Technique, Inc.
    Novell Support Forums Sysop
    My Blog and Wiki with Tips, Tricks, and Tutorials
    http://jaredjennings.org

  • Nodemanager does not restart managed server after Linux OS reboot

    Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
    I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
    Things I've tried:
    + When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
    + The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
    + A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
    Things I'm curious about:
    + Is there some way to see in what state the nodemanager believes the managed server to be?
    + Is there some value in some doc somewhere that might say the server should not be restarted?
    + Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
    Thanks,
    Kevin
    ListenPort=5556
    ListenBacklog=50
    SecureListener=true
    AuthenticationEnabled=true
    NativeVersionEnabled=false
    CrashRecoveryEnabled=true
    JavaHome=/appl/java/jre
    StartScriptEnabled=false
    StopScriptEnabled=false
    StartScriptName=startWebLogic.sh
    StopScriptName=
    LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
    LogLevel=INFO
    LogLimit=0
    LogCount=1

    can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
    Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
    To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
    CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
    NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
    Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
    From Official documentation:
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
    If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    */

  • Restart Managed Server from Adminserver FAILED_NOT_RESTARTABLE

    Hi all,
    I've got problems restarting the managed server from the adminkonsole ('Control'-Tab) and from within wlst while connected to the adminserver 'start('mymanaged','Server','t3://localhost:80', block='true') connected with the adminserver.
    In the logfile of the administration occurs a nullPointerException:
    java.lang.NullPointerException
         at javax.mail.internet.MimeUtility.decodeText(MimeUtility.java:480)
         at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.mimeDecode(DeploymentServiceServlet.java:788)
         at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.authenticateRequest(DeploymentServiceServlet.java:523)
         at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.doPost(DeploymentServiceServlet.java:194)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    The nodemanager-log shows an IOException:
    <02.02.2007 12:08:42> <Warning> <Exception while starting server 'sunetweb': java.io.IOException: Server failed to start up. See server output log for more details.>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:246)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:463)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:115)
         at weblogic.nodemanager.server.Handler.run(Handler.java:66)
         at java.lang.Thread.run()V(Unknown Source)
    In the console, the serverstate of the managed server is:
    FAILED_NOT_RESTARTABLE
    But in config.xml both servers have set auto-restart:true.
    Starting from within wlst connected to Nodemanager instead works (nmStart("mymanaged", 'c:/win32app/bea/user_projects/domains/mydomain').
    Also the serverstart with a command file works.
    I want to restart the managed server from the console and from wlst connected to admin server.
    What is wrong ?
    Thanks, kind regards,
    Thomas

    Hi Jin,
    I use wlst now to do what I want.
    For a gentle restart of the managed server I connect to the Administration server and then run:
    #shutdown mymanaged gently
    shutdown(name='mymanaged',entityType='Server',ignoreSessions='true',timeOut=5, force='false')
    #start the sever again
    start('mymanaged','Server','t3://localhost:80', block='true')
    Still it is not possible to restart the managed server from console (stopping works).
    But wlst works for me.
    I won't follow this problem further.
    Thanks a lot.
    Kind regards,
    Thomas

  • Auto-Deployment and Restarting Managed Server

    Hi,
    We are using WebLogic Server 7.0 SP2 on Solaris 8. Yesterday, a developer copied
    over a new WAR file into the applications directory. Then he ried to restart the
    managed server. This appeared to hang, so he tried restarting the admin. server,
    which also failed. Looking at the log, it looks like the admin. server is trying
    to deploy apps. from the applications/backup directory.
    After I removed the backup directory and edited config.xml to remove all references
    to this directory, I was able to startup the Admin. server (though there were
    still some errors; see later) and the managed server.
    The servers are actually running in "developemnt" mode and have the Aut-Deploy
    feature enabled, so my theory is that the auto-deployment was conflicting with
    the managed server restart. He shouldn't have had to restart the managed server
    since Auto-Deploy is enabled, right?
    I'm also wondering about these errors I got when I the Admin. server finally started:
    Starting WebLogic Server...
    <May 4, 2004 11:41:04 AM MDT> <Notice> <Management> <140005> <Loading configuration
    /wlsapp/prod/ivrprod/./config.xml>
    <May 4, 2004 11:41:14 AM MDT> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <May 4, 2004 11:41:14 AM MDT> <Notice> <WebLogicServer> <000327> <Starting WebLogic
    Admin Server "admin" for domain "ivrprod">
    <May 4, 2004 11:41:44 AM MDT> <Notice> <Application Poller> <149400> <Activating
    application: appsdirbackup_dir>
    <May 4, 2004 11:41:49 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir on admin - Running>
    <May 4, 2004 11:41:51 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir on admin - Completed>
    <May 4, 2004 11:41:54 AM MDT> <Notice> <Management> <141052> <Application Poller
    started for development server.>
    <May 4, 2004 11:41:54 AM MDT> <Notice> <Application Poller> <149400> <Activating
    application: appsdirbackup_dir-0>
    <May 4, 2004 11:41:57 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:41:59 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000365> <Server state
    changed to RUNNING>
    <May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000360> <Server started
    in RUNNING mode>
    <May 4, 2004 11:42:13 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=2268781,name=InternetTroubleshooting,context-path=/backup/
    InternetTroubleshooting)] failed to compile /dialogs/ADSLDisambig.jsp, compiler
    errors:
    /wlsapp/prod/ivrprod/./admin/.wlnotdelete/_appsdir_backup_dir_InternetTroubleshooting_2268781/jsp_servlet/_dialogs/__ADSLDisambig.ja
    va:17: package com.nuance.ps.telus does not exist
    <May 4, 2004 11:42:20 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=1642582,name=ReportAPayment,context-path=/backup/ReportAPa
    yment)] translation of /dialogs/GetStatus.jsp failed: weblogic.servlet.jsp.JspException:
    (line 7): class 'com.nuance.ps.telus.Shared
    Storage' could not be loaded>
    <May 4, 2004 11:42:20 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:42:22 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=3439810,name=TelusLogin,context-path=/backup/TelusLogin)]
    translation of /conf/ClearOldKeys.jsp failed: weblogic.servlet.jsp.JspException:
    (line 2): class 'com.nuance.ps.telus.SharedStorage'
    could not be loaded>
    <May 4, 2004 11:42:22 AM MDT> <Error> <Deployer> <149201> <The Slave Deployer
    failed to complete the deployment task with id 16 for
    the application appsdirbackup_dir.
    weblogic.management.ApplicationException: Prepare failed. Task Id = 16
    Thanks,
    Paul

    The short answer to your question is that auto-deployment and multiple
    servers don't mix.
    If you have a single-server domain and choose to use auto-deployment,
    that'll work fine.
    Once you have separate admin/managed servers, you need to use
    weblogic.Deployer, the wldeploy ant task (8.1), or the console to deploy
    applications.
    -- Rob
    Paul wrote:
    Hi,
    We are using WebLogic Server 7.0 SP2 on Solaris 8. Yesterday, a developer copied
    over a new WAR file into the applications directory. Then he ried to restart the
    managed server. This appeared to hang, so he tried restarting the admin. server,
    which also failed. Looking at the log, it looks like the admin. server is trying
    to deploy apps. from the applications/backup directory.
    After I removed the backup directory and edited config.xml to remove all references
    to this directory, I was able to startup the Admin. server (though there were
    still some errors; see later) and the managed server.
    The servers are actually running in "developemnt" mode and have the Aut-Deploy
    feature enabled, so my theory is that the auto-deployment was conflicting with
    the managed server restart. He shouldn't have had to restart the managed server
    since Auto-Deploy is enabled, right?
    I'm also wondering about these errors I got when I the Admin. server finally started:
    Starting WebLogic Server...
    <May 4, 2004 11:41:04 AM MDT> <Notice> <Management> <140005> <Loading configuration
    /wlsapp/prod/ivrprod/./config.xml>
    <May 4, 2004 11:41:14 AM MDT> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <May 4, 2004 11:41:14 AM MDT> <Notice> <WebLogicServer> <000327> <Starting WebLogic
    Admin Server "admin" for domain "ivrprod">
    <May 4, 2004 11:41:44 AM MDT> <Notice> <Application Poller> <149400> <Activating
    application: appsdirbackup_dir>
    <May 4, 2004 11:41:49 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir on admin - Running>
    <May 4, 2004 11:41:51 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir on admin - Completed>
    <May 4, 2004 11:41:54 AM MDT> <Notice> <Management> <141052> <Application Poller
    started for development server.>
    <May 4, 2004 11:41:54 AM MDT> <Notice> <Application Poller> <149400> <Activating
    application: appsdirbackup_dir-0>
    <May 4, 2004 11:41:57 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:41:59 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000365> <Server state
    changed to RUNNING>
    <May 4, 2004 11:42:02 AM MDT> <Notice> <WebLogicServer> <000360> <Server started
    in RUNNING mode>
    <May 4, 2004 11:42:13 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=2268781,name=InternetTroubleshooting,context-path=/backup/
    InternetTroubleshooting)] failed to compile /dialogs/ADSLDisambig.jsp, compiler
    errors:
    /wlsapp/prod/ivrprod/./admin/.wlnotdelete/_appsdir_backup_dir_InternetTroubleshooting_2268781/jsp_servlet/_dialogs/__ADSLDisambig.ja
    va:17: package com.nuance.ps.telus does not exist
    <May 4, 2004 11:42:20 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=1642582,name=ReportAPayment,context-path=/backup/ReportAPa
    yment)] translation of /dialogs/GetStatus.jsp failed: weblogic.servlet.jsp.JspException:
    (line 7): class 'com.nuance.ps.telus.Shared
    Storage' could not be loaded>
    <May 4, 2004 11:42:20 AM MDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbackup_dir-0 on admin - Running>
    <May 4, 2004 11:42:22 AM MDT> <Error> <HTTP> <101045> <[ServletContext(id=3439810,name=TelusLogin,context-path=/backup/TelusLogin)]
    translation of /conf/ClearOldKeys.jsp failed: weblogic.servlet.jsp.JspException:
    (line 2): class 'com.nuance.ps.telus.SharedStorage'
    could not be loaded>
    <May 4, 2004 11:42:22 AM MDT> <Error> <Deployer> <149201> <The Slave Deployer
    failed to complete the deployment task with id 16 for
    the application appsdirbackup_dir.
    weblogic.management.ApplicationException: Prepare failed. Task Id = 16
    Thanks,
    Paul

  • Restarting AdminServer without shutting down Managed Server

    Using Weblogic 10.3.5 on OEL v8
    To clear some old stats I need to bounce the Admin Server running on port 7001. Would I have to stop the Managed server as well (my applications) for this? Or can I bounce Admin Server without stopping my application?
    Thanks.

    809364 wrote:
    Which stats you want to reset. is it specific to your application-runtime statistic data running on managed server.
    You need to restart your managed server in case of stats belonging to the application or from the managed server.JDBC Data Source - Failure to Reconnect count .

  • Managed server independence mode startup : VERY slow (2h~)

    Hello there,
    I'm posting this thread to ask for some help.
    In my production environnement, where I am running a cluster of several ALSB nodes, a problem showed up when a network card was unplugged on our admin server hardware.
    You have to know that for some reason, we are not using a node manager for our admin operations on the managed servers, but rather scripts that are scheduled by a tool we use for several other things (backup,etc..). This tool runs WLST scripts to do some basic stuff on our servers.
    So, during the shutdown/startup process, when we tried to bring back all the managed servers up, we faced this problem : When the managed servers were not able to contact the admin server, the startup process takes approx 2 hours, but only 10min when admin server is up and running. This is a real problem in our high availibility environnement, if we have to face this "no admin server" situation again.
    My environnement is :
    Weblogic 10.0
    Solaris 10.6.0
    Java HotSpot(TM) Server VM Version 1.5.0_16-b02
    <Jul 22, 2010 10:07:03 AM MEST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    /xx/JMSReportingProviderStartupClass.jar:/xx/SID_AMM_ALSB_SECURITY.jar:/xx/content_system.jar:/xx/p13n-schemas.jar:/xx/p13n_common.jar:/xx/p13n_system.jar:/xx/wlp_services.jar:/xx/analytics_sys.jar:/xx/commerce_system.jar:/xx/groupspace_system.jar:/xx/netuix_common.jar:/xx/netuix_schemas.jar:/xx/netuix_system-full.jar:/xx/netuix_system.jar:/xx/nf-jspcmods.jar:/xx/nf-system.jar:/xx/wlp-schemas.jar:/xx/wlp_content_system.jar:/xx/wps_system.jar:/xx/wsrp-client.jar:/xx/wsrp-common.jar>
    WebLogic Server Temporary Patch for CR382552 Fri Dec 12 13:12:27 IST 2008
    WebLogic Server Temporary Patch for 9112835 Thu Nov 12 10:53:52 EST 2009
    WebLogic Server Temporary Patch for CR368155 Mon Jul 07 15:51:15 PDT 2008
    WebLogic Server Temporary Patch for CR370311 Tue Jun 03 14:40:28 IST 2008
    WebLogic Server Temporary Patch for CR360676 Fri Apr 18 19:41:49 IST 2008
    WebLogic Server Temporary Patch for CR360117 Wed Mar 12 14:47:42 PDT 2008
    WebLogic Server Temporary Patch for CR354395 Mon Dec 10 08:10:43 PST 2007
    WebLogic Server Temporary Patch for CR345092 Wed Oct 24 11:10:56 IST 2007
    WebLogic Server Temporary Patch for CR338239 Fri Jan 11 17:14:11 EST 2008
    WebLogic Server Temporary Patch for CR328282 Thu Nov 08 13:44:54 EST 2007
    WebLogic Server Temporary Patch for CR315317 Mon Feb 25 09:45:40 PST 2008
    WebLogic Server Temporary Patch for CR315317 Mon Feb 25 09:45:40 PST 2008
    WebLogic Server Temporary Patch for CR344429 Mon Nov 26 16:11:55 EST 2007
    WebLogic Server Temporary Patch for CR351304 Thu Feb 21 10:23:22 EST 2008
    WebLogic Server Temporary Patch for CR350614 Sun Nov 11 18:02:20 PST 2007
    WebLogic Server Temporary Patch for CR344375 Fri Oct 19 11:08:33 PDT 2007
    WebLogic Server Temporary Patch for CR353586 Mon Feb 25 18:59:49 EST 2008
    WebLogic Server Temporary Patch for CR353586 Mon Feb 25 18:59:49 EST 2008
    WebLogic Server Temporary Patch for CR339736, CR346639 Mon Nov 26 18:13:36 PST 2007
    WebLogic Server Temporary Patch for CR343580 Mon Oct 29 17:41:35 EDT 2007
    WebLogic Server Temporary Patch for CR315317 Fri Feb 15 11:13:21 PST 2008
    WebLogic Server Temporary Patch for CR351685, CR320630 Thu Dec 06 14:04:31 CST 2007
    WebLogic Server Temporary Patch for CR345472 Thu Jan 17 16:13:48 EST 2008
    WebLogic Server Temporary Patch for CR355338 Mon Jan 21 13:08:48 EST 2008
    WebLogic Server Temporary Patch for CR356295 Wed Dec 19 15:37:45 EST 2007
    WebLogic Server Temporary Patch for CR348244 Fri Oct 19 11:57:37 PDT 2007
    WebLogic Server Temporary Patch for CR346064 Fri Oct 19 13:27:18 PDT 2007
    WebLogic Server Temporary Patch for CR346063 Fri Oct 05 14:48:13 PDT 2007
    WebLogic Server Temporary Patch for Cr346061 Thu Oct 18 15:38:04 PDT 2007
    WebLogic Server Temporary Patch for Cr346061 Thu Oct 18 15:38:04 PDT 2007
    WebLogic Server Temporary Patch for CR346060 Thu Oct 18 15:28:01 PDT 2007
    WebLogic Server Temporary Patch for CR350528 Fri Nov 02 16:19:36 PDT 2007
    WebLogic Server Temporary Patch for CR354048 Thu Dec 06 13:52:09 IST 2007
    WebLogic Server Temporary Patch for CR348229 Wed Oct 24 13:49:07 PDT 2007
    WebLogic Server Temporary Patch for CR362972, CR357095 Fri Mar 07 15:38:53 IST 2008
    WebLogic Server Temporary Patch for CR358677 Wed Jan 23 16:28:40 PST 2008
    WebLogic Server Temporary Patch for CR354390 Wed Feb 27 09:57:23 PST 2008
    WebLogic Server Temporary Patch for CR357287 Thu Jan 31 14:51:56 PST 2008
    WebLogic Server Temporary Patch for CR359323 Fri Mar 07 02:24:20 EST 2008
    WebLogic Server Temporary Patch for CR322355 Tue Oct 23 10:53:45 PDT 2007
    WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184 >
    <Jul 22, 2010 10:10:36 AM MEST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://xx.xx.xx.xx:xx.>
    <Jul 22, 2010 10:10:36 AM MEST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Jul 22, 2010 10:10:36 AM MEST> <Info> <WebLogicServer> <BEA-000215> <Loaded License : xxxxxx>
    <Jul 22, 2010 10:10:36 AM MEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jul 22, 2010 10:10:36 AM MEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <22/07/2010#10:10:36.794#+0200> <Notice> <Log Management> <BEA-170019> <The server log file xxxxxxx.log is opened. All server side log events will be written to this file.>
    <22/07/2010#10:10:41.578#+0200> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <22/07/2010#10:10:42.75#+0200> <Alert> <Security> <BEA-090167> <Cannot retrieve identity certificate and private key on server xxmanaged1xx, because the keystore entry alias is not specified.>
    <22/07/2010#10:10:42.77#+0200> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the JKS keystore file /xxxkeystore.>
    <22/07/2010#10:16:02.665#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <22/07/2010#10:16:02.666#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <22/07/2010#10:45:48.374#+0200> <Alert> <ALSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. AquaLogic Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need ALSB service account support.>
    <22/07/2010#10:45:48.564#+0200> <Error> <ClusterTimer> <BEA-000000> <Cannot contact Admin server. Therefore constructing the Cluster Authority Current time with the time skew 0
    java.rmi.UnknownHostException: Could not discover URL for server 'xxadminxx'
         at weblogic.protocol.URLManager.findURL(URLManager.java:143)
         at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getInitialContext(RemoteClusterTimerAuthority.java:72)
         at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getTimerAuthority(RemoteClusterTimerAuthority.java:84)
         at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getClusterTimerAuthorityCurrentTime(RemoteClusterTimerAuthority.java:44)
         at com.bea.wli.timer.ClusterTimerService.clusterTimeAuthorityCurrentTimeMillis(ClusterTimerService.java:173)
         Truncated. see log file for complete stacktrace
    >
    <22/07/2010#10:45:48.567#+0200> <Error> <ClusterTimer> <BEA-000000> <Cannot contact the admin server. Therefore constructing the Cluster Authority Urzeit from the persisted value
    java.rmi.UnknownHostException: Could not discover URL for server 'xxadminxx'
         at weblogic.protocol.URLManager.findURL(URLManager.java:143)
         at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getInitialContext(RemoteClusterTimerAuthority.java:72)
         at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getTimerAuthority(RemoteClusterTimerAuthority.java:84)
         at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getUrzeit(RemoteClusterTimerAuthority.java:57)
         at com.bea.wli.timer.ClusterTimerService.initialize(ClusterTimerService.java:87)
         Truncated. see log file for complete stacktrace
    >
    <22/07/2010#10:45:52.154#+0200> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library>
    <22/07/2010#11:54:55.765#+0200> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'ALSB Framework Starter Application'.
    RegistrationException : java.rmi.RemoteException: [Deployer:149147]Could not reach the admin server via any of its URLS: 'http://xx.xx.xx.xx:xx'.
         at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.registerHandler(TargetDeploymentService.java:166)
         at weblogic.deploy.service.internal.DeploymentService.registerHandler(DeploymentService.java:177)
         at com.bea.wli.config.deployment.server.ServerDeploymentReceiver.register(ServerDeploymentReceiver.java:82)
         at com.bea.wli.config.deployment.server.ServerDeploymentReceiver.<init>(ServerDeploymentReceiver.java:75)
         at com.bea.wli.config.weblogic.WebLogicConfigService$DeploymentReceiverLauncher.endOfStart(WebLogicConfigService.java:190)
         Truncated. see log file for complete stacktrace
    RegistrationException : java.rmi.RemoteException: [Deployer:149147]Could not reach the admin server via any of its URLS: 'http://xx.xx.xx.xx:xx'.
         at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.registerHandler(TargetDeploymentService.java:166)
         at weblogic.deploy.service.internal.DeploymentService.registerHandler(DeploymentService.java:177)
         at com.bea.wli.config.deployment.server.ServerDeploymentReceiver.register(ServerDeploymentReceiver.java:82)
         at com.bea.wli.config.deployment.server.ServerDeploymentReceiver.<init>(ServerDeploymentReceiver.java:75)
         at com.bea.wli.config.weblogic.WebLogicConfigService$DeploymentReceiverLauncher.endOfStart(WebLogicConfigService.java:190)
         Truncated. see log file for complete stacktrace
    >
    <22/07/2010#11:54:56.271#+0200> <Error> <ConfigFwk> <BEA-000000> <Failed in endLoadNotification. Ignoring.
    java.lang.NullPointerException
         at com.bea.wli.sb.resources.globaloperations.GlobalOperationsResourceLifecycleListener.endLoadNotification(GlobalOperationsResourceLifecycleListener.java:112)
         at com.bea.wli.config.impl.ResourceListenerNotifier.sendLoadNotificationsInContext(ResourceListenerNotifier.java:236)
         at com.bea.wli.config.impl.ResourceListenerNotifier.access$400(ResourceListenerNotifier.java:41)
         at com.bea.wli.config.impl.ResourceListenerNotifier$1.execute(ResourceListenerNotifier.java:151)
         at com.bea.wli.config.transaction.TransactionalTask._doExecute(TransactionalTask.java:217)
         Truncated. see log file for complete stacktrace
    >
    <22/07/2010#11:54:57.153#+0200> <Error> <ConfigFwk> <BEA-000000> <Failed in endLoadNotification. Ignoring.
    java.lang.NullPointerException
         at com.bea.wli.sb.service.ServiceChangeListener.updateAlerts(ServiceChangeListener.java:243)
         at com.bea.wli.sb.service.ServiceChangeListener.endLoadNotification(ServiceChangeListener.java:175)
         at com.bea.wli.config.impl.ResourceListenerNotifier.sendLoadNotificationsInContext(ResourceListenerNotifier.java:236)
         at com.bea.wli.config.impl.ResourceListenerNotifier.access$400(ResourceListenerNotifier.java:41)
         at com.bea.wli.config.impl.ResourceListenerNotifier$1.execute(ResourceListenerNotifier.java:151)
         Truncated. see log file for complete stacktrace
    >
    <22/07/2010#11:54:59.828#+0200> <Error> <ALSB Statistics Manager> <BEA-473004> <Cannot recover from persistent Store : java.lang.NullPointerException
    java.lang.NullPointerException
         at com.bea.wli.monitoring.statistics.collection.Collector.readPersistedRawSnapshot(Collector.java:357)
         at com.bea.wli.monitoring.statistics.StatisticsManager.onStatConfigLoad(StatisticsManager.java:347)
         at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.onStatConfigLoad(ALSBStatisticsManager.java:379)
         at com.bea.wli.sb.service.ServiceStatisticsListener.updateRuntime(ServiceStatisticsListener.java:200)
         at com.bea.wli.sb.service.ServiceStatisticsListener.endLoadNotification(ServiceStatisticsListener.java:168)
         Truncated. see log file for complete stacktrace
    >
    <22/07/2010#11:55:02.434#+0200> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
    <22/07/2010#11:55:02.557#+0200> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    <22/07/2010#11:55:02.557#+0200> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of xxCLUSTERxx.>
    <22/07/2010#11:55:32.595#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <22/07/2010#11:55:32.595#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <22/07/2010#11:57:17.835#+0200> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on xx.xx.xx.xx:14101 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <22/07/2010#11:57:17.835#+0200> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "xxmanaged1xx" for domain "xxDOMAINxx" running in Production Mode>
    <22/07/2010#11:57:17.840#+0200> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server xxadminxx at <JMXServiceURL:null>.>
    <22/07/2010#11:57:20.13#+0200> <Notice> <Cluster> <BEA-000102> <Joining cluster xxCLUSTERxx on xx.xx.xx.xx:7001>
    <22/07/2010#11:57:20.28#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    I have a hard time trying to see what's happening here.
    If you have any input for me to use, I would be very thankful.
    And by the way, please excuse me for my poor english (french here ^^)
    Best regards,
    Serge

    As a test, I shutdown my admin server and then killed the managed server from the command line so that node manager would start it ( and not be able to find the admin server ).
    I'm using WL 10.3.3 ( 11g + OSB + SOA ) on oracle linux (64bit) and the managed server started in 3 minutes.
    So I tried the same in my 10g environment WL 10.3 running OSB 10g ( oracle linux 32-bit ) and the server started in 2 minutes.
    I see a couple of times when your trace shows a pause:
    1. when loading certificates22/07/2010#10:10:42.75#+0200> <Alert> <Security> <BEA-090167> <Cannot retrieve identity certificate and private key on server xxmanaged1xx, because the keystore entry alias is not specified.>
    <22/07/2010#10:10:42.77#+0200> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the JKS keystore file /xxxkeystore.>
    <22/07/2010#10:16:02.665#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    For this server, is the keystore alias entered in the server's SSL tab?
    2. Just after entering STARTING<22/07/2010#10:16:02.666#+0200> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <22/07/2010#10:45:48.374#+0200> <Alert> <ALSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. AquaLogic Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need ALSB service account support.>
    In my test, the "user password credential" message was preceded by messages about the Singleton Marker applications. Are the singleton apps deployed to this server, or to some other managed server? If they are deployed to some other managed server, are they deployed to a managed server on the same host as the (unreachable) admin server?
    <Jul 19, 2010 11:11:54 AM EDT> <Info> <WorkManager> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "ALSB Cluster Singleton Marker Application">
    <Jul 19, 2010 11:11:54 AM EDT> <Info> <WorkManager> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "ALSB Domain Singleton Marker Application">
    <Jul 19, 2010 11:11:54 AM EDT> <Info> <WorkManager> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "ALSB Framework Starter Application">
    <Jul 19, 2010 11:11:56 AM EDT> <Alert> <OSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.>
    3. activating ALSB Framework 22/07/2010#10:45:52.154#+0200> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library>
    <22/07/2010#11:54:55.765#+0200> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'ALSB Framework Starter Application'.
    In my test, this was logged immediately after the "user password credential mapper" message, with the following between:
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssModuleImpl.getInstance>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssModuleImpl.initialize>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <initializing WssHandlerImpl>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssHandlerImpl constructor>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssAuditor initilizing>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <auditingEnbled set to false>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <auditingEnbled set to false>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssAuditor successfully started>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityWss> <BEA-000000> <WssModuleImpl was successfully initialized>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityModule> <BEA-000000> <jndiLookup: [jndi-name: com.bea.alsb.internal.clusterTimerAuthority]>
    <Jul 19, 2010 11:11:56 AM EDT> <Debug> <AlsbSecurityModule> <BEA-000000> <jndiLookup: [jndi-name: com.bea.alsb.internal.clusterTimerAuthority]>
    <Jul 19, 2010 11:11:56 AM EDT> <Info> <Monitoring> <BEA-000000> <New Metadata version is 0>
    <Jul 19, 2010 11:11:56 AM EDT> <Info> <Monitoring> <BEA-000000> <New Metadata version is 0>
    <Jul 19, 2010 11:11:56 AM EDT> <Info> <Monitoring> <BEA-000000> <New Metadata version is 0>
    <Jul 19, 2010 11:11:56 AM EDT> <Info> <Deployer> <BEA-149059> <Module Dummy of application ALSB Framework Starter Application is transitioning from STATE_NEW to STATE_PREPARED on server
    The clusterTimerAuthority involves contacting the admin server in 11g, but not quite sure about 10g. ( I have a separate bug in 11g when the ClusterTime can't be reached if the admin server is using 2way SSL )
    I can't run the same test in my multi-node environments, but is it possible for you to change the targets of the 2 Singleton applications to a managed server which runs on some machine other than the Admin server's machine? Then try starting that managed server while the Admin server is down, and also try restarting another managed server ( which is not on the admin server's host and is not targetted by the Singleton applications. )
    I suspect the managed server with the singleton apps will start more quickly than the one without.

  • Problem with JMS migration when using Ctrl+C to stop the managed server in cluster

              Hi,
              I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
              uses JMS as a asynchrous communication. We have MDB which listens to these JMS
              messages.
              If something is being processed on Managed Server 1 and while the request is in
              process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
              After this, i go to admin console and migrate teh JTA and JMS. After this, i am
              expecting other running Managed Server should restart the incomplete transaction.
              But this is not happening. The Managed Serve2 doesn't process the requst.
              But when i restart teh MAnaged SErver 1 again, it takes up the same request and
              processes it.
              Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
              Please note that the same thing is working fine when i stop the server using Admin
              console(Normal shutdown OR forced shutdown).
              Any comments in this regards are apprecciated.
              Thanks,
              Naresh
              

              Hi,
              I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
              uses JMS as a asynchrous communication. We have MDB which listens to these JMS
              messages.
              If something is being processed on Managed Server 1 and while the request is in
              process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
              After this, i go to admin console and migrate teh JTA and JMS. After this, i am
              expecting other running Managed Server should restart the incomplete transaction.
              But this is not happening. The Managed Serve2 doesn't process the requst.
              But when i restart teh MAnaged SErver 1 again, it takes up the same request and
              processes it.
              Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
              Please note that the same thing is working fine when i stop the server using Admin
              console(Normal shutdown OR forced shutdown).
              Any comments in this regards are apprecciated.
              Thanks,
              Naresh
              

  • Not able to startup managed server on remote machine -- Please advice

    Hi All,
    We have one admin server and two managed server in one domain. The admin server and a managed server are in one machine(say machineA) and another managed server is on a different machine(say machineB). I changed the weblogic admin console password and in boot.properties file also. Now when i am restarting the managed server on machineB, i am getting below error message.
    <May 12, 2009 12:26:37 PM PDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://123.23.4.56:7071 to retrieve th
    e initial configuration.>
    <May 12, 2009 12:26:38 PM PDT> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user weblogic star
    ting the managed server. The reason for the error is .>
    <May 12, 2009 12:26:38 PM PDT> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through UR
    L: http://123.23.4.56:7071/wl_management_internal2/Bootstrap, user: weblogic
    weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the identity of the user we
    blogic starting the managed server. The reason for the error is .
    at weblogic.management.ManagedServerAdmin.retrieveMBeansFromAdminServer(ManagedServerAdmin.java:513)
    at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:150)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:753)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
    at weblogic.Server.main(Server.java:32)
    >
    The WebLogic Server did not start up properly.
    Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the iden
    tity of the user weblogic starting the managed server. The reason for the error is .'
    Reason: weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the identity of the
    user weblogic starting the managed server. The reason for the error is .
    Kindly help me on this.
    Any suggestion is appreciated.
    Thanks & Regards,
    Raj

    Hi Raj,
    Which version of weblogic are you using? Try to delete the cache directory of the managed server and try to restart it again and see if the problem goes away.
    From Weblogic 9 version onwards by default when Managed server starts for the first time it will read boot.properties file inside domain directory and makes a copy of it inside its cache directory domain/servers/ManagedServername/Security folder. I think boot.properties file inside cache directory of managed server might be using old credentials.
    The best way is to delete cache directory of managed server inside domain/servers you will see directory by managed server name, delete it and restart the managed server.
    Hope this helps!!
    - - Tarun

  • Deploying BEA Portal App in Managed Server problems....

    Hello,
    I have a BEA portal application (exploded EAR) that I want to deploy in a managed server. I first created a regular portal domain (8.1 SP4). I then created a managed server via the console. When I went to deploy my portal application (in the console), I received an error indicating that the application was a Split Development Directory and that I would have to run the wlpackage Ant task against the application first. I ran the wlpackage ant task and it seemingly worked.
    I then used the wldeploy Ant task to deploy it in the managed server but got an error indicating that it could not find a JNDI name from one of the data sources. I went back to the console and targeted/deployed all of the default Connection Pools & Data Sources to the managed server thinking that was the reason the deploy failed.
    When I ran the wldeploy again I got the following error:
    Module: content.jar Error: Exception activating module: EJBModule(content.jar, status=PREPARED)
    Unable to deploy EJB: ValueBean from content.jar
    java.sql.SQLException: javax.naming.NameNotFoundException: While trying to lookup 'portalFrameworkPool; contentDataSource;weblogic.jdbc.jts.commercialPool' didn't find subcontext 'portalFrameworkPool;contentDataSource;weblogic' Resolved ; remaining name 'portalFrameworkPool;contentDataSource;weblogic/jdbc/jts/commercialPool'
    Has anyone run into this? Am I not suppose to deploy a portal application in a managed server?
    Any help would be greatly appreciated.
    Thanks - Peter Len

    Problem solved.......
    After targeting all the data sources and poolers to the managed server, I restarted the main domain but did not restart the managed server. After restarting the managed server all was well.
    Thanks - Peter

  • Disaster Recovery - Managed Server Startup

    We are testing some disaster recovery and want to be able to start our managed servers on our B node in MSI mode while the A node with admin server is down. It tests fine and works with nodemanager running. However, we want to assume that there has been a jvm problem on one or more managed servers and they have ceased to run on the B node. When I run the startManagedWebLogic.cmd and plug in my managed server name and admin link (which is obviously unreachable), I get the message below. I copied down the managed servers info (there is no 'config' folder as mentioned in the Oracle instructions so I copied down the 6 server folder into \common\bin\config\acr2 folder). Any tips on getting this to work?
    <Apr 9, 2010 11:11:09 AM CDT> <Info> <Management> <BEA-141107> <Version: WebLogi
    c Server Temporary Patch for 9216172 Tue Jan 12 02:07:27 PST 2010
    WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
    <Apr 9, 2010 11:11:09 AM CDT> <Critical> <WebLogicServer> <BEA-000362> <Server f
    ailed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: [Management:141247]The configuration di
    rectory C:\Oracle\Middleware\wlserver_10.3\common\bin\config does not exist and
    the admin server is not available.
    at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyle
    Config(RuntimeAccessImpl.java:200)
    at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(Runtim
    eAccessImpl.java:115)
    at weblogic.management.provider.internal.RuntimeAccessService.start(Runt
    imeAccessService.java:41)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
    ager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
    icesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
    at weblogic.Server.main(Server.java:67)
    >
    <Apr 9, 2010 11:11:09 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to FAILED>
    <Apr 9, 2010 11:11:09 AM CDT> <Error> <WebLogicServer> <BEA-000383> <A critical
    service failed. The server will shut itself down>
    <Apr 9, 2010 11:11:09 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server sta
    te changed to FORCE_SHUTTING_DOWN>

    So no one has ever had to restart a managed server on a clustered environment when the admin was down? Seems like this would be a common disaster recovery item that would be needed. If anyone has this working please provide details. These details found in Oracle documentation are a bit incomplete...
    Starting a Managed Server in MSI Mode
    To start up a Managed Server in MSI mode:
    1.Ensure that the Managed Server’s root directory contains the config subdirectory.
    If the config directory does not exist, copy it from the Administration Server’s root directory or from a backup to the Managed Server’s root directory.
    Note: Alternatively, you can use the -Dweblogic.RootDirectory=path startup option to specify a root directory that already contains these files.
    2.Start the Managed Server at the command line or using a script.
    The Managed Server will run in MSI mode until it is contacted by its Administration Server. For information about restarting the Administration Server in this scenario, see Restarting a Failed Administration Server.
    I have used the root.directory switch to point to these locations as well but still get message.....<Apr 13, 2010 11:28:05 AM CDT> <Critical> <WebLogicServer> <BEA-000386> <Server
    subsystem failed. Reason: weblogic.descriptor.ResourceUnavailableException: Miss
    ing SerializedSystemIni.dat
    weblogic.descriptor.ResourceUnavailableException: Missing SerializedSystemIni.da
    t
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityPro
    xy.<init>(DescriptorManager.java:153)
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityPro
    xy.instance(DescriptorManager.java:137)
    at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(Des
    criptorManager.java:114)
    at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(Abstract
    DescriptorBean.java:991)
    at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getC
    redential(SecurityConfigurationMBeanImpl.java:709)
    Truncated. see log file for complete stacktrace
    >
    <Apr 13, 2010 11:28:05 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server st
    ate changed to FAILED>

  • Managed server is not starting with MSI mode

    Managed server not starting with MSI mode even though we enabled the managed server independence mode
    Started the admin server and managed server first time enabled the MSI mode.
    Restarted all admin and Managed server.
    We have tested the following scenarios
    scenarios1: Stopped the Admin server and restarted the Managed server with MSI mode it comes up.
    scenarios2:Admin server is running but not able to connect to the managed server
    In this scenario
    we have removed the Network cable and restarted the managed server its throwing ldap error.
    <Aug 14, 2010 1:58:32 PM SGT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: failed to connect to server ldap://sgppsr00383:16827 (91)
    at netscape.ldap.LDAPConnSetupMgr.connectServer(LDAPConnSetupMgr.java:515)
    at netscape.ldap.LDAPConnSetupMgr.openSerial(LDAPConnSetupMgr.java:435) at netscape.ldap.LDAPConnSetupMgr.connect(LDAPConnSetupMgr.java:274)
    at netscape.ldap.LDAPConnSetupMgr.openConnection(LDAPConnSetupMgr.java:199)
    at netscape.ldap.LDAPConnThread.connect(LDAPConnThread.java:109)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:1083) at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:954)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:781)
    at weblogic.ldap.EmbeddedLDAPConnection.getAndInitDelegate(EmbeddedLDAPConnection.java:2031)
    at weblogic.ldap.EmbeddedLDAPConnection.add(EmbeddedLDAPConnection.java:1065) at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.addEntry(DefaultCredentialMapperLDAPHelper.java:537)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.createOrgUnit(DefaultCredentialMapperLDAPHelper.java:432)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.verifyHierarchy(DefaultCredentialMapperLDAPHelper.java:407)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.<init>(DefaultCredentialMapperLDAPHelper.java:146) at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:112)
    at weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
    at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340) at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461) at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854) at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    - with nested exception:
    Managed server looking for ldap configuration from admin server.
    I have checked the all configuration file same on both managed server and admin server.
    Please let me know How to recover the managed server in this scenario.
    Edited by: user10773210 on Aug 16, 2010 11:55 PM
    Edited by: user10773210 on Aug 17, 2010 2:38 AM

    thanks for the reply....
    the managed server is pointing to jrokit_160_22_D1.1.1-3 jdk....the server has enough ram also...while running the managed server showing status 'STARTING' for long period of time...and the admin server health goes 'Warning' because of threadpool....when we stop the managed server then adminserver health becomes ok...

  • ADF Logger in SOA Managed Server

    Hi All,
    I have implemented an ADF Logger in my ADF Application which is deployed on the SOA Managed Server.
    I have followed the steps shown here :- http://digitalspace.wordpress.com/2011/04/08/adf-debugging-how-to-add-custom-log-messages-using-adflogger/
    and then as per the blog , i have changed the logging.xml file,specified the custom logger and modify the setDomainEnv of SOA Managed Server.
    I am able to print the log message using the ADF Logger when my custom logger level sets to FINEST.
    Now i need to modify or remove the Custom Logger from logging.xml, and i did but it didn't reflect at runtime.It still prints the log.
    After restarting the server, i get the appropriate result i.e it doesn't print the log message.
    My question is :- 1.Do we need to restart the managed server if we modify the logging.xml ?
    2.Is there any other configuration file where i need to put the custom logger definition?
    3.Is there any way to modify all these things using the enterprise manager?
    Please Suggest!!
    Regards,
    Shah

    Hi,
    I have implemented the above mentioned suggestions. But seems to have no luck. I had
    1. Copied startup.properties to ${DOMAIN_HOME}/servers/soa_server1/data/nodemanager
    2. Copied the boot.properties to ${DOMAIN_HOME}/servers/soa_server1/security
    These did not added any value, so I though of passing the parameters at nmStart() as WLST object;
    arg="Arguments=\" -Dweblogic.management.server=localhost:8001\"" (My AS and MS runs on same machine)
    prps=makePropertiesObject(arg)
    nmStart('soa_server1',props=prps)
    This started throwing Boot Identity file not valid.
    I changed my way.
    1. Connected to Admin Server using WLST
    connect (username, password)
    2. Start MS
    start('soa_server1')
    Its working fine now and under NM control. Not sure what more NM demands when starting without AS.
    Regards,
    Bhaskar

  • Managed Server not accepting HTTP requests

    We restarted our managed server (it had Oracle Identity Analytics deployed) and received an error after the application came up (pasted below). The application seems to be running but when I attempt to access it I'm getting a Page Not Found error. I deleted the OIA deployment altogether and just started the Managed Server and, though it is Running, I'm seeing the same error and still getting Page Not Found.
    I also restarted the AdminServer and now I'm seeing the same symptoms there. At this point the environment is completely inaccessible. Any ideas on what may be wrong or what the solution may be?
    Weblogic 10.3.3 on Solaris 10
    JDK 1.6.0.21
    ####<Jun 11, 2013 11:30:59 AM CDT> <Error> <Socket> <REDACTED> <OIA-Instance01> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1370968259909> <BEA-000405> <Uncaught Throwable in processSockets
    java.lang.ClassFormatError: LineNumberTable attribute has wrong length in class file weblogic/servlet/internal/ChunkOutput.
    java.lang.ClassFormatError: LineNumberTable attribute has wrong length in class file weblogic/servlet/internal/ChunkOutput
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
    at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at weblogic.servlet.internal.ServletOutputStreamImpl.<init>(ServletOutputStreamImpl.java:92)
    at weblogic.servlet.internal.ServletResponseImpl.<init>(ServletResponseImpl.java:155)
    at weblogic.servlet.internal.MuxableSocketHTTP.<init>(MuxableSocketHTTP.java:111)
    at weblogic.servlet.internal.ProtocolHandlerHTTP.createSocket(ProtocolHandlerHTTP.java:65)
    at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:131)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:901)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
    at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:126)
    at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

    We restarted our managed server (it had Oracle Identity Analytics deployed) and received an error after the application came up (pasted below). The application seems to be running but when I attempt to access it I'm getting a Page Not Found error. I deleted the OIA deployment altogether and just started the Managed Server and, though it is Running, I'm seeing the same error and still getting Page Not Found.
    I also restarted the AdminServer and now I'm seeing the same symptoms there. At this point the environment is completely inaccessible. Any ideas on what may be wrong or what the solution may be?
    Weblogic 10.3.3 on Solaris 10
    JDK 1.6.0.21
    ####<Jun 11, 2013 11:30:59 AM CDT> <Error> <Socket> <REDACTED> <OIA-Instance01> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1370968259909> <BEA-000405> <Uncaught Throwable in processSockets
    java.lang.ClassFormatError: LineNumberTable attribute has wrong length in class file weblogic/servlet/internal/ChunkOutput.
    java.lang.ClassFormatError: LineNumberTable attribute has wrong length in class file weblogic/servlet/internal/ChunkOutput
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
    at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at weblogic.servlet.internal.ServletOutputStreamImpl.<init>(ServletOutputStreamImpl.java:92)
    at weblogic.servlet.internal.ServletResponseImpl.<init>(ServletResponseImpl.java:155)
    at weblogic.servlet.internal.MuxableSocketHTTP.<init>(MuxableSocketHTTP.java:111)
    at weblogic.servlet.internal.ProtocolHandlerHTTP.createSocket(ProtocolHandlerHTTP.java:65)
    at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:131)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:901)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
    at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:126)
    at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

Maybe you are looking for

  • FIM Sync and SharePoint Foundation 2013

    I'm looking into syncing to SharePoint via the FIM synchronisation engine, not using the FIM Portal at all. There's a connector(MA) for SharePoint but it requires UPA, User Profile Service, which isn't in the foundation version. I want to use foundat

  • New features for iTunes 7.1

    Where can I find the new features for iTunes 7.1? Thank you

  • Internal order settlement through KO8G

    Hi gurus, I have created variant sapvar and given inputs int he following fields Order type Order Controlling area Company code and selected the orders tobe settled with selection of all the status and executed But the system is giving the error zero

  • How can I Create Class Diagram and save as image in Java

    Hi I have to make a project in java that will generate class diagram of the input class file. I have some knowledge of listing methods/properties of a class file in text from but don't really know how to draw a class diagram model (JBuilder 2005 such

  • Moving Logic 9.7.1 to Mountain lion

    Hi, I was just about to purchase a Mac Mini Server with Lion for running Logic projects, and then noticed over the last few days they have updraded to Mountain Lion. I know that so far my Audio unit isn't tested (Inspire 1394), and I might have probl