Eddie,
To persist the messages to disk when Orion shuts down, add a
persistence-file entry to your queue, like so:
queue host=127.0.0.1 name=Eye location=jms/EyeQueue
persistence-file=../persistence/jms/eyeQueue.queue
descriptionEye/description
/queue
In my limited experience, this works fine during normal Orion shutdowns, but
does not if Orion terminates abnormally (crashes, kill -9 or X the window).
HTH,
Ernie
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Eddie
Sent: Tuesday, May 29, 2001 7:59 AM
To: Orion-Interest
Subject: Re: Re: ATM example - deployment error - PLEASE some HELP
Hellu there,
I already solved it myself.
How ???
I did an upgrade to 1.5.1. Spend some time, such that all my other
applications worked again.and yes the tiny jms application works as
well:
onMessage
Received new quote : Hello, World
Unknown command: -1
ejbRemove called
---
I only have still this Unknow command when I have jms.debug set to true
when starting orion!!!
Another question: how are the queue's managed and how can I
monitor/influence this ??? For example: when I restart orion, my queues's
are lost or not ??? how does this works ??
Eddie
- Original Message -
From: Eddie [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Monday, May 28, 2001 7:48 PM
Subject: Re: ATM example - deployment error - PLEASE some HELP
Ok... forgot something...
I did some debugging by starting orion with the options:
-Djms.debug=true -Dmulticast.debug=true
I then receive the following when I run the client (sends a message):
Orion/1.4.7 initialized
Unknown command: -1
-
Anyone any idea, what this means and where this comes from :-(
(I can't find this anywhere in my application nor the config dir of Orion)
BTW: when I play around with atm I don't get this unknown command but
mayby this is because I don't get to the logging part. When do I get to
this
part ??
Eddie
- Original Message -
From: Eddie [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Monday, May 28, 2001 7:13 PM
Subject: Re: ATM example - deployment error - PLEASE some HELP
Ok,
I now have my tiny jms client submitting messages, but the ejb doesn't
consume them.
I use the atm example as guideline and have this running. However when I
have a look at the atm example, I notice that neither does atm logs !!1
That
is, there doesn't appear anything in the table com_acme_atm_ejb_mainlog
table, whereas other tables are filled!!
What are the specific orion requirements, such that the jms-ejb consumes
the
message ?? ( I am running on 1.4.7) and how can I debug the problem
(look
at
the topics's or somthing like that )?? I don't get any output from orion
in
any log !! (strange!!!)
I will shortly explain my client and ejb hereunder as they are really
short:
The ejb-jar.xml:
ejb-jar
enterprise-beans
message-driven
descriptionJMS logger/description
ejb-nameHello/ejb-name
ejb-classHelloMSGBean.HelloBean/ejb-class
transaction-typeContainer/transaction-type
message-selectorJMSType='mainLogMessage'/message-selector
message-driven-destination
destination-typejavax.jms.Topic/destination-type
/message-driven-destination
/message-driven
/enterprise-beans
/ejb-jar
The onmessage part in the ejb:
public void onMessage(Message message) {
System.out.println(onMessage);
TextMessage textmessage = null;
if (message instanceof TextMessage) {
textmessage = (TextMessage)message;
} else {
return;
}
--
The client part:
---
ctx=new InitialContext(p);
tcf=(TopicConnectionFactory)ctx.lookup(java:comp/env/jms/theTopicConnection
Factory);
tcon = tcf.createTopicConnection();
tcon.start();
tsession = tcon.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
topic = (Topic)ctx.lookup(java:comp/env/jms/theTopic);
tpublisher = tsession.createPublisher(topic);
TextMessage message = tsession.createTextMessage();
message.setJMSType(mainLogMessage);
message.setText(Hello, World);
tpublisher.publish(message);
The part in the jms.xml file (I am not sure if this is necessary!!!??):
-
topic name=Demo Topic location=jms/theTopic
descriptionA dummy topic/description
/topic
--
The application-client.xml:
-
application-client
display-nameSomething/display-name
resource-ref
res-ref-namejms/theTopicConnectionFactory/res-ref-name
res-typejavax.jms.TopicConnectionFactory/res-type
res-authContainer/res-auth
/resource-ref
resource-ref
res-ref-namejms/theTopic/res-ref-name
res-typejavax.jms.Topic/res-type
res-authContainer/res-auth
/resource-ref
