Managing server process ports

Hello,
I have some questions about ports used by oracle server processes.
Supoose we have listener on 1521
1. Dedicated server: when client connects to the database the listener spawns new process which is also using 1521 (port sharing), right? And if there's another client connecting to the db, and listener spawns another server process, it's also using 1521?
2. Shared server process. We define 4 dispatchers for example.. Are they all using the same port? For example
dispatchers=(address=(protocol=TCP)(Host=myhost)(PORT=1561)(dispatchers=4)"
does it mean all 4 dispatchers are accessible on 1561 ports? What about shared server processes then? If we define shared_server=3 for example, on which port numbers are they listening?
Thanks in advance for help,
Aliq

Aliq,
You need to check whether you are using port redirection.
You can do that by running netstat -a, or by tracing sqlnet (on level 16)
The word 'redirect' will be in your trace file.
The best solution to use one port, is to install Oracle Connection Manager, using a custom install, and to set up all connections for Oracle Connection Manager. You now have
server client
session -------(random port) connection manager----fixed port session
You can misuse shared server for this purpose but you are risking to open extra ports as the number of sessions increases.
Used_shared_sockets will result in a disconnect of all sessions, when you stop the listener. Not a good idea
2
If you hardcode a portnumber for the first dispatcher (and using CMAN you don't need to anymore), subsequent dispatchers will just use the first free port. This may be in your case 1562, or 1566, or ... who knows?
Hth
Sybrand Bakker
Senior Oracle DBA

Similar Messages

  • Re: How to start Weblogic 10.3.5 managed server on port 80

    I can start managed server at port 80 but root permission make some deployments of managed server cannot cooperate with adminserver which is run by oracle user, in my case is oam_server1. Server is run but access server is down.

    I can start managed server at port 80 but root permission make some deployments of managed server cannot cooperate with adminserver which is run by oracle user, in my case is oam_server1. Server is run but access server is down.

  • How to start Weblogic 10.3.5 managed server on port 80

    Hello,
    We're trying to understand how to start Weblogic as root so we can start on port 80 on Linux. We understand that we'll use the post bind UID to run as a non-priv user. Right now in the Admin console under the managed server, Server Start properties (node manager) we have the weblogic user as the user to start the server, which works. Is this where we'd put the root user? We tried that but it fails complaining about root user didn't have permission to start the server. Can someone shed some light?
    Thanks

    Hi
    1. You are asking for 2 things here:
    a) Start Weblogic as root user ?
    Before I answer this question, who (Which User) installed Weblogic Software and who created Domain. I hope its NOT root user. Usually its not preferable to use root account for this. Instead create a new user account like for example oracle or some xyz. Then login with that account. Install Weblogic and create any Domain. I would NOT prefer/recommend using root account to install weblogic. This means, I would not recommend/support to start weblogic as root user. The thing is when you install weblogic, it stores/creates lots of files/scripts. Now when you start, it has to be same user. Because at the startup, we need to read files and also CREATE lots of temp files under domain root folder. So on unix, this becomes very complex. Simple answer is if you install weblogic and domain with user say "xyz" and try to start domain with "root", you corrupted your entire domain. Some files gets changed to root user and some files just FAIL saying you do not have permissions. So its just gone. If you are a Unix Geek, do some magic and restore all permissions back.
    b) Start Weblogic at Port 80
    Very Simple. Forget about above thing. Install Weblogic and create domain say with user "xyz". Just go to domain root folder, open config/config.xml file and edit the localport to 80. By default at time of domain creation if you used all the defaults like port 7001, then you will NOT see this entry in config.xml file. But still you can edit config.xml file manually. Stop the servers. Add a section with listen-port as 80. Just refer docs for the steps. After this change, your weblogic server is now running at port 80. NOW, the main precautions is make sure that you do NOT have any other stuff running at the same port 80. Otherwise, Weblogic server startup will fail saying port 80 is already is in use.
    Now if you want both a) and b), still it is possible. But I would NOT want/recommend a), which is use "root" account to install weblogic server and create and start the Domain. Nope, totally not recommending and supporting this. Yes, port 80 can be used, but not the "root" account.
    Thanks
    Ravi Jegga

  • Finding out a Managed Server Name/Port

    Hi all,
    Hope I have the relevant newsgroup....
    Does anyone know how I might be able to find out the name of the managed server (or its port) that I am currently running on?
    We have a clustered environment (1 admin, 2 managed servers) but I need to get the name of the managed server/port so I can generate some unique information for the server.
    I was reading about JMX and it seems I can return a list of ALL servers configured to run on a cluster. It doesn't really help though as I need to find out the specific server details within the cluster.
    Any help would really be appreciated.
    Cheers,
    Jay.

    Yes, you can use WLST tool :-
    domainConfig()
    cmo.getServers()
    Link : [http://edocs.bea.com/wls/docs100/config_scripting/monitoring.html]
    I hope this helps :)
    Edited by: Manish Chellappan on Jul 22, 2009 9:23 PM

  • Starting Managed Server on port below 1024

    I am trying to configure the Managed Server to listen on port 80. I have tried several configurations but haven't got the right picture yet.
    Let's see.
    My configuration is an Admin Server and a Managed Server.
    I configure a Machine and set the user ID and group ID to weblogic user; configures Node Manager to listen on "localhost:5555" and assigns the Managed Server to the Machine just created.
    From now on, which operating system user should start each piece of this configuration?
    - Is root starting Node Manager?
    - Is weblogic user starting Administration Server?
    - Is root starting Managed Server?
    - Is it automatic or need to be done manually (by script or command prompt)?
    any help whould be appreciated.
    Regards,
    Mariano

    You start the nodemanager as root, and (you typically would) configure the machine to have a post-bind uid/gid (see UnixMachine configuration) that the WLS managed server should assume for all other operations - That is, you need root priviliges only for listening on a well-known port and nothing else.
    It does not matter what other components run as.
    Venkat

  • How to know the port number to which the server process is listening

    I have created oracle 10g Release 1 database(orcl) in Windows Xp Professional edition through DBCA . I also created one more database(sample) manually .
    The ORCL server process listens to port no 1521 and
    SAMPLE server process listens to port no 1522
    Once I start the OracleServiceORCL (Service for orcl) from services.msc and check the listener status it displays
    Service "orcl" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    But when I start OracleServiceSAMPLE (Service for sample) from services.exe and check the listener status there is no change . Only when i start the instance the dynamic registration takes place with port no 1521 .
    There is no entry for listener parameter in init.ora file . My question is how is the service ORCL able to get itself registered with the listener even before the instance is up ?
    And how can i know which port no is linked with which server process?
    Also if we provide a different port number(other than 1521 say 1522) in tnsnames.ora for a service and consider the listener is listening to both 1521 and 1522 . Now consider that port number 1521 is free . In this case to which port number will the service be listening to ?
    The listener file looks like this
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\product\10.1.0\Db_2)
    (PROGRAM = extproc)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = irobo)(PORT = 1521))
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = irobo)(PORT = 1522))
    The tnsnames file has the following entry
    ORCL =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = irobo)(PORT = 1522))
    (CONNECT_DATA =
    (SERVICE_NAME = ORCL)
    SAMPLE =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = irobo)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = ORCL)
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    )

    Service "orcl" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...[coe]
    The status tells you the instance is up. Starting the service often means the instance gets started also, but whatever "often" means, "READY" means "The instance is up, running and taking callers".
    Your statement that "ORCL [is] able to get itself registered with the listener even before the instance is up" is therefore factually incorrect: you started the service, that started the instance. The instance is up and running. Instances that aren't running don't exist. Things which don't exist don't register themselves. Things which HAVE registered themselves therefore do exist.. and if they say they are "ready", it means they are completely, 100% up and running and behaving quite normally.
    I have not set LOCAL_LISTENER initialization parameter.How is this happening ?
    You only need to set LOCAL_LISTENER if (a) you're not using TCP/IP, (b) you're not using port 1521. Otherwise, PMON is hard-coded to register itself with listeners running on port 1521 and using TCP/IP and you don't need to set LOCAL_LISTENER to achieve that.
    Server Processes do not listen. Listeners do (there's a clue in their name). Listeners receive a call to connect to an instance, they spawn a server process to handle your call, and then they connect you to that server process (or send a message back to you telling you how to contact the server process). Each server process of course receives communications from its dedicated client on a specific port (usually in the 50000+ range), and that port is chosen randomly by the listener when it's spawning it. It's a bit blurry and vague to call that server process port a port on which server processes "listen", however.
    If you're talking dedicated server, each client causes one new server process to be spawned, and there is a one-to-one correspondence between server processes and the port that server process happens to accept client communications on.
    If you're going to ask a listener to do listening duty on multiple ports, I'd first question your need to do that and I'd then point out that unless your client tnsnames.ora knows to talk on the second or subsequent port numbers, the listener is never actually going to make use of that second port.
    In either case, the port the listener listens on has nothing whatsoever to do with the port your client-to-server-process communication ends up taking place on.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • How to find manager server port address

    hi
    i want to know managed server (soa_server1) port address in order to seed/remove community using demoCommunitySeedServlet. where to find out that one information
    regards
    ashok.v

    Go to your %ORACLE_MIDDLEWARE_HOME%/user_projects/domains/ or your domain folder, edit %ORACLE_MIDDLEWARE_HOME%/user_projects/domains/<your_domain_name>/config/config.xml. Inside this file check the ->
    <server>
    <name>soa_server1</name>
    <ssl>
    <name>soa_server1</name>
    <listen-port>8002</listen-port>
    </ssl>
    <machine>LocalMachine</machine>
    <listen-port>8001</listen-port>
    <listen-address></listen-address>
    <server-diagnostic-config>
    <name>soa_server1</name>
    <diagnostic-context-enabled>true</diagnostic-context-enabled>
    </server-diagnostic-config>
    </server>

  • Managed Server Monitoring tools for WLS 8.1 on linux

    Our organization uses a set of locally written shell scripts to monitor the status of the managed servers in a WLS 8.1 domain installed on RedHat Linux 4, update4.
    The main monitoring script uses the output of the "ps" and "netstat" commands to determine the process-id, server name, and tcp ports used by each managed server.
    It is able to determine the name of the managed server by parsing the value of the "-Dweblogic.Name" parameter from the command line of the java command that launches the jvm that represents the managed server.
    When a managed server is started, the command line resembles the following:
    java \
    -DLotsofVariables \
    -classpath LotsofCpElements \
    -Djava.security.policy==PolicyFile \
    -Dweblogic.Name=NameOfMgdServer
    The maximum number of characters displayed by the "ps" command with the wide (-w) option is 4096.
    A recent addition to the class path has increased the length of the command line, resulting in the "NameOfMgdServer" being truncated.
    It now appears similar to the following:
    java \
    -DLotsofVariables \
    -classpath LotsofCpElements \
    -Djava.security.policy==PolicyFile \
    -Dweblogic.Name=NameO
    This breaks our monitoring script because it is looking for a managed server named "NameOfMgdServer", not "NameO".
    Each managed server is monitored by the WLS administration server and the local node manager.
    Is there a way to restructure or rewrite the command line used to launch the managed server java jvm such that the "-Dweblogic.Name=NameOfMgdServer" appears before the specification of the classpath?
    I can find no mention of the "-Dweblogic.Name" parameter on the "Remote Start" tab corresponding to each managed server, so it appears that WLS is building the java command line internally based on the contents of the config.xml file, before launching the managed server process.
    I've considered adding an additional parameter to the java command line preceding the specification of the classpath, simply to identify the identity of the managed server, but I don't like this type of hack.
    Perhaps someone else has developed a similar monitoring tool, and could provide some advice?
    Any feedback is appreciated

    Our organization uses a set of locally written shell scripts to monitor the status of the managed servers in a WLS 8.1 domain installed on RedHat Linux 4, update4.
    The main monitoring script uses the output of the "ps" and "netstat" commands to determine the process-id, server name, and tcp ports used by each managed server.
    It is able to determine the name of the managed server by parsing the value of the "-Dweblogic.Name" parameter from the command line of the java command that launches the jvm that represents the managed server.
    When a managed server is started, the command line resembles the following:
    java \
    -DLotsofVariables \
    -classpath LotsofCpElements \
    -Djava.security.policy==PolicyFile \
    -Dweblogic.Name=NameOfMgdServer
    The maximum number of characters displayed by the "ps" command with the wide (-w) option is 4096.
    A recent addition to the class path has increased the length of the command line, resulting in the "NameOfMgdServer" being truncated.
    It now appears similar to the following:
    java \
    -DLotsofVariables \
    -classpath LotsofCpElements \
    -Djava.security.policy==PolicyFile \
    -Dweblogic.Name=NameO
    This breaks our monitoring script because it is looking for a managed server named "NameOfMgdServer", not "NameO".
    Each managed server is monitored by the WLS administration server and the local node manager.
    Is there a way to restructure or rewrite the command line used to launch the managed server java jvm such that the "-Dweblogic.Name=NameOfMgdServer" appears before the specification of the classpath?
    I can find no mention of the "-Dweblogic.Name" parameter on the "Remote Start" tab corresponding to each managed server, so it appears that WLS is building the java command line internally based on the contents of the config.xml file, before launching the managed server process.
    I've considered adding an additional parameter to the java command line preceding the specification of the classpath, simply to identify the identity of the managed server, but I don't like this type of hack.
    Perhaps someone else has developed a similar monitoring tool, and could provide some advice?
    Any feedback is appreciated

  • WebLogic 10.3.2  managed server startup failed : ''31' could not be found'

    Dears: I ran my managed server using script but failed , the weblogic version is 10.3.2 (11g R1) , on Solaris 10 sparc 64bit.:
    ports=( 7001 7003 7005 7007 )
    instances=( instance1 instance2 instance3 )
    adminip=192.168.11.174
    "startManagedWebLogic.sh ${instances[1]} http://$adminip:${ports[0]}"&
    Does anyone get jammed into this situation?
    The Managed Server instance2 is going to running
    JAVA Memory arguments: -Xms768m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=6 -XX:+DisableExplicitGC -XX:MaxPermSize=2048m
    WLS Start Mode=Production
    CLASSPATH=/wls11g/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/wls11g/jdk1.6.0_18/lib/tools.jar:/wls11g/utils/config/10.3/config-launch.jar:/wls11g/wlserver_10.3/server/lib/weblogic_sp.jar:/wls11g/wlserver_10.3/server/lib/weblogic.jar:/wls11g/modules/features/weblogic.server.modules_10.3.2.0.jar:/wls11g/wlserver_10.3/server/lib/webservices.jar:/wls11g/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/wls11g/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/wls11g/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/wls11g/wlserver_10.3/server/lib/xqrl.jar
    PATH=/wls11g/wlserver_10.3/server/bin:/wls11g/modules/org.apache.ant_1.7.0/bin:/wls11g/jdk1.6.0_18/jre/bin:/wls11g/jdk1.6.0_18/bin:/wls11g/user_projects/domains/base_domain:/wls11g/user_projects/domains/base_domain/bin:/wls11g/wlserver_10.3/server/bin:/wls11g/user_projects/domains/base_domain:/wls11g/user_projects/domains/base_domain/bin:/wls11g/wlserver_10.3/server/bin:/usr/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    -bash-3.00$ java version "1.6.0_18-ea"
    Java(TM) SE Runtime Environment (build 1.6.0_18-ea-b05)
    Java HotSpot(TM) 64-Bit Server VM (build 16.0-b12, mixed mode)
    Starting WLS with line:
    /wls11g/jdk1.6.0_18/bin/java -server -d64 -Xms768m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=6 -XX:+DisableExplicitGC -XX:MaxPermSize=2048m -Dweblogic.Name=instance2 -Djava.security.policy=/wls11g/wlserver_10.3/server/lib/weblogic.policy -da -Dplatform.home=/wls11g/wlserver_10.3 -Dwls.home=/wls11g/wlserver_10.3/server -Dweblogic.home=/wls11g/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=http://140.126.24.25:6001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/wls11g/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
    <Jan 20, 2010 6:02:46 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 16.0-b12 from Sun Microsystems Inc.>
    <Jan 20, 2010 6:02:49 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
    <Jan 20, 2010 6:03:00 PM CST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://140.126.24.25:6001.>
    <Jan 20, 2010 6:03:00 PM CST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Jan 20, 2010 6:03:00 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jan 20, 2010 6:03:00 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jan 20, 2010 6:03:01 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jan 20, 2010 6:03:01 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log00026. Log messages will continue to be logged in /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log.>
    <Jan 20, 2010 6:03:01 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log is opened. All server side log events will be written to this file.>
    <Jan 20, 2010 6:03:16 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jan 20, 2010 6:03:19 PM CST> <Error> <Configuration Management> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://140.126.24.25:6001 during startup. Since bootstrap succeeded check that t3://140.126.24.25:6001 uniquely identifies the administration server.
    javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:430)
    at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
    Truncated. see log file for complete stacktrace
    Caused By: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
    at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
    at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:429)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:426)
    Truncated. see log file for complete stacktrace
    >
    <Jan 20, 2010 6:03:19 PM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:430)
    at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
    at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:173)
    at weblogic.server.channels.RemoteChannelServiceImpl.registerForever(RemoteChannelServiceImpl.java:146)
    at weblogic.protocol.ConnectMonitorFactory.registerForever(ConnectMonitorFactory.java:88)
    at weblogic.management.provider.MSIService.registerForReconnectToAdminServer(MSIService.java:174)
    at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.start(CompatibilityMBeanServerService.java:154)
    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)
    Caused by: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
    at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
    at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:429)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:426)
    ... 9 more
    >
    <Jan 20, 2010 6:03:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jan 20, 2010 6:03:19 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jan 20, 2010 6:03:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    -bash-3.00$
    Edited by: user7322888 on 2010/2/4 下午 11:41

    Hi,
    Reproducing this issue is very easy.....
    1). Just Create a Admin and Managed Server
    2). Start AdminServer then from Admin Console Disable the normal listen-port for admin Server (suppose it was 7001 disable it)....AND enable only the SSL port for Admin Server (example 7002).
    Managed Server (Listen Port=7003 and SSL ListenPort=7004)
    3). Now Try Start Managed Server.
    you wil get the Exact same exception
    <Jan 20, 2010 6:03:19 PM CST> <Error> <Configuration Management> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://140.126.24.25:6001 during startup. Since bootstrap succeeded check that t3://140.126.24.25:6001 uniquely identifies the administration server.
    javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.]
    And
    <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://140.126.24.25:6001.>
    Now it will be easy for us to find out where is the issue actually.
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
    Edited by: Jay SenSharma on Feb 24, 2010 4:15 PM

  • Error starting managed server with JRockit VM

    I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
    option on. The OS is NT. Any clues , please ?
    exception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    D:\i252\services>runtxnserver
    JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
    Garbage Collector, started.
    [JRockit] Starting Management Server on port 7090
    Starting WebLogic Server ....
    Connecting to http://ocncat2:7991...
    <May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on fd:
    4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
    java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
    35c4a
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    >
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
    tected attempting to connect to admin server at http://ocncat2:7991 during i
    alization of managed server ( null:7551 ). The reported error was: < java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) > This condition generally results when the managed and
    n servers are using the same listen address and port.>
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize th
    rver: 'Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    '>
    The WebLogic Server did not start up properly.
    Exception raised: weblogic.management.configuration.ConfigurationException:
    .io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace

    I found the solution . The reason for this is that JRockit's High Performance Thread
    System uses asynchrounous I/O "under the hood". Weblogic's Native I/O is also asynchronous.
    The two asynchronous I/O systems clash and the result is the error you see.
    There are two ways around this problem. Either disable JRockit's High Performance
    Thread System (or thinthreads) by using the -Xnativethreads command line flag, or
    disable Weblogic's Native I/O.
    For Weblogic 6.0 and higher, edit the config.xml file. Find the line saying NativeIOEnabled="true"
    and change this to NativeIOEnabled="false".
    For Weblogic 5.1 you edit the file weblogic.properties and change the line weblogic.system.nativeIO.enable=true
    to
    weblogic.system.nativeIO.enable=false
    "Manoj jayadevan" <[email protected]> wrote:
    >
    I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
    option on. The OS is NT. Any clues , please ?
    exception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    D:\i252\services>runtxnserver
    JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
    Garbage Collector, started.
    [JRockit] Starting Management Server on port 7090
    Starting WebLogic Server ....
    Connecting to http://ocncat2:7991...
    <May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on
    fd:
    4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
    java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
    35c4a
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    >
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
    tected attempting to connect to admin server at http://ocncat2:7991 during
    i
    alization of managed server ( null:7551 ). The reported error was: < java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) > This condition generally results when the managed
    and
    n servers are using the same listen address and port.>
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize
    th
    rver: 'Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    '>
    The WebLogic Server did not start up properly.
    Exception raised: weblogic.management.configuration.ConfigurationException:
    .io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace

  • Adding patch jar file while starting Managed Server through Node Manager

    Hi,
    I am using Weblogic Express 10.0 on Linux env, Jrockit JVM.
    I have a patch jar file from BEA, I added it to Weblogic start script, when I start the Managed server by using startManagedWeblogic.sh script, I can see that patch jar file is added to classpath when I grep for Java process.(ps -ef | grep -i java).
    But when I start the Managed server through NodeManager and grep for java process, I dont see the patch jar file added to classpath of Managed server process which is started.
    Can someone let me know if I have to add the patch jar file somewhere else along with Weblogic start script if starting Managed server through Node Manager?
    Weblogic Consultant

    Thanks for your response.
    I found another way to do this.
    Edit nodemanager.properties file and set StartScriptEnabled=true (By default it is false), and then restart the Node Manager process.
    Enabling this setting to true will enable the NodeManager process to use startManagedWeblogic.sh script while starting the managed server, all the added jar files, memory settings will be taken from start script of Weblogic
    Weblogic Consultant

  • Start Managed Server from Another Machine

              Hello,
              In a two machines cluster starting a managed on the secondary machine not the
              one hosting the admin server, I keep getting the following error:
              Managed server log error:
              The WebLogic Server did not start up properly.
              Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
              not found for MBean orsus:Name=orsus,Type=Domain'
              Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
              not found for MBean orsus:Name=orsus,Type=Domain
              Admin Server log:
              <Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error
              occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain.
              Method: null. Exception: javax.management.AttributeNotFoundException: Attribute
              AdministrationMBeanAuditingEnabled
              not found for MBean orsus:Name=orsus,Type=Domain.
              javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
              not found for MBean orsus:Name=orsus,Type=Domain
              at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
              at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
              at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
              at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
              Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
              at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              <Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed
              Server orsusClusterNode_2 is disconnected from the admin server. This may be either
              due to a managed server getting temporarily partitioned or the managed server
              process exiting.>
              <Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest
              failed
              weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
              exception:
              [weblogic.rjvm.PeerGoneException: ; nested exception is:
                      weblogic.utils.net.SocketResetException].
              weblogic.rjvm.PeerGoneException: ; nested exception is:
              weblogic.utils.net.SocketResetException
              at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
              at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
              at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
              Source)
              at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
              at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
              at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              Caused by: weblogic.utils.net.SocketResetException
              at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
              ... 2 more
              --------------- nested within: ------------------
              weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
              exception:
              [weblogic.rjvm.PeerGoneException: ; nested exception is:
                      weblogic.utils.net.SocketResetException]
              at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
              Source)
              at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
              at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
              at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              Any ideas?
              Regards.
              Eran
              [wlerrlog.txt]
              

    Do both the machines have the same weblogic server installation? Looks
              like there is a conflict, the machine where the managed server is
              running has a weblogic server version lesser than the admin server.
              Check the versions on both machines.
              java weblogic.version
              should print the version information.
              Thanks,
              -satya
              eran wrote:
              >
              > Hello,
              >
              > In a two machines cluster starting a managed on the secondary machine not the
              > one hosting the admin server, I keep getting the following error:
              >
              > Managed server log error:
              > ***************************************************************************
              > The WebLogic Server did not start up properly.
              > Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
              > not found for MBean orsus:Name=orsus,Type=Domain'
              > Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
              > not found for MBean orsus:Name=orsus,Type=Domain
              >
              >
              > Admin Server log:
              > <Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error
              > occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain.
              > Method: null. Exception: javax.management.AttributeNotFoundException: Attribute
              > AdministrationMBeanAuditingEnabled
              > not found for MBean orsus:Name=orsus,Type=Domain.
              > javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
              > not found for MBean orsus:Name=orsus,Type=Domain
              > at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
              > at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
              > at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
              > at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
              > Source)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
              > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
              > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
              > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
              > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
              > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              > <Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed
              > Server orsusClusterNode_2 is disconnected from the admin server. This may be either
              > due to a managed server getting temporarily partitioned or the managed server
              > process exiting.>
              > <Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest
              > failed
              > weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
              > exception:
              > [weblogic.rjvm.PeerGoneException: ; nested exception is:
              >         weblogic.utils.net.SocketResetException].
              > weblogic.rjvm.PeerGoneException: ; nested exception is:
              > weblogic.utils.net.SocketResetException
              > at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
              > at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
              > at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
              > Source)
              > at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
              > at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
              > at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              > Caused by: weblogic.utils.net.SocketResetException
              > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
              > ... 2 more
              > --------------- nested within: ------------------
              > weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
              > exception:
              > [weblogic.rjvm.PeerGoneException: ; nested exception is:
              >         weblogic.utils.net.SocketResetException]
              > at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
              > Source)
              > at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
              > at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
              > at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              >
              > Any ideas?
              >
              > Regards.
              > Eran
              >
              >
              >
              >
              > ------------------------------------------------------------------------
              >
              > Managed server log error:
              > ***************************************************************************
              > The WebLogic Server did not start up properly.
              > Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain'
              > Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain
              > ***************************************************************************
              >
              >
              > Admin Server log:
              > <Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain. Method: null. Exception: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
              > not found for MBean orsus:Name=orsus,Type=Domain.
              > javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain
              > at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
              > at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
              > at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
              > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
              > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
              > at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
              > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
              > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
              > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
              > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
              > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
              > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              > <Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed Server orsusClusterNode_2 is disconnected from the admin server. This may be either due to a managed server getting temporarily partitioned or the managed server process exiting.>
              > <Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
              > weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
              > [weblogic.rjvm.PeerGoneException: ; nested exception is:
              >         weblogic.utils.net.SocketResetException].
              > weblogic.rjvm.PeerGoneException: ; nested exception is:
              > weblogic.utils.net.SocketResetException
              > at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
              > at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
              > at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown Source)
              > at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
              > at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
              > at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              > Caused by: weblogic.utils.net.SocketResetException
              > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
              > ... 2 more
              > --------------- nested within: ------------------
              > weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
              > [weblogic.rjvm.PeerGoneException: ; nested exception is:
              >         weblogic.utils.net.SocketResetException]
              > at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown Source)
              > at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
              > at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
              > at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              >
              

  • Question:managed server status display unknown ??

    platform: AS5 weblogic8.16 cluter
    when managed server startup,status ok,but after some days,managed server status is unknown or shutdown in console web
    I check process "ps -ef|grep java" managed server process exit
    and application on managed server is ok
    this is log in domain.log
    ####<2009-9-9 <Warning> <Management> <web3> <myserver> <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <BEA-141138> <Managed Server web03 is disconnected from the admin server. This may be either due to a managed server getting temporarily partitioned or the managed server process exiting.>
    after restart managed server ,status running
    so why managed server status display unknown/shutdown after some days?? how can i solve this problem??

    Status unknown means that node manager can't establish contact with the mgd server. If your server is dropping out of the cluster, that would result in Unknown.
    Your server could be dropping out of the cluster for many, many reasons. If it is always the same server dropping out, that points to a particular node in your cluster.

  • Issue while connecting to managed server through WSLT

    Hi All,
    we have one Admin Server and 6 managed server.
    we are successfully able to connect to Admin server which is running on port 7001 but
    when we are trying to connect to any of the managed server at port 8001 we are getting below error:
    Traceback (innermost last):
    File "<console>", line 1, in ?
    File "<iostream>", line 22, in connect
    File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://<host>:8001
    Use dumpStack() to view the full stacktrace
    Please let us know how to enable WLST to connect to managed servers.
    Thanks

    This was a silly mistake from my side.
    Actually our server hosts multiple managed server on same machines using VIP.
    hence using Alias in WLST connect command solved the issue,
    Thanks.

  • 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

Maybe you are looking for

  • How to create a variant to a report from another program at run time

    Hi experts,                when i am using FM  :  /OSP/REPORT_CREATE_VARIANT to create a report variant from a program then i am getting  an error 'For object /OSP/ERPNR , number range interval 01 does not exist ', how should i avoid it or can any on

  • PO wise venodr payment status

    Hi Experts, Is there any report wherein I can see Purchase Order, Item wise vendor payment status, i.e. whether payment is cleared, Parked or open item. Suggest me if there is any transaction exist or on how to address development of this report. Tha

  • Dual 30" displays and dual pointers

    I have dual 30" displays and find that many times I have TWO mice. I just move the mouse across both monitors and one mouse goes away. But i comes back next time the computer goes to sleep. G5 dual 2.5 - 2GB ram   Mac OS X (10.3.9)  

  • Biztalk 2006 issue

    Hello: We have change the DNS setting of our Standby SQL Server to production. I see connection coming from BIZTALK server into SQL Server and all required BizTalk Services are running fine. I am getting following error as shown below when I try to c

  • What is that weird button next to multitasking volume control that controls whether music comes out of ear speaker or bottom speaker?

    There is a weird button beside the multitasking volume control that allows me to play the music through the ear speaker. The button shows a rectangle and triangle together. Is this normal?