Re: Orion and JMS: javax.naming.NameNotFoundException]
Hi Kesav, Thank you very much for your help, it was as simple as that. Thanks again, Dan Kesav Kumar wrote: If you want to get any resource in your Servlet/jsp you got define resource-ref in your web.xml. One basic information as long as you are in the same container you don't need any parameters to JDNI context. You need jndi.properties only when you try to access from outside the container. Your servlets/jsp/ejb/applicationclient are in the same orion container so in all these components you can directly get JNDI context by Context ctx = new InitialContext(); As long as you are in the same container there is no need for jndi.properties. Regarding the JMS you got define resource-ref in your web.xml. Any container resource of ejb resource you want to use in web tier i.e in servlets/jsp you have to define resource-ref and ejb-ref correspondingly. For JMS which is a resource so you have to declare resource-ref in your web.xml like the following. resource-ref res-ref-namejms/theQueueConnectionFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type res-authContainer/res-auth /resource-ref resource-ref res-ref-namejms/myQueue/res-ref-name res-typejavax.jms.Queue/res-type res-authContainer/res-auth /resource-ref Inside your servlet/jsp for connection factory lookup for jms/theQueueConnectionFactory and for queue lookup for jms/myQueue. snip...
Re: Orion and JMS: javax.naming.NameNotFoundException]
Hi David,
Thank you for your help, this example code might be very useful. What
I'm trying to do is centralised login service, to allow a central
authentication service to control acces to different web applications
that can even be in different hosts. I already succesfully implemented
the login part, but now I want to be able to logout from all the
applications at once, and I also want to be able to trace in one place
the user movements through the different applications. That's why I
thought about using JMS to implement the communication between the
different applications and the central authorization site. My concern is
now whether JMS, specifically Orion's implementation, is mature enough
as to have all my applications depending from it. Or are JMS
implementations in general as inmature and buggy as Michel J. Cannon
stated?
Thank you again,
D.
From: David Libke [EMAIL PROTECTED] jue 16:47
Subject: RE: Orion and JMS: javax.naming.NameNotFoundException]
To: Orion-Interest [EMAIL PROTECTED]
Daniel,
This my second reply to your question. Apperantly my first was lost since another
reply submitted after yours appeared
on the list yesterday but not yours.
In addition, you might want to apply the following edits to jms.xml:
.- Configure jms.xml with this content:
jms-server port=9127 host=
queue name=Demo Queue location=jms/demoQueue
descriptionA dummy queue/description
/queue
log
file path=../logs/jms.log /
/log
/jms-server
This class might simplify your use of messaging:
public class MessageSender implements Serializable
{
public MessageSender(String queueName, String topicName) throws MagnetException
{
this.queueName = queueName;
this.topicName = topicName;
initMessaging();
}
private void initMessaging()
{
try
{
if (queueName == null topicName == null)
{
throw new IllegalArgumentException(MessageSender: initMessaging: No
topic name or queue name);
}
InitialContext jndiEnc = new InitialContext();
if (queueName != null)
{
QueueConnectionFactory factory = (QueueConnectionFactory)
jndiEnc.lookup(JNDINames.QUEUE_CONNECTION_FACTORY);
qConnect = factory.createQueueConnection();
qConnect.start();
qSession = qConnect.createQueueSession(false,
Session.AUTO_ACKNOWLEDGE);
try
{
requestQ = (Queue)jndiEnc.lookup(JNDINames.JMS_DIRECTORY +
queueName);
}
catch (NameNotFoundException nnfex)
{
requestQ = qSession.createQueue(queueName);
}
qSender = qSession.createSender(requestQ);
}
if (topicName != null)
{
TopicConnectionFactory factory = (TopicConnectionFactory)
jndiEnc.lookup(JNDINames.TOPIC_CONNECTION_FACTORY);
System.out.println(MessageSender: initMessaging: got connection
factory + factory);
tConnect = factory.createTopicConnection();
tConnect.start();
tSession = tConnect.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);
try
{
requestT = (Topic)jndiEnc.lookup(JNDINames.JMS_DIRECTORY +
topicName);
}
catch (NameNotFoundException nnfex)
{
requestT = tSession.createTopic(queueName);
}
publisher = tSession.createPublisher(requestT);
}
}
catch (JMSException jmsex)
{
throw new UndeclaredThrowableException(jmsex, MessageSender:
initMessaging: + jmsex.getMessage());
}
catch (NamingException nex)
{
throw new UndeclaredThrowableException(nex,
MessageSender: initMessaging: Problem looking up
JmsQueueConnectionFactory);
}
}
protected void finalize()
{
try
{
if (qConnect != null)
qConnect.close();
qConnect = null;
qSession = null;
qSender = null;
requestQ = null;
if (tConnect != null)
tConnect.close();
tConnect = null;
tSession = null;
publisher = null;
requestT = null;
}
catch (JMSException jex)
{
}
}
private void writeObject(java.io.ObjectOutputStream out) throws IOException
{
try
{
if (qConnect != null)
qConnect.close
RE: Orion and JMS: javax.naming.NameNotFoundException]
Daniel,
For the logout service I think I would use durable 'logout' topic which
would guarantee delivery. If you believe you might run into high volume
degradation, then look at SonicMQ messaging server. They wrote the book on
JMS -- literally.
Dave
-Original Message-
From: Daniel López [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 24, 2001 2:45 AM
To: Orion-Interest
Subject: Re: Orion and JMS: javax.naming.NameNotFoundException]
Hi David,
Thank you for your help, this example code might be very useful. What
I'm trying to do is centralised login service, to allow a central
authentication service to control acces to different web applications
that can even be in different hosts. I already succesfully implemented
the login part, but now I want to be able to logout from all the
applications at once, and I also want to be able to trace in one place
the user movements through the different applications. That's why I
thought about using JMS to implement the communication between the
different applications and the central authorization site. My concern is
now whether JMS, specifically Orion's implementation, is mature enough
as to have all my applications depending from it. Or are JMS
implementations in general as inmature and buggy as Michel J. Cannon
stated?
Thank you again,
D.
From: David Libke [EMAIL PROTECTED] jue 16:47
Subject: RE: Orion and JMS: javax.naming.NameNotFoundException]
To: Orion-Interest [EMAIL PROTECTED]
Daniel,
This my second reply to your question. Apperantly my first was lost since
another reply submitted after yours appeared
on the list yesterday but not yours.
In addition, you might want to apply the following edits to jms.xml:
.- Configure jms.xml with this content:
jms-server port=9127 host=
queue name=Demo Queue location=jms/demoQueue
descriptionA dummy queue/description
/queue
log
file path=../logs/jms.log /
/log
/jms-server
This class might simplify your use of messaging:
public class MessageSender implements Serializable
{
public MessageSender(String queueName, String topicName) throws
MagnetException
{
this.queueName = queueName;
this.topicName = topicName;
initMessaging();
}
private void initMessaging()
{
try
{
if (queueName == null topicName == null)
{
throw new IllegalArgumentException(MessageSender:
initMessaging: No topic name or queue name);
}
InitialContext jndiEnc = new InitialContext();
if (queueName != null)
{
QueueConnectionFactory factory = (QueueConnectionFactory)
jndiEnc.lookup(JNDINames.QUEUE_CONNECTION_FACTORY);
qConnect = factory.createQueueConnection();
qConnect.start();
qSession = qConnect.createQueueSession(false,
Session.AUTO_ACKNOWLEDGE);
try
{
requestQ =
(Queue)jndiEnc.lookup(JNDINames.JMS_DIRECTORY + queueName);
}
catch (NameNotFoundException nnfex)
{
requestQ = qSession.createQueue(queueName);
}
qSender = qSession.createSender(requestQ);
}
if (topicName != null)
{
TopicConnectionFactory factory = (TopicConnectionFactory)
jndiEnc.lookup(JNDINames.TOPIC_CONNECTION_FACTORY);
System.out.println(MessageSender: initMessaging: got
connection factory + factory);
tConnect = factory.createTopicConnection();
tConnect.start();
tSession = tConnect.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);
try
{
requestT =
(Topic)jndiEnc.lookup(JNDINames.JMS_DIRECTORY + topicName);
}
catch (NameNotFoundException nnfex)
{
requestT = tSession.createTopic(queueName);
}
publisher = tSession.createPublisher(requestT);
}
}
catch (JMSException jmsex)
{
throw new UndeclaredThrowableException(jmsex, MessageSender:
initMessaging: + jmsex.getMessage());
}
catch (NamingException nex)
{
throw new UndeclaredThrowableException(nex,
MessageSender: initMessaging: Problem looking up
JmsQueueConnectionFactory);
}
}
protected void finalize()
{
try
{
if (qConnect != null)
qConnect.close();
qConnect = null;
qSession = null;
qSender = null;
requestQ = null
Re: Orion and JMS: javax.naming.NameNotFoundException]
Hi Michael, I apologize if any of the facts that I exposed on my mail seemed to you to be a complain. My intention was to explain that I had sent two messages to the list that I had not seen, just to warn people so if they got too copies, they would know it was not intentional. And the second part to let people know that I was not sure whether nobody was reading my messages, or no one was actually using Orion JMS. I the way I expressed it offended you, I apologize but I don't think it deserved such a harsh response. regards, D. Michael J. Cannon wrote: What browser/MTA? Alos check the Oracle knowledge bank on OTN.oracle.com The server is up, the server is down...so what? Your messages eventually make it here and you eventually get an answer. You didn't pay anything for your answer, so quit complaining, or go to a support company (or switch and get a slower server or pay upwards of USD$6000 minimum for it. Your problem is that JMS and the agents for it aren't yet mature and, besides commercial ISVs, few use the libs. Try the Sun and usenet lists, If you're having probs w/ Orion's JMS, perhaps you should try JBoss (slower) or Jakarta's or the Sun RI. Michael J. Cannon
RE: Orion and JMS: javax.naming.NameNotFoundException]
Title: RE: Orion and JMS: javax.naming.NameNotFoundException]
Daniel,
This
my second reply to your question. Apperantly my first was lost since another
reply submitted after yours appeared on the list yesterday but not
yours.
In
addition, you might want to apply the following edits to
jms.xml:
.- Configure jms.xml with this content:
jms-server port="9127" host=""
queue name="Demo Queue" location="jms/demoQueue"
descriptionA dummy queue/description
/queue
log
file path="../logs/jms.log" /
/log
/jms-server
This
class might simplify your use of messaging:
public
class MessageSender implements Serializable{ public
MessageSender(String queueName, String topicName) throws
MagnetException
{ this.queueName =
queueName; this.topicName =
topicName;
initMessaging(); }
private void
initMessaging()
{
try
{ if
(queueName == null topicName ==
null)
{
throw new IllegalArgumentException("MessageSender: initMessaging: No topic name
or queue
name");
}
InitialContext jndiEnc = new
InitialContext();if
(queueName !=
null)
{
QueueConnectionFactory factory =
(QueueConnectionFactory)
jndiEnc.lookup(JNDINames.QUEUE_CONNECTION_FACTORY);qConnect
=
factory.createQueueConnection();
qConnect.start();
qSession = qConnect.createQueueSession(false,
Session.AUTO_ACKNOWLEDGE);
try
{
requestQ = (Queue)jndiEnc.lookup(JNDINames.JMS_DIRECTORY +
queueName);
}
catch (NameNotFoundException
nnfex)
{
requestQ =
qSession.createQueue(queueName);}
qSender =
qSession.createSender(requestQ);
} if
(topicName !=
null)
{
TopicConnectionFactory factory =
(TopicConnectionFactory)
jndiEnc.lookup(JNDINames.TOPIC_CONNECTION_FACTORY);
System.out.println("MessageSender: initMessaging: got connection factory " +
factory);
tConnect =
factory.createTopicConnection();
tConnect.start();
tSession = tConnect.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);
try
{
requestT = (Topic)jndiEnc.lookup(JNDINames.JMS_DIRECTORY +
topicName);
}
catch (NameNotFoundException
nnfex)
{
requestT =
tSession.createTopic(queueName);}
publisher =
tSession.createPublisher(requestT);
}
} catch (JMSException
jmsex)
{ throw
new UndeclaredThrowableException(jmsex, "MessageSender: initMessaging: " +
jmsex.getMessage());
} catch (NamingException
nex)
{ throw
new
UndeclaredThrowableException(nex,
"MessageSender: initMessaging: Problem looking up
JmsQueueConnectionFactory");
}
}
protected void
finalize() {
try
{ if (qConnect !=
null)
qConnect.close(); qConnect =
null; qSession =
null; qSender =
null; requestQ =
null;
if
(tConnect !=
null)
tConnect.close(); tConnect =
null; tSession =
null; publisher =
null; requestT =
null;
} catch (JMSException
jex)
{ }
}
private void
writeObject(java.io.ObjectOutputStream out) throws
IOException
{
try
{ if (qConnect !=
null)
qConnect.close(); qConnect =
null; qSession =
null; qSender =
null; requestQ =
null;
if
(tConnect !=
null)
tConnect.close(); tConnect =
null; tSession =
null; publisher =
null; requestT =
null;
} catch (JMSException
jex)
{ throw
new IOException("MessageSender: writeObject: " +
jex.getMessage());
} }
protected String queueName =
null; protected transient QueueConnection qConnect =
null; protected transient QueueSession
qSession = null; protected transient
QueueSender qSender = null;
protected transient Queue requestQ = null;
protected String topicName =
null; protected transient TopicConnection tConnect =
null; protected transient TopicSession
tSession = null; protected transient
TopicPublisher publisher =
null; protected transient Topic requestT =
null;}
You will need to define the JNDINames interface with the appropriate values
for its attributes.
Then any class that needs to send messages can extend MessageSender and use
the appropriate attributes
This works for me. Let me know if you still have problems or
questions
Dave
-Original Message-From: Kesav Kumar
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, August 22, 2001 3:17
PMTo: Orion-InterestSubject: RE: Orion and JMS:
javax.naming.NameNotFoundException]
If you want to get any resource in your Servlet/jsp you got
define resource-ref in your web.xml. One basic
information as long as you are in the same container you don't need any
parameters to JDNI context. You need
jndi.properties only when you try to access from outside the container.
Your servlets/jsp/ejb/applicationclient
are in the same orion container so in all these components you
can directly get JNDI context by Context ctx = new
InitialContext(); As long as you are in the same
container there is no need for jndi.properties.
Regarding the JMS you got define resource-ref in your
web.xml. Any container resource of ejb resource you want to use in web
tier i.e in servlet
[Fwd: Re: Orion and JMS: javax.naming.NameNotFoundException]
Hi (third try to the list, first ones didn't make it), I haven't got a single answer, so I'm wondering if nobody is using Orion JMS or this mailing list is playing funny with me. Has anybody configured and used Orion JMS? Could somebody please elaborate on the steps necessary to get this thing working? Thanks in advance, D. Daniel López wrote: Hi, I know this topic has been discussed a lot in here, but I haven't been able to find the answer in the archive or in the documentation. The problem is: I decided to have a go with JMS but I can't even start to play with it, as all I get is javax.naming.NameNotFoundException. These are the steps I have followed: .- Configure server.xml with the following line: ... jms-config path=./jms.xml / ... .- Configure jms.xml with this content: jms-server port=9127 host=localhost queue-connection-factory location=jms/QueueConnectionFactory/ queue name=Demo Queue location=jms/demoQueue descriptionA dummy queue/description /queue log file path=../logs/jms.log / /log /jms-server .- Add jndi.properties to my application's classes(WEB-INF/classes), with the following content: java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory java.naming.provider.url=ormi://localhost/ java.naming.security.principal=admin .- Then in my servlet, I just try to see if the objects are there: ... Context ctx = new InitialContext(); QueueConnectionFactory queueConnectionFactory = (QueueConnectionFactory) ctx.lookup(java:comp/env/jms/QueueConnectionFactory); // Exception is thrown in the line above ... The facts: .- JMS Server seems to have been started, as I can see the jms.log file and reads (Date 1.4.5 Started) .- I have tried with various names, with and without java:comp/env, and with various methods (list, listBindings...) with no look. I cannot get a single object to be looked up. .- Platform is WinNt 4.0, JDK1.3.0-c hotspot, Orion 1.4.5 (I also tried 1.5.2 with the same results) So, what have I forgotten to do? It seems like I just forgot to do some essential step. I tried to find the JMS how to by Kesav Kumar but I couldn't find it. Anybody, please? Thank you in advance, D. PD: On a side note, I have seen man people trying to use external JMS providers with Orion, is that so because Orion JMS is buggy? Would it be better to use some external tool like OpenJMS or so? I had thought it would be nice to have everything in the same place, this way you just have to take care of one server. Comments?
RE: Orion and JMS: javax.naming.NameNotFoundException]
Title: RE: Orion and JMS: javax.naming.NameNotFoundException] If you want to get any resource in your Servlet/jsp you got define resource-ref in your web.xml. One basic information as long as you are in the same container you don't need any parameters to JDNI context. You need jndi.properties only when you try to access from outside the container. Your servlets/jsp/ejb/applicationclient are in the same orion container so in all these components you can directly get JNDI context by Context ctx = new InitialContext(); As long as you are in the same container there is no need for jndi.properties. Regarding the JMS you got define resource-ref in your web.xml. Any container resource of ejb resource you want to use in web tier i.e in servlets/jsp you have to define resource-ref and ejb-ref correspondingly. For JMS which is a resource so you have to declare resource-ref in your web.xml like the following. resource-ref res-ref-namejms/theQueueConnectionFactory/res-ref-name res-typejavax.jms.QueueConnectionFactory/res-type res-authContainer/res-auth /resource-ref resource-ref res-ref-namejms/myQueue/res-ref-name res-typejavax.jms.Queue/res-type res-authContainer/res-auth /resource-ref Inside your servlet/jsp for connection factory lookup for jms/theQueueConnectionFactory and for queue lookup for jms/myQueue. - Original Message - From: Daniel Lopez [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Wednesday, August 22, 2001 8:48 AM Subject: [Fwd: Re: Orion and JMS: javax.naming.NameNotFoundException] Hi (third try to the list, first ones didn't make it), I haven't got a single answer, so I'm wondering if nobody is using Orion JMS or this mailing list is playing funny with me. Has anybody configured and used Orion JMS? Could somebody please elaborate on the steps necessary to get this thing working? Thanks in advance, D. Daniel López wrote: Hi, I know this topic has been discussed a lot in here, but I haven't been able to find the answer in the archive or in the documentation. The problem is: I decided to have a go with JMS but I can't even start to play with it, as all I get is javax.naming.NameNotFoundException. These are the steps I have followed: .- Configure server.xml with the following line: ... jms-config path=./jms.xml / ... .- Configure jms.xml with this content: jms-server port=9127 host=localhost queue-connection-factory location=jms/QueueConnectionFactory/ queue name=Demo Queue location=jms/demoQueue descriptionA dummy queue/description /queue log file path=../logs/jms.log / /log /jms-server .- Add jndi.properties to my application's classes(WEB-INF/classes), with the following content: java.naming.factory.initial=com.evermind.server.ApplicationCli entInitialCont extFactory java.naming.provider.url=ormi://localhost/ java.naming.security.principal=admin .- Then in my servlet, I just try to see if the objects are there: ... Context ctx = new InitialContext(); QueueConnectionFactory queueConnectionFactory = (QueueConnectionFactory) ctx.lookup(java:comp/env/jms/QueueConnectionFactory); // Exception is thrown in the line above ... The facts: .- JMS Server seems to have been started, as I can see the jms.log file and reads (Date 1.4.5 Started) .- I have tried with various names, with and without java:comp/env, and with various methods (list, listBindings...) with no look. I cannot get a single object to be looked up. .- Platform is WinNt 4.0, JDK1.3.0-c hotspot, Orion 1.4.5 (I also tried 1.5.2 with the same results) So, what have I forgotten to do? It seems like I just forgot to do some essential step. I tried to find the JMS how to by Kesav Kumar but I couldn't find it. Anybody, please? Thank you in advance, D. PD: On a side note, I have seen man people trying to use external JMS providers with Orion, is that so because Orion JMS is buggy? Would it be better to use some external tool like OpenJMS or so? I had thought it would be nice to have everything in the same place, this way you just have to take care of one server. Comments?
Re: Orion and JMS: javax.naming.NameNotFoundException
I am also facing similar problem please suggest. Vikas - Original Message - From: Daniel López [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, August 14, 2001 12:05 PM Subject: Orion and JMS: javax.naming.NameNotFoundException Hi, I know this topic has been discussed a lot in here, but I haven't been able to find the answer in the archive or in the documentation. The problem is: I decided to have a go with JMS but I can't even start to play with it, as all I get is javax.naming.NameNotFoundException. These are the steps I have followed: .- Configure server.xml with the following line: ... jms-config path=./jms.xml / ... .- Configure jms.xml with this content: jms-server port=9127 host=localhost queue-connection-factory location=jms/QueueConnectionFactory/ queue name=Demo Queue location=jms/demoQueue descriptionA dummy queue/description /queue log file path=../logs/jms.log / /log /jms-server .- Add jndi.properties to my application's classes(WEB-INF/classes), with the following content: java.naming.factory.initial=com.evermind.server.ApplicationClientInitialCont extFactory java.naming.provider.url=ormi://localhost/ java.naming.security.principal=admin .- Then in my servlet, I just try to see if the objects are there: ... Context ctx = new InitialContext(); QueueConnectionFactory queueConnectionFactory = (QueueConnectionFactory) ctx.lookup(java:comp/env/jms/QueueConnectionFactory); // Exception is thrown in the line above ... The facts: .- JMS Server seems to have been started, as I can see the jms.log file and reads (Date 1.4.5 Started) .- I have tried with various names, with and without java:comp/env, and with various methods (list, listBindings...) with no look. I cannot get a single object to be looked up. .- Platform is WinNt 4.0, JDK1.3.0-c hotspot, Orion 1.4.5 (I also tried 1.5.2 with the same results) So, what have I forgotten to do? It seems like I just forgot to do some essential step. I tried to find the JMS how to by Kesav Kumar but I couldn't find it. Anybody, please? Thank you in advance, D. PD: On a side note, I have seen man people trying to use external JMS providers with Orion, is that so because Orion JMS is buggy? Would it be better to use some external tool like OpenJMS or so? I had thought it would be nice to have everything in the same place, this way you just have to take care of one server. Comments? -- --- Daniel Lopez Janariz ([EMAIL PROTECTED]) Web Services Computer Center Balearic Islands University --- * Disclaimer This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. * Visit us at http://www.mahindrabt.com
