Sun ONE Message Queue and JMS

Is Sun ONE Message Queue software a reference implementation or a
product?

Sun ONE Message Queue is a product. It is a production implementation of the JMS
specification. Sun ONE Message Queue software performs the function of a message
broker, essentially serving as a common denominator enabling the exchange of
information between applications. A number of competing products perform this same
function, but Sun ONE Message Queue software adds the availability of JMS APIs to
promote an open, industry-standard interface to messaging middleware, thus
promoting the platform interoperability of Java while also enabling developers of
business applications to write to only a single interface. In and of itself, this does not
make Sun ONE Message Queue software unique since other MOM products also
conform to the JMS specification. However, the combination of JMS with high
performance, low cost, ease of use, and Sun's world class distribution and support
channels makes Sun ONE Message Queue software a highly competitive product.

Similar Messages

  • HTTP transport  and Sun ONE Message Queue

    How do I get the HTTP transport to work? The docs don't seem to be correct.

    There are a couple of errors in the Sun ONE Message Queue docs that shipped with
    the product.
    The following are corrections for those errors.
    Servlet configuration
    Please note the following correction in the Sun ONE Message Queue 2.0
    Administration Guide, Appendix B -
    The class name of the HTTP Servlet in Step 4 of the "Configuring the Tunnel Servlet"
    section is given as:
    com.sun.messging.jmq.transport.httptunnel.servlet.HTTPTunnelServlet
    The correct class name is :
    com.sun.messaging.jmq.transport.httptunnel.servlet.HttpTunnelServlet
    Client setup for HTTP support
    1.The following connection factory attributes must be specified to use the HTTP
    tunnel connection support.
    JMQConnectionType :
    Set this attribute to "HTTP".
    JMQConnectionURL :
    Set this attribute to the URL that will be used to connect to the Sun ONE
    Message Queue message service (i.e. the URL for the HTTP tunnel servlet).
    Note that there is no need to specify the JMQConnectionHandler attribute as
    mentioned in the Sun ONE Message Queue 2.0 Administration Guide -
    Appendix B.
    2.Before running the client application, set the CLASSPATH variable to include
    jmqutil.jar in addition to the standard Sun ONE Message Queue jar files.
    This file is located at "/opt/SUNWjmq/lib/jmqutil.jar".
    If the "jmqutil.jar" file is not included in the CLASSPATH, the client will get a
    "java.lang.NoClassDefFoundError" exception for the class
    "com/sun/messaging/jmq/util/JMQTimerTask".
    3.If you are using an HTTP proxy, set "http.proxyHost" to the proxy server host
    name, and "http.proxyPort" to the proxy server port number using the -D
    command line option.
    An example command line would look like this:
    java -classpath
    /opt/SUNWjmq/lib/jms.jar:/opt/SUNWjmq/lib/jmq.jar:
    /opt/SUNWjmq/lib/jndi.jar:.:/opt/SUNWjmq/lib/jmqutil.jar
    -DJMQConnectionType=HTTP
    -DJMQConnectionURL=http://webserver:80/imq/servlet ClientApplicaiton

  • How compatible is Sun ONE Message Queue with IBM Websphere MQ and at what version levels?

     

    Hi,
    Just check the "Troubleshooting Installation Problems section " at http://docs.sun.com/source/816-6453-10/windows.html#34247.
    If you still have problems in installation , you can post your question in the Sun ONE message Queue forum
    at http://softwareforum.sun.com/NASApp/jive/forum.jsp?forum=24

  • Sun ONE Message Queue 3.0.1 is now available

    Sun One Message Queue 3.0.1 is now available. Sun ONE Message Queue 3.0.1
    is an implementation of the Java Message Service version 1.1 specification.
    It comes in two editions; a free Platform Edition as well as an Enterprise
    Edition for full-scale, enterprise deployments.
    Noteworthy changes in 3.0.1 (compared to 3.0):
    * Substantial performance boost
    MQ 3.0.1 provides message delivery throughput up to double that
    attained with MQ 3.0, a performance boost that is especially important
    under heavy load conditions.
    * Certified for use with the Sun ONE Application Server 7.0
    MQ 3.0.1 is certified for Sun ONE Application Server 7.0, and is used as
    its native JMS provider. MQ has been integrated with the Application
    Server, providing JMS messaging support in an Application Server
    environment. You can configure the system for an internal MQ message
    server managed with Application Server administration tools, or an
    external MQ message server requiring MQ administration tools.
    * Support for Linux Red Hat 7.2 (JDK 1.4.1)
    MQ 3.0.1 is now certified for JDK 1.4.1 on Linux Red Hat 7.2 (and still
    supported on Linux Red Hat 7.1).
    * Bundled on Solaris
    MQ 3.0.1 Platform Edition will be bundled with Solaris 9 Update 2 when
    it ships in early 2003.
    For more specific details about 3.0.1 please see the product Release Notes
    at: http://docs.sun.com/source/816-6454-10/index.html
    The two editions of Sun ONE Message Queue 3.0.1 are:
    * The Platform Edition provides a free commercial grade JMS implementation,
    ideal for small-scale deployments and development environments on various
    operating environments.
    * The Enterprise Edition delivers maximum scalability and security features
    necessary for larger full-scale deployments.
    For specific details about the editions see the Administration Guide at:
    http://docs.sun.com/source/817-0354-10/overview.html#20864
    For more information about the product or to download the current version
    please visit:
    http://www.sun.com/software/products/message_queue
    Receiving feedback from current and potential customers is important to the
    product team. If you have questions, thoughts for additional features or
    think you have found a bug, we encourage you to send the team feedback.
    Please send mail to [email protected]. If appropriate, be sure to
    include the product version, information on the platform you are using and
    steps to duplicate the problem you are experiencing. If you are interested
    in purchasing the product and have a sales related question send mail to
    [email protected]
    Thank you for your interest in Sun ONE Message Queue!

    Customers who purchased the iPlanet Message Queue for Java version 2.0
    Enterprise Edition, or the iPlanet Java Message Queue version 1.1 Business Edition,
    who also have a current maintenance contract for this product, are entitled to a free
    upgrade. Sun customers should use their normal support channels to request the
    upgrade. All corporate customers with Sun Software Support contracts should be
    automatically notified of the upgrade via the ProductTracker by SubscribeNet
    program. If you haven't, please contact Sun Customer Service online or by phone at
    888-786-8111. Parties interested in upgrading will be required to provide
    proof-of-purchase. Customers of previous versions of the free Developer Editions, or
    customers without a current maintenance contract on this product, can not upgrade
    for free, they must buy the Sun ONE Message Queue 3.0 Enterprise Edition product,
    or they can download the Sun ONE Message Queue 3.0 Platform Edition product for
    free from: http://wwws.sun.com/software/download/download/5275.html

  • SUN One Message Queue: QueueRequestor usage

    All,
    I am trying to send a message to a destination and waiting to getback some information as reply.
    QueueRequestor constructor takes in QueueSession,Queue as parameters
    But the session instance, I am having is .com.sun.messaging.jmq.jmsclient.UnifiedSessionImpl.
    I need few clarifications..
    a) how to use QueueRequestor and how to get QueueSession in Sun One.
    b) is there any other best way to get information back as reply from a destination. ?? ie. I want to send a message to a destination, and wait to get back some information as reply ????
    thanks in advance

    Hi amarnag,
    Let me answer your second question first if thats OK? The Requestor classes (QueueRequestor and TopicRequestor) are the best match from an API perspective for request-response style invocations. To do this any other way you would probably find that you were writing exactly the same code as it already present in the Requestor classes. I would therefore suggest that you use the QueueRequestor class as you are currently doing.
    The code you need to create a QueueRequestor is the same as the code required for any other JMS implementation - do not be worried by the fact that a QueueRequestor requires a QueueSession object. The QueueSession object is simply an interface that a vendor, in your case Sun, must implement. I would presume that the class com.sun.messaging.jmq.jmsclient.UnifiedSessionImpl implements QueueSession.
    The code to use the Requestor is as follows. Note that I am not familiar with Sun ONE Message Queue from a configuration point of view so do not include JNDI configuration:
    Properties props = new Properties();
    // Configuration for Sun ONE Message Queue JNDI goes in here.
    Context jndi = new InitialContext();
    Queue q = (Queue)jndi.lookup("MyQueueName");
    // Note that I do not know the correct name for Sun ONE's default
    // QueueConnectionFactory name, I presume it is QueueConnectionFactory
    QueueConnectionFactory qcf = (QueueConnectionFactory)jndi.lookup("QueueConnectionFactory");
    QueueConnection qc = qcf.createQueueConnection();
    QueueSession qs = qc.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    QueueRequestor qr = new QueueRequestor(qs, q);
    Message request = qs.createMessage();
    // Populate request as neccesary
    Message reply = qr.request(request);
    // Handle reply message

  • 'Bad license dta' with Sun ONE Message Queue trial version

    Why do I get an error message about 'Bad license data' when I attempt to
    use the 90-day trial license on Linux?

    The problem is the permissions of the license file are wrong. Assuming you installed
    the product in /opt/SUNWjmq on your Linux box do the following as root (Super-User)
    and the license should work:
    # chmod 666 /opt/SUNWjmq/lib/lic/jmqbrokertry.lic

  • Sun One App Server 8.1,Sun One Message Q3.6,administered objects in LDAP

    Hi,
    Has anyone tried hosting an MDB on Sun One App Server 8.1 listening to a queue on Sun One Message Queue 3.6 through administered objects in directory server...? It looks quite straight forward but somehow it doesn't seems to work. Any idea if Sun one app server supports this type of architecture...?
    Regards,
    Pritesh

    Hi,
    Even I didn't see any obvious reason why it shouldn't work untill I found that Sun One App Server 8.1 does not support external JNDI lookup to Sun MQ 3.6 through administered objects. However, it is possible using a newly released generic resource adapter for JMS 1.5 RC1. I am still fighiting on it and let you know if it works.
    I was getting an error "JMS resource can not be created" during deployment time.
    Regards,
    Pritesh Thakor

  • (Sun ONE Messaging Server 6.2-8.04)Email sending problem

    situation: user ([email protected]) sent email to [email protected], [email protected], [email protected] and [email protected] then encounter errors message as below, anybody can please help me about what's wrong with the email address or error message?
    This report relates to a message you sent with the following header fields:
    Message-id: <[email protected]>
    Date: Thu, 04 Nov 2010 14:50:19 +0800
    From: [email protected]
    To: [email protected], [email protected], [email protected],
    [email protected]
    Subject: testing
    Your message cannot be delivered to the following recipients:
    Recipient address: @webmail2.rmp.gov.my.lmtp:dccbelaga@lmtpcs-daemon
    Original address: [email protected]
    Reason: Remote SMTP server has rejected address
    Diagnostic code: smtp;555 5.5.4 Unknown RCPT TO parameter ",-2".
    Remote system: dns;webmail2.rmp.gov.my (mbems2 -- Server LMTP [Sun ONE Messaging Server 6.2-8.04 [built Feb 28 2007]])
    Recipient address: @webmail2.rmp.gov.my.lmtp:dccbintulu@lmtpcs-daemon
    Original address: [email protected]
    Reason: Remote SMTP server has rejected address
    Diagnostic code: smtp;555 5.5.4 Unknown RCPT TO parameter ",-2".
    Remote system: dns;webmail2.rmp.gov.my (mbems2 -- Server LMTP [Sun ONE Messaging Server 6.2-8.04 [built Feb 28 2007]])

    This sounds like there is something wrong in your LMTP configuration. Is delivery working at all? Or does it only fail for these addresses?
    I would say to add master_debug to the LMTP channel on the MTA and see what more detail that provides in master debug log files.

  • Integration of Sun One messaging with Trend IMSS

    I have a Sun One messaging server 6.0 with two front ends delivering mails to backend clustered MTA through LMTP.
    I need to integrate Trend IMSS for email scanning which is on a different server on Windows platform.
    Pl*ease help*.
    regards
    jai

    js007 wrote:
    Many Many Thanx ! At least i can see my mails hitting scanner and coming back. But they are in a loop, which i can see that log for the same mail increasing in Trend IMSS.It sounds like the emails from the Trend IMSS system are not being switched to the tcp_scanner source channel.
    You can test IP based channel switching by running:
    ./imsimta test -rewrite random@[IP address of Trend IMSS system] e.g.
    root@peter:2 [sbin] # ./imsimta test -rewrite random@[127.0.0.1]
      address channel        = tcp_intranet                   
      forward channel        =
      backward channel       = tcp_intranet                   
      unique identifier      = blah@[127.0.0.1]
      header forward address = blah@[127.0.0.1]  (route ([127.0.0.1],[127.0.0.1])) (host [127.0.0.1])
      header reverse address = blah@[127.0.0.1]
      envelope forw address  =   (route ([127.0.0.1],[127.0.0.1])) (host [127.0.0.1])
      envelope rev address   = blah@[127.0.0.1]  (route (tcp_intranet-daemon,tcp_intranet-daemon)) (host [127.0.0.1])
      name                   =
      mbox                   = blah
    Extracted address action list:
        blah@[127.0.0.1]
    Extracted 733 address action list:
        blah@[127.0.0.1]
    Address list expansion:
    -13 expansion total.
    Submitted address list:
    Address list error -- 5.1.2 unknown host or domain: blah@[127.0.0.1]Note the: "route (tcp_intranet-daemon,tcp_intranet-daemon)" which due to the following rule:
    [] $E$R${INTERNAL_IP,$L}$U%[$L]@tcp_intranet-daemonYou should see "route (tcp_scanner-daemon,tcp_scanner-daemon)".
    Here is my tcp_scanner definition
    !tcp_scanner
    tcp_scanner smtp mx single_sys subdirs 20 noreverse maxjobs 7 pool SMTP_POOL
    daemon my_a-v_scanner.com enqueue_removeroute
    tcp_scanner-daemonYou should create a new pool for the virus scanner in job_controller.cnf so that problems with the virus scanner don't cause other channels which share SMTP_POOL to build up.
    Also since you are sending to a single anti-virus system you should change "mx single_sys" to "nomx multiple".
    Regards,
    Shane.

  • What is their difference betwwen  Sun ONE Application Server  and J2EE serv

    Sun ONE Application Server is Sun implementation of J2EE server.
    But it seems even no Sun ONE Application Server, use J2EE SDK command
    j2ee -verbose
    we still can launch an Application Server that support EJB, JSP....
    what is their difference betwwen Sun ONE Application Server and J2EE server provided by J2EE SDK ?
    Thanks,

    Sun ONE generally refers to the Sun ONE Application Server version 7.x. This is a J2EE 1.3 compliant application server from Sun. Sun also released a Reference Implementation version (RI) as a requirement of the J2ee 1.3 spec. This is the J2EE server you are refering too. The Sun ONE Application Server 7 is a more robust production ready App Server.
    Going forward, Sun combined the 2 seperate groups to include just 1 release. The J2EE 1.4 Reference Implementation is the Sun Java System Application Server Platform Edition version 8. SJS AS 8 PE is both free and production ready. Other version will include High Availability, Managing and Monitoring features.
    -Jeff

  • Porting varray data from one db to another remote db using queues and jms

    We are trying to port a varray from one db to another db using queues and java jms. The varray is embedded in an object type (necessary according to oracle docs). The varray, embed object, and the queues are identical between the 2 dbs. We have used the capabilities in jdeveloper to generate the necessary classes to access the embed object and its payload the varray.
    However, when we attempt this:
    public void publish( com.wgint.sql.EaiType payload )
    throws JMSException, SQLException
    Connection dbConnection = ((AQjmsSession)session).getDBConnection();
    AdtMessage message = ((AQjmsSession)session).createAdtMessage();
    message.setAdtPayload( payload );
    ( (AQjmsTopicPublisher) publisher ).publish( publisher.getTopic(),
    message,
    agents );
    we get a ora-00902 error, invalid datatype. I cannot find a single example on technet or the internet in which someone has done something similar. I do not know if it is feasible or not.
    Steve

    Do you really need JMS to do this? If not, just let the AQ layer propagate your messages from your local to your remote queue. See the online doc how to do this.

  • Integrate Sun ONE Messaging and Sun ONE Calendar server with Portal 6.0

    We need to integrate (implement a Single Sign On solution) Sun ONE/iPlanet Messaging and Calendar servers with Portal 6.0. The Msg and Cal. servers do not use Portal Profile server as their DS and have a different DS.This directory server is the external DS for Portal. After users login to Portal, they should be able to access Msg and Cal. servers without login to them again.
    1. How do we do this without writing a java code/servlet ?
    2. Is there any way that we could configure DSAME to create the URL,add userID and password to it and forward that URL to above servers ?

    Hi,
    The SunOne communication providers for version 6.0 will be released soon.
    (you can get beta versions from early access program)
    Like in the portal version 3.0 these channels
    are enabling SSO for messaging and calendar servers.
    (I tested them with iMSG5.2 and Calendar5.1.1)
    Cheers,
    Alex :-)

  • Message queues and expiry *HELP*

    My problem is hopefully a simple one to overcome. Without going totally in depth, i have a Server program that creates JMS Object messages and sends them off to a message Queue. Then i have another program, a client, that recieves and processes the object messages accordingly.
    In my case, the server and the client will be on diferent sides of a erroneous wireless setup.
    Basically i want messages to be recieved if, and ONLY if, there is a complete connection to the client, if there is no connection there i want the message to expire. I tried using timeToLive(), but that will not suffice, as there is no way i can tell how long the message will take to reach the JMS provvider, and hence the client.
    Also in using a message Queue the unrecieved messages build up and the latest messages will not be recieved until all outdated ones are recieved. Is there another generic sort of connection that doesn not allow for the build up of messages? unlike topic and queue?

    Hi.
    Strange, you are describing the correct behavior for JMS.
    The simplest way will be to not use JMS at all.
    Since you can't (via JMS) check the connection status, you'd either have to do it
    via the provider's mechanism, or use the TTL.
    As for the queue you are using for the unreceived messages - thar's also a TTL issue. Set a TTL
    and the queue will clear up.
    It might be worthwhile to look into the provider's admin options - perhaps you may be ablr to set ttl at
    the provider itself, which will mean that you don't mind how long it takes the message to get to the provider - only how long it takes it from the provider to the destination.
    Nimo.

  • Non-persistent Queues and JMS API

    Hi,
    Is it possible to use non-persistent queues via JMS API. My application will always get an NullPointerException when trying to create a queue receiver i.e.
    QueueReceiver rec = qsession.createReceiver(queue);
    Any ideas and thx in advance,
    Wolfgang

    Mark,
              If you want this persistent behavior for non-persistent messages, presumably
              for performance reasons, use a persistent QOS backed by a JMS server with
              a file store that has synchronous-writes-disabled. As long as the O/S and/or
              hardware
              doesn't crash, no data will be lost, even if the WebLogic server is killed.
              See the JMS performance whitepaper on dev2dev.bea.com for details.
              Tom
              Mark wrote:
              > If you define a queue to be non-persistent, then all data is lost in the event
              > of a hardware or software failure.
              > What about in the case of a clean shutdown of the weblogic server hosting the
              > queue?
              > Are the messages held in the queue, paged to disk and restored when the server
              > is restarted?
              

  • Sun one server 7 and sun app server 8 incompatibility

    I had all my ejb code running nicely on sun one server 7. Now I have to port to 8 and while the same ear file deploys successfully, I'm unable to make any create calls on my CMP beans. I get server side error "argument type mismatch", but I've checked and rechecked all arguments, number and type, but can't find anything wrong. Any pointers?

    The new one is supposed to be backward comptible. In any case, I've run the migration tool and redeployed, but same issues exist.

Maybe you are looking for