OSB: problem when starting a managed server in an OSB cluster

Hi,
I used the configuration wizard to setup a very simple domain, containing a cluster with a managed server. When I start the managed server from the console I get prompted for the boot user and password. I specify the values I defined during the installation (weblogic user and custom passwort). After some time the managed server exists with the following exception:
####<21.04.2010 19.25 Uhr CEST> <Critical> <WebLogicServer> <DEMUC10525> <ManagedServer1> <main> <<WLS Kernel>> <> <> <1271870735741> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
 at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
 at weblogic.security.SecurityService.start(SecurityService.java:141)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
What is its problem and how do I fix it? I have not configured anything special in the domain - just the cluster, a single machine and the managed server and admin server targeted at this machine.
The admin server starts without these problems. I also tried copying the boot.properties from the admin server to the managed server without any success - the same problem.
Regards
Dimo
Edited by: dimo velev on 21.04.2010 11:24

Hi Anuj,
it turned out to be an OSB related problem - WLS forum would not have been able to help.
The startManagedWebLogic script should be run only within an environment which has been correctly setup using the domain setDomainEnv script. This seems to add some classpaths and stuff like this which, if missing, produces the exception - it actually has absolutely nothing to do with the user and password being wrong.
If you are using a node manager to start the managed servers then it should also be run within an evironment correctly setup with the domain's setDomainEnv script.
Best regards
Dimo

Similar Messages

Problems while starting the Managed Server through Node Manager..

When I was trying to start a Managed Server using the Nodemanager , I am getting the following error :
NodeManager not configured to receive commands from host : emis-develop
I have the "nodemanager.hosts" file under the directory "c:\bea\wlserver6.1\config" and even while invoking the script for the startnodemanager , I am indicating this in the script ! Any ideas for this problem ??

The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.> You may configure custom Identity and Trust in weblogic. It is not recommended to use Demo Trsut and Demo Identity for environments higher to Dev. -
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13707/identity_trust.htm#i1202182
Regards,
Anuj

Problem in starting OIM managed server

Hello,
After configuring the Managed server in a cluster, when we try to start the server it is starting in ADMIN mode.
The SOA Managed server was started successfully.
23:41:38 INFO [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] - Nexaweb Server initialized successfully.
<Sep 20, 2011 11:41:40 PM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Sep 20, 2011 11:41:40 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Sep 20, 2011 11:41:40 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of oim_cluster.>
<Sep 20, 2011 11:42:10 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.10.243:7003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 20, 2011 11:42:10 PM IST> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "WLS_OIM1" for domain "IDM_Domain" running in Development Mode>
<Sep 20, 2011 11:42:13 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Sep 20, 2011 11:42:13 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
Please let us know how to make the server run in RUNNING mode.
Thanks.

Have you done any changes in Weblogic Admin Console ?
Login into Weblogic Console and see what it shows for "Undo All Changes" and "Activate Changes" button.
If "Activate Changes" in enabled then click on that and try to restart.

Error message seen when starting a managed server (dsp_config.ear)

Hi ,
I am having issues when i start the managed server under the admin server.
Seems like when i undeploy dsp_config.ear the managed server seems to start without any issues.
But since the dsp_config.ear is removed the dspconsole is messed up.
The admin server runs fine without any issues with or without dsp_config.ear deployment.
The error trace
####<Jul 27, 2009 9:36:01 AM EDT> <Warning> <DeploymentService> <wdcsn383a> <cashflow1MS1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (
self-tuning)'> <<WLS Kernel>> <> <> <1248701761543> <BEA-290064> <Deployment service servlet encountered an Exception while handling the deployment service m
essage for request id "-1" from server "BEAAdminServer". Exception is: "java.lang.ClassNotFoundException: com.bea.wli.config.deployment.server.ServerVersion:
This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed o
n a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:218)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:85)
at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:61)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at java.util.HashMap.readObject(HashMap.java:1030)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.deploy.service.internal.DomainVersion.readExternal(DomainVersion.java:180)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readMessage(DeploymentServiceMessage.java:325)
at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readExternal(DeploymentServiceMessage.java:301)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.handleDeploymentServiceMessage(DeploymentServiceServlet.java:618)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.internalDoPost(DeploymentServiceServlet.java:235)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.access$000(DeploymentServiceServlet.java:77)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet$1.run(DeploymentServiceServlet.java:210)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.doPost(DeploymentServiceServlet.java:207)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
Can anybody help me on this one?
it seems more of ODSI issue than weblogic server issue.

it sounds like you are deploying dsp_config.ear to a domain/server that is not ODSI-enabled.
com.bea.wli.config.deployment.server.ServerVersion is in <modules>/com.bea.common.configfwk.wlinterop_10.3.0.0.jar which is referenced by <modules>/features/odsi.server.modules_10.3.0.0.xml and used by com.bea.dsp.management.impl.DomainServiceImpl

Memleak cannot work when start the management server by ctrlhandler.act

Hi, all
I use ctrlhandler.act to start a management server on running system. when start the memleak detector, i got the error message on server output:
[JRockit] ManagementServer started trend analysis
java.lang.NullPointerException
Continuing ...
java.lang.Exception: discarding statement XMLEncoder0.writeObject(HeapHistogram0);
Continuing ...
but when I started the management server with command line -Xmanagement. all is ok. What's the matter?
Thanks a lot!

Sorry, the jrocki version is 1.4.2_05 and 1.4.2_08.
And the os: windows XP professional and Redhat AD 7.2
And the weblogic server version is 'weblogic8.1 sp3'
any suggestion? Thank you!

Facing Problem in Starting Weblogic Managed Server

Hi,
While starting a managed server through Weblogic Console it is giving "nodemanager is not running" related error. I am not sure what is happening here. It was working fine earlier.
Thanks
Pawan

Hi,
Please check wheather node manager is running inside the server. Please check the nodemanager listen port in nodemanager.properties file and issue below command from your server.
netstat -a |grep "port"
Regards,
Kishore

Problem while starting the managed server

Hi
We have following configuration :-
We have 2 physical sesrvers :-
Server1 and Server2 in Sun Cluster running Solaris 10.
We also have Oracle DB server 9.2.0.8 in RAC mode, one instance each on Server1 & Server2.
Server 1 :-
cluster1 :- 1 Managed Server running
Server 2 :-
cluster2 :- 1 Managed Server running
we are getting following error in admin server log :-
<Error> <NodeManager> <BEA-300034> <Could not execute command "kill" for server "cluster1" using the node manager. Reason: Connection refused. Couldn't connect to NodeManager. Check that it is running at localhost:5556.>
Recently we have enabled the Connection Filter.
also getting following info in logs :-
<Notice> <Socket> <BEA-000445> <Connection rejected, filter blocked Socket[addr=192.193.164.8,port=53666,localport=8001], weblogic.security.net.FilterException: [Security:090220]rule 16>
<Notice> <Socket> <BEA-000445> <Connection rejected, filter blocked Socket[addr=163.37.174.126,port=58284,localport=8002], weblogic.security.net.FilterException: [Security:090220]rule 17>
Is it because of any misconfiguration in Connection filter ?
Or filter is not allowing the request for ipaddress and port of Managed Server in cluster1
Thanks in advance .. :)

Thanks for the information.
Node Manager is not used.
I found problem in Connection filter.
169.187.186.76 - address ManagedServer1
169.187.186.77- address Managed server2
169.187.186.51 :- Admin Server (8001 is http and 8002 is https)
Tunneling is enable for Managed Server
Please help me understanding below things is there any ambiguity in this rules :-
In the script to stop Managed server we are using t3 protocol like : t3://ip:port but its not allowing t3 protocol .whereas t3 protocol is no where denied in rules.
If I use https to issue request still not working
<connection-filter>weblogic.security.net.ConnectionFilterImpl</connection-filter>
<connection-filter-rule>127.0.0.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.0.129 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.1.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.59 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.51 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.76 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>192.168.10.4 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.4.1 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.77 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>169.187.186.60 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.0.130 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.1.2 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>192.168.10.5 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>172.16.4.2 169.187.186.51 8001 allow</connection-filter-rule>
<connection-filter-rule>ocs1.in.citicorp.com 169.187.186.51 8002 allow https</connection-filter-rule>
<connection-filter-rule>* 169.187.186.51 8001 deny</connection-filter-rule>
<connection-filter-rule>* 169.187.186.51 8002 deny</connection-filter-rule>
Thanks in Advance .......

HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

hi all, i am trying to start a managed server using nodeManager, but i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for
server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
to negotiate an acceptable set of security parameters.. Please ensure that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try to start
the managed server via adminserver console, i got the exception mentioned in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver, and
nodemanager is supposed to run at localhost:5555 (and indeed it does, because
ihave started it successfully).
thanx in advance and regards marco

Marco.
Sorry, this is not a solution to your problem but i am trying to solve the same
problem for a week now.
I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
same error. I know that the default certificate installed provides a hostname
verification of weblogic.com. I turned the hostname verification off, i put in
the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
error when starting the managed server. I went ahead and created my own certificate
for machine called mallik, created my own passphrase, created a new keystore,
made the admin server view the keystore, used the same certificate for both the
admin server and the node manager. It still fails with the same error. I went
ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
totally confused now what needs to be done.
My nodeManger.hosts looks like this:
mallik 10.100.10.130
managedServer1 10.100.10.130
managedServer2 10.100.10.13
Below is the startNodeManager.cmd.
@echo off
@rem *************************************************************************
@rem This script can be used to start the WebLogic NodeManager
@rem
@rem This script sets the following variables before starting the NodeManager:
@rem
@rem WL_HOME - The root directory of your WebLogic installation.
@rem NODEMGR_HOME - The home directory for this NodeManager instance.
@rem JAVA_HOME - Location of the version of Java used to start WebLogic
@rem Server. This variable must point to the root directory of
@rem a JDK installation and will be set for you by the
@rem installer. See the WebLogic platform support page
@rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
list of
@rem supported JVMs on Windows NT.
@rem PATH - Adds the JDK and WebLogic directories to the system path.
@rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
@rem JAVA_OPTIONS - Java command-line options for running the server. (These
@rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
@rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
@rem -client, etc.)
@rem MEM_ARGS - The variable to override the standard memory arguments
@rem passed to java
@rem
@rem *************************************************************************
SETLOCAL
set WL_HOME=C:\bea7.0\weblogic700
set NODEMGR_HOME=%WL_HOME%\common\nodemanager
set JAVA_HOME=C:\bea7.0\jdk131_06
Call %WL_HOME%\common\bin\commEnv.cmd
@rem If NODEMGR_HOME does not exist, create it
:checkNodeManagerHome
if exist %NODEMGR_HOME% goto checkJava
echo.
echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
mkdir %NODEMGR_HOME%
@rem Check that java is where we expect it to be
:checkJava
if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
echo The JDK wasn't found in directory %JAVA_HOME%.
echo Please edit this script so that the JAVA_HOME
echo variable points to the location of your JDK.
goto finish
:runNodeManager
if not "%JAVA_VM%" == "" goto noResetJavaVM
rem set JAVA_VM=-hotspot
set JAVA_VM=%COMM_VM%
:noResetJavaVM
if not "%MEM_ARGS%" == "" goto noResetMemArgs
set MEM_ARGS=-Xms32m -Xmx200m
:noResetMemArgs
@echo on
set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
cd %NODEMGR_HOME%
#"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
"-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
"-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
"-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
"-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
goto finish
:finish
ENDLOCAL
I would appreciate if anybody can help me.
Mallik.
"Marco" <[email protected]> wrote:
>
hi all, i am trying to start a managed server using nodeManager, but
i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for
server managedServer via the Node Manager - reason: [CommandInvoker:
Failed to
send command: 'online to server 'managedServer' to NodeManager at host:
'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
was unable
to negotiate an acceptable set of security parameters.. Please ensure
that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
-Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost
and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try
to start
the managed server via adminserver console, i got the exception mentioned
in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver,
and
nodemanager is supposed to run at localhost:5555 (and indeed it does,
because
ihave started it successfully).
thanx in advance and regards marco

Path problem when use node manager to start Managed Server

Hi, I have met a problem:
My managed server's root directory is /usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is /usr/local/bea/cluster1/weblogic700/common/nodemanager
I have some config file located under managed server's root directory and log
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server, I found
weblogic can not find the config file if I don't move the config file from Managed
server's root directory to node manager server's default directory. and also log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to node manager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?

Hi Lumin,
If the weblogic version is 8.1, there is a RootDirectory field in Remote
Start tab which should resolve your problem. Just enter the absolute
directory pathname on the machine where you are starting your managed server
and the current working directory of the managed server will be this
RootDirectory. Before 8.1, the RootDirectory was used for finding the config
file for weblogic but it was never used to change the working directory of
the managed server created by the node manager.
cheers,
gaurav.
"lumin" <[email protected]> wrote in message
news:3eb7a4ae$[email protected]..
>
Hi, I have met a problem:
My managed server's root directory is/usr/local/bea/cluster1/usr_projects/mydomain
My Node Manager 's default directory is/usr/local/bea/cluster1/weblogic700/common/nodemanager
>
I have some config file located under managed server's root directory andlog
file is also should be generated in managed server's root directory.
But when I try to use node manager to startup/shutdown the Managed Server,I found
weblogic can not find the config file if I don't move the config file fromManaged
server's root directory to node manager server's default directory. andalso log
file was created under node manager's default directory.
It seems that managed server's default directory has been changed to nodemanager's
default directory.
What shall I do if I want Managed Server's default directory to be kept?

Multicast Exception when starting a managed weblogic server.

I receive a Multicast Exception when i try to start a managed weblogic server from the same machine on which my admin server is running.
 when i try to start a managed server from another machine then it does not allow me to do so.
 please help,
 Manish.


see Sanjeev Chopra's response on 10/25/00 , subject named "
weblogic.admin.host -- missing
property"...
Kumar
John Kelvie wrote:
I am having the same problem...any suggestions?
"Srividhya" <[email protected]> wrote in message
news:3a107849$[email protected]..
Hi All,
While starting the weblogic managed server, i get the following error:
Starting WebLogic Server ....
<Mon Nov 13 17:50:12 EST 2000> <Warning> <Management> <Unrecognizedproperty: ad
min.host>
<Mon Nov 13 17:50:15 EST 2000> <Error> <Configuration Management> <Errorconnect
ing to admin server and initializing admin home: admin URL:t3://kerala:7001
javax.naming.ServiceUnavailableException. Root exception isjava.rmi.NoSuchObje
ctException: The object identified by [3] could not because found. Eitherit was
has not been exported or it has been collected by the distributed garbagecolle
ctor.
atweblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:3
78)
atweblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLIniti
alContextFactoryDelegate.java:306)
atweblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:261)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:230)
at weblogic.jndi.Environment.getContext(Environment.java:129)
atweblogic.jndi.Environment.getInitialContext(Environment.java:112)
atweblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
at weblogic.management.Admin.start(Admin.java:295)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
On the admin server, it does not give any error.
What could be the reason?
Regards,
Srividhya

Starting a managed server session and keeping the session when you exit

I created a managed server named "xxx_mgd" with the create managed server wizard in the admin console
when I start the managed server it produces a prompt for the username and password, whcih is the same username
and password entered when i was created. The issue I have is that when I exit the session, the process dies.
In comparison to the starting of the admin server, which is started with custom scripts which calls the standard wl startup scripts and it runs in background using nohup....
Is there away to start my managed server the same way, so that it stays running when you exit. I have tried running it as the admin server, using an option where the password if fed, but it dies and never startup
If you have any clue let me know
Joseph

Assuming that you are running WebLogic version 9.x and above.
Copy the "security" folder inside DOMAIN_HOME/servers/AdminServer directory to DOMAIN_HOME/servers/ManagedServer directory.
This security folder will have boot.properties file which contains encrypted username and password which is used when starting the server.
You can run Admin Server in background using nohup command as below from DOMAIN_DIRECTORY. This command will redirect stdout to AdminServer.out file.
nohup ./startWebLogic>>AdminServer.out &
You can run Managed Server in background using nohup command as below from DOMAIN_DIRECTORY/bin folder. This command will redirect stdout to ManagedServer.out file.
nohup ./startManagedWebLogic.sh <Managed Server Name> t3://<AdminServerListenAddress>:<PortNo> >>ManagedServer.out &
Hope this helps.
- Tarun
Edited by: Tarun Boyella on Feb 3, 2011 2:09 PM

Error when starting Netscape Calendar Server: Module: , Label: 355, Service error: #0x13209

When starting Netscape Calendar Server, the following error message appears:
 
Module: , Label: 355, Service error: #0x13209

The three ACIs listed below need to be present in the Directory Server in order
for Calendar server to work properly. Check the properties on the Base DN to
verify that the following ACIs exist. If they are not present, you will need
to add them, and the Base DN will need to be modified for your enviroment.

<OL>
<LI>ACI for allowing users to modify their own entries. 

(targetattr = "*")(version 3.0; acl "Allow self entry modification";
allow (write)userdn = "ldap:///self";) 

<LI>ACI for allowing anyone permissions to Read, Search, and Compare. 

(target="ldap:///o=basedn.com") (targetattr != "userPassword") (version
3.0; acl "Anonymous access";
allow (read, search, compare) userdn = "ldap:///anyone";) 

<LI>ACI for allowing Calendar Server admins Write access to the Base DN
(this is necessary in order for admins to add users and resources to the node).
 
(target="ldap:///o=basedn.com") (targetattr = "*") (version 3.0; acl
"Calendar Administrators Group"; 
allow(all) groupdn = "ldap:///cn=Calendar Server Admins,ou=Netscape
Servers,o=basedn.com";) 
</OL>

Hi Trinidad,
Thanks for your help!!!
1.
I didn't install EventSender and DIProxy yet, I tried first to upload and deploy the zip files, but I couldn't open the Itegration Application Explorer.
2.
The jvm.dll file is in in the folder pointed by the logs: C:\Program Files (x86)\SAP\SAP Business One Integration\jdk1.5.0_xx_sap\jre\bin\server
and it is also in C:\Program Files (x86)\SAP\SAP Business One Integration\jdk1.5.0_xx_sap_64\jre\bin\server
I tried running the file java5w.exe, but I got an error message:
Access is denied
Unable to open the service tomcat5
Thne I managed to open it by "rua as administrator".
the Java Virtual Machine path is points to the java 1.5 version folder.
Is it possible that the reason that the service can't start is related to administrator rigts??
In the properties in the Integration Service (services.msc):
It is set to be run with the local system account.
all other properties looks fine.
in the properties of the tomcat5.exe (and tomcat5w.exe , I tried both)
In the Compatibility tab I tried setting the flag "Run this program in compatibility mode for" to Vista, windows 7, and server 2008
I didn't have the option of Windows XP.
I have also set the Privilege level of: "Run this program as administrator" to true.
But still the service won't start.
What can be the problem?
What else can I check?
Thanks a lot,
Chana

Http 401 error starting a managed server

Hi,
I'm new to wl and am setting up a managed server on wl6.0.
I read and followed the instructions in the admin guide - really!
I have an admin server running under the petstore domain,
on port 7001 and am trying to run a managed server under
"devdomain".
Below is the java command my startup script is using
to start the managed server. It is failing with a security
error (http 401). I don't see anything in the dox about an
additional userid/password control at the http level.
When I browse directly to http://webdev:7001/Bootstrap,
I get http password pop-up. The system userid and password
does not work.
What dox can I go to for help on this?
Thx
Jim Brockman
java -ms64m -mx64m -classpath
/opt/bea/wlserver6.0:/opt/bea/wlserver6.0/lib/weblogic_sp.jar:/opt/bea/wlser
ver6.0/lib/weblogic.jar:/opt/bea:/opt/bea/wlserver6.0/lib/jdbctype4drivers/c
lasses12.zip -Dweblogic.Domain=devdomain -Dweblogic.Name=devserver -Dweblogi
c.management.server=webdev:7001 -Djava.security.policy=/opt/bea/wlserver6.0/
lib/weblogic.policy -Dweblogic.management.username=system -Dweblogic.managem
ent.password=xxxxxxxx weblogic.Server
Starting WebLogic Server ....
Connecting to http://webdev:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException:
connecting to http://webdev:7001/Bootstrap/ - with nested exception:
[weblogic.net.http.HttpUnauthorizedException: 401]
weblogic.net.http.HttpUnauthorizedException: 401
at
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:32
8)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:825)
at weblogic.management.Admin.initialize(Admin.java:274)

I solved the problem in this command.....
/opt/bea/wlserver6.0:/opt/bea/wlserver6.0/lib/weblogic_sp.jar:/opt/bea/wlser
ver6.0/lib/weblogic.jar:/opt/bea:/opt/bea/wlserver6.0/lib/jdbctype4drivers/c
lasses12.zip -Dweblogic.Domain=devdomain -Dweblogic.Name=devserver -Dweblogi
c.management.server=webdev:7001 -Djava.security.policy=/opt/bea/wlserver6.0/
lib/weblogic.policy -Dweblogic.management.username=system -Dweblogic.managem
ent.password=xxxxxxxx weblogic.Server
When I put the password in the script, the problem is disapeared...
Jim Brockman wrote:
Hi,
I'm new to wl and am setting up a managed server on wl6.0.
I read and followed the instructions in the admin guide - really!
I have an admin server running under the petstore domain,
on port 7001 and am trying to run a managed server under
"devdomain".
Below is the java command my startup script is using
to start the managed server. It is failing with a security
error (http 401). I don't see anything in the dox about an
additional userid/password control at the http level.
When I browse directly to http://webdev:7001/Bootstrap,
I get http password pop-up. The system userid and password
does not work.
What dox can I go to for help on this?
Thx
Jim Brockman
java -ms64m -mx64m -classpath
/opt/bea/wlserver6.0:/opt/bea/wlserver6.0/lib/weblogic_sp.jar:/opt/bea/wlser
ver6.0/lib/weblogic.jar:/opt/bea:/opt/bea/wlserver6.0/lib/jdbctype4drivers/c
lasses12.zip -Dweblogic.Domain=devdomain -Dweblogic.Name=devserver -Dweblogi
c.management.server=webdev:7001 -Djava.security.policy=/opt/bea/wlserver6.0/
lib/weblogic.policy -Dweblogic.management.username=system -Dweblogic.managem
ent.password=xxxxxxxx weblogic.Server
Starting WebLogic Server ....
Connecting to http://webdev:7001...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException:
connecting to http://webdev:7001/Bootstrap/ - with nested exception:
[weblogic.net.http.HttpUnauthorizedException: 401]
weblogic.net.http.HttpUnauthorizedException: 401
at
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:32
8)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
at
weblogic.management.Admin.getBootstrapLocalServer(Admin.java:825)
at weblogic.management.Admin.initialize(Admin.java:274)--
Doyoung Im
Bea Systems Korea
Sales Engineer/Pre Sales
H.P) 82-11-9727-8923
DID) 82-2 -7676-823
Fax) 82-2 -783-7102
mail)[email protected]

Starting a managed server as standalone

 greetings
 environment: weblogic 7.0 clustered on 2 sun boxes (1 box has admin server and
 a managed server, the other just managed server).
 we recently had hardware failure on on the box with the admin server and the managed
 server. I need to document how to get the lone managed server up and running w/o
 the adminserver/box available. I would like know if, in theory, I could start
 the managed server as standalone? That is, normally the managed server is started
 by using startManagedWebLogic.sh, could I use startWebLogic.sh and would it work?
 I dont have a real test environment to test it out or I would have done that (this
 config exists in production only). Any thoughts on this greatly appreciated. thanks
 in advance
 paul


"paul wetzel" <[email protected]> wrote in message
 news:[email protected]...
 >
 > greetings
 > environment: weblogic 7.0 clustered on 2 sun boxes (1 box has admin server
 and
 > a managed server, the other just managed server).
 > we recently had hardware failure on on the box with the admin server and
 the managed
 > server. I need to document how to get the lone managed server up and
 running w/o
 > the adminserver/box available. I would like know if, in theory, I could
 start
 > the managed server as standalone? That is, normally the managed server is
 started
 > by using startManagedWebLogic.sh, could I use startWebLogic.sh and would
 it work?
 Paul, look in the document titled "Creating and Configuring WebLogic Server
 Domains" (rev. September 2002), chapter 4, section "Starting a Managed
 Server when the Administration Server is not accessible".
 I think you are supposed to continue to use the startManagedWebLogic.sh
 script, even when the Administration Server (AS) is down. When the Managed
 Server (MS) fails to connect to the AS, it will fall-back on local copies of
 the configuration files. Now, the problem is how to keep the local
 configuration files on the MS in sync with the AS files. If you have MS1
 running from the same directory as the AS, then you should be fine. But with
 MS2 running on a different piece of hardware, you must either manually copy
 the relevant files, or you must (before disaster strikes) enable replication
 of the files.

AuditLogFileException while starting a managed server

Hi all,
I implemented custom JAAS authentication for WLS 7.0 server and console. There
are no issues with a standalone or single server in the domain. When testing an
AdminServer with a managed server, I could still start the Admin Server without
any problem after configuring the security realm. I got the following errors while
starting the managed server. I tested with both servers on the same machine.
Any help would be appreciated.
<Server failed during initialization. Exception:weblogic.security.service.AuditLogFileException:
Couldn't rename C:\bea7\user_projects\deletedomain\.\DefaultAuditRecorder.log
to C:\bea7\user_projects\deletedomain\.\DefaultAuditRecorder.log2598.old
weblogic.security.service.AuditLogFileException: Couldn't rename C:\bea7\user_pr
ojects\deletedomain\.\DefaultAuditRecorder.log to C:\bea7\user_projects\deletedo
main\.\DefaultAuditRecorder.log2598.old
at weblogic.security.service.AuditLogFile.<init>(AuditLogFile.java:98)
at weblogic.security.providers.audit.DefaultAuditProviderImpl.createLogF
ile(DefaultAuditProviderImpl.java:106)
at weblogic.security.providers.audit.DefaultAuditProviderImpl.initialize
(DefaultAuditProviderImpl.java:89)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1752)

Hi,
Please remember to mark the answers accordingly... Helpful or correct... You will be helping the forum community by doing that.
First thing to fix is the Admin_URL, there should be something like:
-Dweblogic.management.server=http://localhost:7001How are you starting this managed server? Node manager or command line? Try both options and see if they bring up the same error.
Cheers,
Vlad

OSB: problem when starting a managed server in an OSB cluster

Similar Messages

Maybe you are looking for