Notification with user defined type results in PLS-00306: wrong number..

Question

I created a user defined type TLogMessage:
CREATE OR REPLACE TYPE TLogMessage AS OBJECT
module VARCHAR2(4000),
severity NUMBER,
message VARCHAR2(4000)
I also created a multi-consumer queue using this type as payload.
My callback procedure in the package PK_SYST_LOGMESSAGE is defined as follows:
     PROCEDURE DefaultLoggerCallback(
          context          RAW,
          reginfo          SYS.AQ$_REG_INFO,
          descr          SYS.AQ$_DESCRIPTOR,
          payload          RAW,
          payload1     NUMBER
Finally, I registered the callback procedure as follows:
          DBMS_AQADM.ADD_SUBSCRIBER(
               queue_name      => QUEUE_NAME,
               subscriber      => SYS.AQ$_AGENT(
                                        name => 'default_logger',
                                        address => NULL,
                                        protocol => NULL
          DBMS_AQ.REGISTER(
               SYS.AQ$_REG_INFO_LIST(
                    SYS.AQ$_REG_INFO(
                         name          => QUEUE_NAME || ':default_logger',
                         namespace     => DBMS_AQ.NAMESPACE_AQ,
                         callback     => 'plsql://MTDX.PK_SYST_LOGMESSAGE.DefaultLoggerCallback',
                         context          => HEXTORAW('FF')
               1
However, when I put a message in the queue using this procedure:
     PROCEDURE LogMessage(
          pModule          VARCHAR2,
          pSeverity     NUMBER,
          pMessage     VARCHAR2
     IS
          vMessage               TLogMessage;
          vEnqueueOptions          DBMS_AQ.ENQUEUE_OPTIONS_T;
          vMsgProperties          DBMS_AQ.MESSAGE_PROPERTIES_T;
          vMessageHandle          RAW(16);
     BEGIN
          vMessage := TLogMessage(module => pModule, severity => pSeverity, message => pMessage);
          vEnqueueOptions.visibility := DBMS_AQ.IMMEDIATE;
          vMsgProperties.correlation := pModule;
          vMsgProperties.priority := -pSeverity;
          -- Enqueue the message to all subscribers
          DBMS_AQ.ENQUEUE(
               queue_name               => QUEUE_NAME,
               enqueue_options          => vEnqueueOptions,
               message_properties     => vMsgProperties,
               payload                    => vMessage,
               msgid                    => vMessageHandle
     EXCEPTION
          WHEN no_subscribers THEN
               -- No subscribers on the queue; ignore
               NULL;
     END;
I can see the message in the queue, by querying the queue view. I can also see that Oracle tried to call my callback procedure, because in the trace file I see the following:
*** 2009-02-13 08:52:25.000
*** ACTION NAME:() 2009-02-13 08:52:24.984
*** MODULE NAME:() 2009-02-13 08:52:24.984
*** SERVICE NAME:(SYS$USERS) 2009-02-13 08:52:24.984
*** SESSION ID:(609.3387) 2009-02-13 08:52:24.984
Error in PLSQL notification of msgid:4F7962FEDD3B41FA8D9538F0B38FCDD1
Queue :"MTDX"."LOGMESSAGE_QUEUE"
Consumer Name :DEFAULT_LOGGER
PLSQL function :MTDX.PK_SYST_LOGMESSAGE.DefaultLoggerCallback
: Exception Occured, Error msg:
ORA-00604: Fout opgetreden bij recursief SQL-niveau 2.
ORA-06550: Regel 1, kolom 7:
PLS-00306: Onjuist aantal of type argumenten in aanroep naar 'DEFAULTLOGGERCALLBACK'..
ORA-06550: Regel 1, kolom 7:
PL/SQL: Statement ignored.
So.. how many parameters does Oracle expect, and of what type? Is there any way to find out? What is wrong with my code?

Answer 1

Ok, found it... I had defined the last parameter of the callback procedure as 'payload1' (that is: 'payload-ONE') instead of 'payloadl' ('payload-ELL'). It all works like a charm now.
What a way to waste two whole days!