Remove JMS Queue

          Hi!
          I've managed to create JMS Queues by using JMSServerMBean and JMSQueueMBean.
          I'm trying to remove a JMS queue with the method :
          removeDestination(JMSDestinationMBean)
          but the JMS queue is not removed from the config.xml.
          Any suggestions?
          queueName = My Queue Name
          queueJNDI = My Queue JNDI Name
          JMSServerMBean jmsServerMB =
          (JMSServerMBean)mBeanHome_.getMBean(JMSServer,"JMSServer",SERVER);
          JMSQueueMBean jmsQueueMB =
          (JMSQueueMBean)mBeanHome_.findOrCreateAdminMBean
          (queueName,"JMSQueue",SERVER,jmsServerMB);
          jmsQueueMB.setJNDIName(queueJNDI);
          jmsServerMB.removeDestination(jmsQueueMB);
          -Ami

Hi,
Even i have a similar kind of requirement where in, i want to clear the JMS Queue Message programmatically, on certain condition.
i am using Spring JMS. The JMS Queue has a listener. In the listener we want to clear the Queue contents based upon the condition.
If anybody has any idea about this, please reply back.
Thanks in Advance.
Manjunath.

Similar Messages

How to remove header data from JMS Queue while sending by jms adapter

Hi.
I have a problem regarding the MQ-series JMS adapter.
When writing the file the JMS adaptor putting some additional tags.
Actually we are converting idoc-xml to flat file by using ABAP mapping which is available in SAP document. We are using JMS Receiver adapter, whiel sending flat file to JMS QUEUE, it is displaying some extra xml tags. I think this is the header data available in IDoc XML. Can any body help me in removing header data.
There must be some way for XI's JMS adaptor to not include these information.
My example looks like this:
RFH Ø
¸MQSTR
¸ " is junk that I really dont need in the file.
How can you setup the JMS adaptor not to put in these information?
Thanks & Regards,
Madhusudhan

not related

Weblogic 10.3 Not Removing Expired Messages from JMS Queues

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

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

How to remove 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

Hi,
Even i have a similar kind of requirement where in, i want to clear the JMS Queue Message programmatically, on certain condition.
i am using Spring JMS. The JMS Queue has a listener. In the listener we want to clear the Queue contents based upon the condition.
If anybody has any idea about this, please reply back.
Thanks in Advance.
Manjunath.

JMS Queue Works in JDeveloper 10g, but not in Oracle 10g AS

Hello --
I have set up a JMS Queue on my local OC4J included with JDeveloper. I added my ConnectionQueueFactory and ConnectionQueue to the JMS.XML file in my environment. Everything works the way it should using JDeveloper with the embedded OC4J.
As soon as I deploy the application to Oracle Application Server, for some reason my MailSender Message Driven Bean cannot take delivery of the message. I don't know what I could be doing wrong but my JMS.XML file on the Application Server has been updated with the same ConnectionQueue information that is on my local JMS.XML file. In my log file I can see that the message is being posted to the queue, just no delivery.
If anyone out there has a suggestion I would appreciate it. This is my first attempt at ever using JMS.
Thanks,
Frank

Willy_B wrote:
I removed the one that was listed, thinking that it was implicit to that line. BUT of course, I just went back and removed EVERY empty line, even between the comments and all...and it worked.
So the lesson here is that PL/SQL could care less about white space, but SQLPlus is picky....
Thanks. :)Exactly. And I have to make note of that in my written procedure for restoring some of our test databases from a cold backup of production. Turns out the control file trace script (backup controlfile to trace) inserts a blank line ... then sqlplus chokes on it when executing ..

MDBs in 9.1 continue to consume JMS queues even after being deleted

We have an MDB application that reads a batch message off of a JMS queue, archives it in a database, parses the batch message into individual messages and writes them onto other JMS queues to be consumed by another application. Everything was running fine in Weblogic 8.1.5. However, due to problems with XA drivers and the MSDTC(predictable SQL server crashes), we decided to upgrade to Weblogic 9.1 to take advantage of the LLR option.
 First, we had an issue where our MDBs were causing the following exception:
 ####<May 26, 2006 7:42:12 PM EDT> <Error> <JMX> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686932991> <BEA-149500> <An exception occurred while registering the MBean null.
 java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : com.bea:ServerRuntime=wltest1,MessageDrivenEJBRuntime=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,Name=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,ApplicationRuntime=DataBrokerEAR1_2,Type=EJBPoolRuntime,EJBComponentRuntime=DataBrokerEJB new:[email protected] existing weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl@7db003
 at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:146)
 at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:133)
 at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:86)
 at weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$1.registered(RuntimeMBeanAgent.java:104)
 at weblogic.management.provider.internal.RegistrationManagerImpl.invokeRegistrationHandlers(RegistrationManagerImpl.java:205)
 at weblogic.management.provider.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:85)
 at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:320)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:257)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:222)
 at weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl.<init>(EJBPoolRuntimeMBeanImpl.java:32)
 at weblogic.ejb.container.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:49)
 at weblogic.ejb.container.manager.MessageDrivenManager.initialize(MessageDrivenManager.java:503)
 at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:120)
 at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:146)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManager(MessageDrivenBeanInfoImpl.java:1481)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createDDMDManagers(MessageDrivenBeanInfoImpl.java:1378)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onDDMembershipChange(MessageDrivenBeanInfoImpl.java:1285)
 at weblogic.jms.common.CDS$DD2Listener.listChange(CDS.java:454)
 at weblogic.jms.common.CDSServer$DDHandlerChangeListener.statusChangeNotification(CDSServer.java:167)
 at weblogic.jms.dd.DDHandler.callListener(DDHandler.java:318)
 at weblogic.jms.dd.DDHandler.callListeners(DDHandler.java:344)
 at weblogic.jms.dd.DDHandler.run(DDHandler.java:282)
 at weblogic.jms.common.SerialScheduler.run(SerialScheduler.java:37)
 at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
 >
 ####<May 26, 2006 7:42:13 PM EDT> <Info> <EJB> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686933069> <BEA-010060> <The Message-Driven EJB: RhapsodyMDB has connected/reconnected to the JMS destination: weblogic.jms.DMB_BEAN_QUEUE.>
 
 Generally this happend after there were cluster communication issues. Multi-cast messages were lost and our MDB reconnects to the JMS queues as indicated by the below log:
 ####<May 30, 2006 5:19:06 PM EDT> <Info> <EJB> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '54' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1149023946040> <BEA-010060> <The Message-Driven EJB: DataBrokerMDB has connected/reconnected to the JMS destination: weblogic.jms.PHINMS_DMB_QUEUE.>
 ####<May 30, 2006 5:19:10 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023950228> <BEA-000112> <Removing RAPBEA3S jvmid:720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S from cluster view due to timeout.>
 ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951009> <BEA-000115> <Lost 2 multicast message(s).>
 ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951040> <BEA-000111> <Adding RAPBEA3S with ID 720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S to cluster: DMBstg_cluster view.>
 
 This would cause the queues to eventually have hundreds of consumers and cause the server to fail.
 Basically, it seems as though the MDBs that are supposed to stop continue and attempt to process, while new threads connect to the JMS queues.
 I tried undeploying our application and deleted it from the configuration. However there were consumers still on the respective queues and when I sent messages, I got an error indicating a "Class Not Found exception" due to the fact that the EJB was undeployed and deleted from the configuration, however the MDB component was not and continued to listen for messages. In 8.1.5, as soon as the application was undeployed, there were zero consumers on the JMS queues.
 I have read the posts about a soon to be released fix that would have the MDBs connect only to the queues locally and not go out the the cluster. Would this fix my issue?
 Is there something in the deployment descriptor to configure that will cause it to disconnect and now spawn so many consumers to the JMS queues?
 Why is it that the number of MDB consumers on the JMS queues stayed static in 8.1.5, but they are erratic in 9.1 even after I set our 9.1 server to use the 8.1.5 execute queue policy. Help would be much appreciated.

I recommend contacting customer support. There's a known problem with MDBs listening to distributed destinations that are local to the same cluster as the MDB, you're problem may be related (the clue is that the stack trace contains jms.dd.DDHandler.callListeners()). The problem is that the MDB connects to all physical queues in a distributed destination rather than just the local queue.
 Tom

Message Driven bean: message always removed from queue

We use MDB to dequeue messages from database queue (AQ) and want to handle errors: if the transaction rolls back, message should have retry_count updated and after defined retries should move to exception queue.
The problem is, that with all combinations of transactions settings, the message is removed from queue before onMessage is called. If I use Container managed transactions with Mandatory transaction attribute, call to setRollbackOnly fails with message "java.lang.IllegalStateException: Cannot call setRollbackOnly() current thread is NOT associated with a transaction."
How can I write a MDB, which can commit or rollback message depending on whether exception is or is not thrown? I use JDev 10.1.3.
Thanks,
Viliam
Here are my files:
ejb-jar.xml:
<?xml version = '1.0' encoding = 'windows-1250'?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
 <message-driven>
 <description>Message Driven Bean</description>
 <display-name>SendSMSBean</display-name>
 <ejb-name>SendSMSBean</ejb-name>
 <ejb-class>sk.transacty.cc.ejb.SendSMSBeanBean</ejb-class>
 <transaction-type>Container</transaction-type>
 <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
 <message-driven-destination>
 <destination-type>javax.jms.Queue</destination-type>
 </message-driven-destination>
 <resource-ref>
 <res-ref-name>jdbc/CCDataSource</res-ref-name>
 <res-type>javax.sql.DataSource</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
 </message-driven>
</enterprise-beans>
<assembly-descriptor>
 <container-transaction>
 <method>
 <ejb-name>SendSMSBean</ejb-name>
 <method-name>*</method-name>
 </method>
 <trans-attribute>Mandatory</trans-attribute>
 </container-transaction>
</assembly-descriptor>
</ejb-jar>orion-ejb-jar.xml:
<?xml version = '1.0' encoding = 'windows-1250'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
<orion-ejb-jar>
<enterprise-beans>
 <message-driven-deployment max-instances="1" name="SendSMSBean" connection-factory-location="java:comp/resource/jmsAQ/QueueConnectionFactories/aqQue" destination-location="java:comp/resource/jmsAQ/Queues/msg_queue" listener-threads="1" min-instances="0"/>
</enterprise-beans>
<assembly-descriptor>
 <default-method-access>
 <security-role-mapping impliesAll="true" name="<default-ejb-caller-role>"/>
 </default-method-access>
</assembly-descriptor>
</orion-ejb-jar>

As far as I know XMLType JMS messages are not supported when using OJMS. They might be for OC4J 10.1.3, but I thought it's an AQ limitation rather than an OC4J one.. To be sure you might just log a TAR on Metalink.
hth,
Bastiaan

JMS queue problem integrating with TIBCO

Hi all!
We have several communication channels between XI 3.0 (SP21) and TIBCO via JMS queues. All of them are working fine except one. This problem only happens in development and quality systems with SP21, production has SP17 and doesn't have this error on the same communication channel.
We are getting the following error in communication channel details...
27-03-2008 16:32:21 XI message ID corresponding to the JMS message ID 'ID:EMS-QUALITY.14C46ECF3303EC:61' has the value 'null', with the ID: prefix removed+
27-03-2008 16:32:21 XI message ID corresponding to JMS message with ID 'ID:EMS-QUALITY.14C46ECF3303EC:61' will be created with same value as JMSCorrelationID with value 'null'+
27-03-2008 16:32:20 Error while processing message 'null'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in converting Binary message <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_PedCarga_GE xmlns:ns0="http://pt.galp.is-oil.ec"> <Partner> <ZIDIF>62</ZIDIF> </Partner> <Controle> <Nr_Envio>29183049</Nr_Envio> <Dt_envio>20080229</Dt_envio> <Tipo_Carga>CPAT</Tipo_Carga> <Operador>230</Operador> </Controle> <PedCarga> <FRETE> <Tipo_Registo>N</Tipo_Registo> <Inst_Carreg>ES41</Inst_Carreg> <Data_Execucao>20080228</Data_Execucao> <Resp_Transporte>13</Resp_Transporte> <Transporte> </Transporte> <Transportador>1700</Transportador> <Ref_Externa_head>2008022931859</Ref_Externa_head> <Gera_Docs>X</Gera_Docs> <Imprim_Docs>X</Imprim_Docs> <Imprim_Ordem_Carreg>X</Imprim_Ordem_Carreg> <Confirm_Autom>X</Confirm_Autom> <Operador>230</Operador> </FRETE> <ENTREGA> <Tipo_Destinatario>1</Tipo_Destinatario> <Local_Entrega>14018</Local_Entrega> <Cod_Produto>GOA []</Cod_Produto> <Quantidade>05100</Quantidade> <Ref_Externa_Item>01737307470601</Ref_Externa_Item> <Regime_Fiscal>N</Regime_Fiscal> </ENTREGA> <ENTREGA> <Tipo_Destinatario>1</Tipo_Destinatario> <Local_Entrega>14018</Local_Entrega> <Cod_Produto>GOC []</Cod_Produto> <Quantidade>13300</Quantidade> <Ref_Externa_Item>02737307470602</Ref_Externa_Item> <Regime_Fiscal>R</Regime_Fiscal> </ENTREGA> </PedCarga> </ns0:MT_PedCarga_GE> to XI message for message: null: InvalidParamException: Invalid message id: com.sap.guid.GUIDFormatException+
Any clues?
Regards,
Fernando Figueiredo

We changed the conversation ID from Message ID to Correlation ID.

Jms queue in "write only" mode...

Hi.
I have a jms queue and I want set it to "write only mode" for some time. It means that I want to put messages to this queue but I want this messages to not be able to receive by any consumer until I remove "write only" flag. Is it possible?
Thanks in advance!

do you have control of the consumers? at my previous job, we wanted to stop queue consumption at certain points in time. we were using jboss, which enabled us to control the mdb consumer pool via jmx. dunno if other app servers have similar functionality. regardless, you aren't going to find a solution to this within vanilla jms, it will be an app-server specific solution. (possibly you could put the mdb's in their own ear file, and deploy/undeploy this ear as necessary?)

How to query for messages on JMS Queue?

Hi All,
What is the best way to query on a JMS Queue? I would like to query for messages based on values entered on a screen. Can this be achieved using the JMS Adapter or any other adapter?
JDev : 11.1.1.4
Thanks and Regards.

Hi,
I am not 100% clear on your requirement and what selection criteria you need. I would be surprised if you need the DB adapter. If you just want to query how much message are in the queue or other related queries for example related to header information then DB adapter can be used. This only works when JMS queue is stored in the database. Personally I have never come across this requirement.
I suggest to look in more detail of the JMS adapter. The JMS adapter can be used to select (subscribe) to certain messages. Please read the below for more information:
http://docs.oracle.com/cd/E17904_01/integration.1111/e10231/adptr_jms.htm#CJACBCHJ
The message is automatically removed from the queue (implicit delete) the moment it is picked-up. I would not recommend deleting a message directly from the queue using DB adapter. What is the point of publishing the message in the first place?
Thanks
Sander

Polling a JMS Queue

Hi,
I am new to ODI,my scenario is that I want to poll a JMS Queue, from ODI for messages, and once I receive the message I want to persist it in DB, I need help to make this work.
Thanks,
Rahul

I think you ran into a known Bug that has been fixed in recent versions/service-packs (sorry, I don't know the version number). Setting the delivery mode override to Persistent is fine as a work-around as long as you're sure that your applications don't send non-persistent messages to the affected destinations. If this is a concern and you need to force the delivery mode override back to its default whilst still keeping your time-to-live override, I think you can probably do this by shutting down your domain, then editing your XML to remove the delivery mode override stanza, and finally restarting...
Tom

Issue with internal JMS queue

Hi,
We discovered following issue with Netweaver version:
SAP EP 6.0 ON WEB AS 6.20
J2EE version:
Cluster-Version: 6.40 PatchLevel 106831.313
Build-On:Thursday, October 26, 2006 18:56 GMT
Perforce-Server:
Project-Dir:JKernel/630_VAL_REL
JKernel Change-List:106831
Build machine:SAPInternal
Build java version:1.3.1_18-b01 Sun Microsystems Inc.
SP-Number: 19
Source-Dir: D:\make\engine\630_VAL_REL\builds\JKernel\630_VAL_REL\archive\dbg
During sending messages into internal JMS queue we sent messages bigger than 1MB. After that, JMS queue was not able to process any other messages even if it was smaller than 1MB. Same issue occured if there was more smaller messages sent in short time (e.g. in 2 seconds). We don't have any significant error message in any log.
See information thath we have found in dump stack trace file (ix.log):
"SAPEngine_Application_Thread[impl:3]_25" prio=5 tid=0x0000000101f5ebf0 nid=0x37 in Object.wait() [fffffffe0bdfd000..fffffffe0bdff8b0]
at java.lang.Object.wait(Native Method)
- waiting on <0xfffffffe2ebfa1b8> (a java.lang.Object)
at java.lang.Object.wait(Object.java:429)
at com.sap.jms.client.memory.MemoryManager.allocate(MemoryManager.java:132)
- locked <0xfffffffe2ebfa1b8> (a java.lang.Object)
at com.sap.jms.client.memory.MemoryManager.allocateMemoryForBigMessage(MemoryManager.java:92)
- locked <0xfffffffe2ebfa1b8> (a java.lang.Object)
at com.sap.jms.client.session.Session.processFinalMessage(Session.java:1732)
at com.sap.jms.client.session.Session.run(Session.java:675)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
which indicates to us that initializing of memory is locked.
Please let us know:
-if there is any log which indicates this behaviour without making thread dump
-which limits must be fulfilled to process messages without this error
-how to unblock this lock for processing correct messages without restarting NW - or if there is any predefined timout which kill this locked session and disable uncorrect message
-how to manage records in bc_jmsqueue table for removing big messages from queue if there were loaded already
-how to stop application which caused this problem. If we try to stop it through standard stop_App, application stays in Stopping mode forever.
This problem occured in test environment and also in productive environment using the same SAP NW. Now - we do not have any work around solution..... therefore periodically we need to restart SAP NW....
Thx for any suggestions.....

Hi,
We are also facing the same problem of restarting the SAP NW each time, if you have found the solution, please let me know.
Thx in advance.
Ramanath

JMS queue notification delays

We've noticed that when we import large calendars that there is a delay in some of the events propagating to attendee calendars. We assume that there is some sort of a delay or backlog in the JMS queue.
1) how do you monitor the delay? I tried looking at NumMsgsIn and NumMsgsOut in mbean = com.sun.messaging.jms.server:desttype=t,name="DavNotificationTopic",subtype=Monitor,type=Destination. I expected to see NumMsgsIn greater than NumMsgsOut during the period of sync delay, but they were actually pretty equal the whole time.
2) how do you tune the server to reduce or eliminate the delay?

Yes and no. Yes, scheduling messages are deposited into individual users outboxes when the PUT on the calendar collection happens. But those scheduling messages are not removed from there immediately once processed (although they are purged after some time). A global internal queue is processing those messages asynchronously, adding the corresponding event into attendees calendars as needed.
If you have a large calendar with a lot of events, themselves with a lot of attendees, the queue can grow quite large and take some time to process all those scheduling messages. There is currently no way to monitor this internal queue (well, unless you are ready to play with some SQL commands). On the other hand, by looking at the scheduling log, you can track the gap between messages that have been enqueued (second column is "E") and messages that have been delivered ("DL" or "DE", "DM" or "R"). It should come down to zero when all are processed. By looking at the 4th column, you can track the processing of a particular event (it corresponds to the event UID).

I want to access JMS Queue in websphere from a client application

Hello all
I tried to access a jms queue in the websphere from a client application
my connection factory jndi name is : MyConn
my queue name jndi name is : MyQueue
and here is my code :
Hashtable environment = new Hashtable();
environment.put(Context.INITIAL_CONTEXT_FACTORY,
"com.ibm.websphere.naming.WsnInitialContextFactory");
environment.put(Context.URL_PKG_PREFIXES, "com.ibm.ws.naming");
environment.put(Context.PROVIDER_URL, "corbaloc:iiop:localhost:2809");
return new InitialContext(environment);
then:
q = (Queue) ctx.lookup(QJNDIName);
QueueConnectionFactory connFactory = (QueueConnectionFactory)
ctx.lookup(ConnFactName);
I had the following exception :
javax.naming.NameNotFoundException: Context: networking/nodes/networking/servers/server1, name: MyQueue: First component in name MyQueue not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
Can i have any help please ....

Hi
You are missing some critical jar files in your class path. It should be namingclient.jar, also please or something similar that is missing in classpath.
HTH
VJ

Oracle AQ to JMS Queue which is on Oracle Application server

Hi,
I am using Oracle Streams AQ Oracle database 10g
and i have a JMS Queue on oracle Application server.
how i can Propagate message from Oracle AQ (AQ$_JMS_TEXT_MESSAGE)Queue to JMS Queue. ?
Thanks,
Satnani

Hi Justin,
Thanks for Reply, but in my case my JMS queue is on Oracle Application Server.
and i want to propagate message from AQ to JMS queue.
and none of the document is available to describe how to send message from oracle database AQ to JMS queue which is on application server.
please help
Thanks,
Satnani

Remove JMS Queue

Similar Messages

Maybe you are looking for