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.

Similar Messages

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:54

hi,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

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,
Ajmal

Hi 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

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

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.

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)

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

Unable to start Managed server from admin console using nodemanager

I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.

Hi there,
Can you check the following configuration in Weblogic admin console ?
1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
Thanks
Lakshman

Unable to start Managed servers from admin console

Hello!
We have a problem to start Managed Servers throw Node manager.
We get an error:
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Additional information:
weblogic 10.3.3
PT8.51.11
Linux x86_64 RH5
When we starting Manged servers manualy, it's works fine.
Thank you.

Hello!
The problem is found.
We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
<Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
There are no errors in managed servers logs.
PIA1.out:
<Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Attempting to start WebLogic Server PIA1
No activity will be logged to this window.
Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
PID for WebLogic Server PIA1 is: 27018
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
<Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
What can be the reason?
Thank you.

WC_Spaces Managed server not showing up in AdminServer

I am trying to install the webCenter spaces managed server. I installed the schema to database and extended my existing domain with the spaces product and I have all the products that you have to install with it, but when I start the admin server the spaces managed server is not showing up. I created a new domain and put space on that one and when i start the new domains admin server is see the WC_Spaces managed server. Why is it not showing up on my existing domain?

Hi,
By default any managed server will not be up we need to start them by help of Nodemanager or by standalone using script called startManagedWebLogic.sh or cmd file.
when you try to start Managed server from Admin Console then try to enable to Machine for the Managed server where Machine will configure Nodemanager details. Start Nodemanager then in Monitoring of Nodemanager under Machine will show Reachable.
Then we are able to start Managed server through Admin Console.
If you dont want to start through Nodemanager then use following command.
Under Domain_Home / bin / folder
you will find startManagedWebLogic.sh file in Unix and .cmd file in Windows.
Now you following command ./startManagedWebLogic.sh t3://<AdminServer URL >:<Admin Port>
This will help to start Managed server.
Note: Make sure that you have security folder under managed server and provide boot.properties with username and password so that it can encrypted once it get started or else every time we need to provide username and password at startup.
Regards,
Kal

Error while starting ManagedServer from admin console.

HI,
can any one please help me on the below error.
i got the below error when i tried to start managedserver from admin console. and below are the steps i have done before start the manages server.
1. started admin server.
2. started nodemanager from C:\bea\wlng400\server\bin\startNodeManager.cmd
3. started managed server from the admin console.
managed server name is "QualcommServer"
Error from QualcommServer.out file is :
<Apr 27, 2009 4:46:37 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.ClassNotFoundException: com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean>
Below is config.xml file which i am using:
<jms-server>
<name>JMSServer-AdminServer</name>
<target>AdminServer</target>
</jms-server>
<jms-system-resource>
<name>WLNGJMSResource</name>
<target>AdminServer</target>
<descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
</jms-system-resource>
<custom-resource>
<name>networktier</name>
<target>QualcommServer</target>
<descriptor-file-name>custom/nt.xml</descriptor-file-name>
<resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngTierResource</resource-class>
<descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean</descriptor-bean-class>
</custom-resource>
<custom-resource>
<name>wlng-edr</name>
<target>QualcommServer</target>
<descriptor-file-name>custom/wlng-edr.xml</descriptor-file-name>
<resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngEdrResource</resource-class>
<descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngEdrBean</descriptor-bean-class>
</custom-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>wlng.datasource</name>
<target>QualcommServer</target>
<descriptor-file-name>jdbc/wlng-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>wlng.localTX.datasource</name>
<target>QualcommServer</target>
<descriptor-file-name>jdbc/wlng-localTX-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
Thanks,
Srinu Babu P

This classs is usually found in server\lib\wlng\wlng-management.jar, make sure it has that class and that jar is getting loaded by the server.

Configure custom application properties from admin console on 10gR3

Is there a way to promote a property in an application, deploy that application EAR to weblogic server 10gR3 and configure the property from admin console?
E-g: creating two properties loggingEnabled, logLevel in an application and based on the needs configure logging from server admin console.

You have to write your own management mbean,
Examples can be found here:
- http://blogs.oracle.com/WebLogicServer/2009/10/developing_custom_mbeans_to_ma.html
- http://blogs.oracle.com/WebLogicServer/2009/11/developing_custom_mbeans_to_manage_j2ee_applications_part_ii.html
- http://blogs.oracle.com/WebLogicServer/2010/03/developing_custom_mbeans_to_ma_1.html
Good luck

Can't start CMS 4.7 from admin console

I can't start cms instance from admin console. When i try to start it says "operation error: unable to start the server". I tried to start the server from command line, it seems ok, so when i back to admin console and try to open CMS, it says "server off" and the server was already started from command line successfully.
DOES ANYONE KNOW WHAT HAPPENS???
thanks,
Marcelo

Hi, did you manage to solve the problem mentioned here...i'm having the same problem now.
Br

What web service & xml will be used for deleting the packged epub/pdf file from Admin Console

What web service & xml will be used for deleting the packged epub/pdf file from Admin Console?
I am able to delete the files from Admin console directy but not able to get which web service is calling on deleting the file from admin console:
Mangal

Hi Jim,
I tired following web service and xml to delete the packaged ebook but it is giving me error instead of response:
Web Service & XML
http://myserver_url/admin/ManageResourceKey
<request action="delete" auth="builtin" xmlns="http://ns.adobe.com/adept">
<nonce>" . $nonce . "</nonce>
<expiration>'. $expiration .'</expiration>
<resourceKey>
<resource>resource_id</resource>
<resourceItem>1</resourceItem>
</resourceKey>
</request>
Error Message
<error xmlns="http://ns.adobe.com/adept"
data="E_ADEPT_DATABASE http://myserver_url/admin/ManageResourceKey
Cannot%20delete%20or%20update%20a%20parent%20row:%20a%20foreign%20key%20constraint%20fails %20(`adept`.`distributionrights`,%20CONSTRAINT%20`distributionrights_ibfk_2`%20FOREIGN%20K EY%20(`resourceid`)%20REFERENCES%20`resourcekey`%20(`resourceid`))"/>
Magal Varshney

MANAGED SERVER NOT COMMING UP FROM ADMIN CONSOLE,

Similar Messages

Maybe you are looking for