TransactionMap and TCP*Extend

Hi Guys,
     From what I understand, from a Real Time Client I can't make use of local cache transactions, either single or multi cache. I appreciate that, if for no other reason :), death detection isn't as capable on an RTC node determining rollback conditions might not be robust enough. Is it possible that I can use the invocation service to proxy that operation onto a node in the cache cluster?
     Kind Regards,
     Max

Max,
     This is definitely a very good use case for utilizing the Invocation service over Coherence*Extend.
     Regards,
     Gene

Similar Messages

Cache config for distributed cache and TCP*Extend

Hi,
I want to use distributed cache with TCP*Extend. We have defined "remote-cache-scheme" as the default cache scheme. I want to use a distributed cache along with a cache-store. The configuration I used for my scheme was
<distributed-scheme>
<scheme-name>MyScheme</scheme-name>
<backing-map-scheme>
 <read-write-backing-map-scheme>
 <internal-cache-scheme>
 <class-scheme>
 <class-name>com.tangosol.util.ObservableHashMap</class-name>
 </class-scheme>
 </internal-cache-scheme>
 <cachestore-scheme>
 <class-scheme>
 <class-name>MyCacheStore</class-name>
 </class-scheme>
 <remote-cache-scheme>
 <scheme-ref>default-scheme</scheme-ref>
 </remote-cache-scheme>
 </cachestore-scheme>
 <rollback-cachestore-failures>true</rollback-cachestore-failures>
 </read-write-backing-map-scheme>
</backing-map-scheme>
</distributed-scheme>
<remote-cache-scheme>
<scheme-name>default-scheme</scheme-name>
<initiator-config>
 <tcp-initiator>
 <remote-addresses>
 <socket-address>
 <address>XYZ</address>
 <port>9909</port>
 </socket-address>
 </remote-addresses>
 </tcp-initiator>
</initiator-config>
</remote-cache-scheme>I know that the configuration defined for "MyScheme" is wrong but I do not know how to configure "MyScheme" correctly to make my distributed cache the part of the same cluster to which all other caches, which uses the default scheme, are joined. Currently, this ain't happening.
Thanks.
RG
Message was edited by:
user602943

Hi,
Is it that I need to define my distributed scheme with the CacheStore in the server-coherence-cache-config.xml and then on the client side use remote cache scheme to connect to get my distributed cache?
Thanks,

OutOfMemoryError in TCP Extend nodes?

Hi,
We are facing a starnge issue in which a storage disabled tcp extend node is consistently occupying around 450mb of space?
Whenever we populate data in cache even smaller than 40mb the it starts filling up oblivious space in tcp extend nodes. Although the jmx console doesn't provide any details of data residing in the storage disabled extend nodes.
Ideally how much memory does the extend node storage disabled tcp extend node requires to run? Is it propotional to max amount of data loaded as a single unit. I feel the extend node should hold data for short duration and should free itself.
We are running on DGE cluster with 2 linux machines having 11 cache nodes of 1gb each. Each machine has 2 storage disabled Extend nodes with 500m each through which my client connects.
Thanks
-Amit
Message was edited by:
Rock Solid

Is there any standard way of deciding on the space required by Extend TCP nodes (Storage Disabled)?
In my scnario
We are trying to get a Map Object of 42mb from the cache. The TCP extend node to which the client connects is throwing OutOfMemoryError. We are runing 4 Extend Nodes of 600MB each.
By looking at the JMX console AvailableMB is < 200 MB consistently in Extend TCP Node (Storage disabled).
Why is this Memory not released after the data transfer is done?
Thanks
-Amit

Lock Client-Side TCP-Extends

Hi,
I am running 2 processes on the same server both connecting to one cluster node.
I need to ensure only one process performs a write operation @ a certain time (i.e. the first one to attain the lock).
I am finding that both the processes are getting the lock, and cannot work-out why...
We are using tcp-extends, and I am using the following related cluster configuration:
<caching-scheme-mapping>
<cache-mapping>
<cache-name>cache.cluster.*</cache-name>
<scheme-name>scheme.cluster.system</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<proxy-scheme>
<scheme-name>scheme.cluster.proxy</scheme-name>
<service-name>service.cluster.proxy</service-name>
<thread-count>4</thread-count>
<acceptor-config>
<tcp-acceptor>
<local-address>
<address system-property="datacloud.node.tcp-extend.bind-address">localhost</address>
<port system-property="datacloud.node.tcp-extend.port">11200</port>
</local-address>
<keep-alive-enabled>true</keep-alive-enabled>
</tcp-acceptor>
</acceptor-config>
<proxy-config>
<cache-service-proxy>
<lock-enabled>true</lock-enabled>

</cache-service-proxy>
</proxy-config>
<autostart>true</autostart>
</proxy-scheme>
<replicated-scheme>
<scheme-name>scheme.cluster.system</scheme-name>
<service-name>ReplicatedCache</service-name>
<lease-granularity>member</lease-granularity>
<member-listener>
<class-name>datacloud.cluster.listeners.ClusterMemberListener</class-name>
</member-listener>
<backing-map-scheme>
<local-scheme />
</backing-map-scheme>
<autostart>true</autostart>
</replicated-scheme>
</caching-schemes>
The client copies this scheme by using the following:
 <cache-mapping>
 <cache-name>cache.cluster.lock</cache-name>
 <scheme-name>scheme.remote</scheme-name>
 </cache-mapping>
The lock essentially does:
NamedCache cache = CacheFactory.getCache("cache.cluster.lock")
boolean isLockAcquired = cache.lock("KEY", 5000)
try {
if(isLockAcquired) {
(takes 2 seconds to complete)
} finally {
cache.unlock("KEY")
Why can 2 processes acquire the same lock when asked to acquire it @ the same time?
Edited by: 907011 on 10-Jan-2012 03:33

Hi,
This is my explination of why you are seeing the behaviour you are - I think it is correct but I am sure someone will jump in if not.
1. Your cache config has <lease-granularity>member</lease-granularity> which means that a lock taken out by any thread on a member can be released by the same member. It also means that a Member owns the lock so if I do cache.lock() for a key from some code running on a Member and then do cache.lock() again for the same key on the same Member they will both succeed as the Member owns the lock.
2. Now, when your first process calls <tt>boolean isLockAcquired = cache.lock("KEY", 5000)</tt> it gets the lock but it is not your client process that owns the lock, it is the Extend Proxy your client is connected to that owns it.
3. Consequently when process two, connected to the same Extend proxy, asks for the lock, it gets it too, as it is not your client process that owns the lock, it is the Extend Proxy your client is connected to that owns it.
4. Worse, when process one finishes and releases the lock, then it is released, even though your code in process two still thinks it is running inside the lock.
As I said, that is my understanding of it and why locks do not really work from Extend Clients. In fact there are very few occasions where I would bother to use explicit locks in Coherence (hence my unfamiliarity about the exact workings) as there are usually other, more reliable, ways to achieve the same requirements.
JK

Initial Deserialization on TCP*Extend Server

Hi Guys,
I have observed something on a TCP*Extend server which I can't quite explain. We've got some hairy custom serialization inside an Externalizable bean. I was under the impression that classes aren't deserialized inside the cluster unless they need to be e.g. to processed by entry processors or value extractors on indexes. However, when I put one of these objects from a TCP*Extend client into the cluster on the tcp*extend server I see some slightly odd behaviour on the server where the deserialization method is called on an empty object and the object I've just send from the client is then serialized.
Can I therefore assume there is an extra deserialization/reserialization loop on a tcp*extend server on data obtained from the client?
Kind Regards,
Max

Hi Max,
Yes, currently the ProxyService must deserialize/serialize data sent from/to clients as part of a POF translation step in order to support non-Java clients. We will be extending POF serialization support "into" the cluster in the next Coherence release. Once this is in place, this extra deserialization/serialization step will not be necessary and will be removed from the ProxyService.
Regards,
Jason

TCP Extend Server - Failed to start Service - Oracle Coherence GE 3.5.2/463

Hello,
We are about to go to production I see Failed to start Service in TCP Extend Server (Storage disable node).
Regards
/AG
My Configuration look like the following
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<caching-scheme-mapping>
</caching-scheme-mapping>
<caching-schemes>
<distributed-scheme>
<scheme-name>distributedCache</scheme-name>
<service-name>distributedCache</service-name>
<backing-map-scheme>
<local-scheme>
<eviction-policy>HYBRID</eviction-policy>
<high-units>500</high-units>
<low-units>375</low-units>
<unit-calculator>BINARY</unit-calculator>
<unit-factor>1048576</unit-factor>
</local-scheme>
</backing-map-scheme>
</distributed-scheme>
<proxy-scheme>
<service-name>ExtendTcpProxyService</service-name>
<thread-count>15</thread-count>
<acceptor-config>
<tcp-acceptor>
<local-address>
<address system-property="proxy.listen.address">....</address>
<port system-property="proxy.listen.port">....</port>
</local-address>
</tcp-acceptor>
</acceptor-config>
<autostart>true</autostart>
</proxy-scheme>
</caching-schemes>
</cache-config>
------------------------------------------------------------------------- And the Log looks like the following ------------------------------------
2009-12-04 16:21:54.056/25821.278 Oracle Coherence GE 3.5.2/463 <D6> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=12): Closed: Channel(Id=193159068
6, Open=false)
2009-12-04 16:21:54.058/25821.280 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:4, member=12): Repeating SizeReques
t due to the re-distribution of PartitionSet{220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242
, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256}
2009-12-04 16:21:54.058/25821.280 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:12, member=12): Repeating SizeReque
st due to the re-distribution of PartitionSet{220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 24
2, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256}
2009-12-04 16:21:54.058/25821.280 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:11, member=12): Repeating SizeReque
st due to the re-distribution of PartitionSet{220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 24
2, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256}
2009-12-04 16:21:54.058/25821.280 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:7, member=12): Repeating SizeReques
t due to the re-distribution of PartitionSet{220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242
, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256}
2009-12-04 16:21:54.175/25821.397 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:10, member=12): An exception occurr
ed while processing a SizeRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped) java.lang.InterruptedException
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:269)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:107)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForRedistribution(DistributedCache.CDB:34)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.ensureRequestTarget(DistributedCache.CDB:15)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.sendPartitionedRequest(DistributedCache.CDB:31)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.size(DistributedCache.CDB:13)
at com.tangosol.util.ConverterCollections$ConverterMap.size(ConverterCollections.java:1470)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ViewMap.size(DistributedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.size(SafeNamedCache.CDB:1)
at com.tangosol.coherence.component.util.collections.WrapperMap.size(WrapperMap.CDB:1)
at com.tangosol.coherence.component.net.extend.messageFactory.NamedCacheFactory$SizeRequest.onRun(NamedCacheFactory.CDB:7)
at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
at com.tangosol.coherence.component.net.extend.proxy.NamedCacheProxy.onMessage(NamedCacheProxy.CDB:11)
at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:28)
at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer$DaemonPool$WrapperTask.run(Peer.CDB:9)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:96)
... 18 more
2009-12-04 16:21:54.175/25821.397 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:9, member=12): An exception occurre
d while processing a SizeRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped) java.lang.InterruptedException
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:269)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:107)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForRedistribution(DistributedCache.CDB:34)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.ensureRequestTarget(DistributedCache.CDB:15)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.sendPartitionedRequest(DistributedCache.CDB:31)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.size(DistributedCache.CDB:13)
at com.tangosol.util.ConverterCollections$ConverterMap.size(ConverterCollections.java:1470)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ViewMap.size(DistributedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.size(SafeNamedCache.CDB:1)
at com.tangosol.coherence.component.util.collections.WrapperMap.size(WrapperMap.CDB:1)
at com.tangosol.coherence.component.net.extend.messageFactory.NamedCacheFactory$SizeRequest.onRun(NamedCacheFactory.CDB:7)
at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
at com.tangosol.coherence.component.net.extend.proxy.NamedCacheProxy.onMessage(NamedCacheProxy.CDB:11)
at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:28)
at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer$DaemonPool$WrapperTask.run(Peer.CDB:9)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:96)
... 18 more
2009-12-04 16:21:54.175/25821.397 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:13, member=12): An exception occurr
ed while processing a SizeRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped) java.lang.InterruptedException
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:269)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:107)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForRedistribution(DistributedCache.CDB:34)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.ensureRequestTarget(DistributedCache.CDB:15)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.sendPartitionedRequest(DistributedCache.CDB:31)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.size(DistributedCache.CDB:13)
at com.tangosol.util.ConverterCollections$ConverterMap.size(ConverterCollections.java:1470)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ViewMap.size(DistributedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.size(SafeNamedCache.CDB:1)
at com.tangosol.coherence.component.util.collections.WrapperMap.size(WrapperMap.CDB:1)
at com.tangosol.coherence.component.net.extend.messageFactory.NamedCacheFactory$SizeRequest.onRun(NamedCacheFactory.CDB:7)
at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
at com.tangosol.coherence.component.net.extend.proxy.NamedCacheProxy.onMessage(NamedCacheProxy.CDB:11)
at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:28)
at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer$DaemonPool$WrapperTask.run(Peer.CDB:9)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:96)
... 18 more
2009-12-04 16:21:54.175/25821.397 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:11, member=12): An exception occurr
ed while processing a SizeRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped) java.lang.InterruptedException
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:269)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:107)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForRedistribution(DistributedCache.CDB:34)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.ensureRequestTarget(DistributedCache.CDB:15)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.sendPartitionedRequest(DistributedCache.CDB:31)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.size(DistributedCache.CDB:13)
at com.tangosol.util.ConverterCollections$ConverterMap.size(ConverterCollections.java:1470)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ViewMap.size(DistributedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.size(SafeNamedCache.CDB:1)
at com.tangosol.coherence.component.util.collections.WrapperMap.size(WrapperMap.CDB:1)
at com.tangosol.coherence.component.net.extend.messageFactory.NamedCacheFactory$SizeRequest.onRun(NamedCacheFactory.CDB:7)
at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
at com.tangosol.coherence.component.net.extend.proxy.NamedCacheProxy.onMessage(NamedCacheProxy.CDB:11)
at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:28)
at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer$DaemonPool$WrapperTask.run(Peer.CDB:9)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:96)
... 18 more
2009-12-04 16:21:54.175/25821.397 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:2, member=12): An exception occurre
d while processing a SizeRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped) java.lang.InterruptedException
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:269)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:107)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForRedistribution(DistributedCache.CDB:34)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.ensureRequestTarget(DistributedCache.CDB:15)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.sendPartitionedRequest(DistributedCache.CDB:31)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.size(DistributedCache.CDB:13)
at com.tangosol.util.ConverterCollections$ConverterMap.size(ConverterCollections.java:1470)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ViewMap.size(DistributedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.size(SafeNamedCache.CDB:1)
at com.tangosol.coherence.component.util.collections.WrapperMap.size(WrapperMap.CDB:1)
at com.tangosol.coherence.component.net.extend.messageFactory.NamedCacheFactory$SizeRequest.onRun(NamedCacheFactory.CDB:7)
at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
at com.tangosol.coherence.component.net.extend.proxy.NamedCacheProxy.onMessage(NamedCacheProxy.CDB:11)
at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:28)
at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer$DaemonPool$WrapperTask.run(Peer.CDB:9)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:96)
... 18 more
2009-12-04 16:21:54.176/25821.398 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:6, member=12): An exception occurre
d while processing a SizeRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped) java.lang.InterruptedException
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.util.Base.ensureRuntimeException(Base.java:269)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForPartitionRedistribution(DistributedCache
.CDB:107)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.waitForRedistribution(DistributedCache.CDB:34)
:$
2009-12-04 16:21:54.259/25821.481 Oracle Coherence GE 3.5.2/463 <D4> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:8, member=12): Daemon caught an unh
andled exception (com.tangosol.net.messaging.ConnectionException: channel is closed) while exiting.
2009-12-04 16:21:54.264/25821.486 Oracle Coherence GE 3.5.2/463 <D4> (thread=Proxy:ExtendTcpProxyService:TcpAcceptorWorker:3, member=12): Daemon caught an unh
andled exception (com.tangosol.net.messaging.ConnectionException: channel is closed) while exiting.
2009-12-04 16:21:54.330/25821.552 Oracle Coherence GE 3.5.2/463 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=12): Stopped: TcpAcceptor{Name=Pr
oxy:ExtendTcpProxyService:TcpAcceptor, State=(SERVICE_STOPPED), ThreadCount=0, Codec=Codec(Format=POF), PingInterval=0, PingTimeout=0, RequestTimeout=0, Local
Address=[nybc94lxb01/10.12.101.81:21005], LocalAddressReusable=false, KeepAliveEnabled=true, TcpDelayEnabled=false, ReceiveBufferSize=0, SendBufferSize=0, Lis
tenBacklog=0, LingerTimeout=-1, BufferPoolIn=BufferPool(BufferSize=2KB, BufferType=DIRECT, Capacity=Unlimited), BufferPoolOut=BufferPool(BufferSize=2KB, Buffe
rType=DIRECT, Capacity=Unlimited)}
Exception in thread "Thread-2" java.lang.RuntimeException: Failed to start Service "Proxy:ExtendTcpProxyService:TcpAcceptor" (ServiceState=SERVICE_STOPPED)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.waitAcceptingClients(Service.CDB:12)
at com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:10)
at com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:1)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.closeChannel(Peer.CDB:18)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.closeChannel(Peer.CDB:1)
at com.tangosol.coherence.component.net.extend.Channel.close(Channel.CDB:20)
at com.tangosol.coherence.component.net.extend.Channel.close(Channel.CDB:1)
at com.tangosol.coherence.component.net.extend.proxy.NamedCacheProxy.run(NamedCacheProxy.CDB:30)
at java.lang.Thread.run(Thread.java:619)
Exception in thread "Thread-3" java.lang.RuntimeException: Failed to start Service "Proxy:ExtendTcpProxyService:TcpAcceptor" (ServiceState=SERVICE_STOPPED)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.waitAcceptingClients(Service.CDB:12)
at com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:10)
at com.tangosol.coherence.component.net.extend.Channel.request(Channel.CDB:1)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.closeChannel(Peer.CDB:18)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.closeChannel(Peer.CDB:1)
at com.tangosol.coherence.component.net.extend.Channel.close(Channel.CDB:20)
at com.tangosol.coherence.component.net.extend.Channel.close(Channel.CDB:1)
at com.tangosol.coherence.component.net.extend.proxy.NamedCacheProxy.run(NamedCacheProxy.CDB:30)
at java.lang.Thread.run(Thread.java:619)
Edited by: Anand Gupta on Dec 4, 2009 5:10 PM

David,
Thanks for your detailed response. I will try all that you suggested and let you know my observation at the end. To give a back ground of the application I am working on.
Background
Try to replace home grown cache (very well optimized uses custom serialization using NIO bytebuffer etc.,) my mandate is to replace the legacy cache with coherence (I love coherence product (at least 3.4) from my previous job experience). Since all kind of optimization is done in legacy application I am converting NIO byteBuffer generated by legacy serialization to byteArray and converting ByteArray into POF. Also for various other reasons, I have to send entry processor to do even get and put data from the cluster.
Raw Data Set Size
My data size is just 500MB (In Production). I put enough cache nodes so that raw data is just 50MB per node. (Since it is compute heavy with entry processor and the number of clients are going to be ~2500)
What was happening when I got the exception?
I was doing stress testing of the cache. Not sure if that put lot of garbage in some of the node hence may be the garbage collection pause triggered the re-distribution of partition set. Since the stress testing was on the way it might had cascading effect on all the nodes.
Datagram Test result.
Tx summary 4 peers:
life: 96 MB/sec, 68774 packets/sec
now: 100 MB/sec, 71378 packets/sec, packets/burst: 1029, bursts/second: 69.41594
Success rate ranges from 0.87 to 1.0
Is a success rate less than 0.98 a cause for concern?
Regarding Size (to keep the extend client always connected to the proxy)
I do size request every 5 sec. if there is not other request has gone to the cluster in the past 5 sec.
In one of the oracle presentation it was said that "If you have map listener's and no other request from a long period of time extend client has to do a periodic size request to make sure that connection to proxy is alive"
In this regard my question is "Can the same effect achieved by doing member listener on the extend client and on disconnection do the size request?"
Proxy Size guide lines
In production number of extend clients are going to be ~2500 connected all the time.
Of which 2000 clients with few map listener + entry processor gets (Each of the clients will have distinct and disjoint set of data on which they work and listener)
And the remaining ~500 clients will do all kinds of request on the entire data set.
In this circumstance is there any recommendation for Number of extend-client : Number of extend-server : Number of threads ratio?
Regards
/Anand

Multiple TCP*Extend Proxy

Hi,
I am developing a C++ Client for Coherence and using the TCP*Extend to connect to the Cache.
I am able to run multiples nodes on same machine.
My goal is to add more machines to this setup (is different machine called cluster or node ?).
I would like to have a setup as explained below:
NamedCache: AQRCache
Cache Type: Near Cache (Local and distributed/remote)
Host_A:
Tcp*extend A
Node 1
Node 2
C++clientA running on Host_A talking to TCP*Extend_A.
Host_B:
Tcp*extend_B
Node 3
Node 4
C++clientB running on Host_B talking to TCP*Extend_B.
Host_C:
Tcp*extend_C
Node 5
Node 6
C++clientC running on Host_C talking to TCP*Extend_C.
Other C++ Clients:
C++clientD running on Host_D talking to TCP*Extend_A.
C++clientE running on Host_E talking to TCP*Extend_A.
C++clientF running on Host_F talking to TCP*Extend_A.
Questions:
1. To Add more machines, if I running one more instance on different machine with the same configuration file, will it work?
2. Is it possible to run seperate TCP*Extend Proxy on each Host and it will be part of the same cluster?
3. Or should all the C++ clients should talk to only one TCP*Extend Proxy?
Thanks,
NS

1. To Add more machines, if I running one more instance on different machine with the same configuration file, will it work?Yes, you can add more machines/nodes using the same configuration file.
2. Is it possible to run seperate TCP*Extend Proxy on each Host and it will be part of the same cluster?Yes, you can run multiple proxy nodes in a single cluster. Just about every production cluster has multiple proxy nodes.
3. Or should all the C++ clients should talk to only one TCP*Extend Proxy?No, there is no reason to force all C++ clients to connect to a single proxy. In fact you might consider configuring each client with the entire list of proxy servers. Each client will pick a server at random to connect to, thus ensuring that a single proxy isn't overloaded.
Also take a look at this document: http://coherence.oracle.com/display/COH35UG/Best+Practices+for+Coherence+Extend
Thanks,
Patrick

TCP EXTEND Server SIde configuration

one of the configuration which is required for server proxy scheme is address ofteh server
I can't specify localhost as server and tcp client is going to run on two differenet servers
I have to run this tcp extend server for 3-4 server for failover support
How can I specify address ( IP ADDRESS HERE) which can changed for each server configuration without specifying this config for each server differenetly
can I replace this address besed on property or system parameter or spring injection.
<proxy-scheme>
<service-name>ExtendTcpProxyService</service-name>
<thread-count>5</thread-count>
<acceptor-config>
<tcp-acceptor>
<local-address>
*<address>IP ADDRESS OF SERVER HERE</address>*
<port>9099</port>
</local-address>
</tcp-acceptor>
</acceptor-config>
<autostart>true</autostart>
</proxy-scheme>
</caching-schemes>

Why can't you use localhost? Surely this is what you want unless you are running on a machine with multiple network cards and need to bind to a particular address.
If you really want to be able to specify a different address for each machine you can do this
<proxy-scheme>
<service-name>ExtendTcpProxyService</service-name>
<thread-count>5</thread-count>
<acceptor-config>
 <tcp-acceptor>
 <local-address>
 <address system-property="extend.address"></address>
 <port>9099</port>
 </local-address>
 </tcp-acceptor>
 </acceptor-config>
<autostart>true</autostart>
</proxy-scheme>Coherence will now use the value of the extend.address system property as the value for your address. This can be passed in on the command line like this:
java -cp coherence.jar -Dextend.address=IP_ADDRESS_HERE com.tangosol.net.DefaultCacheServerObviously your command to start the cache servers would probably have more in it than that.
JK

TCP Extend (DefaultCacheServer rejects connections)

Hi guys
Have been trying to setup TCP Extend to make a Linux box use cache configured on a windows box and the DefaultCacheServer rejects TCP connections. The config files I'm using are attached. Can anyone help ?
The DefaultCacheServer comes up nicely
SafeCluster: Name=n/a
Group{Address=224.3.2.0, Port=32367, TTL=1}
MasterMemberSet
ThisMember=Member(Id=1, Timestamp=2007-03-29 16:07:16.026, Address=147.114.162.160:54321, MachineId=17312)
OldestMember=Member(Id=1, Timestamp=2007-03-29 16:07:16.026, Address=147.114.162.160:54321, MachineId=17312)
ActualMemberSet=MemberSet(Size=1, BitSetCount=2
Member(Id=1, Timestamp=2007-03-29 16:07:16.026, Address=147.114.162.160:54321, MachineId=17312)
RecycleMillis=120000
RecycleSet=MemberSet(Size=0, BitSetCount=0
Services
TcpRing{TcpSocketAccepter{State=STATE_OPEN, ServerSocket=147.114.162.160:54321}, Connections=[]}
ClusterService{Name=Cluster, State=(SERVICE_STARTED, STATE_JOINED), Id=0, Version=3.2, OldestMemberId=1}
DistributedCache{Name=DistributedCache, State=(SERVICE_STARTED), Id=1, Version=3.2, OldestMemberId=1, LocalStorage=enabled, PartitionCount=257, Bac
upCount=1, AssignedPartitions=257, BackupPartitions=0}
but when I run the client, I get this
2007-03-29 16:09:42.698 Tangosol Coherence DGE 3.2/367 <D4> (thread=TcpRingListener, member=1): Rejecting connection to member 649 using TcpSocket{Sta
te=STATE_OPEN, Socket=Socket[addr=/172.26.102.115,port=36952,localport=54321]} Attachment: cluster-side-config.xml (*To use this attachment you will need to rename 516.bin to cluster-side-config.xml after the download is complete.) Attachment: client-side-config.xml (*To use this attachment you will need to rename 517.bin to client-side-config.xml after the download is complete.)

Hi pandeyv,
You need to configure an instance of the ProxyService in your cluster-side cache configuration file. Coherence*Extend clients connect to the ProxyService over TCP/IP and not the TcpRingService. The TcpRingService is only used by cluster members for death detection.
See the following for instructions on configuring the cluster and client-side configuration files:
http://wiki.tangosol.com/display/COH32UG/Configuring+and+Using+Coherence*Extend
Additionally, I noticed that you are using an old release of Coherence 3.2. Please upgrade to the latest 3.2 service pack (3.2.2):
http://www.tangosol.com/product-downloads.jsp
Regards,
Jason

TCP Extend Errors

Hi All,
I am getting the below errors in my TCP-Extend Proxy nodes.
Oracle Coherence GE 3.5.3/465p3 <Error> (thread=Proxy:ExendTcpProxyService:TcpAcceptorWorker:7, member=19): Extend*TCP has determined that the connection to "Socket[addr=/11.11.56.123,port=18733,localport=17062]" must be closed to maintain system stability: This connection is 1 messages behind (112820921 bytes); the limit is 60000 messages (100000000 bytes).
What does this mean ? Any serious issues in the cluster ?

Hi user594809 ,
Coherence will close an Extend connection if it thinks that the client is not reading messages off of its queue fast enough as this can destabilise the extend proxy. The limit is 60000 messages behind or 100Mbytes behind.
In your case you have tried to return too much data in a single go (112,820,921 bytes) - I have seen this is often the result of an invocation service call or something similar. What tends to happen in this case is that your client has started to read the message back and while doing this Coherence closes the connection so you get stream exceptions in the client.
If you really need to return such a large amount of data there are a couple of settings you can add to your <tcp-acceptor> configuration on the client
For example:
<tcp-acceptor>
 <local-address>
 <address>localhost</address>
 <port>10000</port>
 </local-address>
 <limit-buffer-size>100000000</limit-buffer-size>
 <suspect-buffer-size>10000000</suspect-buffer-size>
</tcp-acceptor>The limit-buffer-size is the maximum size of the queue in bytes before the connection gets closed - The default is 100Mbytes
The suspect-buffer-size is the size of the queue that Coherence starts to log warnings - The default is 10Mbytes
If you increase the limit-buffer-size you should increase the suspect-buffer-size too.
Note there is a reason that these settings are there in the first place and changing them to allow very large results to be returned could have an adverse affect on your extend proxy node and your cluster so it is up to you to test things properly under load.
JK

ContinuousQueryCache and dropped extend connection

Hi Guys,
It seems that CQC won't automatically recover from a dropped extend connection. This is a problem as we have listeners attached to the CQC which don't get fired if the proxy to which it is connected fails.
CQC also doesn't resync if you access a different remote cache on the same proxy connection.
I've tried adding <heartbeat-interval> to <tcp-initiator> which does nothing.
The only thing that appears to work is to poll cqc.size() on a background thread. At which point it looks from the events received as though the CQC is repopulated form scratch - can you confirm?
Surely there's a better way? If we've added a heartbeat, could we at least have a connection listener so we know if we need to wake up CQCs?
Thanks, Paul

Steps to resolve:
1) Get a reference to your NamedCache using standard coherence API's
2) Create your CQC using the namedCache.
3) Register a member listener for that namedCache so you can detect when the tcp extend connection has gone away, and subsequently returned. When the connection has returned just call cqc.size() to force cqc to reconnect/repolulate.
namedCache.getCacheService().addMemberListener(new MemberListener() {
public void memberJoined(final MemberEvent memberEvent) {
if (memberEvent.isLocal()) {
try{ cqc.size() } catch(Ex....){}
public void memberLeft(MemberEvent memberEvent) {
//could take some action here if needed.
}

How to access OS environment and TCP/IP environment

I'm trying to find a way to access the operating systems commands (I've already figured out how to determine which Windows or which Unix or which Linux I'm in) and TCP/IP commands. In REXX, for example, it's ADDRESS CMD but I don't even have a clue as to what the class would be in Java. Can somebody help, please?
The two kinds of things I'd like to be able to do is issue commands written in whatever language for the environment where the Java program is executing and have the output from these commands come back as a string or series of strings which can then be parsed by the parser we've written for each of the environments we need to deal with (since the same command sometimes results in a different return, depending on the environment where it's running).
For the TCP/IP commands, I'd like to be able to do something like
tcp_ipCommands("ping","www.sun.com");
or
tcp_ipCommands("ping www.sun.com");
depending on how I write it, of course.
Thanks for any light anybody can shed on how to do this.
virginia

Have a Pinger. I can't remember where I stole it from and its from an older API with some deprecated methods. I recall making some 'cosmetic' changes to it at the time and I tested it, so it does work. I've also indicated 2 of the deprecations in the comments.
import java.applet.*;
import java.awt.*;
import java.net.*;
import java.lang.Thread;
// The Pinger object measures network latency by sending a packet
// to the UDP Echo Port (Port 7) and timing how long it takes.
// We use this port instead of ICMP because I would have to
// use native methods in order to produce ICMP packets.
class Pinger implements Runnable{
 static final int echoPort = 7;
 static final int maxPingTime = 3000; // Milliseconds
 static final int pingPollInterval = 100; // Milliseconds
 DatagramSocket socket;
 InetAddress fromIP;
 long sendTime;
 long timeMeasured;
 Thread timeOutMonitor;
 Thread pingListenThread;
 byte packetNumber = 0;
public Pinger(InetAddress pingee){
 fromIP = pingee;
// If needed, start a listener thread to notice the reply.
// then we send out a brief message to the echo port.
// Since the Java thread model does not allow one thread to break
// another one out of a wait, we sleep for brief intervals, waking
// up periodically to see if the reply has come in yet.
public long doPing() {
 byte[] msg = new byte[1];
 msg[0] = ++packetNumber;
 timeMeasured = -1;
 if(socket == null) try {
 socket = new DatagramSocket();
 catch (Exception e) {return(0);}
 if(pingListenThread == null) {
 pingListenThread = new Thread(this);
 pingListenThread.start();
 DatagramPacket packet = new DatagramPacket(msg,msg.length,fromIP,echoPort);
 sendTime = System.currentTimeMillis();
 long timeLimit = sendTime + maxPingTime;
 try {
 socket.send(packet);
 while (System.currentTimeMillis() < timeLimit) {
 Thread.sleep(pingPollInterval);
 if(timeMeasured != -1) // reply has been noticed, so return result.
 return(timeMeasured);
 catch (Exception e) {};
 return(timeMeasured); // return what is probably -1.
// Run method for the listener thread
public void run() {
byte[] repBuf = new byte[1];
DatagramPacket reply = new DatagramPacket(repBuf,repBuf.length);
 try {
 while (true) {
 socket.receive(reply);
 if(repBuf[0] == packetNumber) {
 timeMeasured = System.currentTimeMillis() - sendTime;
 pingListenThread = null;
 return;
 catch (Exception e) {
 pingListenThread = null; return;
// Clean up any dangling listener thread and release the socket.
public void stop() {
 if(pingListenThread != null) {
 pingListenThread.stop();
 pingListenThread = null;
 socket.close();
 socket = null;
public class PingDisplay extends Applet {
 Pinger ping;
 TextField timeDisplay;
 String fromHost;
 Button refreshButton;
public void init(){
 try {
 fromHost = this.getCodeBase().getHost();
 // Alternative for testing on unrestricted browsers.
 // fromHost = "www.3dcom.com";
 ping = new Pinger(InetAddress.getByName(fromHost));
 timeDisplay = new TextField("Waiting");
 timeDisplay.setEditable(false);
 this.setLayout(new BorderLayout());
 this.add("Center",timeDisplay);
 refreshButton = new Button("Ping");
 refreshButton.resize(40,20);
 this.add("East",refreshButton);
 catch (Exception e) {}
public void start(){
 super.start();
 displayPing();
public void stop(){
 super.stop();
 ping.stop(); // Thread.stop() is depricated but it still works
void displayPing() {
 timeDisplay.setText("Pinging: " + fromHost); // let user know test underway
 long echoTime = ping.doPing(); // conduct actual test
 if(echoTime == -1) // check timeout status
 timeDisplay.setText(fromHost + " timed out.");
 else // display time in button
 timeDisplay.setText("Latency to " + fromHost + ": " + Long.toString(echoTime) + " ms.");
// When "Ping" button pressed, rerun and redisplay.
// Method also depricated here
public boolean action(Event e, Object what) {
 if((e.target == refreshButton) && (e.id == Event.ACTION_EVENT)) {
 displayPing();
 return (true);
 return(false);
}

Adobe Cloud and CS6 extended trial.

I bought CS6 recently and it is registered in my name. For some reason I found myself on a trial of Adobe Cloud and CS6 extended which I do not want. The trial has finished but when I try quitting it, it will not allow me to use my CS6. How do I get round this problem?

Hi Livlah-T,
Everything looked normal with your account but it didn't appear you had completed the 30 day license check.
My recommendation would be
- Launch Adobe Application Manager from either the Start menu (Windows) or Applications folder (Mac) and install all available product updates.
- Once this is complete launch whatever product was showing up as a trial and click the "License this software" and sign in with your Adobe ID.
If the next time you launch the product it is still coming up as a trial, you might try creating a new administrator account and going through the "License this software" process again
Windows 7 - http://windows.microsoft.com/en-IN/windows7/Create-a-user-account
http://social.technet.microsoft.com/wiki/contents/articles/create-a-new-user-account-in-wi ndows-7.aspx
Windows 8 - http://windows.microsoft.com/en-IN/windows-8/create-user-account
10.7 - http://support.apple.com/kb/PH4600
10.8 - http://support.apple.com/kb/PH11468
and double-check nothing is interfering with the 30 day license check process
http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
Ensure you can reach
https://lm.licenses.adobe.com
and nothing is blocking access such as the hosts file or firewall software
Hope that helps,
-Dave

What is difference between adobe photoshop and photoshop extended cs5

what is difference between adobe photoshop and photoshop extended cs5

Hi,
The biggest difference is the 3D feature set is only available in Ps Extended CS5. Exclusive to Extended CS5 also are timeline for video editing, Dicom format support, Stack mode blending, analysis measurement tools, and some 32-bit painting capabilities.
Some things have changed for the Photoshop Extended CS6 version, mainly enabling more of the video editing features for both products.
regards,
steve

[solved] problems with timeouts and tcp retransmission

I've recently upgraded my archlinux and am having real problems with the network.
I have checked the configuation and all seems ok.
Everything like DNS/Gateways/IPs all seem to be setup (not changed anything from when it was working before)
I read about setting the MTU manually
ifconfig eth0 mtu 1492
I tried this but it doesn't seem to make any difference
Looking at the packetflow on wireshark it seems that there are a huge amount of TCP Dup ACK and TCP Retransmission when trying to POST
If I boot into windows everything is fine so unfortunately it seems that it might be something with linux
Everything in linux seemed to be working ok before I upgraded
Last edited by equilibrium (2009-12-05 15:13:14)

seems that I am still unable to post from my arch system
$ dmesg | grep sky2
sky2 driver version 1.23
sky2 0000:02:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
sky2 0000:02:00.0: setting latency timer to 64
sky2 0000:02:00.0: Yukon-2 EC chip revision 2
sky2 0000:02:00.0: irq 29 for MSI/MSI-X
sky2 eth0: addr xx:xx:xx:xx:xx:xx
sky2 eth0: enabling interface
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:17:31:F4:ED:A2
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1170 errors:0 dropped:0 overruns:0 frame:0
TX packets:1362 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1101154 (1.0 Mb) TX bytes:197742 (193.1 Kb)
Interrupt:19
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4595 errors:0 dropped:0 overruns:0 frame:0
TX packets:4595 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:541498 (528.8 Kb) TX bytes:541498 (528.8 Kb)
/etc/rc.conf
eth0="eth0 192.168.1.20 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(eth0)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)

TransactionMap and TCP*Extend

Similar Messages

Maybe you are looking for