Sxmb_moni exception in queue - noinst

Hi,
I've got an exception condition on one of my queues in sxmb_moni, when looking at the queue I see the following error - Exeption condition "NOINST" raised. The transaction in the error message is SXMB_MONI and the program is "RSXMB_SELECT_MESSAGES".
I tried to delete the entry from the queue and then resending it but got the same error again.
Any help or explanation of the error will be appreciated.
Regards,
Liesel

Hi,
Try to "Execute LUW" and unlock queue.
You can also activate and deactivate queue:
SXMB_ADM->Queue Management.
If this problem is related to queue then it will be solved here else try to read trace in SXMB_MONI and see where the problem is.
Regards,
Gourav

Similar Messages

Failed Entries not visible in EOIO inbound queue

Hi Experts,
The scenario is HTTP->RFC (aysnchornous) i am specifying the queue name in the HTTP client itself (inbound EOIO queue) and i am posting the message from HTTP client to RFC in R/3 system. So after posting the requests i could not find the messages in the queues ( the messages appears in SXMB_MONI with a queue name say XBOQ0_LINE1), but i could not find the entries in this queue at all... COuld you help me what could be the reasons.. Do we need to set any queue parameters for the MEssages to stay?.
Quick response would be highly helpful.
Thanks and Regards,
Raj

Hi Rajeev thanks for your reply, yes it stays in the queue as you said.. But the requirement of the client is that the RFC will be called in one sequence and it any of the transaction fails then all the others should automatically stops. Thats why we have taken up this method of selecting the inbound queue right from the HTTP service.. Now what we expect is that for example if the first message fails due to an exception in R/3 then all the others should wait in the queue.. But right now what is happening is that they are waiting at the adapter and SXMB_MONI shows that they are in the status scheduled.. (the R/3 system is up in this case.. )..
So you mean to say the message would log in the queue only when R/3 system is donw.. Or even when adapter makes max no of tries to R/3 and finds it as system failure then also would the entry come in the queue ?.
THanks in advance for your answer
Raj

QUEUE Error

Hi Everybody,
In SXMB_MONI, the inbound message got struck in the queue and I got the Queue Status as "Stop". The error message in SMQ2 is "SYSFAIL". How to resolve this?
Regards,
Prasad U

Hi Sasi,
I will tell you my whole scenario here under.
I need to post multiple IDOCs from a single flat file.
For that I have created one BPM to post Multiple IDOCs. Here I have used Java Pgm for Mapping. This mapping program will create a structure as that of IDOC. So we need two transasitions to do this.
One is from File to BPM and another one is from BPM to SAP System.
File to BPM is working fine and its status is success flag in SXMB_MONI. But for BPM to SAPSystem, I got struck. Even no error messages except that Queue Stop Message.
Even I have checked it in SXMB_ADM. There it doesnt contain the parameter for QRFC_RESTSRT_ALLOWED. This parameter is under subParameter.
Since I dont know anything in XI Admin, I am feared to touch those things. And tell me one thing, it seems that my scenario will come under TRFC, then how come I have to activate QRFC. Just tell me the difference btwn the two.
And also, if we do that(what you have said) will it be processed automatically or it will be mannually processed.
Regards,
Prasad U

A startup class to enable MQ Queues to trigger MDBs in WLS 6.1(sp4)

          Hi,
          I am hoping for references to documentation or opinions on the following method
          allowing the use of MQ queues to drive MDBs in WLS. The technique involves rebinding
          the connection factory in jndi at "weblogic.jms.MessageDrivenBeanConnectionFactory"
          with MQs connection factory.
          I read in various newsgroup posts that replacing WLS' ConnectionFactory with MQ's
          in a startup class will not allow MDBs to be linked to an MQ queue because startup
          classes are run after MDB deployment during startup. However I found some unused
          in-house code which appeared to do just that and it works.
          Here is the code in abbreviated form:
          public String startup(String str, Hashtable args) throws Exception
               bindMQFactory();
               bindMQQueues();
               return "";
          private void bindMQFactory() throws Exception
               // Create MQ Factory and configure it
               MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
               factory.setChannel(channel );
               factory.setHostName(host);
               factory.setPort(Integer.parseInt(port));
               factory.setQueueManager(qmanager);
               factory.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP );
               // bind connection factory into WLS JNDI for later use by clients
               _wlsContext.bind( connectionFactoryJndi, factory );
               // Force mq connection factory to be the one used for mdb's
               _wlsContext.rebind("weblogic.jms.MessageDrivenBeanConnectionFactory", factory);
          private void bindMQQueue() throws Exception
               // create queue and configure it
               MQQueue queue = new MQQueue();
               queue.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ );
               queue.setBaseQueueName( mqQueueName );
               // bind queue in WLS JNDI
               _wlsContext.bind( wlsJndi, queue );
          Thanks in advance for any comments or opinions on the above.
          regards
          Martin


Start with the white-paper:
          "Using Foreign JMS Providers with WebLogic Server"
          Note that to get transactional behavior you
          will need to use the WebLogic Messaging Bridge feature.
          Note that integrating MQ is easier in 8.1 - consider
          using WL 8.1 if you can.
          One more comment in-line.
          Martin wrote:
          > Hi,
          >
          > I am hoping for references to documentation or opinions on the following method
          > allowing the use of MQ queues to drive MDBs in WLS. The technique involves rebinding
          > the connection factory in jndi at "weblogic.jms.MessageDrivenBeanConnectionFactory"
          > with MQs connection factory.
          Not recommended. Highly not recommended. Do not use the same name
          as the internal factory. Create your own name for a CF, and change the
          weblogic ejb jar to reference your name. The above white-paper
          states how to do this.
          >
          > I read in various newsgroup posts that replacing WLS' ConnectionFactory with MQ's
          > in a startup class will not allow MDBs to be linked to an MQ queue because startup
          > classes are run after MDB deployment during startup. However I found some unused
          > in-house code which appeared to do just that and it works.
          >
          > Here is the code in abbreviated form:
          > public String startup(String str, Hashtable args) throws Exception
          > {
          >      bindMQFactory();
          >      bindMQQueues();
          >
          >      return "";
          > }
          >
          > private void bindMQFactory() throws Exception
          > {
          >
          >      // Create MQ Factory and configure it
          >      MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
          >      factory.setChannel(channel );
          >      factory.setHostName(host);
          >      factory.setPort(Integer.parseInt(port));
          >      factory.setQueueManager(qmanager);
          >      factory.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP );
          >
          >      // bind connection factory into WLS JNDI for later use by clients
          >      _wlsContext.bind( connectionFactoryJndi, factory );
          >
          >      // Force mq connection factory to be the one used for mdb's
          >      _wlsContext.rebind("weblogic.jms.MessageDrivenBeanConnectionFactory", factory);
          > }
          >
          > private void bindMQQueue() throws Exception
          > {
          >      // create queue and configure it
          >      MQQueue queue = new MQQueue();
          >      queue.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ );
          >      queue.setBaseQueueName( mqQueueName );
          >
          >      // bind queue in WLS JNDI
          >      _wlsContext.bind( wlsJndi, queue );
          > }
          >
          > Thanks in advance for any comments or opinions on the above.
          >
          > regards
          >
          > Martin

Replication Queue reader stopped due to Comm failure

Hello,
I have replication (subscription with updateable subscribers) (pull) running on sql 2008 subscriber with 5 sql 2000 publishers. all seem well except the Queue agent stops at loss of network connectivity. It dosen't appear to restart
until I manually restart it.   It will run for hours until it stops or a shorter period.   Usually, early in the morning before any server activity.
It is not all the Queue readers stopping at the same time, seems random.
I have looked for competing jobs or heavy server activity,   I do not see any.
Per the error logs it is a network loss. (the network is a VPN and is know to have short down times.) (mostly seconds. not hours) (this is the reason I am doing queued transactions)
Is there a way to have the queue agent restart itself if down or to keep trying to start until the problem clears.   if so what affect will it have on the publishers overhead.
Is there something else I am missing as I am fairly new to replication.
The other agents seem to just jug along doing their jobs and the trans actions are followed through.
Thanks for any help
Barry

Hi Barryb,
we have 2 options in job step properties for your scenario
1.one is retry attempts :Sets the number of times that SQL Server Agent attempts to retry a failed job step .
2.On failure action: Sets
the action for SQL Server Agent to perform if the job step fails.
Pls marked as answer if this is use full to you
Thanks and Regards,
Chandar

Queue smq2

Hi all,
Are all the entries in smq2 converted to XML (sxmb_moni) after the queue has been processed? Does that mean that 1 entry in the queue is equal to 1 IDOC? thanks for the info.
Regards,
IX

Hi,
No. This is not equal.
Look at this scenario: one file to multiple receivers.
Here the receiver determination determines the no of receiver.
Regards,
Boopathi

SMQ2 Queue sys.failed

HI all,
In CRM system SMQ2 queue name R3AD_ACCOUNTING is getting system failed.
When iam trying to unlock,activate and Execute those queue entries(5677) its not working i am getting the Message that FUNCTIONAL MODULE DOES NOT EXIT for this iam deleting the queue entries one by one after checking each one.
This queues are coming from R3 because of sale/service billing document post. when i check in SMW01 i didnt get any information related to this queue.
Is it any other way to solve this issue. How to resolve ?
Do the needful..
regards,
shoki.

HI,
when i check the queue entries i got the Functional module BAPI_CRM_SAVE,and queue name R3AD_ACCOUNTING, STATUS TEXT says that " Bdoc status failed,Bdoc not found".
system doesn't have dump errors too.
I came to know that when ever you get the message "Function module not found for this exception" for Queue entries we can delete that queue entry, but the problem is i have so many entries, Its not possible check one by one and delete?
sould i delete this all entries at once? Is it any solution?
Thanks,
shoki

Document on the queues

Hi
we have recently installed the SAP 7.0.. just been wondering like if any one document on how to set up the queues and what are main points we need to be considered while configuring the queues..
SV

1) clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them
2)You may need to re-register your queues.
Follow SXMB_ADM -> Manage Queues -> Deregister Queues
Afterwards, re-register the queues and activate from the same screen
3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.
4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.
if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.
a double click on the entry shall take you to detailed list.
if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.
if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.
5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.
If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .
GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.
Now go to SMQ3, right click on the queue and give Restore LUW.
6)this basically means tht message is waiting in the queue.
in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue
If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.
7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.
Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.
This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.
If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.

Queue's have to be unlocked again and again in ECC

Hi All,
We are facing a issue in ECC, that when ever a new message comes in ECC, the queue gets locked and we have to unlock it again and again. The queue gets into Ready state and they have to be unlocked using unlock button on top in SMQR TXN.
I have tried selecting all queues and regestring them again but it doesn't help.
please advice.
XIer

queues are locked when the load to the processor is hight..and the second task is in queue while first one is processing at that time..secodn process will be locked after some time..extent
1) clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them
2)You may need to re-register your queues.
Follow SXMB_ADM -> Manage Queues -> Deregister Queues
Afterwards, re-register the queues and activate from the same screen
3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.
4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.
if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.
a double click on the entry shall take you to detailed list.
if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.
if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.
5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.
If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .
GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.
Now go to SMQ3, right click on the queue and give Restore LUW.
6)this basically means tht message is waiting in the queue.
in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue
If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.
7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.
Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.
This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.
If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.
AND
Due to connection failure or some other system failure the queue will stop...
If once any failure in the queue then after posting msg also stop...
so that we need to run the 3 reports in Xi system..
it will automate the queue process if any error accure ...
If periodicaly u ill run this reports then the reports will Automate your failure messages ..
Trfc- RSQIWKEX
Qrfc RSARFCEX
OtherErrors- RSXMB_RESTART_MESSAGES...

Why the queue is locked in SMQ2?

Sometimes,I find the queue would be locked in SMQ2 ,so i have to release the locked queue so that it can keep on working normally.
I'd like to know what reason can cause the queue locked ?Once the queue is locked,how to get the notificaion?
thanks in advance.
Regards,
brand

Hi
queues are locked when the load to the processor is hight..and the second task is in queue while first one is processing at that time..secodn process will be locked after some time..extent
1) clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them
2)You may need to re-register your queues.
Follow SXMB_ADM -> Manage Queues -> Deregister Queues
Afterwards, re-register the queues and activate from the same screen
3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.
4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.
if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.
a double click on the entry shall take you to detailed list.
if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.
if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.
5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.
If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .
GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.
Now go to SMQ3, right click on the queue and give Restore LUW.
6)this basically means tht message is waiting in the queue.
in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue
If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.
7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.
Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.
This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.
If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.

Exception sending objc_msgsend-style notification in [LibraryItemMetadata parseApplicationsForLibraryItemMetadataID:15]

I am getting the above error following my migration to Mavericks and OS X Server 3. A section of the devicemagrd log is as follows:
0:: [135] [2013/11/06 09:31:14.075] Caught exception sending objc_msgsend-style notification <PGDatabaseNotification:0x7fec7a722800> [channel: 'objc_send', message: '[LibraryItemMetadata parseApplicationsForLibraryItemMetadataID:15]']. -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
0:: [135] [2013/11/06 09:31:14.077] EXCEPTION: Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
    )">
0:: [135] [2013/11/06 09:31:14.078] EXCEPTION: Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
    )">
    USERINFO: {
        SQLSTATE = 25P02;
        errorMessage = "ERROR: current transaction is aborted, commands ignored until end of transaction block\n";
    BACKTRACE:
    ? | 4529649120
    ? | 4529622700
    ? | 4529619667
    ? | 4529620941
    ? | 4529655520
    ? | 4529536613
    ? | 140735424659541
    ? | 140735424525713
    ? | 140735424524859
    ? | 140735529837229
    ? | 140735529846415
    ? | 140735529851357
    ? | 140735529844643
    ? | 140735529849235
    ? | 140735512129272
0:: [135] [2013/11/06 09:31:14.078] Caught unhandled exception -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
0:: [135] [2013/11/06 09:31:14.078] Caught exception processing queued DB notification: -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
0:: [135] [2013/11/06 09:31:24.716] EXCEPTION: Postgres <-[PGConnection executeSQL:withParams:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:432): "Postgres error 22001 (ERROR: value too long for type character varying(63)
    )">
0:: [135] [2013/11/06 09:31:24.718] EXCEPTION: Postgres <-[PGConnection executeSQL:withParams:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:432): "Postgres error 22001 (ERROR: value too long for type character varying(63)
    )">
    USERINFO: {
        SQLSTATE = 22001;
        errorMessage = "ERROR: value too long for type character varying(63)\n";
    BACKTRACE:
    ? | 4529653189
    ? | 4529505852
    ? | 4529569378
    ? | 4529459335
    ? | 4529468107
    ? | 140735386406380
    ? | 140735386405972
    ? | 140735387072422
    ? | 4529499762
    ? | 4529539373
    ? | 4529537070
    ? | 4529655302
    ? | 4529536613
    ? | 140735424659541
    ? | 140735424525713
0:: [135] [2013/11/06 09:31:24.718] EXCEPTION: Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
    )">
0:: [135] [2013/11/06 09:31:24.719] EXCEPTION: Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
    )">
    USERINFO: {
        SQLSTATE = 25P02;
        errorMessage = "ERROR: current transaction is aborted, commands ignored until end of transaction block\n";
    BACKTRACE:
    ? | 4529649120
    ? | 4529490998
    ? | 4529461096
    ? | 4529468107
    ? | 140735386406380
    ? | 140735386405972
    ? | 140735387072422
    ? | 4529499762
    ? | 4529539373
    ? | 4529537070
    ? | 4529655302
    ? | 4529536613
    ? | 140735424659541
    ? | 140735424525713
    ? | 140735424524859
0:: [135] [2013/11/06 09:31:24.720] Caught exception sending objc_msgsend-style notification <PGDatabaseNotification:0x7fec7a673740> [channel: 'objc_send', message: '[LibraryItemMetadata parseApplicationsForLibraryItemMetadataID:15]']. -[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
0:: [135] [2013/11/06 09:31:24.721] EXCEPTION: Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
    )">
0:: [135] [2013/11/06 09:31:24.723] EXCEPTION: Postgres <-[PGConnection executeCSQL:] (/SourceCache/RemoteDeviceManagement/RemoteDeviceManagement-848.17/Compiled/Fra mework-Models/Postgres/PGConnection.m:323): "Postgres error 25P02 (ERROR: current transaction is aborted, commands ignored until end of transaction block
    )">
    USERINFO: {
        SQLSTATE = 25P02;
        errorMessage = "ERROR: current transaction is aborted, commands ignored until end of transaction block\n";
    BACKTRACE:
    ? | 4529649120
    ? | 4529622700
    ? | 4529619667
    ? | 4529620941
    ? | 4529655520
    ? | 4529536613
    ? | 140735424659541
    ? | 140735424525713
    ? | 140735424524859
    ? | 140735529837229
    ? | 140735529846415
    ? | 140735529851357
    ? | 140735529844643
    ? | 140735529849235
    ? | 140735512129272
This repeats continously. During the upgrade process, I encountered the missing devices issue described in https://discussions.apple.com/thread/5467701?start=0&tstart=0 which I fixed using the terminal commands given in that thread to remove the legacy installed applications data. I then encountered the null pointer issue described in https://discussions.apple.com/thread/5471963?start=0&tstart=0, which also was fixed via the terminal commands given in that thread. I have opened Bug Report # 15405799 on this issue.

Back up all data to at least two different storage devices, if you haven't already done so. The backups can be made with Time Machine or with a mirroring tool such as Carbon Copy Cloner. Preferably both.
Boot into Recovery (command-R at startup), launch Disk Utility, and erase the startup volume with the default options.This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For details of how this works, see here:
Using Setup Assistant
Transfer only "Users" and "Settings" – not "Applications" or "Other files." Don't transfer the Guest account, if it was enabled on the old system. Test. If the problem is still there, you have a hardware fault. Take the machine to an Apple Store for diagnosis.
If the problem is resolved, reinstall your third-party software cautiously. Self-contained applications that install into the Applications folder by drag-and-drop or download from the App Store are safe. Anything that comes packaged as an installer or that prompts for an administrator password is suspect, and you must test thoroughly after reinstalling each such item to make sure you haven't restored the problem.
Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

What is queue Control

Hi All,
I read like if ICM goes down , requests will continue to run
normally, except for 'queue control' requests.
What is queue control requests. what is queue control actually mean?
Thanks
Mavrick

What is queue control requests. what is queue control actually mean?Means concurrent programs that control the CMs (like startup/shutdow CM).
Query FND_CONCURRENT_PROGRAMS table (QUEUE_CONTROL_FLAG column to verify) -- See eTRM and "What FND Tables Store All Concurrent Program Information Details? [ID 462063.1]" for details.
Thanks,
Hussein

Cannot start Trex queue service

My /usr/sap/ file system was 100% full ad now I get a core file when starting Trex. All the services start, EXCEPT the queue server. The queue server is creating a core file.

Hello Tim,
I had the same space issue during Trex indexing that the file system was full. We created enough space and started the TREX server and found that a core file was getting created and the Que server was not started. But all other services were started well. When I looked into the /usr/sap/trex_02/trace folder I found the following messages on file TrexQueueServer.0000001077486.000.trc
[03085] 2010-09-03 12:37:13.317 e Q4c7e99f05 Queue.cpp(00262) : Queue::open: unclean shutdown for queue '4c7e99f054360096e1008002a20989b0dh3300' detected, repairing
[03085] 2010-09-03 12:37:13.327 e TREX_C_STORE FileHandle.cpp(01259) : FHW::open restore offset file
[03085] 2010-09-03 12:37:13.327 e TREX_C_STORE FileHandle.cpp(01260) : + filename: /usr/sap/trex_02/queue/4c7e99f054360096e1008002a20989b0dh3300/contentStore.write
After that I deleted the core file, deleted the index file and Que file and restarted the TREX server. Now all the services are running fine.
Logged into the E-recruiting System and via transaction skpr07 recreated the index. Now new index and Que files were created and the problem solved.
You shall try this.
Thanks

Connecting Flight Demo not work

Hi, all
I configed the multi-booking flight demo according to the Guide. After I executed the sample, I can't see any error from the SXMB_MONI except 'Outbound Status' column is a red flag.
The page showing 'Flight booking order sent. Awaiting confirmation. ' all the time.
Could anyone help me on this?

Yes, I checked that post when I config the first sigle flight DEMO.
I am using BPM, and this is the first time for me.
In <Monitor for Processed XML Messages>, I got the error message 'message has error outbound side'. I go into the <Event Queue Browser>, the event status shows 'Waiting because of e'. After I click the 'Deliver' button, the outbound flag changed to green color, and the message changed to 'message scheduled on outbound side'.
I registerd all the Queues, and the integration process return code in XI runtime cache is zero.
Anyone can help??

Lack of randomness in my threads

Hi, I have the following code:
import java.util.Collections;
import java.util.List;
import java.util.LinkedList;
import java.util.Iterator;
public class ThreadSafeCollection {
     public static void main(String args[]) throws Exception {
          List queue = Collections.synchronizedList(new LinkedList());
          LinkedList threads = new LinkedList();
          int i = 0;
          while(i < 25) {
               threads.add(new InsertMessages("Thread" + i, queue));
               i++;
          Iterator iterator = threads.iterator();
          while(iterator.hasNext()) {
               ((InsertMessages)iterator.next()).start();
          Thread.sleep(2000);
          System.out.println("threads contains " + threads.size());
          System.out.println("queue contains " + queue.size() + " items.");
class InsertMessages extends Thread {
     List queue;
     final static int maxIterations = 10;
     public InsertMessages(String threadName, List queue) {
          super(threadName);
          this.queue = queue;
     public void run() {
          int iterations = 0;
          try {
               Thread.sleep((int)Math.random() * 1000);
          catch(InterruptedException e) {
               System.err.println("something");
          while(iterations < maxIterations) {
               queue.add(getName() + " at iteration " + iterations);
               iterations++;
This above code produce the following results for the queue:
Thread0 at iteration 0, Thread0 at iteration 1, Thread0 at iteration 2, Thread0 at iteration 3, Thread0 at iteration 4, Thread0 at iteration 5, Thread0 at iteration 6, Thread0 at iteration 7, Thread0 at iteration 8, Thread0 at iteration 9, Thread1 at iteration 0, Thread1 at iteration 1, Thread1 at iteration 2, Thread1 at iteration 3, Thread1 at iteration 4, Thread1 at iteration 5.....
My problem is that the Thread execute in order from 1 to 10. This seems very deterministic. I expected more randomness. i.e. I expected the order of thread execution to be something like this: Thread3, Threads8, Thread1, Thread7... Any ideas why this is happening?
Thanks,
Paul0al

This is happening because you are inserting the threads into this list, then you are starting them in the same order. So one starts, runs, sleeps, the second starts, runs, sleeps, etc... So of course they go in order. However, if you left it running a long time, it's not impossible that due to factors beyond your control, one thread might sleep a little longer or shorter and therefore cause the threads to start running in different orders, but even that will likely remain in the same different order for some period of time.
If you really are wanting to start them in any order, then put the threads in a collection that doesn't guaranty an order (like Hashtable) and then get an iterator and start them. The other thing to do would be to start threads and have the sleep time be some random value each time to.

Sxmb_moni exception in queue - noinst

Similar Messages

Maybe you are looking for