Polling message from Queue

Hi B2B Gurus,
Is there any way that I could control polling messages from Queue(AQ/JMS).
(e.g) There are 1000 messages in the queue, I want to process 10 at a time.
Are there any settings that can I do so that i can poll 10 messages at a time.
Thanks for your help in Advance.
Regards,
Priyanka

Polling is only based on the interval and not based on size. Please raise an ER.

Similar Messages

Jms adapter not polling messages from jms topic

Hi
We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
<adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
      
      <property name="PayloadType" value="TextMessage"/>
      
      <property name="UseMessageListener" value="true"/>
      <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
    </activation-spec>
</endpoint-activation>
</adapter-config>
If we remove Durable subscriber and message selector properties,its able to poll messages.
Any pointer will help
thanks in advance
Baji

After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
<property name="UseMessageListener" value="false"/>
But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
<property name="DurableSubscriber" value="XYZ"/>
If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
Thanks
Baji

Code to Retrieve the message from Queue in Oracle BPEL

Actually I am placing the Message into JMS Queue using JMS Adapter.After Placing the message,I need to retrieve the placed message from same queue.
Right now I am using the Receive Activity and the JMS Adapter to retrieve the message from Queue.But my receive activity is always in the waiting state itself and I am not able to retrieve the message from queue.What might be the issue????
Can anybody give me a better suggestion so that I can go ahead??
Thanks in advance for your help.

Hi Raja,
Is the process a empty bpel process which is used to get the message from the MQ?
Regards
Surya

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

Poll messages from XI servers

Hi,
Client applications located behind a firewall cannot receive messages from XI over HTTP or SOAP. SAP XI cannot initiate an HTTP connection to them. Would it be possible to develop some sort of polling mechanism whereby the client checks at regular intervals if messages are available?
Maybe some sort of endlessly running business process could be used? But then, each polling call for each client will be monitored.
Or the development of our own adapter? Or some servlet that retrieves messages (files) from directory or jms queue?
Kind regards, Guy Crets

Hi,
>>>Or the development of our own adapter? Or some servlet that retrieves messages (files) from directory or jms queue?
you only said you cannot go for the HTTP nor SOAP
but you didn't say <b>what you can use</b>:)
>>>Would it be possible to develop some sort of polling mechanism whereby the client checks at regular intervals if messages are available?
if you can use FTP/SFTP why don't try this?
XI can puts the file in some folder and the clients appliction just takes the file (scheduled polling)
>>>Or the development of our own adapter?
what for?
BTW
did you thought about j2se adapters ?
maybe the XI will can connect to one of them
through XI SOAP protocol and j2se adapter placed
at the client's place will communicate with the application?
however if you you cannot use SOAP at all this will not work I guess
Regards,
michal

Remove message from queue for rule based subscriber

Hi ,
I created a rule based subscription for one xx_Queue when i am dequeing trying dequeue.conditions like REMOVE it's saying i can mention either dequeue condition or rule based .So if i didn't give REMOVE condition i am able to dequeue but next time when i run again the old message is coming because the message was not removed from queue.So how can i approach that one?

No version number.
No DDL.
And you want us to guess at the actual message when you write: "it's saying i can mention either dequeue condition or rule based."
Not possible.
Unless you can see one of us standing behind your chair reading your monitor ... you need to provide every single relevant unknown.
If you do not know what is relevant, like the actual message, ask a coworker to help you.

Discarding JMS messages from queue

Hi,
I have some Weblogic JMS queues, and some OSB SOAP based JMS Proxy Services listening to those queues.
Sometimes, the source application puts a message in the JMS queue, which is not a valid SOAP XML, or sometimes is a simple text. For such cases, the Proxy service is not able to receive the message from the JMS, and the OSB logs keep on piling up with the error messages.
Is there any way to discard such messages, which the proxy is unable to read, automatically ?

Hello buddies,
I have the same problem. The scenario is the following:
On request:
WS Client -> FrontRequestQueue -> Proxy Service -> Business Service -> BackRequestQueue -> WS Server JMS
On response:
WS Client <- FrontRequestQueue <- Proxy Service <- Business Service <- BackResponseQueue <- WS Server JMS
1st Case: WS Client send a correct & valid Soap Message with all request info OK. Result OK
2nd Case: WS Client send a Soap Message with KO info. Result: Error handled on Proxy Service and error message is returned, OK.
3rd Case: WS Client send a "HelloWorld" String.
Result:
An *<Error> +<OSB Kernel> <BEA-380003> <Excepción en TransportManagerImpl.receiveMessage, com.bea.wli.sb.context.BindingLayerException: Failed to parse XML text+*
com.bea.wli.sb.context.BindingLayerException: Fallo al anular la canalización del mensaje: Failed to parse XML text*
+ at com.bea.wli.sb.context.ContextUtils.newException(ContextUtils.java:933)+
etc...
Proxy Service tries to read the messages from the queue infinitely producing many errors on server, so I have to stop the queue and delete the message to force stop it.
I've changed all the JMS Transport "retry" params on Proxy and Biz services and the behaviour is the same, any suggestions?
Thanks to all.

Error retreiving messages from Queue

Hi Friends,
I am trying to retreive messages from a queue on a remote machine where MQ server has been setup correctly.(nojndi ) I am able to fetch the messages correctly when I use the MQ Base Java API. But I get an exception when I use JMS Api. I am able to put messages on the queue with both MQ base API and JMS API.
When I run the IVTRun program with -nojndi switch I get the following error
C:\Program Files\IBM\MQSeries\Java\bin>IVTRun -nojndi -client -m PINQMGR -host pinnsd01m-0.sabre.com
WebGain Java! JustInTime Compiler Version 4.00.007(x) for JDK 1.2
Copyright (C) 2000 WebGain, Inc.
5648-C60 (c) Copyright IBM Corp. 1999. All Rights Reserved.
MQSeries classes for Java(tm) Message Service 5.200
Installation Verification Test
Creating a QueueConnectionFactory
Creating a Connection
Creating a Session
Creating a Queue
Creating a QueueSender
Creating a QueueReceiver
Creating a TextMessage
Sending the message to SYSTEM.DEFAULT.LOCAL.QUEUE
Reading the message back again
Caught exception: javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue
com.ibm.mq.MQException: Completion Code 2, Reason 2046
IVT finished
I also tried several combinations of the channel switch but still getting the same error.
Does any one knows abt error 2046. I cant see the documentation for any of these errors anywhere and i would be grateful if I get pointers on this.
Advanced Thanks,
Ram

here's an explanation for error code 2046. I will look into why you are getting that if I get time later.
MQRC_OPTIONS_ERROR
The Options parameter or field contains options that are not valid, or a combination of options that is not valid.
For the MQOPEN , MQCLOSE , MQXCNVC , mqBagToBuffer, mqBufferToBag, mqCreateBag, and mqExecute calls, Options is a separate parameter on the call.
This reason also occurs if the parameter pointer is not valid. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
For the MQBEGIN , MQCONNX , MQGET , MQPUT , and MQPUT1 calls, Options is a field in the relevant options structure (MQBO, MQCNO, MQGMO, or MQPMO).
Corrective action: Specify valid options. Check the description of the Options parameter or field to determine which options and combinations of options are valid. If multiple options are being set by adding the individual options together, ensure that the same option is not added twice.

Receive activity pending when trying to consume message from Queue

Hi ,
I'm using a BPEL process to publish and subscribe message into a queue using JMS adapter.The messages in Queue are produced and consumed properly . But the BPEL process is still running, with a receive activity used to consume that queue, in pending state. The schema used throughout the BPEL and JMS adapter are the same.
Edited by: user13829970 on May 8, 2012 2:07 AM

Make sure you use the same schema and same queue name while configuring the Producer JMS Adapter and also the Consumer JMS Adapter
And in the JMS Consumer Composite, define the interface of the BPEL based on the WSDL of the JMS Adapter (service) and then wire the BPEL and the JMS Adapter. Make sure under the receive activity, the create instance checkbox is checked.
Hope this helps
N

In OSB, how to poll message from DTAQ(data queue in AS400)??

Hi,
In our OSB project, I have a data queue(AS400) in proxy side and Oracle AQ at business side, I can easily connect to Oracle AQ, but I am not able to understand how to connect with DTAQ (data queue). Is there any adapter supporting DTAQ for OSB. or does OSB support DTAQ?? Please help me out.
Thanks
Deb

Hi Bolla,
If I understand correct all you would need to do is in your connectivity map, publish the data to that queue.
example high level hierarchy
prj1Data1
-Indata1 svc
-Indata1 topic
-Indata1Translation svc
-Outdata1Delivery svc
-queOutdata1
prj2Data2
-Indata2 svc
-Indata2 topic
-Indata2Translation svc
-Indata2Delivery svc
cmData2Out Indata2Delivery publishes to queOutdata1
Hope this helps and does not add any additional confustion.

Unable to delete messages from queue.

I have a journaling rule setup to send mail to a archive appliance. I have two messages in my queue that are From Address:<> to my recipient (my archiver's email address). The journal rule works fine since it is working for all my users mail, but I have two messages stuck in my queue complaining that they could not be categorized and an event 9213 for MSExchangeTransport every 30 minutes.
"A non-expirable message with the internal message ID 7996 could not be categorized. This message may be a journal report or other system message. The message will remain in the queue until administrative action is taken to resolve the error. Other messages may also have encountered this error. To further diagnose the error, use the Queue Viewer or the Mail Flow Troubleshooter."
I have tried via the GUI and Shell to remove these two messages. The GUI gives me an error:
Microsoft Exchange Error
Action 'Remove (with NDR)' could not be performed on object 'RE: Test to determine if email can be delivered & Received'.
RE: Test to determine if email can be delivered & Received
Failed
Error:
The requested operation can't be performed for the object with identity MyMailServerName\Submission\7999.
OK
The Shell will actually not report back an error but I still have those messages in the queue. The command to see info about the message was:
Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*[email protected]*" } | Format-List
Then I tried deleting the message using the "InternetMessageID" info I gathered from this.
Remove-Message -Filter {InternetMessageID -eq "[email protected]"} -WithNDR $false
This prompts me for a Yes, No, etc... responce (I thought I had it this time) and gave me no error, but the message still resides in queue.
I am at a loss. Any help?

Correct, two messages stuck in queue and cannot remove.
Environment is a Windows 2003 R2 w/ SP2 64bit server, Exchange 2007 SP1 with all roles, AD/DNS is also Windows 2003 R2 w/ SP2 64bit.
This just seemed to start happening a few days ago and just with these two particular messages. I have a archive appliance from ArcMail and a journal rule setup in Exchange to journal all mail to the ArcMail appliance. This has been working and continues to work except for these two messages.
[PS] C:\>Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*[email protected]*" } | Format-List
Identity          : CO-MAIL1\Submission\7996
Subject           : RE: Test to determine if email can be delivered & Received
InternetMessageId : <[email protected]>
FromAddress       : <>
Status            : Retry
Size              : 29638B
MessageSourceName : Journaling
SourceIP          : 255.255.255.255
SCL               : 0
DateReceived      : 9/18/2008 1:39:34 PM
ExpirationTime    :
LastError         : Categorization failed. The message will be deferred and ret
                    ried because it was marked for retry if rejected.
RetryCount        : 0
Queue             : CO-MAIL1\Submission
Recipients        : {[email protected]}
IsValid           : True
ObjectState       : Unchanged
Identity          : CO-MAIL1\Submission\7999
Subject           : RE: Test to determine if email can be delivered & Received
InternetMessageId : <[email protected]>
FromAddress       : <>
Status            : Retry
Size              : 29623B
MessageSourceName : Journaling
SourceIP          : 255.255.255.255
SCL               : 0
DateReceived      : 9/18/2008 1:39:34 PM
ExpirationTime    :
LastError         : Categorization failed. The message will be deferred and ret
                    ried because it was marked for retry if rejected.
RetryCount        : 0
Queue             : CO-MAIL1\Submission
Recipients        : {[email protected]}
IsValid           : True
ObjectState       : Unchanged
Domain Controller Diagnosis
Performing initial setup:
   Done gathering initial info.
Doing initial required tests
   Testing server: co-site\CO-DNS1
      Starting test: Connectivity
         ......................... CO-DNS1 passed test Connectivity
Doing primary tests
   Testing server: co-site\CO-DNS1
      Starting test: Replications
         ......................... CO-DNS1 passed test Replications
      Starting test: NCSecDesc
         ......................... CO-DNS1 passed test NCSecDesc
      Starting test: NetLogons
         ......................... CO-DNS1 passed test NetLogons
      Starting test: Advertising
         ......................... CO-DNS1 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... CO-DNS1 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... CO-DNS1 passed test RidManager
      Starting test: MachineAccount
         ......................... CO-DNS1 passed test MachineAccount
      Starting test: Services
         ......................... CO-DNS1 passed test Services
      Starting test: ObjectsReplicated
         ......................... CO-DNS1 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... CO-DNS1 passed test frssysvol
      Starting test: frsevent
         ......................... CO-DNS1 passed test frsevent
      Starting test: kccevent
         ......................... CO-DNS1 passed test kccevent
      Starting test: systemlog
         ......................... CO-DNS1 passed test systemlog
      Starting test: VerifyReferences
         ......................... CO-DNS1 passed test VerifyReferences
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
   Running partition tests on : lcsd
      Starting test: CrossRefValidation
         ......................... lcsd passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... lcsd passed test CheckSDRefDom
   Running enterprise tests on : lcsd.local
      Starting test: Intersite
         ......................... lcsd.local passed test Intersite
      Starting test: FsmoCheck
         ......................... lcsd.local passed test FsmoCheck
[PS] C:\>Remove-Message -filter {FromAddress -eq "<>"} -withNDR $false -debug -verbose
VERBOSE: Remove-Message : Beginning processing.
Confirm
Are you sure you want to perform this action?
Removing the messages that match filter "FromAddress -eq "<>"".
Yes Yes to All No [L] No to All Suspend [?] Help
(default is "Y"):Y
VERBOSE: Remove-Message : Ending processing.
[PS] C:\>Remove-Message -Filter {InternetMessageID -eq "[email protected]"} -WithNDR $false -debug -verbose
VERBOSE: Remove-Message : Beginning processing.
Confirm
Are you sure you want to perform this action?
Removing the messages that match filter "InternetMessageID -eq
"[email protected]"".
Yes Yes to All No [L] No to All Suspend [?] Help
(default is "Y"):Y
VERBOSE: Remove-Message : Ending processing.
[PS] C:\>Remove-Message -filter {FromAddress -eq ""} -withNDR $false -debug -ver
bose
VERBOSE: Remove-Message : Beginning processing.
Confirm
Are you sure you want to perform this action?
Removing the messages that match filter "FromAddress -eq """.
Yes Yes to All No [L] No to All Suspend [?] Help
(default is "Y"):Y
VERBOSE: Remove-Message : Ending processing.
[PS] C:\>
Tried several filter options and all had the same result. No events in the event viewer and did not remove the stuck messages.

Losing messages from queue

(OT: i can't figure out these newsgroups too well. i tried using the public newsgroups from my isp usenet server, but they don't seem to get posted here...)
          we have a mdb which acts like a pass through to a stateless session bean. (command pattern?). anyway. the mdb requires a transaction, as does all the slsb's involved. the slsb basically posts orders to a database. during load testing, the whole thing goes flaky. a client application submits 1000 orders to be processed (simulates 10 users, 2 orders per minute per user, 100 orders total per user.). the thing is, 1000 orders never make it to the database, but most times the jms queue has processed all it's messages (no messges pending). we're using guaranteed delivery on the client side, and looking at the wls console can see that there were 1000 messages in the queue.
          the mdb's have a pool of 20 beans, and there is 60 max db connections. we know the db connections are having issues, timing out all over the place and such. i would hope that our app can recover from that ok. when there's any error in processing, we set rollback on the context.
          we're noticing that messages seem to get committed from the jms queue and not committed to the database. maybe the db is getting rolled back and the db isn't. maybe the db never has a chance to commit the item.
          i can see that messages are getting re-process ok. so i do know that rollbacks are happening on the db side of things. it's just a little challenging to trace all 1000 messages through the system to find what happened.
          does anyone have some ideas where we can start to troubleshoot these "missing" messages/transactions?
          we're using oracle's thin xa driver with wls 8.1sp2.
          if anyone could perhaps shed a bit of light on this (troubleshooting tips), it would be most certainly appreciated!!
          our next step we're going to take is to enable DebugJMSXA and DebugMessagePath logging from the server, and also logging the message id's and message retry attributes from the applicatin.

(OT: i can't figure out these newsgroups too well. i          > tried using the public newsgroups from my isp usenet
          > server, but they don't seem to get posted here...)
          OT: I'm told that that the transfer between usenet and forums is not immediate - it may take up to 15 minutes. I will forward your comment.
          >
          > we have a mdb which acts like a pass through to a
          > stateless session bean. (command pattern?). anyway.
          > the mdb requires a transaction,
          First thing to check: Is the MDB descriptor marked BOTH with "Container" and "Required"? (Actually, my bet is that your OK here.)
          > as does all the
          > slsb's involved. the slsb basically posts orders to a
          > database. during load testing, the whole thing goes
          > flaky. a client application submits 1000 orders to be
          > processed (simulates 10 users, 2 orders per minute
          > per user, 100 orders total per user.). the thing is,
          > 1000 orders never make it to the database,
          All 1000?
          > but most
          > times the jms queue has processed all it's messages
          > (no messges pending). we're using guaranteed delivery
          > on the client side, and looking at the wls console
          > can see that there were 1000 messages in the queue.
          >
          > the mdb's have a pool of 20 beans, and there is 60
          > 0 max db connections. we know the db connections are
          > having issues, timing out all over the place and
          > such.
          What operation in particular is timing out? And can you post your config.xml for the connection pool and data source?
          > i would hope that our app can recover from
          > that ok. when there's any error in processing, we set
          > rollback on the context.
          >
          > we're noticing that messages seem to get committed
          > from the jms queue and not committed to the database.
          > maybe the db is getting rolled back and the db
          > b isn't. maybe the db never has a chance to commit
          > the item.
          BTW: The Oracle 10g thin driver handles XA much faster than their earlier drivers. I think that BEA consequently now generally recommends using this driver now.
          >
          > i can see that messages are getting re-process ok.
          > so i do know that rollbacks are happening on the db
          > b side of things. it's just a little challenging to
          > trace all 1000 messages through the system to find
          > what happened.
          >
          > does anyone have some ideas where we can start to
          > troubleshoot these "missing" messages/transactions?
          What do you mean by "re-proces ok". Does this mean that once all reprocessing completes, all messages have been processed correctly?
          >
          > we're using oracle's thin xa driver with wls 8.1sp2.
          >
          > if anyone could perhaps shed a bit of light on this
          > (troubleshooting tips), it would be most certainly
          > appreciated!!
          >
          > our next step we're going to take is to enable
          > DebugJMSXA and DebugMessagePath logging from the
          > server, and also logging the message id's and message
          > retry attributes from the applicatin.
          One thing to do is sanity check the entry points in each of your beans (MDB and SSB) to ensure that there is a transaction on the thread. The JMS FAQ contains info on this: TxHelper.getTransaction()...
          Another is to investigate whether transactions are timing out. (Increase the transaction timeout and see if either (A) rollbacks stop occuring or (B) if rollbacks take longer to occur.)

Having problems receiving messages from queue

Hi,
I have one machine simply sending messages to a message queue on another machine. I know that the messages are arriving at the destination queue because I can use a modified version of the SimpleSyncConsumer program from the j2ee tutorial to receive the message with no troubles.
On the destination machine, I also have deployed a web servlet that is trying to do the exact same thing as the SimpleSyncConsumer, connecting to the same connection factory and same destination resource, yet it cannot receive (non-block) the message. It's almost as if it has connected to the wrong queue. There doesn't seem to be any indication of errors prior to the attempt to receive. The connection factory, connection session, consumer, all look fine.
Does anyone know why I'm getting this problem?
Thank you very much

Thanks to strachaj and pazhanikanthan for your replies.
I'd also like to emphasize the small (not servlet) application I made that is just like the SimpleSyncConsumer program which uses the same code I used inthe servlet, to connect to the servlet's queue and that it is able to receive the message.
Is there some configuration that needs to be done on the servlet war file using the deploytool to enable it to properly receive the message? I noticed the other examples in the tutorial made use of MDB's which required some extensive configuration (that dealt with queues) from the deploytool. I did not use any MDB's as I didn't think it was necessary judging from how the SimpleSyncConsumer connected to the queue. Am I mistaken?
Thanks again!

Enterprise Link (Consuming Message from queue)

Hi , I start to use the enterprise link studio and I want to know if there is a way to see the content from a queue , for example I configure in Architect an EMS , and in enterprise link I create Oracle BAM Enterprise Message Receiver , now I want to know if this configuration is correct and the content of my message, more over I want to parse the content of this xml message and input in some variable( is this possible?)
Thanks a lot.

Hi,
You can do this by creating a plan connecting the EMS receiver to a Grid (listed under display sinks ) and then clicking update. This will display the raw message.
Replacing the Grid with Oracle BAM Insert sink you can put the data in a BAM dataobject as a single long string to begin and then add a xsl transformation to EMS (under BAM Architect) to parse. See the samples/tutorials on OTN
Thanks
Ranga

Not able to get the message from Queue using MQ adapter

HI
Using Mq adapter am able to put the message in a queue and am able to get the message if i select the schema type as opaque, but am not able to get the message if i specify any schema type and am getting timed out exception.
Kindly help to proceed with this issue.

Hi,
Am also facing the same issue.
I would be thankful if anyone can provide the solution

Polling message from Queue

Similar Messages

Maybe you are looking for