Configuring MDB to receive message from MQSeries Queues bound on WL JNDI

Hi,
I am using weblogic7.0 sp2. I need to configure my MDB to receive message from MQ Series (on a different server). The queue is bound to WL JNDI using a server startup program.
Anyone with experiece, please help.
Thanks,
Fasih

I'd start here:
http://e-docs.bea.com/wls/docs70/faq/index.html
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Similar Messages

DefaultMessageListenerContainer Does receive message from remote Queue

I am developing an application where I need to consume JMS messages from JMS Queue on remote weblogic server 10.3.3.0. My application is deployed WLS 10.3.2.0 and I using Spring 2.5.6. In my spring configuration, I have used Springframework's DefaultMessageListenerContainer to listen to the Queue on remote server.
Now I have two scenarios in which DMLC does not consumer messages without server restart.
Scenario 1: When the Remote server on which the JMS queue resides is restarted. DMLC stops consuming message from the Queue on remote server. After I restart my server, it starts consuming messages. But I want that DMLC starts consuming messages without the restarting server at my end.
Scenario 2: When the remote server is running and I update/Redploy my application on WLS at my end. In this case also, DMLC stops receiving messages and I have to restart server at my end.
Could anyone please help sorting out this issue?

This seems like a Spring question, you might want to ty the Spring forums. I'm not sure why you would get the behaviour you see.

Can 1 MDB configured to receive messages from 2 Queues

Hi,
Is is possible to configure 1 MDB to listen to 2 queues

Deploying the very same MDB twice is not a "trick" or unusual as your comment suggests. A MDB is a stateless component. It just receives messages. If you deploy the same MDB twice and link it to different queues, it is exactly as if one MDB where configured to receive from 2 queues.
So everything is possible with MDBs. You can consume from multiple destinations and can even mix queues and topics. The only thing you must keep in mind is that you have at least that many MDB instances (of the same MDB) as destinations (= MDB deployments). However, for scalability reasons you would have multiple MDB instances in most cases.
I don't see a reason why sombody should switch to a proprietary thing like your MDS and I don't understand why you mention this in nearly every post. Buy banner ads instead.
-- Andreas

OC4J 9.0.4: Problem receiving message from JMS queue

I've created an application which puts XML files in a JMS queue and try to get it out again. The enqueing (sending) is no problem, but when I dequeue from the same queue I receive nothing and if I don't specify a wait time the programs hangs.
If I create a QueueBrowser I can see there are messages in the queue.
Can someone tell me what I do wrong?
Here is the code of my dequeue action:
public String dequeue(int qName) throws RbsSysException
        final String method = "dequeue(int qName)";
        _log.debug(method);
        QueueConnection queueConnection = null;
        try
            queueConnection = _queueConnectionFactory.createQueueConnection();
            QueueSession queueSession = queueConnection.createQueueSession(false,
                    Session.AUTO_ACKNOWLEDGE);
            QueueReceiver queueRcv = queueSession.createReceiver(getQueue(qName));
            _log.debug("queue = "+ queueRcv.getQueue().getQueueName());
            // Due to bug 3376983 in OC4J We cannot use TextMessage if it exceeds
            // 64 kb. Therefore use ObjectMessage.
            Message msg = queueRcv.receiveNoWait();
            _log.debug("msg = " + msg);
            ObjectMessage objMsg = (ObjectMessage)msg;
            //ObjectMessage objMsg = (ObjectMessage) queueRcv.receiveNoWait();
            _log.debug("objMsg = " + objMsg);
            if (objMsg != null)
                return (String) objMsg.getObject();
            else
                return null;
        catch (JMSException je)
            throw new RbsSysException(je);
        finally
            if (queueConnection != null)
                try
                    queueConnection.close();
                catch (Exception any)
                    _log.error("Error while closing QueueConnection: ", any);
    }

Did you implement javax.jms.MessageListener and the method onMessage(Message)?
If you use onMessage() as wel as receive (or receiveNoWait() or receive(long)), the onMessage() can be called, while the main thread is blocking on a synchronous receive, so make sure you use only one of the two methods: onMessage() or receive.
Receive() blocks your thread until a message is published. So your program 'hangs' by design. Usually this is used when your program is waiting for a particular message. Otherwise use onMessage().
ReceiveNoWait() checks if something is in the queue at that very moment, so if nothing is there (yet), the main thread continues.
Hope this helps,
Lonneke

Recieve/Read Messages from JMS Queue through ALSB

Hi,
I have configured JMS Queue in weblogic server.
I have created Messaging Service in ALSB which sends messages in MESSAGE QUEUE.
Now Is it possinle to receive messages from JMS Queue by creating business service in Aqualogic Service bus???

Hi dear,
 
I am sending Message through Serializable Object.
 
I have JMS Proxy which gets invoked when i send message to JMs Queue. JMS Proxy then calls business service.
 
 
Business Service has two functions. One is taking String as input and one is taking Serializable Object as Input.
 
 
public void recieveString(String str) 
public void recieveObject(Trade obj) 
-------------------------------------------------- 
Now I have configured Proxy Services' Request and Response
Message Type as a "TEXT". and I am sending ObjectMessage here so what kind of change I require.
 
I also want to configure my proxy so that if JMS queue recieves TextMessage then it should invoke reciveString() function and if Object Message then vice versa.....
 
But i am not able to handle object even...
When I am sending Object Message it takes as a TextMessage.
I am getting following exception when I am sending Object Message to JMS QUEUE. Request and Response Message types are XML Schema of that object.
 
 
<Nov 30, 2006 4:57:19 PM IST> <Warning> <EJB> <BEA-010065>
 
<MessageDrivenBean threw an Exception in onMessage(). The exception was: java.lang.AssertionError. 
java.lang.AssertionError at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.j
ava:112)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:42
9)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDL
istener.java:335)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:
291)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
Truncated. see log file for complete stacktrace
>
Message was edited by:
alwaysvaghu

Receiving messages from Service Bus Topics in node js without polling

Hi, I have node js client who subscribed to a Topic, currently I'm using a timer to invoke receiveSubscriptionMessage every few seconds to get messages from the Topic.
Is there a way to do this without polling?
Thanks.

You can implement message pump by OnMessage which will do the poll for you. Please read "How to receive messages from a queue" part from
http://azure.microsoft.com/en-us/documentation/articles/service-bus-dotnet-how-to-use-queues/

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

How can a JMS adapter be configured in BPEL to consume messages from multiple queues ?

If you want to use JMS with AQ as datastore then there is some configuration you need to do to enable this. This is outside SOA Suite per sa, e.g. no adapter required.
If you want to connect to the AQ direct then use the AQ adapter.
this blog may be of some help understand the configuration
http://biemond.blogspot.com/2008/01/oracle-jms-with-esb-and-bpel.html
cheers
James

How can I send and receive a message from a queue using standalone program

Hi,
I want to write a standalone Java program which has to post a message to a queue and receive a message from a queue thats specified as a replyto queue.I want to have my application to be completely standalone without the need of a Application server.What all the Jars do I need to include in the application.My aim is to have the application standalone and portable so that the application runs on any machine that has a JRE.
Thanks in advance,
Prathima

Hi,
You can get quite simple standalone MQ Java programs from this site http://www.capitalware.biz/mq_code_java.html.
Also regarding the jars required for your application depends on the API being used. If you use MQI API few jars are required and if you decide to use JMS API you'll require few other jars. But you got to either install Websphere MQ Java Client, which will copy the jars to the respective location, or you can choose to copy the jars from some other machine manually.
Eventually, all the jars related to MQI and JMS API will reside under /usr/mqm/java/lib/ or /var/mqm/java/lib/ UNIX Environment. And in case of WINTEL, you should find the jars under C:\Program Files\IBM\WebSphere MQ\Java\lib.
Trust it clarifies...
Naren

How to receive message from queue based on JMSPriority

Hi all,
I want to receive message from Receive Message From Queue based on JMSPrirority.
I am able to send message to queue using Send Message To Queue component with specifying Priority value as Five(Liternal value).
Now, when I am trying to receive message from Queue by specifying JMSPriority='Five'; in Message selector, it is not working.
But, when I use JMSPriority is not null in Message selector, I am able to receive message.
How to receive message from queue by specifying exact value of JMSPriority.
Please suggest.

Hi WASIL,
I tried with captial FIVE and it is not working.
I tried also like operator and the standard example doesn't recieve messages based on priority.
I am experiecing below error:
Caused by: javax.jms.InvalidSelectorException: The selector is invalid: JMSPriority LIKE '%FIVE%';
 at com.adobe.livecycle.jms.QueueMessageReceiver.receiveMessageFromQueueWithPropertiesNoWait( QueueMessageReceiver.java:206)
 at com.adobe.livecycle.jms.JMSService.receiveMessageFromQueue(JMSService.java:413)
 at sun.reflect.GeneratedMethodAccessor1017.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
 ... 135 more
Caused by: javax.jms.InvalidSelectorException: The selector is invalid: JMSPriority LIKE '%FIVE%';
 at org.jboss.jms.server.selector.Selector.<init>(Selector.java:107)
 at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegateInternal(Server SessionEndpoint.java:2103)
 at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionE ndpoint.java:277)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advise d$SessionAdvised$createConsumerDelegate$aop(SessionAdvised.java:94)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985 689973.invokeTarget(SessionAdvised$createConsumerDelegate_8721389917985689973.java)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
 at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect .java:124)
 at sun.reflect.GeneratedMethodAccessor389.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
 at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
 at org.jboss.jms.server.endpoint.advised.SessionAdvised.createConsumerDelegate(SessionAdvise d.java)
 at org.jboss.jms.wireformat.SessionCreateConsumerDelegateRequest.serverInvoke(SessionCreateC onsumerDelegateRequest.java:100)
 at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandle r.java:165)
 at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:967)
 at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791 )
 at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744)
 at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:586)
 at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)
 at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:216)
 at org.jboss.remoting.Client.invoke(Client.java:2034)
 at org.jboss.remoting.Client.invoke(Client.java:877)
 at org.jboss.remoting.Client.invoke(Client.java:865)
 at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
 at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
 at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientS essionDelegate$createConsumerDelegate$aop(ClientSessionDelegate.java:267)
 at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_87213899179856 89973.invokeTarget(ClientSessionDelegate$createConsumerDelegate_8721389917985689973.java)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
 at org.jboss.jms.client.container.StateCreationAspect.handleCreateConsumerDelegate(StateCrea tionAspect.java:136)
 at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateCon sumerDelegate_930384804.invoke(StateCreationAspect_z_handleCreateConsumerDelegate_93038480 4.java)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
 at org.jboss.jms.client.container.ConsumerAspect.handleCreateConsumerDelegate(ConsumerAspect .java:76)
 at org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect_z_handleCreateConsumer Delegate_930384804.invoke(ConsumerAspect_z_handleCreateConsumerDelegate_930384804.java)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
 at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.j ava:92)
 at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
 at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:172)
 at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
 at org.jboss.jms.client.delegate.ClientSessionDelegate.createConsumerDelegate(ClientSessionD elegate.java)
 at org.jboss.jms.client.JBossSession.createConsumer(JBossSession.java:237)
 at org.jboss.jms.client.JBossSession.createConsumer(JBossSession.java:220)
 at org.jboss.jms.client.JBossSession.createReceiver(JBossSession.java:396)
 at com.adobe.livecycle.jms.QueueMessageReceiver.receiveMessageFromQueueWithPropertiesNoWait( QueueMessageReceiver.java:198)
 ... 140 more
Please suggest

Can' t consume JMS messages from remote queue

Hello.
We are using Tibco JMS Server as Foreign JMS server from WL server. And WebLoigic (8.1 SP 3) MDBs are receivers. Everything works fine until there is a restart of the Tibco server. Once the queues become unavailabe, we see in the WL log that the destination is unreachable. And also once the Tibco server comes back up, WL log says that the Foreign queues have been re-connected. But still, we don't see any messages being received by the MDB. The MDBs are configured to poll for messages evey 1 second. Still we don't see it happening after the foreign server restart.
But if we re-start the WL server, it begins to work just fine.
Any pointers?
Thanks

I do have the correct IP address of the syslog server set up. I do not want email logs so have not enabled that.
My setup is
remote lan > SA520-remote (192.168.160.1) > [ site to site IPSec VPN over WAN ] > SA520-local (192.168.150.1) > syslog server (192.168.150.25) & local lan
Firewall is set up to allow ANY IN & OUT to local lan on both routers.
I have also set up specific rules for UDP 514 Syslog traffic (no difference, currently disabled)
syslog server has -no- firewall at the moment.
Syslog server is receiving messages from the local router with no issues.
Log Severity is set to Information & Log Facility is set up to send to Syslog.
I have also setup a SNMP trap on the syslog server & pointed the remote router to it in hopes of diagnosing the issue.
Both routers have the latest firmware applied.
Using wireshark on the syslog server I see no traffic on UDP 514 (syslog) or UDP 162 (snmp)
I can use the WUI for the remote & ping the 160.1 with no problem. Both ping & TLS/TCP traffic show up in wireshark on the syslog server when I do so.
It looks to me like there is a problem routing the syslog messages out of the router & then back through the VPN.
Worst case I'll set up another syslog server on an old machine at the remote location & then cron the logs to the central syslog server but it really seems I shouldn't have to.

Weblogic 10.3 Not Removing Expired Messages from JMS Queues

Dear All,
We have an application that is running on Weblogic 10.3.
This application (let us call this application Y) receives messages on a JMS queue. These messages are placed on the queue by another application (let us call this application X). We would like to have these messages expire within a certain amount of time (i.e. 90000 ms) if they are not consumed.
Now when application X places the messages onto the queue for application Y to consume, the JMS producer sets the time to live to 90000 ms. We can see that expiration time has been set appropriately in the weblogic console. If a message sits on the queue for longer than 90000 ms the state string of the message is changed to "receive expired". What we don't understand is why the expired messages still end up being consumed from the queue.
We understand that Weblogic is supposed to have an 'Active Message Expiration' thread that will remove expired messages from the queue. The Expiration Scan Interval for the JMS Server is set to 30 (seconds).
Can anyone tell us why our expired messages don't seem to be deleted from the queues?
Tim

Thank you for the response Rene.
We have set up both the active expiration scan and the message expiration policy. The active expiration scan is set for every 30 seconds. The message expiration policy is set to "discard". However, the expired messages are still being consumed. Is it possible we are doing something wrong? See a portion of our configuration files below.
We have set up the expiration scan time interval. See a portion of our config.xml below:
<jms-server>
<name>brokerJMSServer</name>
<target>AdminServer</target>
<persistent-store xsi:nil="true"></persistent-store>
<store-enabled>true</store-enabled>
<allows-persistent-downgrade>false</allows-persistent-downgrade>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
*<expiration-scan-interval>30</expiration-scan-interval>*
<production-paused-at-startup>false</production-paused-at-startup>
<insertion-paused-at-startup>false</insertion-paused-at-startup>
<consumption-paused-at-startup>false</consumption-paused-at-startup>
</jms-server>
<jms-system-resource>
<name>broker-jms</name>
<target>AdminServer</target>
<sub-deployment>
<name>EhrBrokerRequestQueue</name>
<target>brokerJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/broker-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
We have set up the message expiration policy in our jms descriptor. See a portion below:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<queue name="EhrBrokerRequestQueue">
<delivery-params-overrides>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>-1</redelivery-limit>
*<expiration-policy>Discard</expiration-policy>*
</delivery-failure-params>
<jndi-name>EhrBrokerRequestQueue</jndi-name>
</queue>
</weblogic-jms>
What could we be doing wrong?
Kind Regards,
Tim

BizTalk 2013 SB-Messaging Adapter: Unable to receive messages from a Azure service bus Subscription

Hi,
I am trying to receive messages from a Azure service bus subscription using SB-Messaging Adapter in BizTalk Server 2013 but getting the following error.
"The token provider was unable to provide a security token while accessing 'https://overcasb-sb.accesscontrol.windows.net/WRAPv0.9/'.
Error Code: 407 Proxy Authentication Required. The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. (12209)
It seems the error is related with Service Bus Authentication and Authorization with the Access Control Service. Can anybody help me out if I am missing something here?
Also for consuming the AWSB (namespace, topic name, subscription name, Issuer name, Issuer Key) I have referred the following link
http://soa-thoughts.blogspot.in/2013/02/biztalk-server-2013-new-adapters-series.html
Thanks!
Regards,
Gautam
gautam

Hi,
When I am trying to receive the same messages from a Azure service bus subscription using .net (C#) client,
BusSubscriberbusSubscriber =
newBusSubscriber("TestTopic2",
"Endpoint=sb://overcasb.servicebus.windows.net/;SharedSecretIssuer=owner;SharedSecretValue=wqYlT4yHZimeUZacH+1V1hj/ZrKu7zK9ELaaLYDxqjc=",
"AssetMovement",
"AssetMovement");
I am getting the same error here also.
"The token provider was unable to provide a security token while accessing 'https://overcasb-sb.accesscontrol.windows.net/WRAPv0.9/'.
Error Code: 407 Proxy Authentication Required. The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. (12209)
By setting <defaultProxy useDefaultCredentials="true" /> in appconfig, I got rid of the above error. And now its working fine with .net(C#) client.
<configuration>
<system.net>
<defaultProxy useDefaultCredentials="true" />
</system.net>
</configuration>
The same setting I tried in BTSNTSvc.exe config file and ofcourse restarted the host instance but still getting the same error. Any help?
gautam

MQ Adapter does not clear the rejected message from the queue

Hi All,
I'm using a MQ Adapter to fetch the message from the queue without any Backout queue configured. However, whenever there is any bad structured message found in the queue, MQ adapter rejects the message and moves the message to the rejmsg folder but does not clear it off the queue, as a result of which it keeps retrying the same hence, filling the logs and the physical memory. Somehow we do not have any backout queue configured so I can move the message to blackout queue. I have tried configuring the jca retry properties and global jca retry as well but to no avail.
- Is it not the default behaviour of MQ Adapter to remove the rejected message from the queue irrespective of Backout queue is configured or not? The same behaviour working well with the JMS and File Adapter though.
- Is there any way I can make MQ Adapter delete the message from that queue once it is rejected?
Regards,
Neeraj Sehgal

Hi Jayson,
Check this URL which answers a problem with com.sap.engine.boot.loader.ResourceMultiParentClassLoader problem:
http://209.85.175.132/search?q=cache:RnFZ9viwuKkJ:https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.sdn.folder.sdn!2fcom.sap.sdn.folder.application!2fcom.sap.sdn.folder.roles!2fcom.sap.sdn.folder.navigationroles!2fcom.sap.sdn.role.anonymous!2fcom.sap.sdn.tln.workset.forums!2fforumtest!2fcom.sap.sdn.app.iview.forumthread%3FQuickLink%3Dthread%26tstart%3D45%26threadID%3D1020700+com.sap.engine.boot.loader.ResourceMultiParentClassLoader&hl=en&ct=clnk&cd=3&gl=in&client=firefox-a
Please check that the JDK compliance level is at 5.0
Window->Preferences->Java->Compiler->Compiler compliance level set this to 5.0
Set the installed JRE to the one you have mentioned JDK 5.0 update 16
Window->Preferences->Java->Installed JRE's->
Click on the add button to select the path of your JDK.
once completed click on the check box next to it.
regards,
AKD

Dequeue with OCCI does not remove the message from the queue

Hey there,
I have this problem where no matter what dequeue option I try the messages never seem to be removed from the queue... I tried looking around and found only a similar un-answered question...
Thanks in advance...
void TryAnydataDequeue(oracle::occi::Connection * conn)
 try
 std::cout << "Dequeue Commence..." << std::endl;
 Consumer cons(conn);
 //Settings de dequeue
 cons.setCorrelationId("SPPC");
 cons.setQueueName("Anydata_queue");
 cons.setConsumerName("SNOOP");
 cons.setDequeueMode(cons.DEQ_REMOVE);
 //cons.setDequeueMode(cons.DEQ_LOCKED);
 std::cout << "Reception du message..." << std::endl;
 Message m2 = cons.receive(Message::ANYDATA);
 AnyData any(conn);
 any = m2.getAnyData();
 if(!any.isNull())
 oracle::occi::TypeCode type = any.getType();
 if(type == OCCI_TYPECODE_VARCHAR2)
 std::string msg = any.getAsString();
 std::cout << "Message Reçu: ";
 std::cout << msg << std::endl;
 else
 std::cout << "Format du message invalide..." << std::endl;
 std::cout << "Fin du message... (Press a key)" << std::endl;
 else
 std::cout << "Message invalide..." << std::endl;
 System::String * theInput = System::Console::ReadLine();
 catch(SQLException ex)
 std::cout << "Exception: " << ex.getErrorCode() << " - " << ex.getMessage() << std::endl;
 System::String * tnput = System::Console::ReadLine();
}

The message from the queue will be removed when you do a commit after a successful dequeue call, depending upon your message retention settings.
After you have done this processing and successfully performed a commit, what is the output of the following query:
SQL> connect AQADMIN/password
SQL> select msg_state from aq$<your_queue_table_name_goes_here> ;?
If it is PROCESSED, check your queue retention settings.
Additionally, make sure that the init.ora parameter AQ_TM_PROCESSES is set to a NON-ZERO value for this to happen.

Flex client can SEND but not RECEIVE messages from BlazeDS

Hi there,
I built a sample chat application that should be able to send/receive messages from a JMS topic. However, I am only able to SEND messages, I am not able to receive them. Any advice/suggestions would be GREATLY appreciated as I am seriously stuck.
My setup:
- BlazeDS Turnkey
- FioranoMQ JMS provider on remote machine
What I know:
- My MXML code is good. I am able to use the exact same code and get both subscribing and publishing working when I use 'ActiveMQ' instead of 'FioranoMQ' as my JMS provider
- FioranoMQ JMS provider is working fine, my test Java clients can both subscribe and publish to the same JMS topic that the Flex app uses
- Publishing from my Flex app is working because my Java client is able to receive messages from the same topic whenever Flex messages are sent to FioranoMQ
- My Flex app is supposedly 'subscribed' to and 'connected' to the correct (streaming-amf) channel. I know this because the MXML 'Consumer' object's "subscribed" and "connected" properties are true and no fault events appear whenever I issue "consumer.subscribe()" in my Flex app.
Sample debug console log:
(I tried sending 8 JMS messages from my Java client code to the 'mytopic' topic that my Flex app is using. The end of the log shows that SOMETHING is happening after sending these messages, but notice the actual 'message' is never streamed even in the log!)
[BlazeDS] 01/27/2009 FlexSession created with id '72D3E6EED1364AD328F342F1AF59FF
69' for an Http-based client connection.
[BlazeDS] 01/27/2009 Channel endpoint flextest-streaming-amf received request.
[BlazeDS] 01/27/2009 Deserializing AMF/HTTP request
Version: 3
(Message #0 targetURI=null, responseURI=/1)
(Array #0)
[0] = (Typed Object #0 'flex.messaging.messages.CommandMessage')
operation = 5
correlationId = ""
clientId = null
timestamp = 0
body = (Object #1)
headers = (Object #2)
DSMessagingVersion = 1
DSId = "nil"
timeToLive = 0
destination = ""
messageId = "AECE3D84-789C-29B7-3413-197C7A48A7D2"
[BlazeDS] 01/27/2009 Serializing AMF/HTTP response
Version: 3
(Message #0 targetURI=/1/onResult, responseURI=)
(Externalizable Object #0 'DSK')
(Object #1)
DSMessagingVersion = 1.0
DSId = "ED38E721-2609-CF34-62A2-28D918C4BB8F"
1.233083202182E12
(Byte Array #2, Length 16)
(Byte Array #3, Length 16)
(Byte Array #4, Length 16)
[BlazeDS] 01/27/2009 Channel endpoint flextest-streaming-amf received request.
[BlazeDS] 01/27/2009 Endpoint with id 'flextest-streaming-amf' is streaming mess
age: Flex Message (flex.messaging.messages.AcknowledgeMessage)
clientId = null
correlationId = open
destination = null
messageId = ED38E793-E519-95BB-3E4C-1A7E8D716951
timestamp = 1233083202229
timeToLive = 0
body = ED38E793-E50A-2500-E2F5-7525401FD8CE
[BlazeDS] 01/27/2009 Number of streaming clients for FlexSession with id '72D3E6
EED1364AD328F342F1AF59FF69' is 1.
[BlazeDS] 01/27/2009 Number of streaming clients for endpoint with id 'flextest-
streaming-amf' is 1.
[BlazeDS] 01/27/2009 Channel endpoint flextest-streaming-amf received request.
[BlazeDS] 01/27/2009 Deserializing AMF/HTTP request
Version: 3
(Message #0 targetURI=null, responseURI=/2)
(Array #0)
[0] = (Typed Object #0 'flex.messaging.messages.CommandMessage')
operation = 0
correlationId = ""
clientId = null
timestamp = 0
body = (Object #1)
headers = (Object #2)
DSEndpoint = "flextest-streaming-amf"
DSId = "ED38E721-2609-CF34-62A2-28D918C4BB8F"
timeToLive = 0
destination = "flextest-message-destination"
messageId = "5ED8AAA4-BDA8-C8E4-D85B-197C7AC5E83A"
[BlazeDS] 01/27/2009 JMS consumer for JMS destination 'mytopic' is starting.
[BlazeDS] 01/27/2009 JMS consumer for JMS destination 'mytopic' is

Hi Alex, thanks for your advice. I tried reading the client-side logs, but it just physically shows what I was saying earlier - that the consumer is connected and subscribed, but no messages are coming through to it.
I've attached the output of the 'flashlog.txt' file. For the particular session shown, the flex application was sent 8 JMS messages, but as you can see nothing got through. I put a 'trace' message in the message handler function (for my consumer object), but it never gets called.
'E2513351-75DA-0837-7263-3807B91D9630' consumer set destination to 'flextest-message-destination'.
'7D784A40-DBBB-71F1-4029-3807B91D45E3' producer set destination to 'flextest-message-destination'.
'consumer' consumer subscribe.
'flextest-streaming-amf' channel endpoint set to http://localhost:8400/FLEXTEST/msgbroker/streaming-amf
'flextest-streaming-amf' channel settings are:
'flextest-streaming-amf' pinging endpoint.
'flextest-streaming-amf' channel is connected.
'flextest-streaming-amf' channel sending message:
(mx.messaging.messages::CommandMessage)
body=(Object)#0
clientId=(null)
correlationId=""
destination="flextest-message-destination"
headers=(Object)#0
messageId="8A592005-3C8A-4C6C-B074-380857710C00"
operation="subscribe"
timeToLive=0
timestamp=0
'consumer' consumer connected.
'consumer' consumer acknowledge for subscribe. Client id '37CC5DED-A019-7110-3C89-A9926835103E' new timestamp 1233595684954
'consumer' consumer acknowledge of '8A592005-3C8A-4C6C-B074-380857710C00'.
Seems to me there can only be two explanations: either my BlazeDS configuration is incorrect (which is unlikely given that everything works if I use a ActiveMQ as my JMS provider with only trivial changes to my configuration), or there is some bug within BlazeDS that is preventing it from working properly with FioranoMQ. What do you think?

Configuring MDB to receive message from MQSeries Queues bound on WL JNDI

Similar Messages

Maybe you are looking for