MessageSelector

I have a client which receives messages from am queue. I have defined a message
selector for receiver which reads, JMSCorrelationID='RMA987654321'. The JMS header
field JMSCorrelationID is being set by a WLI process before it publishes messages
to this queue. When I start this client, it does not seem to pick up any messages
from the queue though the JMSCorrelationID has been set to this value for all
the messages.
It does work if I do not specify any messageSelector.
--Krish.

Are you sure the problem is a matter of header property name length? I was
also having a problem setting the JMSCorrelationID header property. It
kept coming back null. I finally decided to make up my own property name
and now it works fine. My property name is ConfirmationCorrelationID.
I thought I read somewhere in the docs, that we are supposed to be able to
set the JMSCorrelationID header property, so there may still be a bug
there.
Tony
[email protected] (Krish Khambadkone) wrote:
>
Sorry for the confusion. The problem is now sorted. It seems that I
was setting the header for the wrong message. I am able to now send JMS
header info. (JMS_CID) on both inbound and outbound messages from and to
WLI. The length is still an issue however. Is this a bug or a feature?
Thank you all for your help.
--Krish.
Sean Garagan <[email protected]> wrote:
Hi Krish,
About the property name, according to the JMS spec, any properties
starting with JMS_ are reserved for the JMS
provider, not a client. JMS and JMSX are also reserved. Try changing
the name to something that doesn't start
with these values.
One other question, which version of WLI are you using?
Sean
Krish Khambadkone wrote:
The problem seems to be the variable name. When I used a short namelike JMS_CID,
it works. I have another interesting problem. When I send the
message to WLI,
I am setting a msg.setStringProperty("JMS_CID","RMA39393"). Whendo a ToString(EventAttribute("JMS_CID"))
in WLI, and print it out, it always prints NULL. Any ideas?
--Krish.
"tony lodge" <[email protected]> wrote:
What is the message selector you have defined
"Krish Khambadkone" <[email protected]> wrote in message
news:[email protected]...
I have a client which receives messages from am queue. I have
defined a
message
selector for receiver which reads,
JMSCorrelationID='RMA987654321'. The
JMS header
field JMSCorrelationID is being set by a WLI process before it
publishes messages
to this queue. When I start this client, it does not seem to
pick up any
messages
from the queue though the JMSCorrelationID has been set to this
value
for
all
the messages.
It does work if I do not specify any messageSelector.
--Krish.

Similar Messages

Search MessageSelector sample for complex boolean express with AND, OR, NOT

As far as I know I can specify in the "Message Selector" field of a JMS-PartnerLink
a boolean expression.
How are AND, OR and NOT written here? Can I use brackets?
Can I use blanks inside the boolean expression?
Assume I would like to specify:
((myfield1 > 3.0) && (myfield2 == 777)) || (myfield3 != 'aaa')
Is the syntax correct for this?

http://www.mcs.csueastbay.edu/support/oracle/doc/10.2/server.102/b14257/jm_create.htm
11.3 JMS Point-to-Point Model Features/MessageSelector
that will give you some examples of how to use it

How does messageSelector work

I have couple of questions about MessageSelctor:
          1. What is the time complexity of message selection operation in terms of queue size? Does this operation browse through the queue sequentially and selects matching messages or can it do some optimization (e.g. use binary search if queue was kept sorted by the attribute used for selection) ?.
          2. What should messageSelector string look like?

I recommend refering to the dev2dev "JMS Performance Guide" white-paper. While it was written for version 8.1, it's mostly up-to-date specifically with respect to selector performance. The two related post 8.1 changes I can think of are (A) 9.0+ message properties may now be paged out of JVM memory - so a selector that references message properties can force additional paging, and (B) depending on the use case, the 9.0+ Unit-of-Order (UOO) feature can sometimes be leveraged fairly elegantly instead of selectors.
          With regard to selector syntax: the JMS API javadoc covers selector syntax well enough for most purposes. You can find more information in the JMS specification.
          Links:
          http://java.sun.com/products/jms/docs.html
          http://dev2dev.bea.com/pub/a/2004/01/WL_JMS_Perform_GD.html
          Tom

ODI JMS to SQL MESSAGESELECTOR

Hi,
Anybody had successful experience using ODI with JMS to SQL technology trying to consume messages from Weblogic Topic with MESSAGESELECTOR option? Having trouble that ODI consumed all messages from Topic indiscriminately whenever there was a MESSAGESELECTOR expression present from ODI Interface. Any suggestion/idea are welcome.
AL

There is definitely a message selector defined in the message. I am using Message Selector and ClientID (Subscriber ID) in LKM. It turns out that the subscriber needs to be configured with same message selector expression. Otherwise when ODI hit the subscriber, it behaves as if it is setting the message selector on the subscriber in Weblogic, and the setting operation will reset all messages.
Not sure if this is documented anywhere ( ODI or Weblogic ).
Thanks
Albert

How do I use a MessageSelector with application-specific properties

According to a couple of JMS references (Sun, Oreilly) and the oracle documentation (under the heading "Using Oracle Java Messaging Service (JMS) to Access AQ", page 102 of 1082 , Application Developers Guide - Advanced Queuing, Release 2 (8.1.6))
Standard JMS Features
"Message selection based on message header fields/properties"
Is there a special syntax for using application-specific (user defined) JMS message properties as message selectors in Oracle 8.1.7?
I've tried to create a message selector based on a custom property that I set, i.e. "username != 'William'". (example from O'Reilly JMS book, pg. 44)
I always get a JMS-159: Invalid selector Selector Parse error unless the property is a JMS-Defined property. i.e., " JMSMessageID = 'ID:9789D65E215B3613E034080020B1456E' " works fine.
From the docs and the oter examples, I figure application-specific (user-defined) properties are legal.
Thans for any help in advance.

Well I found an article in another forum that states in oracle 8i, message selectors are only supported on JMSCorrelationID and JMSMessageID
(9i will have/has the full JMS spec support for message selectors , or so the response to the message says)
Thanks anyway
(Aricle Is In Products > Database > Oracle Advanced Queueing
Title is JMS AQ: selector in createReceiver does not work)

How do I use a JMS MessageSelector with application-specific properties

According to a couple of JMS references (Sun, Oreilly) and the oracle documentation (under the heading "Using Oracle Java Messaging Service (JMS) to Access AQ", page 102 of 1082 , Application Developers Guide - Advanced Queuing, Release 2 (8.1.6))
Standard JMS Features
"Message selection based on message header fields/properties"
Is there a special syntax for using application-specific (user defined) JMS message properties as message selectors in Oracle 8.1.7?
I've tried to create a message selector based on a custom property that I set, i.e. "username != 'William'". (example from O'Reilly JMS book, pg. 44)
I always get a JMS-159: Invalid selector Selector Parse error unless the property is a JMS-Defined property. i.e., " JMSMessageID = 'ID:9789D65E215B3613E034080020B1456E' " works fine.
From the docs and the oter examples, I figure application-specific (user-defined) properties are legal.
Thans for any help in advance.

Well I found an article in another forum that states in oracle 8i, message selectors are only supported on JMSCorrelationID and JMSMessageID
(9i will have/has the full JMS spec support for message selectors , or so the response to the message says)
Thanks anyway
(Aricle Is In Products > Database > Oracle Advanced Queueing
Title is JMS AQ: selector in createReceiver does not work)

OC4J Application Server - InstantiationException

Error : java.lang.InstantiationException: Error initializing ejb-modules: message-destination-mapping tag with missing 'location' attribute
HI All,
Hope someone can help me with the following error. I've got a ear file which deploys 100% correct, and the application can run successfully after deploying. But if I stop and start the container, then i get the following exception, the container starts up but the application does not start successfully.
Oracle Container start-up exception:
09/05/11 09:17:15 Start process
Listening for transport dt_socket at address: 8688
0.000: [GC [PSYoungGen: 43776K->4394K(51008K)] 43776K->4394K(517056K), 0.0290830 secs]
3.295: [GC [PSYoungGen: 48170K->7220K(51008K)] 48170K->8371K(517056K), 0.0499300 secs]
6.817: [GC [PSYoungGen: 50996K->7218K(51008K)] 52147K->13636K(517056K), 0.0504670 secs]
09/05/11 09:17:28 WARNING: Application.setConfig Application: stf-7.0.1 is in failed state as initialization failed.
java.lang.InstantiationException: Error initializing ejb-modules: message-destination-mapping tag with missing 'location' attribute
09/05/11 09:17:29 Oracle Containers for J2EE 10g (10.1.3.2.0) initialized
29.062: [GC [PSYoungGen: 50994K->7226K(51008K)] 57412K->15785K(517056K), 0.0436860 secs]
32.675: [GC [PSYoungGen: 51002K->7228K(50880K)] 59561K->16729K(516928K), 0.0346460 secs]
We use jdk1.5, Ejb3 and Oracle 10.1.3
We use message driven beans, for which we create an ejb-jar.xml that looks as follow:
Start
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
     
     <display-name>vss-ejb</display-name>
     <enterprise-beans>
          <message-driven>
               <display-name>VSSAdvancedQueueBatchBeanMDB</display-name>
               <ejb-name>VSSAdvancedQueueBatchBean</ejb-name>
               <ejb-class>
                    za.globed.varsite.hebs.bsi.services.ejb.VSSAdvancedQueueBatchBean
               </ejb-class>
               <transaction-type>Bean</transaction-type>
               <message-destination-type>
                    javax.jms.Queue
               </message-destination-type>
               <message-destination-link>
                    jms/batchQueue
               </message-destination-link>
               <activation-config>
                    <activation-config-property>
                         <activation-config-property-name>
                              acknowledgeMode
                         </activation-config-property-name>
                         <activation-config-property-value>
                              Auto-acknowledge
                         </activation-config-property-value>
                    </activation-config-property>
                    <activation-config-property>
                         <activation-config-property-name>
                              destinationType
                         </activation-config-property-name>
                         <activation-config-property-value>
                              javax.jms.Queue
                         </activation-config-property-value>
                    </activation-config-property>
                    <activation-config-property>
                         <activation-config-property-name>
                              subscriptionDurability
                         </activation-config-property-name>
                         <activation-config-property-value>
                              NonDurable
                         </activation-config-property-value>
                    </activation-config-property>
                    <activation-config-property>
                         <activation-config-property-name>
                              messageSelector
                         </activation-config-property-name>
                         <activation-config-property-value>
                              Destination =
                              'za.globed.varsite.hebs.bsi.services.VSSAdvancedQueueBatchBean'
                         </activation-config-property-value>
                    </activation-config-property>
               </activation-config>
          </message-driven>
     </enterprise-beans>
     <assembly-descriptor>
          <container-transaction>
               <method>
                    <ejb-name>VSSAdvancedQueueBatchBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Supports</trans-attribute>
          </container-transaction>
          <message-destination>
               <display-name>
                    Destination for VSSAdvancedQueueBatchBean
               </display-name>
               <message-destination-name>
                    jms/batchQueue
               </message-destination-name>
          </message-destination>
     </assembly-descriptor>
</ejb-jar>
-- end --
Any help or suggestions would be much appreciated.
Thanks
Nina

I would advise you to use the latest version - 10.1.3.5 - i remember some issues with 10.1.3.4.
For certifications see here:
http://www.oracle.com/technetwork/middleware/ias/downloads/oracle-soa-certification-101310-097492.html
You have two options to bypass the check:
* Use ignore : runinstaller -ignoresysprereqs
http://onlineappsdba.com/index.php/2008/11/24/upgrade-oracle-application-server-to-10134-10g-r3-patchset-4/
* Or change in the installers file that lists the allowed versions - you can search for the numbers listed in your error dialog

Slow Performance on QueueReciever.recieve() + MQ

Hi,
I have been wrecking my brains around this pickle for the last week or so and would appreciate any assistance I could get here.
Problem Description: Incredibly slow performance when invoking a QueueReciever.recieve() connecting to MQ server version 6
Benchmarks: 100-900ms per invocation
Configuration:
JVM: WS 6's own
MQ: 6.0
Application Server: WAS 6
Managed resources: Queue Connection Factory (queues are dynamically created)
Runtime artifacts: QueueConnectionFactory, QueueConnection, QueueConnection, QueueSession, QueueSender,
QueueReciever, TextMessage, in Queue out Queue
Scenario:
QueueSender created
QueueReciever created using a MessageSelector filtering on JMSCorrelationID
Message is sent to the in queue using QueueSender, embedded with a JMSCorrelationIDImmediately after, a QueueReciever.receive() is invoked listening on the out queue
Result: VERY slow return from the synchronous block on the receive().
Given: reply message is put on the out-queue after about 40ms by 3rd party application.
Again any assistance would be appreciated.
Message was edited by:
sg9aeee

Hi Wietse
Your RFC communication may be slow because limitations on the Gateway connection parameters.
Please check the Gateway profile parameters, like max_conn, blocksize etc
Thanks
Yatin Bhatt

Multiple Messages in Same JMS queue

Hello,
I have interfaces in which different xml messages from the same sender system will be placed in the same MQ queue, is there a way that XI JMS sender channel can differentiate the xml messages based on the payload?
I can create a single communication channel, but the outbound message interface I cannot create a common structure because the xml messages are huge and there will be future interfaces following the same architecture.
1. How can I route in interface determination based on the context in the inbound msg interface?
2. What can I provide as Message interface for the outbound?
3. MessageSelector attribute in Adapter specific properties - any ideas on this? - I can select this in the condition context in interface determination - can I give any values here to differentiate msges?
4. Value mapping - is it possible to define the sender message interface through this?
Any idea is appreciated..THank you..

Hi Thanujja,
We have recently completed a project that had this requirement too. We made use of the MessageSelector to solve this problem. You'll need to make use of some advanced (advanced tab)settings in the comm channel. Basically you want to add Additional JMS Message Properties. You can add up to 10 additonal JMS Properties.
Let's say you've added a property called MESTYP. You then need to get the sender to populate the MESTYP property with a text value for each IDoc involved e.g. DELVRY. You would then set your JMS Message Selector field as follows: MESTYP='DELVRY'.
You'll have a comm channel for each IDoc. These comm channels will then connect to the JMS Queue & only pick up messages that meet the criteria at set in the Message Selector.
There was one other problem that encountered with Message Selector, we were on XI version 7.0, the Message Selector was working intermittently & then we applied SAP Note 1256636 & upgraded to 7.01. Everything is working fine after that.
Trevor

Porting EJB 3 MDB from OC4J to WLS

Posting this again since my last post didn't seem to take.
I get the following three deployment error messages when attempting to deploy an application to WebLogic Server 10.3 technical preview. The problem is centered around my deployment of an EJB 3 message driven bean.
1. An error occurred during activation of changes, please see the log for details.
2. Exception preparing module: EJBModule(EngineEjb.jar) Unable to deploy EJB: Requestor from EngineEjb.jar: [EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'jms/demoQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation. at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:641) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:246) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1013) at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:907) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1211) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:387) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:381) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:517) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
3. Substituted for missing class [EJB - 11026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'jms/demoQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.
My MDB uses an annotation like the following:
@MessageDriven(mappedName = "jms/demoQueue", name = "MyMDB",
activationConfig =
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue")
@ActivationConfigProperty(propertyName = "messageSelector", propertyValue =
"RECIPIENT = 'MyRecipient'")
Earlier, I did create a JMS Module named demoQueue with the following resources:
Name Type JNDI Name
testQueue Queue jms/demoQueue
ConnectionFactory-0 Connection Factory jms/QueueConnectionFactory
Any suggestions to fix the WLS deployment error?
For continuing compatibility with my OC4J deployment, I would like to continue using a connection factory with the following JNDI name "jms/QueueConnectionFactory" shown above.
So I plan to add the following properties to the @MessageDriven annotation above. These are needed to continue working with our OC4J deployment. However, my primary concern is to get this MDB working with WLS. Does this strategy seem reasonable for allowing deployment to both OC4J and WLS?
@ActivationConfigProperty(propertyName = "connectionFactoryJndiName",
propertyValue =
"jms/QueueConnectionFactory") ,
@ActivationConfigProperty(propertyName = "destinationName", propertyValue =
"jms/demoQueue")
Thanks,
Travis

Travis, you pose a very good question. If I understand your goal, you would like to use code that compiles and works in OC4J and WLS. For example, you want to use javax.ejb.MessageDriven instead of weblogic.ejbgen.MessageDriven.
Using something like mappedName as it is referred to here allows you specify the JNDI name in WLS if it is not defined elsewhere, but it appears to be specific to the WLS implementation.
I've seen several other questions posed about finding all of the available ActivationConfigProperty name / value pairs and I have been unable to find it myself.
I tried several permutations of annotations, and I can't figure out why something like this would even work, but it does. The mapped name is my JNDI name, but I never specify that it is a javax.jms.Queue or which connection factory to use. How does WLS figure that out?
@MessageDriven(
     mappedName = "exampleQueue", name = "HelloWorldMDB"
public class HelloWorldMDB implements MessageListener {
     @Override
     @TransactionAttribute(value = javax.ejb.TransactionAttributeType.REQUIRED)
     public void onMessage(Message message) {
          System.out.println( "received message " + message );
}This is a good question for support as the documentation seems to be incomplete here.

Acrobat 9/Vista - Can only covert Office 2007 documents to PDF once before having to stop acrtoray.e

I have Acrobat 9 Pro Extended, Office 2007, and Vista Ultimate 64 with UAC off. I can only convert from an Office document (.doc, .xls) to PDF once before getting problems, after which I have to close the acrotray.exe process in Task Manager (or restart Vista) to get it to work again.
After I successfully convert an Office document, on future attempts it says "Adobe Acrobat is not activated. Cannot create the PDF file."
If in Word I instead choose to Print to Adobe PDF, it says "Word is preparing to background print the document:" but then hangs and I have to stop the program. An error box then says "Adobe PDF creation cannot continue because Acrobat is not activated."
After ending the acrotray.exe process or restarting the computer it works again, but like before only one time. Opening Acrobat and choosing Repair Acrobat Installation doesn't fix the problem unless I restart, which would fix it anyway.
Is there a permanent solution to this issue?

I Also have the same Problem
          When u try to convert word/XLS/TXT to PDF i get this error and when i kill the acrotray process from taskmanager i am able to generate the PDF.
Can anyone of u please let me know what is the problem about and how to solve it.
Error Message:
Error Code:10012
Error Message: ALC-PDG-010-012-PDFMaker reported an error while printing the document.
[5/27/09 12:36:56:665 CDT] 000000f6 SibMessage    W   [:] CWSIV0775W: The creation of a connection for destination adobe_PEDCommandQueue on bus IDP_JMS_Bus for endpoint activation [com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation@5e9a5e9a <active=true> <connections={}> <messageEndpointFactory=com.ibm.ejs.container.MessageEndpointFactoryImpl@f96523e1> <endpointConfiguration=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl$JmsJcaEndp ointConfigurationImpl@593109850 <JmsJcaActivationSpecImpl.this=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl@74 8432540 <userName=null> <password=null> <xaRecoveryAlias=null> <destination=queue://adobe_PEDCommandQueue?deliveryMode=Persistent&busName=IDP_JMS_Bus> <durableSubscriptionHome=null> <destinationType=javax.jms.Queue> <messageSelector=null> <acknowledgeMode=Auto-acknowledge> <subscriptionDurability=NonDurable> <shareDurableSubscriptions=InCluster> <clientId=null> <subscriptionName=null> <maxBatchSize=1> <maxConcurrency=10> <busName=IDP_JMS_Bus> <shareDataSourceWithCMP=false> <targetTransportChain=null> <readAhead=Default> <target=null> <targetType=BusMember> <targetSignificance=Preferred>]>]> <endpointInvoker=com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl@5e8c5e8c> <workManager=com.ibm.ejs.j2c.work.WorkManagerImpl@61246124> <endpointMethodTransactional=false> <remoteConnection=null> <remoteDestination=true> <timer=java.util.Timer@5f045f04>] failed with exception com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus IDP_JMS_Bus running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=IDP_JMS_Bus, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..
[5/27/09 12:36:58:290 CDT] 000000df Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#fbd89dcd0f4e9e5228a3fabc6d917ced"
[5/27/09 12:36:58:290 CDT] 000000df Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:36:58:290 CDT] 000000df Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:36:58:352 CDT] 000000df Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:36:58:509 CDT] 000000df Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:36:58:571 CDT] 000000df Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:36:58:618 CDT] 000000df Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:36:58:665 CDT] 000000df Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#fbd89dcd0f4e9e5228a3fabc6d917ced"
[5/27/09 12:37:02:680 CDT] 000000f7 SibMessage    W   [:] CWSIV0775W: The creation of a connection for destination adobe_PECommandQueue on bus IDP_JMS_Bus for endpoint activation [com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation@7db87db8 <active=true> <connections={}> <messageEndpointFactory=com.ibm.ejs.container.MessageEndpointFactoryImpl@9496c24e> <endpointConfiguration=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl$JmsJcaEndp ointConfigurationImpl@1839361442 <JmsJcaActivationSpecImpl.this=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl@19 78299882 <userName=null> <password=null> <xaRecoveryAlias=null> <destination=queue://adobe_PECommandQueue?deliveryMode=Persistent&busName=IDP_JMS_Bus> <durableSubscriptionHome=null> <destinationType=javax.jms.Queue> <messageSelector=null> <acknowledgeMode=Auto-acknowledge> <subscriptionDurability=NonDurable> <shareDurableSubscriptions=InCluster> <clientId=null> <subscriptionName=null> <maxBatchSize=1> <maxConcurrency=10> <busName=IDP_JMS_Bus> <shareDataSourceWithCMP=false> <targetTransportChain=null> <readAhead=Default> <target=null> <targetType=BusMember> <targetSignificance=Preferred>]>]> <endpointInvoker=com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl@44c444c4> <workManager=com.ibm.ejs.j2c.work.WorkManagerImpl@61246124> <endpointMethodTransactional=true> <remoteConnection=null> <remoteDestination=true> <timer=java.util.Timer@15161516>] failed with exception com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus IDP_JMS_Bus running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=IDP_JMS_Bus, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..
[5/27/09 12:37:05:836 CDT] 000000de Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#fbd89dcd0f4e9e5228a3fabc6d917ced"
[5/27/09 12:37:06:117 CDT] 000000de Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:37:08:664 CDT] 000000f8 SibMessage    W   [:] CWSIV0775W: The creation of a connection for destination adobe_JobManagerQueue on bus IDP_JMS_Bus for endpoint activation [com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation@72607260 <active=true> <connections={}> <messageEndpointFactory=com.ibm.ejs.container.MessageEndpointFactoryImpl@825da81a> <endpointConfiguration=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl$JmsJcaEndp ointConfigurationImpl@1914991140 <JmsJcaActivationSpecImpl.this=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl@10 90535680 <userName=null> <password=null> <xaRecoveryAlias=null> <destination=queue://adobe_JobManagerQueue?deliveryMode=Persistent&busName=IDP_JMS_Bus> <durableSubscriptionHome=null> <destinationType=javax.jms.Queue> <messageSelector=null> <acknowledgeMode=Auto-acknowledge> <subscriptionDurability=NonDurable> <shareDurableSubscriptions=InCluster> <clientId=null> <subscriptionName=null> <maxBatchSize=1> <maxConcurrency=10> <busName=IDP_JMS_Bus> <shareDataSourceWithCMP=false> <targetTransportChain=null> <readAhead=Default> <target=null> <targetType=BusMember> <targetSignificance=Preferred>]>]> <endpointInvoker=com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl@72527252> <workManager=com.ibm.ejs.j2c.work.WorkManagerImpl@61246124> <endpointMethodTransactional=false> <remoteConnection=null> <remoteDestination=true> <timer=java.util.Timer@72ca72ca>] failed with exception com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus IDP_JMS_Bus running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=IDP_JMS_Bus, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..
[5/27/09 12:37:08:680 CDT] 000000de Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:37:08:742 CDT] 000000de Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:37:08:805 CDT] 000000de Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:37:08:883 CDT] 000000de Reference     I org.apache.xml.security.signature.Reference verify Verification successful for URI "#d72defc93c0f2a3e50d48504a433e899"
[5/27/09 12:37:08:883 CDT] 000000de GeneratePDFIm A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-
Job ID for the submitted createPDF job =ADITYA MARLA.doc3c729d-9ec084-189d03-d650cc-0d494f-c2c7cb
[5/27/09 12:37:08:914 CDT] 000000de BMCCaller     A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-024-ADITYA MARLA.doc: Time Job Submitted: 5/27/09 12:37 PM
[5/27/09 12:37:08:914 CDT] 000000de BMCCaller     A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-021-ADITYA MARLA.doc: PDF Settings Used: pdfg Standard 54138
[5/27/09 12:37:08:914 CDT] 000000de BMCCaller     A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-022-ADITYA MARLA.doc: Security Settings Used: No Security
[5/27/09 12:37:08:914 CDT] 000000de BMCCaller     A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-023-ADITYA MARLA.doc: FileType Settings Used: Standard
[5/27/09 12:37:08:914 CDT] 000000de BMCCaller     A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-017-ADITYA MARLA.doc: Job Submitted by User: administrator
[5/27/09 12:37:08:945 CDT] 00000111 WordToPDFConv A com.adobe.service.ProcessResource$ManagerImpl logJdk ALC-PDG-001-001-Begin processing job : C:\Documents and Settings\wasadmin\Local Settings\Temp\pdfg-wasadmin\20\1203-c513d2-9bf144-d0a9f2-f75636-094cdc\native-in.doc
[5/27/09 12:37:12:789 CDT] 00000111 WordToPDFConv A com.adobe.service.ProcessResource$ManagerImpl logJdk ALC-PDG-001-000-Calling function to clean registrys Resiliency entry
[5/27/09 12:37:12:804 CDT] 000000e5 WordToPDFConv A com.adobe.service.ProcessResource$ManagerImpl logJdk ALC-PDG-001-000-The system cannot find the file specified.
[5/27/09 12:37:12:836 CDT] 000000de BMCCaller     A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-028-ADITYA MARLA.doc: Job Completion Status: Failed
[5/27/09 12:37:12:836 CDT] 000000de BMCCaller     A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-025-ADITYA MARLA.doc: Time Job Completed: 5/27/09 12:37 PM
[5/27/09 12:37:12:836 CDT] 000000de BMCCaller     A com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-026-ADITYA MARLA.doc: Time of Job Execution: 3,922 ms
[5/27/09 12:37:12:836 CDT] 000000de GeneratePDFIm E com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-ALC-PDG-010-012-PDFMaker reported an error while printing the document.
[5/27/09 12:37:12:836 CDT] 000000de CreatePDFAct E com.adobe.pdfg.logging.PDFGLogger log ALC-PDG-001-000-Invocation error.
[5/27/09 12:37:12:836 CDT] 000000de CreatePDFAct E com.adobe.pdfg.logging.PDFGLogger log TRAS0014I: The following exception was logged ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:152)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doBMT(EjbTran sactionBMTAdapterBean.java:197)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EJSLocalStatelessEjbTransactionBMTAdapter_ 3af08fdf.doBMT(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:95)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:132)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:118)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:91)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:21 5)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.aes.web.create.CreatePDFAct.createPDF(CreatePDFAct.java:383)
at com.adobe.aes.web.create.CreatePDFAct.createPDF2(CreatePDFAct.java:402)
at com.adobe.aes.web.create.CreatePDFAct.execute(CreatePDFAct.java:174)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at com.adobe.aes.web.AesActionServlet.service(AesActionServlet.java:63)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1096)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1037)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.adobe.idp.um.auth.filter.AuthenticationFilter.doFilter(AuthenticationFilter.java:154)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java: 190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:566)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.jav a:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:748)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink .java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink .java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConn ectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitia lReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionLi stener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
Caused by: ALC-PDG-10012-000: com.adobe.livecycle.generatepdf.client.ConversionException: ALC-PDG-010-012-PDFMaker reported an error while printing the document.
at com.adobe.pdfg.BMCCaller.checkResult(BMCCaller.java:358)
at com.adobe.pdfg.Native2PdfCaller.callNativeBMC(Native2PdfCaller.java:788)
at com.adobe.pdfg.Native2PdfCaller.createPDF(Native2PdfCaller.java:298)
at com.adobe.pdfg.GeneratePDFImpl.createPDFCommon(GeneratePDFImpl.java:342)
at com.adobe.pdfg.GeneratePDFImpl.createPDF(GeneratePDFImpl.java:172)
at sun.reflect.GeneratedMethodAccessor294.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
... 60 more
[5/27/09 12:37:14:695 CDT] 000000f9 SibMessage    W   [:] CWSIV0775W: The creation of a connection for destination Default.Topic.Space on bus IDP_JMS_Bus for endpoint activation [com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation@7cf87cf8 <active=true> <connections={}> <messageEndpointFactory=com.ibm.ejs.container.MessageEndpointFactoryImpl@7aff2ec6> <endpointConfiguration=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl$JmsJcaEndp ointConfigurationImpl@2092727484 <JmsJcaActivationSpecImpl.this=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl@13 28959286 <userName=null> <password=null> <xaRecoveryAlias=null> <destination=topic://adobe_TaskEventTopic?busName=IDP_JMS_Bus> <durableSubscriptionHome=null> <destinationType=javax.jms.Topic> <messageSelector=null> <acknowledgeMode=Auto-acknowledge> <subscriptionDurability=NonDurable> <shareDurableSubscriptions=InCluster> <clientId=null> <subscriptionName=null> <maxBatchSize=1> <maxConcurrency=10> <busName=IDP_JMS_Bus> <shareDataSourceWithCMP=false> <targetTransportChain=null> <readAhead=Default> <target=null> <targetType=BusMember> <targetSignificance=Preferred>]>]> <endpointInvoker=com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl@7cea7cea> <workManager=com.ibm.ejs.j2c.work.WorkManagerImpl@61246124> <endpointMethodTransactional=false> <remoteConnection=null> <remoteDestination=true> <timer=java.util.Timer@7d627d62>] failed with exception com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus IDP_JMS_Bus running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=IDP_JMS_Bus, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..
Thanks and Regards
Aditya Marla

Multiple consumers for AQ-Adpater

Hi,
I want to use a generic queue that will be used by multiple BPEL process. Is there was to specify the channel rule OR AQ-adapter rule so that a content based routing can be done to specific BPEL processes. What are the different options that Adapters provide to achieve this? Is there a concept of dead letter channel/queue for the messages not satisfying any rules?
Thanks,.
Anil

Thanks for info. Where do I set the property or the header variable for a JMS message in an adapter ?
Should I set it using the adapter tab in invoke OR use the property tab in the adapter partnerlink when sending out the message?
I have set the following in the invoke before producing the message and dropping on the queue
<invoke name="Invoke_1" partnerLink="adapt"
portType="ns1:Produce_Message_ptt"
operation="Produce_Message"
inputVariable="Invoke_1_Produce_Message_InputVariable"
bpelx:inputHeaderVariable="Sender"/>
On the receive side I have the message selector configured for the adapter as follows:
<jca:operation
ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec"
DestinationName="dattjndi"
UseMessageListener="false"
MessageSelector="Sender=AdaptationRequest"
PayloadType="TextMessage"
OpaqueSchema="false" >
</jca:operation>
Where AdaptationRequest is the value for the Sender variable which will be used to filter the message. But this does not work. the messages are still not consumed. What could be the problem?
Thanks,
Anil

Messages stuck in Java Queues

I am running PI7.0 SP10 on a MCOD system running ECC6.0 and EP.
We had an issue last week on our Production system where the Java Stack went down, and when the system came back up, we cleared the issues in SMQ1, SMQ2 and SM58 and now we have over two hundred messages stuck in the java queues.
There is nothing locked in SM13, in sxmb_moni all the messgaes are successfully processed... In the RWB the status of the messages are "To be delivered".
I have tried reactivating the adapters but this has not worked.
The queues can be seen in the http://host.fqdn:5<SYSNO>00/MessagingSystem/monitor/systemStatus.jsp
specifically : File_http://sap.com/xi/XI/SystemRecv
and
SOAP_http://sap.com/xi/XI/SystemRecv
where the "isStarted" is set to false, where all the others are true...
How can I go about starting these and processing the backlog of messages??
I have searched OSS, SDN and SAPFans but had not luck!
I have subsequently done a full cache refresh and CPACache refresh but this has not helped.
There are no locked users (XI/PI users) holding this up!

Ok,
It seems to be ok, the return can be http 200 or http 500.
The Soap and File are destinations, ok.
The messages are with status "delivering" on rwb... really, increasing the number of threads will not solve this...
I don't have access to visual admin (only basis team can access it here). I thought it could be something wrong with destination (but you already checked it)... so, the only thing can be done is to find in visual admin somewhere about system properties, conection parameters searching for something wrong there... here are our parameters if you would like to find something (sorry for the size of message)...
AFW.Call.maxConsumers 10
AFW.Recv.maxConsumers 5
AFW.Rqst.maxConsumers 10
AFW.Send.maxConsumers 5
BC_http://sap.com/xi/XI/System.Call.maxConsumers 20
BC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
BC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
BC_http://sap.com/xi/XI/System.Send.maxConsumers 10
BcAdapter.Call.maxConsumers 10
BcAdapter.Recv.maxConsumers 5
BcAdapter.Rqst.maxConsumers 10
BcAdapter.Send.maxConsumers 5
CIDXAdapter.Call.maxConsumers 10
CIDXAdapter.Recv.maxConsumers 5
CIDXAdapter.Rqst.maxConsumers 10
CIDXAdapter.Send.maxConsumers 5
CIDX_http://sap.com/xi/XI/System.Call.maxConsumers 20
CIDX_http://sap.com/xi/XI/System.Recv.maxConsumers 10
CIDX_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
CIDX_http://sap.com/xi/XI/System.Send.maxConsumers 10
EOIO.lockTimeout 5
File_http://sap.com/xi/XI/System.Call.maxConsumers 20
File_http://sap.com/xi/XI/System.Recv.maxConsumers 10
File_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
File_http://sap.com/xi/XI/System.Send.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Call.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Send.maxConsumers 10
JMS_http://sap.com/xi/XI/System.Call.maxConsumers 20
JMS_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JMS_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JMS_http://sap.com/xi/XI/System.Send.maxConsumers 10
JPR.Call.maxConsumers 10
JPR.Recv.maxConsumers 5
JPR.Rqst.maxConsumers 10
JPR.Send.maxConsumers 5
MPA.Call.maxConsumers 10
MPA.Recv.maxConsumers 5
MPA.Rqst.maxConsumers 10
MPA.Send.maxConsumers 5
Mail_http://sap.com/xi/XI/System.Call.maxConsumers 20
Mail_http://sap.com/xi/XI/System.Recv.maxConsumers 10
Mail_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
Mail_http://sap.com/xi/XI/System.Send.maxConsumers 10
Marketplace_http://sap.com/xi/XI/System.Call.maxConsumers 20
Marketplace_http://sap.com/xi/XI/System.Recv.maxConsumers 10
Marketplace_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
Marketplace_http://sap.com/xi/XI/System.Send.maxConsumers 10
RFC_http://sap.com/xi/XI/System.Call.maxConsumers 20
RFC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RFC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RFC_http://sap.com/xi/XI/System.Send.maxConsumers 10
RNIF11Adapter.Call.maxConsumers 20
RNIF11Adapter.Recv.maxConsumers 10
RNIF11Adapter.Rqst.maxConsumers 20
RNIF11Adapter.Send.maxConsumers 10
RNIF11_http://sap.com/xi/XI/System.Call.maxConsumers 20
RNIF11_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RNIF11_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RNIF11_http://sap.com/xi/XI/System.Send.maxConsumers 10
RNIFAdapter.Call.maxConsumers 10
RNIFAdapter.Recv.maxConsumers 5
RNIFAdapter.Rqst.maxConsumers 10
RNIFAdapter.Send.maxConsumers 5
RNIF_http://sap.com/xi/XI/System.Call.maxConsumers 20
RNIF_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RNIF_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RNIF_http://sap.com/xi/XI/System.Send.maxConsumers 10
SOAP_http://sap.com/xi/XI/System.Call.maxConsumers 20
SOAP_http://sap.com/xi/XI/System.Recv.maxConsumers 10
SOAP_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
SOAP_http://sap.com/xi/XI/System.Send.maxConsumers 10
bulkCommit.threshold 100
cluster.timeout 60000
connection.0.ackListener null
connection.0.exceptionListener localejbs/AFWListener
connection.0.jms.messageSelector null
connection.0.jms.profile null
connection.0.jms.provider null
connection.0.jms.queue null
connection.0.messageListener localejbs/AFWListener
connection.0.name AFW
connection.0.pollAttempts 60
connection.0.pollInterval 60000
connection.1.ackListener localejbs/MarketPlaceAdapterListener
connection.1.exceptionListener localejbs/MarketPlaceAdapterListener
connection.1.jms.messageSelector null
connection.1.jms.profile null
connection.1.jms.provider null
connection.1.jms.queue null
connection.1.messageListener localejbs/MarketPlaceAdapterListener
connection.1.name MPA
connection.1.pollAttempts 60
connection.1.pollInterval 60000
connection.2.ackListener null
connection.2.exceptionListener localejbs/JPR
connection.2.jms.messageSelector null
connection.2.jms.profile null
connection.2.jms.provider null
connection.2.jms.queue null
connection.2.messageListener localejbs/JPR
connection.2.name JPR
connection.2.pollAttempts 60
connection.2.pollInterval 60000
connection.3.ackListener null
connection.3.exceptionListener localejbs/RNIFMessageListener
connection.3.jms.messageSelector null
connection.3.jms.profile null
connection.3.jms.provider null
connection.3.jms.queue null
connection.3.messageListener localejbs/RNIFMessageListener
connection.3.name RNIFAdapter
connection.3.pollAttempts 60
connection.3.pollInterval 60000
connection.4.ackListener null
connection.4.exceptionListener localejbs/CIDXMessageListener
connection.4.jms.messageSelector null
connection.4.jms.profile null
connection.4.jms.provider null
connection.4.jms.queue null
connection.4.messageListener localejbs/CIDXMessageListener
connection.4.name CIDXAdapter
connection.4.pollAttempts 60
connection.4.pollInterval 60000
connection.5.ackListener localejbs/BcAdapterListener
connection.5.exceptionListener localejbs/BcAdapterListener
connection.5.jms.messageSelector null
connection.5.jms.profile null
connection.5.jms.provider null
connection.5.jms.queue null
connection.5.messageListener localejbs/BcAdapterListener
connection.5.name BcAdapter
connection.5.pollAttempts 60
connection.5.pollInterval 60000
connection.6.ackListener null
connection.6.exceptionListener localejbs/TestListener
connection.6.jms.messageSelector null
connection.6.jms.profile null
connection.6.jms.provider null
connection.6.jms.queue null
connection.6.messageListener localejbs/TestListener
connection.6.name test
connection.6.pollAttempts 60
connection.6.pollInterval 60000
connection.7.ackListener null
connection.7.exceptionListener localejbs/RNIF11MessageListener
connection.7.jms.messageSelector null
connection.7.jms.profile null
connection.7.jms.provider null
connection.7.jms.queue null
connection.7.messageListener localejbs/RNIF11MessageListener
connection.7.name RNIF11Adapter
connection.7.pollAttempts 60
connection.7.pollInterval 60000
connections (name=AFW, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=MPA, messageListener=localejbs/MarketPlaceAdapterListener, exceptionListener=localejbs/MarketPlaceAdapterListener, ackListener=localejbs/MarketPlaceAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=JPR, messageListener=localejbs/JPR, exceptionListener=localejbs/JPR, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=RNIFAdapter, messageListener=localejbs/RNIFMessageListener, exceptionListener=localejbs/RNIFMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=CIDXAdapter, messageListener=localejbs/CIDXMessageListener, exceptionListener=localejbs/CIDXMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=BcAdapter, messageListener=localejbs/BcAdapterListener, exceptionListener=localejbs/BcAdapterListener, ackListener=localejbs/BcAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=test, messageListener=localejbs/TestListener, exceptionListener=localejbs/TestListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)(name=RNIF11Adapter, messageListener=localejbs/RNIF11MessageListener, exceptionListener=localejbs/RNIF11MessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)
debug HTTP
failover.reassignOnNodeLoss true
initial.delay 0
jdbc.autoConfigure false
jdbc.datasource jdbc/SAP/BC_XI_AF_MSG
jdbc.dbProductName ORACLE
jdbc.substituteEmptyString true
jdbc.supportsOpenSQL true
jdbc.supportsScrollableResultSet false
jms.0.dmq SonicMQ.deadMessage
jms.0.messageLengthKey message_length
jms.0.password ********
jms.0.provider
jms.0.url
jms.0.username
monitoring.displayDefault fromParty, toParty, status, timesFailedRetries, sentRecvTime
persistMessageRemover.checkInterval 1440
proxy.password ********
proxy.user
reassignCheck.waitTime 30
ssl.httpsHandler iaik.protocol.https.Handler
ssl.securityProvider iaik.security.provider.IAIK
ssl.serverNameCheck false
ssl.trustedCACerts.viewName TrustedCAs
startup.delay 0
syncMessageRemover.checkInterval 60
syncMessageRemover.messageCount 1000
syncMessageRemover.removeBody true
system.deafaultMaxConsumersPerQueue 10
system.failNonDelivered false
system.message.lazyRead true
system.node 23654950
system.queueConsumerThreadPoolSize 0
system.statusLog System,Send,Recv,Call,Rqst
system.transactionManager ts
test.Call.maxConsumers 20
test.Recv.maxConsumers 10
test.Rqst.maxConsumers 20
test.Send.maxConsumers 10
throughputStatistics enabled
regards
roberti

JMS Adapter Message Selector Problem...

Hi
I have set the following in the invoke before producing the message and dropping on the queue
<invoke name="Invoke_1" partnerLink="adapt"
portType="ns1:Produce_Message_ptt"
operation="Produce_Message"
inputVariable="Invoke_1_Produce_Message_InputVariable"
bpelx:inputHeaderVariable="Sender"/>
On the receive side I have the message selector configured for the adapter as follows:
<jca:operation
ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec"
DestinationName="dattjndi"
UseMessageListener="false"
MessageSelector="Sender=AdaptationRequest"PayloadType="TextMessage"
OpaqueSchema="false" >
</jca:operation>
Where AdaptationRequest is the value for the Sender variable which will be used to filter the message. But this does not work. the messages are still not consumed. What could be the problem?
Thanks,
Anil

did you check the message selector section on
http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/Message.html
explains all the operators you can use and the correct syntax. Make a note of the case sensitivity.

EJB3 MessageDriven not de-queueing the message

Hi,
I've got a problem setting up a MessageDriven Bean (EJB3) on default JMS Queue in OC4J (10130).
If I open up the enterprise manager, I can see that the bean has been deployed, I can see the Queue contains messages, but it seems like the messages are not being read.
If I look at the MDB properties in the em, the only property that disturbs me is the destination type property, which seems unavailable, however I did configure it in the @MessageDriven annotation properties.
What am I doing wrong here?
Kind regards,
Bert
Here's my code:
Message Driven Bean
@MessageDriven(
          activationConfig = {
               @ActivationConfigProperty(propertyName="connectionFactoryJndiName",propertyValue="jms/RefacQueueConnectionFactory"),
               @ActivationConfigProperty(propertyName="destinationName",propertyValue="jms/MyQueue"),
               @ActivationConfigProperty(propertyName="destinationType",propertyValue="javax.jms.Queue"),
               @ActivationConfigProperty(propertyName="messageSelector",propertyValue="RECIPIENT = 'MDB'") } )
public class TestMDB implements MessageListener, TimedObject {
          public void onMessage(Message message) {
                    System.out.println("onMessage() - " + message);
          public void ejbTimeout(Timer timer) {
               System.out.println("EJB 3.0: Timer with MDB");
               System.out.println("ejbTimeout() called at: " + new Date(System.currentTimeMillis()));
Client putting a test message on the queue
          ConnectionFactory factory = (ConnectionFactory) context.lookup("jms/RefacQueueConnectionFactory");
          Queue queue = (Queue) context.lookup("jms/MyQueue");
          Connection connection = factory.createConnection();
          Session session = connection.createSession(true, Session.AUTO_ACKNOWLEDGE);
          MessageProducer sender = session.createProducer(queue);
          connection.start();
          System.out.println("Sending Message to the queue");
sender.send(session.createTextMessage("HelloWorld"));
session.commit();
View from the Enterprise manager
Message Driven Bean: "TestMDB"
General
Name "TestMDB"
State Up
Start Time Jul 7, 2006 7:25:40 AM CEST
Messaging Type javax.jms.MessageListener
Transactions Container
Transaction Support NotSupported
Performance
Messages Dequeued 0
Messages Rolled Back 0
Average Message Processing Time (seconds) 0.00
Number of Available Instances 0
Number of Used Instances 0
Message Properties
Uses Resource Adapter as Listener False
Destination Type Unavailable
Destination JNDI Location jms/MyQueue
Connection Factory JNDI Location jms/RefacQueueConnectionFactory
Subscription Type NonDurable
Subscription Name Unavailable
Listener Threads 1
Message Selector RECIPIENT = 'MDB'
Acknowledgement Mode AUTO_ACKNOWLEDGE

Well, I got the problem myself.
Just for the record, here's what I did wrong:
I forgot to put the RECIPIENT parameter on the message before sending it to the destination
Message message = session.createMessage();
message.setStringProperty("RECIPIENT", "MDB");
publisher.send(message);
I have no idea if this property is JMS spec, or Oracle specific... in my previous experience with jms, I never had to set this property (if I recall correctly). (this is the first time I'm using jms in an OC4J container.)
grtz

MessageSelector

Similar Messages

Maybe you are looking for