Weblogic quickstart cluster wizard

Hello,
In Weblogic quickstart, cluster wizard what should one write in "cluster address" ?
Given:
Name: cluster1
Cluster messaging mode: unicast
Cluster address:
What should I write in cluster address ? A virtual IP that weblogic will fail over across cluster Machines when there is a failure ?
thanks for any explanation.

Hi,
Cluster Address : It's the Comma Separated List of all those Member Managed Servers, which we want to add as Part of the Cluster.
Example: Suppose in a Cluster-A i want to add two Managed Servers
MS-1 10.10.19.126:7005
MS-2 10.10.19.130:7009
Then Cluster Address will be: *10.10.19.126:7005,10.10.19.130:7009*
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

Similar Messages

JMS messages stuck in queue in weblogic v923 cluster

Hi all,
Enviornment details:
In our pre-production weblogic v923 cluster enviornment with Oracle 10g database, there are 10 server boxes with 2 managed nodes running on each server box in linux enviornment.
There are 3 JMS queues and 1 error queue per managed node.
All the queues are durable and the persitence store is a database table. There is a single database table per single managed node.
High loads of JMS messages from client applications coming on each of the 3 JMS queue are processed by the cluster on daily basis.
The JMS messages that failed to be processed the very first time due to the application logic exceptions are put on error queue since the retry is set to zero on the non-error queue.
The application exceptions are logged to a database table for futher reference.
The falied messages from the error queue are read by spring based MDP and resent to the application for reprocessing.
If no application exceptions, the message will be persisted in a relational database; in the case of failures, MDP code puts the failed message back on to the error queue.
The auto_ack is true on the JMS message.
It is observed about less than 1% of the messages fail the original processing and are in error queue on daily basis.
99.9% of the time, the reprocessing of the messages from the error queue is a success.
Currently due to some obvious reasons, the system administrator stops a managed node when the disk is full and start a different managed node on the same server box. This approach will be stopped in the very near future so that all nodes on all servers are running at any point of time by making few enviornment changes.
Problem:
1a) Occasionally, it is observed that 1 - 4 JMS messages are stuck in the error queue. There are no signs of reprocessing as there are no application exceptions or the corresponing insert into the database. The JMS persistence store table still has the JMS message.
1b) It is observed that over time, the same JMS messages that were originally stuck on server 1's managed node A are no longer there but are found in a different node (say node B) on a different server box.
As far as I understand the JMS, a message could be in a Pending state if MDP (in my case) does not automatically send ACKNOWLEGMENT back due to an issue in the Spring Defaultlisternercontainer before calling MDP's onMessage(). I am not sure as what happens to that status over time).
It is also observed that the stuck messages content is not much different than the other messages that are processed fine.
Any pointers/input is highly appreciated.
Thanks in advance for your valuable input and time.

Off the top of my head, I can only think of two reasons why a message might move from node to node:
(A) An application is dequeueing them and enquening them elsewhere.
(B) The application is using distributed queues, and the distributed queue has been configured to enable "queue forwarding". The forwarding feature automatically moves messages from distributed queue members that have no consumers to members that do have consumers. Queue forwarding is sometimes enabled as a work-around to better enable MDP support of WL distributed destinations, unlike WebLogic MDBs, MDPs have no container logic to ensure that all members of a distributed destination are serviced by a consumer under all circumstances...
Regards,
Tom

Starting Weblogic Server Cluster remotely via VPN

We have a site-to-site VPN setup from our office to our ISP so we can
          control our system remotely. We can stop our Weblogic servers (in a
          cluster) remotely via the VPN no problem via the "stopweblogic.cmd" command
          where we just change the IP address of our remote server. We're having
          trouble starting them through the WebLogic console applet. We can bring the
          applet up & running, but no luck starting them.
          Is there another way to start your weblogic servers (besides using something
          like PC Anywhere).
          Or is there any documentation that could point to an answer here?
          Any suggestions?
          Mike Kendzierski
          B2BGalaxy.com


1. "myserver" is the name of the server. It doesn't want the name of the
machine the server is on.
2. It is possible that something is wrong in the license file. I've made a
typo when changing the license on my server that prevented weblogic from
starting.
Hope this helps.
"Hilmar" <[email protected]> wrote in message
news:[email protected]..
>
When I start WebLogic server using startweblogic.cmd everything seems tobe okay.
Using the 'Start a new WebLogic server or cluster' command from WebLogicConsole
5.1.0, I get the following error message:
Attempting to start server on the machine running the console using
C:\weblogic\jre1_2\jre\bin\java.exe -mx32m -ms32m -classpath"C:\weblogic\jre1_2\jre\lib\rt.jar;C:\weblogic\jre1_2\jre\lib\i18n.jar;C:\we
blogic\lib\i18n.jar;C:\weblogic\classes\boot;C:\weblogic\eval\cloudscape\lib
\cloudscape.jar"
-Dweblogic.class.path=C:\weblogic\license;C:\weblogic\classes;C:\weblogic\myserver\serverclasses;C:\weblogic\lib\weblogicaux.jar
-Dweblogic.system.discardOutAndErr=true -Djava.security.manager -Djava.security.policy==C:\weblogic\weblogic.policy
-Dweblogic.system.name=kenapp00111 -Dweblogic.system.home=C:\weblogic -Dweblogic.cluster.enable=false
-Dweblogic.cluster.name=mycluster -Dweblogic.system.listenPort=7001 -Dweblogic.system.SSLListenPort=7002
-Dweblogic.cluster.multicastAddress=237.0.0.1 weblogic.Server
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Loaded License : C:/weblogic/license/WebLogicLicense.xml
However Unable to start because :
No License found for WebLogic
As well as the fact that: No License found for Tengah
As well as the fact that: No License found for WebLogic/JDBC
As well as the fact that: No License found for Tengah/JDBC
As well as the fact that: No License found for jdbcKona/T3
Is the 'server name' the name of the machine or 'myserver' ? Could therereally
be something wrong with the licence file ?
Thanks for helping !
Hilmar

Create Cluster Wizard in SCVMM 2012 doesn't have IP Address page

i installed the SCVMM 2012 version 3.0.6019.0.
When i use the Create Hyper-V Cluster under Fabric page to create a Cluster.
the Create Cluster Wizard doesn't have the IP Address page to let me input the IP for the Cluster.
after i answer all the wizard, the Install Cluster job shown Error 25325
The cluster creation failed because of error At least one IP address needs to be configured..
so, how to solve it?
thanks alot.

Old thread..
But I got the same problem creating a cluster on SCVMM 2012 R2. To get around it I instead created the cluster using powershell and it worked great:
$HostName1 = "HOST01"
$HostName2 = "HOST02"
$Clustername = "CLUSTER01"
$ClusterIP = "192.168.1.50"
$VMMRunAsAccount = "VMM_AdminAccount"
$credential = Get-SCRunAsAccount -Name $VMMRunAsAccount
$hostsList = @()
$hostsList += Get-SCVMHost -Computername $HostName1
$hostsList += Get-SCVMHost -Computername $HostName2
Install-SCVMHostCluster -ClusterName $Clustername -VMHost $hostsList -RunAsynchronously -Credential $credential -ClusterIPAddress $ClusterIP
_____________________________________ /Michael R

Server1 canot start on weblogic integration cluster

I can not start server1 on weblogic integration cluster, out and logs are:
<> <1345403377689> <BEA-000000> <Error in startup class com.bea.wli.management.configfile.ConfigFileManager Method: initialize:
java.lang.AssertionError: MBeanHome lookup failedjavax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.adminhome'. Resolved 'weblogic.management';
remaining name 'adminhome'
at weblogic.management.Admin.lookupMBeanHome(Admin.java:245)
at weblogic.management.Admin.getAdminMBeanHome(Admin.java:260)
at com.bea.wli.management.MBeanHelper.getMBeanHome(MBeanHelper.java:161)
at com.bea.wli.management.configfile.RepAgent.init(RepAgent.java:116)
at com.bea.wli.management.configfile.RepAgent.<init>(RepAgent.java:100)
at com.bea.wli.management.configfile.ManagedRepAgent.<init>(ManagedRepAgent.java:83)
at com.bea.wli.management.configfile.ManagedConfigFileManager.<init>(ManagedConfigFileManager.java:53)
at com.bea.wli.management.configfile.ConfigFileManager.initialize(ConfigFileManager.java:101)
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.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:488)
at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:287)
at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
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.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:353)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:263)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:198)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:177)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppActivation(ClassDeploymentManager.java:151)
at weblogic.management.deploy.internal.DeploymentAdapter$4.activate(DeploymentAdapter.java:163)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Aug 19, 2012 4:09:37 PM BRT> <Critical> <WebLogicServer> <adriana> <server1> <Main Thread> <<WLS Kernel>> <> <> <1345403377696> <BEA-000362> <Server failed. Reason
There are 1 nested errors:
java.lang.AssertionError: MBeanHome lookup failedjavax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.adminhome'. Resolved 'weblogic.management';
remaining name 'adminhome'
at weblogic.management.Admin.lookupMBeanHome(Admin.java:245)
at weblogic.management.Admin.getAdminMBeanHome(Admin.java:260)
at com.bea.wli.management.MBeanHelper.getMBeanHome(MBeanHelper.java:161)
at com.bea.wli.management.configfile.RepAgent.init(RepAgent.java:116)
at com.bea.wli.management.configfile.RepAgent.<init>(RepAgent.java:100)
at com.bea.wli.management.configfile.ManagedRepAgent.<init>(ManagedRepAgent.java:83)
at com.bea.wli.management.configfile.ManagedConfigFileManager.<init>(ManagedConfigFileManager.java:53)
at com.bea.wli.management.configfile.ConfigFileManager.initialize(ConfigFileManager.java:101)
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.wli.init.BPMStartupShutdown.invoke(BPMStartupShutdown.java:488)
at com.bea.wli.init.BPMStartupShutdown.startup(BPMStartupShutdown.java:287)
at com.bea.wli.init.BPMStartup.main(BPMStartup.java:23)
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.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:353)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:263)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:198)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:177)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppActivation(ClassDeploymentManager.java:151)
at weblogic.management.deploy.internal.DeploymentAdapter$4.activate(DeploymentAdapter.java:163)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

Hi Alex,
That's weird, I have WLI installed here in some of the servers, but there is no ConfigFileManager startup class...
Go to the config.xml file and comment out all startup and shutdown classes and see if that helps to start the server at least... You may have to reinstall WLI though...
Hope this helps...
Cheers,
Vlad

Failover Cluster Wizard Fails

I am trying to create a cluster with two Windows Server 2012 nodes on an existing domain where the domain controller is Windows 2003, and the wizard fails with the message:
Set password on (ClusterName). There are currently no logon servers available to service the logon request.
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait..
There was an cleaning up the cluster node. Use Clear-ClusterNode to manually clean up the nodes.

I found the reason. The port 464 TCP and UDP were blocked by windows 2003 firewall. Windows server 2012 by default leaves these ports open, but you should manually open them on windows server 2003.

Weblogic.rmi.cluster.CallRouter, how to place classes?

Hi,
I,m using Weblogic 7.0. I want a class to be loaded on different cluster servers
depending on an argument.
I've defined a remote interface for the class, the class implementation that implements
that remote interface, and a class that implements the CallRouter interface to
decide what cluster should be used depending on an argument sent to one function
from the class implementation.
After that, I've compiled those 3 classes using java weblogic.rmic -clusterable
-callRouter <callRouterClass> <remoteObjectClass>
It just has created two ---RTD.XML files. My application is outspread as we are
still developing. It's not using WAR or EAR files yet, but we have our web.xml
and application.xml files.
Am I following steps correctly? If so, where should I put the classes and xmls
in the server? Should they all be in the classpath and that's all? If not, what
more should I do, create a jar with 3 classes and xmls? How?

One last question. How should I call the class from client code?
"Ignacio Sanchez" <[email protected]> wrote:
>
Hi,
I,m using Weblogic 7.0. I want a class to be loaded on different cluster
servers
depending on an argument.
I've defined a remote interface for the class, the class implementation
that implements
that remote interface, and a class that implements the CallRouter interface
to
decide what cluster should be used depending on an argument sent to one
function
from the class implementation.
After that, I've compiled those 3 classes using java weblogic.rmic -clusterable
-callRouter <callRouterClass> <remoteObjectClass>
It just has created two ---RTD.XML files. My application is outspread
as we are
still developing. It's not using WAR or EAR files yet, but we have our
web.xml
and application.xml files.
Am I following steps correctly? If so, where should I put the classes
and xmls
in the server? Should they all be in the classpath and that's all? If
not, what
more should I do, create a jar with 3 classes and xmls? How?

Error received when running weblogic in cluster

I am trying out clusters to see what the benefit would be to our application but I keep getting an error in the background. I have obtained a test cluster license and it is loading it up on startup. Does anyone know what this error is or how to fix it? Thanks for the help.
<Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>

I am trying out clusters to see what the benefit would be to our application but I keep getting an error in the background. I have obtained a test cluster license and it is loading it up on startup. Does anyone know what this error is or how to fix it? Thanks for the help.
<Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>

Weblogic 12c cluster and EJB 3.1 timers

Hello!
I'm using Weblogic 12c (12.1.1.0) Cluster.
I configured the cluster to use database for EJB timers (ACTIVE and WEBLOGIC_TIMERS tables). I created a persistence store with logical name 'timerst'.
The timer bean:
@Stateless
public class TimerTestBean {
     private Logger logger = Logger.getLogger(TimerTestBean.class);
     @Resource
     TimerService timerService;
     public void settimer() {
          logger.info("settimer");
          timerService.createTimer(30000, "New timer");
     @Timeout
     public void zszszszs(Timer arg0) {
          logger.info("Tick");
          settimer();
weblogic-ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-ejb-jar xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-ejb-jar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://xmlns.oracle.com/weblogic/weblogic-ejb-jar http://xmlns.oracle.com/weblogic/weblogic-ejb-jar/1.3/weblogic-ejb-jar.xsd">

<wls:weblogic-enterprise-bean>
<wls:ejb-name>TimerTestBean</wls:ejb-name>
<wls:stateless-session-descriptor>
<wls:timer-descriptor>
<wls:persistent-store-logical-name>timerst</wls:persistent-store-logical-name>
</wls:timer-descriptor>
</wls:stateless-session-descriptor>
</wls:weblogic-enterprise-bean>
<wls:timer-implementation>Clustered</wls:timer-implementation>
</wls:weblogic-ejb-jar>
It seems the timer starts normally.
When there timer fires, I've got the following error message:
java.lang.ClassCastException: timertest.TimerTestBean_9kqf6o_Impl cannot be cast to javax.ejb.TimedObject
What is wrong?
Thanks
Balazs
Edited by: 892403 on 2013.02.19. 10:43
Edited by: 892403 on 2013.02.19. 10:44

Issues have been found with @Schedule and @Timeout annotations in WLS clustered timer implementation.
The problem is fixed with 12.1.2 WLS version. Patch exists for 12.1.1.0 version.
Please download and apply Patch 13417115 from Oracle Support Portal.
Thanks,
Vijaya

Weblogic production cluster: how to configure it for ADF, ADF Faces, BC?

Given a production ready cluster of Weblogic 10.2. What should I do to convert it an ADF ready weblogic server ? How to make it as usable for ADF as the integrated weblogic in jdeveloper?
any official guide from Oracle ?
thanks,
fabio

For WLS 11g (aka 10.3.x) you must install the Application Development Runtime (get it from here http://www.oracle.com/technology/software/products/middleware/htdocs/fmw_11_download.html) and extend your existing domains.
Check the Installation Guides first: http://download.oracle.com/docs/cd/E14571_01/install.htm
--olaf

Weblogic JMS Cluster

Hi,
          I have a 6.1 cluster that has a JMS server A and a JMS Server B
          deployed and running on each of the managed nodes. As destination I
          created a topic with the same name for each JMS Server. The connection
          factories I deployed to the cluster only.
          My problem is, when I start the second managed server, I get the
          following error:
          <Error> <Cluster> <Conflict start: You tried to bind an object under
          the name
          com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
          have bound
          from 169.59.5.26 is non clusterable and you have tried to bind more
          than once
          from two or more servers. Such objects can only deployed from one
          server.>
          When I understand correctly, this happens because the JNDI tree gets
          distributed to all nodes of the cluster, so there would be two object
          with the same name. How do I solve this situation? Do I have the
          specify different names for topics in different JMSServer running in a
          cluster? How would the load balancing work?
          Please help. Thanks in advance
          Juerg


Tom,
          Thanks for your help so far, I installed the patch and got things
          working. However I still have some open points where you might be able
          to help.
          Let's assume I don't have these smart forwarders and I have four
          topics per JMSServer deployed to two managed nodes. Connection
          factories deployed to the cluster. When I connect N publishers
          through the cluster, messages from one publisher end up in the
          appropriate topic on nodeA, messages from another publisher end up in
          the appropriate topic on nodeB. Now when I connect a durable
          subscriber via the cluster I only get messages from topics from one of
          the managed nodes, right? (This is exactly what I am seeing in my
          tests) Connecting durable subscribers to each managed node is not
          possible because of JNDI (throws exception like
          InstanceAlreadyExists). How would I connect a subscriber so that it
          subscribes to the right topics on the right node ( one the works with
          the previously described publisher)?
          All this leads me to the conclusion, that without the forwarders, a
          JMS cluster with Weblogic 6.1 is not so powerful, it basically does
          just load balacing.
          Is this correct or am I missing something important here?
          Thanks a lot and have a nice weekend
          Juerg
          Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
          > Juerg Staub wrote:
          > > Tom,
          > >
          > > Thanks a lot. Bascially I did everything right, just need the patch.
          > >
          > > In the other hand I'd like to know what the benefits of the smart
          > > forwarders would be. When I understand correctly, every message would
          > > be forwarded to the appropriate topic in the different JMS servers.
          > > What would that bring in the case of a failure(one node of a cluster
          > > goes down)? As far as I can see, I still would need to 're-establish'
          > > the connection factory, topic session, topic and publisher in order to
          > > publish messages again?
          > >
          >
          > Yep. I think we are on the same page:
          >
          > The "smart-forwarders" would do what the 7.0 distributed topic
          > forwarders do for you. They would forward messages bound to
          > a particular physical topic to all instances of the topic.
          > This can be implemented via a durable subscription on a
          > member topic by each remote member topic's host.
          > MDBs could be used to service the durable subscription,
          > as they already have the reconnect logic built in.
          > (Durable subscriptions are used if you wish to guard against
          > lost messages). The forwarders
          > need to change a property on the message to indicate
          > that the message is already forwarded, and forward
          > only messages that have'nt been forwarded (to prevent
          > endless loops!).
          >
          >
          > > Thanks
          > >
          > > Juerg
          > >
          > > Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
          > >
          > >>I suggest you read the "emulating 7.0 distributed destinations"
          > >>section of the JMS performance white-paper available on dev2dev.bea.com.
          > >>You will need to apply the referenced enhancement patch on top of SP3 to
          > >>disable JNDI replication (or update to 6.1SP4).
          > >>
          > >>If you need to create a true distributed topic, you will also need to
          > >>write your own "smart-forwarders" to forward messages
          > >>between the different physical instances of the topic. Or simply
          > >>use WL JMS 7.0 (the upgrade from 6.1 is straight-forward).
          > >>
          > >>Tom
          > >>
          > >>Juerg Staub wrote:
          > >>
          > >>>Hi,
          > >>>
          > >>>I have a 6.1 cluster that has a JMS server A and a JMS Server B
          > >>>deployed and running on each of the managed nodes. As destination I
          > >>>created a topic with the same name for each JMS Server. The connection
          > >>>factories I deployed to the cluster only.
          > >>>
          > >>>My problem is, when I start the second managed server, I get the
          > >>>following error:
          > >>>
          > >>><Error> <Cluster> <Conflict start: You tried to bind an object under
          > >>>the name
          > >>>com.csg.pb.tit.tms.TMSSignalTopic in the JNDI tree. The object you
          > >>>have bound
          > >>>from 169.59.5.26 is non clusterable and you have tried to bind more
          > >>>than once
          > >>>from two or more servers. Such objects can only deployed from one
          > >>>server.>
          > >>>
          > >>>
          > >>>When I understand correctly, this happens because the JNDI tree gets
          > >>>distributed to all nodes of the cluster, so there would be two object
          > >>>with the same name. How do I solve this situation? Do I have the
          > >>>specify different names for topics in different JMSServer running in a
          > >>>cluster? How would the load balancing work?
          > >>>
          > >>>
          > >>>Please help. Thanks in advance
          > >>>
          > >>>Juerg
          > >>

Running Weblogic in Cluster mode on Win2K Pro

Hi :
          I am running WL5.1 (sp8) on Win2K Pro, Is there any limitation that I cannot
          run Weblogic as Clustered in Win2k Pro ??.
          and how to setup Multicast IP Address ?. I tried with the default 237.0.0.1
          (using it with -D option to start the server) and other MultiCastIPs too I
          am having some problems :
          Note : I dont have any weblogic cluster / other applications that use the
          above MIP.
          =====================
          C:\weblogic>java utils.MulticastTest -n server111 -a 237.0.0.1
          ***** WARNING ***** ***** WARNING ***** ***** WARNING *****
          This utility should NOT be run on the same multicast address as a running
          WLAS cluster.
          Pausing for 5 seconds prior to starting test.
          Starting test. Hit any key to abort
          Set up to send and receive on Multicast on Address 237.0.0.1, on port 7001
          Will send a sequenced message under the name server111 every 2 seconds.
          Will also inform console every 600 seconds if no messages received
          New Neighbor server111 found on message number 1
          I (server111) sent message num 1
          java.net.SocketException: socket closed
          at java.net.PlainDatagramSocketImpl.receive(Native Method)
          at java.net.DatagramSocket.receive(DatagramSocket.java:392)
          at utils.MulticastTest$Receiver.run(MulticastTest.java, Compiled
          Code)
          I (server111) sent message num 2
          can anyone help me understand what the above problem is all about ?
          thanks
          Balaji.


Balaji Venkataraman wrote:
          > Hi :
          >
          > I am running WL5.1 (sp8) on Win2K Pro, Is there any limitation that I cannot
          > run Weblogic as Clustered in Win2k Pro ??.
          Not that I know of. Does this happen all the time.
          -- Prasad
          >
          > and how to setup Multicast IP Address ?. I tried with the default 237.0.0.1
          > (using it with -D option to start the server) and other MultiCastIPs too I
          > am having some problems :
          > Note : I dont have any weblogic cluster / other applications that use the
          > above MIP.
          > =====================
          > C:\weblogic>java utils.MulticastTest -n server111 -a 237.0.0.1
          > ***** WARNING ***** ***** WARNING ***** ***** WARNING *****
          > This utility should NOT be run on the same multicast address as a running
          > WLAS cluster.
          >
          > Pausing for 5 seconds prior to starting test.
          >
          > Starting test. Hit any key to abort
          >
          > Set up to send and receive on Multicast on Address 237.0.0.1, on port 7001
          > Will send a sequenced message under the name server111 every 2 seconds.
          > Will also inform console every 600 seconds if no messages received
          >
          > New Neighbor server111 found on message number 1
          > I (server111) sent message num 1
          > java.net.SocketException: socket closed
          > at java.net.PlainDatagramSocketImpl.receive(Native Method)
          > at java.net.DatagramSocket.receive(DatagramSocket.java:392)
          > at utils.MulticastTest$Receiver.run(MulticastTest.java, Compiled
          > Code)
          > I (server111) sent message num 2
          >
          > can anyone help me understand what the above problem is all about ?
          >
          > thanks
          > Balaji.

How to receive emails of the same inbox from in a Weblogic Server cluster

Hi All,
I have an application running on WebLogic Server with 6 instances. Many requests for the application come from Email. We already set up an email account that will be used by all clients to send email to. But the problem is that the email account inbox can only be opened for reading by a single connection, unlike a typical database. Currently I can only deploy the email reading service on a single server instance, this will effectively create a single point of failure and unbalanced load. What's the best way to read from the same inbox from multiple servers? I am thinking developing something using a database table, sort of leasing, whoever locked the table own the lease and can connect to the email server, but this is pretty hard to implement correctly in all circumstances.
I did an intensive search on the internet, but couldn't find anything.
I appreciate your help very much.
Thanks
Tao

Hi Aditya
By default, OPA 10.4 will collect the minimum amount of information needed to answer the goal of your interview and then display the answer and the reasons for the answer.You can change what appears on these screens within OPM itself (you don't need to change those settings).
So I would:
- add a Summary Screen to your project (if you haven't already)
- add <your goal attribute> to your summary screen. This will display as a link if the goal is unknown and as a sentence showing the outcome and a Why? link when it is known.
- add a label to the summary screen, providing information about the outcome (eg "Congratulations you are eligible") or simply show the value of the outcome (eg Your total deduction is %deduction_amount%).
- use visibility rules to control which items to display at the start/end of your interview (in your case, maybe hide your goal once it is known and show your label once your goal is known). See OPA help topic "Tutorial: Hiding and displaying summary screen elements".
The Inferred Brand Discount sample supplied in the OPM install provides an example of this (see Help topic Sample Rulebases for information on how to open this).
Hope that helps,
Fiona

Accessing Coherence Extend* Proxy Deployoed on Weblogic Coherence Cluster from Java Client

Hi,
I am trying to access Extend Proxy through Thick Java Client
Followed steps as per below links and deployed a GAR on 3 Server ( 2 Storage Enabled Coherence Cluster and 1 Coherence Storage Disabled Extend Proxy Enabled). I could see ExtendProxyService using JMX and can see Port running on the System.
Ref :
Setting Up Coherence*Extend - 12c (12.1.2)
http://docs.oracle.com/middleware/1212/coherence/COHAG/deploy_options.htm#CHDJBJDI
Issue :
When I tried to Execute Java Client to Connect to Proxy Server it Connects to Port and then Disconnects with ConnectionException as below.
Observer below Lines in Box is show he Connected Socket with Port 9099 which is Extend Proxy Port
Error Message
2013-11-08 14:55:55.114/1.202 Oracle Coherence GE 12.1.2.0.0 <D5> (thread=TcpClientRemoteService:TcpInitiator, member=n/a): Started: TcpInitiator{Name=TcpClientRemoteService:TcpInitiator, State=(SERVICE_STARTED), ThreadCount=0, Codec=Codec(Format=POF), Serializer=com.tangosol.io.DefaultSerializer, PingInterval=0, PingTimeout=30000, RequestTimeout=30000, ConnectTimeout=10000, SocketProvider=[email protected], RemoteAddresses=WrapperSocketAddressProvider{Providers=[[DTC37446E9C6CBD/127.0.0.0:9099]]}, SocketOptions{LingerTimeout=0, KeepAliveEnabled=true, TcpDelayEnabled=false}}
2013-11-08 14:55:55.146/1.234 Oracle Coherence GE 12.1.2.0.0 <D5> (thread=main, member=n/a): Connecting Socket to 127.0.0.0:9099
2013-11-08 14:55:55.146/1.234 Oracle Coherence GE 12.1.2.0.0 <Info> (thread=main, member=n/a): Connected Socket to 127.0.0.0:9099
2013-11-08 14:55:55.161/1.249 Oracle Coherence GE 12.1.2.0.0 <Info> (thread=main, member=n/a): Error establishing a connection with 127.0.0.0:9099: com.tangosol.net.messaging.ConnectionException: TcpConnection(Id=null, Open=true, LocalAddress=0.0.0.0:54384, RemoteAddress=127.0.0.0:9099)
2013-11-08 14:55:55.161/1.249 Oracle Coherence GE 12.1.2.0.0 <Error> (thread=main, member=n/a): Error while starting service "TcpClientRemoteService": com.tangosol.net.messaging.ConnectionException: could not establish a connection to one of the following addresses: [127.0.0.0:9099]; make sure the "remote-addresses" configuration element contains an address and port of a running TcpAcceptor
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.initiator.TcpInitiator.openConnection(TcpInitiator.CDB:121)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.peer.Initiator.ensureConnection(Initiator.CDB:11)
    at com.tangosol.coherence.component.net.extend.remoteService.RemoteCacheService.openChannel(RemoteCacheService.CDB:7)
    at com.tangosol.coherence.component.net.extend.RemoteService.doStart(RemoteService.CDB:11)
    at com.tangosol.coherence.component.net.extend.RemoteService.start(RemoteService.CDB:5)
    at com.tangosol.coherence.component.util.SafeService.startService(SafeService.CDB:53)
    at com.tangosol.coherence.component.util.safeService.SafeCacheService.startService(SafeCacheService.CDB:5)
    at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:27)
    at com.tangosol.coherence.component.util.SafeService.start(SafeService.CDB:14)
    at com.tangosol.net.ExtensibleConfigurableCacheFactory.startService(ExtensibleConfigurableCacheFactory.java:681)
    at com.tangosol.net.ExtensibleConfigurableCacheFactory.ensureService(ExtensibleConfigurableCacheFactory.java:599)
    at com.tangosol.coherence.config.scheme.AbstractCachingScheme.realizeCache(AbstractCachingScheme.java:50)
    at com.tangosol.coherence.config.scheme.AbstractBundlingScheme.realizeCache(AbstractBundlingScheme.java:31)
    at com.tangosol.net.ExtensibleConfigurableCacheFactory.ensureCache(ExtensibleConfigurableCacheFactory.java:254)
    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:205)
    at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:182)

If this proxy design (not starting up due to a invalid entry in "authroized-hosts") is on-purpose from Coherence Engineers - then it should be re-visited.
I think the PROXY Server should just log a message stating about the invalid DNS entry for the Authorized-host and continue with the startup...Failing to start completely doesn;t make sense since one cannot rely completely on DNS to
say everything should be correct before a server start.
Ofcourse you can overcome by writing your own Custom Filter - but the issue pop's out as with any custom filter(s) is maintaining them along the road (with all minor/major coherence upgrades).
Also - this "Authorized-Hosts" concept should be carefully analyzed particularly for the following issues...
(1) if the client IP is changed in the DNS server - will the proxy-server allow the new Client connection without any issues? when will the PROXY server flush its CLIENT DNS entries or what is the TTL time-limit for a CLIENT cached through Authorized-hosts by the PROXY-SERVER?
(2) Suppose, we have a CLIENT in the "Authroized-Hosts" making a valid connection to the PROXY and putting some cache into the SERVER CACHE through the PROXY....now if the IP-address (DNS being the same) of the CLIENT is changed - can the CLIENT can GET the CACHE it just PUT into the SERVER without any ERRORS?
(3) How often we need to re-start PROXIES? Do we need to re-start them often for the DNS issues (if any) mentioned above?
Looks like the Limited documentation & examples for Coherence*Extend - particularly for .NET & C++ clients & *Extend Proxies is a point of concern.
vk

Oracle Weblogic 11g Cluster on two seperate unix machine

hi to all,
Can any one plz provide help how to create cluster having managed servers on different machine , in full details.
Thanks

Steps to set-up clusters using the admin console can be found here: http://download.oracle.com/docs/cd/E17904_01/apirefs.1111/e13952/taskhelp/clusters/ClusterRoadmap.html
Steps to configure machine using the admin console can be found here: http://download.oracle.com/docs/cd/E17904_01/apirefs.1111/e13952/taskhelp/machines/ConfigureMachines.html
You still need to perform the pack and unpack steps, as described in the blog.

Weblogic quickstart cluster wizard

Similar Messages

Maybe you are looking for