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.

Similar Messages

Error starting oim managed server

Hi,
I am getting the following error when trying to start oim managed server using the command
startmanagedweblogic.cmd oim_server1
<Jul 15, 2012 8:36:54 PM CDT> <Critical> <WebLogicServer> <BEA-000386> <Server s
ubsystem failed. Reason: weblogic.security.SecurityInitializationException: Auth
entication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblo
gic denied
but i am able to login into admin console with that user. Please help.

Hi ,
Try to clear your ldap folder with in your %Domain_Home%\ server \ <server name> \ data \ ldap
create a new boot.properties under %Domain_Home%\ server \ <server name> \ security folder.
Regards
shashank

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

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

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 .......

Starting OIM managed server

I had th weblogic managed server running with command:
xlStartmanagedServer.sh OIM_DOMAIN http://localhost:7001
This was working fine. Now, after restart, I issue the same command and I get an error:
$/bin/setDomainEnv.sh: No such file or directory.
In looking at the script xlStartManagedServer.sh, it seems $bea_domain$ is not set. The file its looking for is in the bea domain directory.
Not sure what happened.
Any idea anyone?
thx

Hi ,
Try to clear your ldap folder with in your %Domain_Home%\ server \ <server name> \ data \ ldap
create a new boot.properties under %Domain_Home%\ server \ <server name> \ security folder.
Regards
shashank

OIM Managed server is frequently reaching maximum data sources count

Hi All,
We are using OIM 11.1.1.3.0 , Weblogic Version 10.3.3,database 11.2.0.1 for one of our client bank . Recently we encountered a problem that my oim managed server is being overloaded ,when we check the error i see data sources reaching maximum count . We have increased the maximum count to 500 and still we are facing the same issue . We also find out dead-locks in the alert log . Now,i dont understand why data sources consumption is too high .
Please let us know your valuable inputs on the specific areas where we can check this .
Regards,
Nag.

Nag,
You don't need the developer to understand what code is causing the issue. You can analyse these issues using JRockit Mission Control, check these:
1-http://itnaf.org/2012/06/24/jrockit-flight-recorder-into-oim-environment/
2-http://itnaf.org/2012/08/26/jrockit-flight-recorder-analysis-into-oam-11g-environment/
I hope this helps,
Thiago Leoncio.

Error while starting the OIM managed server in oracle VM

Hi ,
I am getting the following error , while starting the OIM managed server in Oracle VM.
<Jun 14, 2012 4:45:38 AM EDT> <Error> <org.quartz.impl.jdbcjobstore.JobStoreCMT> <BEA-000000> <MisfireHandler: Error handling misfires: Unexpected runtime exception: null
org.quartz.JobPersistenceException: Unexpected runtime exception: null [See nested exception: java.lang.NullPointerException]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3042)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)
Caused By: java.lang.NullPointerException
at org.quartz.SimpleTrigger.computeNumTimesFiredBetween(SimpleTrigger.java:800)
at org.quartz.SimpleTrigger.updateAfterMisfire(SimpleTrigger.java:514)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doUpdateOfMisfiredTrigger(JobStoreSupport.java:944)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSupport.java:898)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3029)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)
>
How to resolve this issue.Any one please suggest me , i am in a big trouble ...
Thanks in advance ..
-Deena.

Hi P.k,
The table QRTZ92_TRIGGERS is there in the database.But while trying to run this command (UPDATE QRTZ92_TRIGGERS set NEXT_FIRE_TIME=1 where NEXT_FIRE_TIME < 0)in database i am getting the table or view does not exist.
What is GTC resource?
OIM version - 11.1.1.5.0.
-Deena.

Error while starting weblogic Managed Server

Hi ,
I am new to SOA 11g. I installled the latest version(11.1.1.4) of all the components.I started web logic and able to login into Admin Console but I have a problem
while starting Managed Server.It gives me an error saying
<Feb 2, 2011 2:01:29 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 17.0-b17
from Sun Microsystems Inc.>
<Feb 2, 2011 2:01:30 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: Unable to obtain lock on C:\Oracle\Middleware\user_projects\domains\fmw_domain\servers\AdminServer\tmp\AdminServer.lok.
Server may already be running
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)
at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
at weblogic.Server.main(Server.java:71)>
<Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Feb 2, 2011 2:01:30 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Can anyone help ?
Regards,
Vikas Manchanda
Edited by: 829347 on Feb 2, 2011 12:48 AM

How are you starting the managed server? Is it a new install? The error suggests that the managed server is already running. You could check the windows task manager to see if there is a Java process running (or two if managed and admin server is on the same machine)
Damien

Error while starting the managed server using nodemanager

HI ,
I am getting the below error while starting the managed server from the Admin console. All the serverstart and the node manager proeprties looks fine.
Below is the error in the managed server log,
startWebLogic.sh: grep: not found
startWebLogic.sh: uname: not found
startWebLogic.sh: test: argument expected
can you help me to solve the problem please. i am using weblogic 10.3.3
thanks
Arun

I think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?

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

Is there any way changing the priviledge after starting the managed server with the other user

Hi,
is there any way to change the user privilege after i have started the managed
server with one user.....say for example ....i have started one of my Managed
server as "root" ...but after that i wanted to make this instance work under as
"inet"
how do i do this OR is it possible ????
please advise ....
sangita

Thanks again Rob.
Rob Woollen <[email protected]> wrote:
>
>
sangita wrote:
Thanks Rob for been so quick in responding.
I have 3 questions for you:
Running a server under root is a huge security hole.My Question: 1) what are the probable security issues while runninga server under
root ?
are these security issues external(from outside world) or internal(internally
within a company) ?
Iam basically curious to know external threats.
The problem is the root user can do anything. So if someone finds a
security hole in your server, then they have complete control of your
system.
The usual reason people want to do this is so they can bind to a port
<
1024. ie they want their web server to listen to 80.My Question: 2) What is the harm in using port 80 for webserver andwhy do the
people wanted to bind to a port < 1024 ?
People normally use 80 for web servers because that's the well-known
port.
Personally I would not recommend that you go that route. I would
recommend that you start the server as a very unprivileged user andbind
it to some port (say 7001).
Most firewalls support redirecting ports. Your firewall can redirect
80
on the external net to 7001 on the internal net. That's the solution
I
would recommend.My Question: 3) Suppose iam having a cluster of 2 Managed servers runningon port
7070. And Iam having a Iplanet server working as a Webserver that basicallyproxies
requests to this cluster. Then what is the best approach that i shouldfollow
in this context.....to be honest with you ....i still couldnot understandwhat
does "binding" the webserver port to a managed server in weblogic mean.
I would have your firewall redirect 80 to whatever port Iplanet is
listening on and then have iplanet proxy to WLS.
Do not run your WLS servers as root.
-- Rob
Iam sorry for asking these "silly" questions(in your opinion) ...butiam a bit
confused.
thanks, sangita
Rob Woollen <[email protected]> wrote:
Running a server under root is a huge security hole.
The usual reason people want to do this is so they can bind to a port
<
1024. ie they want their web server to listen to 80.
There is a set uid option in WLS where you start the server as root
and
then after it binds to the low port, it will switch to another userthat
you specify.
Personally I would not recommend that you go that route. I would
recommend that you start the server as a very unprivileged user andbind
it to some port (say 7001).
Most firewalls support redirecting ports. Your firewall can redirect
80
on the external net to 7001 on the internal net. That's the solution
I
would recommend.
-- Rob
sangita wrote:
<Sure, it's possible to do this, >
how to do this?
<but why do you want to do it? >
Iam not sure why this group (the other group than me) does start theirserver
as "root"...but somebody from that group asked me about this today.
I would not recommend that you start WLS as root on your production
system ever under any cirucmstance.then what is the best approach and what are the pros and cons if westart the
server as "root" OR as different user ????
please advise ....
thanks again.
Rob Woollen <[email protected]> wrote:
Sure, it's possible to do this, but why do you want to do it?
I would not recommend that you start WLS as root on your production
system ever under any cirucmstance.
-- Rob
sangita wrote:
Hi,
is there any way to change the user privilege after i have startedthe managed
server with one user.....say for example ....i have started one
of
my Managed
server as "root" ...but after that i wanted to make this instance
work
under as
"inet"
how do i do this OR is it possible ????
please advise ....
sangita

Problem in starting OIM managed server

Similar Messages

Maybe you are looking for