Any Guidelines on Configuring Weblogic 8.1 with Node Manager

Hi All, I want to configure Weblogic 8.1 with Node Manager using 4 ports. Is there any step by step guide? Please let me know...
Currently I am referring to this link:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/nodemgr.html
Thanks.

Hi,
Hope the below link may be little helpful: http://middlewaremagic.com/weblogic/?p=971
NOTE: you need not to follow Step8). mentioned in above link because.... WLS8.1 nmEnroll() is not available as part of WLST ...In WLS8.1 no need to start the NodeManager. You can also ignore the Clustering part in the above link ...rest all you need to follow.
Thanks
Jay SenSharma

Similar Messages

Hi any body having configuration material on Generic with holding tax

Hi SAP Guru's
Any body having configuration material on Generic with holding tax
Please help me on this because presently i am working UK porject when i am executing transaction code S_P00_07000134 getting no list genarated
Please give me some inputs
Regards,
satya

Hello abhijeeth,
Sent!! chk u r mail for the notes.
Regrads,
shashikanth,
Asssign points for usefull answer.

Weblogic 8.1 Enable Load Balancing with Node Manager

Hi All,
Please provide any guidelines on how to enable Load Balancing in Bea Weblogic 8.1
I have configured *1 Admin Server* with *4 Managed Servers* on a single machine each having different port.
I want to setup load balancing such that any 1 of 4 ports responds when a central URL is clicked by the user.
Any guidelines are welcome.

Review the document How to Implement Load Balancing on SAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver

Issue listeneing queue from Weblogic Cluster server with multiple managed server

Haveing issue listeneing queue from Weblogic Cluster server with multiple managed server.
Weblogic Cluster structure is like
Weblogic Cluster01
--ManagedServer01(http://server01.myhost.com:7001)
--ManagedServer02(http://server02.myhost.com:7001)
JMS Servers
JMSserver01 targeting: ManagedServer01
JMSserver02 targeting: ManagedServer02
JMSmodule
ConnectionFactory01 targeting:JMSserver01,JMSserver02
UDQueue01 targeting:JMSserver01,JMSserver02
Uniform Distributed Queue in Monitoring tab showing like this
mysystemmodule!JMSserver01@UDQueue01
mysystemmodule!JMSserver02@UDQueue01
So when I am sending message to any Host(by specifying the provider URL) its distributing equally on both server like
mysystemmodule!JMSserver01@UDQueue01 10
mysystemmodule!JMSserver02@UDQueue01 10
But when try to listen message from these queue, it is listening from one server, for which URL given to connect.
mysystemmodule!JMSserver01@UDQueue01 0
mysystemmodule!JMSserver02@UDQueue01 10
untill I connect to other server by giveing its URL, will not able to access other message left on the queue.
Solutions that tried
1) we have tried give both server URL coma sparated in provider URL
we need to configur same scenario for 5 managed server with 3 listener on other servers.
Do any one have solution for this.

You need to have:
1. Consumers connected to each UDQ member
OR
2. If no consumers in some of the members is expected, you can configure Forward Delay (specify the amount of time, in seconds, that a queue member with messages, but with no consumers, will wait before forwarding its messages to other queue members that do have consumers):
http://docs.oracle.com/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/distributed_queues/ConfigureUDQGeneral.html
For example you can set it to 10 (10s)
Additional Information here:
http://docs.oracle.com/cd/E23943_01/web.1111/e13727/dds.htm#i1314228
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13951/mbeans/DistributedQueueBean.html?skipReload=true#ForwardDelay
How Does JMS Load Balancing Work with Distributed Queues and Uniform Distributed Queues? (Doc ID 827294.1)
I hope this helps
Best Regards
Luz

[wls8.1 sp.3] cannot remote start with node manager on another server

In this domain run on 2 physical servers in windows 2003. In machine that has admin server can start with node manager but another machine without admin server cannot remote start . when i remote start , the node manager has facing error messages as below:
# AT "node manager monitoring" in weblogic admin console
[[NodeManager:300033]Could not execute command ping on the node manager. Reason: weblogic.nodemanager.NodeManagerException: [CommandInvoker: Failed to send command: 'ping to server 'null' to NodeManager at host: 'xxx.xxx.xxx.24:5555' with exception Connection reset by peer.. Please ensure that the NodeManager is active on the target machine].]
# AT "nodemanger.log" has facing error messages as below:
<Aug 20, 2008 7:34:07 PM ICT> <Info> <[email protected]:5555> <NodeManage r started, log messages being written into file C:\bea\WEBLOG~1\common\NODEMA~1\ NodeManagerLogs\NodeManagerInternal\nm_server02_08_20_2008-19_34_03.log>
<Aug 20, 2008 7:59:58 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - 10.208.50.23 during SSL handsha ke.> <Aug 20, 2008 8:00:11 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - xxx.xxx.xxx.23 during SSL handsha key.>
I would REALLY appreciate any suggestions as to what might be the cause or what i could try.
Thanks ....

Hi,
It is up to you to decide whether you want to use nodemanager or not.
It does not make any difference if the server is started via script or nodemanager.
if i want everything (AS, MS, and NM) to come up at server boot i need to set each of them up as windows services (which is what i have at the moment) but this wont allow me to use the node manager ==> Yes this statement is correct.
You can either set AS and MS as windows service (or) AS and nodemanager as service.
Thanks,
Sharmela

Health Monitoring and Restart Configuration with Node Manager

We have a WL 9.2.2 instance setup using Node Manager to control it. It contains a JMS server with a persistant store that is in an oracle database. If the Oracle database becomes unavailable, the Weblogic server throws a number of errors eventually leaving the Managed Server in a "FAILED" state. I configuring/activated the following "Configuration - Health Monitoring" options for the managed server to have it automatically recover from this situation:
Health Check Interval: 180
Auto Kill If Failed: Checked
Auto Restart: Checked
Max Restarts Within Interval: 2
Restart Delay Seconds: 0
However it is not automatically restarting, even though the server shows in a "FAILED" state.
1st question: Do I need to restart the server with the settings above to have it react to the FAILED state? I would think that 3 minutes after I configured the above it would begin a restart on the FAILED server, but that does not happen
I also note on the "Configuration - OverLoad" page, there is a setting for "Failure Action:" that can be set to "Ignore, take no action" or "Force Immediate Shutdown of this server" I did configure/activate this for "Force immediate Shutdown..." but again the currently FAILED server does not restart.
2nd question: Does this "Configuration - Overload- Failure Action" setting override or effect in any way the configuration of restart on the "Configuration - Health Monitoring" page?
3rd question: Same as 1st question but for these Overload settings: Do they require a full restart of the managed server to somehow take effect?


Have you set the field : CrashRecoveryEnabled=true in file : ..\bea\weblogic92\common\nodemanager\nodemanager.properties ?

Timezone issue with Node manager

Hi
We have a strange problem in our Weblogic manager server as below.
We started the manage server & Node manager in Jan 2011, when the daylight saving was on., then when time zone changed to winter time to summer time, node manager was unable to pick the time zone change.
It was still printing log files with wintertime in April 2011.
But after we restart the node manager & manage server, we found that then it has pick the summer time.
So want to know how to avoid such problems, that node manager & manage server should pick the current timezone (even when it change to summer to winter or vice versa) without restarting the servers.
Please can anyone guide me on this such strange problem & solution of it.
regards,
jay

Hi
My OS is Linux box and is able to pick the time correctly, but nodemanager & manage server which are started before time zone change is not able to pick the timezone change and continue running with timezone where it has started and the same time OS (date command) shows that it is changed to summer time.
Do i need to specify any configuration for nodemanger & manage server for picking the time when time zone is changed.
regards,
Jay
Edited by: user13160729 on May 23, 2011 11:07 PM

Not able to start SOA managed server first time with node manager by WLST

Hi all,
I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
In server log file I am getting the following error : -
Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
Can anyone please tell me what can be the issue?
Thanks in Advance!!!
Edited by: 008 on Dec 6, 2012 7:53 PM

Hi,
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
username=type-the-username-here
password=type-the-password-here
Cheers,
Vlad

Server stop problem with node manager

Hi ,
I get this error often when I try to stop a managed server via the nodemanager
from the admin console or from the weblogic.Admin command. The server does not
stop and it goes into an unknown state and I have to do a force shutdown
[java] Error: [Could not execute command shutdown for server xxx via the N e Manager
- reason: [__COMMAND_EXCEPTION__Request: failed to execute command ' utdown' on
server 'xxx - reason: '[Unable to send shutdown request to server.> ].]
[java] Start server side stack trace: [java] weblogic.nodemanager.NodeManagerException:
[Could not execute comman shutdown for server xxx via the Node Manager - reason:
[__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' on server 'xxx
- reason: '[Unable o send shutdown request to server.]'> ].] [java] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
gerRuntime.java:472) [java] at weblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method) [java]
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(D amicMBeanImpl.java:732)
[java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicM anImpl.java:714)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1557)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1525)
[java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

Hi Anil,
A little more information might be helpful. Which version are you talking
about ? What is the server state when you issue the command ? Is the server
very busy. Are you able to get the server state from the nodemanager when
the server is running ? Are you able to communicate from admin server ->
nodemanager <-> managed server ?
cheers,
gaurav.
"Anil Jacob" <[email protected]> wrote in message
news:3fb16b7c$[email protected]..
>
Hi ,
I get this error often when I try to stop a managed server via thenodemanager
from the admin console or from the weblogic.Admin command. The server doesnot
stop and it goes into an unknown state and I have to do a force shutdown
[java] Error: [Could not execute command shutdown for server xxx via the N
e Manager> - reason: [__COMMAND_EXCEPTION__Request: failed to execute command 'utdown' on> server 'xxx - reason: '[Unable to send shutdown request to server.> .]
[java] Start server side stack trace: [java]weblogic.nodemanager.NodeManagerException:
[Could not execute comman shutdown for server xxx via the Node Manager -
reason:> [__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' onserver 'xxx> - reason: '[Unable o send shutdown request to server.'> ].] [java] atweblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
gerRuntime.java:472) [java] atweblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method)[java]
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DamicMBeanImpl.java:732)
[java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicManImpl.java:714)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1557)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1525)
[java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

Starts servers with node manager

How to configure the node manager to start admin server and SOA services in the background in linux.

How to configure the node manager to start admin server and SOA services in the background in linux.

Steps to configure Weblogic 10.3 with SSL enabled Sybase 12.5

In WLS 10.3, there is a new feature for supporting the SSL encryption on Sybase 12.5.4.
I want to connect from Weblogic 10.3 to the SSL enabled Sybase 12.5.4.
Can any one please provide the step by step instructions for how to configure on the Weblogic 10.3? Do I need to create any custom class for this?
Thanks

Here is an example of connecting using the Sybase driver.
SybDriver sybDriver = (SybDriver)
Class.forName("com.sybase.jdbc3.jdbc.SybDriver").newInstance();
sybDriver.setVersion(com.sybase.jdbcx.SybDriver.VERSION_6);
DriverManager.registerDriver(sybDriver);
Connection conn = DriverManager.getConnection
("jdbc:sybase:Tds:<host>:5000?ServiceName=<dbname>",<user>,<passwd>);Not sure that the setVersion() call is absolutely necessary.

Configuring weblogic 6.1 with jbuilder4.

HOw can i configure weblogiv 6.1 sp1 with jbuilder 4.0.I tried changing enterprises server and properties as well, but nuthing happened.There are lots of messages related to this here but when i click on them, then the pop up says 'message not available on server'.
Thanks in advance

I have basically resigned to the fact that most ide's don't play well
with app servers and started using ant for all my projects. There are
plugins to use ant for most ide's, and it is cross-platform compatible.
This may hamper some of your debugging efforts, but there is usually a
workaround for that. At least deployment isn't a complete headache, and
everything is consistent.
http://jakarta.apache.org/ant
Just a suggestion. It works for me.
Nic
Harry wrote:
HOw can i configure weblogiv 6.1 sp1 with jbuilder 4.0.I tried changing enterprises server and properties as well, but nuthing happened.There are lots of messages related to this here but when i click on them, then the pop up says 'message not available on server'.
Thanks in advance

Configuring weblogic's internal webserver for clustering

Hi
          I have created a weblogic cluster running on 9001. The cluster has 2 managed servers running on 8001 and 8003. I can access the application depolyed on the cluster by using http://localhost:8001/Appname & http://localhost:8003/Appname.
          I was wondering if there is any way to configure weblogic internal webserver to actually use the cluster. I don't want to use external webservers like Apache etc , because I don't have enough memory in my machine.
          I can't see any document describing this in bea website, Can somebody help please?
          Vijay

There is no way you can avoid additional memory usage(unless you have hardware loadbalancer that is configured to route request to the weblogic cluster).
          If you do not want to use other webservers, you can always use HttpClusterServlet as proxy mechanism to cluster.
          All you need to do is create another managed server and host the httpclusterservlet webApp on that managed server.
          (you can host the HttpClusterServlet on admin server itself but its not recommended approach though)
          Look at http://e-docs.bea.com/wls/docs81/cluster/setup.html#684345

To manage coherence JVM's from weblogic server node manager

we have configured weblogic server node managers on weblogic admin console and want to add multiple coherence JVM on node manager to manage multiple coherence server JVM's. we have configured mode manager on each computer that hosts the Coherence server instance that we want to control with Node Manager. Is it possible to spawn multiple JVM's using the node manager which has been installed on each weblogic machines.

I was able to start the server but while passing the tangosol parameters as arguments we are getting below errors.
Console encountered the following error weblogic.management.provider.UpdateException: [Management:141191]The prepare phase of the configuration update failed with an exception: at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateDeploymentContext(RuntimeAccessDeploymentReceiverService.java:670) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:28) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:112) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52) at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211) at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:457) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) Caused by: weblogic.management.ManagementException: Must import new custom cluster configuration file for Coherence-1. at weblogic.management.mbeans.custom.CoherenceClusterSystemResource.setUsingCustomClusterConfigurationFile(CoherenceClusterSystemResource.java:149) at weblogic.management.configuration.CoherenceClusterSystemResourceMBeanImpl.setUsingCustomClusterConfigurationFile(CoherenceClusterSystemResourceMBeanImpl.java:354) 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 com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48) at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:539) at com.bea.staxb.runtime.internal.MultiIntermediary.setValue(MultiIntermediary.java:82) at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType$ElementQNameProperty.fill(ByNameRuntimeBindingType.java:348) at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:159) at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51) at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:48) at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184) at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156) at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51) at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:48) at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199) at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169) at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65) at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150) at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleConfigTreeLoad(RuntimeAccessDeploymentReceiverService.java:967) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateDeploymentContext(RuntimeAccessDeploymentReceiverService.java:599) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:29) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:114) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52) at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211) at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:458)
Please let me know if anyone has come across this error and got any solution for it.

Problem with starting managed server

In a domain , I have one admin server and one managed server. When im trying to start managed server , the message says,
Message icon - Warning For server Server-0, the Node Manager associated with machine Machine-0 is not reachable.
Message icon - Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
Already i started the node manager , i checked with node manager's log files, and I found these error in log files,
<Jul 30, 2010 12:54:32 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
 at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
 at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
 at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
 at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
 at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
 at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
 at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
 at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
 at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
 at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
 at com.certicom.tls.record.ReadHandler.read(Unknown Source)
 at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
 at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
 at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
 at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
 at java.io.InputStreamReader.read(InputStreamReader.java:167)
 at java.io.BufferedReader.fill(BufferedReader.java:136)
 at java.io.BufferedReader.readLine(BufferedReader.java:299)
 at java.io.BufferedReader.readLine(BufferedReader.java:362)
 at weblogic.nodemanager.server.Handler.run(Handler.java:66)
 at java.lang.Thread.run(Thread.java:619)
Can any one help me to troubleshoot this.

Hi Jose,
To Disable SSL communication for NodeManager do the following:
Step1). Open the *"nodeManager.properties"* file from *<WL_HOME>\common\nodemenager* (Example Location : C:\bea103\wlserver_10.3\common\nodemanager ) directory and change the value of SecureListener property to false:
SecureListener=false
Step2). Login to AdminConsole and then
AdminConsoleHome--->Machines --><Your_MachineName> (Click here)--->NodeManager (Tab)---> Select the type as "Plain" from the combo box (by default it will be SSL)
Step3). Restart the NodeManager ....better if you follow Step4) as well...
Step4). Please Enroll your NodeManager as described in the Step8) of the following Link: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/
Thanks
Jay SenSharma

Any Guidelines on Configuring Weblogic 8.1 with Node Manager

Similar Messages

Maybe you are looking for