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|javax.enterprise.system.stream.err|_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-166.37.164.45(a3:9:b0:3e:53:95)-59079-1244231440955[[co nsumer:4198236325854191872, type=NONE]:[consumer:0, type=CLIENT_ACKNOWLEDGE]]TUID=4198236325911618048 has already be en removed user=guest, broker=ndcplc01:43570(50816)

Oracle Community | cobar | 8 years ago
  1. 0

    AUTO_ACKNOWLEDGEMENT issues

    Oracle Community | 8 years ago | 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|javax.enterprise.system.stream.err|_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-166.37.164.45(a3:9:b0:3e:53:95)-59079-1244231440955[[co nsumer:4198236325854191872, type=NONE]:[consumer:0, type=CLIENT_ACKNOWLEDGE]]TUID=4198236325911618048 has already be en removed user=guest, broker=ndcplc01:43570(50816)
  2. 0

    Re: CORBA NO_PERMISSION exception with JAAS & wlclient.jar

    Google Groups | 1 decade ago | Andy Piper
    java.rmi.AccessException: CORBA NO_PERMISSION 0 Maybe; nested exception is: org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: Maybe
  3. 0

    Re: CORBA NO_PERMISSION exception with JAAS & wlclient.jar

    Google Groups | 1 decade ago | Andy Piper
    java.rmi.AccessException: CORBA NO_PERMISSION 0 Maybe; nested exception is: org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor >code: 0 completed: Maybe
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Re: CORBA NO_PERMISSION exception with JAAS & wlclient.jar

    Google Groups | 1 decade ago | Andy Piper
    java.rmi.AccessException: CORBA NO_PERMISSION 0 Maybe; nested exception is: org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: Maybe
  6. 0

    Re: CORBA NO_PERMISSION exception with JAAS & wlclient.jar

    Google Groups | 1 decade ago | Andy Piper
    java.rmi.AccessException: CORBA NO_PERMISSION 0 Maybe; nested exception is: org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: Maybe

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. 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|javax.enterprise.system.stream.err|_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-166.37.164.45(a3:9:b0:3e:53:95)-59079-1244231440955[[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()
    2. com.sun.messaging
      OnMessageRunner.run
      1. com.sun.messaging.jmq.jmsclient.ProtocolHandler.throwServerErrorException(ProtocolHandler.java:3930)
      2. com.sun.messaging.jmq.jmsclient.ProtocolHandler.acknowledge(ProtocolHandler.java:2555)
      3. com.sun.messaging.jmq.jmsclient.SessionImpl.doAcknowledge(SessionImpl.java:1321)
      4. com.sun.messaging.jmq.jmsclient.SessionImpl.acknowledgeFromRAEndpoint(SessionImpl.java:1057)
      5. com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:267)
      5 frames
    3. Embedded GlassFish Web
      OneWork.doWork
      1. com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:76)
      1 frame
    4. glassfish-corba-orbgeneric
      ThreadPoolImpl$WorkerThread.run
      1. com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
      1 frame