FCS 3 (or call it Upgrade!) Well-known Long Pauses during Installation

Does anyone know if the issue with the 'long pauses' of the progress bar hitting 100% during the installation of components and discs still exists during the Installation of FCS3? Just want to know what to expect!
This was well-known for FCS2 I seem to remember.
thanks.

Hi,
What exactly are you experiencing with FxFactory? Please do contact [email protected] if you are having any problems at all with FxFactory after the Final Cut Studio Upgrade.
Thanks so much,
Niclas

Similar Messages

  • Well known scam called my home phone from a Skype ...

    Hi,
    Recently I have been contacted 2 or 3 times a day at my home phone number from 'Computer Maintenance Department' or 'Windows Department', claiming my computer was sending them error messages. The latest phonecall came from Skype number 001 956 460 5604.
    This is a well known scam where the perpetrators aim to convince their victims that their computer has a virus and then persuade them to allow remote access in order to 'fix' the problem.
    As this came from a Skype number, how do I go about reporting this?

    Let me add to my earlier response.   DO not even attempt to discuss this matter with comcast or their techs. They simply are unaware of the problem and can do nothing to fix it. Call Neustar at the number I gave you in ealrier post..  Tell them the problem and either have them delete your cellphone number from their data base or set the caller id to show city, state and your number.  Deletion is probably better. Tech at Neustar did this told it would take effect in two hours and the problem was gone in 5 minutes. I am sick and tired of disconnects, talking to techs at comcast who barely can speak english, mumble, one told me today to go to the website and disable call blocking from my cell then call  home and then reenable it after making the call.  LMAO!   Yeah, while driving down the road. This afternoon I got a call from a  rather arrogant tech who didn;t want to hear the problem, didn;t undertand the problem and tried to blame the problem on my cell service.  No problem when I call anyone outside of Comcast and it was corected once before .   So the problem is with your cell phone number listing at Neustar.  Since Comcast uses Neustar for their caller id numbers they should be be able to delete or correct entires but apparently cannot.   Good Luck, my days with comcast are limited.

  • Is there a reason why well-known-address config option requires enterprise?

    Looking at the documentation for the well-known-address config option the unicast listener - it states
    >
    Use of the Well Known Addresses (WKA) feature requires a Coherence Enterprise License.
    Why is an enterprise license required for such a mundane feature? (asking because we bought clustered edition licenses and our network admins are asking about the multicast traffic).

    Hi George,
    This is really not a technical question. I will give you a call to discuss the rationale.
    Stephan
    Tangosol Sales

  • Installation Problems of SAP CE 7.1 SP3 (Dev. Ed.) "well-known groups"

    Hi,
    I tried to install NW CE on XP prof. (german), I received an error while doing the "Prerequisite Checker" :
    Checking the names of selected well-known groups. The following names were expected:
         "everyone, users, guests, power users".
    The following names were found:
         "jeder, benutzer, gäste, hauptbenutzer".
    If they do not match, it is most probably because you are not using an English
    international version of Windows but a localized one instead.
    Only English international versions of Windows are supported.
    Is there any workaround for german XP systems ?
    regards
    Gabor nemes

    Hi Oliver,
    Thanks for the reply!
    I have login into the system, using User Id and Password.
    I have tried unsinstalling everything but the result remains the same.
    Previously only one service SAPCE_01 was showing up in the services explorer. But when I tried the
    Instance 00:
    sc create SAPRKT_00 binPath= "C:\usr\sap\RKT\SYS\exe\uc\NTI386\sapstartsrv.exe pf=C:/usr/sap/RKT/SYS/profile/CE1_SCS00_xxxxx" start= auto obj= "NT AUTHORITY\LocalService" password= abcd1234
    Instance 01:
    another service SAPCE1_00 was created. But when I tried to retry the instlattio, the installation again stopped at the point while starting the service and when I tried to retry it terminted with the following error.
    Please guide.
    sapinst.exe - Application Error
    The instruction at "0x00cbf040" referenced memory at "0x0072006d". The memory could not be "read".
    Click on OK to terminate the program
    Click on CANCEL to debug the program
    Selfextractor error
    iaextract.c:888: child has signaled an exec error. Keeping directory C:/DOCUME1/I047488/LOCALS1/Temp/sapinst_exe.1448.1196681060
    OK  
    Manish

  • Issue to setup local Coherence cluster with WKA (well-known-address)

    Hello - I have started local coherence cluster using WKA with single node,but when I start CacheFactory (coherence.cmd) with same configuration it throws following error message.
    Any help is appricicated.
    JVM startup Arrgument
    -Dtangosol.coherence.override=cluster.xml
    cluster.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <coherence xmlns="http://xmlns.oracle.com/coherence/coherence-operational-config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-operational-config http://xmlns.oracle.com/coherence/coherence-operational-config/1.1/coherence-operational-config.xsd">
    <cluster-config>
      <unicast-listener>
       <well-known-addresses>
        <socket-address id="1">
         <address>171.193.103.25</address>
         <port>8088</port>
        </socket-address>
       </well-known-addresses>
          </unicast-listener>
    </cluster-config>
    <logging-config>
      <destination>stdout</destination>
      <severity-level>9</severity-level>
    </logging-config>
    </coherence>
    Cluster startup Message
    WellKnownAddressList(Size=1,
      WKA{Address=171.193.103.25, Port=8088}
    MasterMemberSet(
      ThisMember=Member(Id=1, Timestamp=2013-10-24 11:07:18.603, Address=171.193.103.25:8088, MachineId=9041, Location=site:,machine:FD4C9EF534D5D,process:16704, Role=CoherenceServer)
      OldestMember=Member(Id=1, Timestamp=2013-10-24 11:07:18.603, Address=171.193.103.25:8088, MachineId=9041, Location=site:,machine:FD4C9EF534D5D,process:16704, Role=CoherenceServer)
      ActualMemberSet=MemberSet(Size=1
        Member(Id=1, Timestamp=2013-10-24 11:07:18.603, Address=171.193.103.25:8088, MachineId=9041, Location=site:,machine:FD4C9EF534D5D,process:16704, Role=CoherenceServer)
      MemberId|ServiceVersion|ServiceJoined|MemberState
        1|3.7.1|2013-10-24 11:07:48.843|JOINED
      RecycleMillis=1200000
      RecycleSet=MemberSet(Size=0
    TcpRing{Connections=[]}
    IpMonitor{AddressListSize=0}
    2013-10-24 11:07:48.869/31.794 Oracle Coherence GE 3.7.1.0 <D5> (thread=Invocation:Management, member=1): Service Management joined the cluster with senior service member 1
    2013-10-24 11:07:49.058/31.983 Oracle Coherence GE 3.7.1.0 <D5> (thread=DistributedCache, member=1): Service DistributedCache joined the cluster with senior service member 1
    2013-10-24 11:07:49.077/32.002 Oracle Coherence GE 3.7.1.0 <D6> (thread=DistributedCache, member=1): Service DistributedCache: sending PartitionConfig ConfigSync to all
    2013-10-24 11:07:49.121/32.046 Oracle Coherence GE 3.7.1.0 <D5> (thread=ReplicatedCache, member=1): Service ReplicatedCache joined the cluster with senior service member 1
    2013-10-24 11:07:49.128/32.053 Oracle Coherence GE 3.7.1.0 <D5> (thread=OptimisticCache, member=1): Service OptimisticCache joined the cluster with senior service member 1
    2013-10-24 11:07:49.131/32.056 Oracle Coherence GE 3.7.1.0 <D5> (thread=Invocation:InvocationService, member=1): Service InvocationService joined the cluster with senior service member 1
    2013-10-24 11:07:49.132/32.057 Oracle Coherence GE 3.7.1.0 <Info> (thread=main, member=1):
    Services
      ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_JOINED), Id=0, Version=3.7.1, OldestMemberId=1}
      InvocationService{Name=Management, State=(SERVICE_STARTED), Id=1, Version=3.1, OldestMemberId=1}
      PartitionedCache{Name=DistributedCache, State=(SERVICE_STARTED), LocalStorage=enabled, PartitionCount=257, BackupCount=1, AssignedPartitions=257, BackupPartitions=0}
      ReplicatedCache{Name=ReplicatedCache, State=(SERVICE_STARTED), Id=3, Version=3.0, OldestMemberId=1}
      Optimistic{Name=OptimisticCache, State=(SERVICE_STARTED), Id=4, Version=3.0, OldestMemberId=1}
      InvocationService{Name=InvocationService, State=(SERVICE_STARTED), Id=5, Version=3.1, OldestMemberId=1}
    Started DefaultCacheServer...
    Error Message from CacheFactory
    C:\Users\Zk5rjg8>C:\coherence37\bin\coherence.cmd
    ** Starting storage disabled console **
    java version "1.6.0_51"
    Java(TM) SE Runtime Environment (build 1.6.0_51-b11)
    Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01, mixed mode)
    2013-10-24 11:13:22.851/0.392 Oracle Coherence 3.7.1.0 <Info> (thread=main, member=n/a): Loaded operational configuration from "jar:file:/C:/coherence37/lib/coherence.jar!/tangosol-coherence.xml"
    2013-10-24 11:13:22.920/0.462 Oracle Coherence 3.7.1.0 <Info> (thread=main, member=n/a): Loaded operational overrides from "file:/C:/coherence37/cluster.xml"
    2013-10-24 11:13:22.924/0.465 Oracle Coherence 3.7.1.0 <D5> (thread=main, member=n/a): Optional configuration override "/custom-mbeans.xml" is not specified
    2013-10-24 11:13:22.924/0.465 Oracle Coherence 3.7.1.0 <D6> (thread=main, member=n/a): Loaded edition data from "jar:file:/C:/coherence37/lib/coherence.jar!/coherence-grid.xml"
    Oracle Coherence Version 3.7.1.0 Build 27797
    Grid Edition: Development mode
    Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.
    2013-10-24 11:13:23.722/1.263 Oracle Coherence GE 3.7.1.0 <D4> (thread=main, member=n/a): TCMP bound to /171.193.103.25:8090 using SystemSocketProvider
    2013-10-24 11:13:54.001/31.542 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): This Member(Id=0, Timestamp=2013-10-24 11:13:23.762, Address=171.193.103.25:8090, MachineId=9041, Location=site:,machine:FD4C9EF534D5D,process:17192, Role=CoherenceConsole) has been attempting to joi
    2013-10-24 11:13:54.001/31.542 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:14:24.402/61.943 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:14:54.805/92.346 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:15:25.207/122.748 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:15:55.610/153.151 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:16:26.012/183.553 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:16:56.414/213.955 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:17:26.817/244.358 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:17:57.219/274.760 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; waiting for well-known nodes to respond
    2013-10-24 11:17:58.271/275.812 Oracle Coherence GE 3.7.1.0 <Error> (thread=Cluster, member=n/a): Detected soft timeout) of {WrapperGuardable Guard{Daemon=IpMonitor} Service=ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_ANNOUNCE), Id=0, Version=3.7.1}}
    2013-10-24 11:17:58.273/275.814 Oracle Coherence GE 3.7.1.0 <Error> (thread=Recovery Thread, member=n/a): Full Thread Dump
    Thread[PacketListener1,8,Cluster]
            java.net.PlainDatagramSocketImpl.receive0(Native Method)
            java.net.PlainDatagramSocketImpl.receive(Unknown Source)
            java.net.DatagramSocket.receive(Unknown Source)
            com.tangosol.coherence.component.net.socket.UdpSocket.receive(UdpSocket.CDB:22)
            com.tangosol.coherence.component.net.UdpPacket.receive(UdpPacket.CDB:1)
            com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketListener.onNotify(PacketListener.CDB:20)
            com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
            java.lang.Thread.run(Unknown Source)
    Thread[PacketReceiver,7,Cluster]
            java.lang.Object.wait(Native Method)
            com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
            com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketReceiver.onWait(PacketReceiver.CDB:2)
            com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
            java.lang.Thread.run(Unknown Source)
    Thread[Attach Listener,5,system]
    Thread[PacketPublisher,6,Cluster]
            java.lang.Object.wait(Native Method)
            com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
            com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketPublisher.onWait(PacketPublisher.CDB:2)
            com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
            java.lang.Thread.run(Unknown Source)
    Thread[Cluster|STATE_ANNOUNCE|Member(Id=0, Timestamp=2013-10-24 11:13:23.762, Address=171.193.103.25:8090, MachineId=9041, Location=site:,machine:FD4C9EF534D5D,process:17192, Role=CoherenceConsole),5,Cluster]
            sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
            sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(Unknown Source)
            sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(Unknown Source)
            sun.nio.ch.WindowsSelectorImpl.doSelect(Unknown Source)
            sun.nio.ch.SelectorImpl.lockAndDoSelect(Unknown Source)
            sun.nio.ch.SelectorImpl.select(Unknown Source)
            com.tangosol.coherence.component.net.TcpRing.select(TcpRing.CDB:11)
            com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.ClusterService.onWait(ClusterService.CDB:6)
            com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
            java.lang.Thread.run(Unknown Source)
    Thread[Reference Handler,10,system]
            java.lang.Object.wait(Native Method)
            java.lang.Object.wait(Object.java:485)
            java.lang.ref.Reference$ReferenceHandler.run(Unknown Source)
    Thread[Finalizer,8,system]
            java.lang.Object.wait(Native Method)
            java.lang.ref.ReferenceQueue.remove(Unknown Source)
            java.lang.ref.ReferenceQueue.remove(Unknown Source)
            java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)
    Thread[Signal Dispatcher,9,system]
    Thread[PacketSpeaker,8,Cluster]
            java.lang.Object.wait(Native Method)
            com.tangosol.coherence.component.util.queue.ConcurrentQueue.waitForEntry(ConcurrentQueue.CDB:16)
            com.tangosol.coherence.component.util.queue.ConcurrentQueue.remove(ConcurrentQueue.CDB:7)
            com.tangosol.coherence.component.util.Queue.remove(Queue.CDB:1)
            com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketSpeaker.onNotify(PacketSpeaker.CDB:21)
            com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
            java.lang.Thread.run(Unknown Source)
    Thread[Logger@1457155060 3.7.1.0,3,main]
            java.lang.Object.wait(Native Method)
            com.tangosol.coherence.component.util.Daemon.onWait(Daemon.CDB:18)
            com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:39)
            java.lang.Thread.run(Unknown Source)
    Thread[PacketListener1P,8,Cluster]
            java.net.PlainDatagramSocketImpl.receive0(Native Method)
            java.net.PlainDatagramSocketImpl.receive(Unknown Source)
            java.net.DatagramSocket.receive(Unknown Source)
            com.tangosol.coherence.component.net.socket.UdpSocket.receive(UdpSocket.CDB:22)
            com.tangosol.coherence.component.net.UdpPacket.receive(UdpPacket.CDB:1)
            com.tangosol.coherence.component.util.daemon.queueProcessor.packetProcessor.PacketListener.onNotify(PacketListener.CDB:20)
            com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
            java.lang.Thread.run(Unknown Source)
    Thread[main,5,main]
            java.lang.Object.wait(Native Method)
            com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:18)
            com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
            com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:56)
            com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
            com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
            com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
            com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
            com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
            com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
            com.tangosol.coherence.component.application.console.Coherence.run(Coherence.CDB:25)
            com.tangosol.coherence.component.application.console.Coherence.main(Coherence.CDB:3)
            sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
            sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
            java.lang.reflect.Method.invoke(Unknown Source)
            com.tangosol.net.CacheFactory.main(CacheFactory.java:827)
    Thread[Recovery Thread,5,Cluster]
            java.lang.Thread.dumpThreads(Native Method)
            java.lang.Thread.getAllStackTraces(Unknown Source)
            com.tangosol.net.GuardSupport.logStackTraces(GuardSupport.java:810)
            com.tangosol.internal.net.cluster.DefaultServiceFailurePolicy.onGuardableRecovery(DefaultServiceFailurePolicy.java:44)
            com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$WrapperGuardable.recover(Grid.CDB:1)
            com.tangosol.net.GuardSupport$Context$1.run(GuardSupport.java:653)
            java.lang.Thread.run(Unknown Source)
    2013-10-24 11:17:58.273/275.814 Oracle Coherence GE 3.7.1.0 <Warning> (thread=Recovery Thread, member=n/a): Attempting recovery of Guard{Daemon=IpMonitor}
    Exception in thread "main" 2013-10-24 11:18:24.025/301.566 Oracle Coherence GE 3.7.1.0 <Error> (thread=main, member=n/a): Error while starting cluster: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=MasterMemberSet(
        ThisMember=null
        OldestMember=null
        ActualMemberSet=MemberSet(Size=0
        MemberId|ServiceVersion|ServiceJoined|MemberState
        RecycleMillis=1200000
        RecycleSet=MemberSet(Size=0
            at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
            at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
            at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
            at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:56)
            at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
            at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
            at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
            at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
            at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
            at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
            at com.tangosol.coherence.component.application.console.Coherence.run(Coherence.CDB:25)
            at com.tangosol.coherence.component.application.console.Coherence.main(Coherence.CDB:3)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
            at java.lang.reflect.Method.invoke(Unknown Source)
            at com.tangosol.net.CacheFactory.main(CacheFactory.java:827)
    java.lang.reflect.InvocationTargetException
    2013-10-24 11:18:24.025/301.566 Oracle Coherence GE 3.7.1.0 <D5> (thread=Cluster, member=n/a): Service Cluster left the cluster at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
            at java.lang.reflect.Method.invoke(Unknown Source)
            at com.tangosol.net.CacheFactory.main(CacheFactory.java:827)
    Caused by: com.tangosol.net.RequestTimeoutException: Timeout during service start: ServiceInfo(Id=0, Name=Cluster, Type=Cluster
      MemberSet=MasterMemberSet(
        ThisMember=null
        OldestMember=null
        ActualMemberSet=MemberSet(Size=0
        MemberId|ServiceVersion|ServiceJoined|MemberState
        RecycleMillis=1200000
        RecycleSet=MemberSet(Size=0
            at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onStartupTimeout(Grid.CDB:3)
            at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:28)
            at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
            at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:56)
            at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
            at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
            at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
            at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
            at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2)
            at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:427)
            at com.tangosol.coherence.component.application.console.Coherence.run(Coherence.CDB:25)
            at com.tangosol.coherence.component.application.console.Coherence.main(Coherence.CDB:3)
            ... 5 more
    C:\Users\Zk5rjg8>

    Hi SajeevPynadath
    1
    First start the server process  with "cache-server.cmd"
    2
    After that you can start another server or client process,  the "coherence.cmd" script is to start a client process to join the cluster .
    3
    Then now you have 2 processes , and your cluster.xml will look like this :
    <socket-address id="serverprocess">
         <address>171.193.103.25</address>
         <port>8088</port>
        </socket-address>
    <socket-address id="clienprocess">
         <address>171.193.103.25</address>
         <port>8089</port>
        </socket-address>
    4
    Before start each process remember put in java command line :
    for server
    -Dtangosol.coherence.localhost=171.193.103.25 -Dtangosol.coherence.localport=8088
    for client
    -Dtangosol.coherence.localhost=171.193.103.25 -Dtangosol.coherence.localport=8089
    regards,
    Leo_TA

  • Wireless clients not trusting well-known Certificate Authorities by default??

    I'm using PEAP-MSCHAPv2 for wireless authentication.  The radius server is a Windows 2008 server running NPS.  The clients consist of a bunch of laptops (mostly running Windows).  Not all of these laptops are members of Active Directory.  So, pushing any type of policy out to all clients isn't feasible (ie. using a private PKI and using AD to push the server cert and wireless config to all domain members).  So we decided to use a public PKI and obtained a certificate for our radius server through a well known CA.  So far, so good.
    When clients to go connect, they still get a nasty warning saying:
    --START--
    The credentials provided by the server could not be validated. We recommend that you terminate the connection and contact your administrator with the information provided in the details. You may still connect but doing so exposes you to security risk by a possible rogue server.
    Details
    Radius Server:           $radius
    Root CA:                    $ca
    The server "$radius" presented a valid certificate issued by "$ca", but "$ca" is not configured as a valid trust anchor for this profile. Further, the server "$radius" is not configured as a valid NPS server to connect to for this profile.
    --STOP--
    (I replaced the actual radius server name with $radius and the CA with $ca).
    Doing a little digging, it appears this is just the expected behavior of the Windows wireless client???  What's the point of getting a signed cert by a well-known CA if the client is still going to get a nasty warning like this?
    Web browsers certainly don't behave like this.  The only difference between a web browser and the wireless client is with a browser, you're always going after a URL (ie, you can match what the browser wants to connect to versus what the CN on the server's cert comes back with) whereas on the wireless client, you generally won't know the radius server you're going to authenticate against.  But, in either scenario, the server's cert is signed by a well known CA.
    I found a nice post that mentions this, but no solution:
    http://social.technet.microsoft.com/Forums/en/winserverNIS/thread/26886f09-e424-48da-9ecc-cf7efd9dccc0
    Well, I suppose a solution is to manually configure the client to trust certs issued by the CA and/or configure my radius server in the connection profile.  But that requires configuring each client.  And there's no way we can use AD to push a policy/cert to all clients.
    So my questions are:
    -is this really the expected behavior?
    -so browsers generally trust the default CAs whose certs are stored on the OS by default but the wireless adapters don't?

    This is a limitation of the Windows wireless client.
    http://support.microsoft.com/kb/2518158
    Somewhere was an artical the described that Microsoft wirless client does not trust public root CAs by default.  Using a 3rd party utility like Intel Pro Set trusts all the 3rd party root CAs by default so you dont get this message.
    Please respond to Microsoft and voice your problem maybe they will fix their wireless client to trust public root CAs.
    Justin.

  • [N97 mini - UPDATED] Well known bug: "camera alrea...

    I updated my N97 mini device to latest fw which is 30.04.
    Like whenever I capture image with my camera, after capturing image I can't interact with the handset.
    Rather it shows "camera already in use".
    I have to wait a lot more rather usual time in order to delete captured image or interact. Is there any solution of this?
    I heard of some mod which arent authorized can fix it. But i don't trust those, neither I think is acceptable to be forced to put "custom" firmware to solve a problem Nokia should have fixed asap.
    Of course I won't buy another Nokia cellphone anymore and I will discourage friends (and they are really many) to do the same because of lack of support.
    Please:
    - don't tell me it is a problem of my phone because it is not (all people with N97 mini have the same problem)
    - don't tell me to reset it or to re-update firmware because it is useless (and I have already tried it)
    - tell me you are awared of the problem and it will be fixed in the next coming firmware release because it is the only thing worth saying
    Thanks for your attention and availability.
    Goodbye.

    Same problem here.
    Nokia Developers;
    Sir/s Maam/s..
    No particular software updates from Nokia in order to fix this "Well known BUG Problem"?
    --thanks..

  • Vista x64, Dell Laptop Lately I have been getting audio ads from Lysol etc which I can stop by deleting the process plug-in container Iknow how to delete this process but why does the audio ad run despite the application of two well known antivirus progs?

    Vista x64, Dell Laptop Lately I have been getting audio ads from Lysol etc which I can stop by deleting the process plug-in container Iknow how to delete this process but why does the audio ad run despite the application of two well known antivirus progs?

    Oh, PLEASE IGNORE the line:
    deleted everything under HKLM\SYSTEM\CurrentControlSet\Enum\Root\SYSTEM (folders 0000 to 0004)
    That was left there inadvertedly. Can't seem to find the edit button here...

  • I have Soundtrack Pro 1.1 It opens OK but the everything takes 4 seconds to work. It's very slow and unusable. Is this a well known problem?

    I have Soundtrack Pro 1.1 It opens OK but the everything takes 4 or so seconds to work. It's very slow and unusable in its present state. Is this a well known problem?

    STP 3.0.1 was the version designed to work with OSX 10.6.8. Anything earlier than that and issues may arrise. Hard to tell what yours are.
    You may want to run Digital Rebellion's Preference Manager to reset the prefs back to the default state. If nothing else, it is a good troubleshooting step.
    Good luck.
    x

  • Does XE include well-known text for polygon vertices?

    I have installed OracleXE on my ubuntu laptop, and have everything configured and working nicely. I am using many of the functions of locator for a university project I'm working on. I have many polygons stored in my database, and I would like to extract their vertices in well-known text (wkt) format, but for some reason the query returns a blank result.
    I can run a getvertices query, and extract all the polygon vertices in this format, but I would prefer to be working with wkt. When I run my wkt query I just get one blank row for every polygon in the database. I am confident that my query is suitable, and that the metadata for these polygons is set up right. I can only assume that oracle XE doesn't include the wkt functionality, though if this is the case, why does it return blanks, rather than an error?
    Any help with this would be greatly appreciated.
    tom

    See Reference for SDO_ELEM_INFO, SDO_UTIL and SDO_GEOM in Spatial User's Guide and Reference.
    XE supports Oracle Locator - one subset of Spatial.
    You can also search this Forum for: SDO_GEOMETRY
    HTH

  • UnknownHostException when using well-known-addresses prevents startup

    We found an issue that seems like a bug in Coherence.
    We are using well-known-addresses instead of multicast server discovery. Everything worked great, until one of the servers that used to be in the list was removed from DNS. We are no longer able to start the grid. The exception is
    Error while starting cluster: (Wrapped: Invalid configuratio
    n element: <socket-address id='1'>
    <address>SERVER1</address>
    <port>9999</port>
    </socket-address>) java.net.UnknownHostException: SERVER1
    at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
    at com.tangosol.net.ConfigurableAddressProvider.configure(ConfigurableAd
    dressProvider.java:196)
    at com.tangosol.net.ConfigurableAddressProvider.<init>(ConfigurableAddre
    ssProvider.java:50)
    at com.tangosol.net.ConfigurableAddressProvider.createAddressProvider(Co
    nfigurableAddressProvider.java:227)
    We have other hosts in the list that are still available. My understanding, is that as long as one host is available, we should be able to start the grid. If Server1 is not available in DNS, Server2, Server3, and Server4 should still be able to start.

    This issue has been resolved in 3.5.1.
    Thanks,
    Mark
    Oracle Coherence

  • Multicast vs Well known address

    Couple of questions regarding the multicast communication in a Coherence 3.3 cluster
    - What are the downsides of using the well known address scheme compared to multicast for cluster communication. One i could think of was having to explicitly specify all the addresses that need to be part of the cluster. Was wondering if there were any performance related differences?
    - What is the amount of multicast traffic that is handled by a member of the Coherence cluster which participates without having any local data stored? Is every message that is sent to the data storage members also sent to the non-data members
    Thanks
    Ramdas

    Hi Ramdas,
    What are the downsides of using the well known address scheme compared to multicast for cluster communication. One i could think of was having to explicitly specify all the addresses that need to be part of the cluster. Was wondering if there were any performance related differences?
    You don't need to list all addresses, only a subset of servers that is sufficiently large to guarantee that at least one server will be up at all times. Membership data in Coherence is entirely dynamic, so once a client connects to any of those servers, it will make introductions to the rest. For more details, please see:
    http://wiki.tangosol.com/display/COH33UG/well-known-addresses
    Using well-known-addresses (WKA) completely disables multicast, both for discovery of members and for communication of data. Discovery itself is a fairly inexpensive process. While Coherence relies mostly on point-to-point communication (it automatically selects the most efficient combination of unicast and multicast), there are use cases that require messages to be sent to all nodes (for example, cluster membership information). As you can imagine, if the sending node must send the same data to all other nodes, using unicast is going to be far more expensive that multicast as the cluster size increases (e.g. we've found that in clusters of 1000+ JVMs, the load on the sending member is a significant problem).
    Another way of looking at this ... for one-to-all communications (or even one-to-many), with multicast enabled, the switch is effectively acting as a "hardware accelerator" ... if you disable multicast, then you are emulating that behavior in software, which is obviously going to be less efficient (the sender will have the send the same packet to the switch N times (e.g. 1000 in the example above) rather than once).
    Fortunately, for a lot of workloads, this isn't as critical, especially for ones that have strong data affinity (e.g. only a few nodes are working with each piece of data).
    What is the amount of multicast traffic that is handled by a member of the Coherence cluster which participates without having any local data stored? Is every message that is sent to the data storage members also sent to the non-data members
    Aside from membership events (which are global), storage-enabled nodes really only use multicast to notify other nodes when data changes, and this only occurs if multicast is deemed more efficient than unicast (e.g. if there are a lot of subscribers interested in the changed data).
    Storage-disabled nodes (clients) will receive (some) multicast traffic for change events. If there isn't good data affinity (e.g. a lot of client-side near caches have overlapping data), then chances are that the storage nodes will be broadcasting data updates rather than sending them individually, and so there will be some multicast packets that need to be ignored (which is relatively inexpensive).
    Jon Purdy
    Oracle

  • Well Known Address (wka) issue

    Hi,
    I am hitting some issues whilst trying to configure and use multiple wkas in my cluster using Coherence 3.5.3.
    It appears that only the first WKA is being picked up from the configuration file, rather than the full list.
    For example, if I include the following in my tangosol-coherence-override.xml config file:
    <well-known-addresses>
    <socket-address id="1">
    <address>cyclone</address>
    <port system-property="tangosol.coherence.wka.port"></port>
    </socket-address>
    <socket-address id="2">
    <address>tornado</address>
    <port system-property="tangosol.coherence.wka.port"></port>
    </socket-address>
    </well-known-addresses>
    The logs will indicate that only a single wka is available (i.e. cyclone).
    If we try and bring proxy and storage nodes up on tornado they will not start up, as they will attempt to use cyclone.
    Does anyone have any ideas about where we might be going wrong?
    Cheers

    Hi Luk,
    Below is the tangosol-coherence-override.xml file I am using:
    Many Thanks
    <?xml version='1.0'?>
    <!-- Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
         Oracle is a registered trademarks of Oracle Corporation and/or its affiliates.
         This software is the confidential and proprietary information of Oracle Corporation.
         You shall not disclose such confidential and proprietary information and
         shall use it only in accordance with the terms of the license agreement you
         entered into with Oracle. This notice may not be removed or altered. -->
    <!DOCTYPE coherence SYSTEM "coherence.dtd">
    <!-- Note: This XML is set up for a development mode; search for "Note:"
         to find specific notes on changes suggested for production use. -->
    <coherence>
         <cluster-config>
              <member-identity>
                   <!-- Note: All members of the cluster must specify the same cluster name
                        in order to be allowed to join the cluster. -->
                   <cluster-name system-property="tangosol.coherence.cluster"></cluster-name>
                   <site-name system-property="tangosol.coherence.site"></site-name>
                   <rack-name system-property="tangosol.coherence.rack"></rack-name>
                   <machine-name system-property="tangosol.coherence.machine"></machine-name>
                   <process-name system-property="tangosol.coherence.process"></process-name>
                   <member-name system-property="tangosol.coherence.member"></member-name>
                   <role-name system-property="tangosol.coherence.role"></role-name>
                   <priority system-property="tangosol.coherence.priority"></priority>
              </member-identity>
              <unicast-listener>
                   <!-- Note: Specifying one or more "well known" addresses (WKA) will disable
                        all multicast communication. In this case, for a member to join the cluster
                        it will either have to be a WKA or there will have to be at least one WKA
                        member running. -->
                   <well-known-addresses>
                        <socket-address id="1">
                             <address>cyclone</address>
                             <port system-property="tangosol.coherence.wka.port"></port>
                        </socket-address>
    <socket-address id="2">
    <address>tornado</address>
    <port system-property="tangosol.coherence.wka.port"></port>
    </socket-address>
                   </well-known-addresses>
                   <!-- Note: The "localhost" setting may not work on systems that define
                        localhost as the loopback address; in that case, specify the machine name
                        or the specific IP address. -->
                   <address system-property="tangosol.coherence.localhost">localhost</address>
                   <port system-property="tangosol.coherence.localport">8088</port>
                   <port-auto-adjust system-property="tangosol.coherence.localport.adjust">true</port-auto-adjust>
                   <packet-buffer>
                        <maximum-packets>1428</maximum-packets>
                   </packet-buffer>
                   <priority>8</priority>
              </unicast-listener>
              <tcp-ring-listener>
                   <!-- Note: When encountering problems getting Coherence running on a system,
                        we suggest that this value be set to "false" until all other issues are resolved
                        in order to simplify trouble-shooting. -->
                   <enabled system-property="tangosol.coherence.tcpring">true</enabled>
                   <maximum-socket-closed-exceptions>2</maximum-socket-closed-exceptions>
                   <priority>6</priority>
              </tcp-ring-listener>
              <shutdown-listener>
                   <!-- Note: For production use, the suggested value is "none" (or "false")
                        unless testing has verified that the behavior on external shutdown is exactly
                        what is desired. -->
                   <enabled system-property="tangosol.coherence.shutdownhook">force</enabled>
              </shutdown-listener>
              <service-guardian>
                   <service-failure-policy>exit-cluster</service-failure-policy>
                   <!-- Note: For production use, the recommended value is equal to or greater
                        than the packet-delivery timeout. -->
                   <timeout-milliseconds system-property="tangosol.coherence.guard.timeout">65000</timeout-milliseconds>
              </service-guardian>
              <packet-speaker>
                   <priority>8</priority>
              </packet-speaker>
              <packet-publisher>
                   <packet-size>
                        <maximum-length>1468</maximum-length>
                        <preferred-length>1468</preferred-length>
                   </packet-size>
                   <packet-pool>
                        <maximum-packets>2048</maximum-packets>
                   </packet-pool>
                   <packet-delivery>
                        <resend-milliseconds>200</resend-milliseconds>
                        <!-- Note: For production use, the recommended value is the greater of
                             60000 and two times the maximum expected full GC duration. -->
                        <timeout-milliseconds>60000</timeout-milliseconds>
                        <heartbeat-milliseconds>1000</heartbeat-milliseconds>
                        <flow-control>
                             <enabled>true</enabled>
                             <pause-detection>
                                  <maximum-packets>16</maximum-packets>
                             </pause-detection>
                             <outstanding-packets>
                                  <maximum-packets>4096</maximum-packets>
                                  <minimum-packets>64</minimum-packets>
                             </outstanding-packets>
                        </flow-control>
                        <packet-bundling>
                             <maximum-deferral-time>1us</maximum-deferral-time>
                             <aggression-factor>0</aggression-factor>
                        </packet-bundling>
                   </packet-delivery>
                   <notification-queueing>
                        <ack-delay-milliseconds>16</ack-delay-milliseconds>
                        <nack-delay-milliseconds>1</nack-delay-milliseconds>
                   </notification-queueing>
                   <burst-mode>
                        <maximum-packets>0</maximum-packets>
                        <pause-milliseconds>10</pause-milliseconds>
                   </burst-mode>
                   <traffic-jam>
                        <maximum-packets>8192</maximum-packets>
                        <pause-milliseconds>10</pause-milliseconds>
                   </traffic-jam>
                   <packet-buffer>
                        <maximum-packets>32</maximum-packets>
                   </packet-buffer>
                   <priority>6</priority>
                   <!-- Note: Disabling the Publisher is used only by Java Real-Time Clients
                        to restrict their ability to use the cluster protocol (TCMP). When disabled,
                        a client is only be able to access clustered services via Extend proxies. -->
                   <enabled system-property="tangosol.coherence.tcmp.enabled">true</enabled>
              </packet-publisher>
              <incoming-message-handler>
                   <maximum-time-variance>16</maximum-time-variance>
                   <packet-pool>
                        <maximum-packets>2048</maximum-packets>
                   </packet-pool>
                   <use-nack-packets>true</use-nack-packets>
                   <priority>7</priority>
              </incoming-message-handler>
              <outgoing-message-handler>
                   <!-- Note: Uncomment the following section to activate gzip compression
                        for all network messages, which can help substantially with WAN and low-bandwidth
                        networks; for more information, see: http://www.tangosol.com/faq-coherence.jsp#filterconfig -->
                   <use-filters>
                        <!-- <filter-name>gzip</filter-name> -->
                   </use-filters>
              </outgoing-message-handler>
              <authorized-hosts>
                   <host-address></host-address>
                   <host-range>
                        <from-address></from-address>
                        <to-address></to-address>
                   </host-range>
              </authorized-hosts>
              <services>
                   <service id="1">
                        <service-type>ReplicatedCache</service-type>
                        <service-component>ReplicatedCache</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>standard-lease-milliseconds</param-name>
                                  <param-value>0</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>lease-granularity</param-name>
                                  <param-value>thread</param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>mobile-issues</param-name>
                                  <param-value>false</param-value>
                             </init-param>
                             <init-param id="4">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.replicated.request.timeout"></param-value>
                             </init-param>
                             <init-param id="5">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="6">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.replicated.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="2">
                        <service-type>OptimisticCache</service-type>
                        <service-component>ReplicatedCache.Optimistic</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.optimistic.request.timeout"></param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.optimistic.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="3">
                        <service-type>DistributedCache</service-type>
                        <service-component>DistributedCache</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>standard-lease-milliseconds</param-name>
                                  <param-value>0</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>lease-granularity</param-name>
                                  <param-value>thread</param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>partition-count</param-name>
                                  <param-value>257</param-value>
                             </init-param>
                             <init-param id="4">
                                  <param-name>local-storage</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.localstorage">true</param-value>
                             </init-param>
                             <init-param id="5">
                                  <param-name>transfer-threshold</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.transfer">512</param-value>
                             </init-param>
                             <init-param id="6">
                                  <param-name>backup-count</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.backupcount">1</param-value>
                             </init-param>
                             <init-param id="7">
                                  <param-name>backup-storage/type</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.backup">on-heap</param-value>
                             </init-param>
                             <init-param id="8">
                                  <param-name>thread-count</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.threads">5</param-value>
                             </init-param>
                             <init-param id="9">
                                  <param-name>key-associator/class-name</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="10">
                                  <param-name>key-partitioning/class-name</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="11">
                                  <param-name>partition-listener/class-name</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="12">
                                  <param-name>task-hung-threshold</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.task.hung"></param-value>
                             </init-param>
                             <init-param id="13">
                                  <param-name>task-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.task.timeout"></param-value>
                             </init-param>
                             <init-param id="14">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.request.timeout"></param-value>
                             </init-param>
                             <init-param id="15">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="16">
                                  <param-name>backup-count-after-writebehind</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="17">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.distributed.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="4">
                        <service-type>Invocation</service-type>
                        <service-component>InvocationService</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>thread-count</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.threads">5</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>task-hung-threshold</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.task.hung"></param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>task-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.task.timeout"></param-value>
                             </init-param>
                             <init-param id="4">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.request.timeout"></param-value>
                             </init-param>
                             <init-param id="5">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="6">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.invocation.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="5">
                        <service-type>LocalCache</service-type>
                        <service-component>LocalCache</service-component>
                        <init-params>
                             <init-param id="1">
                                  <param-name>lock-enforce</param-name>
                                  <param-value>false</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>lock-wait</param-name>
                                  <param-value>0</param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="6">
                        <service-type>SimpleCache</service-type>
                        <service-component>SimpleCache</service-component>
                   </service>
                   <service id="7">
                        <service-type>Proxy</service-type>
                        <service-component>ProxyService</service-component>
                        <use-filters>
                             <filter-name />
                        </use-filters>
                        <init-params>
                             <init-param id="1">
                                  <param-name>acceptor-config</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>proxy-config</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>thread-count</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.threads">10</param-value>
                             </init-param>
                             <init-param id="4">
                                  <param-name>task-hung-threshold</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.task.hung"></param-value>
                             </init-param>
                             <init-param id="5">
                                  <param-name>task-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.task.timeout"></param-value>
                             </init-param>
                             <init-param id="6">
                                  <param-name>request-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.request.timeout"></param-value>
                             </init-param>
                             <init-param id="7">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="8">
                                  <param-name>guardian-timeout</param-name>
                                  <param-value system-property="tangosol.coherence.proxy.guard.timeout"></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="8">
                        <service-type>RemoteCache</service-type>
                        <service-component>RemoteCache</service-component>
                        <init-params>
                             <init-param id="1">
                                  <param-name>initiator-config</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                        </init-params>
                   </service>
                   <service id="9">
                        <service-type>RemoteInvocation</service-type>
                        <service-component>RemoteInvocation</service-component>
                        <init-params>
                             <init-param id="1">
                                  <param-name>initiator-config</param-name>
                                  <param-value></param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>serializer</param-name>
                                  <param-value></param-value>
                             </init-param>
                        </init-params>
                   </service>
              </services>
              <filters>
                   <filter id="1">
                        <filter-name>gzip</filter-name>
                        <filter-class>com.tangosol.net.CompressionFilter</filter-class>
                        <init-params>
                             <init-param id="1">
                                  <param-name>strategy</param-name>
                                  <param-value>gzip</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>level</param-name>
                                  <param-value>default</param-value>
                             </init-param>
                        </init-params>
                   </filter>
                   <filter id="2">
                        <filter-name>symmetric-encryption</filter-name>
                        <filter-class>com.tangosol.net.security.PasswordBasedEncryptionFilter</filter-class>
                        <init-params>
                             <init-param id="1">
                                  <param-name>password</param-name>
                                  <param-value system-property="tangosol.coherence.security.password"></param-value>
                             </init-param>
                        </init-params>
                   </filter>
                   <filter id="3">
                        <filter-name>pkcs-encryption</filter-name>
                        <filter-class>com.tangosol.net.security.ClusterEncryptionFilter</filter-class>
                        <init-params>
                             <init-param id="1">
                                  <param-name>store</param-name>
                                  <param-value system-property="tangosol.coherence.security.keystore">./keystore.jks</param-value>
                             </init-param>
                             <init-param id="2">
                                  <param-name>keyAlias</param-name>
                                  <param-value>local</param-value>
                             </init-param>
                             <init-param id="3">
                                  <param-name>keyPassword</param-name>
                                  <param-value system-property="tangosol.coherence.security.password"></param-value>
                             </init-param>
                        </init-params>
                   </filter>
              </filters>
         </cluster-config>
         <logging-config>
              <destination system-property="tangosol.coherence.log">stdout</destination>
              <logger-name system-property="tangosol.coherence.log.logger"></logger-name>
              <severity-level system-property="tangosol.coherence.log.level">9</severity-level>
              <message-format>{date}/{uptime} {product} {version} &lt;{level}&gt;
                   (thread={thread}, member={member}): {text}</message-format>
              <character-limit system-property="tangosol.coherence.log.limit">1048576</character-limit>
         </logging-config>
         <configurable-cache-factory-config>
              <class-name>com.tangosol.net.DefaultConfigurableCacheFactory</class-name>
              <init-params>
                   <init-param>
                        <param-type>java.lang.String</param-type>
                        <param-value system-property="tangosol.coherence.cacheconfig">coherence-cache-config.xml</param-value>
                   </init-param>
              </init-params>
         </configurable-cache-factory-config>
         <cache-factory-builder-config>
              <class-name system-property="tangosol.coherence.cachefactorybuilder">com.tangosol.net.DefaultCacheFactoryBuilder</class-name>
         </cache-factory-builder-config>
         <management-config>
              <!-- Note: Setting this value to 'local-only', 'remote-only or 'all' will
                   require the javax.management.* classes be available on the classpath. -->
              <managed-nodes system-property="tangosol.coherence.management">all</managed-nodes>
              <!-- Note: Setting this value to 'true' will require the Enterprise Edition
                   license. -->
              <allow-remote-management system-property="tangosol.coherence.management.remote">true</allow-remote-management>
              <refresh-policy system-property="tangosol.coherence.management.refresh.policy">refresh-ahead</refresh-policy>
              <refresh-expiry system-property="tangosol.coherence.management.refresh.expiry">1s</refresh-expiry>
              <refresh-timeout system-property="tangosol.coherence.management.refresh.timeout">250ms</refresh-timeout>
              <read-only system-property="tangosol.coherence.management.readonly">false</read-only>
              <default-domain-name>AGP Cache</default-domain-name>
              <service-name>Management</service-name>
              <server-factory>
                   <class-name system-property="tangosol.coherence.management.serverfactory"></class-name>
              </server-factory>
              <mbeans xml-override="{tangosol.coherence.mbeans /custom-mbeans.xml}">
                   <mbean id="1">
                        <mbean-query>java.lang:*</mbean-query>
                        <mbean-name>type=Platform</mbean-name>
                        <enabled system-property="tangosol.coherence.management.jvm.all">true</enabled>
                   </mbean>
              </mbeans>
              <reporter>
                   <configuration system-property="tangosol.coherence.management.report.configuration">reports/report-group.xml</configuration>
                   <autostart system-property="tangosol.coherence.management.report.autostart">false</autostart>
                   <distributed system-property="tangosol.coherence.management.report.distributed">false</distributed>
              </reporter>
         </management-config>
         <security-config>
              <enabled system-property="tangosol.coherence.security">false</enabled>
              <login-module-name>Coherence</login-module-name>
              <access-controller>
                   <class-name>com.tangosol.net.security.DefaultController</class-name>
                   <init-params>
                        <init-param id="1">
                             <param-type>java.io.File</param-type>
                             <param-value system-property="tangosol.coherence.security.keystore"></param-value>
                        </init-param>
                        <init-param id="2">
                             <param-type>java.io.File</param-type>
                             <param-value system-property="tangosol.coherence.security.permissions"></param-value>
                        </init-param>
                   </init-params>
              </access-controller>
              <callback-handler>
                   <class-name />
              </callback-handler>
         </security-config>
         <license-config>
              <edition-name system-property="tangosol.coherence.edition">GE</edition-name>
              <license-mode system-property="tangosol.coherence.mode">dev</license-mode>
         </license-config>
    </coherence>

  • My Mac is blocking me from accessing one well known shopping website, why? I can access it from my iPhone.

    My Mac is blocking me from accessing a well  known shopping website (no problem at their end with my account).  I can access it from my iphone, so why not my Mac?

    From the Safari menu bar, select
    Safari ▹ Preferences... ▹ Security
    and check the box marked Enable JavaScript.
    If the Develop menu is showing and Disable JavaScript is checked, uncheck it.

  • I m staying at Mumbai and one of the very well known apple ipod's reseller is offering me ipod nano 7G without bill at little cheap rate. So I want to know that if I will make a purchase from there then am I eligible for APPLE'S one year limited warranty?

    I m staying at Mumbai and one of the very well known apple ipod's reseller is offering me ipod nano 7G without bill at little cheap rate. So I want to know that if I will make a purchase from there then am I eligible for APPLE'S one year limited warranty?

    The warranty for ipod nano in india is here:
    http://www.apple.com/legal/warranty/products/nios-ipod-english-uk.html
    Im not really sure but some resellers have their own warranty.
    If the iPod is brand new, it should have the apple one year limited warranty
    hope it helps

Maybe you are looking for

  • IWeb '09 "Hit Counter"  Widget

    Is the "hit counter" widget supposed to log a "hit" every time someone views/visits an/each individual page of a website, or only once per visit to the site? It appears that every page visited of the site registers a "hit." Is this usual and customar

  • Problem to see photos in APEX loaded in Forms 9i

    I have a table employees with field "Photo" BLOB. This table was filled from Forms 9i using WEBUTIL. Now, i´m using APEX 3.1 to access photo but not view image. I have a application Apex 3.1 to upload the news records and photos from Employees, and i

  • Does apple charge for Genius Bar help

    Does apple charge for Genius Bar help

  • 4.0.1 to 4.1.1 -- LDAP Directory Authentication Scheme fails

    Using the out of the box LDAP directory authentication scheme that worked fine in v. 4.0.1 is failing in v. 4.1.1. User authentication is failing with 'Invalid Login Credentials'. Debug shows that the User is 'nobody'. Looking at v. 4.0.1, User shows

  • Reinstall of CS5.5 student edition

    I have the student/teacher edition of CS5.5 and need to switch it to my Macbook pro with no disk drive. How do I do this?