Politics for queues

hi!
i have two queues definied for server1 (default and MyExecute Queue) in weblogic 8.1 sp3. the queues are definied with the same priority (5). if there are one request both queues, whichÂ´s process first? WhatÂ´s politics used and how i can configure it (if itÂ´s possible).
Thanks in advance.

Hi
Pls refer the below link
Refer the blog.
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4b88cb90-0201-0010-5bb1-a65272a329bf
http://help.sap.com/saphelp_nw04/helpdata/en/e8/57fb3b8a40bd50e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/f7/2c4b3f53275003e10000000a114084/content.htm
U Can Follow these Links
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
/people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1 -- ccms alerts 1
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2 -- ccms alerts 2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3 -- ccms alerts --- 3
Alerts with variables from the messages payload (XI) - UPDATED -
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
From HelpFile
<b>Reward Points if Helpful</b>

Similar Messages

Why we will go for Queue delta instead of Unserialized and Direct delta ?

Hi Experts,
Why we will go for Queue delta instead of Unserialized and Direct delta ? specify any reasons for that ?
What happens internally when we use Queue delta , Direct delta ?
I will allocate points to those who help me in detail. My advance thanks who respond to my query.

Hi,
Direct Delta
With this update mode, extraction data is transferred directly to the BW delta queues every time a document is posted. In this way, each document posted with delta extraction is converted to exactly one LUW in the related BW delta queues. If you are using this method, there is no need to schedule a job at regular intervals to transfer the data to the BW delta queues. On the other hand, the number of LUWs per DataSource increases significantly in the BW delta queues because the deltas of many documents are not summarized into one LUW in the BW delta queues as was previously the case for the V3 update.
If you are using this update mode, note that you cannot post any documents during delta initialization in an application from the start of the recompilation run in the OLTP until all delta init requests have been successfully updated successfully in BW. Otherwise, data from documents posted in the meantime is irretrievably lost. The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.
b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.
Queued Delta
With this update mode, the extraction data for the affected application is compiled in an extraction queue (instead of in the update data) and can be transferred to the BW delta queues by an update collective run, as previously executed during the V3 update.
Up to 10,000 delta extractions of documents to an LUW in the BW delta queues are cumulated in this way per DataSource, depending on the application.
If you use this method, it is also necessary to schedule a job to regularly transfer the data to the BW delta queues ("update collective run"). However, you should note that reports delivered using the logistics extract structures Customizing cockpit are used during this scheduling. This scheduling is carried out with the same report which is used when you use the V3 updating (RMBWV311, RMBWV312 or RMBWV313).There is no point in scheduling with the RSM13005 report for this update method since this report only processes V3 update entries. The simplest way to perform scheduling is via the "Job control" function in the logistics extract structures Customizing Cockpit. We recommend that you schedule the job hourly during normal operation - that is, after successful delta initialization.
In the case of a delta initialization, the document postings of the affected application can be included again after successful execution of the recompilation run in the OLTP (e.g OLI7BW, OLI8BW or OLI9BW), provided that you make sure that the update collective run is not started before all delta Init requests have been successfully updated in the BW.
In the posting-free phase during the recompilation run in OLTP, you should execute the update collective run once (as before) to make sure that there are no old delta extraction data remaining in the extraction queues when you resume posting of documents.
Using transaction SMQ1 and the queue names MCEX11, MCEX12 or MCEX13 you can get an overview of the data in the extraction queues.
If you want to use the functions of the logistics extract structures Customizing cockpit to make changes to the extract structures of an application (for which you selected this update method), you should make absolutely sure that there is no data in the extraction queue before executing these changes in the affected systems. This applies in particular to the transfer of changes to a production system. You can perform a check when the V3 update is already in use in the respective target system using the RMCSBWCC check report.
In the following cases, the extraction queues should never contain any data:
- Importing an R/3 Support Package
- Performing an R/3 upgrade
For an overview of the data of all extraction queues of the logistics extract structures Customizing Cockpit, use transaction LBWQ. You may also obtain this overview via the "Log queue overview" function in the logistics extract structures Customizing cockpit. Only the extraction queues that currently contain extraction data are displayed in this case.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method.
This update method is recommended for the following general criteria:
a) More than 10,000 document changes (creating, changing or deleting a document) are performed each day for the application in question.
b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.
Un-serialized V3 Update
Note: Before PI Release 2002.1 the only update method available was V3 Update. As of PI 2002.1 three new update methods are available because the V3 update could lead to inconsistencies under certain circumstances. As of PI 2003.1 the old V3 update will not be supported anymore.
With this update mode, the extraction data of the application in question continues to be written to the update tables using a V3 update module and is retained there until the data is read and processed by a collective update run.
However, unlike the current default values (serialized V3 update); the data is read in the update collective run (without taking the sequence from the update tables into account) and then transferred to the BW delta queues.
The restrictions and problems described in relation to the "Serialized V3 update" do not apply to this update method since serialized data transfer is never the aim of this update method. However, you should note the following limitation of this update method:
The extraction data of a document posting, where update terminations occurred in the V2 update, can only be processed by the V3 update when the V2 update has been successfully posted.
This update method is recommended for the following general criteria:
a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.
Thanks,
JituK

Filter for queue prioritization ...

Hi guys,
I have a question relating to filters for queue prioritization. I have defined filter for large messages (i.e. messages larger than 2048kB should go into XBTL queue). Is it possible to define another one that would say:
"All messages from Sender Name XXXXX larger than 1024kB should be passed into XBTL queue" ?
I know how to create such filters for other queues but XBTL queue is special case.
Do you know how to do it?
Thanks in advance!
Regards
Zbynek

Hi,
Please find the link for "How To prioritize XI messages in queues" below.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/59e837d3-0201-0010-c096-dc1869733413.reward me if useful. Let me know if ur issue not resolved.
Thanks,
Ramesh

Reports 6i development for Queue Manager

I'm trying to write reports to run from the Queue Manager and am having a truly horrible time. I am able to write complete reports and run them from my desk top, but when I try to run them on the Manager, they have problems at least 8 times out of ten - and then everytime it is back to the drawing board to redesign the report. The error messaging is also not up to scratch - please tell me what 'REP 1212 - Object 'Margin' is not fully enclosed by it's enclosing object 'dept_name' ' means. I understand the message, but it is just plain rubbish - I have built reports the same way many times without problems. The real answer I am looking for is 'Is there a standards document on designing for Queue Manager' ?
Please help
I'm going nuts
Marc

Marc,
There shouldn't be a difference running the report from the queue manager vs. from the command line as long as all of your parameters are the same. The rep-1212 error you are getting sounds like a report that was designed for bitmap being run with mode=character. You would see this difference between the command line and queue manager if from the command line you are running the report with mode=bitmap (or default if your report already has mode as default or bitmap) and run with mode=character in the queue manager. It seems to me that there is probably a difference in how the reports are being run rather than how you've designed them. I'd discuss the issue with Support so they can go into more detail with you.
Hope that helps,
Toby

Configuration for Queue Prioritization for EOIO Queues

Hi,
Please can anybody help me in configuring the queue prioritization for EOIO Queues.
Regards
Srinivas

hi,
Check these help..
Eo/EOIO?BE - Queue - ? - /people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
Please go through these links
/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
For queues in message mapping
/people/venkat.donela/blog/2005/06/09/introduction-to-queues-in-message-mapping
Here are the Queues for Asynchronous Message Processing
http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/94553b4d53273de10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Thanks,
Vijaya.

CCMS monitoring for Queues(SMQ1/SMQ2)

Hi,
How do we monitor Queues(SMQ1/SMQ2) in CCMS. My requirement is to monitor Queues(SMQ1/SMQ2) in CCMS based on the Queue name. I want to create different nodes in CCMS and I want queue name falling under certain criteria should come and sit in the respective node of CCMS.
Means queue with name High_priority should come n sit under node say Test1, queue name with medium_priority should come n sit under node say Test2 and queue name with medium_priority should come n sit under node say Test3.
Is it possible to do so.

Hello,
also for queue monitoring the easier and more flexible way to monitor is via Business Process Monitoring. The configuration is easier than CCMS where you have to use transaction RZ21 and need to transport objects. And the qRFC monitoring is more flexible than in the CCMS. Basically all customers knowing both standard CCMS qRFC monitoring and qRFC monitoring in BPMon chose the later or exchange their existing CCMS monitoring by BPMon.
See also the SDN blog /people/johannes.fleig/blog/2008/06/11/new-business-process-monitoring-functionalities-in-sap-solution-manager-150-qrfc-monitoring
and check out the Interface Monitoring Setup Guide under http://service.sap.com/bpm > Media Library > Technical Information.
Best Regards
Volker
Edited by: Volker von Gloeden on Jul 2, 2010 4:48 PM

Too many Subscribers/Receivers for Queue

The link of Feedback in Java EE 5 tutorial doesn't work, because of this I ask my question here.
I have tried the " Simple Example of Synchronous Message Receives" in Chapter 32 of Java EE 5 tutorial.
In case of destination type queue I got error message.
The log of test:
M:\java\javaeetutorial5\examples\jms\simple\producer\dist>appclient -client producer.jar queue 3
Destination type is queue
Sending message: This is message 1
Sending message: This is message 2
Sending message: This is message 3
M:\java\javaeetutorial5\examples\jms\simple\producer\dist>cd ../../synchconsumer/dist
M:\java\javaeetutorial5\examples\jms\simple\synchconsumer\dist>appclient -client synchconsumer.jar queue
Destination type is queue
Exception occurred: com.sun.messaging.jms.ResourceAllocationException: [C4073]:
A JMS destination limit was reached. Too many Subscribers/Receivers for Queue :
PhysicalQueue user=guest, broker=pc2900:7676(1442)
My question: How can I configure the Queue for more subcribers/receivers?

Hi,
Depending on the version of JMS, this may be a limitation of iMQ PE Edition (This is early in the morning for me, I can't remember which one). So you can look at the documentation, this may be a limitation of PE versus SE or EE. If you can modify it it would be using either the command line imqcmd or the gui based, imqadmin. With it, you can get into the connection factory, and change the maximum number of active consumers onto the queue.
I beleive that using glassfish (as 9) would alleviate this limitation, if it is there, since this is using openmq (imq v4.0).
HTH
TE

Bug in timeout behavior of wait for queue element

The first time a wait for queue element is executed with an infinite timeout (-1 ms) after previously having waited with a finite timeout, it actually times out after the previously used finite interval, a subsequent wait with an infinite timeout then works correctly. Attached is a test program demonstrating the problem. I have tried this demo on both Mac and Sun (LV 6.1 on Mac, LV 6.1f1 on Sun) and it behaves the same on both.
Attachments:
QueueTest.vi.sit ‏22 KB

I do not have an answer at the moment but I have unsuffited the file so that others can look at the program.
Jeremy Braden
Attachments:
Queue.vi ‏77 KB

Docs for Queuing in Tux

Hi all,
Is some comprehensive documentation available for queueing in Tuxedo?
The docs at [e-docs at bea.com] are more like for managing and
changing already existing queues. I especially need it for queuing
on the client side.
Thanxalot,
Sameer
Sameer Bora
Infosys Tech Ltd
Bangalore India
+91 80 8520261 ext 51602
email:[email protected]

/usr/include/sys/errno.h will give you a list of error codes.
The following err code is from OS , not from our plugin.
os error 146 means CONNECTION REFUSED,the backend can't be reached.
Kumar
Graham Dunlop wrote:
Hi,
I have deployed the plug-in in iPlanet 4.1sp8 and it is proxying requests to WLS6.0sp2
Where can I find details of any errors generated by the plug-in. For example in the
error shown below, where can I find the definition of "os error=146" ?
[27/May/2002:11:52:50] failure (26347): for host 217.34.204.9 trying to GET /Admin,
wl-proxy reports: exception occurred for backend host '10.192.32.136/7001':'CONNECTION_REFUSED
[os error=146, line 1198 of URL.cpp]: 10.192.32.136:7001'
Regards,
Graham

ExecuteThread for queue: 'weblogic.kernel.Default' stuck

Hello!
I have web application deployed on WebLogic 8.1 SP 4 cluster which is seriously loaded (~30 concurrent users) and periodically I get such messages wrote to log file:
<Apr 2, 2007 10:11:54 AM EDT> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '51' for queue: 'weblogic.kernel.Default' has been busy for "233" seconds working on the request "Http Request: /myurl/some_jsp.jsp", which is more than the configured time (StuckThreadMaxTime) of "180" seconds.>
As far as I could find from BEA documentation these messages mean that some threads (it is ExecuteThread#51 here) are runned for too long time.
I've made a thread dump and found that for a few (10-15min) thread is doing the same work:
"ExecuteThread: '51' for queue: 'weblogic.kernel.Default'" daemon prio=1 tid=0x6ca004b8 nid=0x3094 runnable [0x6c9fe000..0x6c9ff868]
     at java.net.SocketOutputStream.socketWrite0(Native Method)
     at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
     at weblogic.servlet.internal.ChunkUtils.writeChunkNoTransfer(ChunkUtils.java:280)
     at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:241)
     at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:311)
     at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:387)
     at weblogic.servlet.internal.ChunkOutput.write(ChunkOutput.java:254)
     at weblogic.servlet.internal.MultibyteOutput.write(ChunkOutput.java:482)
     at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:125)
     at weblogic.servlet.jsp.JspWriterImpl.write(JspWriterImpl.java:455)
As you can see, thread is just writing to the socket for 10-15 minutes!!!
Can you help with some suggestions? Can this problem occure because of huge overloading to the server?
Thanks for all your responses.
Thanks

I have installed the Spring application on WebLogic 8.1 SP4 on Red HAt Linux 3.0.
These message doesn't appear for WebLogic 8.1 SP4 on windows.
2007-05-10 10:22:50,356 [l.Default'] DEBUG org.springframework.web.servlet.DispatcherServlet: Rendering view [org.springframework.web.servlet.view.JstlView: unnamed; URL [/util/noAccess.jsp]] in DispatcherServlet with name 'spring'
2007-05-10 10:22:50,376 [l.Default'] DEBUG org.springframework.web.servlet.DispatcherServlet: Could not complete request
java.net.SocketException: Connection reset
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at weblogic.servlet.internal.ChunkUtils.writeChunkTransfer(ChunkUtils.java:267)
at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:239)
at weblogic.servlet.internal.ChunkOutput.flush(ChunkOutput.java:311)
at weblogic.servlet.internal.ChunkOutput.checkForFlush(ChunkOutput.java:387)
at weblogic.servlet.internal.ChunkOutput.write(ChunkOutput.java:254)
at weblogic.servlet.internal.ChunkOutputWrapper.write(ChunkOutputWrapper.java:125)
at weblogic.servlet.jsp.JspWriterImpl.write(JspWriterImpl.java:455)
at jsp_servlet._util.__noaccess._writeText(__noaccess.java:74)
at jsp_servlet._util.__noaccess._jspService(__noaccess.java:283)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322)
at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:111)
at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:250)
at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:965)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:744)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:663)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:394)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:348)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322)
at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:531)
at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:383)
at weblogic.servlet.FileServlet.findSource(FileServlet.java:281)
at weblogic.servlet.FileServlet.service(FileServlet.java:184)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

How to delete the data in update queue and delta queue for Queued delta?

Dear BWers,
How do i delete the delta queue and update queue data before i fill the setup tables for a extraction based on Queued delta. Please help.
Thanks
Raj

Hi Raj,
I think you need some ground work for the LO extraction same as others here. Please read the 3 blogs expliciltly created for LIS by Robert Negro.
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
As well, the OSS 380078 would clear your doubts reagrding the the BW QUEUE mainatinance.
Please let me know if these material has been suffecient enough.
regarda,
raj

E-Mail alerts for queues in SMQ2

Hi,
In a asynchronous IDOC->ABAP Proxy scenario, some of the messages are getting stucked in the transaction SMQ2 in PI system.This happens only when we send 100 IDOCs to PI at the same time and only 5-10 messages are getting stucked with status as "Running". The remaining messages are processed and send to the target system.
I would like to know a solution to trigger an E-mail alert to a specific Mail id if any messages gets stuck in the queue for more than 5 minutes.
Do we need to configure CCMS to achieve this? If so, please let me know the steps.
Thanks and Regards,
Sakthi

Hi Just check for
configure E-mail alerts
Configuring scenario specific E-mail alerts in XI-CCMS: Part-2 By Aravindh Prasanna
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2
XI : Configuring CCMS Monitoring for XI- Part I By Naveen Pandrangi
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
XI : GRMG Customizing for XI CCMS Heartbeat Monitoring Part II By Naveen Pandrangi
/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
Configuring scenario specific E-mail alerts in XI-CCMS: Part 3 by Aravindh Prasanna
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
Regards
Abhishek

Alerts for Queues

Hi All:
I tried a lot to search a blog or forum(but have not get any relevant link) from that I can come to know that we can throw an Alert when queue get stuck in Adapter Engine and ABAP stack.
If any one has some information in his/her mind then please share it with me.
I need to throw an alert when queue (for EOIO) get stuck i.e Holding state, Waiting state, System Error,
Thanks
Farooq.

Hi
Pls refer the below link
Refer the blog.
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4b88cb90-0201-0010-5bb1-a65272a329bf
http://help.sap.com/saphelp_nw04/helpdata/en/e8/57fb3b8a40bd50e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/f7/2c4b3f53275003e10000000a114084/content.htm
U Can Follow these Links
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
/people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1 -- ccms alerts 1
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2 -- ccms alerts 2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3 -- ccms alerts --- 3
Alerts with variables from the messages payload (XI) - UPDATED -
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
From HelpFile
<b>Reward Points if Helpful</b>

Will the memory leak for queue when used in producer and consumer mode in DAQ to transfer different sized array.

In the data acquisition, I use one loop to poll data from hardware, another loop to receive the data from polling loop sent by queue.
But everytime the size of the transferred data array may not be the same, so the system may assign different array size and recycle very frequently.
Will it cost memory leak. Or will it slow down the performance, since the array size is not fixed, so every time need to create a new sized array.
Any suggestion or better method.
Solved!
Go to Solution.

As i understand your description, your DAQ-loop acquires data with the setting '-1' for samples to read at the DAQmx read function. This results in the different array sizes.
Passing those arrays directly to a queue is valid and it does not have significant drawback in performance (at least as far as i know) and it definetly does not leak memory.
So the question is more or less:
Is it valid that your consumer receives different array sizes for analysis? How does your consumer handle those arrays?
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Wish list for Queues

A few functionalities I would like to see added to Queue functions:
1. The ability to queue up an array of elements all at once (rather than having to use a For Loop with the Enqueue Element function inside).
2. Given: A Queue with a set maximum number of elements. I would like a boolean flag on the Enqueue Element function to allow addition of elements to a full queue (thus pushing out the oldest element(s)).
Granted, I can reproduce the above effects thru coding, but it would be nice if they could be handled by the existing Queue functions.

For getting around this, what you can do is build your routines once and then use some hierarchy renaming tool so that you can have unique names for all the VIs. Personally, I occasionally do this with a modified version of a duplicating tool I downloaded from MGI - I simply take the base files I want to duplicate, make a copy of the hierarchy and tell the tool to change\add the prefix or suffix I want.
If you still want to keep the functionality in some base files you can modify, you can write the core using variants (place in the user.lib folder inside a folder beginning with an underscore and it won't appear in the palettes) and then only use the wrappers per project. Of course, you'll suffer some performance penalty with this method.
Try to take over the world!

Politics for queues

Similar Messages

Maybe you are looking for