Monitor 2 implementation

Similar Questions

• Monitor HPx2301: HP x 2301 spent 1920 x 1080 at 1024 x 768 resolution, and I can't go back

  My monitor is implemented alone since 1920 x 1080 60 Hz at 1024 x 768 60 Hz without reason and I can it switch back.

  When you switch on the monitor it flashes up a box indicating "current 1024 x 768 60 Hz" and recommended "1920 x 1080 Hz.

  But the list of display settings to select does not 1920 x 1080.

  Using HP Support I checked that I have the updated driver software for the monitor.

  I have been using Windows Home 64 bit several months 10.

  Please can someone help.

  Update... I managed to solve the problem in the Device Manager, uninstalling the driver Intel(r) HD Graphics (who had not been working properly and showed error code 43) and then seeking changes to the software (which is automatically loading a newer driver that seems to have solved the problem).

• best practices of command buttons

  Hello

  I would ask how others view their GUI with several command buttons (OK Boolean button).

  For example, it is a simple application where the user can start data acquisition by clicking on a button with text 'Start monitoring '. Instead of having another button with text "Stop monitoring", usually I just change the label text to "Stop monitoring" button, so it is obvious to the user that clicking on that will stop the process of monitoring the implementation (in the case of this button, I read the text of the actual label with property node in order to decide what message action to the loop the loop handler data acquisition of) GUI).

  If I have another button with the label as "Record of startup file" text, I do the same way: after saving the file, change the text 'Stop-save file.

  To avoid unnecessary additional programming, this button is in the enabled state if the application is already in the State of "monitoring". In addition, if there is a current folder (+ DAQ obviously), the user cannot press the button "stop monitoring". So according to the status of applications, some of the buttons are enabled, some in 'grey disabled' State.

  I wonder how others do their app/GUI?

  I don't know if it's a good way to do, but at least I can avoid check additional status of programming and by minimizing the number of buttons...

  I use the Boolean options text in the Properties menu where you can have different text for the States TRUE and FALSE to your buttons.  This eliminates some of the code that it sounds as you write.

  Play / Pause are the two options I usually use if buttons.

• HP a6567c problems with OS and recovery!

  So my desktop came with vista x 64 and it was not compatible with a lot of software that I was working with (audio recording/production). I downgraded to XP and found all the drivers appropriate successfully, but there was a big problem which, if I turned the monitor then next turn the system would block and I see a background with no icons and the manually restart the computer. This happens every time

  My first question is if there is a way to successfully run the XP on my a6567c? I had all the right drivers, but I do not leave the monitor on all the time to avoid the hit... I was running XP instead if possible

  Secondly, at the moment that I am trying to plant recover my original settings. I left the partition image factory of tact, but I guess I have no HP Recovery Assistant little more and cannot find a download for it. How can I recover my system? I tried to do from the start screen by pressing f11 but that doesn't work either...

  Help, please! and if anyone knows how to make XP pro stableon my machine, I'd be happy!

  1. strange problem I've ever seen. You manually turn off the monitor or implement power opt to let XP it turned off?

  You have the latest version of the Driver from Chipset Intel G33

  You have the latest version of the driver Nvidia graphics

  2. once change you the MBR on the use of drive C: F11 recovery no longer works, and as you saw the wizard also went... crushed by installing XP on C:. Did you by chance your Vista Recovery set before you install XP? Otherwise they can be ordered from HP at a low price

  .

  It is a procedure not supported (by HP) who has worked for many people. Use Disk Management in XP to view your hard disk partitions. Select the Recovery partition, right click and "Mark as active. To restart "without typing F11" the pc should start and start Vista recovery.

  http://www.theeldergeek.com/disk_management.htm

  Message edited by CherylG on 03/14/2009 10:05

• Update of the screen

  Hello

  I have two screens... screen1 and screen2.

  in screen1, I have a BasicEditField t1. by clicking on a button in screen1 I press control of screen1 to screen2.

  now, I've run a few screen2 logicin and now I want to set a value for BasicEditField which is in screen1 and I want to close this screen.

  I want to see the update in BasicEditField value.

  Please let me know how can I update the BasicEditField in anotherScreen...

  Thanks in advance

  Pass your first screen (dirty) object or a similar interface (cleaner) to your second monitor and implement a public method that you can call in your second screen.

  for example (without interface):
  in screen1
  {} public void update (String text)
  basicEditField.setText (text);
  }
  pushScreen (new Screen2 (screen1));
  in screen2
  Screen1. Update ("NewText");

  Read about callbacks, much of Google.

• Trouble with the voice and data Vlan vlan translate between CT3905 and SF300 - 24 p

  Hey actually, we have the solution to monitoring of implementation with CT3905 phone, SF300 - switches 24 p cameras and AIR-AP1041N Access Points

  

  We have the problem with the vlan tag in SF300 switch ports - 24 p we can´t tag vlan of the voice and data VLANs on the same port on SF300 - 24 p it is Possible or we must dedicate a port for each VLAN or ussing the same data segment of VLANs and vlan voice?

  Someone has an answer or technical documentation that can help us

  Best regards

  First of all,

  Please disable lldp transmit in SF 300 switch.

  The command is "no lldp transmitted."

  After you disable check the following steps.

  https://supportforums.Cisco.com/docs/doc-27005

  facing the same problem with cisco SG 300 and 3905 ip phone switch.

  And nested thing was my 7945 and 6941 phones use to work properly, without above configuration.

  Cisco 3905 became not vlan Ip address votes and even if I put static, it did not work.

  After a long struggle, I was able to solve the problem. Now both phone and system work fine in the same port.

  Samantha

• 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

• BAM works with the Oracle database only in the backend.

  Hi, I was wondering if Oracle Business Activity Monitor (BAM) implemented in ADF application works with the Oracle database as Oracle database is one of the databases very little supporting the database change Notification? Or can it be implemented using database of MySQL etc.
  
  Thank you!
  
  Published by: 996574 on June 3, 2013 14:06

  As far as I KNOW only Oracle db supports the database change Notification.

  Timo

• Implementation of two monitors multiple questions

  I tried to set up two monitors - however - the display screen where I can change the appearance of the poster ends up on my HP Envy laptop screen and my mouse cursor on my Dell monitor screen and won't get to the laptop screen - so I can't do the implementation. I hope someone can help me with this. Thank you

  I tried to set up two monitors - however - the display screen where I can change the appearance of the poster ends up on my HP Envy laptop screen and my mouse cursor on my Dell monitor screen and won't get to the laptop screen - so I can't do the implementation. I hope someone can help me with this. Thank you

  Hello

  Have tried to move the mouse cursor on both sides of the screen to the external monitor?

  When you move the cursor beyond the external screen left or right border, it should appear on the screen of the laptop.

  Let us know.

  Concerning

• HP ENVY x 360-15-u011dx Touch: help the implementation of multiple external monitors

  recently bought a HP ENVY laptop touch 360-15-u011dx x. Try to put in place two external monitors with a HDMI splitter. I can "extend" office, but both screens display the same image, which is not what I want. Can I set up two external monitors with this laptop using a separator (that was what I was told would work when I bought the unit and both monitors.)  Computers portable precedents had ports HDMI and VGA that allows two monitors.  This laptop (and most recent) no longer have a VGA port.

  Hello

  If you want 2 external monitors to have different point of view, you need two different outputs. Two monitors of a same source cannot have 2 times. My cheap suggestion: buy a cheap USB - DVI Cela will fix the problem. I did a test using a cheap DisplayLink and get:

  

  The central screen is the screen of my laptop

  Kind regards.

• Monitor Dell 02415... stupid mistake, I can't get on so that the implementation of new

  Hello
  Setting up this monitor today with my Mac Mini for 2012, I have seem to inadvertently disrupted the input setting and cannot be changed again.

  I managed to set up and it was all working earlier today, and the only question is what I did!

  I was browsing the display of OSD settings and I think I have 'activated' the DisplayPort 1.2 setting.   He warned me something on the graphics card (I guess my mini Mac would hae appropriate card) and the screen may be blank. He did, and now I can't work again.

  Now, it is said that is to enter a message or says the energy saving mode press the monitor button to reset the input device.    The only control OSD, it will allow me to do this is to change the entry.

  When I select the top of the page 'DL' which is what he worked on before, it makes no change.

  It doesn't let me access the rest of the OSD menu to factory reset.

  I tried the unplug all cables, turn off and hold down the power button for 15 sec without change.

  It is a brand new monitor and I'e lost hours of my day's work, already - I'm so angry at myself for doing this and now I hope that someone can help me to get it sorted as soon as possible and all simply.

  Thanks in advance

  Adrian

  I think you mean "U2415"?

  From the manual page 29, change to Disable =

  

• implementation monitoring and alerts SLA through the Workspace studio

  Hello
  Is it possible game of replicas and alert rules SLA through the studio of the workspace. If so, could you please help me how do.
  Thank you
  James

  Hello..

  Operational parameters such as active, tracing, monitoring etc. are easily defined within eclipse by editing with the text rather than the proxy editor editor...

  SLA alerts are possible to change in the same way, but they are a little more complicated to understand.

  .. Select this option.

• How to document the application to another monitor

  I have a setup of 3 monitor for work. I need to have my video capture software, Media Express, on the primary and secondary monitor. On my 3rd monitor, I wish I had Final Cut for editing.

  Does anyone have a solution for this?

  In setting system preferences displays, displays as an extended desktop, and then drag one poster rather than another. For more information, scroll down to the last section on how to "implement some screens for implementing mirrored and extended desktop":

  Connect multiple monitors to your Mac

  https://support.Apple.com/kb/PH19039

• Third monitor does not work with Eyefinity more

  I am trying to run 3 monitors on my ATI HD 5770

  I have two computers that, for years, have worked with several thin monitors... until very recently.  Through all my updates to the OS, they continued to work.  I don't remember exactly at what time each card has ceased to power its third monitor.  Each of my "third monitors" would come on periodically until they all finally stopped.

  All monitors are working fine as I juggle the cables and adapters each refreshes and lights up but not all at the same time.

  Here's what I have available for troubleshooting.

  I have two Mac Pros below.  (OS 10.11.6) on one and (OS 10.7.5) on the other.

  Each tower has (2) 5770 cards installed that each have a DVI and 2 mini ports.

  So I have a total of (4) cards and is starting the new one that I got on ebay last week.

  I have LG E2350V 23 "monitors (6) and (3) 22" ACER monitors

  All my cables are active and I have several active adapters

  I just bought some passive extra and many very active adapters to the experience and trouble shooting with.

  Thanks in advance for the help and time!

  DisplayPort and its variant electrically identical but small size Mini DisplayPort and the implementation which is a subset of Thunderbolt, any differential use (push-pull) of signals pilot very low voltage. They are MORE immune to noise than old methods because the signal is encoded on the difference between the two signals, not a single signal referenced to a "everybody" on the ground. If possible, you must connect all screens with DisplayPort [full-size] or Mini DisplayPort. These put a lot less load on your system.

  When you convert this very low level signal to an "inherited" display, the map is short of ability to directly signal levels in the car high enough to be recognized after connection of TWO monitors legacy of any kind. If you choose to use a DVI or HDMI port supplied directly, that still counts as one of your two "free" conversions (It is also possible that a very fussy display is moved even earlier).

  All display "legacy" beyond the first two requires ACTIVE description adapters. Adapters ASSETS contain re-drivers of signal and are therefore more expensive than ordinary adapters. Typical prices are of the order of $ 40, but competition has lowered some prices slightly. Mini DisplayPort has a descendant-comparability mode requested by the regular cards, who can get to produce a Single-Link DVI signal to up to 1920 wide, but a regular adapter not pushed the signal levels.

  The Apple Mini DisplayPort to DVI Dual-Link, which is used for DVI displays wider width of 1920, is more complex and expensive and requires extra power beyond all signal re-pilots. This power is usually taken on a tail of pig USB, USB data are generally not used by the adapter, so a different USB power source can be overridden.

• Dell U2715H as second monitor sleep problem

  I just bought a Dell U2715H monitor to connect to my iMac 27 "mid-2010.

  Implementation, the system works beautifully. Plug n play, as we are accustomed to the Apple universe.

  But after an automatic start, this morning, the Dell remained black, what I tried.

  A phone call with the helpdesk Dell did not bring a solution; they are willing to trade for a new monitor, but I think not (just a feeling) which will tackle the problem.

  After having a cup of coffee, I came back to my Mac, who had fallen asleep in the meantime.

  Pressing a button all of life, including (surprise) the Dell monitor system.

  After a few experiences, I discovered that after a reboot, the Dell remains black.

  Put the system to sleep (using a hot corner) and pressing a key is not wake up the Dell.

  Bringing the system to sleep and pressing a button after waiting 10-20 seconds, puts the entire system, including the Dell monitor.

  The monitor is connected to a mid 2010 iMac 27 "2.93 GHz Intel Core i7, with a miniDP to DP cable.

  Although I found this 'solution' after hours of frustrating attempts, it feels a bit inadequate.

  Anyone who is familiar with this problem who found a more definitive solution?

  Reset the SMC of the iMac, as in > reset the management system (SCM) controller on your Mac - Apple Support

  and discover > get help with graphics issues on external displays connected to your Mac - Apple Support