JMS QueueRequestor not working ??

Hi all.
I am trying to get a Request and Reply mechanism working, but I am getting a weird exception: Exception occurred: javax.jms.InvalidDestinationException: Invalid queue. Does anyone have a suggestion ?
QueueConnection queueConnection = null;
try {
Context ctx = new InitialContext();
QueueConnectionFactory queueConnectionFactory = ( QueueConnectionFactory )
ctx.lookup("jms/QueueConnectionFactory");
queueConnection = queueConnectionFactory.createQueueConnection();
queueSession = queueConnection.createQueueSession( false,Session.AUTO_ACKNOWLEDGE );
Queue queue = queueSession.createQueue( "jms/myQueue" );
queueConnection.start();
QueueRequestor requestor = new QueueRequestor( queueSession, queue );
TextMessage message = queueSession.createTextMessage();
message.setText( "helloooo" );
Message response = requestor.request( message );
System.out.println( ( ( TextMessage ) response ).getText() );
catch (NamingException e) {
System.out.println("Could not create JNDI context: " + e.toString() );
System.exit( 1 );
catch( JMSException ex ) {
System.out.println("Exception occurred: " + ex.toString());
finally {
if (queueConnection != null) {
try {
queueConnection.close();
catch (JMSException e) {}
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Ashok Banerjee ([email protected]):
Try looking up the QueueConnection factory as
java:comp/env/jms/theQueueConnectionFactory.
If you are not finding the QueueCOnnectionFactory itself this will fix it. If problems still persist please provide full stacktrace and the line in source code at which it occurs.
Cheers,
Ashok<HR></BLOCKQUOTE>
I am running this client as stand-alone that's why I am using "jms/QueueConnectionFactory".
The stack trace: javax.jms.InvalidDestinationException: Invalid queue
javax.jms.QueueReceiver com.evermind.server.jms.EvermindQueueSession.createReceiver(javax.jms.Queue, java.lang.String)
javax.jms.QueueReceiver com.evermind.server.jms.EvermindQueueSession.createReceiver(javax.jms.Queue)
void javax.jms.QueueRequestor.<init>(javax.jms.QueueSession, javax.jms.Queue)
void jmsMiddleware.TestServer.<init>()
void jmsMiddleware.TestServer.main(java.lang.String[])
Exception occurred: javax.jms.InvalidDestinationException: Invalid queue
null

Similar Messages

  • Jms is not working properly in clustered environment

    Hi all,
    i am using the application server oc4j 10.1.3.1.0 enterprise edition . my application is standalone application(thick client)
    we are using the jndi.properties as follows ...
    java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
    java.naming.provider.url=opmn:ormi://172.16.1.38:6005:group/Security,opmn:ormi://172.16.1.38:6006:deceval_group/Security
    java.naming.security.principal=oc4juser
    java.naming.security.credentials=oc4juser
    oracle.j2ee.rmi.loadBalance=lookup
    we have two application servers in cluster topology as u can see above we have used one instance from one application server and one from another.
    i have seen that for every instance there one jms server. at runtime it is taking one application servers services
    say opmn port 6005 but when the application is connecting to the another application server say opmn 6006
    here jms is not working properly when i send message
    As we have clustered environment message must be propagated all the applications who use above jndi.properties.
    if i keep use only one application server opmn say
    java.naming.provider.url=opmn:ormi://172.16.1.38:6005:group/Security
    then its is working excellently
    please can u provide any solution ASAP
    thanks in advance
    Manu

    Dear Aravindth
      (.*?) means -> Select all contents from where you start and end,
    For Ex. <month>(.*?)</month> then Select for start <month> and end last </month> tag.
    (?) Match zero or one occurrences. Equivalent to {0,1}.
    (*) Match zero or more occurrences. Equivalent to {0,}.
    (+) Match one or more occurrences. Equivalent to {1,}.
    (.) (Dot). Match any character except newline or another Unicode line terminator.
    (.*?) means -> Zero or more times Match any character except newline or another Unicode line terminator + Match zero or more occurrences. Equivalent to {0,}.+Match zero or one occurrences. Equivalent to {0,1}.
    Could you please refere the below cite :
    http://www.javascriptkit.com/jsref/regexp.shtml
    Thanks & Regards
    T.R.Harihara SudhaN

  • JMS Demo Not working!!!Very poor samples from Oracle.

    Hi i have installed the CHat JMS Sample into Oc4j.
    Everything was OK until i wanted to log into the chat application.
    Then on my oc4j consol the following occured:
    03/10/04 14:49:08 javax.jms.JMSException: TopicConnection[Oc4jJMS.Connection.bak
    desktop.e06940:f807230602:-8000.9]: cannot invoke method "setClientID" within th
    e J2EE container.
    03/10/04 14:49:08 at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1
    920)
    03/10/04 14:49:08 at com.evermind.server.jms.JMSUtils.toJMSException(JMSUt
    ils.java:2003)
    03/10/04 14:49:08 at com.evermind.server.jms.JMSUtils.toJMSException(JMSUt
    ils.java:1969)
    03/10/04 14:49:08 at com.evermind.server.jms.JMSUtils.assertNotContainer(J
    MSUtils.java:2427)
    03/10/04 14:49:08 at com.evermind.server.jms.EvermindConnection.setClientI
    Can anyone help? It is very sad because i experienced that most samples will not work if you only follow the install manual.
    regads,
    attila

    Hello Attila,
    It seems that you are using OC4J 10G to run the sample. The sample has been tested on OC4J 904 Developers preview. Please use this to run the sample application.
    This demo uses JMS 1.0 and OC4J 10G supports JMS 1.1. In JMS 1.1, you cannot call setClientID() directly within the J2EE container. Due to this inherent change in the spec, the Chat Demo does not work properly in OC4J 10G.
    This is a known problem and we are working on rectifying this.
    Thanks,
    Rajat

  • JMS Bridge not Working

    Hi,
    I have a weblogic 9.2 running one application.
    I what that application to post messages on a internal JMS queue. That message gets fw to a Weblogic 8 JMS queue.
    To achieve this I created a JMS Bridge with the Weblogic 8 destination, and the Weblogic 9 source.
    When i activate the bridge, i did not see anything on the logs, so i restarted the server.
    Once the server was Up I went to check how many consumers where register on my internal queue, and to my surprise there where none.
    I posted a message to that queue and still nothing. not even on the logs.
    On the source and destination, i put the following:
    Adapter JNDI Name: the XA one
    Classpath: weblogic.jar
    Connection URL: t3://172.16.76.28:8001 on the internal and t3://172.16.76.29:7001 on the external
    weblogic.jndi.WLInitialContextFactory: weblogic.jndi.WLInitialContextFactory
    and the JNDI stuff, user and password.
    I do not see anything in the logs. Any idea?

    I would like to make sure that I understand where you are now.
    1. The bridge is always running on 9.2.
    2. When the bridge is configured to forward messages from local (9.2) to remote (8.1), everything works.
    3. When the bridge is configured to forward messages from remote to local, you run into the SecurityException.
    Is my understanding correct? Where did you see the Exception (on the 9.2 side or the 8.1 side)?
    Are you always using the adapter from the same release as the server that is running the bridge?
    Assuming that you have configured everything correctly, I don't see why remote-to-local case does not work for you. There was an issue similar to what you are seeing in 8.1 GA, which has been fixed in 8.1SP1 and 9.2. You should not see this issue as long as your bridge is running on 9.2 (or 8.1SP1) or later.
    At this point you could try the following:
    1. Change the bridge to run in sync mode (by setting AsyncEnabled to false, the default is true) and see if the problem persists.
    2. Enable domain trust on both the 9.2 and 8.2 domains (see http://edocs.bea.com/wls/docs92/bridge/wls_interop.html#wp1126213 for details).
    3. Run the bridge on 8.1 (using the 8.1 adapter) to forward messages to 9.2. (I know the doc recommends that one should run the bridge on the later version of WebLogic when forwarding between two different releases, but it does not hurt to try as long as your source destination is on the same release are the bridge).
    Thanks,
    Dongbo

  • JMS messaging not working with LCDS and Fiorano

    Hi there,
    Been struggling at this all day with no luck. I have a finished Flex application which uses JMS messaging, and it has worked just fine on my Tomcat server while using ActiveMQ. As soon as I switched to using the JMS provider Fiorano however, my application can no longer use JMS resources. It fails whenever the application tries to subscribe or publish to a JMS topic. I made all the appropriate JMS related changes to messaging-config.xml.
    In the tomcat log, I turned on LCDS debugging and saw this error whenever a publisher or subscriber was trying to start:
    "JMS invocation caught exception: SECURITY_EXCEPTION :: Security exception occurred while trying to perform operation :: CreateSubscriber failed,creation of Non-durable Subscriber NOT allowed."
    I am passing my JMS security credentials via messaging-config.xml AND even tried doing it via the Flex application (setRemoteCredentials(..)). I know they are correct because I have a working Java application with the exact same credentials and other JMS settings working just fine. It seems only the Flex application fails using the same JMS credentials/settings.
    Is there some other file that needs modification other than messaging-config.xml to get a new JMS provider to work? Any idea what may be going on?
    Thanks!

    A large number of messages, or messages large in size, basically total size of all messages can hang things up.  Back up your messages with a GPStore app.  Erase them.  Lower your message character size.  IF it still continues, its the recipients phone.  Both of you should power down, remove SIM, reinsert, power up.

  • JMS UDD not working properly

    Hello
    First of all I new to weblogic world and started using it recently, the issue which we are facing is that we had a doc given by our client to create a weblogic JMS uniform distributed destination with queue. We followed it and everything came up properly. In our test env we have 2 Physical Machines on which each machine has a one node in a cluster and then we created JMS servers, connection factory with UDD. We started the nodes everything comes up properly.
    But the issue starts when we tested it for the load balancing which I believe is a feature of UDD is not working properly. All the messages are going to the same node. The same documentation has been used by our client several times and it works fine for them.
    What is the issue with our configuration? I have gone through the doc many times but cant find the issue.
    Please help us.

    Hi,
    I think there might be some issue with the communication between the 2 machines, check that out also check if you have disabled the Server Affinity Enabled
    Below links might help you in your issue.
    Topic: JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
    http://middlewaremagic.com/weblogic/?p=3759
    Topic: Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
    http://middlewaremagic.com/weblogic/?p=3747
    Hope this would help you.
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

  • JMS Dequeue not working after upgrade from 11gR1 to 11gR2

    Our database was migrated to a new database with new hardware running 11gR2
    enqueue appears to be working as the queue table just grows and grows
    However, my JMS async subscriber is never getting messaged.
    Is there any logical reason for this?
    in select * from all_queues my queue does show ENQUEUE and DEQUEUE enabled
    also
    the user that makes the subscription has DEQUEUE grant priviledge
    Is there anything else that is needed for this to work?
    I have already recreated the queue and queue table and ended up in the same place with no JMS consumer being able to consume.
    when enabling trace on JMS I see
    Caused by: oracle.jms.AQjmsException: JMS-122: Internal error Corrupted message
         at oracle.jms.AQjmsError.throwEx(AQjmsError.java:334)
         at oracle.jms.AQjmsUtil.getTextData(AQjmsUtil.java:718)
         at oracle.jms.AQjmsTextMessage.readGenMessageContainer(AQjmsTextMessage.java:322)
         at oracle.jms.AQjmsTextMessage.<init>(AQjmsTextMessage.java:172)
         at oracle.jms.AQjmsConsumer.dequeue(AQjmsConsumer.java:2481)
    What incompatibilities exist b/w 11gR1 and 11gR2 ... my client is using aqapi 11.1
    Edited by: steffi on Jan 14, 2013 3:14 PM

    It's looking like it was a missing jar in this case the orai18n.jar
    Is there any kind of release notes for how to move working AQ from 11gR1 to 11gR2?

  • WL8.1 jms client not working with WLS9.1

    Hi,
              I have a JMS client(MDB) with weblogic.jar(8.1 version) and its not able to pick messages from a queue which is created in WLS9.1.
              I have actually upgraded my weblogic domain using the wizard and i can see my queues getting created properly.
              At the client side when i use weblogic.jar(9.1 version) it works but not with weblogic81.jar..
              Any help is greatly appreciated.
              Thanks.

    This should work as far as I know, you might want to try contacting customer support. For now, it might help to try using 8.1 with the latest service-pack.
              Tom

  • JMS Throttling not working on WLS 10?

    Hi,
    I've been trying to get throttling working for some time, and it just doesn't appear to work as I'd expect (or indeed at all)
    Has anyone seen it working?
    I'd like to restrict the flow of messages into my queue to 5 messages / sec, but messages are just flying through the system as quickly as I can send them.
    Each message is generating the following log entries though:
    <04-Aug-2009 17:11:09 o'clock BST> <Alert> <JMS> <BEA-040024> <JMSServer "wlsbJMSServer" byte threshold for destination jmsResources!test-throttlingResponse has been exceeded.>
    <04-Aug-2009 17:11:09 o'clock BST> <Alert> <JMS> <BEA-040025> <JMSServer "wlsbJMSServer" byte threshold condition for destination jmsResources!test-throttlingResponse has cleared.>
    I've followed the following steps:
    (Single Server environment)
    JMS Server
    * Messages threshold high: 2
    * Messages threshold low: 1
    Connection Factory
    * set flow maximum to be 5 messages / sec
    * set flow minimum to be 1 messge / sec
    * Flow interval: 3600
    * Flow steps: 5
    * Flow Control Enabled: On
    Queue
    * Bytes threshold high: 1
    * Bytes threshold low: 0
    * Messages threshold high: 1
    * Messages threshold low: 0
    Quota:
    Messages Maximum: 1
    Policy: FIFO
    Shared: false
    Any ideas?
    Cheers
    Peet

    Thanks for your input on this.
    It's definitely moved me on a bit further.
    When I remove the messageListener, the queue accepts a single message, and then the Quota kicks in and doesn't allow any further messages to be published. The producer blocks for the ConnectionFactory "Send Timeout" (30 seconds) and then throws an exception:
    weblogic.jms.common.ResourceAllocationException: weblogic.messaging.kernel.QuotaException: Quota blocking time exceeded and no quota available
    It seems that this is due to the Quota that I had applied to the queue. This rejects the addition of any messages in excess of the quota, but doesn't trigger the ConnectionFactory throtting.
    Disabling the Quota allows the messages to flow again as quickly as I can produce them.
    So can we say then: Quotas are not required to acheive ConnectionFactory Throttling?
    Once the quota is removed, all of the messages flow freely through the queue, and we get a single instance of these messages:
    <05-Aug-2009 14:59:50 o'clock BST> <Alert> <JMS> <BEA-040024> <JMSServer "wlsbJM
    SServer" byte threshold for destination jmsResources!test-throttlingResponse has been exceeded.>
    <05-Aug-2009 14:59:50 o'clock BST> <Alert> <JMS> <BEA-040026> <JMSServer "wlsbJM
    SServer" message threshold for destination jmsResources!test-throttlingResponsehas been exceeded.>
    <05-Aug-2009 14:59:50 o'clock BST> <Alert> <JMS> <BEA-040030> <JMSServer "wlsbJMSServer" message threshold for the server has been exceeded.>
    Nothing else happens until we turn on the receivers again and then we get these messages alternating again:
    <05-Aug-2009 14:58:52 o'clock BST> <Alert> <JMS> <BEA-040024> <JMSServer "wlsbJM
    SServer" byte threshold for destination jmsResources!test-throttlingResponse has been exceeded.>
    <05-Aug-2009 14:58:52 o'clock BST> <Alert> <JMS> <BEA-040025> <JMSServer "wlsbJM
    SServer" byte threshold condition for destination jmsResources!test-throttlingResponse has cleared.>
    So, it appears that although we're exceeding the message and byte thresholds, the ConnectionFactory throttling is not kicking in
    Could this be a bug?

  • JMS config not working with OSB

    I have been trying the JMS through out the day and I believe that this is currently becoming a show-stopper.This is because, the jms configuration is not properly done.
    In case you happen to find time, please ask this question to Oracle:
    Steps:
    1. Created JMS Module -->ERAM JMS Module
    2. Created a Queue->ERAMInQueue with jndi name-jms/EramIn
    3.Used the default connection factory-weblogic.jms.XAConnectionFactory
    4.In OSB
    1. Created a separate BS with TP as JMS
    2. gave the endpoint uri as :jms://localhost:7001/weblogic.jms.XAConnectionFactory/jms/EramIn
    3. Deployed the configuration
    5.Receiving the error in the error log
    <Jun 18, 2009 8:11:01 PM IST> <Error> <JCATransport> <BEA-381951> <JCA inbound r
    equest only invocation failed, exception: java.security.PrivilegedActionExceptio
    n: com.bea.wli.sb.transports.TransportException: Unable to resolve 'jms'. Resolv
    ed ''
    java.security.PrivilegedActionException: com.bea.wli.sb.transports.TransportExce
    ption: Unable to resolve 'jms'. Resolved ''
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:373)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.security.Security.runAs(Security.java:61)
    at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener.sendM
    essage(JCAInboundRequestListener.java:156)
    at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener.post(
    JCAInboundRequestListener.java:71)
    Truncated. see log file for complete stacktrace
    com.bea.wli.sb.transports.TransportException: Unable to resolve 'jms'. Resolved
    at com.bea.wli.sb.transports.TransportException.newInstance(TransportExc
    eption.java:195)
    at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(Transpo
    rtManagerImpl.java:386)
    at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener$1.run
    (JCAInboundRequestListener.java:158)
    at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener$1.run
    (JCAInboundRequestListener.java:156)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    Truncated. see log file for complete stacktrace
    com.bea.wli.sb.context.BindingLayerException: Unable to resolve 'jms'. Resolved
    at com.bea.wli.sb.context.ContextUtils.createBindingLayerException(Conte
    xtUtils.java:924)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContex
    tImpl.java:595)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextI
    mpl.java:498)
    at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeSt
    ep.java:128)
    at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(Debu
    ggerRuntimeStep.java:74)
    Truncated. see log file for complete stacktrace
    com.bea.wli.sb.transports.TransportException: Unable to resolve 'jms'. Resolved
    at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutbo
    undMessageContext.java:537)
    at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(J
    msTransportProvider.java:680)
    at sun.reflect.GeneratedMethodAccessor334.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    Truncated. see log file for complete stacktrace
    javax.naming.NameNotFoundException: Unable to resolve 'jms'. Resolved ''; remain
    ing name 'jms'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(Basic
    NamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.jav
    a:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.j
    ava:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:20
    6)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.j
    ava:254)
    Truncated. see log file for complete stacktrace
    >
    Any pointers helpful
    RS

    This not the proper forum for OSB, please use the SOA Suite forum.
    SOA Suite
    Also, I see you are referencing the JMS JCA Adapter, so you might be using OSB 10.3.1 release? Are you sure that you want to use the JCA transport for JMS when OSB supports JMS with a native OSB transport?

  • JMS MQ not working on BINDINGS mode

    I'm trying to improve the performance by using BINDINGS(JMSC.MQJMS_TP_BINDINGS_MQ) on a SUSE linux with MQ 5.3 and Weblogic 7.0 sp2. The same setting on Windows 2000 is working fine and works fine for CLIENT(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) mode on both the platforms. We are not using transaction and the calls to the MQ are made from a Java class (i.e., the connection, session etc are created in this class). The error has MQ code 2102.
              Will appreciate any suggestions/help.
              Thanks,
              Sanjeev Chakravarty

    I'm trying to improve the performance by using BINDINGS(JMSC.MQJMS_TP_BINDINGS_MQ) on a SUSE linux with MQ 5.3 and Weblogic 7.0 sp2. The same setting on Windows 2000 is working fine and works fine for CLIENT(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) mode on both the platforms. We are not using transaction and the calls to the MQ are made from a Java class (i.e., the connection, session etc are created in this class). The error has MQ code 2102.
              Will appreciate any suggestions/help.
              Thanks,
              Sanjeev Chakravarty

  • Sender JMS Adapter - NOT Working

    Hello Everybody - We are on SP13, also installed JMS Driver files on the system. We are running, Central Adapter Engine.
    We configured the Sender JMS Adapter for WBI MQ->XI->SAP scenario. We need to JMS Adapter to be configured to connect to WBI from XI. Everything looks great in configuration but in the Adpater Monitoring, JMS Adapter is with Error Status and Message says "Sender channel. Details: (No detail information set.)".
    Does anybody has any idea about this error ?
    I checked SAP Help link as well on this. Based on this link http://help.sap.com/saphelp_nw04/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm. Do we need to configure this JMS Adapter somewhere on teh server as well ? If yes, then where ? Pls respond if you have any clue about it.
    Thanks in anticipation...

    Hello Stefan - Thanks for response.
    Here are the Parameters.......
    Adapter Type: JMS
    Sender Type Clicked
    Transport protocol:WebSphereMQ (non-JMS)
    Message protocol:JMS 1.x
    Adapter Engine:Integration Server
    Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
    Queue Java Class:com.ibm.mq.jms.MQQueue
    IP Address or Server Name:10.9.48.154
    Server Port:1414
    Queue Manager Name:WBIDEV
    Channel Name:WBI.XI.SVRCONN
    JMS Queue:XI_REQUEST
    Transport/Network Protocol:TCP/IP
    JMS-Compliant:JMS-Compliant
    Transactional JMS Session:Check box Set
    JMS Queue User:XIUSER
    JMS Queue Password:********
    Set XI message ID(MessageID) to:GUID(recommended value)
    Set XI cenversation ID(conversationID) to:No value
    Mapping of Message:Message Payload=JMS Payload
    Quality of Service:Exactly Once
    Time Period for duplicate check for EO(IO)(secs):86400
    Wait After Message Error(msecs):1000
    Wait before Reconnect(msecs):1000
    Status:Active
    The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
    Pls advice If I am missing anything ?
    Thanks....
    Amrish.

  • Sender JMS Connectivity not working

    Hi All,
    We have developed a scenario where we have to pick messages from DTS JMS queue and we are using JMS provider with JNDI as the sender transport protocol. We have deployed the jar files given by the DTS team successfully in our XI 3.0 system and we have configured the sender JMS channel. Since this queue is in another NWDS sever, we have also set Additional JMS parameters: JNDI.InitialContext.property.5=java.lang.String force_remote, java.lang.String true.
    But when we are testing, I am getting the below error in Adapter monitoring :
    Sender channel. Details: com/sap/jms/client/connection/RemoteConnectionFactoryInterface (Unsupported major.minor version 49.0)
    Please let me know if I have missed any parameters or any suggestions to solve the issue.
    Thanks,
    Laawanya

    Hello Stefan - Thanks for response.
    Here are the Parameters.......
    Adapter Type: JMS
    Sender Type Clicked
    Transport protocol:WebSphereMQ (non-JMS)
    Message protocol:JMS 1.x
    Adapter Engine:Integration Server
    Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
    Queue Java Class:com.ibm.mq.jms.MQQueue
    IP Address or Server Name:10.9.48.154
    Server Port:1414
    Queue Manager Name:WBIDEV
    Channel Name:WBI.XI.SVRCONN
    JMS Queue:XI_REQUEST
    Transport/Network Protocol:TCP/IP
    JMS-Compliant:JMS-Compliant
    Transactional JMS Session:Check box Set
    JMS Queue User:XIUSER
    JMS Queue Password:********
    Set XI message ID(MessageID) to:GUID(recommended value)
    Set XI cenversation ID(conversationID) to:No value
    Mapping of Message:Message Payload=JMS Payload
    Quality of Service:Exactly Once
    Time Period for duplicate check for EO(IO)(secs):86400
    Wait After Message Error(msecs):1000
    Wait before Reconnect(msecs):1000
    Status:Active
    The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
    Pls advice If I am missing anything ?
    Thanks....
    Amrish.

  • WLS JMS bridge not working

    Hi All,
    I have been looking for a solution for the last two days and this is my third post regarding JMS bridge. I configured ome JMS bridge which initially ,on the monitoring tab, was giving information "Failed to look uo the source adapter" then I deployed the resource adapter. Now on the monitoring tab its showing the message "Connected to the source" instead of shoing "Forwarding Messages" . can anyone tell me what could be thw cause. Please help its really urgetnt!!!

    Can anybody please help me?

  • JMS-send operation not working in a SessionBean [OC4J10.1.3.1.0-standalone]

    Salut,
    i am envisaged with a nasty problem calling a message-send operation from
    a method (transaction-type="required") inside a session bean (transaction-type="container").
    This problem occured in OC4J 10.1.3.1 and may fail also in 10.1.3.0. The same
    code run under OC4J 10.1.2.x without any problems.
    The adressed JMS type is a OEMS JMS and fails to work regardless if the JMS ressource
    is using a file-persistence or is running in-memory. Anyway the factory is a
    jms/XAQueueConnectionFactory, so the created queue must support XA transactions.
    Another test with an advanced-queue JMS provider succeeded.
    As a consequence of this, i believe that the OEMS provider shall cause the problem.
    The original code is quite unspectaculary:
    * The non-surprising thing is, that the QueueConnectionFactory
    * is a XAQueueConnectionFactory.
    QueueConnectionFactory qcf = (QueueConnectionFactory) (jndiContext.lookup(MY_QFAC));
    Queue q = (Queue) (new InitialContext().lookup(MY_QUE));
    c = qcf.createQueueConnection() ;
    QueueSession s = c.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    [... create a message ]
    QueueSender qs = s.createSender(q)
    qs.send(m);
    qs.close()
    s.close();
    c.close()
    The funny thing is, that the queue-session behaves as it is working outside
    of a transaction context. Inside the JMX-Console you will notice the
    arrival of a message and ... a cancellation of it. This would not surprise
    me, if this code sequence would have been called outside of
    a Session bean, cause the absence of a queue-session.commit does not
    fix the send message in the jms ressource.
    As a matter of fact the code is executed inside a Session bean and
    the connection.createQueueSession will notice this and forget both
    given parameters, and let the covering transaction take over of the
    JMS ressource. But this does not happen (completly).
    The acknowledge-mode has been modified (SESSION_TRANSACTED)
    but the code still does not work!
    After i recognized that the enlist-ment did not work, i
    decided to enfore the use of XA transaction by using the
    XA classes and methods of JMS.
    I startet to cast the jndi-references and:
    XAQueueConnectionFactory qcf = (XAQueueConnectionFactory) (jndiContext.lookup(MY_QFAC));
    Queue q = (Queue) (new InitialContext().lookup(MY_QUE));
    XAQueueConnection c = qcf.createXAQueueConnection() ;
    XAQueueSession s = c.createXAQueueSession();
    [... create a message ]
    QueueSender qs = s.createSender(q)
    qs.send(m);
    qs.close()
    s.close();
    c.close()
    The funny thing is ... the code worked without any problem until
    the send operation, where i received an JMSException, containing
    the text:
    Oc4jJMS.Session.hpcl057.4e9c06e4:1112674930d:-7fff.41,true,SESSION_TRANSACTED]: An attempt was made to perform work in a XA-backed session without being enlisted. Either the session must be enlisted (using the JMS Connector or JMS Adapter) to participate in the global transaction, or a non-XA connection and a non-XA session should be used to not participate in the global transaction.
    How bizarre, i thought the enlistment has been taken place by invoking
    the c.createXAQueueSession or c.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    How bizarre how bizarre
    any clues ????

    OC4J JMS was changed to not auto-enlist in XA transactions.
    In releases prior to 10.1.3 XA usage was not actually supported. (It did not meet all of the XA requirements when used with OC4J.)
    Auto-enlisting by the JMS provider was also a spec violation, which was causing trouble for people who needed to do out-of-transaction work and had no way to do it.
    In 10.1.3 XA usage is fully supported, but only when you use the JMS Connector. You can find the JMS Connector ("Oracle's Generic JMS Resource Adapter") demos here:
    http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/index.html#JMS
    The JMS Connector is documented in the OC4J Services Guide, OEMS/JMS chapter.
    -Jeff

Maybe you are looking for

  • Error while running the concurrent program

    Hi All, We ran a concurrent program to create XML report which completed in warning. we got the following message in the log file. [091907_050229025][][EXCEPTION] java.io.IOException: Bad file descriptor      at java.io.FileOutputStream.writeBytes(Na

  • BI EE Presentation Services Connections error

    After I try to create a BISoapConnection in EM,and when saving this connection,i got errors says "javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: These mbeans encountered exceptions and may not have been saved biserver

  • Error or termination in target client

    Hi All, We are able to move Transport Request from Development BW Client  to Quality BW Client smoothly. But when we move the same TR to Production client, we are getting the following error log. I would be very grateful if somebody could throw light

  • What is the role of java in the netweaver platform

    Hi All sapnetweaver platform is the integration of the java and abap.then what is the role of java in that netweaver platform regards Sunil

  • Syncing shared calendar

    I used to have an iphone 3G and could easily sync my 2010 outlook calendar along with a shared calendar that I would periodically email to my home account from work.  Now I have switched to an iphone 4S with an updated os and it no longer syncs my sh