[Creating a channel to push]

Similar Questions

• Create a channel by combining smaller values of the other two channels

  Hello, I have two channels (v + and Volts1 +) and I am trying to create another channel (Volts_Small) that will have smaller values of the two channels. I need to compare each data point in the two channels and add little value to the new channel.

  THS is what I tried without success:

  I have Sun
  
  Dim: Set Group = Data.Root.ChannelGroups ("200_68")
  
  Dim Chn1: Set Chn1 = Group.Channels ("v +")
  
  Dim Chn2: Set Chn2 = Group.Channels ("Volts1 +")
  
  Dim Chn3: Set Chn3 = Group.Channels ("Volts_Small")
  
  For i = 1 to Chn1.Size
  
    If (Chn1.Values (i) > Chn2.Values (i)) then
  
      Chn3.values (i) = Chn2.Values (i)
  
    On the other
  
      Chn3.values (i) = Chn1.Values (i)
  
    End If
  
  Next

  I would give much help appreciate with this! Thank you.

  Cedric

  EDIT:

  Nevermind, I solved this problem:

  I have Sun
  
  Dim: Set Group = Data.Root.ChannelGroups ("200_68")
  
  Dim Chn1: Set Chn1 = Group.Channels ("v +")
  
  Dim Chn2: Set Chn2 = Group.Channels ("Volts1 +")
  
  Dim Chn3: Set Chn3 = Group.Channels ("Volts_Small")
  
  For i = 1 to 900000
  
    If (Chn1.Values (i) > Chn2.Values (i)) then
  
      Chn3.values (i) = Chn2.Values (i)
  
    On the other
  
      Chn3.values (i) = Chn1.Values (i)
  
    End If
  
  Next

  Hi Cedric,

  I strongly advise to use the calculator channel and the MinV() function that is already integrated to tiara.  You have less code that runs much faster, especially for the largest data sets.

  Dim: Set Group = Data.Root.ChannelGroups ("200_68")
  
  Dim Chn1: Set Chn1 = Group.Channels ("v +")
  
  Dim Chn2: Set Chn2 = Group.Channels ("Volts1 +")
  
  Dim Chn3: Set Chn3 = Group.Channels ("Volts_Small")
  
  Var Variables: Variables = Array ("Ch1", "Ch2", "Ch3")
  
  Dim channels: channels = Array (Chn1, Chn2, Chn3)
  
  Call to calculate ("Ch3 = MinV (Ch1, Ch2)", Variables, channels)

  Brad Turpin

  Tiara Product Support Engineer

  National Instruments

• DAQmx create virtual channel (VI) error-229771 reports

  Hello

  When in a project that I am working to get error-229771 code whenever I try to run 'DAQmx create Virtual Channel (VI)' this does not happen when I create a vi not in a project.  The problem is that this project is very large and it if poster impossible to recreate. It's several hundred vi. Y at - it something that I missed in the forums and support that could explain this. I created the VI below in the project and outside the project. In the project, the error occurs outside the project, it runs without any problems.

  Message:

  229771 error occurred at .vi:1780003 DAQmx create channel (I-voltage-Basic)

  Possible reasons:

  Internal software error has occurred in the MIG software. Please contact the support of National Instruments.

  Task name: _unnamedTask

  Any help would be appreciated.  Thank you, Matt.

  LabVIEW version: 15.052(32bit)

  OR Max Version: 15.0.f0

  NEITHER DAQmx Verson: 15

  OS: windows 7 service pack 1

  PC: Intel Core i7-2600, 8 GB of ram

  Data Aquistion: NEITHER DAQ USB-6289 calibrated June 2015

  This code snippet returns the name of the first channel of analog input on the device first, and then tries to create a task for her. The bed of the canal, then close the task.

  

  Error message

  

  Hi Matthew,

  Thank you for following up after you fix your problem.  I'm glad to hear that you do not encounter this problem more.

  Here is an article that lists the reasons for this error (although unfortunately, I cannot pin down which is the exact cause in this case).

  http://digital.NI.com/public.nsf/allkb/03123D0E8A36C48E862577A4005B6BAA

  NOTE: This article specifies that the error occurs at startup task VI DAQmx.  You do not use the start task VI, so the task starts automatically in the DAQmx Read function.  The error will occur instead in the DAQmx virtual channel create, that you encounter in your error.

  I hope this gives you an idea about what could have gone wrong, and I'm sorry he is no more details.

  Good programming!

• How to create a channel for a PXI-6509

  I'm working on a program to fight the PXI-6509. The only area that I have problems with creates the string by calling the function DAQmxCreateDOChan. I get no errors during the first DAQmxCreateTask, but get an error when you try to create the channel. Exactly how to create the channel name? In MAX, I have named the "DIO" device, do not know if it matters. Any help would be greatly appreciated.

  Hi schelgr,

  Have you had a glance examples DAQmx in finder example found in help > find examples.  In input and output equipment > DAQmx there is a lot of examples that should be able to help with this query.

  Concerning

• How to create analog channels in Labview

  I need to create 4 channels analog pressure through card PCI-6229 in Labview v8.2 and I have to set these channels so that labview can communicate with the card... But I'm failing to do...

  If you have an idea, then please e-mail me back...
  Waiting for your valuable advice...

  Thank you all for reply

  but my problem is still not resolved I want yo not individually define the four channels at once.

  If possible please sen me some screenshots.

  Thank you

  waiting for your advice

• What are the options to programmaticaly create new channels of i/o hardware?

  I saw a post that usescustom channels to possibly do what I want to do. I was wondering other options available, for no custom devices?

  I have a set of AIs, AOs, tell and back. Instead of manually enter, I just want to do it programmatically. It's ok if I have to treat separately the different types (I, AO...).

  Which API to use to achieve this?

  THX.

  L.

  Replying to myself...

  It seems that there is an option using a variation on the example: NI Veristand > API > API definition system > support > create an SDF file with the user Channels.vi.

  Will post after actually trying.

  If you know other options, I'm always interested in hearing thereon.

  THX.

  L.

• Adding a date and time to create a channel in a data plugin

  I would like to preface this question with the fact that I am new to VBS programming.  What I want to do is to create a plugin. Most of it is done, but I'm having a problem with the addition of two times to a.  I have a text file that stores the date and time separated by a tab character.  This file format was designed to excel.  When I bring him both the date and time are in different channels and I can not figure out a way to add both and either replace them or even place it in a separate variable.  Here is an example.

  Chan (1) contains the date, Chan (2) contains both.  This statement, which places the data in the string is:

  The StandChannels value (0). Values (k) = Chan (1). Values (i)

  I tried:

  The StandChannels value (0). Values (k) = Chan (1). Values (i) + Chan (2). Values (i)

  error: object doesn't support this property or method

  or

  Chan (1). Values (i) = Chan (1). Values (i) + Chan (2). Values (i)

  error: object doesn't support this property or method

  I tried several other iterations and have had no success.  This seems to be an easy task, Miss me probably something simple.

  Hi Eric,.

  The first problem is that your datetime format string was wrong, you need to use:

  File.Formatter.TimeFormat = "MM/DD/YY SS.fff.

  Or maybe if your year is first of all it must be:

  File.Formatter.TimeFormat = "YY/MM/DD SS.fff.

  The second question was slippery.  The newsgroups (0) you throw combines the ProcessedChannel values correctly, but you were not successfully picking off those that you wanted to leave Chan (0).  I don't really know why the method you were using did not work, but I found a similar one that does.  Note that I've only changes part SUB New_File (file, ChanNames) of the code, not the SUB Previous_File (file, ChanNames) part of the code (got tired of typing).

  Brad Turpin

  Tiara Product Support Engineer

  National Instruments

• StatBlockCalc without creating data channels for results

  I am creating the min, max and average for a group of channels (3 of them), but I don't want to create/store new data channels - I prefer to use the variables StatMin, StatMax, and StatArithMean.  For example, by using the script

  StatClipCopy = 0

  StatClipValue = 0

  StatFormat = «»

  StatResChn = 1

  Call StatBlockCalc ("Channel", "2-254", "" [1] / Ah - ' [1] / temperature A1'") '... StatDirec, RowNoStr, ChnNoStr

  causes of 3 new channels (min/max/AVG) with 3 items in each channelto created in the data portal.  Rather than create channels, I change the StatResChn = 0, I thought I should store only the values in the variables StatMin, StatMax, and StatArithMean

  StatClipCopy = 0

  StatClipValue = 0

  StatFormat = «»

  StatResChn = 0

  Call StatBlockCalc ("Channel", "2-254", "" [1] / Ah - ' [1] / temperature A1'") '... StatDirec, RowNoStr, ChnNoStr

  However this only seems to work uses a single channel (amperes / hour or temperature A1)

  Is it possible to get multiple statistical values (statmin, statmax, etc.) on multiple channels without creating separate portal data channels?

  Otmar

  Exactly what I was looking for.  I tried and it works fine.  Thank you very much!!!

  I have a supplementary question - is there any kind of available documents describing these properties/values such as ResultMin, etc.?

• create global channels programmatically

  Hi all

  My question has to do with daqmx.

  I want to know if theres nothing to create the global channels or tasks programmatically without using the wizard of max or daqmx

  the usual procedure is to create global tasks or channels using the wizard of max or daqmx and then add them to your tasks programmatically.

  I want to avoid the use of max here and create channels by program that can be used or called later.

  You can use the task of saving DAQmx or DAQmx save Global Channel screws to register programmatically.

  http://zone.NI.com/reference/en-XX/help/370469AA-01/lvdaqmx/mxsavetask/

  I agree with Dennis, however, almost all the tasks of data acquisition is possible using the standard functions.  You might want to take a look at a few examples of data acquisition by going to help > find examples > Input and Output material > DAQmx.  I always start by these examples, and change them if necessary.

• How can I autoindex looping for to create several channels daqmx

  I'm trying to autoindex create a loop FOR containing the DAQmx vi to create AI multi-channel voltage with identical settings, except that I need to apply specific channel names using a constant and specific physical channels using a constant of channel. Wiring of a constant DAQmx of physical channel does not work because the data type is incorrect. Similarly, I don't understand how to use a string constant to autoindex through the channel names is or how to configure the constant string (s) to assign names. Also, when I try to make one of these, I get a tunnel to exit the DAQmx autoindex create channel, rather than a task out. I can achieve my goal using several explicit DAQmx create calls to channel, but for high channel count, it is very time consuming.

  I use LV 8.5.

  I'm hoping to find the code showing how to perform the conversion type, flattening, or what to do.

  Diane has.

  I have an array of clusters.  Each element of this array is a cluster.  The cluster consists of a (scalar) string and input/output (also scalar).

  In addition, my TI attachment extracted.  I think that your file has been LV2009.  If so, you can drag the image from the browser and drop it onto a diagram.

• Problem creating new channels charger after an election when ReplicationGroupAdmin or DbPing used

  This question relates to 5.0.84.  I have found no messages forward precisely the same problem here.

  My application uses I HA with replication on 4 nodes.  We tested different failure scenarios in which us network-isolate the master node.  We see survivors 3 replicas of an election, a master is determined, food chains are established and the overall replication group resumes its features.   We also tested the scenarios in which the master of the now 3-node replication-reduced group is isolated from the network in the same way.    The results generally worked, but were less reliable when the Group transitions from 3 to 2 knots.   We thought the quorum (replacement of likely to be elected group size) setting was the proper way to address this issue and had good results by manually setting the substitution of group likely to be elected to down size.

  We have set up a StateChangeListener and in its stateChange() method try to automate adjustment of the size of likely to be elected group override by calling DbPing getNodeState() (alternating) methods and ReplicationGroupAdmin for interview each of 4 nodes possible to see who was available and no INDIVIDUAL State.    However, it seems that DbPing or ReplicationGroupAdmin employment within our application to any node causes the implementation of feeder channels after an election of a new master failed (regardless of the number of survivors is likely to be elected nodes).    It seems rather ironic, or that the introduction be DbPing or ReplicationGroupAdmin in our application code introduces a principle of Heisenberg uncertainty effect in which tent to observe the number of active nodes causes the behavior of replication group, or more precisely - creating channel charger - for change.    Is there a prohibition against using DbPing, ReplicationGroupAdmin or getNodeState() in an application node methods likely to be elected?   Do same using these objects/methods in a cause of app monitor a change in behavior among the nodes to be elected after an election?    We seem to be observing such behavior.

  Thank you

  Ted

  Here's the log of je.info.0, of NŒUD01.  Initially, the NŒUD02 is the master.   17:57:55, we network-isolate NŒUD02.  We see an election is called, node01 wins and starts trying to establish the feeders but can't.

  130903 17:55:56:752 INFO [NŒUD01] began to ServiceDispatcher. HostPort = ap01.domain.acme .net: 13000

  current group 130903 size INFO [NŒUD01] 17:55:56:867: 4

  INFO [node01] existing 17:55:56:868 130903 node01 mark for a current master node.

  17:55:56:913 INFO [node01] node node01 130903 began

  17:55:56:914 130903 INFO [node01] committed election; choice #1

  130903 17:55:56:926 INFO [node01] Started election thread kills Sep 03 17:55:56 CDT 2013

  130903 changed NŒUD02 master INFO [node01] 17:56:29:308

  17:56:29:310 130903 INFO [node01] election is completed. Elapsed time: 32396ms

  17:56:29:310 INFO [NŒUD01] exit election after 5 attempts 130903

  130903 wire INFO [node01] election of 17:56:29:311 came out. Group master: node02 (64)

  130903 17:56:29:310 INFO [node01] Replica loop started with master: node02 (64)

  Departure from 130903 17:56:29:343 INFO [node01] Replica-power handshake

  Handshake 130903 17:56:29:536 INFO [node01] Replica-charger NŒUD02 completed.

  130903 17:56:29:553 INFO [node01] Replica-charger NŒUD02 syncup began. Replica range: first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  130903 17:56:29:650 INFO [node01] Rollback to matchpoint 843 393-0 x 33/0x2d38 status not = no active txns, nothing to restore

  17:56:29:651 130903 NŒUD02 start INFO [node01] VLSN Replica-feeder stream: 843 394

  130903 17:56:29:652 INFO [node01] Replica-charger NŒUD02 syncup completed. Elapsed time: 102ms

  Replica of INFORMATION [node01] 130903 17:56:29:658 initialization is complete. Replica VLSN: VLSN validation master Heartbeat 843 393: 843 393 delta VLSN: 0

  17:56:29:662 INFO [NŒUD01] 130903 joined group as a replica.  Join consistencyPolicy = PointConsistencyPolicy targetVLSN = 843, 393 first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  130903 17:56:29:667 Replay INFO [node01] started thread. Message queue size: 1000

  130903 17:56:29:666 INFO [node01] refreshed 0 monitors.

  130903 17:56:30:939 WARNING [node01] likely to be elected changed size override group: 3

  130903 inactive channel INFO [NŒUD01] 17:57:54:860: node02 (64) forced close. Timeout: 7000ms.

  17:57:55:406 130903 INFO [NŒUD01] exit inner loop of the replica.

  130903 replica of the INFO [NŒUD01] 17:57:55:407 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:57:56:049 130903 INFO [node01] committed election; choice #2

  130903 17:57:56:050 INFO [node01] pending election. Waiting...

  130903 17:57:56:057 INFO [node01] Started election thread kills Sep 03 17:57:56 CDT 2013

  17:58:08:115 INFO [node01] 130903 master changed to node01

  17:58:08:116 130903 INFO [node01] election is completed. Elapsed time: 12067ms

  17:58:08:121 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:08:122 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:08:122 INFO [NŒUD01] exit election after 2 attempts 130903

  130903 wire INFO [node01] election of 17:58:08:123 came out. Group master: node01 (61)

  17:58:09:124 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:09:130 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:10:128 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:10:137 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  17:58:11:132 130903 INFO [NŒUD01] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  ...      The same message repeated ad nauseam...

  Here's the log of je.info.0 of NŒUD02 for the same period of time.   NŒUD02 begins as master, but this host becomes isolated from the network and its supply channels stops at 17:57:55:

  130903 17:56:26:861 INFO [NŒUD02] file chose lowest used for cleaning. fileChosen: 0x2f totalUtilization: 50 bestFileUtilization: 0 lnSizeCorrectionFactor: isProbe 0.55577517: false

  17:56:26:912 130903 INFO [NŒUD02] CleanerRun 1 ends on the probe file 0x2f = false invokedFromDaemon = true finished = true fileDeleted = false nEntriesRead = 1 nINsObsolete = 0 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nBINDeltasObsolete = 0 nBINDeltasCleaned = 0 nBINDeltasDead = 0 nBINDeltasMigrated = 0 nLNsObsolete = 0 nLNsCleaned = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0 logSummary = < CleanerLogSummary endFileNumAtLastAdjustment = '0 x 33' initialAdjustments = '5' recentLNSizesAndCounts = "Horn : 1274201 / 3219 - is: 1494628 / 3219 Cor: 535 / 6-is: 965 / 11 Cor: 788 / 8-East: 1190 / Cor 13: 789 / 8-is: 1289/14 Horn: 714 / 2-is: 1310 / 9 Horn: 37694 / 611 - is: 178596 / 619 Horn: 168637 / 3961 - is: 1164331 / 3961 Cor: 62 / 1-is: 2286 / 21 Cor: 22130 / 1446 - is: 417561 / 1451 Horn: 2429020 / 9915 - is: 3837944 / 9915 "> inSummary = < totalINCount INSummary = '0' totalINSize = '0' totalBINDeltaCount = '0' totalBINDeltaSize = '0' obsoleteINCount = '0' obsoleteINSize = '0' obsoleteBINDeltaCount = '0' obsoleteBINDeltaSize = '0' / >» estFileSummary = < Sommaire totalCount = « 1 » totalSize = « 31 » totalINCount = « 0 » totalINSize = « 0 » totalLNCount = « 0 » totalLNSize = « 0 » maxLNSize = « 0 » obsoleteINCount = « 0 » obsoleteLNCount = « 0 » obsoleteLNSize = « 0 » obsoleteLNSizeCounted = « 0 » getObsoleteSize = « 31 » getObsoleteINSize = « 0 » getObsoleteLNSize = « 0 » getMaxObsoleteSize = « 31 » getMaxObsoleteLNSize = « 0 » getAvgObsoleteLNSizeNotCounted = « NaN » / > recalcFileSummary = < Sommaire totalCount = « 1 » totalSize = « 31 » totalINCount = « 0 » totalINSize = « 0 » totalLNCount = « 0 » totalLNSize = « 0 » maxLNSize = « 0 » obsoleteINCount = « 0 » obsoleteLNCount = « 0 » obsoleteLNSize = « 0 » obsoleteLNSizeCounted = « 0 » getObsoleteSize = « 31 » getObsoleteINSize = « 0 » getObsoleteLNSize = « 0 » getMaxObsoleteSize = « 31 » getMaxObsoleteLNSize = « 0 » getAvgObsoleteLNSizeNotCounted = « NaN » / > lnSizeCorrection = 0.55577517 newLnSizeCorrection = 0.55577517 estimatedUtilization = 0 correctedUtilization = 0 recalcUtilization = 0

  130903 17:56:26:973 INFO [NŒUD02] began to ServiceDispatcher. HostPort = ap02.domain.acme .net: 13000

  [17:56:26:992 130903 INFO [NŒUD02] Unknown Service request: Acceptor registered services:]

  current group 130903 size INFO [NŒUD02] 17:56:27:108: 4

  INFO [NŒUD02] existing 17:56:27:108 130903 NŒUD02 mark for a current master node.

  17:56:27:186 INFO [NŒUD02] node NŒUD02 130903 began

  17:56:27:186 130903 INFO [NŒUD02] committed election; choice #1

  130903 17:56:27:206 INFO [NŒUD02] Started election thread kills Sep 03 17:56:27 CDT 2013

  130903 17:56:29:290 INFO [NŒUD02] winning proposal: Proposal(00000140e6787717:0000000000000000000000000a000253:00000001) value: value: 10.0.2.83 13000. $ $$$ $$ NŒUD02$ $$ 64

  17:56:29:299 INFO [NŒUD02] master changed from NŒUD02 130903

  17:56:29:301 130903 INFO [NŒUD02] completed election. Elapsed time: 2114ms

  Manager of Feeder INFO [NŒUD02] 17:56:29:302 130903 accepts applications.

  17:56:29:309 130903 INFO [NŒUD02] Unknown Service request: registered Feeder services: [Acceptor learner, LogFileFeeder, LDiff, NodeState, group, BinaryNodeState]

  Group INFO [NŒUD02] Joining 130903 17:56:29:312 as master

  130903 17:56:29:317 INFO [NŒUD02] refreshed 0 monitors.

  130903 wire INFO [NŒUD02] election of 17:56:29:318 came out. Group master: node02 (64)

  17:56:29:374 130903 Feeder INFO [NŒUD02] has accepted the java.nio.channels.SocketChannel connection [connected local=/10.0.2.83:13000 remote=/10.0.2.82:60052]

  Departure of handshake 17:56:29:477 INFO [NŒUD02] replica Feeder 130903

  Handshake 130903 17:56:29:539 INFO [NŒUD02] Feeder-replica completed node01.

  Syncup 17:56:29:542 130903 INFO [NŒUD02] Feeder-replica node01 began. Range of charger: first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  17:56:29:654 130903 node01 start INFO [NŒUD02] replica Feeder to VLSN stream: 843 394

  130903 17:56:29:656 INFO [NŒUD02] Feeder-replica node01 syncup completed. Elapsed time: 113ms

  130903 17:56:29:660 Feeder INFO [NŒUD02] release thread for the replica node01 started at master VLSN 843 394 to 843 393 VLSN delta = - 1 = socket (node01 (61)) java.nio.channels.SocketChannel [remote=/10.0.2.82:60052 connected local=/10.0.2.83:13000]

  17:56:30:321 130903 Feeder INFO [NŒUD02] has accepted the java.nio.channels.SocketChannel connection [connected local=/10.0.2.83:13000 remote=/10.0.2.63:47920]

  Departure of handshake 17:56:30:326 INFO [NŒUD02] replica Feeder 130903

  Handshake 130903 17:56:30:349 INFO [NŒUD02] Feeder-replica completed node04.

  130903 17:56:30:350 INFO [NŒUD02] Feeder-replica node04 syncup began. Range of charger: first = 843, 326 last = 843, 395 sync = 843, txnEnd 395 = 843, 395

  17:56:30:363 130903 node04 start INFO [NŒUD02] replica Feeder to VLSN stream: 843 394

  130903 17:56:30:364 INFO [NŒUD02] Feeder-replica node04 syncup completed. Elapsed time: 14ms

  17:56:30:383 130903 Feeder INFO [NŒUD02] out of thread for the replica node04 started to master VLSN 843 394 to 843 395 delta VLSN = 1 socket = (node04 (62)) java.nio.channels.SocketChannel [remote=/10.0.2.63:47920 connected local=/10.0.2.83:13000]

  130903 17:56:31:678 likely to be elected [NŒUD02] WARNING group size changed override: 3

  17:57:21:200 130903 Feeder INFO [NŒUD02] has accepted the java.nio.channels.SocketChannel connection [connected local=/10.0.2.83:13000 remote=/10.0.2.84:38224]

  Departure of handshake 17:57:21:206 INFO [NŒUD02] replica Feeder 130903

  Handshake 130903 17:57:21:272 INFO [NŒUD02] Feeder-replica completed node03.

  130903 17:57:21:273 INFO [NŒUD02] Feeder-replica node03 syncup began. Range of charger: first = 843, 326 last = 843, 399 sync = 843, 399 = 843, 399 txnEnd

  17:57:21:389 130903 node03 start INFO [NŒUD02] replica Feeder to VLSN stream: 843 394

  130903 17:57:21:390 INFO [NŒUD02] Feeder-replica node03 syncup completed. Elapsed time: 117ms

  17:57:21:392 130903 Feeder INFO [NŒUD02] out of thread for the replica node03 started to master VLSN 843 394 to 843 399 delta VLSN = 5 socket = (node03 (63)) java.nio.channels.SocketChannel [remote=/10.0.2.84:38224 connected local=/10.0.2.83:13000]

  130903 inactive channel INFO [NŒUD02] 17:57:55:115: node01 (61) forced close. Timeout: 7000ms.

  130903 inactive channel INFO [NŒUD02] 17:57:55:115: node04 (62) forced close. Timeout: 7000ms.

  130903 17:57:55:116 INFO [NŒUD02] closing feeder for replica node01 reason: null write time: 2ms Avg write time: 98us

  130903 inactive channel INFO [NŒUD02] 17:57:55:125: node03 (63) forced close. Timeout: 7000ms.

  130903 17:57:55:126 INFO [NŒUD02] closing feeder for replica node04 reason: null write time: 3ms Avg write time: 147us

  130903 17:57:55:127 INFO [NŒUD02] closing feeder for replica node03 reason: null write time: 1ms Avg write time: 90us

  17:57:55:409 130903 Feeder INFO [NŒUD02] out to stop node01 replica. VLSN charger: 843 402 currentTxnEndVLSN: 843 401

  Out of the 17:57:55:410 130903 Feeder INFO [NŒUD02] judgment of the node03 replica. VLSN charger: 843 402 currentTxnEndVLSN: 843 401

  Out of the 17:57:55:411 130903 Feeder INFO [NŒUD02] judgment of the node04 replica. VLSN charger: 843 402 currentTxnEndVLSN: 843 401

  17:58:49:456 INFO [NŒUD02] master changed to node01 130903

  17:58:50:227 130903 Master INFO [NŒUD02] change: managing change. The ID of the master node: master group to node02 id (64): node01 (61)

  Block latch commit 17:58:50:228 130903 Releasing INFO [NŒUD02]

  130903 Feeder INFO [NŒUD02] 17:58:50:229 Manager is out. VLSN CurrentTxnEnd: 843 401

  17:58:50:230 INFO [NŒUD02] RepNode thread 130903 main stop.

  Shutdown 17:58:50:233 130903 INFO [NŒUD02] RepNode exception:

  (I 5.0.84) NŒUD02 (64): / data / NŒUD02 com.sleepycat.je.rep.stream.MasterStatus$ MasterSyncException: master the change. The ID of the master node: master group to node02 id (64): node01 (61) MASTER_TO_REPLICA_TRANSITION: this node was a master and must reset the internal State to become a replica. The application must close and reopen all the environment handles. The environment is not valid and must be closed.node02 (64) [MASTER]

  No feeders.

  GlobalCBVLSN = 843, 393

  Group info [RepGroup] 8e8b97b5-f9bc-4b9e-bb6e-56edfbe79674

  Version of the representation: 2

  Change version: 4

  Node for the max rep ID: 64

  Node: NŒUD02 ap02.domain.acme .net: 13000 (belongs) changeVersion:4 LocalCBVLSN:843, 393 to: kills Sep 03 17:56:31 CDT 2013

  Node: node03 ap03.domain.acme .net: 13000 (belongs) changeVersion:3 LocalCBVLSN:843, 393 to: kills Sep 03 17:57:21 CDT 2013

  Node: node01 ap01.domain.acme .net: 13000 (belongs) changeVersion:1 LocalCBVLSN:843, 393 to: kills Sep 03 17:56:29 CDT 2013

  Node: node04 ap04.domain.acme .net: 13000 (belongs) changeVersion:2 LocalCBVLSN:843, 393 to: kills Sep 03 17:56:30 CDT 2013

  vlsnRange = first = 843, 326 last = 843, 401 sync = 843, txnEnd 401 = 843, 401

  lastReplayedTxn = null lastReplayedVLSN = 843, 393 numActiveReplayTxns = 0

  130903 17:58:50:234 INFO [NŒUD02] stop the node node02 (64)

  INFO [NŒUD02] elections stop 130903 17:58:50:235 triggered

  INFO [NŒUD02] elections stop 130903 17:58:50:238 finished

  130903 17:58:50:239 RepNode INFO [NŒUD02] main thread: MASTER node02 (64) was released.

  17:58:50:240 130903 INFO [NŒUD02] ServiceDispatcher stop starting. [HostPort = ap02.domain.acme .net: 13000 registered services:]

  Stop INFO [NŒUD02] ServiceDispatcher 17:58:50:243 130903 done. HostPort = ap02.domain.acme .net: 13000

  Stop 17:58:50:243 INFO [NŒUD02] node02 130903 (64) finished.

  Here's the log of node03.  We see node01 wins the election, but

  17:57:20:961 130903 INFO [node03] CleanerRun 1 ends on the probe file 0x2f = false invokedFromDaemon = true finished = true fileDeleted = false nEntriesRead = 1 nINsObsolete = 0 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nBINDeltasObsolete = 0 nBINDeltasCleaned = 0 nBINDeltasDead = 0 nBINDeltasMigrated = 0 nLNsObsolete = 0 nLNsCleaned = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0 logSummary = < CleanerLogSummary endFileNumAtLastAdjustment = '0 x 32' initialAdjustments = '5' recentLNSizesAndCounts = "Horn : 1274201 / 3219 - is: 1494628 / 3219 Cor: 535 / 6-is: 965 / 11 Cor: 788 / 8-East: 1190 / Cor 13: 789 / 8-is: 1289/14 Horn: 714 / 2-is: 1310 / 9 Horn: 37694 / 611 - is: 178596 / 619 Horn: 168637 / 3961 - is: 1164331 / 3961 Cor: 62 / 1-is: 2286 / 21 Cor: 22130 / 1446 - is: 417561 / 1451 Horn: 2429020 / 9915 - is: 3837944 / 9915 "> inSummary = < totalINCount INSummary = '0' totalINSize = '0' totalBINDeltaCount = '0' totalBINDeltaSize = '0' obsoleteINCount = '0' obsoleteINSize = '0' obsoleteBINDeltaCount = '0' obsoleteBINDeltaSize = '0' / >» estFileSummary = < Sommaire totalCount = « 1 » totalSize = « 31 » totalINCount = « 0 » totalINSize = « 0 » totalLNCount = « 0 » totalLNSize = « 0 » maxLNSize = « 0 » obsoleteINCount = « 0 » obsoleteLNCount = « 0 » obsoleteLNSize = « 0 » obsoleteLNSizeCounted = « 0 » getObsoleteSize = « 31 » getObsoleteINSize = « 0 » getObsoleteLNSize = « 0 » getMaxObsoleteSize = « 31 » getMaxObsoleteLNSize = « 0 » getAvgObsoleteLNSizeNotCounted = « NaN » / > recalcFileSummary = < Sommaire totalCount = « 1 » totalSize = « 31 » totalINCount = « 0 » totalINSize = « 0 » totalLNCount = « 0 » totalLNSize = « 0 » maxLNSize = « 0 » obsoleteINCount = « 0 » obsoleteLNCount = « 0 » obsoleteLNSize = « 0 » obsoleteLNSizeCounted = « 0 » getObsoleteSize = « 31 » getObsoleteINSize = « 0 » getObsoleteLNSize = « 0 » getMaxObsoleteSize = « 31 » getMaxObsoleteLNSize = « 0 » getAvgObsoleteLNSizeNotCounted = « NaN » / > lnSizeCorrection = 0.55577517 newLnSizeCorrection = 0.55577517 estimatedUtilization = 0 correctedUtilization = 0 recalcUtilization = 0

  130903 17:57:20:991 INFO [node03] began to ServiceDispatcher. HostPort = ap03.domain.acme .net: 13000

  current group 130903 size INFO [node03] 17:57:21:111: 4

  INFO [node03] existing 17:57:21:112 130903 node03 mark for a current master node.

  17:57:21:155 130903 INFO [node03] master changed from NŒUD02

  17:57:21:182 INFO [node03] node node03 130903 began

  130903 17:57:21:183 INFO [node03] Replica loop started with master: node02 (64)

  Departure from 17:57:21:205 130903 INFO [node03] Replica-power handshake

  Handshake 130903 17:57:21:269 INFO [node03] Replica-charger NŒUD02 completed.

  Syncup of NŒUD02 17:57:21:282 130903 INFO [node03] Replica-power began. Replica range: first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  130903 17:57:21:385 INFO [node03] Rollback to matchpoint 843 393-0 x 32/0x55da status not = no active txns, nothing to restore

  17:57:21:386 130903 NŒUD02 start INFO [node03] Replica-feeder VLSN stream: 843 394

  130903 17:57:21:387 INFO [node03] Replica-charger NŒUD02 syncup completed. Elapsed time: 105ms

  Replica of the INFO [node03] 130903 17:57:21:391 initialization is complete. Replica VLSN: VLSN validation master Heartbeat 843 393: 843 399 delta VLSN: 6

  130903 17:57:21:396 Replay INFO [node03] thread started. Message queue size: 1000

  17:57:21:417 INFO [node03] 130903 joined group as a replica.  Join consistencyPolicy = PointConsistencyPolicy targetVLSN = 843, 399 first = 843, 326 last = 843, 399 sync = 843, 399 = 843, 399 txnEnd

  130903 17:57:21:421 INFO [node03] refreshed 0 monitors.

  130903 inactive channel INFO [node03] 17:57:55:069: node02 (64) forced close. Timeout: 7000ms.

  17:57:55:406 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:57:55:407 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:57:56:059 130903 INFO [node03] committed election; choice #1

  130903 17:57:56:068 INFO [node03] Started election thread kills Sep 03 17:57:56 CDT 2013

  130903 17:58:08:101 INFO [node03] winning proposal: Proposal(00000140e679d235:0000000000000000000000000a000254:00000001) value: value: 10.0.2.82 13000. $ $$$ $$ NŒUD01$ $$ 61

  17:58:08:108 130903 INFO [node03] master changed to node01

  17:58:08:112 130903 INFO [node03] completed election. Elapsed time: 12053ms

  130903 17:58:08:113 INFO [node03] Replica loop started with master: node01 (61)

  17:58:08:124 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:08:125 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:08:126 INFO [node03] try again #: 0/10 retries loop replica after 1000ms.

  130903 17:58:09:127 INFO [node03] Replica loop started with master: node01 (61)

  17:58:09:131 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:09:131 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:09:132 INFO [node03] try again #: 1/10 retries loop replica after 1000ms.

  130903 17:58:10:133 INFO [node03] Replica loop started with master: node01 (61)

  17:58:10:138 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:10:138 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:10:139 INFO [node03] try again #: 2/10 retries loop replica after 1000ms.

  130903 17:58:11:139 INFO [node03] Replica loop started with master: node01 (61)

  17:58:11:142 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:11:142 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:11:143 INFO [node03] try again #: 3/10 retries loop replica after 1000ms.

  130903 17:58:12:144 INFO [node03] Replica loop started with master: node01 (61)

  17:58:12:146 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:12:147 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:12:147 INFO [node03] try again #: 4/10 retries loop replica after 1000ms.

  130903 17:58:13:148 INFO [node03] Replica loop started with master: node01 (61)

  17:58:13:162 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:13:222 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:13:222 INFO [node03] try again #: 5/10 retries loop replica after 1000ms.

  130903 17:58:14:223 INFO [node03] Replica loop started with master: node01 (61)

  17:58:14:225 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:14:226 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:14:226 INFO [node03] try again #: 6/10 retries loop replica after 1000ms.

  130903 17:58:15:227 INFO [node03] Replica loop started with master: node01 (61)

  17:58:15:229 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:15:230 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:15:230 INFO [node03] try again #: 7/10 retries loop replica after 1000ms.

  130903 17:58:16:231 INFO [node03] Replica loop started with master: node01 (61)

  17:58:16:233 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:16:234 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:16:234 INFO [node03] try again #: 8/10 retries loop replica after 1000ms.

  130903 17:58:17:235 INFO [node03] Replica loop started with master: node01 (61)

  17:58:17:237 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:17:238 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:17:238 INFO [node03] try again #: 9/10 retries loop replica after 1000ms.

  130903 wire INFO [node03] election of 17:58:18:112 came out. Group master: node01 (61)

  130903 17:58:18:239 INFO [node03] Replica loop started with master: node01 (61)

  17:58:18:280 INFO [node03] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node03] 17:58:18:280 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:58:18:281 130903 INFO [node03] could not recover from exception: failed after attempts: 10 with retry interval: 1000ms., despite 10 attempts.

  com.sleepycat.je.rep.impl.node.Replica$ ConnectRetryException: failed after attempts: 10 with retry interval: 1000ms.

  at com.sleepycat.je.rep.impl.node.Replica.createReplicaFeederChannel(Replica.java:777)

  at com.sleepycat.je.rep.impl.node.Replica.initReplicaLoop(Replica.java:578)

  at com.sleepycat.je.rep.impl.node.Replica.runReplicaLoopInternal(Replica.java:392)

  at com.sleepycat.je.rep.impl.node.Replica.runReplicaLoop(Replica.java:328)

  at com.sleepycat.je.rep.impl.node.RepNode.run(RepNode.java:1402)

  17:58:18:282 130903 INFO [node03] committed election; choice #2

  130903 17:58:18:282 INFO [node03] in the current election. Waiting...

  .... Attempts and the ConnectRetryException repeat ad nauseam...

  We see a similar trend in the node04 newspaper.  We observe on 17:58:08:101 node01 became master, but we are unable to establish a connection to power supply to:

  130903 17:55:48:149 INFO [node04] began to ServiceDispatcher. HostPort = ap04.domain.acme .net: 13000

  current group 130903 size INFO [node04] 17:55:48:230: 4

  130903 17:55:48:231 INFO [node04 Existing node04 mark for a current master node.

  17:55:48:258 INFO [node04] node node04 130903 began

  17:55:48:259 130903 INFO [node04] committed election; choice #1

  130903 17:55:48:266 INFO [node04] Started election thread kills Sep 03 17:55:48 PDT 17:56:29:300 2013130903 Master INFO [node04] changed to NŒUD02

  17:56:29:301 130903 INFO [node04] completed election. Elapsed time: 41043ms

  130903 17:56:29:301 INFO [node04] Replica loop started with master: NŒUD02 (64) 130903 17:56:29:303 INFO [node04] out election after 5 retries130903 17:56:29:304 wire INFO [node04] election came out. Group master: NŒUD02 (6

  4)

  17:56:29:309 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:56:29:310 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:56:29:310 INFO [node04] try again #: 0/10 retries loop replica after 10

  00ms.130903 17:56:30:310 INFO [node04] Replica loop started with master: node02 (64)

  Departure from 17:56:30:324 130903 INFO [node04] Replica-power handshake

  Handshake 130903 17:56:30:348 INFO [node04] Replica-charger NŒUD02 completed.

  Syncup of NŒUD02 17:56:30:352 130903 INFO [node04] Replica-power began. Replica range: first = 843, 326 last = 843, 393 sync 843, 393 = txnEnd = 843, 393

  130903 17:56:30:361 INFO [node04] Rollback to matchpoint 843 393-0 x 34 / 0 x 1628

  status = no active txns, nothing to restore

  17:56:30:362 130903 NŒUD02 start INFO [node04] Replica-feeder VLSN stream: 843 394

  130903 17:56:30:362 INFO [node04] Replica-charger NŒUD02 syncup completed. Elapsed time: 10 ms

  Replica of the INFO [node04] 130903 17:56:30:382 initialization is complete. Replica VLSN: VLSN validation master 843 393: 843 395 delta VLSN: 2 Heartbeat

  130903 17:56:30:386 Replay INFO [node04] thread started. Message queue size: 1000

  17:56:30:397 INFO [node04] 130903 joined group as a replica.  Join consistencyPolicy = PointConsistencyPolicy targetVLSN = 843 395 first = 843, 326 last = 843, 395 sync = 843, txnEnd 395 = 843, 395

  130903 17:56:30:401 INFO [node04] refreshed 0 monitors.

  130903 17:56:30:922 WARNING [node04] likely to be elected changed size override group: 3

  130903 inactive channel INFO [node04] 17:57:55:223: node02 (64) forced close. Timeout: 7000ms.

  17:57:55:398 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:57:55:399 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:57:55:401 130903 INFO [node04] committed election; choice #2

  130903 17:57:55:401 INFO [node04] in the current election. Waiting...

  130903 17:57:55:406 INFO [node04] Started election thread kills Sep 03 17:57:55 CDT 2013

  17:58:08:101 130903 INFO [node04] master changed to node01

  17:58:08:102 130903 INFO [node04] completed election. Elapsed time: 12701ms

  17:58:08:102 INFO [node04] 130903 exit election after 2 attempts

  130903 17:58:08:102 INFO [node04] Replica loop started with master: node01 (61)

  130903 wire INFO [node04] election of 17:58:08:103 came out. Group master: node01 (61)

  17:58:08:110 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:08:110 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:08:111 INFO [node04] try again #: 0/10 retries loop replica after 1000ms.

  130903 17:58:09:111 INFO [node04] Replica loop started with master: node01 (61)

  17:58:09:114 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:09:114 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:09:114 INFO [node04] try again #: 1/10 retries loop replica after 1000ms.

  130903 17:58:10:115 INFO [node04] Replica loop started with master: node01 (61)

  17:58:10:117 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:10:118 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:10:118 INFO [node04] try again #: 2/10 retries loop replica after 1000ms.

  130903 17:58:11:118 INFO [node04] Replica loop started with master: node01 (61)

  17:58:11:121 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:11:121 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:11:122 INFO [node04] try again #: 3/10 retries loop replica after 1000ms.

  130903 17:58:12:122 INFO [node04] Replica loop started with master: node01 (61)

  17:58:12:125 INFO [node04] 130903 exit inner loop of the replica.

  130903 17:58:12:125 INFO [node04] try again #: 4/10 retries loop replica after 1000ms.

  130903 17:58:13:126 INFO [node04] Replica loop started with master: node01 (61)

  17:58:13:129 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:13:129 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:13:129 INFO [node04] try again #: 5/10 retries loop replica after 1000ms.

  130903 17:58:14:130 INFO [node04] Replica loop started with master: node01 (61)

  17:58:14:132 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:14:133 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:14:133 INFO [node04] try again #: 6/10 retries loop replica after 1000ms.

  130903 17:58:15:133 INFO [node04] Replica loop started with master: node01 (61)

  17:58:15:136 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:15:136 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:15:137 INFO [node04] try again #: 7/10 retries loop replica after 1000ms.

  130903 17:58:16:137 INFO [node04] Replica loop started with master: node01 (61)

  17:58:16:140 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:16:140 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:16:140 INFO [node04] try again #: 8/10 retries loop replica after 1000ms.

  130903 17:58:17:141 INFO [node04] Replica loop started with master: node01 (61)

  17:58:17:143 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:17:144 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  130903 17:58:17:144 INFO [node04] try again #: 9/10 retries loop replica after 1000ms.

  130903 17:58:18:145 INFO [node04] Replica loop started with master: node01 (61)

  17:58:18:147 INFO [node04] 130903 exit inner loop of the replica.

  130903 replica of the INFO [node04] 17:58:18:148 stats - Lag waiting: 0 Lag delay: 0ms.  VLSN waiting: 0 Lag delay: 0ms.

  17:58:18:148 130903 INFO [node04] could not recover from exception: failed after attempts: 10 with retry interval: 1000ms., despite 10 attempts.

  com.sleepycat.je.rep.impl.node.Replica$ ConnectRetryException: failed after attempts: 10 with retry interval: 1000ms.

  at com.sleepycat.je.rep.impl.node.Replica.createReplicaFeederChannel(Replica.java:777)

  at com.sleepycat.je.rep.impl.node.Replica.initReplicaLoop(Replica.java:578)

  at com.sleepycat.je.rep.impl.node.Replica.runReplicaLoopInternal(Replica.java:392)

  at com.sleepycat.je.rep.impl.node.Replica.runReplicaLoop(Replica.java:328)

  at com.sleepycat.je.rep.impl.node.RepNode.run(RepNode.java:1402)

  17:58:18:149 130903 INFO [node04] committed election; choice #3

  130903 17:58:18:149 INFO [node04] in the current election. Waiting...

  130903 17:58:18:150 INFO [node04] Started election thread kills Sep 03 17:58:18 CDT 2013

  .... Attempts and the ConnectRetryException repeat ad nauseam...

  The problem is that you touch a model not supported by violating the contract of the StateChangeListener by launching an expensive operation in the middle of the stateChange method. Of http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/StateChangeListener.html#stateChange (com.sleepycat.je.rep.StateChangeEvent), we caution:

  void stateChange(StateChangeEvent stateChangeEvent) throws RuntimeException
  

  ....

  This method should do the minimum amount of work, queuing any intensive operations of resource for processing by another thread before returning to appellant, so that it does not unduly delay the other cleaning operations performed by the internal thread that calls this method.

  In other words, we really mean the work done by stateChange shouldn't make any IO or network communication, and if he does, he should leave this thread back, and do the expensive work in another thread.

  It seems rather ironic, or that the introduction be DbPing or ReplicationGroupAdmin in our application code introduces a principle of Heisenberg uncertainty effect in which tent to observe the number of active nodes causes the behavior of replication group, or more precisely - creating channel charger - for change.    Is there a prohibition against using DbPing, ReplicationGroupAdmin or getNodeState() in an application node methods likely to be elected?   Do same using these objects/methods in a cause of app monitor a change in behavior among the nodes to be elected after an election?    We seem to be observing such behavior.

  While an application can certainly use DbPing or ReplicationGroupAdmin, the problem is that the state change listener runs in the critical path the replication group state changes. You talked about monitors and another model of watch and manage the replication group membership is to use http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/monitor/Monitor.html. This class and the MonitorStateChangeListener partner, run outside the ReplicatedEnvironment and could be another means of implementation of the application logic.

  So in summary, you should use com.sleepycat.je.rep.monitor.monitor * to implement your logic, or have the implementation of StateChangeListener cause another thread to perform work asynchronously, so that stateChange() can quickly return.

  Please let me know if it helps.

  Thank you

  Bogdan

• Creating a channel alpha in a weird way?

  My question is about the features of After Effects. I highly doubt it is possible, but I would run it through people who know. My question is perhaps not clear because I don't know how to describe it!

  I wonder if I can create an alpha channel using the bottom again at once, as an alternative to green screens and makes it easier for outside without the need of mad lights.

  Here is an example. Do you film yourself using a tripod (if the background is always) away from a building and want to add an explosion behind you without hiding all images, would you be able to recognize the background by using a picture without you in it, or one that has the same lighting and use it to have it automatically differentiate this context you thus creating an alpha channel or mask automatic...

  Thank you

  For a mast of difference to work absolutely nothing can move in the scene. Difference matte will not work with the compressed original film. I know I've tried several times. If the wind blows in the grass or trees are moving the difference Matte will not work.

  If you plan this kind of shot, then the best thing to do is try to find a few good areas of contrast in the shot, so you can create a procedure cache. A small cache of transparency and a procedure cache created by adjusting the levels or color or shade can create a much better Matt and does not rely on the pixels being exactly the same on each image.

  Even easier is a well-planned and the Roto brush.

• DAQmx create several channels of

  I downloaded the program entry OR bridge-continues and tries to modify it slightly to allow several Wheatstone bridges to connect. Currently, it has the ability to connect to a single channel but don't not to acquire information from several channels simultaneously. All information regarding the shunt calibration, bridge information and waveform graphic output remains the same. Ideally, the program displays the greatest value in the final waveform graph, but it is fine if it shows separate graphs for each of the two entrances. I was playing with it without much luck though if I start from scratch and you use the DAQ assistant, I'm able to get information without penalty. Any help would be appreciated.

  In fact you are 99.99% of the way.

  You just need to 4 characters

  

  The name filtering on this control is even properly defined to allow multiple selections and just shift click on the second channel

• How select specific channels attached to specific 'create virtual channel '.

  Dear user of LabView,

  I did a program of acquiring data of an LVDT, a forcecell and a strain gauge. I did so that I can add multiple LVDT and several gauges... So we can task 1 voltage and task 1 strain, but also multiple tasks of tension and the multiple tasks of strain...

  The problem is now I want to show these data on 3 different graphics, each task would have its own chart. But unfortunately I'm not able to choose which chart should show which task. I tried to do it with the index, it went good for when I had 1 each connected sensor, but when I joined an additional LVDT Sensor, so an additional channel, the sequence of my graphics moved to the top and there were only 3 channels appear instead of 4. I wanted to show the data from the sensors LVDT 2 1 graphic, and another chart for the forcecell and one for the strain.

  Is there a possibility to filter the tasks so that I can choose on which graphic task should work?

  I joined my program.

  With sincere friendships.

  Peter

  
  

• Can I use two 2 GB double-sided DDR2 memory stick sets in a motherboard ASUS 939 to create two-channel operation?

  939 supports up to 4 GB of RAM, also what DIMM slots I would use to achieve dual channel operation?

  Thank you.

  ~ kwduke

  Hello

  I suggest that you contact Asus support for assistance on this issue because the problem is with the motherboard.

  http://support.ASUS.com/contactus.aspx?SLanguage=en