Script vs Java Node Manager - Yes again!

Similar Questions

• Steps to install and configure Node Manager on the local machine and remote

  Hello
  
  I'm using WLS 10.3 on Windows.
  I did the following till now.
  
  (1) installed WebLogic 10.3 on one machine (local computer, on which I created the field and my Server Admin is under execution. 1 managed server is also created on this machine).
  (2) installed WebLogic 10.3 on computer B (remote computer, which Managed Server 2 will be created).
  (3) on the machine, I used the Setup Wizard and create a domain. When creating the domain, I did the following:
  (i) created two managed servers.
  (II) create a cluster
  (III) the servers assigned to regroup.
  (IV) created two machines.
  (v) the servers assigned to machines (Admin Server and MS_1 to the machine and MS_2 machine B).
  
  (4) start Admin Server.
  (5) on the administration Console, I made some configurations for the node Manager on Machines-> Machine A-> Node Manager. The assigned values:
  (i) type (SSL)
  (II) Address (ip_address machine A) listen
  (III) listening port (5556)
  (6) in the same way it did for Machine B.
  
  So far, phsically the managed server (MS_2) directory and configuration is not there on the Machine B (its only configured on A computer because I created the field on computer A).
  
  I went through the documents on the Node Manager and found what to configure. But I have not found what is the sequence of configuration.
  
  Please let me know the sequence of steps I must follow to install and configure the Manager of nodes on the local and remote machine. I want to use Java Node Manager (not the Script node Manager).
  
  Thank you
  
  Sanjay

  Hello Sanjay

  Basically if I understand your question, you have A machine where you had installed ""(permet de supposer admin serveur) and "VAS_MS1_A VAS_ADM_A" (lets assume the managed server.» And on the second machine B you want to create a managed server 'VAS_MS2_B' which must be controlled by node manager, so that you can start console, auto restart the managed server and perform other activities such as the migration of servers using nodemanager. If this is correct, this is the sequence of steps.

  Since you say you are on windows, I start from the principle

  WebLogic version 10'3
  BEA_HOME:-c:\bea
  WL_HOME:-C:\bea\wlserver_10.3
  DOMAIN_DIR:-c:\VASDomains

  Machine has

  (1) install the BEA.
  Using 2 Setup Wizard) create the domain under "c:\VASDomains".
  (3) to start the Admin Server and connect to the console and create two machines "Machine_A" and "Machine_B". Select the types of machines as 'other '.
  (4) once machines are created go to each machine and go to the tab 'NodeManager' and enter the details nodemanager.
  (5) create server 'VAS_MS1_A' and 'VAS_MS2_B '. Enter the respective details. To "VAS_MS1_A", enter a machine name of host or ip and machine "Machine_A" and "VAS_MS2_B", enter the hostname of the machine B or ip and machine 'Machine_B '.

  Machine B

  (1) on this machine install BEA
  (2) then you have to register the machine with the Manager of nodes. So for this first set the environment go to "C:\bea\wlserver_10.3\server\bin" and run "setWLSEnv.cmd". Then type 'java weblogic. Enter the WLST", once you run this command at the next prompt Details ' connect ('', 'adminserverpassword','t3: / / adminserver:port" ")
  (3) then run this command.
  nmEnroll('c:/VASDomains','C:\bea\wlserver_10.3\common\nodemanager')

  Orders above fits machine with nodemanager. The first parameter is "domestic field", now if you see "c:\". ' directory 'VASDomains' will be created. Second parameter is nodemanager House, now if you go into nodemanager houses that some properties will be updated.
  (4) If this node Manager runs on this computer, kill that one and restart the node Manager again.
  (5) now if you go to "Adminconsole--> Machines--> Machine_B--> Monitoring" you can see the status as accessible.
  (6) now you can go "Servers--> VAS_MS2_B--> Control" and start the server. Newspapers to see how the server gets up the tail.

  If you want more details on "nodemanager", dedicated to my 'vasweblogic.blogspot.com' blog, not a lot of messages but post nodemanager can help you.

  I hope that's what you're looking for, have a nice day.

  Naour Vijay.

• Node Manager

  Dear all,

  Please explain below.
  

  There is One Node Manager for each Machine.

  There is One Node Manager for each area.

  
  

  Thank you and best regards,

  Irfan
  

  
  

  
  

  What version of weblogic do you use?

  From WebLogic Server 12.1.2 it provides an option to set up and run the node Manager: default Node Manager is now configured with the domain name.

  In previous versions, a Node Manager process was not associated with a specific WebLogic domain but with a host computer. You have used the same process Node Manager on server control instances in any WebLogic domain, as long as the server instances reside on the same computer, a reach machine by host Node Manager. In this version of WebLogic Server, Java of Node Manager version is configured by default to control all the server instances in the same domain, one by domainNode Manager. Server instances must not reside on the same machine. Now you can run each specific field-based Java Node Manager with a different configuration.

  See: https://docs.Oracle.com/middleware/1212/WLS/NODEM/overview.htm#NODEM113

  https://blogs.Oracle.com/WebLogicServer/entry/new_node_manager_configuration_model

• Stop a server managed using WLST and Node Manager

  Hello

  I use Node Manager (NM) to start my managed servers. After connecting to the Server Admin, I run the command:

  Start ('myserver1', 'Server')

  I check the log file and the console and the managed server shows no error, either it RUNS. The tail of the log file says "SOA platform is running accept queries"

  I'm now trying to write a script to stop for the same managed servers. I connect to the Node Manager via wlst, connect to the Admin Server successfully and deliver:

  Shutdown ('myserver', 'Server')

  Here is the error I see in the managed server log file:

  [JCABindingManager]: this operation is not supported for JCA base MDB.

  The managed server then passes State SUSPENDED.

  I have renamed the data files, cache and tmp, restarted the server and once again tried to arrest him, but the same thing happened.

  Any suggestion is appreciated.

  Thank you

  Andy

  What happens if you add strength = "true" as an additional parameter for your

  stop command?

• Node Manager warning - need help

  Once after the Node manager stopped and started, I get the warning in the nodemanager.log file below.

  < 26 March 2015 05:01:45 > < WARNING > < error e/s all by closing the socket connection >

  java.nio.channels.ClosedChannelException

  Below the details I have read from the console

  Status:	Inactive
  Description of the problem:	javax.net.ssl.SSLHandshakeException

  error below I get when I try to start the server from the console, run

  To the server Server1, the Node Manager associated with oam_server1 of the machine is not accessible.

  All selected servers are currently in a State that is not compatible with this operation or are not associated with a Node Manager running or you are not authorized to perform the requested action. No action will be taken

  After WLS 8.1.x Weblogic Nodemanager doesnot require a CustomTrust.

  However, even if you specify the customTrust parameter in nodemanger.properties should not cause problems. It ignores only them.

  Make sure that the following settings are added to ndoemanager.properties:

  CustomIdentityAlias = xx

  CustomIdentityKeyStoreFileName = identity.jks

  CustomIdentityKeyStorePassPhrase = xxx

  CustomIdentityKeyStoreType = JKS

  CustomIdentityPrivateKeyPassPhrase = xxx

  Keystore = CustomIdentityAndCustomTrust

  Make sure that the CN of the certificate that you use is the same as the address to listen specified in the nodemanager.properties file, if it is not, and then add the following indicator d as an option java script startNodemanager:

  -Dweblogic.nodemanager.sslHostNameVerificationEnabled = false

  If you use SHA2 certificates, so make sure you add the following parameter as a java (enable JSSE) option in the startNodemanager script:

  -Dweblogic.security.SSL.enableJSSE = true

  In addition,

  Connect to the console-> machinery-> nodemanager-> Listenaddress (specify address of listening that you mentioned in the nodemanager.properties file)

  The certificate root of nodemanager must be imported in the Admin Server Trust keystore.

  If you use the same keystore in ndoemanager and the administrator of the server, and then you skip the previous step.

  -Emile Laurent

• Node Manager or the administrator of the server - which one to start first?

  Hi Experts,

  Somehow I see his way.

  OBIEE 11.1.1.6 | OBIEE

  To start the Oracle Business Intelligence system, you start:

  • the node Manager (It is by default windows service in Enterprise Installation of OBIEE 11 G)
  • the Administration Server (it is weblogic Admin Server)
  • managed servers (comes with the company of OBIEE 11 G Installation)
  • and then you start the components of the system. (All the OBIEE components: BI Server, presentation server, schedular, Java host, Cluster Services.)

  and in other places, I see this...

  OBIEE 11G - starting Oracle Business Intelligence | GerardNico.com (BI, OBIEE, data warehouse and OWB)

  To start the Oracle Business Intelligence system, you start:

  • the Administration Server
  • the Node Manager
  • servers managed,
  • and then you start the components of the system.

  I have Linux environment and there only one BI server and I'll like that.

  (1) script startWeblogic.sh

  (2) startNodeManager.sh

  (3) startManagedWeblogic.sh

  (4) then the system components.

  Thank you

  Ashish

  Hi RM,.

  When it comes to a simple installation you can run on the management server without nodemanager but when you do the installation of the company and trying to bi_server1 (managed server) not to mention the nodemanager.sh you will get the following message. Correct me if my interpretation is wrong!

  http://obinsight.blogspot.com/2013/02/starting-OBIEE-11g-service-components.html

  Thank you

  Angelique

• Can I run more than one Node Manager by machine?

  EIS,
  
  We have a situation in our project, where we need to run different areas on a Solaris machine in modes different from java.
  Domain1 say must be running in the 32-bit version of java while Domain2 should be run in 64-bit mode because of the nature of the tests currently underway in different areas.
  We could successfully get both running in different modes of java at the same time by changing the startup scripts to decide what data model South to start the servers based on some parameters. However, the pain here is with the node Manager.
  
  I believe that there should be a Node Manager running by the machine for all areas currently running on this computer. Whenever I have to run a different mode than what Node Manager domain runs on java, so I had to kill the node Manager and launch it in the same version that I want to start other servers in as Node Manager uses his departure parms internally to start managed servers (Note: there is no problem in running the administration server regardless of the node as expected Manager mode).
  
  Can someone tell me if there is a way around these problems?
  I want to know if we can run more than one Manager node by machine.
  
  Here are the details of my approx.
  
  WebLogic Server 10.3
  Solaris 10 SPARC 64 bit (SunOS 5.10 Generic_142900-14 sun4v sparc)
  Java version "1.6.0_20.
  
  Hope that all makes sense...
  
  See you soon,.
  Satish.
  
  Published by: apsnaidu on March 15, 2013 15:29

  Running multiple NodeManagers with different settings on the same box: -.

  http://Tim.blackamber.org.UK/?p=797

• Problem: WebLogic Node Manager under Windows Services

  Hi all
  
  Details of the environment :
  -Windows Server 2008 R2 - x 64
  -Oracle WebLogic Server 11 g R1 (10.3.6.0) - generic
  -Reports and forms oracle 11g R2 (11.1.2.0) - x 64
  -Oracle JRockit JDK R28.3.0 - x 64
  
  I have windows servers that we want managers node and managed to run instances. As you can see I would like to run Node Manager under Windows Services.
  
  I use this guide:
  
  < a link = http://wlsjavatips.blogspot.com/2009/09/how-to-install-node-manager-as-windows.html >http://wlsjavatips.blogspot.com/2009/09/how-to-install-node-manager-as-windows.html< /a >
  
  Create boot.properties that include the user name and password:
  
  - AdminServer (location: < WL_HOME > \user_projects\domains\ < DomainName > \servers\AdminServer\data\nodemanager)
  - WLS_FORMS (location: < WL_HOME > \user_projects\domains\ < DomainName > \servers\WLS_FORMS\data\nodemanager)
  - WLS_REPORTS (location: < WL_HOME > \user_projects\domains\ < DomainName > \servers\WLS_REPORTS\data\nodemanager)
  
  Results :
  1 are you able to automatically start all servers (AdminServer, WLS_FORMS and WLS_REPORTS) after the server restarted.
  2. I can't access to http:// < hostname >: 7001/console, < hostname > http://: 7001/em, http:// < hostname >: 9001/forms/frmservletand http:// < hostname >: 9002/reports/rwservlet
  
  Questions :
  1. on WebLogic Console http:// < hostname >: 7001/console, the status of AdminServer, WLS_FORMS and WLS_REPORTS are running, but the State of health is OK just to AdminServer, and others have no status.
  2. as I said before, I can run my form on http:// < hostname >: 9001/forms/frmservlet and run my report on http:// < hostname >: 9002/reports/rwservlet. But when I found
  on Order FM OEM http:// < hostname >: 7001/em, the State of WLS_FORMS and WLS_REPORTS are down. I can't monitor sessions connected to the server and I can not change the configurations via EM.
  
  Any help is greatly appreciated and sorry for my bad English.
  
  Thank you and best regards,
  
  -Rob-

  Hello

  After a reboot the server I had the same problem, also windows environment. AdminServer but OK/console WLS_FORMS and WLS_REPORTS nothing.

  Process Explorer indicated there are 3 java process for each server that had begun the nodemanager (beasvc)
  Also everything worked very well for end users, but not for the side default where forms and reports where "down".

  I added settings offers and reinstalled the service nodemanger. But always without success.

  Finally I solved it by stopping the servers (WLS_FORMS and WLS_REPORTS) in the / console and by them from the option default (fusion middleware control)

  Everything is 'healthy' and 'OK' again!

  I think that nodemanager and the opmn obtained in a "things are complicated" after the break-up... I mean :) server restart

  Greetz,

  B.

• WebLogic Node Manager as a Windows Service

  Hi all
  
  I tried all my resources / google / etc to solve this problem.
  
  We have servers windows that we managers node and instances managed to run. As you can see, we start Node Manager under Windows Services.
  
  We have a network mapped to W: to \\wlsadminmachine\$WLS_SHARE share drive where we have entire folders of domain and Node Manager. I used BEA condition Node Manager install scripts and Service Windows are created. I specified a UNC path during the installation of the service. No problem.
  
  I opened regedit and look at the params.
  CmdLine =- client-Xms32m-Xmx200m - classpath ".;" E:\APPS\bea_x64\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar; E:\APPS\bea_x64\jrockit-R27.5.0-JDK1.5.0_14\lib\tools.jar; E:\APPS\bea_x64\WEBLOG~1\server\lib\weblogic_sp.jar; E:\APPS\bea_x64\WEBLOG~1\server\lib\weblogic.jar; E:\APPS\bea_x64\WEBLOG~1\server\lib\webservices.jar; »-Djava.Security.policy="E:\APPS\bea_x64\WEBLOG~1\server\lib\weblogic.policy «-Dweblogic.nodemanager.javaHome="E:\APPS\bea_x64\jrockit-R27.5.0-jdk1.5.0_14"- DListenAddress ="wlsadminmachine1"- DListenPort ="1011"weblogic. NodeManager
  
  JavaHome=E:\APPS\bea_x64\jrockit-R27.5.0-jdk1.5.0_14
  
  ExecDir = \\wlsadminmachine\$ WLS_SHARE\domain_dir\nodemanager
  
  Path = E:\APPS\bea_x64\WEBLOG~1\server\native\win\x64; E:\APPS\bea_x64\WEBLOG~1\server\bin; E:\APPS\bea_x64\jrockit-R27.5.0-JDK1.5.0_14\jre\bin; E:\APPS\bea_x64\jrockit-R27.5.0-JDK1.5.0_14\bin
  
  Log=\\wlsadminmachine\$WLS_SHARE\domain_dir\servers\NM_ADMIN_PROD_UPGR\NM_ADMIN_PROD_UPGR_service.log
  
  
  Security: I ensure that the Service is running as the user who shared the :) mapped drive
  
  When I try to run the service, I get an Error Message:
  ===================== Error Logs ==========================================
  [Fri Apr 23 14:51:41 2010] [ServiceStart] Thread created successfully
  [Fri Apr 23 14:51:41 2010] [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] statement SCM of SERVICE_START_PENDING with delay = 0
  [E] [StartJVM] a fine of a JVM Impossible
  [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] statement SERVICE_RUNNING SCM
  [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] waiting for several events
  [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] is waiting for several events. Wait = 1
  [Fri Apr 23 14:51:41 2010] [E] [ServiceStart] error in the JVM. Cause = could not find a JVM.
  [Fri Apr 23 14:51:41 2010] [I] [ServiceStart] inform SCM SERVICE_STOP
  ===================== Error Logs ==========================================
  
  I have being debugged the issue using the following URL: http://connectionserver.blogspot.com/2009/06/weblogic-as-windows-service.html
  
  I am able to run the command line node Manager except that my exec directory is W:\domain_dir\nodemanager.
  
  I've eliminated all wait because of the execution of java in the command prompt with exec as a uncpath [\\wlsadminmachine\$WLS_SHARE\domain_dir\nodemanager] directory.
  
  Details of the environment:
  Windows Enterprise Server 2008 SP 2
  Processor Intel Xeon CPU - 2
  16 GB OF RAM
  Operating system - 64 bit
  
  Strange behavior:
  When I try to install a Manager service node on the admin machine which is "wlsadminmachine" where the shared drive is available for the other Manager node servers, all works fine. This kind of proves that if the shared drive is local and not the network drive, it works. I'm really going crazy. Please help me.
  
  Thank you and best regards,
  Pazhanikanthan. P

  Hi Paz,

  Its great you did it works. In the interest of all those who may be blocked with how to map network drives when weblogic or node Manager must be run as a windows service, please go through the below.

  *******************************************************************************************

  http://download-llnw.Oracle.com/docs/CD/E13222_01/WLS/docs81/notes/resolved_sp05.html

  CR202167
  When beasvc on Win2003 starts a server on a network share, an error occurs is no longer.

  Now the network drive mapping happens within the service itself. The following new settings have been added to the beasvc:

  localName
  RemoteName
  RemoteUser
  RemotePassword
  Usage example:
  -localname: "X:»-remotename:"\\172.17.24.130\src810sp4"- remoteuser:"xyz"- remotepassword:"xyz ".
  You map \\172.17.24.130\src810sp4 to your local computer as X: and the remoteuser and remotepassword are used to connect to the remote computer.

  *******************************************************************************************

  Note: Services Windows runs as a different user session and is not the same as the session of the interactive user used to log on to the computer. Beasvc has therefore to map the drive under this different session and to get all the details in its configuration.

  Kind regards
  Carina

• View CD can't mistake of player Director, was not found in the object #getPropRef, Script error. Continue?, yes no

  OT: Error player Director, not found in the object #getPropRef, Script error. Continue?, Yes No. nursing student cannot run his CD CD practice to work on other laptops. but not on it!

  Nursing Student cannot carry out its practice CD which comes with Prentice Hall Nursing book: "medical and nursing care 2nd edition, comments & justifications surgical."  CD works on PC and a laptop running Windows XP, Vista and Windows 7 and on an iMac; but not on it!  She has a Toshiba laptop with Windows Vista Home Premium and it just doesn't work!  My wife has lent her one of its laptops with Windows Vista, but the CD works fine.  What is the problem? I called Prentice Hall and got no help from them!  They said it was a computer problem.  This student is an exchange student and she would really any help.  I tried to clean the system and even tried the Optimizer5.2 perfect for the correction of errors in Script, but it didn't work.  Help please!  My only recourse is to backup all files and wipe the disk clean and start again to do a reinstall of all applications.  Any other ideas?  She had the phone since 2005 and the hard drive has only about 30% free space left on 147 GB.

  Hello cobblestone47,

  1. What is the version of the steering drive you use on your computer?

  2. the other users who are able to play the CD using the Director or shockwave player player is

  Player de Macromedia Director is also known as the Shockwave Player. I suggest that you uninstall the Director player and install the latest version of Shockwave player, and check if you have the same problem.

  You can follow the link below to download and install the latest version of Shockwave player:

  http://get.Adobe.com/Shockwave/

  Thank you
  Irfan H, Engineer Support Microsoft Answers. Visit ourMicrosoft answers feedback Forum and let us know what you think.

• Node Manager command 'CALL' failed done Oracle 12 c

  Hi all

  I started the servers like this

  (1) node manager started. Running successfully

  (2) logical web Admin Server started. Running successfully

  (3) Wls_forms server started. Running successfully

  (4) Wls_Reports server started. Running successfully

  (5) http Server. ohs1 running successfully

  After I began namingservice.bat 14021-> the appointment service has started successfully.

  But when I start the server reports-> startComponent.cmd rep_wls_reports <-my name of report server started successfully.

  Status is displayed in the Console of Node Manager rep_wls_reports now works.

  But after awhile, he launched the warning

  < WARNING > < order Node Manager 'INVOCATION' unexpected failure due to: [Plugin not found for the 'ReportsServerComponent' system component type, type of plugin "METRICS"].

  Please check Node Manager log or journal of the server for detailed information. >

  Please provide the solution? How do I solve this problem

  Thanks to everyone who helped me.

  My problem has been resolved I have reinstall java, weblogic, and forms 12 c my problem has been resolved.

• Node Manager can be used to restart Weblogic Server Administration?

  Hello guys,.

  According to my understanding 'Machines' created in Weblogic are the logical representation of define what Node Manager to Point to perform actions on managed servers. But when we place servers on Machine here in my environment I get name "Admin Server" also make a link to a machine.

  So far, I thought that assistance from the node Manager we can control the events of life cycle of the managed server. Is it possible to order the start/stop of the Administration also using Node Manager server?

  PS: I use Weblogic 12 c and configured NM within my domain.

  Kind regards

  Puneet

  Hello

  Yes, short words, it is possible. Check out this doc for more information on how to accomplish this task > http://docs.oracle.com/cd/E24329_01/web.1211/e21050/starting_nodemgr.htm#NODEM219

  Kind regards

  White

• WLST script to stop the managed server takes 30 mins

  Hello

  I have a setup where I use Node Manager and WLST to stop a managed server. The script is simply:

  nmConnect('weblogic;,'password','123.456.78.9','5556','soa_domain','/u01/soa_domain','plain')

  Connect('weblogic','password','t3://123.2456.78.9:8001')

  Shutdown ('soa_ms1', 'Server', 'true ', 3000,' force = true')

  Exit()

  It takes usually more than 30 minutes for the server managed to stop using this method. However, if I use the console and select the managed server and select to FORCE SHUTDOWN NOW, the action is completed in less than 2 minutes.

  Why is there such a difference in time?

  Thank you very much

  Andy

  Hello

  Have you tried running the command shutdown() WLST directly and not the script created... ? If so the results were the same... ?

  In addition, in your script, I think it would be advisable to print the output for each line text using the command 'Print', just to see where exactly it takes all this time...

  [EDIT: now I noticed in the shutdown command, you use a timeout of 3000 seconds value, which, according to the wlst command Manual is "Duration (in seconds) during which WLST waiting for subsystems to complete ongoing work and to hang before you stop the server".] Try to reduce this value to, say, 30. If the shutdown command would look like this:

  Shutdown ('soa_ms1', 'Server', 'true ', 30,' force = true')

  Or, you can completely remove > shutdown('soa_ms1','Server','true','force=true')

  [/ END EDIT]

  Kind regards

  White

• The Node Manager associate machine MyServer01 is not accessible

  Hello
  
  I work with the version 11.1.2.2, my EssbaseAdminServices0 from the logical Web server running.
  I have the following error when I started s EssbaseAdminServices0.
  
  1. for EssbaseAdminServices0, the node Manager server machine MyServer01 is not accessible.
  2. all selected servers are currently in a State which is not compatible with this operation or are not associated with a Node Manager running or you are not authorized to perform the requested action. No action will be taken.
  
  
  I checked Node Manager in services, but it is not present in the services also.can u suggest me how can I get Node Manager.
  So could you please tell me how should I start my EssbaseAdminServices0 of web logic server.
  
  Thank you

  You must have windows services for each of the Web start Applications and then for example 'Hyperion Foundation Services - Managed Server'
  If you want to create the node Manager as a service there is a script to \wlserver_10.3\server\bin\installNodeMgrSvc.cmd

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Could not start the server via the SOA node Manager

  Hi all
  
  I try to install AIA 11.1.1.6.0 on top of the SOA Suite 11.1.1.6.0.
  
  I was able to install the weblogic, UCR, soa and osb servers server correctly. Now, before installing the AIA, the document I am following it says, make sure to start the server soa through the Manager of nodes.
  
  Now I start to the administrator of the server, then the node Manager, to make sure I checked the node Manager is in place, I logged the weblogic console, went to the Machines, and I see that it's upward and accessible.
  
  Now using WLST commands, first of all, I have connected to Manager nodes by using the nmConnect() command, so I try to start the server soa through node Manager with the command start ('soa_server1').
  
  I get an error when you try to start the server with the command nmStart() soa, below is the error message...
  
  «Error at startup server soa_server1: weblogic.nodemanager.NMException: Exception when starting Server «soa_server1»»
  
  I ran the command dumpStack(), and I get the output as 'no trace available battery.
  
  If I am able to start the server soa through the node Manager, I can go ahead and install the pack of AIA, but wrong to let me go forward.
  
  I also tried to boot the server from soa through the weblogic console, go to the servers tab, select the soa_server1 and start, the State of the soa server will "FAILED_NOT_RESTARTABLE".
  
  I followed some of those blogs like...
  
  http://Neeraj-SOA-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
  
  http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
  
  Experts, please give your opinion.
  
  Thank you very much
  N

  Hi Patricia,

  I had exactly the same problem some time ago...

  The cause:
  There are two servers trying to run in debug mode and use the same debug port
  -Xrunjdwp: transport = dt_socket, address = 8453, server = y, suspend = n

  Possible solutions:
  1. turn off debugging (this is what I did)
  2 use the various debugging ports to different servers (difficult to do because the servers share the same scripts)

  What worked for me was:
  1. in % DOMAIN_HOME%\bin, I created a script called startWebLogic_nodebug.cmd with the following content:
  %CD%\bin\startWebLogic.cmd /nodebug % *.
  2. in nodemanager.properties, I changed the following property
  StartScriptName = startWebLogic_nodebug.cmd

  Now my servers start without debugging...

  I hope this helps.

  See you soon,.
  Vlad