While trying to send a message to the receipient outside the domain...

Question

While trying to send a message to the receipient outside the domain,the server
sends back the delivery error email message to the sender. this is OK. But for
some reason the the mail server keeps searching for the wrong recepient and
sending back the deleivery error email to the sender periodically. In this way,
it has sent around 450 such messages to my mailbox.
the mail delivery error looks like this :
451.. Name Server timeout while searching a.com in DN
Reporting -MTA;: dns; s-ghq-csc-ocsapp1.tawasul.mil.ae
Received -From-MTA:DNS;w-anh-sic-004.ANH.mil.ae
Final Recepient:RFC822; [email protected]
ACtion: Failed
Remote-MTA:DNS; a.com
Diagnostic-Code:SMTP;451... Name server timeout while searching a.com in DNS
Last-Attempt-Date:Tue, 18Feb 2003 08:34:38 =0000
solution ???

Answer 1

Hi,
This is apparently the week for integration questions!
There's no such product as "WebLogic MQ". I assume that what your trying to do is communicate with MQSeries or some other non-WebLogic vendor.
You cannot use a WebLogic client to communicate with MQ or vice-versa. You must create an MQ client using a MQ JMS connection factory in order to communicate with an MQ destination. Similarly, you must create a WL client using a WL connection factory in order to communicate with a WL destination. This advice applies to any JMS vendor, and is quite similar to the way JDBC drivers work.
Note that if you're communicating with MQ from a client rather than an application that's running on a WebLogic server, then there's often little purpose in using the "Foreign JMS" mapping facilities (in addition, these facilities may not work on the client for all foreign vendors -- I assume it depends on whether the foreign vendor connection factories and destinations are fully serializable/transferable between JVMs). Instead, you might want to consider using the standard JNDI and JMS APIs to communicate with MQ directly (eg, there's no need to involve WebLogic code in this case).
For information on integration, see the WebLogic doc for [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E12839_01/web.1111/e13727/interop.htm#JMSPG553 ] and, if the "MQ" your refering to in this case happens to be MQSeries, also see the blog post [Integrating WebSphere MQ 6 with BEA Weblogic Server 10|http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html].
Note that the majority of MQSeries integration customer apps that I've run across require "exactly-once" behavior, which means they must run on a WebLogic server (not a client) in order to participate in a WebLogic JTA transaction.
Hope this helps,
Tom