Sensors - Configuring JMS queue properties at runtime through console

Hi,
Kindly guide me with configuring of the JMS queue name at runtime for a JMS sensor configured on an activity in Jdeveloper's BPEL process. I have created a JMS sensor but i want to change the queue name at runtime without rebuilding i.e if possible through console. Does oracle 10g SOA suite gives ant such facility where by we can configure sensor related properties from console ??
NOTE: i m creating NON-BAM JMS and custom sensors

Hi,
This is not supported at the moment but planned to be added soon.
So right now, you have to redeploy the process in case of a sensor/
sensor action modification.
Regards,
Ralf

Similar Messages

How to configure JMS queue on OC4J server. Development in JDeveloper 10G

Hi there,
I have to configure a JMS for an Asynchronous process in my Application which will be running in Oracle 10G Application Server. Development Environment is Oracle JDeveloper 10G.
I am facing a problem on how to configure JMS queue.
Steps Followed are:
in the <JDevloperHome>/j2ee/home/config
1. Made the new queue and connection factory's JMS entry in jms.xml.
2. Specifed the queue in oc4j-connectors.xml.
3. played around with application.xml
and tried all combinations, but the message producer always failed to lookup the queue.
Need help on the steps to follow so that the producer can post the message in the queue.
Also please help how to configure the MDB to listen to the queue.
Thanx and Regards
Subham

If you were dealing with Oracle 10g app server as opposed to standalone, I might be better able to help you.
One thing though, when you are configuring your MDB in the orion-ejb-jar.xml file, do not forget to specify attribute listener-threads, otherwise no matter how many beans you have in your MDB pool, only one bean will be listening to the queue. Many listener-threads equal to max number of beans in pool.

Recieve/Read Messages from JMS Queue through ALSB

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

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

ODI 11g : JMS Queue XML Data Server creation

Hi Everybody,
I am facing a problem while i am trying to create a JMS Queue XML data server in ODI 11g. I have
the following details of the queue.
QueueManager=xxx;
TransportType=1;
HostName=ab.cde.fe.com;Port=77777;
Channel=CLIENT.TO.xxx1
destination name : SU.BH.RAJY.OTI.UPDATE_ITEM_RESPONSE.01
user : xyz
password : 123
I have sussefully created an jms datasouce in weblogic name 'eis/jms/abc' and also I have successfully
retrived the xml message from queue in BPEL
(using a jms adapter where
JMS Provider : Third Party,
Jms Provider Jndi Name -eis/jms/abc,
Operation name : consume_message,
destinamtion name is queue:///SU.BH.RAJY.OTI.UPDATE_ITEM_RESPONSE.01?targetClient=1).
But the new reqirement is to retive the xml data in ODI using "JMS Queue XML data server".I have tried
several ways(reading from internet) but failed to configure physical dataserver and reverse the xml message.
Also failed to understand properly the oracle post (http://docs.oracle.com/cd/E21764_01/integrate.1111/e12644/jms_xml.htm#CHDFCFBI).
Speically this portion "JNDI URL: <JMS_RESOURCE>?d=<DTD_FILE>&s=<SCHEMA>&JMS_DESTINATION=<JMS_DESTINATION_NAME>.".
What will be the "JMS_RESOURCE" in my case.
How can I configure JMS Queue XML?
Please help!
Note : I don't have the XML message structure of the Queue(also DTD file). So , I have to reverse it.
Thanks & Regards,
Subhra
Message was edited by: SubhrajyotiKundu

Hi Everybody,
I am facing a problem while i am trying to create a JMS Queue XML data server in ODI 11g. I have
the following details of the queue.
QueueManager=xxx;
TransportType=1;
HostName=ab.cde.fe.com;Port=77777;
Channel=CLIENT.TO.xxx1
destination name : SU.BH.RAJY.OTI.UPDATE_ITEM_RESPONSE.01
user : xyz
password : 123
I have sussefully created an jms datasouce in weblogic name 'eis/jms/abc' and also I have successfully
retrived the xml message from queue in BPEL
(using a jms adapter where
JMS Provider : Third Party,
Jms Provider Jndi Name -eis/jms/abc,
Operation name : consume_message,
destinamtion name is queue:///SU.BH.RAJY.OTI.UPDATE_ITEM_RESPONSE.01?targetClient=1).
But the new reqirement is to retive the xml data in ODI using "JMS Queue XML data server".I have tried
several ways(reading from internet) but failed to configure physical dataserver and reverse the xml message.
Also failed to understand properly the oracle post (http://docs.oracle.com/cd/E21764_01/integrate.1111/e12644/jms_xml.htm#CHDFCFBI).
Speically this portion "JNDI URL: <JMS_RESOURCE>?d=<DTD_FILE>&s=<SCHEMA>&JMS_DESTINATION=<JMS_DESTINATION_NAME>.".
What will be the "JMS_RESOURCE" in my case.
How can I configure JMS Queue XML?
Please help!
Note : I don't have the XML message structure of the Queue(also DTD file). So , I have to reverse it.
Thanks & Regards,
Subhra
Message was edited by: SubhrajyotiKundu

OSB 10.3 JMS queue problem: JMSCorrelationID is null

Hi everybody,
I am new to OSB/ALSB, and need some help regarding JMS message handling. I am trying to put some input data into a JMS queue( say, reqQueue) and to get the response from another JMS queue(say resQueue). My architecture is:
OSB proxy service->OSB business service->JMS queue(reqQueue)->BPEL process(through JMS adapter) ->JMS queue(resQueue)->OSB business service->OSB proxy service.
I have used JMSCorrelationID for response correlation. but my problem is that when I am trying to test the service from proxy service, I am getting the JMSCorrelationId as null in BPEL process as well as in the weblogic server JMS log, and as I am getting the CorrelationId as null, I am unable to correlate the response, so I am not getting any response.
This is urgent, please help me as soon as possible as possible.
Thanks in advance.
Joy

Sovled it..
OSB 10.3 JMS queue problem: JMSCorrelationID is null

Configuring JMS in Production mode

Hi all
I need to configure JMS queue and i tried this flow, correct me if i am wrong
1.persistent store
2.JMS server
3.JMS module
3.1.Connection factory with default targetting
3.2 Queue with soa_server1 as target.
I am getting a error while creating persistent store when activating changes in admin console.
"FujitsuJMSFileStore" is the filestore name
Server Log is
<Warning> <Management> <BEA-141197> <The deployment of FujitsuJMSFileStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:182)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: [Store:280044]The file store directory "/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore" does not exist
at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:173)
at weblogic.store.io.file.StoreDir.createDirectory(StoreDir.java:226)
at weblogic.store.io.file.StoreDir.checkOK(StoreDir.java:202)
at weblogic.store.io.file.Heap.<init>(Heap.java:185)
at weblogic.store.io.file.Heap.<init>(Heap.java:163)
Truncated. see log file for complete stacktrace
>
<Apr 30, 2012 2:48:04 AM PDT> <Critical> <Management> <BEA-141190> <The commit phase of the configuration update failed with an exception:
weblogic.descriptor.DescriptorUpdateFailedException: one or more registered update listeners reported activation problems.
The following failures occurred:
-- The following failures occurred:
weblogic.management.DeploymentException:
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:182)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.io.IOException: [Store:280044]The file store directory "/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore" does not exist
at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:173)
at weblogic.store.io.file.StoreDir.createDirectory(StoreDir.java:226)
at weblogic.store.io.file.StoreDir.checkOK(StoreDir.java:202)
at weblogic.store.io.file.Heap.<init>(Heap.java:185)
at weblogic.store.io.file.Heap.<init>(Heap.java:163)
at weblogic.store.io.file.FileStoreIO.<init>(FileStoreIO.java:79)
at weblogic.store.xa.PersistentStoreManagerXA.makeXAStore(PersistentStoreManagerXA.java:51)
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:178)
... 21 more
weblogic.descriptor.BeanUpdateFailedException: The following failures occurred:
weblogic.management.DeploymentException:
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:182)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.io.IOException: [Store:280044]The file store directory "/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore" does not exist
at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:173)
at weblogic.store.io.file.StoreDir.createDirectory(StoreDir.java:226)
at weblogic.store.io.file.StoreDir.checkOK(StoreDir.java:202)
at weblogic.store.io.file.Heap.<init>(Heap.java:185)
at weblogic.store.io.file.Heap.<init>(Heap.java:163)
at weblogic.store.io.file.FileStoreIO.<init>(FileStoreIO.java:79)
at weblogic.store.xa.PersistentStoreManagerXA.makeXAStore(PersistentStoreManagerXA.java:51)
at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:178)
... 21 more
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:189)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:257)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
Truncated. see log file for complete stacktrace
I tried restarting the admin and SOA server more than twice still i am getting this error .
Thanks in advance
Anand.U

Hi Anand,
here is your error,
*Caused by: java.io.IOException: [Store:280044]The file store directory "/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore" does not exist*
/u105/app/Oracle/Middleware/user_projects/domains/soat_domain/FujitsuJMSFileStore does not physically exists on your WLS host as a directory or file system to write to
Or it is not mounted
Or you don't have the permissions to write in it.
For detailed explanation about how to configure JMS queue,can be obtained from the below link
http://middlewaremagic.com/weblogic/?p=1987
Regards
Fabian

Creating XML string to be pushed into a JMS queue

Hello All
I am trying to pass the following XML string into a sender obj, however, I am not sure how it is supposed to be done, with the right escape sequencing.
message.setText("<rawData><Name="Mike"></Name><Value="200"></rawData>");
Please guide me.
Thanks,
AJ

Login User should have the Admin privilege, Otherwise it is not possible to post data manually into the JMS Queue.
Log into weblogic Console > click on JMS Module > <select the JMSModule where the Queue resides : e.g SOAJMSModule> >Select the Queue > Monitoring > Check the Box > click on "Show Message" > New > Post the data in "Body" section.
Or, you can create another BS in OSB, pointing to that JMS Queue(using Input.xsd) . then execute the BS using your Input.xml

Configuration for JMS Adapter Sensor action and JMS Queue sensor action..!!

Hi,
Id like my BPEL process to send an XML message to JMS on Websphere,I was able to do this through a JMS adapter.But I would more like to add sensors into my process which would really do the same thing - send an XML message to JMS Q.
Now I understand that there are two ways to do this,JMS Queue and JMS Adapter - thorugh bpel sensor action.
I am able to use JMS Queue and it works fine , but adds its own xml tags to the message,Is there any way I could send only my xml payload as a message to the queue??
Also could any1 tell me what is the configuration for JMS Adapter sensor action?
Any suggestions how do I go about it??

Hey Anirudh,
Thanx for the response :-)
All these hold good when I have an AQ adaptor right,But the thing is I want to send a message to a 'JMS' queue with out actually using an adapter configuration wizard and everythng..So I resolved to JMS queue Sensor action..Heres the xml snippet from the sensorAction.xml files which is generated..
<actions targetNamespace="http://xmlns.oracle.com/Test_JMS_Logging" xmlns="http://xmlns.oracle.com/bpel/sensor" xmlns:tns="http://xmlns.oracle.com/Test_JMS_Logging" xmlns:pc="http://xmlns.oracle.com/bpel/sensor">
<action name="JMS_LogEntry" publishName="" publishType="JMSQueue" enabled="true" filter="" publishTarget="jms/L_Queue">
<property name="JMSConnectionFactory">jms/L_QueueCF</property>
<sensorName>ActivitySensor_JMS</sensorName>
</action>
</actions>
This works grt and adds messages to the queue..But adds its own header info according to the sensor.xsd loacted at the Oracle_home\bpel\system\xmllib\ folder.
Right now the XML message added to the Queue is:-
<actionData xmlns="http://xmlns.oracle.com/bpel/sensor">
<header>
<sensor sensorName="ActivitySensor_JMS" classname="oracle.tip.pc.services.reports.dca.agents.BpelActivitySensorAgent" kind="activity" target="AddLEntr
y" xmlns:pc="http://xmlns.oracle.com/bpel/sensor" xmlns:ns2="http://www.ulrhome.com/2008/10/L_Entry" xmlns:tns="http://xmlns.oracle.com/Test_JMS">
<activityConfig evalTime="completion">
<variable outputDataType="string" outputNamespace="http://www.w3.org/2001/XMLSchema" target="$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName"/>
</activityConfig>
</sensor>
<instanceId>950016</instanceId>
<processName>Test_JMS</processName>
<processRevision>v2009_04_15__40833</processRevision>
<domain>default</domain>
<timestamp>2009-04-15T11:21:23.596-04:00</timestamp>
<midTierInstance>app01.ulrhome.com:9700</midTierInstance>
</header>
<payload>
<activityData>
<activityType>scope</activityType>
<evalPoint>completion</evalPoint>
<durationInSeconds>0.011</durationInSeconds>
<duration>PT0.011S</duration>
</activityData>
<variableData>
<dataType>12</dataType>
<data>
<ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
</data>
<queryName/>
<target>$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName</target>
<updaterName>AddL_Entry</updaterName>
<updaterType>scope</updaterType>
</variableData>
</payload>
</actionData>
My requirement is that I need to add a sensor to the BPEL process which posts 'Only my payload message to the JMS queue'..
What I would want the message in the Queue to be is : -
<data>
<ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
</data>
Also while creating a Sensor action I get another option as JMS Adaptor,I am not sure of what value to type in this wizard..Heres what I keyed in..M sure this is not right..Cos it dosnt work :-)
<action name="SensorAction_JMS" publishName="" publishType="JMSAdapter" enabled="true" filter="" publishTarget="jms/LoggingQueue">
<property name="JMSConnectionName">Log</property>
</action>
</actions>
Could any 1 tel me what values are the right values..And does JMS Adapter mean that I have to create a JMS Apator in the project and give that connection name as a Value..
I am not finding sufficiant Documentation for 'JMS Adapter' so M clueless and right now any help will be appriciated :-)
Regards,
Akshatha.

Configure backout queue and Dead letter queue in weblogic JMS provider

Hi,
How to configure the JMS backout queue and dead letter queue in weblogic JMS provider in weblogic application server console?
Any links or documents are highly appreciated.
Thanks.

Thanks anon. When i say backout message the poisonous message , A poison message is one which cannot be processed by a receiving MDB application. If a poison message is encountered, the JMS MessageConsumer and ConnectionConsumer objects can requeue it according to two queue properties, BOQUEUE, and BOTHRESH.
Normally this happens in the websphere MQ . Where we will configure the backout queue and dead letter queue.
The dead letter queue was always used in MQSeries (the last time I used MQ) to store messages that arrived at the queue manager but the queue didn't exist. For eample, if the message was address to queue manager X and queue Y, it would arrive via a channel at manager X. If the receiver channel discovered there was no queue Y, it would be placed in the dead letter queue.
The backout queue, on the other hand, is more of an application-level thing (at least in terms of MQ). When an MQ client cannot process the message for some reason, it can back it out for later processing (back to it's original queue).If it's backed out too many times (the threshold can be configured), it gets moved to the backout queue.
The Dead Letter Queue behaves the same as a Backout. I treat the Dead Letter Queue as the Crematorium for messages that cannot be recovered in the Error or Backout queues and have some last, non-business specific data that need be collected. Once the info is captured, the message is put down for good. Backout is good for analyzing messages for data that may need to be recovered to completely reprocess or be sent back to an application area for them to decision on.
How we configure these in weblogic server both Backout and Deadletter queue , whether this is a simple queue in which we will set the error destination in case of any poisonous message so that it will logged in those queue?
Thanks.

Alsb trying to reach weblogic jms queues through VIP

Hi,
I have jms queues created in wLS. ALSB business service which puts the message into the queue .
ALSB and WLS are in 2 different boxes. When the end pointas follows jms://hostname:portnumber/connection factory/JNDI name is given the service is able to reach the Q.
The problem arises when VIP is used to connect to any of the queues in the box. the jms protocol is getting converted to "t3" protocol which is not understood by VIP and hence resulting in connection timed out exception .
Can anybody please help me to access jms queues through VIP from ALSB service .
Thanks in Advance ,
LKV

the jms protocol is getting converted to "t3" protocol which is not understood by VIP and hence resulting in connection timed out exception . Virtual IP as such doesnt influence anything...what it matters is what is listening at the Virtual IP, If you have configured weblogic server listen thread at this port then it should be able to understand t3.. Weblogic server's listen thread can interpret all supported protocol's ( http, t3, iiop, ldap etc) on its listen port...
So check at your wls side whether the server is listening at virtual ip and port. If you have firewall between alsb and wls then it could be an issue as firewalls can block certain protocols on an opened port..

Configuring error queue through script

Hello,
I have two queues where the second is the error queue for the first. I can set everything manually through console but I need to create a python script that will do it automatically.
I looked up some information on internet and I was able to create the queues:
<pre>
def create_Queue( moduleName, queueName, queueJNDIName, subDeployementName):
print "creating Queue named " + queueName
cd( '/JMSSystemResources/' + moduleName + '/JMSResource/' + moduleName)
theBean = cmo.lookupQueue( queueName)
if theBean == None:
cmo.createQueue( queueName)
else :
print "Queue already created ..."
cd("/JMSSystemResources/" + moduleName + "/JMSResource/" + moduleName + "/Queues/" + queueName)
set( "Name", queueName)
set( "SubDeploymentName", subDeployementName)
set( "JNDIName", queueJNDIName)
</pre>
but I don't know how to set up the Error Queue. I tried:
<pre>
prefix = "/JMSSystemResources/" + JMSModuleName + "/JMSResource/" + JMSModuleName + "/Queues/"
cd(prefix + "first")
set("ErrorDestination", prefix + "second")
</pre>
but without success. I don't know if I am trying something completely wrong or if just the name of the attribute is wrong ...

transferModule = cmo.createJMSSystemResource('TransferModule');
#optionally target
#transferModule.getTargets().append(aserver);
jmsResource = transferModule.getJMSResource();
jmsResource.createQueue('TransferQueue');
transferQueue = jmsResource.lookupQueue('TransferQueue');
jmsResource.createQueue('ErrorQueue');
errorQueue = jmsResource.lookupQueue('ErrorQueue');
transferQueue.setJNDIName('jms/TransferQueue');
#transferQueue.setSubDeploymentName('TransferSubDeployment');
transferQueue.getDeliveryParamsOverrides().setRedeliveryDelay(100);
transferQueue.getDeliveryFailureParams().setRedeliveryLimit(5);
transferQueue.getDeliveryFailureParams().setExpirationPolicy('Redirect');
transferQueue.getDeliveryFailureParams().setErrorDestination(errorQueue);What you also can do is configure your JMS environment using the console.
While you are doing this, you can record your modifications.
The record button is located in the top middle of the console.

Runtime configuring JCaps Environment properties

Hey hi,
Can any one suggest a way for configuring the JCaps environment runtime through properties file or XML file.
Example :
Configuring
1.SQLServer properties
2. Email properties.

Assuming you are talking about Classic Repository Based CAPS 6, all details can be found at: http://wikis.sun.com/download/attachments/38767325/JavaCAPS6+Application+Configuration.pdf.
Essentially - first you create (extract) the configuration, before you change it and import it. Note that it could be a good idea to remove any SJMQ configuration from the file before importing it - or explicitly set the authentication information in the file, since the existing user/pwd will not be properly generated. In addition if you use JMSJCA options in the Connectivity Map (such as redelivery) they will be superseded if you override the SJMQ information - and thus not work at all.
Johan

How to configure my JMS QUEUE serve only one message at a time?

Hi All,
I have requirement where I need to develope a JMS QUEUE in weblogic. This MDB has to serve only one message at a time. Is there any way to configure via annotations or in weblogic server settings ?
Any help would be really appreciated...
Thank you,
K.

I'm not aware of any way to configure the max pool size via annotations, you might try posting to the EJB newsgroup (please post back the answer). Of course you can set the size via an EJB descriptor, as per the MDB chapter of the Performance and Tuning guide in the edocs.
By the way, if you have ordered message processing requirements, I highly recommend taking a look at the WebLogic JMS "Unit-of-Order" (UOO) feature as per the UOO chapter of the JMS programmer's guide. For a variety of reasons, the UOO features is often, by far, the best option for handling such requirements. If this feature applies to your use case, then there would be no need to force single threaded message processing in some sort of manual fashion (the feature enforces this for you).
Tom

How to configure a JMS Queue

Hi,
I have an EAR file thai includes an EJB 3.0 module with a MDB. I use a Queue.
This is my code,
@Resource(mappedName = "jms/NotificationQueue")
private Queue notificationQueue;
@Resource(mappedName = "jms/NotificationQueueFactory")
private ConnectionFactory notificationQueueFactory;
public Customer update(Customer customer){
Customer updated = em.merge(customer);
try {
sendJMSMessageToNotificationQueue(updated);
} catch (JMSException ex) {
Logger.getLogger(CustomerSessionBean.class.getName()).log(Level.SEVERE, null, ex);
System.out.println("Customer updated in CustomerSessionBean!");
return updated;
private Message createJMSMessageForjmsNotificationQueue(Session session, Object messageData) throws JMSException
//Modified to use ObjectMessage instead
ObjectMessage tm = session.createObjectMessage();
tm.setObject((Serializable) messageData);
return tm;
private void sendJMSMessageToNotificationQueue(Object messageData) throws JMSException
Connection connection = null;
Session session = null;
try
connection = notificationQueueFactory.createConnection();
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
MessageProducer messageProducer = session.createProducer(notificationQueue);
messageProducer.send(createJMSMessageForjmsNotificationQueue(session, messageData));
finally
if (session != null)
try
session.close();
catch (JMSException e)
Logger.getLogger(this.getClass().getName()).log(Level.WARNING, "Cannot close session", e);
if (connection != null)
connection.close();
layed inside a stateless EJB 3.0.
And the MDB looks as follow,
@MessageDriven(mappedName = "jms/NotificationQueue", activationConfig = {
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
public class NotificationBean implements MessageListener {
public NotificationBean() {
public void onMessage(Message message)
try
Object msgObj = ((ObjectMessage)message).getObject();
if (msgObj != null)
Customer customer = (Customer)msgObj;
System.out.println("Customer with the following details has been updated:");
StringBuilder sb = new StringBuilder();
sb.append("Customer ID=");
sb.append(customer.getCustomerId());
sb.append(", ");
sb.append("Name=");
sb.append(customer.getName());
sb.append(", ");
sb.append("Email=");
sb.append(customer.getEmail());
System.out.println(sb.toString());
catch (JMSException ex)
Logger.getLogger(NotificationBean.class.getName()).log(Level.SEVERE, null, ex);
I have configured both "jms/NotificationQueue" and "jms/NotificationQueueFactory" inside OC4J server.
But when I try to deploy the EAR file, the server gives me the following error,
Operation failed with error: No destination location set for message-driven bean NotificationBean
How must I do to let the EAR file be deployed?
Thanks in advance
Jose

Mingzhuang
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
Let me know if we are not on same page.
Cheers
Manoj

How toremove messages from JMS Queue?how to configure queue in spring?

Hi
I have Confiured a JMS configaration in spring applicationConfiguaration.xml file
<bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
 <property name="brokerURL" value="tcp://localhost:61616"/>
 <property name="useAsyncSend" value="true"/>
 </bean>
 <bean id="queue" class="org.apache.activemq.command.ActiveMQQueue">
 <constructor-arg value="foo"/>
</bean>
 <bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
 <property name="config" value="classpath:activemq.xml" />
 <property name="start" value="true" />
 
 </bean>
 <bean id="auditInterface"
 class="org.springframework.jms.remoting.JmsInvokerProxyFactoryBean">
<property name="serviceInterface" value="com.infiniti.gpn.auditing.AuditInterface"/>
<property name="connectionFactory" ref="connectionFactory"/>
<property name="queue" ref="queue"/>
</bean>
 <bean id="listenerContainer" class="org.springframework.jms.listener.SimpleMessageListenerContainer">
<property name="connectionFactory" ref="connectionFactory"/>
<property name="destination" ref="queue"/>
<property name="messageListener" ref="auditMessageListener"/>
 </bean>
Sender is sedning messages continusly messages that messages r storing in queue , these r acupying more memory in RAM , due to that jboss is restarting for each request, is there any way to clean up messages in Queue ? if it is there then how will configure that queue in apllicationConfiguaration.xml file?
Thanks in advance
Nara

I suggest posting your question on the [Spring Remoting and JMX forum|http://forum.springframework.org/forumdisplay.php?f=30].

Sensors - Configuring JMS queue properties at runtime through console

Similar Messages

Maybe you are looking for