Weblogic Installation gets managed server of old installation

Hi. In my CentOS I had a weblogic 10.3.3.0 with three managed servers, then I unistalled it, delete the folder of installation manually for the files that the uninstaller didn't erase and then I installed again weblogic (jdevstudio11113install.bin) with new managed servers and when I want to start them up it tells me that it doesn't exist that the only ones that exist are the old ones I had in the previous installation. So I assume they are in a hidden file that I had to remove or update with new managed servers, which sounds strange because that should be deleted during uninstall process. Anyway any hint would be highly appreciated. Greetings.

From what I understand about your problem you have a domain - Admin server running on one physical machine and Managed server running on another physical machine, when stopping the Managed server its getting hung at suspending state, which in turn is causing Admin server slow down in response or hang.
          Please confirm on this how are you stopping and starting your managed server
          make sure that you do not use localhost when creating domains which spread across more than one physical machine.
          Make sure that your Adminserver & Managed server have address as hostname's of physical server instead of Localhost
          You should be starting / stopping Managed server something like this
          startManagedWeblogic.sh -url t3://AdminserverHostName:PortNo <servername>
          stopManagedWeblogic.sh -url t3://AdminserverHostName:PortNo <servername>
          Let me know if you still have the problem.
          Weblogic Consultant

Similar Messages

How to get managed server name in Weblogic10.2 ?

Hi
I want to get managed server name from a cluster in a servlet or util project class whom that one is called by ?
Do I have to implement any interface or I have to extends a class ? Please help me to resolved.
Thanks

Here is a snippet of code that I use in WL10 MP1 that works fine:
import javax.management.MBeanServer;
import javax.management.ObjectName;
import javax.naming.InitialContext;
String managedServerName = null;
InitialContext ctx = null;
try {
//fetch managed server name by accessing the
//RuntimeServerMBean using the
//MBeanServer interface
ctx = new InitialContext();
MBeanServer server = (MBeanServer) ctx.lookup("java:comp/env/jmx/runtime");
ObjectName service = new ObjectName("com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean");
managedServerName = (String) server.getAttribute(service, "ServerName");
} catch (Exception ex) {
//error occurred
} finally {
if (ctx != null) {
try {
ctx.close();
} catch (Exception dontCare) {

Cloud Control 12c identifies unused Weblogic version on Managed Server

I'm using Cloud Control to monitor our domain. In this case I upgraded from WebLogic 10.3.1 to Weblogic 12.1.2.0.0 by installing 12c on a separate Oracle/Middleware/Oracle_Home and updateing the startup script to use this new WL_Home location.
The Weblogic 10.3.1 installation is still there.
When I connect through Cloud Control to discover the Middleware Targets (WebLogic) it identifies my server as being 10.3.1
I checked the path and classpath in the startup script and there are no references to the 10.3 path. How is the cloud control agent finding the inactive one ?
any help is appreciated

For the error messagee:
Shell path is incorrect or not defined.:/usr/local/bin/bash(SH_PATH),-c(SH_ARGS) on host XXX. Check the property values in the following files in this order, ssPaths_<plat>.properties or sPaths.properties or Paths.properties, in "/oracle/em12c/oms/oui/prov/resources" directory.For more details, refer to the Oracle Enterprise Manager Basic Installation Guide.
yes , you are suppose to change the shell patch as its at a different location.
The file where you have to chnage is: $<OMS_HOME>/oui/prov/resources/hpi.properties and change the variable: SH_PATH=
Try the agent deployment
On your another question: deploy manual agent , you have to get the em12c agent binaries usings elf update console. For information on Self Update and how you can use it to download the software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/self_update.htm#CACBHCBH

Weblogic 8.1 managed server unable to contact Admin server

I have a strange issue here.
I have admin server on Linux Machine A
Managed server on Linux Machine B.
When i try to start managed server on Machine B, i get the following error.
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150001]An error occurred while connecting to the admin server to bootstrap through URL: http://MachineA:7100/wl_management_internal2/Bootstrap, user: system
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.readFully(ObjectInputStream.java:2571)
at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:1990)
The error suggests that managed server on machine B, is unable to contact Admin server on Machine A.
But i know for sure that Admin server is running on that port 7100 for sure.
It has been for the last 3 years.
To see if Machine B and Machine A have network issues, i did telnet.
From Machine B: i typed the following
telnet MachineA 7100
Connected to MachineA.
Escape character is '^]'
The above telnet command tells us that no network issues exist.
After a few tries, the managed server contacts to admin server and comes up.
This is not a one time thing.
I saw this behavior many times.
How should i resolve this?
Edited by: gvamsius on Feb 12, 2009 1:23 PM

Every thing is configured fine.
Nothing wrong with Configuration.
This domain has been running for the past 3 years.
Recently, i found something interesting in admin server logs, when i try to start the managed servers.
I realized there will be some amount of hand shake that happens during managed server startup, when it tries to communicate with admin server.
Here is the log snippet when managed server A contacts Admin server and starts up successfully.
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server A.>
####<Mar 10, 2009 12:11:42 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server A.>
####<Mar 10, 2009 12:11:46 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150031> <*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Here is the log snippet when managed server B contacts Admin server and does not start.
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action isrunning from managed server Managed Server B.>
####<Mar 10, 2009 12:07:07 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150030> <The bootstrap servlet has acknowledged that the admin server is running to the booting managed server Managed Server B.>
####<Mar 10, 2009 12:07:08 PM EDT> <Info> <Configuration Management> <Admin Host> <admin-server> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-150023> <Bootstrap servlet invoked with action bootstrap from managed server Managed Server B.>
The difference as you can see here is that managed server starts up only when Admin Server does the following
<*The bootstrap servlet has finished sending the configuration to Managed Server A*.>
Does any one knows why Admin server would not send the above bootstrap configuation all the times for the managed servers?

WebLogic 9.2 Managed Server Is not starting

I have WebLogic 9.2 Application Server installed on Solaris Box and have deployed some ear and war files.
If I try to start the managed server its getting the following exception leading to FORCE_SHUTDOWN of the server.
Please help me if any one know the solution for this.
The Exception is
<Jan 5, 2009 4:46:12 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Ve
rsion 1.5.0_10-b03 from Sun Microsystems Inc.>
java.io.IOException: Error while downloading files from admin server. Undelying error is : null
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:7
1)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandl
erManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doDownload(ConfigDataUpdate.java:75)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.downloadFiles(RuntimeAccessDeploymentR
eceiverService.java:892)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateFiles(RuntimeAccessDeploymentRec
eiverService.java:851)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleRegistrationResponse(RuntimeAcce
ssDeploymentReceiverService.java:706)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.registerHandler(RuntimeAccessDeploymen
tReceiverService.java:677)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.start(RuntimeAccessDeploymentReceiverS
ervice.java:169)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:67)
<Jan 5, 2009 4:46:19 AM CST> <Error> <Management> <BEA-141196> <The managed server could not update the configuration files du
ring the registration with the deployment service. The update failed due to an exception:
weblogic.management.DeploymentException: Exception occured while downloading files
at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doDownload(ConfigDataUpdate.java:83)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.downloadFiles(RuntimeAccessDeploymentR
eceiverService.java:892)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateFiles(RuntimeAccessDeploymentRec
eiverService.java:851)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleRegistrationResponse(RuntimeAcce
ssDeploymentReceiverService.java:706)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.registerHandler(RuntimeAccessDeploymen
tReceiverService.java:677)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.start(RuntimeAccessDeploymentReceiverS
ervice.java:169)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:374)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:67)
java.io.IOException: Error while downloading files from admin server. Undelying error is : null
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:7
1)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandl
erManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doDownload(ConfigDataUpdate.java:75)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.downloadFiles(RuntimeAccessDeploymentR
eceiverService.java:892)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateFiles(RuntimeAccessDeploymentRec
eiverService.java:851)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleRegistrationResponse(RuntimeAcce
ssDeploymentReceiverService.java:706)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.registerHandler(RuntimeAccessDeploymen
tReceiverService.java:677)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.start(RuntimeAccessDeploymentReceiverS
ervice.java:169)
Thanks
Shailesh
Edited by: user6488619 on Jan 5, 2009 6:48 PM

I'd say it's time to file a support case. Go to [https://support.bea.com] for this. You'll have to register if you haven't before. Note that this portal is going away at the end of this month.

Weblogic 6.1 managed server

Hello,
After installing weblogic 6.1, I tried running a managed server. However, it
gave me the following error message:
<2001/11/1 譯觼04渀05禳49秮> <Notice> <WebLogicServer>
<Starting WebLogic Managed Server "SimsOneServer" for domain "mydomain">
<2001/11/1 譯觼04渀05禳56秮> <Emergency> <WebLogicServer>
<ListenThread.run() failed: java.lang.UnsatisfiedLinkError: no weblogicunix1 in
java.library.path
java.lang.UnsatisfiedLinkError: no weblogicunix1 in java.library.path
at java.lang.ClassLoader.loadLibrary ClassLoader.java:1312)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
at weblogic.platform.Unix.<init>(Unix.java:14)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.platform.OperatingSystem.getOS(OperatingSystem.java:75)
at weblogic.t3.srvr.T3Srvr$2.run(T3Srvr.java:1004)
at weblogic.t3.srvr.Callback.done(Callback.java:37)
at weblogic.t3.srvr.ListenThread.newServerSocket(ListenThread.java:186)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:223)
>
I am using the supplied script of the default domain, "mydomain".
I have no problem running weblogic as administration server.
Thanks.

You need to have the directory where 'libweblogicunix1.so' resides in the LD_LIBRARY_PATH.
Depending on the platform you are using, LD_LIBRARY_PATH will be set by the
'startManagedWebLogic.sh' script in a case statement that figures out what platform you are
running on by using 'uname -s'. It then sets and exports LD_LIBRARY_PATH.
Look at your 'startManagedWebLogic.sh' script and make sure that this environment variable
is being set correctly and look in the directory that is being set to make sure that a copy
of 'libweblogicunix1.so' (.sl on HPUX) exists.
Bill Kemp
BEA Systems
Mark Liu wrote:
Hello,
After installing weblogic 6.1, I tried running a managed server. However, it
gave me the following error message:
<2001/11/1 譯觼04渀05禳49秮> <Notice> <WebLogicServer>
<Starting WebLogic Managed Server "SimsOneServer" for domain "mydomain">
<2001/11/1 譯觼04渀05禳56秮> <Emergency> <WebLogicServer>
<ListenThread.run() failed: java.lang.UnsatisfiedLinkError: no weblogicunix1 in
java.library.path
java.lang.UnsatisfiedLinkError: no weblogicunix1 in java.library.path
at java.lang.ClassLoader.loadLibrary ClassLoader.java:1312)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
at weblogic.platform.Unix.<init>(Unix.java:14)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at weblogic.platform.OperatingSystem.getOS(OperatingSystem.java:75)
at weblogic.t3.srvr.T3Srvr$2.run(T3Srvr.java:1004)
at weblogic.t3.srvr.Callback.done(Callback.java:37)
at weblogic.t3.srvr.ListenThread.newServerSocket(ListenThread.java:186)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:223)
>
I am using the supplied script of the default domain, "mydomain".
I have no problem running weblogic as administration server.
Thanks.

Remote Server Output of Weblogic 8.1 managed server.

Just have a quick question.
Where's the exact(default) location of the file that is showing on Server>Control>Remote Start Output>View Server Output.

Thanks,
I found the file under user_projects/domains/mydomain/NodeManagerClientLogs/mydomain_someserver folder. But they were organized with the date and time as the file name. Can I configure the system to point to a file with fixed name so that I can view it from a servlet, for example. One of the reasons is the file may grow to big and it will take a long time to load up from console and check it from there. Second question is if it is possible to redirect both stdout and stderr to a single file. I can do it from the command line when starting weblogic (> a.out 2>1&). But I don't know how to do the same in Remote managed server startup.

Weblogic 8.1 managed server shuttdown problem

Hi Friends,
When we log in to Admin console and selecting servers in the left pane and right clicking a server instance and selecting start/stop server, it shows
start this server
resume this server
graceful shutdown of this server
force shutdown of this server
The problem is graceful shutdown of this server and force shutdown of this server links are not highliting for a perticular managed server and they are highlighting all remaining servers.
that means we are unable to shutdown the server from console. we are doing from command line.
can please respond where the problem is?
thanks for advance friends.
weblogic-admin

Hi,
I have been watching responses on this issue (that I have encountered too). I use IE6.0 and this does not happen always. I have seen it happen twice where the Graceful Shutdown and Forced Shutdown links are not highlighted for one managed server whereas for others it is highlighted. The only option then to shutdown/restart this is via the CLI. Please note that other times, these links are high-lighted for the same managed server that did not have these options high-lighted.
So I would like to know when and why this would happen?
Thanks.
Jay

Weblogic Admin and Managed Server start using boot.properties and LDAP Acc.

Hello - Can any one please tell me if Weblogic 10.3.x can be started using boot.properties file and by using a user account from the External LDAP (OID) server?
I have configured the Weblogic server and have added a LDAP authenticator.
The Group in OID is mapped to the Admin role in Weblogic so that the user can start and stop the server.
LDAP users can successfully authenticate and access WLS console.
We would like to remove Default Authenticator (Embeded LDAP) from the list of available providers for our security releam.
Thank you.

Tested and got it worked.

Getting a perl error when trying to discover a Weblogic Managed Server

Hi,
Any help working this out would be greatly appreciated. I've searched Oracle Support and here without success so far.
I am trying to add a weblogic 10.3 manager server as a target for the agent on that host. Using Grid Control 10.2.0.5 patch 3 on both the OMS and the agent.
I get past the 2nd screen of the wizard then it fails. So far I've entered hostname, port, credentials for weblogic, then on the next page the credentials for the linux user on the host. Hitting next goes to a clock icon for a few seconds then it fails with:
Can't locate File/Find.pm in @INC (@INC contains: /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/5.8.3/i686-linux-thread-multi /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/5.8.3 /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl/5.8.3/i686-linux-thread-multi /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl/5.8.3 /ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl .) at /app/oracle/agent10g/sysman/admin/scripts/weblogicdiscovery.pl line 2. BEGIN failed--compilation aborted at /app/oracle/agent10g/sysman/admin/scripts/weblogicdiscovery.pl line 2.
I understand that when the agent runs the perl script weblogicdiscovery.pl, perl cant find the Find module to include (as instructed on line 2). The file in question exists in /app/oracle/agent10g/perl/lib/5.8.3/File/Find.pm .
I've tried tweaking the PERL5LIB env variable in the shell before I start the agent, and also in the emctl script itself, but neither seems to have any effect on that error message. It at least should have the basic $ORACLE_HOME/perl/lib in the path which is doesn't.
Anywhere else I should look for this variable setting?
Edit: Next question. I've been wondering where those "/ade/smayer_perl58_main_linux/..." paths were coming from as they aren't going to work and I see them (or at least very similar paths) defined in /app/oracle/agent10g/perl/lib/5.8.3/i686-linux-thread-multi/Config.pm . I've checked another linux host with the agent installed and it is the same, so must be defaults from Oracle. Was I supposed to change these after the install? I didn't read that anywhere. Still if we can set PERL5LIB before running emctl this should prepend real paths, right?
Quick test:
export PERL5LIB=$ORACLE_HOME/perl/lib:$ORACLE_HOME/perl/lib/site_perl
perl -e 'print join "\n", @INC'
/perl/lib/5.8.3
/app/oracle/agent10g/perl/lib/5.8.3/i686-linux-thread-multi
/app/oracle/agent10g/perl/lib/5.8.3
/app/oracle/agent10g/perl/lib
/app/oracle/agent10g/perl/lib/site_perl/5.8.3/i686-linux-thread-multi
/app/oracle/agent10g/perl/lib/site_perl/5.8.3
/app/oracle/agent10g/perl/lib/site_perl
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/5.8.3/i686-linux-thread-multi
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/5.8.3
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl/5.8.3/i686-linux-thread-multi
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl/5.8.3
/ade/smayer_perl58_main_linux/perl58/bin/Linux/Opt/lib/site_perl
Should $ORACLE_HOME/Perl be rebuilt during the agent install? I'm thinking it should because those details in the file point to someone with a username smayer configuring perl as per his environment.
Cheers,
Damian
Edited by: user11127564 on 29-Jun-2010 21:42
I've located something slightly useful on Metalink. Note ID 762125.1 particularly as we're using delegated privs and sudo.
However, this says this problem is fixed in 10.2.0.5. I'll prod my sysadmins some more on the sudoers configuration.
Edited by: user11127564 on 30-Jun-2010 16:55

Right. If you are using delegated privs and sudo, make sure that sudo is configured to pass on the PERL5LIB and ORACLE_HOME environment variables at least.

How to start managed server on Weblogic 9.1 Admin console with jRockit

I configured a new 9.1 domain with jRockit as the JVM. Under Server Start, I used -server -Xgcprio:pausetime -Xpausetarget=400ms -Xms:256m -Xmx:384m -Xns:81m -Xgcpause in the Argument field. When I tried to start the server, I am getting the following error:
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Starting WebLogic server with command line: C:\bea\jrockit90_150_04\bin\java -Dweblogic.Name=jdevext -Dbea.home=C:\bea -Djava.security.policy=c:\bea\weblogic91\server\lib\weblogic.policy -Dweblogic.management.server=http://144.111.155.145:7001 -Djava.library.path=C:\bea\WEBLOG~1\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\bea\WEBLOG~1\server\native\win\32;C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\bea\WEBLOG~1\server\native\win\32\oci920_8;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Support Tools\;C:\Program Files\Intel\Wireless\Bin\;C:\Program Files\ThinkPad\ConnectUtilities;C:\Program Files\QuickTime\QTSystem\ -Djava.class.path=C:\bea\weblogic91\server\lib\weblogic.jar;C:\bea\jrockit90_150_04\lib\tools.jar;c:\bea\weblogic91\server\lib\wamapps\commons-logging.jar;c:\bea\weblogic91\server\lib\wamapps\log4j.jar;c:\bea\weblogic91\server\lib\wamapps\xalan.jar;c:\bea\weblogic91\server\lib\wamapps\xercesImpl.jar;c:\bea\weblogic91\server\lib\wamapps\xml-apis.jar -Dweblogic.system.BootIdentityFile=C:\bea\user_projects\domains\jdev\servers\jdevext\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false java -server -Xgcprio:pausetime -Xpausetarget=400ms -Xms:256m -Xmx:384m -Xns:81m -Xgcpause -verbose weblogic.Server >
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Working directory is "C:\bea\user_projects\domains\jdev">
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Server output log file is "C:\bea\user_projects\domains\jdev\servers\jdevext\logs\jdevext.out">
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-jrockit     to select the "jrockit" VM
-client     to select the "client" VM
-server     to select the "server" VM [synonym for the "jrockit" VM]
The default VM is jrockit.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
<May 24, 2006 11:16:57 AM> <Info> <NodeManager> <Server failed during startup so will not be restarted>

It looks like your command line is broken. You have:
java <lots of -Dprop=value> java <JRockit flags> weblogic.Server
That second "java" shouldn't be there.
-- Henrik

SCCM 2012 Installation Directory Registry Key chaning automatically to Old Installation Path

Hi Guys,
I have recently recovered SCCM 2012 SP1 CAS Site from Primary Site by reinstalling CAS site and database was replicating with Primary sites properly after CAS recovery. But we noticed that after approx. 2 hours of CAS site recovery database replication stopped.
After long digging into SCCM log files we found that SCCM installation directory was pointing to old CAS Site Installation Directory (Which was before recovery) instead of NEW Installation Directory so we changed SCCM CAS Site Installation Directory manually
to new installation path in below registry key and everything was running fine again on CAS Site.
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Identification
But again when we restarted SMS_EXEUTIVE Service, SCCM Installation Directory again changed to old installation patch under above registry location and all is bad again. We are unable to figure out what is causing this and even we formatted our HDD before
installation CAS Site.
Can anyone please help to get rid of this issue. Our while CAS site is down due to this issue.
Thanks.

I think that you have to use the same installation directory in a site recovery scenario.
Torsten Meringer | http://www.mssccmfaq.de

Cannot start WebLogic Managed Server

Hi,
I have an weblogic domain on a physical machine with two servers (AdminServer and osb_server1 [Managed Server]). (Weblogic 10.3.6)
I started nodeManager and enrolled the domain using nmEnroll command through WLST.
I can start "AdminServer" thourgh nmStart('AdminServer') command. AdminServer starts successfully.
However, when I want to start managed server (osb_server1):
1. Through WebLogic administrator console it says:
(Warning) The user is not authorized to perform lifecycle operations on server osb_server1.
(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.
2. Using startManagedWebLogic.cmd script after entering username/password, it returns authentication denied.
Oct 22, 2012 10:31:21 AM EEST> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied>
<Oct 22, 2012 10:31:21 AM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
3. Using nmStart command on nodeManager, it is complaining about boot.properties file.
I can login AdminServer with same account without problems.
Best Regards,
Edited by: ToRRaDo on Oct 22, 2012 5:25 PM

Copied boot.properties from AdminServer to osb_server1 and the error below occured. (I also with plain text passwords in boot.properties file but error did not change)
<Oct 23, 2012 8:03:59 AM EEST> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user weblogic starting the managed server. The reason for the error is .>
<Oct 23, 2012 8:03:59 AM EEST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:7001/.>
<Oct 23, 2012 8:03:59 AM EEST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Oct 23, 2012 8:03:59 AM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Oct 23, 2012 8:03:59 AM EEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Oct 23, 2012 8:04:00 AM EEST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\my_domain\servers\osb_server1\logs\osb_server1.log is opened. All server side log events will be written to this file.>
<Oct 23, 2012 8:04:19 AM EEST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Oct 23, 2012 8:04:19 AM EEST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid;
The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
<Oct 23, 2012 8:04:20 AM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password fromthe boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created.
Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:960)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace>
<Oct 23, 2012 8:04:20 AM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
Edited by: ToRRaDo on Oct 23, 2012 8:13 AM
Edited by: ToRRaDo on Oct 23, 2012 8:14 AM

How to setup WebLogic Admin Server and Managed Server

Hi,
I working to setup a Weblogic admin and managed server but fail.
May i know the correct steps to setup the system ?
Tx.

TX. I will proceed to upload more logs here later.
Anyway I notice that after i follow the guide to setup the admin and managed server, I only able to access the web apps on admin server. I can not access web apps for managed server.
I setup the admin server using port 7001 and managed server using port 7003 based on oracle guide.
I found weird here. when I browse to http://adminserver:7001/apps, it works. But when i browse to http://managedserver:7003/apps it does not work.
But funny thing is when i browse to http://adminserver:7003/apps, it works.
I confuse that which configuration I have done is incorrect and have this result???
besides that I notice that in the nodemanager setting...the listening address is set to localhost and it works. If i configure it to IP address, it will give me errors.
Edited by: Wilson78 on Dec 22, 2008 12:29 PM

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

Weblogic Installation gets managed server of old installation

Similar Messages

Maybe you are looking for