[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-433: ---------------------------------- With dtgov, we have been moving away from using property files, and instead storing configuration in sramp. So might be worth also storing sramps 'event producer' information in sramp. If this is not possible without having a new UI (which might take time), then may be use property file as a stop gap. In terms of the JMS setup - actually durable subscription would have been the most appropriate solution. SRAMP could happily publish on a pre-defined single topic, and clients could either use non-durable subscription to just get notifications, or durable subscription to ensure they don't miss out on anything. The one drawback is the issue we are trying to solve for DTGov - only a single active durable subscriber is permitted - so we couldn't have two or more dtgov clustered servers all operating in a load balanced manner across a durable subscription. This is a pity, as it would have been a good generic solution. ActiveMQ has a capability called Virtual Topics that may provide a solution - but think we need to remain JMS compliant to enable use of other JMS providers if necessary - so looks like we are stuck with queues, and therefore need to configure a queue per interested consumer. I think it would be good to have a default topic on which the events are published - this would cater for systems just interested in being notified - and also enable durable subscriptions for systems that don't want to miss anything. In terms of the queue for dtgov - how about: - have a default queue name configured in properties (not with a dtgov specific name, so could potentially be used by any consumer) - sramp event producer - when it attempts to access the jndi name, if it does not exist, it disables itself (queue must exist before sramp is started) - dtgov install will cause the queue to be created - so no explicit configuration, either by user on installation, or dtgov modifying sramp config thoughts? -- This message was sent by Atlassian JIRA (v6.2.6#6264)