JMS C API - Retention Of Non-Acknowledged Messages

I am sending messages via the JMS C API from a session created using CLIENT_ACKNOWLEDGE option in JmsConnectionCreateSession() call. Yet, if I receive a message and do not acknowledge it, then I shut down and bring back up my app, the message is not there.
Shouldn't it be there on startup of app? Is there a special API call to retrieve messages that weren't acknowledeged?
Thanks.
Moshe

I got it to work, i had to reorder the path directories.. which is kind of strange!
here is how i sat up the environment to get the C API to work based on : "JmsContextCreate" return -3 (JMS_JVM_ERROR)
CLASSPATH:
     <somepath>\lib\weblogic.jar
NLSPATH:     
     <somepath>\lib
PATH:
     <somepath>\lib;                              // : jmsc.lib, LIBJMSC_CAT, weblogic.jar or wlfullclient.jar
     <somepath>\bin                              // : jmsc.dll
     C:\Oracle\Middleware\weblogic92\common\lib          // : jni.dll
     C:\Oracle\Middleware\jdk160_18\jre\bin;               // : java.exe++
     C:\Oracle\Middleware\jdk160_18\jre\bin\client;          // : jvm.dll
Directories in ENV->PATH should be ordered like this:
1. <somepath>\lib;                              // : jmsc.lib, LIBJMSC_CAT, weblogic.jar or wlfullclient.jar
2. <somepath>\bin;                              // : jmsc.dll
3. C:\Oracle\Middleware\weblogic92\common\lib;                         
4. C:\Oracle\Middleware\jdk160_18\jre\bin;
5. C:\Oracle\Middleware\jdk160_18\jre\bin\client;

Similar Messages

  • Problem JMS-c api for message Acknowledgement

    Hi,
              I am working in a project that uses bea-JMS C api for
              Communictions.In my project i am using topic messaging for message reciving and sending..Here i am using durablesubscriber for receiving and client Acknowledgement to Acknowledge the message.
              In receiving function I store the message in another JmsMessage for Client-Acknowledgement.
              Here comes one problem that, while i Acknowledge on the receive function each and every message Acknowledge correctly.But while i Acknowledge that message from some other function it return -1 as , that it cannot Acknowledge.The other function is working in another thread.
              Wheather the seprate thread will make the problem for confirmation.

    Similar to JDBC connections, JMS sessions and their related child producers and consumers are not thread-safe (with the one exception of the session.close() method).
              For example, without added application level locking, its not safe to acknowledge a message from one thread while another thread receives or produces a message. This has special implications for asynchronous consumers, as once the asynchronous consumer is created, access to the session and objects is limited to code within the "onMessage()" and "onException()" callbacks.
              This behavior is detailed in the JMS specification.
              Tom

  • Message redelivery with non-transactional message bean JMS standard or weblogic standard?

    It is my understanding (or maybe my assumption) that a message is
              re-queued only if the transaction attribute of a container-managed
              message bean is set to "Required" and the message is PERSISTENT. So if
              it's set to "NotSupported", and thus, message receival is not within a
              transaction, the message would be un-queued and thus never be
              redelivered, should a failure occur within the bean. I discovered that
              even if the message bean is set as "NotSupported", should a failure
              occur within the bean, the message is re-queued to be received again
              at a later time.
              I'm very confused as to whether this mechanism is a JMS standard, or a
              feature of Weblogic. Well, maybe I'm just confused about message
              delivery/re-delivery. I understand that the JMS standard requires
              guaranteed delivery of a message to a receiver. Does this mean a
              message is only considered delivered if an acknowledgement is
              received, regardless of the transaction level? In other words, is the
              JMS standard that a message is considered delivered only if
              acknowledgement is indicated through the container, regardless of the
              transaction level of the message bean itself?
              

    You're right on the second part. That is, a JMS message is not considered to
              be "delivered" until it is acknowledged. There are a number of ways to make
              this happen when programming to the raw JMS API -- a look at the Javadoc for
              JMS or a good JMS book should clarify how to do this.
              With a message-driven bean, the EJB container acknowledges the message after
              you've successfully returned from the "onMessage" method. If you throw a
              RuntimeException from the "onMessage" method, or if it's an MDB with a
              transaction mode of "Required" and you call "setRollbackOnly" on the
              "MessageDrivenContext" object -- then your message will be redelivered.
              Regardless of how a message is acknowledged, if it's not acknowledged then
              it will be redelivered. This has nothing to do with whether the message is
              persistent. The difference is that if a message is persistent, then the JMS
              server is required to keep a copy on stable storage until the message is
              acknowledged so that if the JMS server itself crashes, the message will not
              be lost. For a non-persistent message, on the other hand, if the JMS server
              crashes, then the message may be lost.
              greg
              "Justin" <[email protected]> wrote in message
              news:[email protected]...
              > It is my understanding (or maybe my assumption) that a message is
              > re-queued only if the transaction attribute of a container-managed
              > message bean is set to "Required" and the message is PERSISTENT. So if
              > it's set to "NotSupported", and thus, message receival is not within a
              > transaction, the message would be un-queued and thus never be
              > redelivered, should a failure occur within the bean. I discovered that
              > even if the message bean is set as "NotSupported", should a failure
              > occur within the bean, the message is re-queued to be received again
              > at a later time.
              >
              > I'm very confused as to whether this mechanism is a JMS standard, or a
              > feature of Weblogic. Well, maybe I'm just confused about message
              > delivery/re-delivery. I understand that the JMS standard requires
              > guaranteed delivery of a message to a receiver. Does this mean a
              > message is only considered delivered if an acknowledgement is
              > received, regardless of the transaction level? In other words, is the
              > JMS standard that a message is considered delivered only if
              > acknowledgement is indicated through the container, regardless of the
              > transaction level of the message bean itself?
              

  • Temporary JMS paging files for non-persistent messages

    Hello,
    WLS 9.2
    When does the server clean up, if at all, the temporary paging files created for large non-persistent messages? Should the files be deleted after the messages are acknowledged?
    Thanks,
    Bob

    Or are they really gets stored ?
    i.e the non_persistent messages are not stored atall either in memory or anywhere.
    Or non_persistent messages are stored in memory only ....similar to PERSISTENT messages with no file store/database store ?

  • How can I delete the TemporaryTopic using JMS C API or VC++

    Hello everybody,
    how can I delete the TemporaryTopic after created TemporaryTopic using JMS C API "JmsSessionCreateTemporaryTopic"?
    I checked the document about JMS C API, but I couldn't find any API for delete TemporaryTopic, it's really not existing?
    Or if there's any other way that I can delete TemporaryTopic using VC++? Any comments will be appreciated.
    Thanks for your help!
    Youbing he

    As far as I can tell, there's no C-API option for deleting a temporary topic other than to close the connection used to create the temporary topic. Note that it is inefficient to frequently create and destroy temporary topics.
    You can get pretty much equivalent performance and functionality with a shared regular topic, non-durable subscriptions, and selectors that take advantage of the "indexed subscriber" optimization. (Consumers specify a selector that is unique to them in the exact form of "MyUniqueID NOT NULL", while publishers send to a specific consumer by adding "MyUniqueID" as a message property. The "X NOT NULL" selector format activates the indexed subscriber optimization.)
    Tom
    Edited by: TomB on Apr 27, 2010 10:44 AM

  • Difference between a persistent messages  and non persistent messages in JM

    Hi
    This question is with respect to persistent messages , and non persistent messages .
    As per the docs it says that for persistent messages the QueueSender.send() blocks until it recivies an acknowledgement .
    Here my question is what is the difference between a persistent messages , and non persistent messages
    Thanks in advance .

    The exact behaviour depends on the JMS provider being used. But since non-persistent messages are defined to be unreliable, the provider may indeed decide that it's not necessary for the server to acknowledge the receipt of a non-durable message from a producer.
    Nigel

  • Is WebLogic JMS C API backwards compatible with 8.1

    I need to be able to send a JMS message from a C++ legacy application, so I am looking at using the JMS C API to do this. However, I am stuck with using WebLogic Server version 8.1. The JMS C API came out with version 9, so I am wondering if it would be possible to use it with 8.1?
              Can this be done? Thanks in advance.

    I've shot off an internal email to see if I can get an answer - I'll post again if I get one. Some notes:
              - Prior to 9.0, there was a separate C-API kit available on dev2dev which is supported (via this newsgroup only), I don't know where it is now.
              - I think its likely the 9.0 C-API will work with an 8.1 client (or 7.0 for that matter), I just don't know if this usage supported.
              - You could use the 9.2 C-API with a 9.2 client to communicate with an 8.1 server. This is definitely supported.
              Tom, BEA

  • Solaris JMS C api

              Hello,
              I am having some problems using the JMS C api. The
              call to JmsContextCreate is failing with a -3;
              JMS_JVM_ERROR. The url, username, and password are
              correct and I am passing NULL for the jndiFactory
              to use the deafult Weblogic server context factory
              of "weblogic.jndi.WLInitialContextFactory".
              Setup:
              Solaris 8, Weblogic 8.1 sp1, jdk_141_03, c/c++ client
              using the Studio8 compiler with other third party libraries,
              and the JMS C api obtained from:
              http://ftpna2.bea.com/pub/downloads/jmscapi.ZIP
              The c/c++ client compiles, links, and runs. The
              CLASSPATH and JAVA_HOME environment variables
              have been set accordingly with the JMS C api
              classes directory added to the CLASSPATH.
              I have compiled the c/c++ client with the JMSDEBUG
              defined and it produces the following to stdout/stderr:
              There was an error trying to initialize the HPI library.
              Please check your installation, HotSpot does not work correctly
              when installed in the JDK 1.2 Solaris Production Release, or
              with any JDK 1.1.x release.
              Also the c/c++ client produces another log file
              called "ULOG.pid". Inside this log contains the
              following:
              085910.fusion!?proc.23074.12.-2: 12-01-2003: Weblogic Server Version 7.1
              085910.fusion!?proc.23074.12.-2: LIBJMSC_CAT:15: NLS:6: Message not found, catal
              og LIBJMSC_CAT, set 1, num 15
              It looks like the libjmsc.so library, that is part of
              the jmscapi.ZIP file, is conpiled against an older version
              of jdk and Weblogic. Is there a newer version of the jmscapi.ZIP
              package compiled against a new version of jdk and Weblogic?
              Or is there something going wrong.
              Thanks,
              Keith
              

    It was caused by the 2nd threads' classloader.
              The 2nd thread uses the bootstrap classloader by default when attached to jvm, which loads the 'core' java classes only, not even extended classes.
              <p>
              This cause JNDI factory initialization failed.
              <p>
              The solution is to set the 2nd thread's context loader as the system class loader using JNI. See java.lang.Thread#setContextLoader and java.lang.ClassLoader#getSystemClassLoader.

  • Routing xml (non-soap) messages in OWSM

    Hi all,
    Normaly we receive soap message from our business partners. These soap messages are then routed internally (by OWSM) to our services based on content (content based routing).
    OWSM is used as a proxy. Partners do not refer to a specific service endpoint but to the owsm as the single virtual endpoint.
    Recently a new business partner was added. This partner sends pure xml messages instead of soap messages. These messages are received in OWSM and must also be routed to the right service.
    However, it seems that routing these xml messages in OWSM does not work. Can anybody give an acknowledgement of this finding that xml (non-soap) messages cannot be routed in OWSM?
    If you have any solutions to this issue I would be glad to hear them.
    Many regards,
    Ton
    Edited by: tvdven on 31-mrt-2010 2:23

    Ram--
    Everywhere in XI, the acronym "LCR" is synonymous with "SLD", System Landscape Directory.  It seems like it may be a term they used early on, or maybe it's the German equivalent.  The LCR acronym is sprinkled throughout SAP's underlying code.
    In your error message, it's complaining about the Business System entry in the SLD. 
    My first thought would be that either the source or target business system is not configured in the SLD, or you haven't defined the business system properly in the SOAP adapter configuration.  See the "XI20 Adapter Engine" manual for instructions on how to configure the SOAP adapter. 
    NOTE: You may be able to configure the SLD to make this solution work on your own, but for long-term usage, you're going to want an expert to model your system landscape and configure the SLD properly.
    --Dan King
    Capgemini

  • JMS C API -- Memory usage

    Hi
    Im writing an application to using JMS C API on Soalris platform.
    When Im executing the program , after the connection is made memory usage is shooting up !!!
    Do JMS library reserve any memory when a connection is made. ???
    Does JMS api create any threads ???
    Adv Thanks
    Chandu
    Edited by: Raja_cs on May 27, 2008 11:40 PM

    The client runtime is caching messages sent by the broker (default number is 1000). So I'd expect to see memory usage going up.

  • JMS event generator only gets non-transactional queue msg

    Hi,
    I have created a JMS event generator to listen to a particular queue. It seems to work perfectly fine if, when posting a message to the queue that the JMS EG is listening to, the queue created is a non-transactional queue, i.e. queueConnection.createQueueSession(false, ...).
    However if I created a transactional queue to post message to the JMS EG, i.e. queueConnection.createQueueSession(true, ...), then the JMS EG can't seem to see the message. I checked in the WLI Admin console, JMS EG section, and there are no messages read by the particular JMS EG after I have posted the msg to the queue.
    My question is: is there a known limitation on the JMS EG that it can only read from a non-transactional JMS queue, or is this a bug? (I am using weblogic 8.1 sp2).
    Thanks
    Regards,
    xlfhk

    Hi,
    sorry, just discovered it's my mistake. Instead of using the transaction created when calling queueConnection.createQueueSession(true, ...), and committing that, I created a JTA transaction artificially wrapping the entire chunk of code.
    As a result, I ended up with a pair of transactions that are nested (I think ...), and the external transaction's commit was called when the nested JMS transaction hasn't been committed yet. As a result, no commit ever took place (I think again ...).
    I have now tried calling queueSession.commit() after sending the message. It seems to work fine. Thanks for the help.
    Regards,
    xlfhk.

  • Jms c api does NOT support multiple threads on solaris?

    It appears that weblogic jms c api (solaris) does not work with multiple threads.
              I wrote a simple test program with multiple threads in the following environment:
              <p>
              <pre>solaris 5.7 Generic_106541-22 sun4u sparc SUNW,Ultra-250,
              weblogic 8.1.3
              jdk 1.4.2_b04
              </pre>
              <b>ONLY the first thread is able to create jms queue senders and send text messages without any problem. The second thread always get the following exception:</b>
              <pre>weblogic.jms.common.JMSException
              at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperStat
              e.java:440)
              at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:382)
              at weblogic.jms.client.JMSProducer.send(JMSProducer.java:207)
              Caused by: java.lang.ExceptionInInitializerError
              at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:309)
              at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:258)
              at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:253)
              at weblogic.rjvm.MsgAbbrevInputStream.resolveClass(MsgAbbrevInputStream.java:324)
              at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream
              .java:96)
              at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:117)
              at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
              at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:159)
              at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
              at weblogic.jms.dispatcher.DispatcherImpl_813_WLStub.dispatchSyncTranFuture(Unknown Sour
              ce)
              at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperStat
              e.java:406)
              ... 2 more
              Caused by: <b>java.lang.NullPointerException</b>
              at weblogic.i18ntools.L10nLookup.loadProps(L10nLookup.java:88)
              at weblogic.i18ntools.L10nLookup.<init>(L10nLookup.java:160)
              at weblogic.i18ntools.L10nLookup.init(L10nLookup.java:132)
              at weblogic.i18ntools.L10nLookup.getLocalizer(L10nLookup.java:315)
              at weblogic.management.commo.internal.CommoCommandLineTextFormatter.<init>(CommoCommandL
              ineTextFormatter.java:20)
              at weblogic.management.commo.Commo.<clinit>(Commo.java:89)
              ... 13 more</pre>

    It was caused by the 2nd threads' classloader.
              The 2nd thread uses the bootstrap classloader by default when attached to jvm, which loads the 'core' java classes only, not even extended classes.
              <p>
              This cause JNDI factory initialization failed.
              <p>
              The solution is to set the 2nd thread's context loader as the system class loader using JNI. See java.lang.Thread#setContextLoader and java.lang.ClassLoader#getSystemClassLoader.

  • Jms c api crashes when accessing jms queue senders from different threads

    Does anybody encountered similar problem or know how to solve the following problem?
              <p>
              The jms c api crashes if I created jms queue senders/producers from one threads and have another thread to send messages using the senders:
              <p>
              <b>JMSDEBUG:</b>
              <p>
              JMSDEBUG: An exception occurred at line 281 in file src/jniimpl/JmsUtilities.c
              <b>JMS Exception:</b>
              <pre>
              weblogic.jms.common.JMSException
              at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(Dispa
              tcherWrapperState.java:440)
              at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:382)
              at weblogic.jms.client.JMSProducer.send(JMSProducer.java:207)
              Caused by: <b>java.lang.NoClassDefFoundError
              </b> at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:30
              9)
              at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:25
              8)
              at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:25
              3)
              at weblogic.rjvm.MsgAbbrevInputStream.resolveClass(MsgAbbrevInputStream.
              java:324)
              at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedO
              bjectInputStream.java:96)
              at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.ja
              va:117)
              at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
              at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:159)
              at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
              at weblogic.jms.dispatcher.DispatcherImpl_813_WLStub.dispatchSyncTranFut
              ure(Unknown Source)
              at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(Dispa
              tcherWrapperState.java:406)
              ... 2 more
              </pre>
              <p>
              <b>the ULOG file:</b>
              <p>
              162722.tekton!?proc.16113.1.-2: 04-04-2005: WebLogic Server Version 9.0
              162722.tekton!?proc.16113.1.-2: NLS:4: Cannot open message catalog LIBJMSC_CAT, set 1, num 13; check NLSPATH, LANG=C
              <p>
              <b>NOTE:</b>
              The senders works fine if the same thread creates the senders and uses them to send messages.
              <p>
              <pre>
              Environemnt:
              OS:SunOS 5.7 Generic_106541-22 sun4u sparc SUNW,Ultra-250
              WL: 8.1.3
              C++: Forte 7
              <pre>

    It appears that the problem is caused by the following NPE:
              <pre>
              Caused by: java.lang.NullPointerException
              at weblogic.i18ntools.L10nLookup.loadProps(L10nLookup.java:88)
              at weblogic.i18ntools.L10nLookup.<init>(L10nLookup.java:160)
              at weblogic.i18ntools.L10nLookup.init(L10nLookup.java:132)
              at weblogic.i18ntools.L10nLookup.getLocalizer(L10nLookup.java:315)
              at weblogic.management.commo.internal.CommoCommandLineTextFormatter.<ini
              t>(CommoCommandLineTextFormatter.java:20)
              at weblogic.management.commo.Commo.<clinit>(Commo.java:89)
              ... 13 more
              </pre>

  • Difference between Persistent Messaging and Non Persitent Messaging

    Hi ,
    I have a confusion related to Persistent messaging.
    According to my knowledge the message becomes persistent if the flag JMSDeliveryMode is set
    SO what is it by defalut ??
    Where do messges get stored for time being for non -persistent messages.
    Thanks in Advance:)

    Message persistence is set by Delivery mode attribute of the message producer in the JMS client or it can bet set on a message basis during the send operation. The default value for the delivery mode on the message producer is PERSISTENT.
    Weblogic JMS has a feature to override the delivery mode set by the message producer. This is at the Destination configuration where there is an attribute called the Delivery Mode Override which can take the values:
    No-Delivery: Delivery mode of the message producer will not be overridden
    Persistent: All messages are marked as persistent irrespective of the message producer setting
    Non Persistent: All Messages are marked as non persistent irrespective of the message producer setting.
    All non persistent messages are stored in memory in normal case. If there is a pile up of messages, weblogic moves the body Messages to disk within what is called as a paging store for the JMS server, only retaining message headers in memory. The characteristic of non persistent messages is that it can't survive server restart. So these messages even when they are on the disk within the paging store wont survive the server restarts.

  • Help needed - JMS C API

    I have situation where I need to talk to the legacy application (C++), which is running in a different host. How do I do that?
              Based on reading all the documents and going thru various WL8.1 tutorials, I got an idea that I need to use JMS C API to accomplish that. Correct me if I am wrong, the request needs to sent to the JMS queue (using P2P), and have it picked up by the legacy appplication and put the results back on the queue, which will be picked up by the MDB EJB to process further on the WL8.1.
              1. I am not sure about what is needed in the legacy application host (its a unix machine)?
              2. If any of you could lay-out the logistics on what is needed in the server where have the WL8.1 running, and also on the legacy application host?

    Hi,
              There are a variety of ways to talk to non-java applications. I've appended my notes on the topic.
              If you choose to use the JMS C API (which is JNI based and so requires the JVM), there is no special configuration needed on the server side - just configure JMS connection factories/servers/stores/destinations as per usual.
              If you choose to use the IIOP client (which is not JNI based and so doesn't need the JVM), you would used it to call an EJB (that you write yourself) that in turn calls into JMS. In addition you would need to set the server configuration to enable the "IIOP" protocol on the WebLogic server port the client uses.
              Tom Barnes, BEA
              Non-Java Integration Options
              - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs61/jcom.html
              http://e-docs.bea.com/wls/docs70/jcom/
              http://e-docs.bea.com/wls/docs81/jcom/
              - Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs81/rmi_iiop/
              http://e-docs.bea.com/wls/docs70/rmi_iiop/
              http://e-docs.bea.com/wls/docs61/rmi_iiop/
              Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
              - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
              - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from the client. The servlets in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
              http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
              - Finally, there are .NET/C/C++ integration libraries that are not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.

Maybe you are looking for

  • Creating a alias or a new folder is blocked

    I have a MM as headless server. It has two users both with admin rights. I am working in the folder Library/application support/X It refuses to let me create more folders in folder X or any aliases for that matter. Anybody knows how to get this chang

  • Migarting from Approva to SAP GRC AC 5.3

    Hello All, One of our client using Approva applications now they are planning to move to SAP GRC Access Controls 5.3, so kindly help me or guide he how I proceed. Key doubts u2013 1-How we upload rules in RAR, because we downloaded the rules from App

  • How can i fix corrupted iphone backup

    GM Team,      kindly be informed that i backed my iphone 4G , then i updated to the latest verison on IOS 6.0.1, then after updating i tried to restore from my latest backup. but in evertime i am trying to restore it gives me an error " that the back

  • VTK-1000

    I have installed ORACLE 9i Standard Edition on WinXP Professional Edition. When i try to login to OEM, i get VTK -1000 error. Please advice to resolve this as i am a novice user to Oracle. Thanks Neeraj

  • Illustrator CS5 Doesn't Update Preview in .ai files

    I have a very simple .ai file created in CS3. I turned a layer off in CS5 and saved the file. The layer still shows in the preview image in the finder, in the application I'm using to import the graphic, and on output. Snow Leopard 10.6.7 Another Bug