Starts servers with node manager

How to configure the node manager to start admin server and SOA services in the background in linux.

Similar Messages

[wls8.1 sp.3] cannot remote start with node manager on another server

In this domain run on 2 physical servers in windows 2003. In machine that has admin server can start with node manager but another machine without admin server cannot remote start . when i remote start , the node manager has facing error messages as below:
# AT "node manager monitoring" in weblogic admin console
[[NodeManager:300033]Could not execute command ping on the node manager. Reason: weblogic.nodemanager.NodeManagerException: [CommandInvoker: Failed to send command: 'ping to server 'null' to NodeManager at host: 'xxx.xxx.xxx.24:5555' with exception Connection reset by peer.. Please ensure that the NodeManager is active on the target machine].]
# AT "nodemanger.log" has facing error messages as below:
<Aug 20, 2008 7:34:07 PM ICT> <Info> <[email protected]:5555> <NodeManage r started, log messages being written into file C:\bea\WEBLOG~1\common\NODEMA~1\ NodeManagerLogs\NodeManagerInternal\nm_server02_08_20_2008-19_34_03.log>
<Aug 20, 2008 7:59:58 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - 10.208.50.23 during SSL handsha ke.> <Aug 20, 2008 8:00:11 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - xxx.xxx.xxx.23 during SSL handsha key.>
I would REALLY appreciate any suggestions as to what might be the cause or what i could try.
Thanks ....

Hi,
It is up to you to decide whether you want to use nodemanager or not.
It does not make any difference if the server is started via script or nodemanager.
if i want everything (AS, MS, and NM) to come up at server boot i need to set each of them up as windows services (which is what i have at the moment) but this wont allow me to use the node manager ==> Yes this statement is correct.
You can either set AS and MS as windows service (or) AS and nodemanager as service.
Thanks,
Sharmela

Any Guidelines on Configuring Weblogic 8.1 with Node Manager

Hi All, I want to configure Weblogic 8.1 with Node Manager using 4 ports. Is there any step by step guide? Please let me know...
Currently I am referring to this link:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/nodemgr.html
Thanks.

Hi,
Hope the below link may be little helpful: http://middlewaremagic.com/weblogic/?p=971
NOTE: you need not to follow Step8). mentioned in above link because.... WLS8.1 nmEnroll() is not available as part of WLST ...In WLS8.1 no need to start the NodeManager. You can also ignore the Clustering part in the above link ...rest all you need to follow.
Thanks
Jay SenSharma

Integrate other directory servers with access manager

How to integrate other directory servers with access manager ?

Please read the Access Manager admin guide at http://docs.sun.com/app/docs/doc/819-4670/6n6qardvq
Any further questions regarding this integration, post them to the AM forum at http://forums.sun.com/forum.jspa?forumID=770

Not able to start SOA managed server first time with node manager by WLST

Hi all,
I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
In server log file I am getting the following error : -
Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
Can anyone please tell me what can be the issue?
Thanks in Advance!!!
Edited by: 008 on Dec 6, 2012 7:53 PM

Hi,
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
username=type-the-username-here
password=type-the-password-here
Cheers,
Vlad

Problem starting servers with nodemanager

Hi,
I'm following the Oracle By Example:
[http://www.oracle.com/technology/obe/fusion_middleware/wls103/InstallConfig/admin_mngd_srvr/admin_ms_using_nm.htm]
I have installed on Windows (not on Linux), but that shouldn't make much difference.
Now look at what I got on Step 10 of the OBE:
OUTPUT
D:\oracle\Middleware\user_projects\domains\dizzyworld\bin>startManagedWebLogic.cmd dizzy1 http://localhost:7001
JAVA Memory arguments: -Xms256m -Xmx512m -Xns128m -Xgcprio:pausetime -XpauseTarget:200ms
WLS Start Mode=Production
CLASSPATH=D:\oracle\MIDDLE~1\patch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\oracle\MIDDLE~1\JROCKI~1.5-3\lib\to
ols.jar;D:\oracle\MIDDLE~1\utils\config\10.3\config-launch.jar;D:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\oracle\MIDDLE~1\W
LSERV~1.3\server\lib\weblogic.jar;D:\oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.2.0.jar;D:\oracle\MIDDLE~1\WLSERV~1.3\ser
ver\lib\webservices.jar;D:\oracle\MIDDLE~1\modules\ORGAPA~1.0/lib/ant-all.jar;D:\oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;D:
\oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;D:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;D:\oracle\MIDDLE~1\pa
tch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\oracle\MIDDLE~1\JROCKI~1.5-3\lib\tools.jar;D:\oracle\MIDDLE~1\util
s\config\10.3\config-launch.jar;D:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.j
ar;D:\oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.2.0.jar;D:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;D:\orac
le\MIDDLE~1\modules\ORGAPA~1.0/lib/ant-all.jar;D:\oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;.;C:\Program Files\Java\jre6\lib\
ext\QTJava.zip
PATH=D:\oracle\MIDDLE~1\patch_wls1032\profiles\default\native;D:\oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;D:\oracle\MIDDLE~1\WLSERV~1
.3\server\bin;D:\oracle\MIDDLE~1\modules\ORGAPA~1.0\bin;D:\oracle\MIDDLE~1\JROCKI~1.5-3\jre\bin;D:\oracle\MIDDLE~1\JROCKI~1.5-3\bin;D:\oracl
e\MIDDLE~1\patch_wls1032\profiles\default\native;D:\oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;D:\oracle\MIDDLE~1\WLSERV~1.3\server\bin
;D:\oracle\MIDDLE~1\modules\ORGAPA~1.0\bin;D:\oracle\MIDDLE~1\JROCKI~1.5-3\jre\bin;D:\oracle\MIDDLE~1\JROCKI~1.5-3\bin;D:\app\alsemgpa\produ
ct\11.2.0\dbhome_2\bin;D:\oracle\product\11.1.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\Win
dowsPowerShell\v1.0\;C:\Program Files\Microsoft Application Virtualization Client;C:\Program Files\ThinkPad\ConnectUtilities;C:\Program File
s\Windows Imaging\;C:\Program Files\IDM Computer Solutions\UltraEdit-32;C:\Program Files\QuickTime\QTSystem\;D:\oracle\MIDDLE~1\WLSERV~1.3\s
erver\native\win\32\oci920_8;D:\oracle\MIDDLE~1\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:
[INFO ][memory ] GC mode: Garbage collection optimized for throughput, initial strategy: Generational Parallel Mark & Sweep
[INFO ][memory ] heap size: 65536K, maximal heap size: 1048576K, nursery size: 32768K
[INFO ][memory ] s-end: GC beforeK-after K (heap K), pause ms
[INFO ][memory ] s/start - start time of collection (seconds since jvm start)
[INFO ][memory ] end - end time of collection (seconds since jvm start)
[INFO ][memory ] before - memory used by objects before collection (KB)
[INFO ][memory ] after - memory used by objects after collection (KB)
[INFO ][memory ] heap - size of heap after collection (KB)
[INFO ][memory ] pause - total sum of pauses during collection (milliseconds)
[INFO ][memory ] run with -Xverbose:gcpause to see individual pauses
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
BEA JRockit(R) (build R27.6.5-32_o-121899-1.6.0_14-20091001-2107-windows-ia32, compiled mode)
Redirecting output from WLS window to D:\oracle\MIDDLE~1\USER_P~1\domains\DIZZYW~1\servers\AdminServer\logs\garbage.log
Het proces heeft geen toegang tot het bestand omdat het door een ander
proces wordt gebruikt.
D:\oracle\Middleware\user_projects\domains\dizzyworld\bin>
The last line says in Dutch "The process has no access to the file because it is being used by another process". I don't know if that is relevant.
Question
Now when I go back to my admin console, I don't see dizzy1 server RUNNING, it has status SHUTDOWN. Screen refresh doesn't help either.
Any suggestions ??
Edited by: PaulAlsemgeest on Apr 12, 2010 9:43 AM
Edited by: PaulAlsemgeest on Apr 12, 2010 9:44 AM
Edited by: PaulAlsemgeest on Apr 12, 2010 9:44 AM
Edited by: PaulAlsemgeest on Apr 12, 2010 9:45 AM
Edited by: PaulAlsemgeest on Apr 12, 2010 9:45 AM

user12115898 wrote:
Try to see if anything is running on that port ( the port you specified for dizzy1) also try to see if anything is running with the name dizzy1 on that box. Because sometime it happens that console doesnt update so if anything is running on that box with the same name or on that port, then kill it and try to restart it again.Hi,
I did an netstat -na > checkports.log
The server dizzy1 has been configured with Listen Port 7003 and SSL Listen Port 7004. Both are not in the checkports.log.
What I did see in my nodemanager.log was:
Domains file not found: D:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\nodemanager.domains, this is strange, because the file is really there.
And when I try to start server dizzy1, the Console gives the
Messages
- Warning For server dizzy1, the Node Manager associated with machine dizzyMachine1 is not reachable.
- Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
Any further help greatly appreciated.

Timezone issue with Node manager

Hi
We have a strange problem in our Weblogic manager server as below.
We started the manage server & Node manager in Jan 2011, when the daylight saving was on., then when time zone changed to winter time to summer time, node manager was unable to pick the time zone change.
It was still printing log files with wintertime in April 2011.
But after we restart the node manager & manage server, we found that then it has pick the summer time.
So want to know how to avoid such problems, that node manager & manage server should pick the current timezone (even when it change to summer to winter or vice versa) without restarting the servers.
Please can anyone guide me on this such strange problem & solution of it.
regards,
jay

Hi
My OS is Linux box and is able to pick the time correctly, but nodemanager & manage server which are started before time zone change is not able to pick the timezone change and continue running with timezone where it has started and the same time OS (date command) shows that it is changed to summer time.
Do i need to specify any configuration for nodemanger & manage server for picking the time when time zone is changed.
regards,
Jay
Edited by: user13160729 on May 23, 2011 11:07 PM

Oracle Management Server not starting up. says node manager is down!!!

Hi ALL,
We are trying to startup (OMS) Oracle Management Server but it's not starting up. it tries to connect to the node manager and says failed to connect to Node Manager as the node manager is not running.
OPMN also not running.
I have attached a snapshot so you can see.
PLEASE HELP
hi Again, below are the error reports
2014-01-30 18:56:52,360 [Thread-2] INFO commands.BaseCommand run.554 - <ERR>weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at omkn-ms01.int.unisa.ac.za:7403.
2014-01-30 18:56:52,360 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.PlainSocketImpl.socketConnect(Native Method)
2014-01-30 18:56:52,360 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at java.net.Socket.connect(Socket.java:529)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:228)
2014-01-30 18:56:52,361 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:200)
2014-01-30 18:56:52,362 [Thread-1] INFO commands.BaseCommand run.554 - <OUT>Attempt to connect to nm failed. Trying to start it...
2014-01-30 18:56:52,362 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:206)
2014-01-30 18:56:52,362 [Thread-1] INFO commands.BaseCommand run.554 - <OUT>status of node manager:
2014-01-30 18:56:52,362 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:53)
2014-01-30 18:56:52,362 [Thread-1] INFO commands.BaseCommand run.554 - <OUT>Not connected to Node Manager
2014-01-30 18:56:52,362 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:179)
2014-01-30 18:56:52,363 [Thread-2] INFO commands.BaseCommand run.554 - <ERR> at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:172)
regards,
Ambrose.

I assumethe node manager is not running on Exadata though you have posted in the Exadata forum !
how are you starting it. Are you using the gcstartup script within init.d ?
Thanks

Weblogic 8.1 Enable Load Balancing with Node Manager

Hi All,
Please provide any guidelines on how to enable Load Balancing in Bea Weblogic 8.1
I have configured *1 Admin Server* with *4 Managed Servers* on a single machine each having different port.
I want to setup load balancing such that any 1 of 4 ports responds when a central URL is clicked by the user.
Any guidelines are welcome.

Review the document How to Implement Load Balancing on SAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver

Server stop problem with node manager

Hi ,
I get this error often when I try to stop a managed server via the nodemanager
from the admin console or from the weblogic.Admin command. The server does not
stop and it goes into an unknown state and I have to do a force shutdown
[java] Error: [Could not execute command shutdown for server xxx via the N e Manager
- reason: [__COMMAND_EXCEPTION__Request: failed to execute command ' utdown' on
server 'xxx - reason: '[Unable to send shutdown request to server.> ].]
[java] Start server side stack trace: [java] weblogic.nodemanager.NodeManagerException:
[Could not execute comman shutdown for server xxx via the Node Manager - reason:
[__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' on server 'xxx
- reason: '[Unable o send shutdown request to server.]'> ].] [java] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
gerRuntime.java:472) [java] at weblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method) [java]
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(D amicMBeanImpl.java:732)
[java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicM anImpl.java:714)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1557)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1525)
[java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

Hi Anil,
A little more information might be helpful. Which version are you talking
about ? What is the server state when you issue the command ? Is the server
very busy. Are you able to get the server state from the nodemanager when
the server is running ? Are you able to communicate from admin server ->
nodemanager <-> managed server ?
cheers,
gaurav.
"Anil Jacob" <[email protected]> wrote in message
news:3fb16b7c$[email protected]..
>
Hi ,
I get this error often when I try to stop a managed server via thenodemanager
from the admin console or from the weblogic.Admin command. The server doesnot
stop and it goes into an unknown state and I have to do a force shutdown
[java] Error: [Could not execute command shutdown for server xxx via the N
e Manager> - reason: [__COMMAND_EXCEPTION__Request: failed to execute command 'utdown' on> server 'xxx - reason: '[Unable to send shutdown request to server.> .]
[java] Start server side stack trace: [java]weblogic.nodemanager.NodeManagerException:
[Could not execute comman shutdown for server xxx via the Node Manager -
reason:> [__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' onserver 'xxx> - reason: '[Unable o send shutdown request to server.'> ].] [java] atweblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
gerRuntime.java:472) [java] atweblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method)[java]
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DamicMBeanImpl.java:732)
[java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicManImpl.java:714)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1557)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1525)
[java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

Health Monitoring and Restart Configuration with Node Manager

We have a WL 9.2.2 instance setup using Node Manager to control it. It contains a JMS server with a persistant store that is in an oracle database. If the Oracle database becomes unavailable, the Weblogic server throws a number of errors eventually leaving the Managed Server in a "FAILED" state. I configuring/activated the following "Configuration - Health Monitoring" options for the managed server to have it automatically recover from this situation:
Health Check Interval: 180
Auto Kill If Failed: Checked
Auto Restart: Checked
Max Restarts Within Interval: 2
Restart Delay Seconds: 0
However it is not automatically restarting, even though the server shows in a "FAILED" state.
1st question: Do I need to restart the server with the settings above to have it react to the FAILED state? I would think that 3 minutes after I configured the above it would begin a restart on the FAILED server, but that does not happen
I also note on the "Configuration - OverLoad" page, there is a setting for "Failure Action:" that can be set to "Ignore, take no action" or "Force Immediate Shutdown of this server" I did configure/activate this for "Force immediate Shutdown..." but again the currently FAILED server does not restart.
2nd question: Does this "Configuration - Overload- Failure Action" setting override or effect in any way the configuration of restart on the "Configuration - Health Monitoring" page?
3rd question: Same as 1st question but for these Overload settings: Do they require a full restart of the managed server to somehow take effect?


Have you set the field : CrashRecoveryEnabled=true in file : ..\bea\weblogic92\common\nodemanager\nodemanager.properties ?

Load Balancing Directory Servers with Access Manager - Simple questions

Hi.
We are in the process of configuring 2 Access Manager instances (servers) accessing the same logical LDAP repository (comprising physically of two Directory Servers working together with Multi-Master Replication configured and tested) For doing this, we are following guide number 819-6258.
The guide uses BigIP load balancer for load balancing the directory servers. However, we intend to use Directory Proxy Server. Since we faced some (unresolved) issues last time that we used DPS, there are some simple questions that I would be very grateful to have answers to:
1. The guide, in section 3.2.10 (To configure Access Manager 1 with the Directory Server load balancer), talks about making changes at 4 places, and replacing the existing entry (hostname and port) with the load balancer's hostname and port (assuming that the load balancer has already been configured). It says that changes need not be made on Access Manager 2 since the LDAPs are in replication, and hence changes will be replicated at all places. However, the guide also states that changes have to be made in two files, namely AMConfig.properties, and the serverconfig.xml file. But these changes will not be reflected on Access Manager 2, since these files are local on each machine.
Question 1. Do changes have to be made in AMConfig.properties and serverconfig.xml files on the other machine hosting Access Manager 2?
Question 2: What is the purpose of putting these values here? Specifically, what is achieved by specifying the Directory server host and port in AMConfig.properties, as well as in serverconfig.xml?
Question 3. In the HTTP console, there is the option of specifying multiple primary LDAP servers, as well as multiple secondary LDAP servers. What is the purpose of these? Are secondary servers attempted when none of the list in the primary list are accessible? Also, if there are multiple entries in the primary server list, are they accessed in a round robin fashion (hereby providing rudimentary load balancing), or are other servers accessed only when the one mentioned first is not reachable etc.?
2. Since I do not have a load balancer setup yet, I tried the following deviation to the above, which, according to me, should have worked. If viewed in the HTTP console, LDAP / Membership / MSISDN and Policy configuration all pointed to the DS on host 1. When I changed all these to point to the directory server on host 2 (and made AMConfig.properties and serverconfig.xml on host 1 point to DS of host 2 as well), things should have worked fine, but apparently Access manager 1 could not be started. Error from Webserver:
[14/Aug/2006:04:30:36] info (13937): WEB0100: Loading web module in virtual server [https-machine_1_FQDN] at [search]
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Exception in thread "EventService" java.lang.ExceptionInInitializerError
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.iplanet.services.ldap.event.EventServicePolling.run(EventServicePolling.java:132)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at java.lang.Thread.run(Thread.java:595)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Caused by: java.lang.InterruptedException
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.sun.identity.sm.ServiceManager.<clinit>(ServiceManager.java:74)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: ... 2 more
In effect, AM on 1 did not start. On rolling back the changes, things again worked like previously.
Will be really grateful for any help / insight / experience on dealing with the above.
Thanks!

Update to the above, incase anyone is reading:
We setup a similar setup in Windows, and it worked. Here is a detailed account of what was done:
1. Host 1: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST1:389)
2. Host 2: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST2:389)
3. Host 1: Started replication. Set to Master
4. Host 2: Started replication. Set to Master
5. Host 1: Setup replication agreement to Host 2
6. Host 2: Setup replication agreement to Host 1
7. Initiated the remote replica from Host 1 ----> Host 2
Note that since default installation uses abc.....xyz as the encryption key, setting this to same was not an issue.
9. Started webserver for Host 1 and logged into AM as amadmin.
10. Added Host 2 FQDN in DNS Aliases / Realms
11. Added http://HOST2_FQDN:80 in the Platform server (instance) list.
12. Started Host 2 webserver. Logged in AM on Host 2, things worked fine.
At this stage, note the following:
a) Host 1:
AMConfig.properties file has
com.iplanet.am.directory.host=host1_FQDN
and
com.iplanet.am.directory.port=389
serverconfig.xml has:
<Server name="Server1" host="host1_FQDN" port="389" type="SIMPLE" />
b) Host 2:
AMConfig.properties file has
com.iplanet.am.directory.host=host2_FQDN
and
com.iplanet.am.directory.port=389
serverconfig.xml has:
<Server name="Server1" host="host2_FQDN" port="389" type="SIMPLE" />
c) If one logs into AM, and checks LDAP servers for LDAP / Policy Configuration / Membership etc services, they all contain Host2_FQDN:389 (which makes sense, since replica 2 was initialized from 1)
Returning back to the configuations:
13. On Host 1, login into the Admin server console of the Directory server. Navigate to the DPS, and confgure the following:
a) Network Group
b) LDAP servers
c) Load Balancing
d) Change Group
e) Action on-bind
f) Allow all actions (permit modification / deletion etc.).
g) any other configuations required - Am willing to give detailed steps if someone needs them to help me / themselves! :)
So now, we have DPS configured and running on Host1:489, and distributing load to DS1 and DS2 on a 50:50 basis.
14. Now, log into AM on Host 1, and instead of Host1_fqdn:389 (for DS) in the following places, specify Host1_fqdn:489 (for the DPS)--
LDAP Authentication
MSISDN server
Membership Service
Policy configuation.
Verified that this propagated to the Policy Configuration service and the LDAP authentication service that are already registered with the default organization.
15. Log out of AM. Following the documentation, modify directory.host and directory.port in AMConfig.properties to point to Host 1_FQDN and 489 respectively. Make this change in AMConfig.properties of both Host 1 as well as 2.
16. Edit serverconfig.xml on both hosts, and instead of they pointing to their local directory servers, point both to host1_FQDN:489
17. When you start the webserver, it will refuse to start. Will spew errors such as:
[https-host1_FQDN]: Sun ONE Web Server 6.1SP5 B06/23/2005 17:36
[https-host1_FQDN]: info: CORE3016: daemon is running as super-user
[https-host1_FQDN]: info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_04] from [Sun Microsystems Inc.]
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amserver]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [ampassword]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amcommon]
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amconsole]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [search]
[https-host1_FQDN]: warning: CORE3283: stderr: netscape.ldap.LDAPException: error result (32); matchedDN = dc=sun,dc=com; No such object (DN changed)
[https-host1_FQDN]: warning: CORE3283: stderr: Got LDAPServiceException code=-1
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getConnection(DSConfigMgr.java:357)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewFailoverConnection(DSConfigMgr.java:314)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewConnection(DSConfigMgr.java:253)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:184)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:194)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.initLdapPool(DataLayer.java:1248)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.(DataLayer.java:190)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:215)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:246)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.initialize(SMSLdapObject.java:156)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.(SMSLdapObject.java:124)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance0(Class.java:350)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance(Class.java:303)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.SMSEntry.(SMSEntry.java:216)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ServiceSchemaManager.(ServiceSchemaManager.java:67)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.getServiceSchemaManager(AMClientDetector.java:219)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.(AMClientDetector.java:94)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.mobile.filter.AMLController.init(AMLController.java:85)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:322)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:120)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3271)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3747)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]: failure: WebModule[amserver]: WEB2783: Servlet /amserver threw load() exception
[https-host1_FQDN]: javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
[https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]: ----- Root Cause -----
[https-host1_FQDN]: java.lang.NullPointerException
[https-host1_FQDN]: at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
[https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]:
[https-host1_FQDN]: info: HTTP3072: [LS ls1] http://host1_FQDN:58080 [i]ready to accept requests
[https-host1_FQDN]: startup: server started successfully
Success!
The server https-host1_FQDN has started up.
The server infact, didn't start up (nothing even listening on 58080).
However, if AMConfig.properties is left as it originally was, and only serverconfig.xml files were changed as mentioned above, web servers started fine, and things worked all okay. (Alright, except for some glitches when viewed in /amconsole. If /amserver/console is accessed, all is good. Can this mean that all is still not well? I am not sure).
So far so good. Now comes the sad part. When the same is done on Solaris 9, things dont work. You continue to get the above error, OR the following error, and the web server will refuse to start:
Differences in Solaris and Windows are as follows:
1. Windows hosts have 1 IP and hostname. Solaris hosts have 3 IPs and hostnames (for DS, DPS, and webserver).
No other difference from an architectural perspective.
Any help / insight on why the above is not working (and why the hell does the documentation seem so sketchy / insecure / incorrect).
Thanks a bunch!

Starting Servers with Ant

Hi,
I am using WLS 8.1 SP2 and the Ant that comes with it to start my managed server.
However, as documented the server VM shuts when the Ant script finishes. I have
tried adding fork="true" to my <wlserver> task but this still does not work. I
have resorted to using an <exec> task and a shell script but this does not seem
as nice.
Can anyone offer some advice?
Regards
Geoff

Well my examples assumed you were starting a managed server that was
connecting an admin server listening @ t3://127.0.0.1:7001. If your admin
server isn't listening at that address and on that port you'll need to
obviously make changes to the build file ;-) but I know it will work as I
pulled the example straight from a project build file. You could also
enable MSI on the servers but that's not an ellegant sollution just to get
around an error. Let me know if it works for you ;-)
~Ryan Upton
"Geoff Lawrence" <[email protected]> wrote in message
news:40e900ce$1@mktnews1...
>
Ryan,
I tried that but I got this:
[java] <05-Jul-2004 08:14:42 o'clock BST> <Error> <Management><BEA-141137>
<Managed Server was attempting to boot in Managed Server Independencemode, but
was unable to complete the boot process as the Managed Server was unableto locate
the cached configuration file:/opt/apps/bea/user_projects/domains/mydomain/./msi-config.xml>
>
Which is fair given I do not have one of those files! Any suggestions?
Regards
Geoff
"ryan upton" <[email protected]> wrote:
Geoff,
You could try:
<java classname="weblogic.Server" fork="yes"
dir="${env.WEBLOGIC_DOMAIN}">
<jvmarg value="-Xms32m"/>
<jvmarg value="-Xmx32m"/>
<sysproperty key="weblogic.Name" value="server1"/>
<sysproperty key="bea.home" value="${BEA_HOME}"/>

<sysproperty key="weblogic.management.username" value="system"/>
<sysproperty key="weblogic.management.password" value="weblogic"/>
<sysproperty key="weblogic.management.server"
value="t3://127.0.0.1:7001"/>
<sysproperty key="java.security.policy"
value="${WL_HOME}/server/lib/weblogic.policy"/>
</java>
If you want to start more than one with the same script
<parallel>
<java classname="weblogic.Server" fork="yes"
dir="${env.WEBLOGIC_DOMAIN}">
<jvmarg value="-Xms32m"/>
<jvmarg value="-Xmx32m"/>
<sysproperty key="weblogic.Name" value="server1"/>
<sysproperty key="bea.home" value="${BEA_HOME}"/>
<sysproperty key="weblogic.management.username" value="system"/>
<sysproperty key="weblogic.management.password" value="weblogic"/>
<sysproperty key="weblogic.management.server"
value="t3://127.0.0.1:7001"/>
<sysproperty key="java.security.policy"
value="${WL_HOME}/server/lib/weblogic.policy"/>
</java>
<java classname="weblogic.Server" fork="yes"
dir="${env.WEBLOGIC_DOMAIN}">
<jvmarg value="-Xms32m"/>
<jvmarg value="-Xmx32m"/>
<sysproperty key="weblogic.Name" value="server2"/>
<sysproperty key="bea.home" value="${BEA_HOME}"/>
<sysproperty key="weblogic.management.username" value="system"/>
<sysproperty key="weblogic.management.password" value="weblogic"/>
<sysproperty key="weblogic.management.server"
value="t3://127.0.0.1:7001"/>
<sysproperty key="java.security.policy"
value="${WL_HOME}/server/lib/weblogic.policy"/>
</java>
</parallel>
HTH, someone else might have a better idea :)
~Ryan Upton
"Geoff Lawrence" <[email protected]> wrote in message
news:40e4243e$1@mktnews1...
Hi,
I am using WLS 8.1 SP2 and the Ant that comes with it to start my
managed
server.
However, as documented the server VM shuts when the Ant script
finishes.
I
have
tried adding fork="true" to my <wlserver> task but this still doesnot
work. I
have resorted to using an <exec> task and a shell script but this doesnot
seem
as nice.
Can anyone offer some advice?
Regards
Geoff

After I do Node Manager nmConnect(...) I can no longer start a managed svr

I am running 10.3.2 on both windown and redhat
I have a domain with AdminServer and one managed server.
I can start AdminServer from the shell with startWebLogic.cmd
I can log into the web based 'console'
I can go to Environment -> Servers and start/shutdown the managed server.
If I use WLST and...
connect('user', 'pass', 't3://localhost:7001')
nmEnroll('fullPathToDomainDir')
I am still OK, I can still use the console to start and stop the managed server and I can so WLST start('managedSever')
I stop running the AdminServer from the shell - it is no longer running.
Now, I want to start the AdminServer with Node Manager, so (with WLST)...
nmConnect('user','pass','localhost','5556','domainName)
I get the error...
'Cannot connect to Node Manager: Access to domain 'domainname' for user 'user' denied
As suggested elsewhere, I go and edit nm_password.properties and change the hashed user/pass to
username=user
password=pass
I go back to WLST, now nmConnect works!!!
I can then do..
nmStart('AdminServer')
The AdminServer start, I go to the web console, and I try to start the managed server, I get...
'For server managedServer, the Node Manager associated with machine machineName is not reachable'
So it looks like the re-hashed password from nmConnect(...), while it works for WLST, it no longer works for the console.
Bottom line, I can get either get the console to start the managed server (if I do WLST connect(...) + nmEnroll(...)) or I can get WLST to start the servers (if I reset nm_password.properties and do nmConnect), but I can not get WLST to start the AdminServer and have the AdminSever console start the managed server.
I know for a fact that others have run into this, but in the threads I found, the thread stops before a soluton is posted.
Anyone know about this issue?
Regards

There are a couple of things you need to keep in mind:
-- There is one and only one valid username / passwrod for connecting to the node manager.
-- When you use nmEnroll, the username / password placed in the nm_password.properties file is taken from the admin server, hashed an placed in the nm_password file.
-- When you edit the nm_password.properties, and place the line "enter in username=user / password='pass',", in clear text, you have over ridden the U/P \thje admin server knows.
That is why you have a situation, oen of the two works but never both at the same time.
What you need to do is:
-- Log in to the WL Console.
-- in the Domain Tree, click at teh root level, which is the domain name.
-- Under the security tab, under advanced there is a node manager username / password.
-- Click on "Lock and edit", and change those to match what you are using through WLST.
-- Activate changes.
-- Just to make sure all is well, use nmEnroll to re enroll the node manager again , this way the nm_password.properties file will be set up correctly.
Now, both the WL Console should be able to talk to the node manager as well as nmConnect('user','pass','localhost','5556','domainName) would succeed.
Also, if you want to use node manager to start /servers, make sure you edit the file ( $WL_HOME/common/nodemanager/nodemanager.properties) and change the line
StartScriptEnabled=false
to
StartScriptEnabled=true
This will ensure all the proper class paths and properties etc needed are set up when using the node manager.
You would need to bounce the node manager for this change t take effect
Hope this helps.

For server the Node Manager associated with machine is not reachable

Hello all,
I am getting this error, when i start my Managed Server which is in shutdown state
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The configuration details are
i am using weblogic 9.2 MP3 version in windows 2k3 server.
It has a machine vm-bea-dev, a cluster cluster-saa-dev, to which both the managed servers saa-dev-1 and saa-dev-2 are assigned. There are 3 applications deployed onto managed Server 1 and 1 for managed Server 2.
Managed Server 1 is in shutdown state, and when i start the server, it gives the error specified below
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The same for Managed Server 2 too, and this server is in Admin State, i dont know how it went into that state.
Can somebody please help me reslove it.
Thanks in advance

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

Starts servers with node manager

Similar Messages

Maybe you are looking for