Writing to a JMS Queue via Timer Method.

[Annie McCall]

Hi,
My server is BEA WebLogic Server 8.1.
I currently inherited a JMS app where it uses an Asyncronous Message bean.
The logic in this bean is very simple. It has an OnMessage method which looks at the input message. This input message is just a textmessage, depending on it's value it will implement different processes.
For example:

public void onMessage(Message inMessage) {
        TextMessage msg = null;
        
           try {                
            if (inMessage instanceof TextMessage) {
                      
            msg = (TextMessage) inMessage;
            String msgString=msg.getText();
            
            if (msgString.equalsIgnoreCase("Annie")){
               AnnieTest();
            
            }
             else{
                if (!(inMessage instanceof  
                        weblogic.jms.common.HdrMessageImpl)) {
                system.err.println("event-portlet.AsyncProcessorBean.onMessage: Message of wrong type: " +
                   inMessage.getClass().getName());
                  }
            }  
            
        } catch (Throwable te) {
            System.err.println("event-portlet.AsyncProcessorBean.onMessage: " +
                "Exception: " + te.toString());
        }
        
    } 
      private void AnnieTest(){
    
    String filename = "\\\\Proj\\Wlv_apps\\Eventstuff.dat";
    PrintWriter out = null;
    File myFile = new File(filename);
        try{
    FileOutputStream outStream = new FileOutputStream(myFile);
    out = new PrintWriter(outStream);
 
   out.println("Hello, this is a test.");
    out.println(45);
    out.close();
        }catch(Exception e){
        
        
        }finally{
        
        out.close();
        }
    
    }

I have a listener which gets kicked off when the server starts.
This listener kicks off a method (let's say around every 10 minutes) that attempts to write to the JMS queue.

Now is where the problem occurs.

Here is the logic that attempts to send a text message to the queue.

public static void sendMessage(String text) throws Exception{
Context jndiContext = null;
QueueConnectionFactory  queueConnectionFactory = null;
        QueueConnection         queueConnection = null;        
        QueueSession            queueSession = null;
        Queue                   queue = null;
        String                  queueName = "event.jms.asyncProcessingQueue";
        QueueSender             queueSender = null;
        TextMessage             message = null;
        
        
        
        // get the jndi context
try {
            
jndiContext = new InitialContext();
        } catch (NamingException e) {
           throw new Exception("Could not create JNDI API " +
        "context: " + e.toString());
            
        }
        
        // get the connection factory and queue
        try {
            queueConnectionFactory = (QueueConnectionFactory)
                jndiContext.lookup("event.jms.ConnectionFactory");
            
            queueConnection = 
                queueConnectionFactory.createQueueConnection();
            
            queue = (Queue) jndiContext.lookup(queueName);
            
        } catch (NamingException e) {
        throw new Exception("JNDI API lookup failed: " + 
        e.toString());
        }
        try {
        
            queueSession = 
                queueConnection.createQueueSession(false, 
                    Session.AUTO_ACKNOWLEDGE);
            
            queueSender = queueSession.createSender(queue);   
            
         
            message = queueSession.createTextMessage(); 
            message.setText(text);
                        
          
            queueSender.send( message);
                       /* 
             * Send a non-text control message indicating end of
             * messages.
             */
            queueSender.send(   
            queueSession.createMessage)                     
            
        } catch (JMSException e) {
            System.out.println("Exception occurred: " + 
                e.toString());
        } finally {
            if (queueConnection != null) {
                try {
                    queueConnection.close();
                } catch (JMSException e) {}
            }
        }
            
}   

The exception occurs on this line:

queueSender = queueSession.createSender(queue);

I get this error:

[B]Exception occurred: weblogic.jms.common.JMSSecurityException: Access denied to r
esource: type=<jms>, application=, destinationType=queue, resource=eventAsyncPro
cessingQueue, action=send[/B]

I think I am getting this because the process is being kicked off on the server rather than from an user.

Does anyone know how to do this?

I tried using an anonymous producer but doing this:

queueSender = queueSession.createSender(null); 

But then I got an invalid destination error.


Has anyone attempted to this before ( Write to a JMS queue from a method which was set off with a timer)?

Any help would be greatly appreciated,

[ February 06, 2008: Message edited by: Annie McCall ]
[ February 06, 2008: Message edited by: Annie McCall ]

[Annie McCall]

Hi All,

I do have an answer to my JMS Security Exception. I will post the
solution for any JMS newbies like myself.

It was not an application code fix but rather a change in the security
configuration of my JMS queue on my Weblogic Server.

Since there was no "real" user, the user context is "guest". All I
needed to do was add an 'acl entry' for guest in the send action of my
JMS queue.

An 'acl entry' is really adding a row in a table in the realm database.

For example:
<CODE>
insert into weblogic.realm_acl_entries values ('realm_domain','guest', 'JMS QUEUE NAME','send', null);</CODE>

Hope this information helps someone who may encounter the same problem.