Hi,

I'm facing an issue using camel-cache 2.13.1 in a route, it blows with a
with 
**[__DEFAULT__] DEBUG net.sf.ehcache.util.UpdateChecker  - Update check
failed: *
java.net.SocketTimeoutException: connect timed out
*. See complete trace below. 

Found similar issue with quartz but resolved. Is there a property that I
need to set in the route to disable it as in quartz?
*Route:*

from("direct:suspend")
             .setHeader(CacheConstants.CACHE_OPERATION, 
constant(CacheConstants.CACHE_OPERATION_ADD))
             .setHeader(CacheConstants.CACHE_KEY, 
constant("cache_cts_userlist"))
            
.to("cache://CTSUserCache?maxElementsInMemory=1000&memoryStoreEvictionPolicy=MemoryStoreEvictionPolicy.LFU"
+
                         
"&overflowToDisk=true&eternal=true&timeToLiveSeconds=200&timeToIdleSeconds=200"
+
                          
"&diskPersistent=true&diskExpiryThreadIntervalSeconds=200");


*Trace:*
[main] DEBUG org.apache.camel.component.cache.CacheProducer  - Adding an
element with key cache_cts_userlist into the Cache
[main] DEBUG net.sf.ehcache.store.disk.Segment  - put added 0 on heap
[main] DEBUG net.sf.ehcache.store.disk.Segment  - put updated, deleted 0 on
heap
[main] DEBUG net.sf.ehcache.store.disk.Segment  - put updated, deleted 0 on
disk
[%0043%0054%0053%0055ser%0043ache.data] DEBUG
net.sf.ehcache.store.disk.Segment  - fault removed 0 from heap
[%0043%0054%0053%0055ser%0043ache.data] DEBUG
net.sf.ehcache.store.disk.Segment  - fault added 0 on disk
*[__DEFAULT__] DEBUG net.sf.ehcache.util.UpdateChecker  - Update check
failed: *
java.net.SocketTimeoutException: connect timed out
        at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
        at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
        at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
        at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
        at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
        at java.net.PlainSocketImpl.connect(Unknown Source)
        at java.net.SocksSocketImpl.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at sun.net.NetworkClient.doConnect(Unknown Source)
        at sun.net.www.http.HttpClient.openServer(Unknown Source)
        at sun.net.www.http.HttpClient.openServer(Unknown Source)
        at sun.net.www.http.HttpClient.<init>(Unknown Source)
        at sun.net.www.http.HttpClient.New(Unknown Source)
        at sun.net.www.http.HttpClient.New(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown
Source)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown 
Source)
        at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
Source)
        at
net.sf.ehcache.util.UpdateChecker.getUpdateProperties(UpdateChecker.java:153)
        at net.sf.ehcache.util.UpdateChecker.doCheck(UpdateChecker.java:117)
        at 
net.sf.ehcache.util.UpdateChecker.checkForUpdate(UpdateChecker.java:104)
        at net.sf.ehcache.util.UpdateChecker.run(UpdateChecker.java:95)
        at java.util.TimerThread.mainLoop(Unknown Source)
        at java.util.TimerThread.run(Unknown Source)

*Links below might be related:*
https://jira.terracotta.org/jira/browse/QTZ-29
https://issues.apache.org/jira/browse/SHINDIG-1617?jql=text%20~%20%22updatechecker%22




--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-cache-2-13-1-fails-on-UpdateChecker-tp5753294.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to