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

Similar Messages

  • 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

  • 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

  • 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>

  • 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

  • Weird "relay access denied" error when using "%" in email address

    Hi, I've written a solution that allows emails to be processed and redirected through my mail server. First, we receive mail at user%[email protected]. Then, we do some checks to make sure its legit, alter its content and re-send it to [email protected]. I posted another topic in this forum getting some advice as to how to build it, but it's all built and working well... or so I thought...
    I initially had trouble with using the % symbol as the delimiter because of a default postfix behavior (postfix by default treats the % as my custom application is, which of course can be dangerous). However, I added "allowpercenthack = no" to main.cf and that seemed to allow postfix to not attempt to process it itself and let my application do the work.
    However, if I now send mail now to my server (from another server) destined to user%[email protected], I (and my log) gets:
    <user%[email protected]>: Relay access denied (in reply to RCPT TO command)
    However, if I send to an address WITHOUT the %, like something [email protected], the whole thing works correctly.
    HOWEVER, if I send messages WITH and WITHOUT the % from the command line while ON the server, I don't get these errors.
    My main.cf has the following restrictions(s):
    <pre>smtpdrecipientrestrictions = rejectnon_fqdnrecipient, checkrecipientaccess hash:/etc/postfix/access,
    permit_mynetworks, rejectunauthdestination, rejectnon_fqdnsender,
    rejectnon_fqdnhostname, rejectinvalidhostname, checkheloaccess hash:/etc/postfix/helo_access,
    rejectrblclient zen.spamhaus.org, rejectrblclient bl.spamcop.net, rejectrblclient relays.ordb.org,
    permit</pre>
    I'm assuming that permit_mynetworks is allowing this to work from my server's command line, and therefore I'm suspecting rejectunauthdestination is what's killing my ability to use the % symbol. As a test, I removed rejectunauthdestination temporarily and reload postix. The next mail received triggered this error in the log:
    Mar 16 12:24:28 server postfix/smtpd[1368]: fatal: parameter "smtpdrecipientrestrictions": specify at least one working instance of: checkrelaydomains, rejectunauthdestination, reject, defer or deferifpermit
    Of course. I needed one of those directives. I didn't want reject, defer or deferifpermit, and documentation on checkrelaydomains was not available at http://www.postfix.org/postconf.5.html. However, I tried checkrelaydomains, and it seemed to work as expected permitting my % emails and rejecting stuff it should, but of course the 'gotcha' was that postfix's log now reflected:
    Mar 16 12:33:08 server postfix/smtpd[1579]: warning: support for restriction "checkrelaydomains" will be removed from Postfix; use "rejectunauthdestination" instead
    Mar 16 12:33:08 server postfix/smtpd[1579]: warning: restriction `rejectnon_fqdnsender' after `checkrelaydomains' is ignored
    So, can anyone recommend a way I can polish up my restrictions to allow these % addresses without opening myself up for anything dangerous?
    Side question: I placed `rejectnon_fqdnsender' after rejectunauthdestination destination because I didn't want to bother checking the sender unless I confirmed the recipient was at my server. Does that comment that it doesn't work after checkrelaydomains, mean that it also doesn't get processed after rejectunauthdestination?
    MacBook   Mac OS X (10.4.8)  

    However, I added "allowpercenthack = no" to main.cf
    and that seemed to allow postfix to not attempt to
    process it itself and let my application do the
    work.
    However, if I now send mail now to my server (from
    another server) destined to
    user%[email protected], I (and my
    log) gets:
    Hardly ever had a need for this, but if I remember correctly you will need to set:
    allowuntrustedrouting = yes
    in main.cf
    (No need for allowpercenthack (I think))
    or you could create a hash table before rejectunauthdestination to return OK based on your needed patterns.
    I think the first method will work though.
    Side question: I placed `rejectnon_fqdnsender'
    after rejectunauthdestination destination because I
    didn't want to bother checking the sender unless I
    confirmed the recipient was at my server. Does that
    comment that it doesn't work after
    checkrelaydomains, mean that it also doesn't get
    processed after
    checkrelaydomains is deprecated
    You can place rejectnon_fqdnsender anywhere you like or even omit it, but I don't see why you would have to.

  • Two clusters on same machine using well know addresses - is it possible?

    Hi,
    I try to setup two clusters (each with two nodes) on the same machine and want to use WKA for both of them. For the first one I do not have problems and it starts normaly.
    When I try to start a node from the second cluster I get this message :
    2011-07-07 12:00:06.984/10.710 Oracle Coherence EE 3.5.2/463p5 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior servi
    ce member n/a
    2011-07-07 12:00:14.899/18.625 Oracle Coherence EE 3.5.2/463p5 <Error> (thread=Cluster, member=n/a): This member could not join the cluster because of
    a configuration mismatch between this member and the configuration being used by the rest of the cluster. This member specified a cluster name of "Ac
    meCluster2" which did not match the name of the running cluster. This indicates that there are multiple clusters on this network attempting to use ove
    rlapping network configurations. Rejected by Member(Id=1, Timestamp=2011-07-07 10:08:34.426, Address=<IPaddress>:8088, MachineId=3377, Location=site:c
    orproot.net,machine:<MachineName>,process:564, Role=TibcoCepContainerBEMain).
    2011-07-07 12:00:14.899/18.625 Oracle Coherence EE 3.5.2/463p5 <D5> (thread=Cluster, member=n/a): Service Cluster left the cluster
    2011-07-07 12:00:14.899/18.625 Oracle Coherence EE 3.5.2/463p5 <Error> (thread=main, member=n/a): Error while starting cluster: java.lang.RuntimeExcep
    tion: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)
    I have configured the "java.property.tangosol.coherence.wka.port" and "java.property.tangosol.coherence.wka1.port" to different values for the second cluster than the values of the first.
    Fist of all is such setup possible?
    Any idea why I get this error and what else I need to change in the configuration for the second cluster?
    greetings Georgi

    Hi,
    Now it works for me. I think I was setting the WKA on too many places as the documention of the application I have is a little bit confusing.
    First I have posted the WKA with java.property as it was specified in the documentation of my application to set them in the script that starts it. I have removed them from the script and used only the xml file to configure coherence.
    I am not using the override file but rather change the WKA configuration in the jar file itself. For the real enviornment and not my laptop I will use it.
    Also there were two coherence.jar files in my class path and the first one was common for the both clusters and the second one was different for each cluster. In this second one I was changeing tangosol-coherence.xml the logs were showing that the configuration loaded from and also in the classpath this second was before the other one . Maybe I was wrong so I have removed the first coherence.jar that was common.
    Maybe the combination of those two things were the problem but now it works. Thanks for your comments.
    greetings Georgi

  • Wrong reply from, when using multiple email addresses

    Apple Mail has this strange behavior. Maybe it is a bug.
    I have 3 email addresses in Mail: [email protected], [email protected] and [email protected]
    [email protected] is my primary email address, the other ones are from my co-workers.
    Sometimes I get an email with my email address (among others) in the CC field and the other two in the TO field. When I press the Reply All button, Mail generates a new message. But instead of sending it from the [email protected] account, it tries to send it from the first email account what it found in the TO field of the original message. And it does not reply to any of the email addresses in the CC field of the original message.
    I tried this with different domains. Same result. Tried it by forcing Mail sending mail from my account only. Same result.
    What is going on here? Is it a bug?

    Normally mail would create a new email using the top email address in your list of accounts. For example, in in preferences you accounts are listed like this:
    [email protected]
    [email protected]
    [email protected]
    then normally new messages would be sent from the top email address.

  • All of a sudden I get error message when using Mail " Sender address rejected: not owned by user dgill42041"

    I've been using Mail for years with no problems, accessing my AOL accounts.  Today I can receive mail but not send.  I get the above error message and it says that my mailboxes are "off line". 

    Mail troubleshooting - Yosemite
    What does Mail/Window/Connection Doctor Show? If the server is red, select it and look at the Show Details box.
    Troubleshooting sending and receiving email messages
    Troubleshooting sending email messages
    SMTP servers keep going offline

  • TS1629 Apple destination ip addresses for well known TCP and UDP ports used by Apple software products

    I work for a large enterprise organisation with dual layer firewalls. The Apple article titled "allowing well known ports through the firewall "does not provide enough information on what the destination ip addresses of Apple servers are which host Apple ICloud services.
    Does anyone have information on the destination Apple Ip addresses? So that I can lock down my firewall rules, just so that Apple devices, access Apple services on the Internet.
    Many thanks

    One option is to use "connection-reuse" cli under sip-ua configuration mode.
    sip-ua
      connection-reuse
    This will enable the 7200 to create a connection with source and destination udp port number set to 5060. This feature is available in IOS 12.4(25d) which requires minimum of 256 / 512MB DRAM (depends on the feature set) and flash of 48 MB.

  • Jax-ws 2.2.8 and ws-addressing: Client throwing java.lang.NullPointerException on receipt of HTTP 202 when using non-anonymous ReplyTo address

    Server: JBoss EAP 6.2.0
    Client: JDK 1.7.0_51 x64
    JAX-WS: RI 2.2.8 ( via -Djava.endorsed.dirs )
    I am getting a java.lang.NullPointerException when calling the operation on the WS endpoint from the client when using non-anonymous replyTo address.
    I have simplified the scenario into a small test case that hopefully others can replicate. Since the exception is happening on the client instead of the server, I would think that the container used is irrelevant, but I have specified it nonetheless.
    1) WebService:
    package test.webservice;
    import java.util.Random;
    import javax.jws.WebMethod;
    import javax.jws.WebParam;
    import javax.jws.WebService;
    import javax.jws.soap.SOAPBinding;
    import javax.xml.ws.soap.Addressing;
    @WebService(targetNamespace="http://services.nowhere.org/")
    @Addressing(required=true)
    @SOAPBinding(style = SOAPBinding.Style.DOCUMENT)
    public class RandomTest {
        @WebMethod
        public long nextRandom(@WebParam boolean forceException) throws Exception {
            if( forceException ) {
                throw new Exception("Some exception");
            Random rand = new Random();
            return rand.nextLong();
    2) Generated WSDL by JBossEAP 6.2.2:
    <?xml version='1.0' encoding='UTF-8'?><wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:tns="http://webservice.test/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" name="RandomTestService" targetNamespace="http://webservice.test/">
      <wsdl:types>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://webservice.test/" elementFormDefault="unqualified" targetNamespace="http://webservice.test/" version="1.0">
      <xs:element name="nextRandom" type="tns:nextRandom"/>
      <xs:element name="nextRandomResponse" type="tns:nextRandomResponse"/>
      <xs:complexType name="nextRandom">
        <xs:sequence/>
      </xs:complexType>
      <xs:complexType name="nextRandomResponse">
        <xs:sequence>
          <xs:element name="return" type="xs:long"/>
        </xs:sequence>
      </xs:complexType>
    </xs:schema>
      </wsdl:types>
      <wsdl:message name="nextRandom">
        <wsdl:part element="tns:nextRandom" name="parameters">
        </wsdl:part>
      </wsdl:message>
      <wsdl:message name="nextRandomResponse">
        <wsdl:part element="tns:nextRandomResponse" name="parameters">
        </wsdl:part>
      </wsdl:message>
      <wsdl:portType name="RandomTest">
        <wsdl:operation name="nextRandom">
          <wsdl:input message="tns:nextRandom" name="nextRandom" wsam:Action="http://webservice.test/RandomTest/nextRandomRequest" wsaw:Action="http://webservice.test/RandomTest/nextRandomRequest">
        </wsdl:input>
          <wsdl:output message="tns:nextRandomResponse" name="nextRandomResponse" wsam:Action="http://webservice.test/RandomTest/nextRandomResponse" wsaw:Action="http://webservice.test/RandomTest/nextRandomResponse">
        </wsdl:output>
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="RandomTestServiceSoapBinding" type="tns:RandomTest">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsaw:UsingAddressing wsdl:required="true"/>
        <wsp:PolicyReference URI="#RandomTestServiceSoapBinding_WSAM_Addressing_Policy"/>
        <wsdl:operation name="nextRandom">
          <soap:operation soapAction="" style="document"/>
          <wsdl:input name="nextRandom">
            <soap:body use="literal"/>
          </wsdl:input>
          <wsdl:output name="nextRandomResponse">
            <soap:body use="literal"/>
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="RandomTestService">
        <wsdl:port binding="tns:RandomTestServiceSoapBinding" name="RandomTestPort">
          <soap:address location="http://localhost:8080/servertest/RandomTest"/>
        </wsdl:port>
      </wsdl:service>
        <wsp:Policy xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="RandomTestServiceSoapBinding_WSAM_Addressing_Policy"><wsam:Addressing><wsp:Policy/></wsam:Addressing></wsp:Policy>
    </wsdl:definitions>
    3) ant build.xml to generate the client code from WSDL
    <?xml version="1.0" encoding="UTF-8"?>
    <project default="build" basedir="..">
        <property name="jaxws.classpath" location="C://jaxws-2.2.8/jaxws-ri/lib/*.jar"/>
        <taskdef name="wsimport" classname="com.sun.tools.ws.ant.WsImport">
               <classpath path="${jaxws.classpath}"/>
        </taskdef>
        <target name="build" >
            <!-- For these to work, the JAR files in tools/jaxws-ri must be included in Ant's classpath -->
            <wsimport wsdl="http://localhost:8080/servertest/RandomTest?wsdl"
                   verbose="true"
                   sourcedestdir="src"
                   destdir="bin"
                   keep="true">
                   <xjcarg value="-enableIntrospection"/>
            </wsimport>
        </target>
    </project>
    4) Client code
    4a) ClientTest.java - Actual client run from client
    package test.wsclient;
    import java.util.ArrayList;
    import java.util.List;
    import javax.xml.ws.BindingProvider;
    import javax.xml.ws.Endpoint;
    import javax.xml.ws.handler.Handler;
    import javax.xml.ws.soap.AddressingFeature;
    import org.nowhere.services.RandomTest;
    import org.nowhere.services.RandomTestService;
    public class ClientTest {
        public static void main(String args[]) throws Exception {
            ClientTest app = new ClientTest();
            app.testAddressing();
        public void testAddressing() throws Exception {
            String REPLY_TO_ADDRESS = "http://localhost:8082/servertest/RandomCallback";
            String FAULT_TO_ADDRESS = "http://localhost:8082/servertest/RandomCallbackFault";
            RandomTestService service = new RandomTestService();
            RandomTest port = service.getRandomTestPort(new AddressingFeature());
            BindingProvider provider = (BindingProvider) port;
            // pass the replyTo address to the handler
            provider.getRequestContext().put("ReplyTo", REPLY_TO_ADDRESS);
            provider.getRequestContext().put("FaultTo", FAULT_TO_ADDRESS);
            // Register handlers to set the ReplyTo and FaultTo on the SOAP request sent to the WS endpoint
            List<Handler> handlerChain = new ArrayList<Handler>();
            handlerChain.add(new ClientHandler());
            provider.getBinding().setHandlerChain(handlerChain);
            // Start endpoint to receive callbacks from WS
            Endpoint endpoint = Endpoint.publish(REPLY_TO_ADDRESS, new CallbackSEI());
            try {
                port.nextRandom(false);
            } catch( Exception ex ) {
                ex.printStackTrace();
            } finally {
                Thread.sleep(10000);
            endpoint.stop();
            System.exit(0);
    4b) ClientHandler.java - Used to set the wsa ReplyTo address and FaultTo address when sending SOAP request from client to server
    package test.wsclient;
    import java.util.Set;
    import javax.xml.namespace.QName;
    import javax.xml.soap.SOAPEnvelope;
    import javax.xml.soap.SOAPHeader;
    import javax.xml.ws.handler.MessageContext;
    import javax.xml.ws.handler.MessageContext.Scope;
    import javax.xml.ws.handler.soap.SOAPHandler;
    import javax.xml.ws.handler.soap.SOAPMessageContext;
    import org.w3c.dom.Node;
    import org.w3c.dom.NodeList;
    public class ClientHandler implements SOAPHandler<SOAPMessageContext> {
        public ClientHandler() {};
        @Override
        public Set<QName> getHeaders() {
            return null;
        @Override
        public void close(MessageContext arg0) {
        @Override
        public boolean handleFault(SOAPMessageContext context) {
            return true;
        protected void setAnAddress(SOAPHeader header, String tagName, String address) {
            NodeList nodeListReplyTo = header.getElementsByTagName(tagName);
            NodeList nodeListAddress = nodeListReplyTo.item(0).getChildNodes();
            for (int i = 0; i < nodeListAddress.getLength(); i++) {
                Node node = nodeListAddress.item(i);
                if ("Address".equals(node.getLocalName())) {
                    node.setTextContent(address);
                    break;
        protected String getMessageID(SOAPHeader header) {
            NodeList nodeListMessageId = header.getElementsByTagName("MessageID");
            return nodeListMessageId.item(0).getTextContent();
        @Override
        public boolean handleMessage(SOAPMessageContext context) {
            Boolean isOutbound = (Boolean) context.get(SOAPMessageContext.MESSAGE_OUTBOUND_PROPERTY);
            if (isOutbound) {
                try {
                    SOAPEnvelope envelope = context.getMessage().getSOAPPart().getEnvelope();
                    SOAPHeader header = envelope.getHeader();
                    /* extract the generated MessageID */
                    String messageID = getMessageID(header);
                    context.put("MessageID", messageID);
                    context.setScope("MessageID", Scope.APPLICATION);
                    /* change ReplyTo address */
                    setAnAddress(header, "ReplyTo", (String) context.get("ReplyTo"));
                    setAnAddress(header, "FaultTo", (String) context.get("FaultTo"));
                } catch (Exception ex) {
                    throw new RuntimeException(ex);
            return true;
    4c) CallbackSEI.java - endpoint on the client for server to send the SOAP response back to the client
    package test.wsclient;
    import javax.annotation.Resource;
    import javax.jws.Oneway;
    import javax.jws.WebParam;
    import javax.jws.WebService;
    import javax.xml.ws.Action;
    import javax.xml.ws.RequestWrapper;
    import javax.xml.ws.WebServiceContext;
    import javax.xml.ws.soap.Addressing;
    @WebService
    @Addressing
    //@HandlerChain(file = "/handler-chain.xml")
    public class CallbackSEI {
        @Resource
        private WebServiceContext context;
         * If there is no namespace specified in the method below, then the CallbackSEI needs to be in the same package as the
         * WS endpoint.
        @Oneway
        @Action(input="http://services.nowhere.org/RandomTest/nextRandomResponse")
        @RequestWrapper(localName="nextRandomResponse", targetNamespace="http://services.nowhere.org/")
        public void handleNotification(@WebParam(name="return")long random) {
            System.out.println("Asynch response received");
            System.out.println( random );
            //System.out.println("This response relates to the message ID: "+ getMessageID());
    In summary:
    Server is listening on port 8080
    Client will listen in port 8082 for the callback from the server for the SOAP response
    Now when I run the client, I see that the proper behaviour as far as ws-addressing is concerned. That is:
    client  -- SOAP request ( on port 8080 ) --> server
    client <-- HTTP 202 ( empty HTTP body )  --- server
    client <-- SOAP response ( on port 8082 )  --- server
    All well and good, except that I am getting a NullPointerException on the client side when I call the operation.
    With debugging of the SOAP request and responses, I get the following output:
    ---[HTTP request - http://localhost:8080/servertest/RandomTest]---
    Accept: text/xml, multipart/related
    Content-Type: text/xml; charset=utf-8
    SOAPAction: "http://services.nowhere.org/RandomTest/nextRandomRequest"
    User-Agent: JAX-WS RI 2.2.8 svn-revision#13980
    <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><S:Header><To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/servertest/RandomTest</To><Action xmlns="http://www.w3.org/2005/08/addressing">http://services.nowhere.org/RandomTest/nextRandomRequest</Action><ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
        <Address>http://localhost:8082/servertest/RandomCallback</Address>
    </ReplyTo><FaultTo xmlns="http://www.w3.org/2005/08/addressing">
        <Address>http://localhost:8082/servertest/RandomCallbackFault</Address>
    </FaultTo><MessageID xmlns="http://www.w3.org/2005/08/addressing">uuid:bcd2f6ef-3034-49e8-b837-dbd6a772fb93</MessageID></S:Header><S:Body><ns2:nextRandom xmlns:ns2="http://services.nowhere.org/"><arg0>false</arg0></ns2:nextRandom></S:Body></S:Envelope>--------------------
    ---[HTTP response - http://localhost:8080/servertest/RandomTest - 202]---
    null: HTTP/1.1 202 Accepted
    Content-Length: 0
    Content-Type: text/xml;charset=UTF-8
    Date: Fri, 18 Jul 2014 08:34:36 GMT
    Server: Apache-Coyote/1.1
    java.lang.NullPointerException
        at com.sun.proxy.$Proxy38.nextRandom(Unknown Source)
        at test.wsclient.ClientTest.testAddressing(ClientTest.java:43)
        at test.wsclient.ClientTest.main(ClientTest.java:18)
    ---[HTTP request]---
    Cache-control: no-cache
    Host: localhost:8082
    Content-type: text/xml; charset=UTF-8
    Content-length: 704
    Connection: keep-alive
    Pragma: no-cache
    User-agent: Apache CXF 2.7.7.redhat-1
    Accept: */*
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><Action xmlns="http://www.w3.org/2005/08/addressing">http://services.nowhere.org/RandomTest/nextRandomResponse</Action><MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:65d8d7fc-09e4-494a-a9c5-0a01faf4d7e6</MessageID><To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8082/servertest/RandomCallback</To><RelatesTo xmlns="http://www.w3.org/2005/08/addressing">uuid:bcd2f6ef-3034-49e8-b837-dbd6a772fb93</RelatesTo></soap:Header><soap:Body><ns2:nextRandomResponse xmlns:ns2="http://services.nowhere.org/"><return>2870062781194370669</return></ns2:nextRandomResponse></soap:Body></soap:Envelope>--------------------
    Asynch response received
    2870062781194370669
    As you can see from the output above, the proxy is throwing an Exception when it receives the HTTP 202 response.
    Any ideas ?

    I think I have found when I get this error and probably I have found a bug. I will appreciate if someone can confirm this.
    In my BPEL project setup, my BPEL process's wsdl file imports another wsdl from different namespace. Here is sample snippet -
    <wsdl:definitions targetNamespace="http://namespace/1">
    <wsdl:import namespace="http://namespace/2" location="resources/another.wsdl"/>
    <plnk:partnerLinkType....../>
    </wsdl:definitions>
    Please let me know. I checked the bundled samples with Oracle BPEL PM and did not find any similar case where process wsdl imports another wsdl.
    Thank you.
    Meghana

  • Slow(er) startup when using captive runtime on windows

    I  just converted two AIR apps from native exe installers (requiring AIR installed) to Captive Runtime relases (just a folder structure).
    One difference i see is that my applications now load a little slower (because of the packaged instead of installed runtime?).
    When using flex 4 sdk the white and centered flex4-loadbar now appears for a few seconds before the splash screen of the app. appears. The same happens when using flex 3 sdk (in compatibility mode) but instead the "initializing" text appears.
    Is this slowdown a known effect of the captive runtime packaging?

    I responded to your other thread in the bugs forum but wanted to also respond here.
    I'm not aware of any slower performance implications when using the captive runtime but I'm going to investigate further.  In the meantime, would you mind opening a new bug over at bugbase.adobe.com regarding the startup performance hit?  It would be great if you could also provide us with a sample application that illustrates the slower startup time.  If you'd like to keep it private, please email me directly at [email protected]
    Thanks,
    Chris

  • Certain web address not available when using Airport Extreme Base Station

    Hello. To access my "secure" account at the local library, I must use a web address that contains a colon followed by a number. I believe that this is a port number, but I confess that all the discussions here regarding ports are going well over my head, and I may be incorrect with this assumption.
    My problem is that while I CAN access this site by connecting to my DSL router directly via ethernet cable from my iMac G5, I cannot access the site when connecting to the internet in the mode: iMac Airport to Airport Extreme Base Station to DSL router via ethernet.
    The format of the web address is: http://xxxx.yyyy.net:####/zzzzz/, where #### is the number I guess may be specifying a port and causing my problem.
    Can anyone advise me, in simple terms, how to get to this address when in the Airport--internet connection mode? Will the solution have any adverse side effects?
    Regards and Thanks
    iMac G5, 2.5 year old AEBS   Mac OS X (10.3.9)   Westell 327W 4-port DSL Modem, not using wireless feature.

    Very likely the embedded firewall that comes with your AirPort blocks the port you are trying to use.
    In order to solve this, best way is to modify the AirPort settings (open the AirPort maintenance app):
    Click at the tab "port forwarding" and add the desired port as "public port" to the list. "private IP" is the IP of your Mac and for "private port" type in the port number again.
    If you are unsure about the IP of your Mac, look at the network maintenance application.
    Well, one side-effect is that you have an open port in your configuration which could cause security issues... but only if you are paranoid So there is nothing to care about (note that without the AirPort inbetween your Mac and your modem, this port would be not blocked and freely accessible

  • When I login on my When I sign in to a site on my ipad using my email address as ID a short cut of my email address comes up. How can I get rid of it?

    When I sign in to a site on my iPad using my email address as ID a short cut of my email address comes up. How can I get rid of it?

    You can edit keyboard shortcuts in Settings>General>Keyboard>Shortcuts>Edit.

  • The configuration file did not contain well formed AppV configuration XML - When using Office 2013 ODT package

    All,
    I'm experiencing an issue where when using the Office 2013 package pulled down from ODT, that if I try to change the locations of either InfoPath Filler 2013 or Publisher 2013 from the default of Microsoft Office 2013 then I receive the message "The
    configuration file did not contain well formed AppV configuration XML. Please check the management server event log for more information". If I check Applications and Services\Microsoft\AppV\Server-Management\Admin the error displayed there is "An
    error was encountered parsing dynamic configuration file '0'. However I am able to change the shortcut location for all other applications except the above 2. I've tried redownloading the files using the ODT and also changing the version number (so far I've
    tried both the 15.0.4631.1002 and 15.0.4659.1001 with the same result).
    As all I'm interested in so far is having a package which contains Visio and Project I've tried following the article to exclude all the other Office elements:
    http://technet.microsoft.com/library/jj219426(v=office.15).aspx#BKMK_ExcludeAppElement. However the package looks to be the same and when I load it into the management console all the options and elements to Office 2013 are available like they were before
    when I hadn't set the exclude tags so I'm not sure whether the ExcludeApp parameters actually work correctly.
    This then brings me onto the 3rd issue I've experienced. I have a group for the Visio users and I've set custom security for them to have Visio delivered to them but not Project and then a seperate group for just Project users who will have Project delivered
    to them but not have Visio. When testing this sometimes seems to work but other times it seems to trip out and a user just in the Project or Visio group will get all of the Office 2013 applications and under the default location of Microsoft Office 2013. When
    trying to spot correlation with this it appears random and can happen to any user on any device. We have sequenced a few applications ourselves where different parts are needed for different users and we have successfully managed this using different security
    groups for different applications, just as I'm trying here with Office 2013.
    Has anyone else experienced the issue with the "did not contain well formed XML" as at the start of the post and how were you able to resolve this? Also has anyone any advice on how to troubleshoot the issue with the security seeming to trip out
    and publish all applications within a package to a user regardless of whether they are in the correct group or not?
    The management / publishing servers are 5.0.1224.0 which is SP1 HF4 and the clients are on SP2 HF5.
    Thanks

    Nicke,
    The config files are UTF-8. I did find the same article as yourself, however when searching for the value ‘TakeoverExtensionPointsFrom46=’ within either of the configuration.xml files that text isn’t found.
    No sinister reason not to share the file used, just it’s the same structure as referenced in the article:
    http://technet.microsoft.com/en-us/library/dn745895(v=office.15).aspx. The only difference being that I’m using ProPlusVolume and I’ve set a version number (which is the October
    2014 update). I’ve even looked to follow the above example as closely as possible in just using the ExcludeApp ID of Access and InfoPath, just to try and prove the process. However I still get the usual full package. The version of the Click-to-Run setup.exe
    I’m using is 15.0.4623.1001, so later than the version specified at the end of that article which is 15.0.4619.1000. Where can I expect to see the elements excluded? Will it be when loading the package into the management console or would it just not appear
    on the machine when delivered?
    <Configuration>
      <Add SourcePath="C:\OfficeDeploymentToolV2" Version="15.0.4659.1001" OfficeClientEdition="32">
        <Product ID="ProPlusVolume">
          <Language ID="en-us" />
    <ExcludeApp ID="Access" />
    <ExcludeApp ID="InfoPath" />
        </Product>
      </Add>
    </Configuration>
    3). We’ve not used global publishing in our environment yet so I will try that. I’ve set both GlobalRefreshEnabled and GlobalRefreshOnLogon to True and when using the command Get-AppvPublishingServer on the client I’m testing with I can see this is pulled
    through correctly. I’ve also added the client name to the AD group used to grant access to the package and it is published. However nothing is pulling through onto the Client, so are there any steps I’ve missed or misinterpreted when looking to set this up?
    I guess the global publishing is there to keep in with licensing for Office being per device? On a slight aside, as Windows licensing is being changed to allow per user licensing
    http://www.zdnet.com/microsoft-to-make-per-user-windows-licensing-available-to-enterprise-customers-7000035401/ does anyone know if there are any plans to allow for Office / Project / Visio licenses to go per user as well? We’re a volume license customer
    rather than subscription based so I think a lot of the options to selectively deploy Visio and Project are excluded for us.
    Dan,
    Ok that explains why the security could be tripping out then and leading to this result. As above I’ll try with global publishing and see how I get on.
     From what I’ve read / watched  I think only one Office 2013 package can be published to a machine, so we would be unable to have a separate package for Visio and a separate package for Project and then attempt to deliver
    them both together. If a user wanted both Project and Visio then I guess we’d need to have a combined Project and Visio package to cover than scenario, but then 2 more separate Project and Visio packages for those who would only want either Project and Visio
    (I think).
    The scenario we’re looking at is to see whether we are able to deliver Project and / or Visio to different users through an AppV package and this will then cover users on XenApp or on fat clients. Only a small proportion of our
    users will need access to Project and / or Visio so therefore we’d only have a small amount of Project and Visio licenses.
    However from what I’ve tested up to this point and from what I’ve picked up from Forum posts / watched on TechEd sessions is that as publishing is Global and is unable to use different security groups for different elements of the
    suite, then using Office through AppV is only suitable if you will be delivering the whole suite (including Project and Visio) to all of your users. So in a scenario where you’d only want certain elements to be delivered to a handful of users then you’d need
    to keep with traditional ESD methods to have this installed onto fat clients and steer clear of XenApp. If wanting to install to XenApp then a lockdown tool like AppSense or AppLocker would also need to be brought into the equation.
    Is my understanding above correct or have I missed some options / methods?
    If the full Office package is always delivered but a company only has Office licenses and no Project and Visio licenses for all its users, how do they stop Project and Visio being delivered and being available? Or again if you have
    this use case is the AppV method one which will be unsuitable?
    Thanks

Maybe you are looking for

  • Variation on itunes 6.0.1 (3) problems

    My new 6.0.1 (3) works just fine in all respects EXCEPT that the program crashes when I try to connect to the music store, or, to update a podcast. I haven't had the whole computer crash like others have, and I haven't lost the library, as have other

  • What is the best way to link 4 Airport units together wirelessly?

    Hi guys, I have a home with tick walls and creating  a decent wireless network was always a challenge. Recently I’ve decided to go for Apple products since I had a 4th gen airport express that worked well for airplay. I bought a new time capsule, air

  • Fact Column Name displayed as a Legend (Pivot)

    All, The report has a Horizontal Stacked Bar Chart. Activity Status that has values Auto Closed & Open is pulled in the Column Section of the Pivot All Activity that has value 'All Activities' is pulled in the Row Section Measure Section has the # of

  • How to develop a simple HMI in LabView

    Hello, I need to develop a very simple HMI for TestStand. This HMI must only show some IDs of the DUT and the Name and Result of the step actually running. The language I know best is LabView, so I would like to write this HMI in this language. I loo

  • Volume changes on music

    Haven't seen any topics on this so I thought I'd bring it up. I seem to have finally stabilized my AirTunes connection, but I have one outstanding issue: the volume. When a song is playing, sometime the volume level changes for a while and then retur