• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Clustering on Weblogic 8.1 on standalone windows machine

 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
kindly help in confugring and deployment of Clustering application on Weblogic 8.1 on standalone windows machine.

regards
Faisal
 
Bartender
Posts: 9626
16
Mac OS X Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Setting up Weblogic Clusters
 
faisal khan
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i have go through the link and setup admin server and two managed(cluster) servers. i also update running-managed-servers.xml file and add two managed servers. i also start Node Manager as a window service.

the problem is that when i start one of the managed server it will throw exception that NodeManager will not listen devserver9933(managed server).
 
Joe Ess
Bartender
Posts: 9626
16
Mac OS X Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've only set up NodeManager on Unix servers so I'm not sure of any windows-specific issues. The easy stuff to check would be to make sure that NodeManager's listening to the same port you've configured your servers to hook up to. I've had SSL issues between servers and NodeManager. Do you have your own cert?
 
faisal khan
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i had also setup cluster on IBM AIX.
But on standalone window machine i have found some exception during startup of managed server shown below.

From Console to start cluster server
weblogic.nodemanager.NodeManagerException: [Failed to complete the request to start the server devServer9922 of domain devdomain in state RUNNING]
at weblogic.nodemanager.client.CommandInvoker.execute(CommandInvoker.java:233)
at weblogic.nodemanager.client.CommandInvoker.invoke(CommandInvoker.java:91)
at weblogic.nodemanager.client.NodeManagerClient.executeCommand(NodeManagerClient.java:161)
at weblogic.nodemanager.client.NodeManagerExecuteRequest.execute(NodeManagerRuntime.java:1641)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)


From startManagedServer.cmd
####<Oct 23, 2006 7:18:30 PM PKT> <Info> <Deployer> <cdc-a2feb6fa6ae> <devServer9922> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<Oct 23, 2006 7:18:30 PM PKT> <Error> <Cluster> <cdc-a2feb6fa6ae> <devServer9922> <main> <<WLS Kernel>> <> <BEA-000116> <Failed to join cluster devCluster at address 239.192.0.0 due to: java.net.SocketException: error setting options.
java.net.SocketException: error setting options
at java.net.PlainDatagramSocketImpl.join(Native Method)
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:169)
at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:43)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:924)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
>
####<Oct 23, 2006 7:18:30 PM PKT> <Critical> <WebLogicServer> <cdc-a2feb6fa6ae> <devServer9922> <main> <<WLS Kernel>> <> <BEA-000364> <Server failed during initialization. Exception:weblogic.server.ServerLifecycleException: Failed to listen on multicast address
weblogic.server.ServerLifecycleException: Failed to listen on multicast address
at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:48)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:924)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
Caused by: java.net.SocketException: error setting options
at java.net.PlainDatagramSocketImpl.join(Native Method)
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:169)
at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:43)
... 4 more
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic