Manage Server Health Goes Blank in Admin Console
Hello Team,
I am continously facing issue with OSB manage server. It is running fine but health is blank in Admin Console.
Due to which it is not responding to any user request.
Kindly guide me to troubleshoot this issue.
Hi,
It is due to the problem with the JMX communication between and Admin and your OSB managed servers. Did you observed any messages related to it?
Is it a SSL communication, then try to make sure that certificates are valid.
As a general practice, make sure you have listen address configured for your servers. If left it blank(default), then it would be listening on the all the available host and communication would get messy in these situations.
If still facing problem, i would suggest you enable the below debugs and raise a support case
1. Apply the below three debug logs from console(for admin as well as Managed Server)
weblogic->management->JMXCore
weblogic->management->JMXDomain
weblogic->management->JMXRuntime
2. Restart all the servers
If the issue, occurs, provide the debug along with the thread dump(take 5 thread dump at an interval of 5seconds) for the Managed Server(which is unknown state) and for the admin server.
Regards
Rosario
Similar Messages
-
MANAGED SERVER NOT COMMING UP FROM ADMIN CONSOLE,
Hi All,
I can't start managed server from admin console.
The status is showing FAILED_NOT_RESTARTABLE.
below is the error it is showing in the node manager.
But i can start managed server from the back-end successfully. If i start the nodemanager then managed server is not comming up.
<May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed
_server'>
java.io.IOException: Server failed to start up. See server output log for more d
etails.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
May 24, 2011 4:12:22 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'my_managed_server'
java.io.IOException: Server failed to start up. See server output log for more d
etails.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
Please help.
Regards,
nag.<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain'>
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out00039">
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server error log also redirected to server log>
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out'>
<May 24, 2011 4:12:22 AM> <INFO> <weblogic_domain> <my_managed_server> <Server failed during startup so will not be restarted>
<May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed_server'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
This is what i found in nodemanager log file
Regards,
Nag. -
Can't start manager server on other machine from admin console
hi, m fredzh
i have weblogic 10.3.2 where i created a cluster named cluster1 on production mode
the machines and servers list as follow:
cluster1 192.168.1.100
--machine1
--server1 192.168.1.100
--machine2
-server2 192.168.1.101
i create nodemanager on machine2, and set the type as ssl, the listener address 192.168.1.101,
then login on 192.168.1.101, and run wlst.sh , nmEnroll and then start startNodemanaged.sh ..
start server2 on the admin console(on 192.168.1.100), failed and the log as follow:
can anbody help me, thank you..
==============================================================================
<Critical> <WebLogicServer> <localhost.localdomain> <managerServer2> <main> <<WLS Kernel>> <> <> <1286788326928> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
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.lang.reflect.InvocationTargetException
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.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
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: weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:125)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:173)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
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.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
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)
Edited by: fredzh on 2010-10-12 下午6:54hi,Jay
i followed the steps as follow:
1、change prod mode to dev
2、modified the config.xml entrys on the all two servers:
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<credential-encrypted>test</credential-encrypted>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
3、enrolled the node, then started the two adminservers, started server2's nodemanager..server2 can be started from the cluster admin console.
4、change the dev mode to prod mode on admin console, it failed throw error:
"in production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean"
i checked the config.xml ,the entrys i had changed were not aotomatically encrypted,may i manually encryp the clear text value? ..follow is the config.xml :
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>cluster_domain</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>cluster_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<anonymous-admin-lookup-enabled>false</anonymous-admin-lookup-enabled>
<credential-encrypted>test</credential-encrypted>
<web-app-files-case-insensitive>false</web-app-files-case-insensitive>
<compatibility-connection-filters-enabled>false</compatibility-connection-filters-enabled>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<principal-equals-case-insensitive>false</principal-equals-case-insensitive>
<principal-equals-compare-dn-and-guid>false</principal-equals-compare-dn-and-guid>
<downgrade-untrusted-principals>false</downgrade-untrusted-principals>
<enforce-strict-url-pattern>true</enforce-strict-url-pattern>
<cross-domain-security-enabled>false</cross-domain-security-enabled>
</security-configuration>
<jta>
<security-interop-mode>default</security-interop-mode>
</jta>
<server>
<name>AdminServer</name>
<ssl>
<hostname-verifier xsi:nil="true"></hostname-verifier>
<hostname-verification-ignored>true</hostname-verification-ignored>
<export-key-lifespan>500</export-key-lifespan>
<client-certificate-enforced>false</client-certificate-enforced>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
<inbound-certificate-validation>BuiltinSSLValidationOnly</inbound-certificate-validation>
<outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
<allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
<use-server-certs>false</use-server-certs>
</ssl>
<listen-port>7110</listen-port>
<listen-address></listen-address>
</server>
<server>
<name>server2</name>
<machine>machine2</machine>
<listen-port>7110</listen-port>
<listen-address>192.168.1.101</listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<java-home>/opt/jdk1.6.0_21</java-home>
<bea-home>/root/Oracle/Middleware</bea-home>
<root-directory>/root/Oracle/Middleware/user_projects/domains/cluster_domain</root-directory>
<username>weblogic</username>
<password-encrypted>{AES}xhSI75AxXtXdMrCXRgA2uY5pfcxUGE9X4YXTjfe1XEY=</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>machine2</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>192.168.1.101</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<admin-server-name>AdminServer</admin-server-name>
</domain>
Edited by: fredzh on 2010-10-13 下午7:57 -
How to start managed server on Weblogic 9.1 Admin console with jRockit
I configured a new 9.1 domain with jRockit as the JVM. Under Server Start, I used -server -Xgcprio:pausetime -Xpausetarget=400ms -Xms:256m -Xmx:384m -Xns:81m -Xgcpause in the Argument field. When I tried to start the server, I am getting the following error:
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Starting WebLogic server with command line: C:\bea\jrockit90_150_04\bin\java -Dweblogic.Name=jdevext -Dbea.home=C:\bea -Djava.security.policy=c:\bea\weblogic91\server\lib\weblogic.policy -Dweblogic.management.server=http://144.111.155.145:7001 -Djava.library.path=C:\bea\WEBLOG~1\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\bea\WEBLOG~1\server\native\win\32;C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\bea\WEBLOG~1\server\native\win\32\oci920_8;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Support Tools\;C:\Program Files\Intel\Wireless\Bin\;C:\Program Files\ThinkPad\ConnectUtilities;C:\Program Files\QuickTime\QTSystem\ -Djava.class.path=C:\bea\weblogic91\server\lib\weblogic.jar;C:\bea\jrockit90_150_04\lib\tools.jar;c:\bea\weblogic91\server\lib\wamapps\commons-logging.jar;c:\bea\weblogic91\server\lib\wamapps\log4j.jar;c:\bea\weblogic91\server\lib\wamapps\xalan.jar;c:\bea\weblogic91\server\lib\wamapps\xercesImpl.jar;c:\bea\weblogic91\server\lib\wamapps\xml-apis.jar -Dweblogic.system.BootIdentityFile=C:\bea\user_projects\domains\jdev\servers\jdevext\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false java -server -Xgcprio:pausetime -Xpausetarget=400ms -Xms:256m -Xmx:384m -Xns:81m -Xgcpause -verbose weblogic.Server >
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Working directory is "C:\bea\user_projects\domains\jdev">
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Server output log file is "C:\bea\user_projects\domains\jdev\servers\jdevext\logs\jdevext.out">
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-jrockit to select the "jrockit" VM
-client to select the "client" VM
-server to select the "server" VM [synonym for the "jrockit" VM]
The default VM is jrockit.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
<May 24, 2006 11:16:57 AM> <Info> <NodeManager> <Server failed during startup so will not be restarted>It looks like your command line is broken. You have:
java <lots of -Dprop=value> java <JRockit flags> weblogic.Server
That second "java" shouldn't be there.
-- Henrik -
11g node manager reachable but server does not start from admin console
I have a issue with node manager is reachable from admin console and from command prompt it is not connected and could not able to start the managed server.
If i change /config/nodemanager/nm_password.properties plain text and restart it is not reachable in admin console abut can connect from command prompt. I could not able to start the even with this scenario.
i see below error when try to check machine monitor tab.
<Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Access to domain 'dom_11gint' for user 'Ckr10ycOJN' denied".>
Ckr10ycOJN username in config.xml
node manager and managed servers are not root user process.
Please help me if have any suggestions.Pls. make sure the following points in your environment.
1) Check '*nodemanager.domains*' file in <<WL_HOME>>\commo\nodemanager directory
a) This file should have the entry for your domain 'dom_11gint'.
b) Ensure the path referred in the nodemanager.domains file is correct one.
2) Ensure the following remote server startup parameters are passed properly.
a) In the Admin Console, Navigate Servers --> <<SERVER_NAME>> -->Configuration --> Server Start
b) Pass the required Class Path, Arguments, User Name, Password(User name and Password to boot the managed servers) -
Managed server trying to start as admin server
I have one VM with SOA Suite that it is fully functional.
I made a copy of that VM and changed the hostname and IP.
Making a search under all the disk I replaced all occurences of the old hostname and IP with the new ones.
Now I can start AdminServer and soa_server, but when I try to start bam_server I'm getting the following error:
weblogic.management.ManagementException: Booting as admin server, but servername, bam_server, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
The steps I'm following to start the servers it is as follows:
cd $NM
wlst.sh
startNodeManager()
nmConnect('weblogic','welcome1','localhost','5556','soa_domain','/u01/app/oracle/user_projects/domains/soa_domain')
nmStart('AdminServer')
nmStart('soa_server')
nmStart('bam_server')
This post is related to this other post, but I don't have permissions to reply on that one, so I created a new one:
starting managed server with nodemanager
Thanks in advance for any tip you can give me.The servers starts correctly if I run the scripts, but not from the wlst.sh console:
$nohup $WL_HOME/server/bin/startNodeManager.sh > nodemanager.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/startWebLogic.sh > adminserver.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh soa_server > soa_server.out &
$nohup $MW_HOME/user_projects/domains/soa_domain/bin/startManagedServer.sh bam_server > bam_server.out & -
Managed servers are started/stopped from admin console using NodeManager
Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
AjmalHi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody -
Managed server not communicating back to admin server - JMX issue?
Hi,
I have a domain that consisted of:
1) 2 managed servers deploying an EAR for online use on server A
2) 1 managed server being used as a Queue Server for the JMS Module/JMS Server on server A
3) 2 managed servers deploying an EAR for online use on server B
4) 1 admin server to control the domain on server C
Servers A, B & C are running win2k3 and I'm using WLS 9.2.3
We've been shifting our infrastructure and I was tasked with relocating the Queue server to a new win2k8 box, server D. To achieve this 3 options occurred to me (having configured the new machine in my domain):
1) Change the IP address and machine for the Queue Server and then start it up on the new machine
2) Create a new Queue server on the new machine, and re-point the targets of the JMS Server and JMS Module to this new Queue server instead of the old one.
3) Create a new Queue server, new JMS Module and subdeployment and JMS Server, and all the JMS Queues (there are c.25)
I discounted option 3 due to the sheer amount of changes involved and the scope for error. I tested approaches 1 & 2 using a test domain on the new box first and all went well - the JMS queues could be populated and consumed following the migration to the new machine. For Production I went with approach 1 which was simplest.
However, despite the Queue server clearly working on the new machine (we've tested populating and consuming documents at both ends), for some reason it does not report back to the queue server - information such as it's health (e.g. OK, although it does report its state (e.g. RUNNING). Furthermore, the JMS queues no longer report their content - they all simply say "There are no items to display".
Looking in the Queue_Server_1.out file, I can see the following error occurred:
<26-Jun-2011 12:53:52 o'clock BST> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
<26-Jun-2011 12:55:18 o'clock BST> <Warning> <JMX> <BEA-149509> <Unable to establish JMX Connectivity with the Adminstration Server Administration_Server at service:jmx:admin://20.XXX.XXX.137:9002/jndi/weblogic.management.mbeanservers.domainruntime.
java.io.IOException
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:151)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:199)
Truncated. see log file for complete stacktrace
javax.naming.CommunicationException [Root exception is java.net.ConnectException: admin://20.XXX.XXX.137:9002: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:49)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
at weblogic.jndi.Environment.getContext(Environment.java:307)
at weblogic.jndi.Environment.getContext(Environment.java:277)
Truncated. see log file for complete stacktrace
java.net.ConnectException: admin://20.XXX.XXX.137:9002: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:204)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:154)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:350)
at weblogic.jndi.Environment.getContext(Environment.java:307)
at weblogic.jndi.Environment.getContext(Environment.java:277)
Truncated. see log file for complete stacktrace
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out: connect; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:475)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:326)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:261)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:204)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:226)
Truncated. see log file for complete stacktrace
Now the IP address of the admin server itself is OK (I've XXX out part of the number as it's my client's machines) but it looks like it's trying to connect using the 'admin' protocol, when it should connect using t3s shouldn't it? Any ideas?Hi there, thanks for your post. I can confirm that the IP and port can be reached as I've had the networks guys look at this. The issue seems to me to be related to the protocol used to establish the connection.
-
I have a warning on a fairly new managed server under health status...error is 'threadpool has stuck threads'. WHen I dump the thread stack I find this section. Any ideas?
"[STUCK] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'" id=1691 idx=0x328 tid=3904 prio=1 alive, in native, daemon
at jrockit/net/SocketNativeIO.readBytesPinned(Ljava/io/FileDescriptor;[BIII)I(Native Method)
at jrockit/net/SocketNativeIO.socketRead(SocketNativeIO.java:46)[optimized]
at java/net/SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[BIII)I(SocketInputStream.java)[inlined]
at java/net/SocketInputStream.read(SocketInputStream.java:129)[optimized]
at weblogic/jdbc/db2/drda/DRDAByteOrderedDataReader.receive()V(Unknown Source)
at weblogic/jdbc/db2/drda/DRDARequest.submitRequest()V(Unknown Source)[inlined]
at weblogic/jdbc/db2/DB2ImplResultSet.close()V(Unknown Source)[optimized]
at weblogic/jdbc/db2/DB2ImplStatement.close()V(Unknown Source)[optimized]
at weblogic/jdbc/db2/DB2ImplStatement.getAutoGeneratedKeyResultSet()Lweblogic/jdbc/db2base/BaseImplResultSet;(Unknown Source)
at weblogic/jdbc/db2base/BaseStatement.getGeneratedKeys()Ljava/sql/ResultSet;(Unknown Source)
at weblogic/jdbc/wrapper/PreparedStatement_weblogic_jdbc_db2base_BasePreparedStatement40.getGeneratedKeys()Ljava/sql/ResultSet;(Unknown Source)
at sun/reflect/GeneratedMethodAccessor1009.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[optimized]
at java/lang/reflect/Method.invoke(Method.java:597)[optimized]
at org/hibernate/util/GetGeneratedKeysHelper.getGeneratedKey(GetGeneratedKeysHelper.java:59)
at org/hibernate/persister/entity/BasicEntityPersister.insert(BasicEntityPersister.java:1761)
at org/hibernate/persister/entity/BasicEntityPersister.insert(BasicEntityPersister.java:2178)
at org/hibernate/action/EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:34)
at org/hibernate/engine/ActionQueue.execute(ActionQueue.java:239)
at org/hibernate/event/def/AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:240)
at org/hibernate/event/def/AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:160)
at org/hibernate/event/def/AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:95)
at org/hibernate/event/def/DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:184)
at org/hibernate/event/def/DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33)
at org/hibernate/event/def/DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:173)
at org/hibernate/event/def/DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27)
at org/hibernate/event/def/DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:69)
at org/hibernate/impl/SessionImpl.save(SessionImpl.java:481)
at org/hibernate/impl/SessionImpl.save(SessionImpl.java:476)
at com/fc/hibernate/DataContext.sessionSave(DataContext.java:71)
at com/fc/commandnet/fdm/SubmitDocumentAction.onSave(SubmitDocumentAction.java:111)
at com/fc/commandnet/fdm/FdmBaseAction.execute(FdmBaseAction.java:118)
at org/apache/struts/action/RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org/apache/struts/action/RequestProcessor.process(RequestProcessor.java:274)
at org/apache/struts/action/ActionServlet.process(ActionServlet.java:1482)
at org/apache/struts/action/ActionServlet.doPost(ActionServlet.java:525)
at javax/servlet/http/HttpServlet.service(HttpServlet.java:727)
at javax/servlet/http/HttpServlet.service(HttpServlet.java:820)
at weblogic/servlet/internal/StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic/servlet/internal/StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic/servlet/internal/ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic/servlet/internal/WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
at weblogic/security/acl/internal/AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)[inlined]
at weblogic/security/service/SecurityManager.runAs(SecurityManager.java:121)[optimized]
at weblogic/servlet/internal/WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic/servlet/internal/WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic/servlet/internal/ServletRequestImpl.run(ServletRequestImpl.java:1432)[optimized]
at weblogic/work/ExecuteThread.execute(ExecuteThread.java:201)[inlined]
at weblogic/work/ExecuteThread.run(ExecuteThread.java:173)[optimized]
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of traceAnd also the admin shows Health status of others OK very slowly it may take more than 30mins for all servers(13) to show the Heath state as OK untill then it shows Not reachable..
-
Why do I get timeout when deploying SQL Server data source in Weblogic Admin Console?
Hi all
I'm attempting connectivity between WLS 10.3.6.0 and SQL Server 2008R. I've downloaded sqljdbc4.jar and added to the end of the Weblogic Classpath in commEnv.cmd. Then I set up a data source in Admin Console and pressed the Test Data Source button - success. But when I tick the box to deploy to AdminServer it hangs for ages and I get timeout exception.
Any ideas?
Many thanks
JamesMake sure the web server settings between the QA and the Production servers are also compatible.
I suspect your suspecion about permissions is the closest to the answer. But this is a little out of my depth of expertise.
Realize that ColdFusion default behavior is to NOT generate and actual swf FILE. Rather what it does is generate the swf content in memory and directly deliver it to the client. But if the web server is configured to look for an actual file system file you may have a clash going on -
Start Managed Server from Admine clonsole FAILED_NOT_RESTARTABLE
when trying to start the managed server Managed-Server-01 from the WLS Admin Console the managed server status becomes <FAILED_NOT_RESTARTABLE> and not coming up:
Managed servers logs:
/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-01/logs:
3/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false>
<Sep 13, 2011 6:15:46 PM> <Debug> <NodeManager> <Environment: SERVER_NAME=Managed-Server-03>
<Sep 13, 2011 6:15:46 PM> <Info> <NodeManager> <Working directory is "/usr/local/bea/user_projects/domains/eShop">
<Sep 13, 2011 6:15:46 PM> <Info> <NodeManager> <Server output log file is "/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-03/logs/Managed-Server-03.out">
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: expr: not found
/usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: test: argument expected
<Sep 13, 2011 6:15:47 PM> <Debug> <NodeManager> <Waiting for the process to die: 1226>
<Sep 13, 2011 6:15:47 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<Sep 13, 2011 6:15:47 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
--=--
Node Manager log during Managed-Server-01 start from WLS Admin Console shows:
15:46 PM> <Info> <eShop> <Managed-Server-03> <Working directory is "/usr/local/bea/user_projects/domains/eShop">
<Sep 13, 2011 6:15:46 PM> <Info> <eShop> <Managed-Server-03> <Server output log file is "/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-03/logs/Managed-Server
-03.out">
<Sep 13, 2011 6:15:47 PM> <Info> <eShop> <Managed-Server-03> <Server failed during startup so will not be restarted>
<Sep 13, 2011 6:15:47 PM> <Warning> <Exception while starting server 'Managed-Server-03': 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:6
Note:
The installation of WLS done using Root.
We can start/stop MS using conventional ways.
Cheers,although i am not an expert,
but i am very confident that any WLS you install,
it can be configured like i tried it,
First Environment-----Machine
Add a machine by giving a name
Second Environment------Server
Add a server giving a sever name
Third Environment----machine
Add the server to the machine from the tab server
Fourth Environment-------server
Add A a SSL Port to the Sever and save
Click Start Server and every thing goes well
Thanks
Edited by: kashif, pakistan on Sep 14, 2011 4:09 AM -
My realm error while starting managed server on a remote machine
Tried to start the managed server on the remote from admin console...got the below error message
Node manager on the remote machine is up and running.Start request reaches the node manager but it fails to start the server because of below error.
<May 6, 2011 2:12:46 AM PDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: javax.jdo.JDOFatalInternalException: Unexpected exception caught.
NestedThrowables:
java.lang.reflect.InvocationTargetException.
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: javax.jdo.JDOFatalInternalException: Unexpected exception caught.
NestedThrowables:
java.lang.reflect.InvocationTargetException
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
Truncated. see log file for complete stacktrace
Caused By: com.bea.common.engine.ServiceInitializationException: javax.jdo.JDOFatalInternalException: Unexpected exception caught.
NestedThrowables:
java.lang.reflect.InvocationTargetException
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)
Truncated. see log file for complete stacktrace
Caused By: javax.jdo.JDOFatalInternalException: Unexpected exception caught.
NestedThrowables:
java.lang.reflect.InvocationTargetException
at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:549)
at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:149)
at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:99)
at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
Truncated. see log file for complete stacktrace
Caused By: java.lang.reflect.InvocationTargetException
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 javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:534)
Truncated. see log file for complete stacktrace
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:891341 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "org.apache.openjpa.abstractstore.AbstractStoreBrokerFactory". See the nested exception for details.
at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)
at kodo.jdo.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(PersistenceManagerFactoryImpl.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Truncated. see log file for complete stacktrace
Caused By: java.lang.OutOfMemoryError: allocLargeObjectOrArray: [Ljava/lang/Object;, size 782611408
at java.util.Arrays.copyOf(Arrays.java:2760)
at java.util.Arrays.copyOf(Arrays.java:2734)
at java.util.ArrayList.ensureCapacity(ArrayList.java:167)
at java.util.ArrayList.add(ArrayList.java:351)
at org.apache.openjpa.conf.CacheMarshallerImpl.setInputUrlFromResourceLocation(CacheMarshallerImpl.java:226)
Truncated. see log file for complete stacktrace
>
<May 6, 2011 2:12:46 AM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<May 6, 2011 2:12:46 AM PDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any pointers would be very helpful.I think your problem is here: Caused By: java.lang.OutOfMemoryError: allocLargeObjectOrArray: [Ljava/lang/Object;, size 782611408
And is probably related to this: http://mail-archives.apache.org/mod_mbox/openjpa-dev/201006.mbox/%3C26423199.85161276545675046.JavaMail.jira@thor%3E
the comment in here is saying: Make the CacheMarshallerImpl a bit more tolerant to different configurations.
Could be the out of memory error you getting is related to your openjpa configuration, not sure here -
Weblogic 10 doesn't start through admin console
Hi,
While starting a managed server on WebLogic 10.3 through the admin console I get the below error. However when starting the same managed server with a script I can successfully start it up.
<Sep 30, 2010 10:31:52 AM EEST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://10.123.456.78:7001.>
<Sep 30, 2010 10:31:52 AM EEST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Sep 30, 2010 10:31:52 AM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
Sep 30, 2010 10:31:55 AM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.
java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.
at weblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:40)
at weblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:35)
at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:105)
at weblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:60)
at weblogic.server.channels.ChannelService.start(ChannelService.java:197)
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)
java.net.UnknownHostException: myServer: myServer
at java.net.InetAddress.getLocalHost(InetAddress.java:1353)
at weblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:38)
at weblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:35)
at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:105)
at weblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:60)
at weblogic.server.channels.ChannelService.start(ChannelService.java:197)
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)
The environment had been up and running for many months, have done many successfull restarts occasionally. But after an ungraceful shutdown (database connection was down and managed server wouldn't shutdown through admin console) of the managed server & admin server, the startup through admin console stopped working. No configurations had been modified and we have two other systems working with similar configurations.
The log is stating that "<The admin server could not be reached at http://10.123.456.78:7001.>" but it actually is listening at that IP and port and I can connect to it with other means. I'm able to ping the hostname, IP, localhost etc... and network connection shouldn't be an issue even though the log states so.
Does anyone have any ideas what is broken? Thanks for any help in advance!Hi,
With script I meant the startManagedWebLogic.cmd script (on Windows). The managed server is running on the same machine as the admin server.
The hosts file has also been checked, it has the same content as two other environments which are working fine. But anyway we tried adding the IP & hostname there, but it didn't fix the issue. Nothing is wrong with the DNS either.
I'm also able to ping the address:port, with the command you gave I get the following result:
Sending 1 ping of 100 bytes.
RTT = ~0 milliseconds, or ~0 milliseconds/packet
When I'm trying to restart the managed server through admin console (on my laptop), I can see on the server side that there is a connection to the IP:port of admin server from my laptop's IP:
C:\>netstat -an | grep 7001
TCP 10.123.456.78:7001 0.0.0.0:0 LISTENING
TCP 10.123.456.78:7001 10.164.51.33:3965 ESTABLISHED
I again want to say that no changes have been done to any configurations in the environment. It was working fine before the "ungraceful" shutdown, where the connection to DB (that the managed server uses) was down and neither the managed or admin server would shutdown through admin console, but were shutdown by closing the cmd prompt window(used to start admin server) and java.exe task from taskmgr (managed server). -
In Admin Console We are unable to start Managed Server.
Hi,
We are using Weblogic 10.3.1.0 version.
Totaly 4 Managed Severs
1 Admin Server
with Nodemanger.
In Admin Console When ever we going to Stop the Manged Servers.
1. Environment ----- > Servers ---- > Control ----------- > Mananged Server 1 -----------> Force shutdown
2. Then click refresh button ---- showing "FAILED_NOT_RESTARTABLE"
3. after that when ever we going to start the Managed Server in Admin console
First its Showing ----- Starting
and next its showing ----- FAILED_NOT_RESTARTABLE
4. its not coming to Running State.
In Logs
Domain log
-----------> <1273141345460> <BEA-000450> <Socket 8 internal data record unavailable (probable closure due idle timeout), event received 17>
####<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280738> <BEA-000396> <Server shutdown has been requested by weblogic>
####<06-May-2010 11:54:40 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280771> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
####<06-May-2010 11:54:40 o'clock BST> <Notice> <Cluster> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280844> <BEA-000163> <Stopping "async" replication service>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281061> <BEA-000365> <Server state changed to ADMIN>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281064> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <Server> <ukirt156> <twpserver1> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <1273143281113> <BEA-002607> <Channel "Default" listening on 172.21.149.168:7003 was shutdown.>
####<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <ukirt156> <AdminServer> <[ACTIVE] ExecuteThread: '45' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273143390016> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
AdminServer log
<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
<06-May-2010 11:57:33 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
<06-May-2010 12:07:02 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
ManagedServer Log
<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler pause
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
<06-May-2010 11:54:54> <Debug> <NodeManager> <Waiting for the process to die: 19316>
<06-May-2010 11:54:54> <Info> <NodeManager> <Server was shut down normally>
<06-May-2010 11:54:54> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
NodeManager Log
<06-May-2010 11:54:54> <Info> <twp_domain> <twpserver1> <Server was shut down normally>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Boot identity properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Startup configuration properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/startup.properties">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00020">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Starting WebLogic server with command line: /appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/bin/java -Dweblogic.Name=twpserver1 -Djava.security.policy=/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.management.server=http://ukirt156:7001 -Djava.library.path="/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386/jrockit:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/../lib/i386::/appl/nsm/CA/UnicenterNSM/lib:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386/client:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386:/appl/nsm/CA/SharedComponents/ccs/dia/dna/lib:/appl/nsm/CA/SharedComponents/ccs/dia/lib:/usr/lib:/opt/CA/CAlib:/appl/nsm/CA/SharedComponents/lib:/appl/nsm/CA/SharedComponents/Csam/SockAdapter/lib:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/data/share/package/twp/WEB-INF/lib/ojdbc14.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.jar -Dweblogic.system.BootIdentityFile=/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xmanagement:port=7091,ssl=false,authenticate=false -Xms=1200m -Xmx=1200m -Xverbose:gc,gcpause -Dreflexis.scheduler=true -Dreflexis.server=twpserver1 -Djava.awt.headless=true -Dclient.encoding.override=UTF-8 -Doracle.jdbc.V8Compatible=true weblogic.Server >
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Working directory is "/appl/weblogic/scripts">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00021">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
<06-May-2010 11:56:29> <Info> <twp_domain> <twpserver1> <Server failed during startup so will not be restarted>
<06-May-2010 11:56:29> <Warning> <Exception while starting server 'twpserver1': 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:332)
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)
Server logs
<06-May-2010 12:06:57> <Info> <NodeManager> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
[INFO ][memory ] GC mode: Garbage collection optimized for throughput, initial strategy: Generational Parallel Mark & Sweep
[INFO ][memory ] heap size: 1228800K, maximal heap size: 1228800K, nursery size: 614400K
[INFO ][memory ] <s>-<end>: GC <before>K-><after>K (<heap>K), <pause> ms
[INFO ][memory ] <s/start> - start time of collection (seconds since jvm start)
[INFO ][memory ] <end> - end time of collection (seconds since jvm start)
[INFO ][memory ] <before> - memory used by objects before collection (KB)
[INFO ][memory ] <after> - memory used by objects after collection (KB)
[INFO ][memory ] <heap> - size of heap after collection (KB)
[INFO ][memory ] <pause> - total sum of pauses during collection (milliseconds)
[INFO ][memory ] run with -Xverbose:gcpause to see individual pauses
[JRockit] Management server started on port 7091, ssl=false, authenticate=false.
<06-May-2010 12:06:59 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.2-20_o-108500-1.6.0_05-20090120-1115-linux-ia32 from BEA Systems, Inc.>
<06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {AES}xvFgPysVi5b89pYwaAppoqPXQ5wFVW13yoFhzhKmuQo= from the file /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
<06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the password attribute value of {AES}WSsjiXk6ppStq4WFajxaXkqCwpcBwaMJni7vk/pqXvk= from the file /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
Enter username to boot WebLogic server:<06-May-2010 12:07:00 o'clock BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.1.0 Thu Jun 11 00:26:56 EDT 2009 1227385 >
<06-May-2010 12:07:01 o'clock BST> <Info> <Management> <BEA-141223> <The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.>
<06-May-2010 12:07:01 o'clock BST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<06-May-2010 12:07:01 o'clock BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<06-May-2010 12:07:02> <Debug> <NodeManager> <Waiting for the process to die: 19443>
<06-May-2010 12:07:02> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<06-May-2010 12:07:02> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Note: if i start the manged servers through WLST scripts its working fine.
[twpuser@ukirt156 /appl/weblogic/scripts]$ java weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
Connecting to Node Manager ...
Successfully Connected to Node Manager.
wls:/nm/twp_domain> nmStart('twpserver1')
Starting server twpserver1 ...
Successfully started server twpserver1 ...
Please provide the solution, how to solve this issue.
Thanks
SRKIn my question some content was strike.... now again i updated...pls see now...
Server logs
<06-May-2010 12:06:57> <Info> <NodeManager> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
[INFO ][memory ] GC mode: Garbage collection optimized for throughput, initial strategy: Generational Parallel Mark & Sweep
[INFO ][memory ] heap size: 1228800K, maximal heap size: 1228800K, nursery size: 614400K
[INFO ][memory ] <s>-<end>: GC <before>K-><after>K (<heap>K), <pause> ms
[INFO ][memory ] <s/start> - start time of collection (seconds since jvm start)
[INFO ][memory ] <end> - end time of collection (seconds since jvm start)
[INFO ][memory ] <before> - memory used by objects before collection (KB)
[INFO ][memory ] <after> - memory used by objects after collection (KB)
[INFO ][memory ] <heap> - size of heap after collection (KB)
[INFO ][memory ] <pause> - total sum of pauses during collection (milliseconds)
[INFO ][memory ] run with -Xverbose:gcpause to see individual pauses
[JRockit] Management server started on port 7091, ssl=false, authenticate=false.
<06-May-2010 12:06:59 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.2-20_o-108500-1.6.0_05-20090120-1115-linux-ia32 from BEA Systems, Inc.>
<06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {AES}xvFgPysVi5b89pYwaAppoqPXQ5wFVW13yoFhzhKmuQo= from the file /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
<06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the password attribute value of {AES}WSsjiXk6ppStq4WFajxaXkqCwpcBwaMJni7vk/pqXvk= from the file /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
Enter username to boot WebLogic server:<06-May-2010 12:07:00 o'clock BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.1.0 Thu Jun 11 00:26:56 EDT 2009 1227385 >
<06-May-2010 12:07:01 o'clock BST> <Info> <Management> <BEA-141223> <The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.>
<06-May-2010 12:07:01 o'clock BST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<06-May-2010 12:07:01 o'clock BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<06-May-2010 12:07:02> <Debug> <NodeManager> <Waiting for the process to die: 19443>
<06-May-2010 12:07:02> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<06-May-2010 12:07:02> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Note: if i start the manged servers through WLST scripts its working fine.
[twpuser@ukirt156 /appl/weblogic/scripts]$ java weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
Connecting to Node Manager ...
Successfully Connected to Node Manager.
wls:/nm/twp_domain> nmStart('twpserver1')
Starting server twpserver1 ...
Successfully started server twpserver1 ...
Please provide the solution, how to solve this issue.
Thanks
SRK -
Error start managed server from admin console in SSL mode
I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
<Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
<Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
<Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
<Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
<Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
<Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
<Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
<Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
I am running everything on IBM UNIX server.
I appriciate your help.
Thanks & regards,
Laxman.Hi
From the admin console ... Are you able to check the status of Node Manager ?
If yes ... please check the SSL configuration of managed servers ...
Check the domain administration port also.
Jin
Maybe you are looking for
-
I have Macbook Pro Retina and unlike the older Macbook Pro, my desktop display is not consistent in the picture display. The picture doesn't show the picture when I start the computer. I've also tried to do slideshow and it doesn't do that when I sta
-
I have many large (8 to 200 Meg) file size pdf's made up of images I need to make website links to. I can use them as is, but ended up buying Acrobat X Standard to help me make them smaller and more quickly accessible. I used Acrobat X to extract (
-
Encoding Error for Premier Elements 3.0, when downloading video to DVD
I have been using Adobe Premier Elements 3.0 for three years without any serious problems. However, when I try to download my latest edited video from my camcorder, to DVD, it hangs up every time at exactly the same place. It starts "ENCODING MEDIA".
-
CS5 Bridge and Photoshop not opening the CR2 files from my Canon 6D. Please help!
Any and all ideas would be appreciated greatly. Working on a deadline. Thank you so much!
-
Recover Print parameters from the Background popup for 3.1 I
How to recover the PRINT PARAMETERS (i.e. Printer name, new spool id) from the Background Popup window SAP version 3.1 I and I need use printer name in the program. Thanks in ADVANCE. you can contact me [email protected]