HANDSHAKE_FAILURE problem when starting managed server via NOdeManager
hi all, i am trying to start a managed server using nodeManager, but i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for
server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
to negotiate an acceptable set of security parameters.. Please ensure that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try to start
the managed server via adminserver console, i got the exception mentioned in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver, and
nodemanager is supposed to run at localhost:5555 (and indeed it does, because
ihave started it successfully).
thanx in advance and regards marco
Marco.
Sorry, this is not a solution to your problem but i am trying to solve the same
problem for a week now.
I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
same error. I know that the default certificate installed provides a hostname
verification of weblogic.com. I turned the hostname verification off, i put in
the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
error when starting the managed server. I went ahead and created my own certificate
for machine called mallik, created my own passphrase, created a new keystore,
made the admin server view the keystore, used the same certificate for both the
admin server and the node manager. It still fails with the same error. I went
ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
totally confused now what needs to be done.
My nodeManger.hosts looks like this:
mallik 10.100.10.130
managedServer1 10.100.10.130
managedServer2 10.100.10.13
Below is the startNodeManager.cmd.
@echo off
@rem *************************************************************************
@rem This script can be used to start the WebLogic NodeManager
@rem
@rem This script sets the following variables before starting the NodeManager:
@rem
@rem WL_HOME - The root directory of your WebLogic installation.
@rem NODEMGR_HOME - The home directory for this NodeManager instance.
@rem JAVA_HOME - Location of the version of Java used to start WebLogic
@rem Server. This variable must point to the root directory of
@rem a JDK installation and will be set for you by the
@rem installer. See the WebLogic platform support page
@rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
list of
@rem supported JVMs on Windows NT.
@rem PATH - Adds the JDK and WebLogic directories to the system path.
@rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
@rem JAVA_OPTIONS - Java command-line options for running the server. (These
@rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
@rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
@rem -client, etc.)
@rem MEM_ARGS - The variable to override the standard memory arguments
@rem passed to java
@rem
@rem *************************************************************************
SETLOCAL
set WL_HOME=C:\bea7.0\weblogic700
set NODEMGR_HOME=%WL_HOME%\common\nodemanager
set JAVA_HOME=C:\bea7.0\jdk131_06
Call %WL_HOME%\common\bin\commEnv.cmd
@rem If NODEMGR_HOME does not exist, create it
:checkNodeManagerHome
if exist %NODEMGR_HOME% goto checkJava
echo.
echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
mkdir %NODEMGR_HOME%
@rem Check that java is where we expect it to be
:checkJava
if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
echo The JDK wasn't found in directory %JAVA_HOME%.
echo Please edit this script so that the JAVA_HOME
echo variable points to the location of your JDK.
goto finish
:runNodeManager
if not "%JAVA_VM%" == "" goto noResetJavaVM
rem set JAVA_VM=-hotspot
set JAVA_VM=%COMM_VM%
:noResetJavaVM
if not "%MEM_ARGS%" == "" goto noResetMemArgs
set MEM_ARGS=-Xms32m -Xmx200m
:noResetMemArgs
@echo on
set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
cd %NODEMGR_HOME%
#"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
"-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
"-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
"-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
"-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
goto finish
:finish
ENDLOCAL
I would appreciate if anybody can help me.
Mallik.
"Marco" <[email protected]> wrote:
>
hi all, i am trying to start a managed server using nodeManager, but
i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for
server managedServer via the Node Manager - reason: [CommandInvoker:
Failed to
send command: 'online to server 'managedServer' to NodeManager at host:
'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
was unable
to negotiate an acceptable set of security parameters.. Please ensure
that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
-Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost
and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try
to start
the managed server via adminserver console, i got the exception mentioned
in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver,
and
nodemanager is supposed to run at localhost:5555 (and indeed it does,
because
ihave started it successfully).
thanx in advance and regards marco
Similar Messages
-
Problems starting managed server via nodemanager
Hello,
I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
One hosts the admin server and the seconds hosts a managed server.
I installed the nodemanager on both maschines. They seems to run
normally.
I configured the "Remot Start" for the managed server as mentioned in
the manual. I didn't specified any values in that panel because the
nodemanager uses the same environment as the WLS so these values should
fit the managed WLS too.
But as I try to start the managed server I got the following error
message:
Starting WebLogic Server ....
Child exited
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
So I specified some basic values on the "Remote Start" panel:
BEA_HOME: /www/apps/bea/
ROOT_DIR: /www/apps/bea/wlserver6.1
CLASSPATH:
/www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
No I got this message:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Child exited
What did I wrong?
Has anybody experiences on this problem?
Thanks !
Falko Zurell - Webmaster
Pixelpark AG
Germanynodemanager must be using the old jvm (1.2.2 or whatever comes by
default with 2.8). set up the environment or modify
startNodeManager.sh so that it uses java 1.3.1 that ships with WLS6.1
o.
Falko Zurell <[email protected]> wrote in message news:<[email protected]>...
Hello,
I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
One hosts the admin server and the seconds hosts a managed server.
I installed the nodemanager on both maschines. They seems to run
normally.
I configured the "Remot Start" for the managed server as mentioned in
the manual. I didn't specified any values in that panel because the
nodemanager uses the same environment as the WLS so these values should
fit the managed WLS too.
But as I try to start the managed server I got the following error
message:
Starting WebLogic Server ....
Child exited
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
So I specified some basic values on the "Remote Start" panel:
BEA_HOME: /www/apps/bea/
ROOT_DIR: /www/apps/bea/wlserver6.1
CLASSPATH:
/www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
No I got this message:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
at weblogic.management.Admin.initialize(Admin.java:279)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Child exited
What did I wrong?
Has anybody experiences on this problem?
Thanks ! -
ClassNotFoundException When Starting Managed Server with NodeManager
Hi Experts,
ENV:
Weblogic Server 10.3.3
Webcenter 11.1.1.3
My managed server can be brought up correctly by stopManagedWebLogic.sh <ManagedServerName>. But when trying to start them up, app on that server can not run correctly, and node manager log complained that below classes are not found:
oracle.jrf.wls.JRFStartup
oracle.security.jps.wls.JpsWlsStartupClass
oracle.core.ojdl.weblogic.ODLConfiguration
oracle.jrf.AppContextStartup
oracle.ias.cache.Startup
oracle.dms.wls.DMSStartup
My Nodemanager is setup following instructions in OBE.Administering Managed Servers by Using the Node Manager(http://www.oracle.com/technology/obe/fusion_middleware/wls103/installconfig/admin_mngd_srvr/admin_ms_using_nm.htm#t4). Output javaclaspath of setWLSEnv.sh has been copy&pasted to admin console->server->..->Server start->classpath
Thanks,
ToddTrying setting the property StartScriptEnabled=true instead of false.
You can change this in the nodemanager.properties file (usually located in the directory <middleware-home>/wlserver_10.3/common/nodemanager)
The classes are set in the startscripts, such as setDomainEnv, which is called by startWebLogic.
The latter script is set by default in the nodemanager.properties file, through the property StartScriptName=startWebLogic.cmd. -
Problem while starting managed server using nodemanager
Hi everyone,
I am using WLST of Weblogic server 10.3, to automate the creation of domain, managed servers,JDBC,JMS resources etc.. and trying to start the managed servers using node manager. I have an environment which contains few domains. All the domains are using machine named "X".
Now, i am creating the same machine in my domain WLSTDomain. I have the following doubts.
Is there a way to check whether the nodemanager(of X) is already running.
If there is a way to check that, how can we start the managed servers in WLSTDomain using that existing nodemanager.1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig> -
Authentication for user weblogic denied problem when starting managed serve
Hi All,
I have a strange situation here. I installed WLS and SOA and BAM servers. Initially I could start both WLS and SOA.
Later I changed some files (possibly startManagedWebLogic.sh or deleted soa_server1/data/ldap/ or AdminServer/security/boot.properties), but later I remember I changed them back. I am now seeing that my WLS is starting up fine, but SOA is not. I am always getting the error:
<Critical> <WebLogicServer> <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(CommonSecurityServiceManagerDelegateImpl.java:965)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
>
I tried to go to admin console to change/verify the password for weblogic user, and then put plaintext password in AdminServer/security/boot.properties, then restart Adminserver. But I still cannot start SOA server.
Could you please let me know how to resolve this issue? I do want to save my environment at this point. Many thanks.Hi,
My understanding is admin user server is coming up fine but when you try to bring the soa_server1(managed instance) is not coming up due the below mentioned exception.
If not please correct me.
I have a few query, please give me comment on this.
1) Admin and managed instances are running on the same box or different
2) Did you try to reset the password from console or using weblogic.security command
3) Did you cleared the soa_server1 temp directory(server/soa_server1/*)
Solution-1 (If Domain running on different box)
=============================
1) Copy the DefaultAuthenticatorInit.ldift file from Domain_dir/Security/ to Remote machine - Domain_dir/Security/
Note- Remote machine - take a backup of DefaultAuthenticatorInit file.
2) Remote machine- rename or take a backup of ldap directory and boot.properties file
/servers/soa_server1/ldap
/servers/soa_server1/security/boot.properties.
3) Now try to brought up the soa_server1.It will prompt you the username and password.
Please let me know.
Thanks,
Rajkumar -
Facing error in starting managed server from nodemanager
Hi All,
I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
<11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
Can anyone please tell me what could be the issue. It is really urgent. Please help!!Hi Roshni,
It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
3. Save and close the file.
4. Restart the Node Manager
If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
Thanks,
Scott (PITSS)
http://pitss.com/us -
Error when starting managed server
Hi,
I have a setup with a admin-server and a managed server. Everything
worked fine, until one day, an exception started occurring in the logs
when starting the managed server.
The setup is:
- WLS6.1SP2
- Solaris 8, SPARC
The exception is:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
I've taken a look in the admin-servers JNDI-tree, and it is correct,
it only has "weblogic.transaction.resources", and is missing the
unresolved "atserver1" part.
Why is it suddenly referencing this, and what can/should I do about
it.
The server seems to be running even with this exception.
Full stack trace at managed server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
oid: '9', implementation: 'weblogic.jndi.interna
l.RootNamingNode@6fb3d6''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy6.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Full server stack trace in admin server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
oid: '267', implementation: 'weblogic.management.inte
rnal.AdminMBeanHomeImpl@46cc9c''
javax.management.InstanceNotFoundException:
atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help appreciated!
Regards, PerHi Per
I have problems in creating managed server in the default mydomain .Do i need
to configure a new machine if the managed server and admin server are going to be
in the same machine.
I created a new machine that has the following parameters
listen address :localhost
Listen port :7001
As the next step i created a server with the machine name pointing to new one, when
i tried to start this as a managed server it gives an Error
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: java
.security.acl.NotOwnerException - with nested exception:
[java.lang.IllegalAccessError: java.security.acl.NotOwnerException]
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:12
5)
could you please help me on creating a managed server
thanks in advance
karthik
[email protected] (Per Olesen) wrote:
Hi,
I have a setup with a admin-server and a managed server. Everything
worked fine, until one day, an exception started occurring in the logs
when starting the managed server.
The setup is:
- WLS6.1SP2
- Solaris 8, SPARC
The exception is:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
I've taken a look in the admin-servers JNDI-tree, and it is correct,
it only has "weblogic.transaction.resources", and is missing the
unresolved "atserver1" part.
Why is it suddenly referencing this, and what can/should I do about
it.
The server seems to be running even with this exception.
Full stack trace at managed server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
oid: '9', implementation: 'weblogic.jndi.interna
l.RootNamingNode@6fb3d6''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy6.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Full server stack trace in admin server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
oid: '267', implementation: 'weblogic.management.inte
rnal.AdminMBeanHomeImpl@46cc9c''
javax.management.InstanceNotFoundException:
atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help appreciated!
Regards, Per -
Problem with starting managed server
In a domain , I have one admin server and one managed server. When im trying to start managed server , the message says,
Message icon - Warning For server Server-0, the Node Manager associated with machine Machine-0 is not reachable.
Message icon - Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
Already i started the node manager , i checked with node manager's log files, and I found these error in log files,
<Jul 30, 2010 12:54:32 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Can any one help me to troubleshoot this.Hi Jose,
To Disable SSL communication for NodeManager do the following:
<b><font color=maroon>Step1).</font></b> Open the *"nodeManager.properties"* file from *<WL_HOME>\common\nodemenager* (Example Location : C:\bea103\wlserver_10.3\common\nodemanager ) directory and change the value of SecureListener property to false:
SecureListener=false
<b><font color=maroon>Step2).</font></b> Login to AdminConsole and then
AdminConsoleHome--->Machines --><Your_MachineName> (Click here)--->NodeManager (Tab)---> Select the type as "Plain" from the combo box (by default it will be SSL)
<b><font color=maroon>Step3).</font></b> Restart the NodeManager ....better if you follow Step4) as well...
<b><font color=maroon>Step4).</font></b> Please Enroll your NodeManager as described in the Step8) of the following Link: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/
Thanks
Jay SenSharma -
Fatal initialization exception occurs when starting Managed Server
Hi all,
First I configured a Adminisistration server and started it. After that I added
a another server as ManagedServer.These two points to the same Weblogic server.
When I try to start Managed server by running the script, it gave me following
error. _______________________________
<Jun 25, 2001 5:25:11 PM GMT+06:00> <Emergency> <Server> <Unable to initialize
the server: 'Fatal initialization exception Throwable: java.lang.IllegalAccessError:
java.security.acl.NotOwnerException java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91) at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183) at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116) at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:444)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:287)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:259)
at weblogic.jndi.Environment.getContext(Environment.java:135) at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:891) at weblogic.management.Admin.start(Admin.java:305)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35) ______________________________________________
I suspect reason for this might be weblogic.policy file. There you need to edit
some lines replacing the location of the directory in which you installed WebLogic
Server. I did this but still error occurs.
Do u have any idea why above error occurs and if it is due to the weblogic.policy
file entry please tell me how it correctly done.
I am using WL60(sp2)in Win NT,
My installed dir: E:\bea\wlserver6.0\
Thanks NalikaHi
(It was me and Berit that sent the original question).
After some experimentation we saw that the managed server did get
some configuration from the admin server, so the problem was in
there somewhere.
I had added an (empty) cluster and machine to the admin server, just
to test adding. When I removed them everything worked fine afterward.
So it was some kind of configuration error from our side, but we never
did find out what it was.
I guess the lesson is to only define things when you really need them :-)
Regards
Mikael
Timothy Fry wrote:
We're getting the same problem, but on Solaris 2.7.
Did you get a solution from bea yet?
Tim
"Berit Bylund" <[email protected]> wrote in message
news:[email protected]..
Hello
We are trying to start a managed server (under the examples
domain, NT 4.0, WLS 6.0 Beta 2)
We start the managed server with the parameter
-Dweblogic.management.server=http://127.0.0.1:7001 -
Starting managed server with nodemanager
Hi there,
Please help me with the weblogic server installation, i've studk with failed to start managed server with node manager. My scenario as below:
(1) set up the main server and able to run the server successfully.
(2) set up one managed server, set up one machine on same server as main server.
(3) assign machine to created managed server.
(4) after that i've tried to run that managed server and error giving as below:
Error from main server terminal
===================
<NodeManager> <BEA-300048> <Unable to start the server 'ManagedServer1': Exception while starting server 'ManagedServer1': java.io.IOException: Server failed to start up. See server output log for more details.>
Error from Node Manager Termal
====================
<Info> <MainServer> <'ManagedServer1'> <Server failed during startup so will not be restarted>
<Dec 7, 2009 7:04:45 PM> <Warning> <Exception while starting server ''ManagedServer1'': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Thanks in advance,
TimSorry , i forgot to mention that the OS i am using is Solaris.
Thx -
Cannot start managed server via WLST - 'Overriding the ListenPort ...'
Hello everyone
I've created a development domain that has two machine, each of them has two weblogic server instances. On machine-2, I've started NodeManager already.
I started WLST tool, connect to AdminServer and invoke 'start' command to start managed server on machine-2:
start('MS-02','Server','t3://dvc.danang.vn:7003')
but I get fail message like that
wls:/dnict_domain/serverConfig> start('MS-02','Server','t3://dvc.danang.vn:7003')
Overriding the ListenPort or ListenAddress is not supported.
WLST will use the ListenPort and ListenAddress that are configured on the ServerMBean
Starting server MS-02 ....Permission denied (publickey,password).
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1280, in start
File "<iostream>", line 1744, in raiseWLSTException
WLSTException: Error occured while performing start : Error starting the server : Error occured while performing start : Server with name MS-02 failed to be started
Use dumpStack() to view the full stacktrace
wls:/dnict_domain/serverConfig> dumpStack()
This Exception occurred at Sun Oct 09 18:46:16 ICT 2011.
weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name MS-02 failed to be started
at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleHandler.java:501)
at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.java:477)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx21.start$80(<iostream>:1270)
at org.python.pycode._pyx21.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx28.f$0(<console>:1)
at org.python.pycode._pyx28.call_function(<console>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.core.Py.exec(Unknown Source)
at org.python.util.PythonInterpreter.exec(Unknown Source)
at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name MS-02 failed to be startedI'm wondering about "Permission denied (publickey,password)" error. Can you show me how to fix this issue?
Any suggestion is appreciated
Regards
Cuong PhamTry removing the 't3://dvc.danang.vn:7003' argument. If this information is configured in the managed server, its unnecessary.
Also, is the NodeManager registered with the AdminServer? You can use the command "nmEnroll([domainDir], [nmHome])" while connected to the AdminServer to if its not. -
Problem in starting managed server
hi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
andhi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
and -
Can't start vanilla 8.1.4 platform managed server via NodeManager
I cannot get a managed server to start via the NodeManager if I create a WL Platform domain. I CAN get it to work just fine if I create a regular WLS domain. I was wondering if anyone else has seen this behavior.
Steps to Reproduce
===================
1) Use the configuration wizard to create a WebLogic Platform domain. Name the domain "Test". Use all defaults.
2) Once the domain is created, go into the domain directory and run the create_db.cmd script to build out the necessary tables to support the platform domain
3) Start the node manager. On my machine I use the following command:
C:\bea\weblogic81\server\bin\startnodemanager 127.0.0.1 5555
4) Start the admin server via the startWebLogic.cmd file
5) Open the console for the admin server. Create a Machine "MyMachine" (name is really unimportant). Use the default NodeManager port of 5555
6) Create a managed server. Call it "test1". Set the port to 8000 and be sure to assign it to the machine you just created.
7)Set the remote start properties. On my machine I just set the classpath to "c:\bea\weblogic81\server\lib\weblogic.jar;C:\bea\weblogic81\workshop\lib\wsrp-common.jar;C:\bea\weblogic81\server\lib\xbean.jar" and I also set the Java Home to point to the default JRocket JVM that ships with 8.1.4
8) Be sure to save your changes by hitting the "Apply" button. Then using the "Control" tab for the "test1" managed server, click the "Start this Server" link.
9) Wait about 30 - 40 seconds, then click on the server log for that server. On my machine I get the following exception in the log:
<Mar 22, 2005 6:04:46 PM PST> <Info> <[email protected]:5555> <Starting Server test::test1 ...>
<Mar 22, 2005 6:04:47 PM PST> <Info> <[email protected]:5555> <Server test::test1 started, process id = 5,504>
<Mar 22, 2005 6:04:48 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
<Mar 22, 2005 6:04:49 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://169.254.40.11:7001 to check if there exists a running admin server at this URL.>
<Mar 22, 2005 6:04:49 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 22, 2005 6:04:49 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Mar 22, 2005 6:04:49 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://169.254.40.11:7001 to retrieve the initial configuration.>
<Mar 22, 2005 6:04:50 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\test1\test1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:205)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
Reason: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
<Mar 22, 2005 6:04:53 PM PST> <Critical> <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:205)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
<Mar 22, 2005 6:04:53 PM PST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.>
I am baffled by this error. Can anyone help shed some light on this issue? I'm sure there is some bit I left un-flipped somewhere, but I don't know where to look. Many thanks in advance!
- JeffPlease help me over this error: (Weblogic clustered setup, two managed servers and one admin server, siteminder security providers configured)
bash-2.05$ ./startManagedWebLogic.sh managedServer5 http://sunert1.ad.infosys.com:7007
./startManagedWebLogic.sh: -Dsmasa.home=/export/home/ngtyasqa/bea/asa: not found
CLASSPATH=/export/home/ngtyasqa/bea/asa/conf:/export/home/ngtyasqa/bea/asa/lib/smjavaagentapi.jar:/e
xport/home/ngtyasqa/bea/asa/lib/log4j.jar:/export/home/ngtyasqa/bea/asa/lib/sm_jsafe.jar:/export/hom
e/ngtyasqa/bea/asa/lib/smclientclasses.jar:/export/home/ngtyasqa/bea/asa/lib/smjavasdk2.jar:/export/
home/ngtyasqa/bea/asa/lib/imsapi.jar/export/home/ngtyasqa/bea_kunal/jdk142_04/lib/tools.jar:/export/
home/ngtyasqa/bea/weblogic81/server/lib/weblogic_sp.jar:/export/home/ngtyasqa/bea/weblogic81/server/
lib/weblogic.jar::/export/home/ngtyasqa/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/exp
ort/home/ngtyasqa/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/export/home/ngtyasqa/bea_
kunal/jdk142_04/jre/lib/rt.jar:/export/home/ngtyasqa/bea/weblogic81/server/lib/webservices.jar:
PATH=/export/home/ngtyasqa/bea/weblogic81/server/bin:/export/home/ngtyasqa/bea_kunal/jdk142_04/jre/b
in:/export/home/ngtyasqa/bea_kunal/jdk142_04/bin:/export/home/ngtyasqa/bea_kunal/jdk142_04/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 *
<Mar 21, 2006 5:25:48 PM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server w
ith Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
<Mar 21, 2006 5:25:49 PM GMT+05:30> <Info> <Management> <BEA-141140> <The managed server is going to
contact the admin server at http://sunert1.ad.infosys.com:7007 to check if there exists a running a
dmin server at this URL.>
<Mar 21, 2006 5:25:49 PM GMT+05:30> <Info> <Configuration Management> <BEA-150017> <This server is b
eing started as a dependent managed server.>
<Mar 21, 2006 5:25:49 PM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 S
P5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 >
<Mar 21, 2006 5:25:50 PM GMT+05:30> <Info> <Configuration Management> <BEA-150015> <Connecting to th
e administration server http://sunert1.ad.infosys.com:7007 to retrieve the initial configuration.>
<Mar 21, 2006 5:25:54 PM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file /exp
ort/home/ngtyasqa/bea/user_projects/domains/mydomain/managedServer5/managedServer5.log is opened. Al
l server side log events will be written to this file.>
<Mar 21, 2006 5:26:03 PM GMT+05:30> <Critical> <WebLogicServer> <BEA-000364> <Server failed during i
nitialization. Exception:weblogic.security.service.SecurityServiceRuntimeException: [Security:090371
]Problem instantiating Authentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexp
ected Exception - with nested exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Au
thentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with ne
sted exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:2
25)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:283)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManager
DelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServ
iceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceMan
agerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecuritySer
viceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceMa
nagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:7
34)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:821)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
at weblogic.Server.main(Server.java:32)
>
<Mar 21, 2006 5:26:03 PM GMT+05:30> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize
the server: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem inst
antiating Authentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Excepti
on - with nested exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]>
The WebLogic Server did not start up properly.
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Au
thentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with ne
sted exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:2
25)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:283)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManager
DelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServ
iceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceMan
agerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecuritySer
viceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceMa
nagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:7
34)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:821)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
at weblogic.Server.main(Server.java:32)
Reason: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instanti
ating Authentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception -
with nested exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]
Thanks and Regards,
Shefali -
Error when starting managed server Message Too Long
Hi,
I'm trying to setup clustering with WLS6.1sp2.
I use the jdk include with wls
2 servers in the cluster OS=AIX
1 Adminserver running on Solaris 8
When I start a managed server on one of the clustered machines
I see the following error.
Starting Cluster Service ....
<Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread listening
on port 7001, ip address 10.160.3.74>
<Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast message:
java.io.IOException: Message too long
java.io.IOException: Message too long
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
at java.net.DatagramSocket.send(DatagramSocket.java:341)
at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
Code))
at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast messages
(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
<Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic Managed
Server "s01ap007" for domain "axa" running in Production Mode>
Also deploying doesn't seem to succeed could this be coused by this error
I hope someone can help me.
Best regards,
Peter Van der Goten
Because I found the answer via Mr. yunyee who also had this problem on an AIX machine
I will post this also here.
The problem was that the upd_sendspace variable was set on
a mutch to low value (9126) or something in this range
It had to be set on 32769.
this was done with no -o udp_sendspace=32769
Best regards,
Peter
"Peter Van der Goten" <[email protected]> wrote:
>
>Hi,
>I'm trying to setup clustering with WLS6.1sp2.
>I use the jdk include with wls
>2 servers in the cluster OS=AIX
>1 Adminserver running on Solaris 8
>
>When I start a managed server on one of the clustered machines
>I see the following error.
>Starting Cluster Service ....
><Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread
>listening
>on port 7001, ip address 10.160.3.74>
><Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast
>message:
>java.io.IOException: Message too long
>java.io.IOException: Message too long
> at java.net.PlainDatagramSocketImpl.send(Native Method)
> at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
> at java.net.DatagramSocket.send(DatagramSocket.java:341)
> at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
> at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
> at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
>Code))
> at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
> at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
> at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
> at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
> at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
> at weblogic.Server.main(Server.java:35)
>>
><Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast
>messages
>(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
><Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic
>Managed
>Server "s01ap007" for domain "axa" running in Production Mode>
>
>Also deploying doesn't seem to succeed could this be coused by this error
>
>I hope someone can help me.
>Best regards,
>Peter Van der Goten
>
-
Failes to start Managed server using Nodemanager from admin console
Hi
I have created the cluster using Weblogic version 9.2 MP3 with
Machine 1 --> Admin (AS) + Managed server (MS1)
Machine 2 --> Managed server(MS2)
All the servers(AS,MS1,MS2) are SSL configured to run in production mode.
Machine is associated with each managed server and node manager is up and running.
I have made Host name verification as "None"
When i start the MS 1 from admin console it comes up in running.However MS2 is not coming in running mode.
The server logs states that "Could not connect to admin server"
Cannot decrypt the password ,username and TrustKeyStorePrivatepassphrase.
Even when i write the clear text password and username in Server_Name/data/nodemanager/boot.properties,then also it throws the same error.
Node manager is not configured to SSL.
Any Clue what i am missing????Is your Machine #2 shown as "Reachable" in the admin console ( Machines -> Machine2 -> Monitoring )?
Does your managed server #2 have the same userid and password on its Server -> Configuration -> Server Start page ( UserName & Password fields ) as managed server #1?
Your boot.properties only needs 2 lines, like:
password=your plain text password
username=your plain text username
Maybe you are looking for
-
When i try to send email from my ipad i get the message The recipient "£)()&&£)" was rejected by the server. This has only just started to happen and I don't know why. Please can someone help. I have tried lots of things now and cannot solve it.
-
There's a corrupted file in my trash, how to delete it?
I need your help. I dont want to do anymore damage to my computer now. You could see Park.Mp4 is invisible-and there's no such file on the desktop Thanks!
-
my itunes dont have a check box thats way i dont know how can i be able to save or install aplication to my iphone3g.pls. help
-
How can i fix imessage when my friends send me too many messages and it wont load
My friends sent me 92 messages on the same group message and iMessage won't load because there are too many messages. Is there any way I can fix it because I tried resetting all settings and it didn't work.
-
BI_PROCESS_TRIGGER event job in released status ONLY
HI ALL, I WANT TO TRIGGAR PC TWICE IN DAY 5 PM AND 2AM. 1.I CTEATED EVENT IN SM62 (ZSDPC_EVENT) 2.I CTEATED SE 38 PROGRAM (zsdpp_pc_event_program )LIKE BELOW REPORT zsdpp_pc_event_program. DATA: gv_time TYPE sy-uzeit, eventid TYPE btceventid.