"Application authentication required. Incorrect method call." on server start with Queues

Question

Hi people!
I am using a message-driven EJB listening on a queue.
Everytime a start the server, the server deploys the enterprise
application with the MDB and the queue, and then gives this error
message:
"Application authentication required. Incorrect method call."
What am I missing?
Here are more details: The server is in fact CFMX6.1 in
standalone installation and I am using the hidden JRun inside it.
Here is an extract of ejb-jar.xml:
<message-driven>
<ejb-name>ij.portal.EventExecutor</ejb-name>
<ejb-class>ij.portal.EventExecutor</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<!--javax.jms.Queue or javax.jms.Topic-->
<destination-type>javax.jms.Queue</destination-type>
<!--Durable or NonDurable-->
<subscription-durability>Durable</subscription-durability>
</message-driven-destination>
<!--
The queue that this MDB listens to. The name must be mapped
to
a real JNDI name in jrun-ejb-jar.xml.
-->
<resource-env-ref>
<resource-env-ref-name>EventQueue</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
</message-driven>
A part of the jrun-ejb-jar.xml is:
<message-driven>
<ejb-name>ij.portal.EventExecutor</ejb-name>
<jndi-name>ij.portal.EventExecutor</jndi-name>
<resource-env-ref>
<resource-env-ref-name>EventQueue</resource-env-ref-name>
<jndi-name>jms/queue/EventQueue</jndi-name>
<mdb-destination>jms/queue/EventQueue</mdb-destination>
</resource-env-ref>
<message-driven-subscription>
<client-id>MDBSubscriber</client-id>
</message-driven-subscription>
</message-driven>
Finally, here is the jrun-resources.xml that defines the
queue:
<?xml version="1.0" encoding="UTF-8"?>
<!--
<!DOCTYPE jrun-resources PUBLIC "-//Macromedia Inc.//DTD
jrun-resources 4.0//EN"
http://jrun.macromedia.com/dtds/jrun-resources.dtd">
-->
<jrun-resources>
<jms-destination>
<jndi-name>jms/queue/EventQueue</jndi-name>
<destination-name>EventQueue</destination-name>
<destination-type>javax.jms.Queue</destination-type>
</jms-destination>
<jms-connection-factory>
<!-- jms provider factory name. Optional-->
<factory-name>QueueConnectionFactory</factory-name>
<!-- jndi name - name under wich this connection factory
will be available -->
<!-- to client in jndi. Required. -->
<jndi-name>jms/jndi-QueueConnectionFactory</jndi-name>
<!-- connection factory type (required ifno -->
<!-- can be one of the -->
<!-- following: -->
<!-- javax.jms.QueueConnectionFactory, -->
<!-- javax.jms.XAQueueConnectionFactory, -->
<!-- javax.jms.TopicConnectionFactory -->
<!-- javax.jms.XATopicConnectionFactory -->
<type>javax.jms.QueueConnectionFactory</type>
<!-- jms transport (rmi, tcpip, rmiiiopi, intravm).
-->
<!-- Required if no factory name was specified. -->
<transport>RMI</transport>
<!-- userName and password required if seamless
authorization will be used -->
<!-- (can be specified and updated, upon application
deployment via resorce-ref) -->
<username>guest</username>
<password>guest</password>
</jms-connection-factory>
<!-- MDB specifc connection factory - utilizes intra vm
connection, cannot be used by remote client -->
<jms-connection-factory>
<!-- jms provider factory name. Optional-->
<factory-name>MDBQueueConnectionFactory</factory-name>
<!-- jndi name - name under wich this connection factory
will be available -->
<!-- to client in jndi. Required. -->
<jndi-name>jms/jndi-MDBQueueConnectionFactory</jndi-name>
<!-- connection factory type (required ifno -->
<!-- can be one of the -->
<!-- following: -->
<!-- javax.jms.QueueConnectionFactory, -->
<!-- javax.jms.XAQueueConnectionFactory, -->
<!-- javax.jms.TopicConnectionFactory -->
<!-- javax.jms.XATopicConnectionFactory -->
<type>javax.jms.QueueConnectionFactory</type>
<!-- jms transport (rmi, tcpip, rmiiiopi, intravm).
-->
<!-- Required if no factory name was specified. -->
<transport>INTRAVM</transport>
<!-- username and password required if seamless
authorization will be used -->
<!-- (can be specified and updated, upon application
deployment via resorce-ref) -->
<username>guest</username>
<password>guest</password>
</jms-connection-factory>
</jrun-resources>
What am I doing wrong? I should add that the queue and the
MDB actually work. I just want to get rid of the error message.
I have found out that the error message comes from the class
jrun.jms.wrapper.enterprise.JRunConnectionFactoryWrapper, method
createQueueConnection, when instance variable m_useContainerAuth is
false.

Answer 1

I dont think you should it on server-side - you can do it in client side logic. Start playing live stream - if no data is coming - i think you can use ns.time for checking this - then switch to recorded file play.