Connection refused

Terracotta | sppnew | 6 years ago
  1. 0

    ehcache 1.3 - cahce not initialized and listener is not working | 11 months ago Connection refused
  2. 0

    ehcache 1.3 - cahce not initialized and listener is not working

    Terracotta | 6 years ago | sppnew Connection refused
  3. 0

    When CAS sends the PGT back to a clustered client, that cluster must perform synchronous replication, as the client will retrieve the PGT from the storage within milliseconds. However, when one of the nodes (configured for manual peer discovery because multicast does not work at that site) goes down, Ehcache throws the following exception: SEVERE: Servlet.service() for servlet default threw exception net.sf.ehcache.distribution.RemoteCacheException: Error doing put to remote peer. Message was: Connection refused to host: AAA.BBB.CCC.DDD; nested exception is: Connection refused at net.sf.ehcache.distribution.RMISynchronousCacheReplicator.replicatePutNotification( at net.sf.ehcache.distribution.RMISynchronousCacheReplicator.notifyElementPut( at net.sf.ehcache.event.RegisteredEventListeners.notifyElementPut( at net.sf.ehcache.Cache.put( at net.sf.ehcache.Cache.put( at at org.jasig.cas.client.util.CommonUtils.readAndRespondToProxyReceptorRequest( at org.jasig.cas.client.validation.Cas20ProxyReceivingTicketValidationFilter.preFilter( at org.jasig.cas.client.validation.AbstractTicketValidationFilter.doFilter( at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( at org.apache.catalina.core.ApplicationFilterChain.doFilter( at org.apache.catalina.core.StandardWrapperValve.invoke( at org.apache.catalina.core.StandardContextValve.invoke( at org.apache.catalina.core.StandardHostValve.invoke( at org.apache.catalina.valves.ErrorReportValve.invoke( at org.apache.catalina.valves.AccessLogValve.invoke( at org.apache.catalina.core.StandardEngineValve.invoke( at org.apache.catalina.connector.CoyoteAdapter.service( at org.apache.coyote.http11.Http11Processor.process( at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( at$ at This exception propagates all the way to Tomcat (it's re-thrown in 3.1.12), which causes the application server to report HTTP result code 500. When CAS receives that code, it does not include the PGTIOU in the /serviceValidate response even though all the live client nodes have received the PGT. I think it should be OK for EhcacheBackedProxyGrantingTicketStorageImpl to catch the RemoteCacheException when replicating synchronously, log it, and NOT propagate it to allow CAS to operate normally. After all, one of the reasons to have a cluster is to be able to take down a node and continue operating the cluster.

    Apereo Issues | 6 years ago | Adam Rybicki Connection refused
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    jbpm-console war deployment failed

    Google Groups | 3 weeks ago | Unknown author
    org.hibernate.exception.GenericJDBCException: Could not open connection
  6. 0

    jbpm-console war deployment failed

    Google Groups | 3 weeks ago | Unknown author
    javax.resource.ResourceException: IJ031084: Unable to create connection

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis


      Connection refused

      at net.sf.ehcache.distribution.ManualRMICacheManagerPeerProvider.listRemoteCachePeers()
    2. Ehcache
      1. net.sf.ehcache.distribution.ManualRMICacheManagerPeerProvider.listRemoteCachePeers(
      2. net.sf.ehcache.distribution.RMISynchronousCacheReplicator.listRemoteCachePeers(
      3. net.sf.ehcache.distribution.RMISynchronousCacheReplicator.replicatePutNotification(
      4. net.sf.ehcache.distribution.RMISynchronousCacheReplicator.notifyElementPut(
      5. net.sf.ehcache.event.RegisteredEventListeners.notifyElementPut(
      6. net.sf.ehcache.Cache.put(
      7. net.sf.ehcache.Cache.put(
      7 frames
      1 frame
      1 frame