Problem in XI regarding Queue

Hi,
I have got problem in XI regarding Queue.
When i am sending Message to XI if there is some exceptions raised like Invalid Date etc it's status in Q is SYSFAIL n message is in Scheduled mode.
But the message coming next in to XI is also going to schedule mode N showing Queue entry same as that of previous message.
And it's not getting processed. If we r deleting the Queue entry manually n reprocessing the message it's successfully processing.
Can we do something to make that the messages without any exception should process even though there are entries in queue.
And also can nybdy send me some links relating to this Queue maintenance concepts in XI.
Appriciate ur help
Kishore

Hey,
chk out this thread
"Scheduled for Outbound processing" message
regards
jithesh

Similar Messages

Problem to initialize delta queue of datasource from CRM 7.0.

Hi all,
I've some problem to initialize delta queue of datasource from CRM 7.0. After initialize the Init in BW, the delta queue was created but after the user changed data, this changed didn't populated into delta queue.
I tried the steps below but without any success. Anybody know how can I correct this issue?
Suggestion 3: Please check the following.
Please Check if the services have been generated in transaction GNRWB.
If they are not active(not marked 'X' before their names) then activate
the services following the steps here.
Go to transaction GNRWB
Select BUS_TRANS_MSG
Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue
Press Generate.
Also check for the following:
1. The delta should have been initialized successfully.
2. Confirm that all Bdocs of type BUS_TRANS_MSG
are processed with success in SMW01.
3. If there are queues in SMQ1 with erroneous status then activate
these queues.
In Transaction SMQ1 if there are Queues existing with
names beginning with CRM_BWAn (n is number) then
activate these queues in the same transaction.
4.a)If required activate the datasource
Go to transaction BWA5 > select the required datasource and
activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
selecting the name of the datsource and pressing the candle icon for
'activate delta'.
5. In BW system
Go to transaction RSA1 > modeling > infosources > select the
infosource > right mouse click on the selected
infosource > choose option replicate datasource
Activate the infosource.
6. Go to the scheduler for the infosource > select delta in the
update >choose the option PSA only (in the Processing tab)

Hi Peter,
Thank you for your answer.
But we need to find out what the reason for this import error is.
Our customer will not be very pleased to see that all IDocs from CRM system cannot be found in the IDOC folder.
IDX2 import of metadata is no issue.
We were successful for standard and customer Idocs here.
Additional information:
We are already importing Idocs from a SAP ECC 6.0 system into PI in another SWCV
successfully. So this is a CRM system specific issue in our environment.
Regards
Dirk
Edited by: Meinhard Dirk on Aug 27, 2010 10:30 AM

MessageDriven Bean problem.Working but the queues r not getting cleared

I have written a simple message driven bean.It just sends a message to an another queue myadapterqueue
on getting a message .
It is working. But the problem is if I restart my application server then it again reads the messages which had been sent to it earlier.Also the queue size is
not getting to 0 bytes after it has consumed messages.
My application server is JBOSS2.4.3
I think I have to specify some attributes in the
descriptor files.But how??????????????
Here is my code
import java.util.*;
import javax.ejb.*;
import javax.jms.*;
import javax.naming.*;
public class MyMessageBean implements javax.ejb.MessageDrivenBean,javax.jms.MessageListener
     private QueueConnection connect=null;
     private QueueSession session=null;
     private QueueSender sender =null;
private Queue sendQueue=null;
private MessageDrivenContext ctx = null;
     public void setMessageDrivenContext(MessageDrivenContext mdc){
          System.out.println ("In setMessageDrivenContext--------------");
          this.ctx=mdc;
     public void ejbCreate(){
          try{
               System.out.println ("Message bean Created--------------");
               InitialContext jndi=new InitialContext();
               QueueConnectionFactory queueFactory=(QueueConnectionFactory) jndi.lookup("ConnectionFactory");
               connect=queueFactory.createQueueConnection();
               session=connect.createQueueSession (true,Session.AUTO_ACKNOWLEDGE);
               System.out.println ("After session creation--------------");
               sendQueue=(Queue)jndi.lookup("queue/myadapterqueue");
               System.out.println("************ queue/myadapterqueue");
          sender=session.createSender (sendQueue);
          System.out.println ("Before Connection start--------------");
          connect.start();
          }catch(javax.jms.JMSException jmse){
               System.out.println ("In ejbcreate exception-------------------");
               throw new javax.ejb.EJBException();
          }catch(javax.naming.NamingException jne){
               System.out.println ("In ejbcreate exception-------------------");
               throw new javax.ejb.EJBException();
     public void ejbRemove(){
          try{
          System.out.println("ejbRemove done");
          connect.close ();
               this.ctx=null;
          }catch (javax.jms.JMSException jmse){
               System.out.println ("In ejbremove exception-------------------");
               System.out.println("ejbRemove excetion");
               throw new javax.ejb.EJBException();
     public void onMessage(Message msg){
          try{
          this.sender.send (msg);
          this.session.commit();
          System.out.println(" Message");
     }catch(javax.jms.JMSException jmse ){
          jmse.printStackTrace();
here are my descriptors
ejb-jar.xml
<?xml version="1.0"?>
<!DOCTYPE ejb-jar>
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>MyMessageBean</ejb-name>
<ejb-class>MyMessageBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
and the correspong xml file for the application server here is jboss.xml
?xml version="1.0" encoding="UTF-8"?>
<jboss>
<enterprise-beans>
     <message-driven>
          <ejb-name>MyMessageBean</ejb-name>
          <configuration-name>Standard Message Driven Bean</configuration-name>
          <destination-jndi-name>queue/MyMessageBeanQ</destination-jndi-name>
     </message-driven>
</enterprise-beans>
</jboss>

it is unclear whether you are commiting on the first queue or second one.
but it appears like you have created a transactional problem across the two queues. although you commit on the first queue, this commit is not extended to the second queue.
things will be fine unless you get an exception of shutdown.
if you shut your message provider down first then you cannot send the message to the second queue. (assuming that queue 2 is also on the same server)
if you shut your MB app server down then you may be in the middle of accepting a onMessage callback from the first queue.
do you have another MB that registers this one as a listener, or are you infact sending a message back onto the same queue...
public void onMessage(Message msg){
try{
     this.sender.send (msg);
     //your server may shutdown here and leave messages on the first queue. and send extra messages on the second.
        this.session.commit();
        System.out.println(" Message");
} catch(javax.jms.JMSException jmse ){
        jmse.printStackTrace();
}

Problem regarding queues..............XBQO*

file ->BPM->File scenario................
when i run this scenario......i see two rows in the SXMB_MONI....
First: message from sender business service to BPM and
Second: message from BPM to Receiver business service.....
but for these rows in the MONI i see queue XBQO* for the first one and
XBTO* for the second one.....
but i have learnt that......when message comes from the business service to the integration server it should use an inbound queue (like XBTI, XBT1, XBT9* in case of EO and XBQI, XBQ1, XBQ9*) of the integration server.....
can u expalin this contradiction????????????????

hi
check the below links
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
regards
Chilla

Problem STMS: "Copying Import Queue SID "

Hello
I have a quetion, yesterday we changed the name server of production, now when I want to make the tranports I got this message
Copying Import Queue <SID>, I had checked the configuration of stms, RFCs and I did the test and these are ok
In the alert viewer I found this mesage
Could not start transport control program tp
Message no. TP608 Diagnosis
There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.
Error code: 4
RFC error text: connection to partner 'prod.line-online.com:1823'
Meaning of the error codes:
03 RFC system failure
04 RFC communication failure
System Response
The function terminates. Details about the error can be found in the trace file of the Gateway Monitor (SMGW).
Procedure
Contact your system administrator or use report RSTPTEST to localize the error. You can then execute the command again.
I don`t know Where can I check?
thanks a lot

Hi Danny,
Can u just clear us is the is the problem with transport control program is resolved.
in the above reply u r telling the requests don't load in the queue.
Is that means spool request or transport request. please clear the point.
Also as ur telling in SM21: "Spool is full" ; and another message says: "Run-time error "SPOOL_INTERNAL_ERROR" occurred"
are occurring. Can u just go to those work processes, and analyze the trace file errors(which will be listed in red colour).
if ur having any issues, paste the trace file error log here.
let us know if u have any issues,
Regards,
Ravi

Print problem: Appleworks and Print Queue Constipation

Let me start by saying that I have had this problem intermittently on my own computer, and now my mother has it on hers. My computer is wicked fast and loaded, hers is a basic iMac17" G4. I strongly suspect that the problem only occurs with Appleworks, but I may be wrong.
So the problem is this. When I try to print, the item goes to the print queue, and then the job stops. The printer icon shows up in the dock with a red exclamation point. The job stays in the queue. In the printer queue dialog box, you can click on the "start jobs" icon, and the icon will change to the "stop jobs" icon..... but within seconds the icon will revert back to saying "start Jobs."
At this point, I have a problem that is hard to eliminate. Cleaning out the queue is not enough to make the computer behave. I do a variety of things like a restart, unplugging the usb, unplugging the power cord to the printer, etc. Eventually things get better, and I am never sure what thing I did fixed it.
This has happened only rarely on my computer, so I have not gotten too excited. But it is chronic on my Mom's, so I spent hours doing varouis disk fixing programs and dumping the printers preference files and making sure she has the latest driver (it is an Epson C88). None of that works. (incidentally, I have various printers, including an Epson R320, not sure it that printer is always the culprit on my computer).
I thought I had her problem solved when I made her go to the Page Setup dialog every time and make sure her Epson printer is selected there before printing. But today she said the problem reoccured, even doing as I suggested.
She can print from every other program. She can print to PDF and open that PDF in Preview and print from that. But that is an awkward workaround for an older woman who is scared of her computer to begin with.
So... any ideas. I scoured this forum and couldn't find anything that I hadn 't already tried

Peter,
More a guess than anything else, but I'd suspect a corrupted preferences file.
See Peggy's tip "AppleWorks has stopped working correctly" here:
http://discussions.apple.com/thread.jspa?threadID=121704
for more information.
Regards,
Barry

R/3 Patch Upgrde Problem due BW Delta Queue.

Hi Expert,
I have extracted all the logistic & delta data in BW to make delta queue emplty. My query is that ,should it delete these queue in RSA7 or it should disappear after extraction.
In LBWQ there are only two entry MCEX17 & MCEX17_1 , these queue are still there after extraction.what to do these queue ?
These queues are giving error while upgrading patch.
2LIS_13_VDITM
2LIS_13_VDHDR
2LIS_11_VDITM
2LIS_11_VDHDR
2LIS_17_IONOTIF
Regards,
Anand Mehrotra.

Hello Anand ,
There is no need to delete the queues for the upgrade, you only need to make sure that there is no data in these queues in rsa7 that need to be extracted, if you run the relevant infopackage twice on the BW side then it should clear the data from RSA7 , before doing this please make sure that all data has been updated from lbwq to rsa7 (if using queued delta) and that there is no data in sm13 for the queues. In RSA7 you can double click on the Individual queues and if you check under delta and delta repeat option for these logistics queues you should find 0 records.
Best Regards,
Des

Problem with initialization Delta queue

Hi Gurus,
I have problem with initialization of delta queue when I try load transaction data from R3 (FM) to BI.
Error message: Deviation of (64 seconds) between qRFC counter (000012365466830000080000) and actual time (08.03.2009 21:10:19).
I have no idea where is the problem because this problem occurs only in PRD systems. In DEV and QUA system everything is OK.
System BI: BI 7.0
Source system: ECC 6.0
Thank you for all answers!
mp

Hi,
Replicate the DS in BW Prod and then Activate Transfer rules and then try.
First you delete the DElta quae in RSA7 for the particular datasource in the R/3
source system then you try to intialize, here you are trying to intialize datasource with
same selection conditons . thats why it is giving shortdump
Check
Business Content and Extractors
Thanks
Reddy

Having problems receiving messages from queue

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

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

Problem in CIF Inbound Queue

Hello Every1,
When I try to process the CIF inbound queue (APO system) it says the logical system is not found. But when I check in the table TRFCQIN and TRFCQSTATE the logical system has assigned properly. So please let me know how to rectify this.
Thanks,
Siva.

Hello Chinni,
Master data cannot be reconciled using Delta Report. It is only for transaction data. If you are still having problem transferring inforecords - first check if the location product combinations used in the inforecord exist in APO.
Next follow these steps:
0. Make sure there are no error CIF queues inboudn to APO
1. Do you have an active integration model with the inforecord and still the procurement relationship is not created in APO? If so then exclude the particular inforecord (by document number) from the integration model.
2. Generate it and activate it.
3. Then generate the integration model again without the exclusion and activate this model. This will force sending the inforecord to APO.
4. See what is the error coming and send the details.
Thanks,
Somnath

Problem Connecting to JMS queue with C sharp client

Hi there,
I am trying to connect to a JMS queue using a C# client but i have a problem trying to connect. The problem comes in when i run the C# script a dialog box appears requesting a T3TransportFactory.cs which i do not have on the client. and when i close it i get an exception on
IContext context = ContextFactory.CreateContext(paramMap);
Exception - Failed to connect using URL <t3://10.103.130.18:7001>
StackTrace - at WebLogic.Messaging.Physical.T3TransportFactory.CreateT3Transport(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\T3TransportFactory.cs:line 226
at WebLogic.Messaging.Physical.ContextPhysical.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\ContextPhysical.cs:line 83
at WebLogic.Messaging.Context.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Context.cs:line 56
The stacktrace indicates that it is looking for a T3TransportFactory.cs file in that particular path on the client (This is my speculation) but this directory path does not exist on the client machine with the c# code.
I got a WebLogic.Messaging.dll referenced in my c# project and the ip/port numbers are correct (we know this cause we tried a java client that connected successfully)
Can anyone assist me on this issue?

The issue might be the dll file you are referring to. Did you use the dll from the weblogic installation folder (BEA_HOME/modules/com.bea.weblogic.jms.dotnetclient_1.X.X.X).
Refer - http://docs.oracle.com/cd/E15051_01/wls/docs103/jms_dotnet/install.html#wp1075258
Hope this helps.
Thanks,
Patrick

Problem writing to AQ queue

Hi,
I am having a hard time trying to connect to a AQ queue (on oracle 8.1.7)
from a Java 2 client. Can anyone make something out of this? Any help would be
appreciated!
Regards,
-Per
Classpath :
aqapi.jar;jmscommon.jar;classes12.zip;nls_charset12.zip
Error : ("Ikke stxttet tegnsett" means "Encoding not supported")
oracle.jms.AQjmsException: Ikke stxttet tegnsett: oracle-character-set-46
     at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:934)
     at oracle.jms.AQjmsProducer.send(AQjmsProducer.java:469)
     at oracle.jms.AQjmsProducer.send(AQjmsProducer.java:386)
     at aetat.felles.mail_ejb.OracleWrite.write(OracleWrite.java:50)
     at aetat.felles.mail_ejb.OracleWrite.main(OracleWrite.java:23)
My client looks like this :
package aetat.felles.mail_ejb;
import javax.jms.*;
import oracle.jms.*;
import java.util.Properties;
public class OracleWrite {
String ORACLE_CONN_STRING = "jdbc:oracle:thin:@xxx:1522:yyy";
Properties props = new Properties();
String user = "user";
String password = "password";
String greeting = "Hello";
String QUEUE = "QUEUE_NAME";
public OracleWrite() throws Exception {
props.setProperty(user, password);
public static void main(String[] args) {
try {
OracleWrite writer = new OracleWrite();
writer.write();
} catch (Exception e) {
e.printStackTrace();
private void write() throws Exception {
QueueConnection qc = null;
QueueSession qs = null;
AQjmsSession ora_qs = null;
QueueSender sender = null;
try {
QueueConnectionFactory qcf =
AQjmsFactory.getQueueConnectionFactory(ORACLE_CONN_STRING, props);
qc = qcf.createQueueConnection(user, password);
qc.start();
qs = qc.createQueueSession(true, QueueSession.AUTO_ACKNOWLEDGE);
Queue q = ((AQjmsSession)qs).getQueue(user, QUEUE);
sender = qs.createSender(q);
TextMessage m = qs.createTextMessage(greeting);
sender.send(q, om);
qs.commit();
qc.stop();
catch (Exception e)
e.printStackTrace();
qs.rollback();
finally
try { sender.close(); } catch (Exception e) {}
try { qs.close(); } catch (Exception e) {}
try { qc.close(); } catch (Exception e) {}
}

The character set of our database where I tested your program is WE8MSWIN1252.
Another database on our systems has WE8ISO8859P1 as the character set.
Hi,
Thanks for your reply - it's nice to know that the program is working correctly!
When it comes to the database, we are using the following character set : "WE8ISO8859P15". What are you using? Do you know what character sets that
are "allowed"?
Regards,
Per Mengshoel

Problem Configuring JMS Error Queue

Domain configuration : one adminServer, One cluster, 2 managedservers in cluster
Two distibuted Queues: InboundQueue, Error Queue
I want to redirect any bad message from InboundQueue to ErrorQueue and discard it.
It worked fine for 4 yrs in Wls 8.1 ( did configured in 8.1)..
now i upgrde to wls 10.1 and i did same configuration but InboundQueue is not redirecting to Errorqueue..
Dont know where i am missing..
here is the config.xml entry and jms/JmModule.xml files..
config.xml entry_
<jms-system-resource>
<name>JmsModule</name>
<target>cluster1</target>
<sub-deployment>
<name>subdeployment1</name>
<target>JmsServer1,JmsServer2</target>
</sub-deployment>
<descriptor-file-name>jms/JmsModule-jms.xml</descriptor-file-name>
</jms-system-resource>
JmsModule.xml_
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<uniform-distributed-queue name="ErrorQueue">
<sub-deployment-name>subdeployment1</sub-deployment-name>
<delivery-params-overrides>
<delivery-mode>Non-Persistent</delivery-mode>
<time-to-deliver>-1</time-to-deliver>
<time-to-live>-1</time-to-live>
<priority>-1</priority>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>0</redelivery-limit>
</delivery-failure-params>
<jndi-name>ErrorQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
</uniform-distributed-queue>
<uniform-distributed-queue name="InboundQueue">
<sub-deployment-name>subdeployment1</sub-deployment-name>
<delivery-params-overrides>
<delivery-mode>Persistent</delivery-mode>
<time-to-deliver>10</time-to-deliver>
<time-to-live>10</time-to-live>
<priority>2</priority>
<redelivery-delay>10</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<error-destination>ErrorQueue</error-destination>
<redelivery-limit>1</redelivery-limit>
<expiration-policy>Redirect</expiration-policy>
</delivery-failure-params>
<jndi-name>InboundQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>10</forward-delay>
</uniform-distributed-queue>
</weblogic-jms>
Any help
Thanks
ksr

Are you still having a problem? If so, I recommend trying to simplify the reproducer by removing the "time-to-deliver", "redelivery-delay", and "time-to-live" settings.
<time-to-deliver>10</time-to-deliver>
<time-to-live>10</time-to-live>
<redelivery-delay>10</redelivery-delay>
Note that these are all set to a very small value (10 milliseconds), and that the message will expire before it can be delivered or redelivered. The delivery delay is 10 millis, so by the time the delivery delay completes, the time-to-live will have passed -- furthermore, if there was no delivery delay, the redelivery delay is at 10 millis -- so by the time the redel occurs the time-to-live expires).
Tom

Problems in the play queue management that have been around forever without having been addressed

Hey all,
It's been a while since I last contributed here. Think my last post was around 2011 or so - right around the time when the Spotify team announced they are going to be concentrating on polishing the basic functionalities of the player. It's been around 3 or so years and I still find myself cursing the badly neglected play queue management on a more or less daily basis. This makes me a sad panda.
As I wrote 3+ years ago, I don't know about anyone else but at least to me the play queue management is like the 3rd most basic functionality in a music player - right after being able to find music in the first place and then being able to actually play it too.
I just spent mere 15 minutes and came up with this list of issues that are still present in the player:
Play queue is treated differently depending on whether you choose to "play" some tracks or if you "queue" them. In the former case you can delete the tracks from the play queue, in the latter case you can not.
If you "queue" up tracks in spotify, the shuffle setting has no effect (okay, this might be intentional, or it might not be, I don't know).
If you first choose to "play" some tracks and then you "queue" up additional music, the queued tracks are not placed at the end of the current play queue but, rather, immediately after the currently playing song. Sure, this might also be intentional but, to me, it seems counter-intuitive and just plain wrong.
You can change the order of the "queued" tracks - but only within the confines of the "queued" tracks i.e. if you first choose to "play" tracks and then you "queue" up additional tracks, you can not move a "queued" track to be played in the middle of the tracks you chose to "play".
As a continuation to the previous point, you CAN, however, make a track you chose to "play" to be played in the middle of the "queued" tracks but, instead of just changing the track's position in the play queue, it is duplicated, or triplicated, or quadruplicated (is that a word?) instead i.e. you get to hear that track in the middle of the "queued" tracks... and then again as part of the tracks you chose to "play". Additionally, once you do that, the duplicated tracks becomes "queued" i.e. you can no longer delete it from the play queue.
You can not "queue" tracks by right-clicking on a playlist - the only way to do that is to select the playlist so you can see the tracks in it, then click a track, select all, and then "queue" through a right-click.
Remember folks; it took me all of 15 minutes to come up with all of that.
-typo
PS. I know these are not exactly ideas but, since I can't post on the bug board, I didn't know where else to post this.
PPS. I can't seem to be able to add tags to this post by writing in the text field that tells me to separate the tags by a comma.

Here's an explanation of my typical behavior when using Spotify, to try and help explain why I consider these points a major problem:
Quite often, when I launch Spotify, it is to find something new to listen to. To achieve that, I use a number of means, one of which is the absolutely fantastic "Discover" functionality (I love it!). Typically, I listen to some recommended artists/tracks/albums, and when I find an album or artist I like, I click "Play" on top of the track list in the album view and start listening.
Then I continue browsing and discovering and, when I come across something else that I find interesting, I can no longer choose to "play" it because it would completely override the current play queue, the currently playing track included, and start playing the new album I just found. So the only option is to "queue" it.
Now, this is where the problems kick in. Instead of being queued up nicely at the end of the play queue like it should do in my view, this new album is like the neighborhood bully, cutting in line straight to the entrance. If I leave things the way they now are, I'm going to hear the currently playing track... and then the entire new album I just "queued" up... and only after that do I get to hear the rest of the tracks I first chose to "play".
If, at this point, I keep on browsing and discovering and finding more interesting music, I can pretty much only keep on "queueing" them up which means that the rest of the first album just keeps getting pushed back further and further. However, the neighborhood bullies seem to respect one another, so all music added beyond the first "queued" tracks take their place at the end of the queue, like they should.
Sure, I could just "queue" up the first album as well but I really dislike the way the whole "queue" functionality has been implemented - simply because I want to be in full control of my play queue which means that I want to be able to move any track to any position in the play queue regardless of how it was added there and I want to be able to delete any track I choose from the play queue at any time.
Also, I would very much like to be able to just add like a 100 tracks in the play queue, one track or one album at a time and then hit "Shuffle" to have them play in a random order. With a vast majority of the tracks being "queued" up this does not happen.
I hope this helps at least some people see things from my perspective.
-typo

Regarding Queue

If "Maintain Order At Runtime" was checked in Interface determination, then are all the messages with same process Id will go to the same Queue always?
Please clarify me here.
Thanks,
Regards,
Naresh

Hi,
> Do we need to check Manintain Order At Runtime when Qos is EOIO?
Just go through this sap link, you will get all the answers.
http://help.sap.com/saphelp_nw70/helpdata/EN/42/ea20e737f33ee9e10000000a1553f7/content.htm
Regards,
Sarvesh

Problem in XI regarding Queue

Similar Messages

Maybe you are looking for