I'm on a platform where a daemon is not currently supported (HP-UX 11.23, JDK 1.6.0, synapse 1.1.1). Could anyone suggest a shutdown script for synapse that's a bit more graceful than a kill on the PID? I would hate to kill Synapse in the midst of a proxy transaction. Is there a way to stop incoming transactions (close the port or return an appropriate http status code) for a minute or two and then shutdown synapse when proxy transactions have completed?
Can WS-Policy be applied to other inbound-to-synapse services not defined as proxy services? It looks like a ws-policy can be applied to endpoints, but not to inbound non-proxy services. True? I understand that you can't make a registry-based synapse configuration dynamic, but couldn't a clustered environment appear to be dynamic if you use a full registry-based configuration (like sample 11). With 2 instances of Synapse sharing the same configuration file, you update the shared configuration file with the new configuration, restart instance#1 with the new configuration while instance#2 has the old configuration and then restart instance#2 with the new configuration. With an apache proxy for failover in front of the cluster it would appear to have no downtime and the configuration would change, wouldn't it? ~john
