topic Re: Node does not exist when using JMS in a custom behavior in Alfresco Archive

Node does not exist when using JMS in a custom behavior

geemorin — Fri, 19 Jun 2009 14:12:58 GMT

Hi,I hope I'm in the right forum for that kind of question! I'm actually working on a custom behavior that produces a JMS message when an "onContentUpdate" event is raised containing the new node id. I'm injecting the JNDI name of the connection factory and destination in my bean, I initilize them,

Re: Node does not exist when using JMS in a custom behavior

mrogers — Fri, 19 Jun 2009 17:37:11 GMT

You are about to go into a mine-field of distributed transaction processing considerations. And while I'm sure it can be done, as I've said in other threads it won't be easy. For a start you will have to re-plumb all Alfrescos existing transaction handling and caching implementations.

A much easier solution would be to use two separate transactions and drive your JMS message production from the result of your node creation transaction. Its a tiny bit less reliable but much easier.

Another solution would be to kick off a workflow which produces your JMS message and that would have full transactional guarantees.

Re: Node does not exist when using JMS in a custom behavior

geemorin — Fri, 19 Jun 2009 21:03:20 GMT

Thank you for your prompt reply!!

I'm currently investigating if I could use the org.springframework.transaction.support.TransactionSynchronizationManager in combination with the org.springframework.transaction.support.TransactionSynchronization and use the after commit or after completion callback to send my JMS message. I think it might work but again I've never worked with spring so its progressing slowly but surely I'll keep you informed of my progressionn/regression

Have a nice day!

Re: Node does not exist when using JMS in a custom behavior

geemorin — Fri, 19 Jun 2009 21:46:23 GMT

Up to now, this solution seems to work. If you have any comment on how i could improve it or if you see any problems i might run into, tell me!!! Thank you!

private class JMSSynchronization implements TransactionSynchronization{
        
        public JMSSynchronization(String documentId, String documentName, String user, EVENT_TYPE event_type, byte[] documentContent){
            super();
            this.documentId = documentId;
            this.documentName = documentName;
            this.user = user;
            this.event_type = event_type;
            this.documentContent = documentContent;
        }
        
        private String documentId; 
        private String documentName;
        private String user;
        private EVENT_TYPE event_type;
        private byte[] documentContent;
        
        @Override
        public void afterCommit() {}

        @Override
        public void afterCompletion(int arg0) {
            System.out.println("Entering after completion…");
            try {
                BytesMessage bytesMessage = session.createBytesMessage();
                bytesMessage.setStringProperty(PROP_KEY_DOCUMENT_ID, documentId);
                bytesMessage.setStringProperty(PROP_KEY_EVENT_TYPE, event_type.toString());
                
                switch(event_type){
                    case DOCUMENT_ADDED:
                    case DOCUMENT_UPDATED:
                        bytesMessage.setStringProperty(PROP_KEY_DOCUMENT_NAME, documentName);
                        bytesMessage.setStringProperty(PROP_KEY_DOCUMENT_CREATOR, user);
                        break;
                    case DOCUMENT_DELETED:
                    default:
                }
                
                if(sendDocumentContent && documentContent != null){
                    bytesMessage.writeBytes(documentContent);
                }
                
                messageProducer.send(bytesMessage);
            }
            catch (JMSException e) {
                e.printStackTrace();
            }
            System.out.println("Leaving after completion…");
        }

        @Override
        public void beforeCommit(boolean arg0) {}

        @Override
        public void beforeCompletion() {}

        @Override
        public void resume() {}

        @Override
        public void suspend() {}
    }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

private void sendJMSEvent(String documentId, String documentName, String user, EVENT_TYPE event_type, byte[] documentContent){
       JMSSynchronization jmsSynch = new JMSSynchronization(documentId, documentName, user, event_type, documentContent);
       TransactionSynchronizationManager.registerSynchronization(jmsSynch);      
   }‍‍‍‍

Re: Node does not exist when using JMS in a custom behavior

mrogers — Sat, 20 Jun 2009 12:06:42 GMT

Your solution is sound. But have you thought through the consequences of what happens if your JMS call in the callback fails?

Re: Node does not exist when using JMS in a custom behavior

sradha — Tue, 16 Oct 2012 13:00:55 GMT

Hi,

I am trying to execute a script which send jms message to server while any content will getting updated.Can you please mention the steps you followed?