There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

    via by cobar,
    • java.rmi.AccessException: CORBA NO_PERMISSION 9998 Maybe; nested exception is: org.omg.CORBA.NO_PERMISSION: ----------BEGIN server-side stack trace---------- org.omg.CORBA.NO_PERMISSION: vmcid: 0x2000 minor code: 1806 completed: Maybe and returns from the onMessage. However, the container does not remove the message from the queue and we end up in an endless loop. I have changed this to a CLIENT_ACKNOWLEDGEMENT and called message.acknowledge() which solved the endless resending of the same message. However, I am now receiving [#|2009-06-05T14:50:55.121-0500|WARNING|sun-appserver9.1||_ThreadID=30;_ThreadName =p: thread-pool-1; w: 12;_RequestID=5b1ef737-4ba0-44a2-9b0e-707b2b10e3a7;| com.sun.messaging.jms.JMSException: [ACKNOWLEDGE_REPLY(25)] [C4036]: A broker error occurred. :[409] [B1261]: Transa ction acknowledgement could not be added because message 741-[[co nsumer:4198236325854191872, type=NONE]:[consumer:0, type=CLIENT_ACKNOWLEDGE]]TUID=4198236325911618048 has already be en removed user=guest, broker=ndcplc01:43570(50816) at com.sun.messaging.jmq.jmsclient.ProtocolHandler.throwServerErrorException( at com.sun.messaging.jmq.jmsclient.ProtocolHandler.acknowledge( at com.sun.messaging.jmq.jmsclient.SessionImpl.doAcknowledge( at com.sun.messaging.jmq.jmsclient.SessionImpl.acknowledgeFromRAEndpoint( at at at$
    No Bugmate found.