Mdb "JMSConnection Alive" false in cluster

          Hi
          I am deploying an MDB [jar] in a cluster of 2 servers - and I send a message to
          the Queue [pinned queue to server1]. I am seeing that there are no consumers for
          the Queue and the "monitoring the MDB" link shows JMSConnection Alive property
          to be false - what does that mean? is the MDB not able to see the Queue? The message
          remains in the Queue.
          thanks
          Anamitra

Please post your log files, config.xml, and the code for the producer
          that can't find the info. JNDINameReplicated is set to true by default.
          Anamitra wrote:
          > Hi Tom
          > I fixed all my cluster issues [actually I reinstalled wls 7.0 sp2 in both the
          > boxes - and did the cluster setup again - that solved it]. Now both the servers
          > can see each other. But the problem is with the jms queues. I am not using distributed
          > queues. I am just pinning the queue to server1 and a producer form server2 is
          > not able to see it!. This is nothing to do with MDBs - I suspect the queue jndi
          > name is not getting replicated somehow - looks like a bug. I rerember that there
          > was a attr JNDINameRplicated somewhere - is it something to do with that?
          >
          > thanks
          > Anamitra
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>Hi Anamitra,
          >>
          >>Before trying to get the MDB to work, I think you need to resolve
          >>the cluster synchronization problems. The MDB depends
          >>on JNDI to find its destination, and JNDI in turn depends
          >>on cluster synchronization.
          >>
          >>I suspect a problem with multicasting. Try
          >>posting to clustering and/or jndi newsgroup to get a diagnosis.
          >>
          >>Tom
          >>
          >>Anamitra wrote:
          >>
          >>>pls note that when the cluster comes up the server2 never finds the
          >>
          >>server1 to
          >>
          >>>synchronize with[in case when server 2 boots up after server1] - but
          >>
          >>server1 always
          >>
          >>>finds the server2 [in case when server1 boots up after server2]. This
          >>
          >>is strange!
          >>
          >>>Also the queue that has the data is maxqueues/contqueuein - and monitoring
          >>
          >>that
          >>
          >>>queue shows there are no consumers.
          >>>
          >>>thanks
          >>>Anamitra
          >>>
          >>>Tom Barnes <[email protected]> wrote:
          >>>
          >>>
          >>>>Check your log file for errors and warnings. Even if
          >>>>an MDB is successfully deployed, it may not be able
          >>>>to reach the queue due to misconfiguration.
          >>>>If you like, post your config.xml and descriptor files
          >>>>and I'll take a quick look.
          >>>>
          >>>>Tom
          >>>>
          >>>>Anamitra wrote:
          >>>>
          >>>>
          >>>>>Hi
          >>>>>I am deploying an MDB [jar] in a cluster of 2 servers - and I send
          >>>>
          >>>>a message to
          >>>>
          >>>>
          >>>>>the Queue [pinned queue to server1]. I am seeing that there are no
          >>>>
          >>>>consumers for
          >>>>
          >>>>
          >>>>>the Queue and the "monitoring the MDB" link shows JMSConnection Alive
          >>>>
          >>>>property
          >>>>
          >>>>
          >>>>>to be false - what does that mean? is the MDB not able to see the
          >>>>
          >>Queue?
          >>
          >>>>The message
          >>>>
          >>>>
          >>>>>remains in the Queue.
          >>>>>
          >>>>>thanks
          >>>>>Anamitra
          >>>>
          >

Similar Messages

WLS 7 MDB JMSConnection Alive false - where is the error reported?

I have a few MDBs subscribed to various destinations. One of them is
subscribed to a queue called jms.queue.queue1 in JNDI. queue1 is a
regular Queue (not distributed), lives in JMSServer1, which is
deployed to WLS server1. An entry for it appears in JNDI on each
server in the cluster (server1 + server2). The MDB lives in an
ejb-jar which is deployed to the cluster containing server1 & server2.
In the console, under deployments -> ejb -> myejb.jar -> monitoring ->
Monitor all Message Driven EJBRuntimes, all the other MDBs have
"JMSConnection Alive" appearing as "true", but the one subscribed to
queue1 has "false". I cannot see any exceptions in the server logs.
Is there any way to get at the reason for the "false"?
I can use a command-line QueueSender and Receiver on queue1 without a
problem, using the t3:// url of either of the WLS Servers.
What's most important to me is where the error is reported - I've had
this problem a couple of times and it seemed to go away on its own.
I'm not getting any diagnositics right now.
Many thanks,
Jeremy.

I guess you got the answer by this time.
IF not the answer is:
Use enable the TX flags in the JMSConnectionFactory. Goto console. Select
the JMSConnectionFactory (what MDB is using). Click on the trnsactions tab.
Check the boxes there.
Cheers,
..maruthi
"Jeremy Watson" <[email protected]> wrote in message
news:[email protected]..
>
I "stumbled on" this - if you set these system properties:
weblogic.ejb20.jms.connect.verbose=trueweblogic.ejb20.jms.connect.debug=true
>
..then you get some informative error messages from the EJB runtime as ittries
to connect to the JMS destination. In my case, I got the followingexception coming
out:
[JMSConnectionPoller] : ** FAILED TO CONNECT TO JMS WITH:weblogic.ejb20.WLDeploymentException:
Message Driven Bean 'mdb3' is transacted but the provider defined in theejb is not
transacted. Provider should be transacted if onMessage method in MDB istransacted.
>
>
Apologies for double-posting. Thanks for the piece of direction Tom (inthe jms group),
which helped me find the answer.
Jeremy.

Mdb "JMSConnection Alive" False in clustered domain

I have a clustered domain with 2 servers on 2 seperate boxes. The Queue is pinned to server1. I am seeing 1 consumer for the Queue when both servers are running. Server2 does not appear to connect to the Queue but there is nothing written to the logs to suggest it is not. I also have another domain exactly like the first on the same boxes with the same problem with the 2nd server. Any ideas? I have looked through the forums and everyone says to check the logs, but there is nothing written to our logs concerning this Queue.

I have a clustered domain with 2 servers on 2 seperate boxes. The Queue is pinned to server1. I am seeing 1 consumer for the Queue when both servers are running. Server2 does not appear to connect to the Queue but there is nothing written to the logs to suggest it is not. I also have another domain exactly like the first on the same boxes with the same problem with the 2nd server. Any ideas? I have looked through the forums and everyone says to check the logs, but there is nothing written to our logs concerning this Queue.

WLS 10 MDB migration within a WLS cluster

Hi,
I'm trying to get MDB migration working. From my reading in the documentation regarding this topic, it appears that I have to deploy my MDB to all of the cluster server instances.
Ex, if the JMS server that my MDB is using is on a migratable target and it composes of srv1 and srv2, then I also have to deploy my MDB to srv1 and srv2 in order to get some form of "migration" working.
What I want to know is if it's possible to do a real migration like migrating JMS service for example? Instead of doing this multiple deployment of my MDB.
this snippet from http://edocs.bea.com/wls/docs100/ejb/message_beans.html#wp1168630 seems to be talking about the above setup.
MDBs do not have migratable targets. Instead, an MDB automatically detects the JMS Server migration target during deployment, and uses that as its migratable target. You must ensure that MDB are deployed everywhere that a JMS Server is deployed. You can do this in two ways:
* Deploy MDBs homogeneously to the cluster.
* Match an MDB’s targets to the JMS migratable target list in the config.xml file for the server instance’s cluster. The MDB target server name must match the JMS migratable target list, or MDB migration will fail. For more information on configuring migratable targets, see “Defining Migratable Target Servers in a Cluster” in Using WebLogic Server Clusters.

Hi,
Thanks for the information.
Can you explain why this is happening though?
I have a distributed queue with two members (or specifically two JMS servers), which is targetted across the cluster (two servers cluster).
I have 1 MDB that is targetted to one of the JMS server in the distributed queue.
I deployed the MDB to the whole cluster. During monitoring, I noticed that two copies of the MDB are resident at startup (1 active on the cluster instance where the JMS server is hosting the source destination; the other is active residing on the other cluster instance). When I manually migrate the JMS server, the MDBs' status just switch due to one able to connect while the other cannot connect anymore.
So, this is what's to be expected of MDB migration, correct? In this simple scenario for example, there will always be 1 resident running/suspended copy of the MDB in memory within each cluster server instance. The MDB migration is just simply switching between one cluster instance's resident MDB to another instance's.
Is this correct?
Thanks.

Best way to determine if JMS server is alive in a cluster

Can anyone give me an idea on the best way to find out if a JMS server
          in a cluster
          has failed so I can signal migration to another server in the cluster.
          Thanks Larry
          PS weblogic 7.0 sp1


Hallo Larry,
          you can go via JMX and retrieve the according RuntimeMBeans in order to
          check the health state of the
          JMSServer resp. the server hosting the JMSServer. If they are not available
          or failed you can trigger the
          migration. At least that's the way I'm doing it...
          try
          JMSServerMBean jmsServer = null;
          ServerMBean candidateServer = null;
          MigratableTargetMBean migratableTarget = null;
          * Retrieve all JMSServer defined for the current domain
          Set jmsServerSet = home.getMBeansByType("JMSServer", domainName);
          Object[] jmsServers = jmsServerSet.toArray();
          * Just the first one is picked assuming there is only one defined
          * within the active FHO domain
          if(jmsServers != null && jmsServers.length > 0)
          jmsServer = (JMSServerMBean) jmsServers[0];
          if(s_logger.isDebugEnabled())
          s_logger.debug("JMSServer: " + jmsServer.getName());
          * A JMSServer can only be associated with a single target,
          * thus pick again the first from the list.
          TargetMBean[] targets = jmsServer.getTargets();
          if(targets != null && targets.length > 0)
          boolean hostingServerRunning = false;
          boolean candidateServerRunning = false;
          * Check whether the JMSServer is really associated with
          * a migratable target. Otherwise the migration must be canceled
          * since it cannot be performed!
          if(targets[0] instanceof MigratableTargetMBean)
          migratableTarget = (MigratableTargetMBean) targets[0];
          * Retrieve all available candidates and select a running instance
          * if any. First check for constrained candidate servers, than for
          * all candidate servers
          ServerMBean[] candidates =
          migratableTarget.getConstrainedCandidateServers();
          if(candidates == null || candidates.length == 0)
          candidates = migratableTarget.getAllCandidateServers();
          if(candidates != null && candidates.length > 0)
          ServerMBean hostingServer = migratableTarget.getHostingServer();
          boolean gotHostingServer = false;
          boolean gotCandidateServer = false;
          boolean runningInstance = false;
          * Loop over all candidates as long as hosting server and candidate
          * server are visited and there running state has been determined
          for(int i=0; i< candidates.length; i++)
          ServerRuntimeMBean serverRuntime = null;
          * Retrieve the current state from the according runtime MBean
          * if available
          try
          serverRuntime = (ServerRuntimeMBean) home.getMBean(new
          WebLogicObjectName(candidates.getName(), "ServerRuntime", domainName,
          candidates[i].getName()));
          runningInstance =
          serverRuntime.getState().equalsIgnoreCase(ServerRuntimeMBean.RUNNING);
          catch(InstanceNotFoundException inf)
          * When a server instance is not available, an InstanceNotFoundException will
          be raised
          * by WLS, which can be ignored
          if(hostingServer != null && hostingServer.equals(candidates[i]))
          hostingServerRunning = runningInstance;
          gotHostingServer = true;
          else
          * A running candidate server will be prefered, thus only if no running
          * instance can be detected, another instance is selected
          if(!gotCandidateServer)
          candidateServerRunning = runningInstance;
          candidateServer = candidates[i];
          gotCandidateServer = runningInstance;
          if(gotCandidateServer && gotHostingServer)
          break;
          if(s_logger.isDebugEnabled())
          s_logger.debug("Migratable Target: " + migratableTarget.getName());
          s_logger.debug("Candidate Server: " + candidateServer.getName());
          else
          throw new Exception("JMSServer not deployed on a migratable target!");
          * Retrieve the migration service coordinator for the active domain assuming
          * there exists only one and invoke the migration later on
          MigratableServiceCoordinatorRuntimeMBean coordinator = null;
          Set coordinatorSet =
          home.getMBeansByType("MigratableServiceCoordinatorRuntime", domainName);
          Object[] coordinators = coordinatorSet.toArray();
          if(coordinators.length > 0)
          coordinator = (MigratableServiceCoordinatorRuntimeMBean) coordinators[0];
          if(enforceMigrationOnInstancesDown)
          coordinator.migrate(migratableTarget, candidateServer, hostingServerRunning,
          candidateServerRunning);
          else
          coordinator.migrate(migratableTarget, candidateServer);
          s_logger.info("Migration of JMSServer from node "
          + migratableTarget.getName()
          + " to node "
          + candidateServer.getName()
          + " has been started");
          else
          throw new Exception("MigrationServiceCoordinator cannot be retrieved");
          catch(Exception e)
          s_logger.error("Could not migrate JMSServer", e);
          Regards,
          CK
          "Larry Presswood" <[email protected]> schrieb im Newsbeitrag
          news:[email protected]...
          > Can anyone give me an idea on the best way to find out if a JMS server
          > in a cluster
          > has failed so I can signal migration to another server in the cluster.
          >
          > Thanks Larry
          >
          > PS weblogic 7.0 sp1
          >

Limiting MDB to one instance per cluster

I'm working on a Weblogic setup that has one cluster consisting of three servers. We have one queue in particular whose MDB does a lot of database access. We're running into locking problems with the database because Weblogic is running an instance of the MDB on each of the three servers at the same time and they are stepping on each other's toes.
          I would like to limit the queue so it only runs on one server in the cluster. The pool size for this MDB is set to "1". I thought this would limit the total number of MDBs to one, but apparently it limits it to one per server.
          Any idea what sort of configuration I need to make sure only one instance of the MDB exists in the cluster? Do I need to turn this into a distributed queue and do something with load balancing?
          Thanks,
          Matt

Thanks for the reply.
          I looked around and I couldn't find a way to target the MDB to a specific server. I can target the JMS server, but not a single MDB. The way I have it setup currently, the JMS server is targeted to one server in the cluster (non-migratable).
          How do I target a MDB to a specific server?
          Matt

为什么我写的消息驱动bean监听不到jms客户端发送的消息

客户端发送了一条文本消息，topic主题中已经收到该信息，但是消息驱动bean没收到。onMessage()方法的代码如下：
public void onMessage(Message msg)
try {
System.out.println("InvokingMDB onMessage() now.");
System.out.println("MessageObject is: " + msg);
System.out.println("Textmessage is: " + ((TextMessage)msg).getText());
System.out.println();
catch (JMSException e) {
System.out.println("Whoops!A JMSException occurred: " + e);
e.printStackTrace();
这是我的weblogic-ejb-jar.xml文件的内容：
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN' 'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>MessageTopic</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>15</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>JMSTopic</destination-jndi-name>
<connection-factory-jndi-name>JMSConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
这是ejb-jar.xml中的定义的一部分：
<message-driven>
<display-name>MessageTopic</display-name>
<ejb-name>MessageTopic</ejb-name>
<ejb-class>demo.message.MessageTopicBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
<subscription-durability>Durable</subscription-durability>
</message-driven-destination>
</message-driven>
如下是我在weblogic console下监视活动消息驱动bean 的信息：
EJBName：MessageTopic
Idle Beans Count：1
Beans In Use Count：0
Waiter Total Count：0
Timeout Total Count：0
JMSConnection Alive: false);
System.out.println("MessageObject is: " + msg);

去掉这个试试：
<connection-factory-jndi-name>JMSConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>

消息驱动bean问题,请教

上载的消息驱动bean的监视状态如下：
EJBName Pool Idle Beans Count Pool Beans In Use Count Pool Waiter Total Count Pool Timeout Total Count JMSConnection Alive
NewCustomerReceiverBean 3 0 0 0 false
请教一下Bea工程师，是不是90天使用版的消息驱动Bean，有问题？？
JMSConnection Alive 总是处于false的？？？
我的配置如下：
ejb－jar.xml部署描述：
<message-driven>
<display-name>NewCustomerReceiverBean</display-name>
<ejb-name>NewCustomerReceiverBean</ejb-name>
<ejb-class>testweb.NewCustomerReceiverBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
weblogic－ejb－jar.xml 部署描述：
<weblogic-enterprise-bean>
<ejb-name>NewCustomerReceiverBean</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>3</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>JMSQueueJNDI</destination-jndi-name>目的JNDI名字 <connection-factory-jndi-name>JMSConnectionFactory</connection-factory-jndi-name>连接工厂JNDI名字
</message-driven-descriptor>
</weblogic-enterprise-bean>
config。Xml配置文件：
<JMSConnectionFactory JNDIName="JMSConnectionFactory"
Name="MyJMS Connection Factory" Targets="myserver"/>这里是连接工厂JNDI配置
<JMSFileStore Directory="c:\jms_store" Name="MyJMSFile Store"/>
<JMSServer Name="MyJMSServer" Store="MyJMSFile Store" Targets="myserver">
<JMSQueue JNDIName="JMSQueueJNDI" Name="MyJMSQueue"/>这里是目的JNDI配置
<JMSTopic JNDIName="JMSTopicJNDI"
MulticastAddress="237.124.35.35" Name="MyJMSTopic"/>
</JMSServer>
此文被shufei在2003/07/18 13:16:30修改!

不好意思，再声明一下，
我单独做的测试配置的 JMS连接工厂和目的，能正常作为中间层运转。
还有消息驱动bean的程序和测试程序如下：
public class NewCustomerReceiverBean implements MessageDrivenBean, MessageListener {
MessageDrivenContext messageDrivenContext;
public void ejbCreate() throws CreateException {
/**@todo Complete this method*/
public void ejbRemove() {
/**@todo Complete this method*/
public void onMessage(Message msg) {
/**@todo Complete this method*/
if(msg instanceof MapMessage){
try{
MapMessage m = (MapMessage) msg;
int id = m.getInt("customerId");
String company=m.getString("companyName");
String address=m.getString("address");
System.out.println("生成："+id+","+company+","+address+" 成功。。。。" );
}catch(JMSException ex){
System.out.println(" ++++++++++"+ex);
}catch(Exception ex){
System.out.println(" ++++++++++"+ex);
messageDrivenContext.setRollbackOnly();
public void setMessageDrivenContext(MessageDrivenContext messageDrivenContext) {
this.messageDrivenContext = messageDrivenContext;
System.out.println(" 设置 context成功：");//这一步也总能服务器端的启动dos窗口打//印出来.
客户程序如下：
public static void main(String[] args){
MessageClient client=new MessageClient();
if(client.SendMessage(100))
System.out.println("发送成功");
public boolean SendMessage(int i) {
try {
Context ctx = null;
Hashtable ht = new Hashtable();
QueueConnectionFactory tConnectionFactory = null;
QueueConnection tConnection = null;
QueueSession tSession = null;
javax.jms.QueueSender tPublisher = null;
Queue t = null;
Hashtable ht=new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
ctx = new InitialContext(ht);
tConnectionFactory = (QueueConnectionFactory) ctx.lookup(
"JMSConnectionFactory");
tConnection = tConnectionFactory.createQueueConnection();
tSession = tConnection.createQueueSession(false,
javax.jms.QueueSession.
AUTO_ACKNOWLEDGE);
t = (Queue) ctx.lookup("JMSQueueJNDI");
tPublisher = tSession.createSender(t);
MapMessage mm=(MapMessage)tSession.createMapMessage();
mm.setInt("customerId",i);
mm.setString("companyName","电脑公司");
mm.setString("address","公司地址");
tPublisher.send(mm);// 这里发送消息
System.out.println("消息放松完成............");
try {
tPublisher.close();
tSession.close();
tConnection.close();
catch (Exception ex) {
ex.printStackTrace();
return false;
return true;
catch (Exception ex) {
ex.printStackTrace();
return false; }
return false;
return true;
catch (Exception ex) {
ex.printStackTrace();
return false; }

MDB deployment in cluster

i have an MDB deployed to a weblogic cluster(weblogic10).
My requirement is i need MDB failover in case one server goes down. so i have no choice of deploying the MDB to any of the manged server. i ahve set the maximum pool size as 1 for MDB,but the MDB is instantiated from each managed server. I need only one MDB to service the queue ,but needs failover in case the any of the servere fails. Any option to do this in weblogic server.If not possible by waht way i can accomplish this task.

Is there any special reason why you only want one MDB to consume messages fro the queue?

Error on setup failover cluster with Windows 2008 R2 enterprise and SQL Server 2008 R2 (also with SP1)

Hi!
The setup process fails with this error:
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
I have found some hints by google, but nothing really helpfull.
Has anyone had a simular problem when installing SQL server 2008 R2?
All posts I found are about sql server 2008 (no R2!).
The cluster itself is working (storage, network, msdtc, quorum...).
Any hints?
Andreas
Here is the complete log:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2067791871
Exit facility code:            1216
Exit error code:               1
Exit message:                  Failed: see details below
Start time:                    2012-04-06 11:23:57
End time:                      2012-04-06 12:01:21
Requested action:              InstallFailoverCluster
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x625969A3%400x294A9FD9
Cluster properties:
Machine name: OC-SQLCL02ND01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine name: OC-SQLCL02ND02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine Properties:
Machine name:                  OC-SQLCL02ND01
Machine processor count:       32
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
Installation location:         G:\x64\setup\
Installation edition:          STANDARD
Slipstream:                    True
SP Level                       1
User Input Settings:
ACTION:                        InstallFailoverCluster
AGTDOMAINGROUP:                <empty>
AGTSVCACCOUNT:                 MANAGEMENT\sqladmin
AGTSVCPASSWORD:                *****
ASBACKUPDIR:                   S:\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   S:\OLAP\Config
ASDATADIR:                     S:\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      S:\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  MANAGEMENT\sqladmin
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            MANAGEMENT\administrator
ASTEMPDIR:                     S:\OLAP\Temp
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
CUSOURCE:
ENU:                           True
ERRORREPORTING:                False
FAILOVERCLUSTERDISKS:          Cluster Disk 3,Cluster Disk 4,Cluster Disk 5
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    IPv4;172.29.2.122;Cluster Network 2;255.255.255.0,IPv4;172.29.3.122;Cluster Network 3;255.255.255.0
FAILOVERCLUSTERNETWORKNAME:    CLUSTER02
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             S:\
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
PASSPHRASE:                    *****
PCUSOURCE:                     d:\install\mssql\sp1
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  MANAGEMENT\sqladmin
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLDOMAINGROUP:                <empty>
SQLSVCACCOUNT:                 MANAGEMENT\sqladmin
SQLSVCPASSWORD:                *****
SQLSYSADMINACCOUNTS:           MANAGEMENT\administrator
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBDIR:                  T:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQMREPORTING:                  False
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Analysis Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Integration Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\SystemConfigurationCheck_Report.htm

Hi Andreas Plachy,
Please make sure that the Virtual Server Name ‘CLUSTER02’ is unique on the network. In addition, are there any resources named ‘SQL Server’ on the Windows cluster? If that is the case, you may need to rename the related resources to avoid conflicting with
SQL Server, and try again.
Stephanie Lv
TechNet Community Support

Deployement order of MDBs and SSBs

Hi All,
Facing the issue with deployment order of EJBs in one ear,
MDBs start reading and processing message before SSBs are initialised in JNDI while server startup.
And JNDI lookup for SSB from MDB failes JNDI lookup exception gets raised, failing the whole processing of message.
1) MDBs jar and SSBs jar are in one EAR, so deployment order attribute can't be specified in config.xml or thru admin console, as it is with an application.
2) Have tried <start-mdbs-with-application>false</start-mdbs-with-application> (even with true)
as per http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ejb/message_beans.html#wp1167264
but it doesn't work.
3) Now planning to use WL LifeCyclelistner and get server state = RUNNING, before starting to process the messages in MDB.
Anybody has any viable solution other than this?
Thanks & Regards,
Keyur

Hi Keyur,
Which version on weblogic are you using because its seems that this might be a bug and similar bug was seen in WLS-9.2 version more details are given below:
From the link below which you gave it states that
“Set to false to defer message processing until after WebLogic Server opens its listen port.”
Search for: start-mdbs-with-application
Link-1 http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ejb/message_beans.html#wp1167264
# Conclusion:
This means that “false” should have resolved your issue but it is not so this might be a bug. Similar bug was seen in WLS-9.2 version which was fixed in WLS-9.2 Mp-1 version check out the link below.
Search for: CR293982 or CR299012
Link-2 http://download.oracle.com/docs/cd/E13222_01/wls/docs92/issues/known_resolved.html
However if it was fixed in WLS 9.2 Mp-1 then the same issue is most probably taken care in WLS 10.x.x version also.
# Suggestion:
- Try to set “start-mdbs-with-application” as “true” and check if that works for you.
This is because if you read the “Link-1″ carefully it states that “With default setting of true”, however when you check the “Default” column it shows “false”. Hence cant say which one is default. It might be document bug as well. However you have tried it so you can skip this suggestion.
# How to solve this issue:
1) Create a simple test case to prove that “start-mdbs-with-application” when set as “false” does not work.
2) Open a ticket with Oracle and provide all the details with the test case and let them do their job.
Hope this information helps.
Regards,
Ravish Mody

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

Disabling Keep Alive

We are using GWT with Glassfish and Sun Web server. We're encountering occassional problems causing the servlet to fail with "Client did not send xxxx bytes" exception.
I read in another post elsewhere that people have solved this problem in Glassfish-Apache configuration with the following settings:
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
Can someone tell me what is the equivalent setting in Sun Webserver?
Thanks

Try "set-reverse-proxy-prop"
[http://docs.sun.com/app/docs/doc/820-2204/set-reverse-proxy-prop-1?l=en&a=view|http://docs.sun.com/app/docs/doc/820-2204/set-reverse-proxy-prop-1?l=en&a=view]
* use-keep-alive Indicates whether the HTTP client should attempt to use persistent connections. The default value is true.
* keep-alive-timeout The maximum number of seconds to keep a persistent connection open. The default value is 29.
* always-use-keep-alive Indicates whether the HTTP client can reuse the existing persistent connections for all types of requests. The default value is false, indicating that persistent connections will not be reused for non-GET requests or for requests with a body.
* protocol The HTTP protocol version string. By default, the HTTP client uses either HTTP/1.0 or HTTP/1.1 based on the contents of the HTTP request. In general, you should not use the protocol parameter unless you encounter specific protocol interoperability problems.
...So, probably this will work for you:
set-reverse-proxy-prop use-keep-alive=false protocol="HTTP/1.0"

Setting the initial of MDB as Suspended

Hi,
Is it possible to set the initial state of an MDB as suspended after server startup?
I want to control the processing of messages after server startup.
Thanks,
S

If you want to make MDB process messages after server startup, you can setup weblogic-application.xml in this way:
<weblogic-application xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-application" 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/javaee_5.xsd http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd">
<ejb>
<start-mdbs-with-application>false</start-mdbs-with-application>
</ejb>
</weblogic-application>
Once you set start-mdbs-with-application to false, MDB will not startup until the server is activated.

Deactivating MDB using JMX

Hi All,
I have a requirement to deactivate a MDB from its own onMessage method , when it detects some error.
This is the piece of code I was using:
DeployerRuntimeMBean deployer = DeployerRuntime.getDeployerRuntime();
deployer.deactivate("MDBName", null, null);
I was able to pause the MDB by running the above code in our developer environment where there is only the admin server . When I tested this in our UAT environment I was getting a null pointer exception. In UAT environment we are having an admin server + a cluster . There is only a single managed server in the cluster and the MDB is targeted to the cluster.
Any clue why this error is happening.
TIA
-Atheek

If you need to access this from a managed server, you could use one of
the getDeployerRuntime methods that connects as a client to the admin
server:
http://e-docs.bea.com/wls/docs100/javadocs/weblogic/management/deploy/DeployerRuntime.html
Tony
Tony wrote:
The DeployerRuntimeMBean only exists on the admin server:
http://e-docs.bea.com/wls/docs100/javadocs_mhome/weblogic/management/runtime/DeployerRuntimeMBean.html
Tony
Atheek Rahuman wrote:
Hi All,
I have a requirement to deactivate a MDB from its own onMessage method , when it detects some error.
This is the piece of code I was using:
DeployerRuntimeMBean deployer = DeployerRuntime.getDeployerRuntime();
deployer.deactivate("MDBName", null, null);
I was able to pause the MDB by running the above code in our developer environment where there is only the admin server . When I tested this in our UAT environment I was getting a null pointer exception. In UAT environment we are having an admin server + a cluster . There is only a single managed server in the cluster and the MDB is targeted to the cluster.
Any clue why this error is happening.
TIA
-Atheek

Mdb "JMSConnection Alive" false in cluster

Similar Messages

Maybe you are looking for