IDOC Process Stops Due To System Warning

Hello Friends,
Here is the ALE inbound scenario: We are setting up an order BOM interface using idoc BOMORD01. During the test, we found that the idoc has the error status 51 and this was due to a warning message issued by the system. In dialog mode (CS61 or CS62), we press enter to confirm the warning and thereby continue with the transaction. <b>The ALE process treats this API-warning as an error and stops.</b>
How can this be handled/resolved? Please help me out!
Thanks,
Sam

This turned out to be data problem. Of course, SAP's error message was not helpful.
We had to report this to SAP and they found the problem after some debugging.

Similar Messages

TS3048 My MacBook OSX 10.6.8 detects the wireless keyboard apple A1255 but once the passkey is ask the "pairing" process stops and displays a warning saying it was unsuccessful. Bateries are new on the keyboard and it has been paired to this MacBook .

My MacBook OSX 10.6.8 detects the wireless keyboard apple A1255 but once the passkey step show on the screen the "pairing" process stops and displays a warning saying it was unsuccessful. Bateries are new on the keyboard and it has been paired to this MacBook before. Mouse, iphone and other bluertooth devices have no problem pairing via bluetooth. Any suggestions where to look?

I read somwhere that firefox disables certain versions of java because it might give control of your computer to other malicious websites
I think you have to go to the java website and down load the version you need and enable it in firefox's prefrences
Sorry I may be a veteran in using firefox, but I know very little since I hardly had problems with mozilla untill just very recently hope this helps

HT4972 After the process stops due to a "corrupted" download of the new iOS file, why does the second try repeat the ten-hour backup process?

After the process stops due to a "corrupted" download of the new iOS file, why does the second try repeat the ten-hour backup process? I am doing this on the latest iTunes, and a Windows XP computer.

After the process stops due to a "corrupted" download of the new iOS file, why does the second try repeat the ten-hour backup process? I am doing this on the latest iTunes, and a Windows XP computer.

IDOC processing inbound in receiver system , transaction WE57

Hello,
possibly a simple question for those who are familar with IDOC processing.
In transaction WE57 you can add function modules for processing IDOCs e.g. inbound IDOCs.
Now I see in our system that there are two function modules added to the same IDOC.
Example Basis type MATMAS03:
Function modules: IDOC_INPUT_MATMAS01 and IDOC_INPUT_MATMASMDM.
We want to add an individual mapping on receiver side (not on XI, because it has to be accessible to a user group on receiver side to change required field contents sometimes) for fields which are empty.
My idea is that we can add a func.module here in WE57 for this purpose. But what about the existing two FMs?
Will they be processed in a sequence so that we can add more FMs to the same IDOC type?
Or should I replace one of them with a Z_IDOC_INPUT_MATMASxxx by copying it and adding the required functionality?
Any help is appreciated!
Regards
Dirk

Hi Dirk,
Will they be processed in a sequence so that we can add more FMs to the same IDOC type?
I dont think ....
BTW you would get better response if you post the question in ABAP forum.
https://www.sdn.sap.com/irj/sdn/abap-forums
Regards,
Sumit

What does it mean when your imovie formatting process stops due to "not enough room in heap zone /"? Thanks.

I am trying to make an imovie from 369 slides I scanned to my computer. I have the slides in order with titles and music attached. The next step was formatting it before burning to the DVD. About 2 hours into the formatting process, it stopped with a message that said "error" and "not enough room in heap zone /" I don't know what the heap zone is and what to do next. Thanks for any help.

I am asking the moderators of the forum to move this discussion to the iMovie forum for fastest assistance with this question. Good luck

Why does firefox stop loading then when i close it and try to open it up again I keep getting this message:Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system

Firefox will just stop loading/ connecting to the internet. The gray circle will just continually move but it never turns green to load the pages. I know it's not my internet because my internet explorer works just fine while this is happening to firefox. So I close firefox and then try to re open it but I get the message: Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system. So I wait a little bit then try and re open it and still get the same message. I then go into my windows task manager and try and end the firefox proccess but it won't end. So I restart my computer and firefox eventually starts acting up again.

For possible causes of this error, and how to troubleshoot it see [[Firefox is already running but is not responding]].

Problem description: My iMac (early 2008) with OS 10.10.2 runs slow. I have run EtreCheck several times, and I am unable to move beyond Problem System Launch Agents (11 processes killed due to memory pressure) and Launch Daemons (12 processes killed

Problem description:
My iMac (early 2008) with OS 10.10.2 runs slow. I have run EtreCheck several times, and I am unable to move beyond Problem System Launch Agents (11 processes killed due to memory pressure) and Launch Daemons (12 processes killed).
EtreCheck version: 2.1.8 (121)
Report generated April 14, 2015 at 9:50:48 AM EDT
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Click for support] links for help with non-Apple products.
Click the [Click for details] links for more information about that line.
Hardware Information: ℹ️
    iMac (24-inch, Early 2008) (Verified)
    iMac - model: iMac8,1
    1 3.06 GHz Intel Core 2 Duo CPU: 2-core
    4 GB RAM Upgradeable
        BANK 0/DIMM0
            2 GB DDR2 SDRAM 800 MHz ok
        BANK 1/DIMM1
            2 GB DDR2 SDRAM 800 MHz ok
    Bluetooth: Old - Handoff/Airdrop2 not supported
    Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
    NVIDIA GeForce 8800 GS - VRAM: 512 MB
        iMac 1920 x 1200
System Software: ℹ️
    OS X 10.10.2 (14C1510) - Time since boot: 4 days 20:29:22
Disk Information: ℹ️
    Hitachi HDS721010KLA330 disk0 : (1 TB)
        EFI (disk0s1) <not mounted> : 210 MB
        Mac iBook HD (disk0s2) / : 999.35 GB (521.60 GB free)
        Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
USB Information: ℹ️
    Apple Inc. Built-in iSight
    Apple, Inc. Keyboard Hub
        Apple, Inc Apple Keyboard
    Apple Computer, Inc. IR Receiver
    Apple Inc. BRCM2046 Hub
        Apple Inc. Bluetooth USB Host Controller
Configuration files: ℹ️
    /etc/sysctl.conf - Exists
Gatekeeper: ℹ️
    Mac App Store and identified developers
Problem System Launch Agents: ℹ️
    [killed]    com.apple.CallHistoryPluginHelper.plist
    [killed]    com.apple.CallHistorySyncHelper.plist
    [killed]    com.apple.coreservices.appleid.authentication.plist
    [killed]    com.apple.icloud.fmfd.plist
    [killed]    com.apple.Maps.pushdaemon.plist
    [killed]    com.apple.printtool.agent.plist
    [killed]    com.apple.SafariNotificationAgent.plist
    [killed]    com.apple.sbd.plist
    [killed]    com.apple.scopedbookmarkagent.xpc.plist
    [killed]    com.apple.telephonyutilities.callservicesd.plist
    [killed]    com.apple.warmd_agent.plist
    11 processes killed due to memory pressure
Problem System Launch Daemons: ℹ️
    [killed]    com.apple.AssetCacheLocatorService.plist
    [killed]    com.apple.ctkd.plist
    [killed]    com.apple.emond.aslmanager.plist
    [killed]    com.apple.icloud.findmydeviced.plist
    [killed]    com.apple.ifdreader.plist
    [killed]    com.apple.nehelper.plist
    [killed]    com.apple.nesessionmanager.plist
    [killed]    com.apple.periodic-daily.plist
    [killed]    com.apple.periodic-weekly.plist
    [killed]    com.apple.softwareupdate_download_service.plist
    [killed]    com.apple.wdhelper.plist
    [killed]    org.cups.cupsd.plist
    12 processes killed due to memory pressure
Launch Agents: ℹ️
    [not loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [running]    com.adobe.AdobeCreativeCloud.plist [Click for support]
Launch Daemons: ℹ️
    [loaded]    com.adobe.fpsaud.plist [Click for support]
    [loaded]    com.adobe.SwitchBoard.plist [Click for support]
    [running]    com.arubanetworks.via.NetworkMonitorLaunchd.plist [Click for support]
    [loaded]    com.microsoft.office.licensing.helper.plist [Click for support]
User Launch Agents: ℹ️
    [loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [loaded]    com.adobe.ARM.[...].plist [Click for support]
    [loaded]    com.adobe.ARM.[...].plist [Click for support]
    [loaded]    com.google.keystone.agent.plist [Click for support]
    [running]    com.spotify.webhelper.plist [Click for support]
User Login Items: ℹ️
    ChronoSyncBackgrounder    Application (/Library/Application Support/ChronoSync/ChronoSyncBackgrounder.app)
    Dropbox    Application (/Applications/Dropbox.app)
    Canon IJ Network Scanner Selector2    Application Hidden (/Library/Printers/Canon/IJScanner/Utilities/Canon IJ Network Scanner Selector2.app)
    Google Drive    Application (/Applications/Google Drive.app)
Internet Plug-ins: ℹ️
    Google Earth Web Plug-in: Version: 6.1 [Click for support]
    Default Browser: Version: 600 - SDK 10.10
    AdobeExManDetect: Version: AdobeExManDetect 1.1.0.0 - SDK 10.7 [Click for support]
    Flip4Mac WMV Plugin: Version: 3.1.0.24   - SDK 10.8 [Click for support]
    OVSHelper: Version: 1.1 [Click for support]
    AdobeAAMDetect: Version: AdobeAAMDetect 2.0.0.0 - SDK 10.7 [Click for support]
    AdobePDFViewerNPAPI: Version: 11.0.10 - SDK 10.6 [Click for support]
    DivX Web Player: Version: 3.2.4.1250 - SDK 10.6 [Click for support]
    FlashPlayer-10.6: Version: 17.0.0.134 - SDK 10.6 [Click for support]
    Flash Player: Version: 17.0.0.134 - SDK 10.6 Outdated! Update
    iPhotoPhotocast: Version: 7.0
    QuickTime Plugin: Version: 7.7.3
    SharePointBrowserPlugin: Version: 14.4.8 - SDK 10.6 [Click for support]
    AdobePDFViewer: Version: 11.0.10 - SDK 10.6 [Click for support]
    Silverlight: Version: 5.1.20913.0 - SDK 10.6 [Click for support]
    JavaAppletPlugin: Version: 15.0.0 - SDK 10.10 Check version
User internet Plug-ins: ℹ️
    WebEx: Version: 1.0 [Click for support]
    Google Earth Web Plug-in: Version: 7.1 [Click for support]
3rd Party Preference Panes: ℹ️
    Adobe Version Cue CS2 [Click for support]
    Flash Player [Click for support]
    Flip4Mac WMV [Click for support]
    VIA PrefPane [Click for support]
Time Machine: ℹ️
    Time Machine not configured!
Top Processes by CPU: ℹ️
         3%    WindowServer
         3%    Mail
         2%    com.apple.iCloudHelper
         1%    Creative Cloud
         1%    Google Chrome
Top Processes by Memory: ℹ️
    223 MB    Google Chrome
    150 MB    Finder
    129 MB    Google Chrome Helper
    112 MB    Mail
    69 MB    Google Drive
Virtual Memory Information: ℹ️
    35 MB    Free RAM
    1.45 GB    Active RAM
    1.45 GB    Inactive RAM
    888 MB    Wired RAM
    27.01 GB    Page-ins
    851 MB    Page-outs

When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

How to stop the duplicate idoc processing ? whar need to done SAP R/3

Hi All
If the Same Idoc is processed to SAP R/3 then what to do for not processing
the duplicate IDOC ?
Or some thing like this...
If by mistake same idoc processed then how to avoid to process the idoc?
what i need to in SAP R/3 side?
Regards
Kiran lvs

Hi
some thing like this:Using T.code: we19 ...Idoc processed a day ago
                                       today by using the same t.code we19 ..processed the
                                       same idoc, what i sent a day ago.
                                       Here how to stop this duplicate processing ?
I hope this is clear...else pl put a note
regards
Kiran lvs

Suppress Warning/Information Messages in Idoc Processing

Hi,
Is there any way through which I can suppress all the warning/information messages in Inbound Idoc processing.
I was trying to create some Sales Orders from Idocs. But, the problem is Idoc is getting failed with status as 51 and displays the status message as the warning/information message that has been written in the userexit. However, the Sales Order is getting saved successfully.
Is there any setting through which I can override this?
Thanks in advance.
-Babu Kilari

@ Brad....
It is working in our development box and not in testing box. So, do you think this is an issue ?
@ Bhat.....
I tried the way you said. But, it didnt help.
Any other help will be appreciated!!!
Thanks in advance
-Babu Kilari

I get this warning on firefox a lot...."Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.

'''''Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.''''' this is a message I get a lot. Whats happening? Thanks Tony'

See "Hang at exit":
* http://kb.mozillazine.org/Firefox_hangs
* https://support.mozilla.com/kb/Firefox+hangs

Server stopped due to start up failure

hi!
i have downloaded and installed j2ee sdk without any problems.
however when i start the server it closes itself.
at the end of the log file it says:
" [#|2005-07-13T09:54:37.267+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]"
the whole log file is below. can anybody help?
ps: i am a beginner.
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2005-07-13T09:52:32.438+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2005-07-13T09:52:36.413+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2005-07-13T09:52:37.104+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-07-13T09:52:46.137+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2005-07-13T09:52:46.187+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2005-07-13T09:52:46.237+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-07-13T09:52:54.299+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2005-07-13T09:52:59.106+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2005-07-13T09:53:02.210+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2005-07-13T09:53:05.565+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2005-07-13T09:53:05.856+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2005-07-13T09:53:05.956+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2005-07-13T09:53:05.986+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2005-07-13T09:53:07.007+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1022:Deployment failed - Detailed Message:
com.sun.enterprise.admin.common.exception.ServerInstanceException
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getVirtualServerHostAndPort(ApplicationsConfigMBean.java:2133)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.setHostAndPort(ApplicationsConfigMBean.java:3038)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:274)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:53:07.017+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear. -- null -- null|#]
[#|2005-07-13T09:53:07.097+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-07-13T09:53:07.097+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2005-07-13T09:53:07.117+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1022:Deployment failed - Detailed Message:
com.sun.enterprise.admin.common.exception.ServerInstanceException
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getVirtualServerHostAndPort(ApplicationsConfigMBean.java:2133)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.setHostAndPort(ApplicationsConfigMBean.java:3038)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:274)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:53:07.127+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear. -- null -- null|#]
[#|2005-07-13T09:53:07.137+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-07-13T09:53:07.298+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2005-07-13T09:53:08.900+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2005-07-13T09:53:10.683+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2005-07-13T09:53:10.693+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-07-13T09:53:10.743+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2005-07-13T09:53:10.803+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2005-07-13T09:53:10.803+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2005-07-13T09:53:11.363+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2005-07-13T09:53:25.003+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2005-07-13T09:53:32.724+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2005-07-13T09:53:32.864+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2005-07-13T09:53:33.916+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2005-07-13T09:53:33.946+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2005-07-13T09:53:34.006+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2005-07-13T09:53:34.026+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Sun\AppServer\imq\var\instances|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-07-13T09:54:36.326+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
     at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
     at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
     at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
     at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
     ... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:452)
     at java.net.Socket.connect(Socket.java:402)
     at java.net.Socket.<init>(Socket.java:309)
     at java.net.Socket.<init>(Socket.java:124)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
     ... 25 more
|#]
[#|2005-07-13T09:54:36.326+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
[#|2005-07-13T09:54:36.336+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 8080 server:type=ThreadPool,name=http8080|#]
[#|2005-07-13T09:54:36.506+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 1043 server:type=ThreadPool,name=http1043|#]
[#|2005-07-13T09:54:36.536+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 4848 server:type=ThreadPool,name=http4848|#]
[#|2005-07-13T09:54:37.027+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-07-13T09:54:37.057+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-07-13T09:54:37.057+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:364)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:54:37.267+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]

Hi,
Did you resolve this issue? I have the same problem. I appreciate if you could please let me know what the problem was.
Thanks

Time Machine stops due to computer going into Sleep/Hibernation Mode

Time Machine stops due to computer going into Sleep/Hibernation Mode then restarts to try to start the Back up process again and again vicious cycle. I have made sure all settings are turned off. I have done one or two backups since the initial first backup. My HDD is almost full and I want it backed up before I try to clone/mirror the drive to upgrade it to a 1TB HDD. Thank you in advance.

Set the Energy Saver (in System Preferences) to Never. Then reset the NVRAM, as follows:
Shut down your Mac.
Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the third time.
Release the keys.

Idoc processing best practices - use of RBDAPP01 and RBDMANI2

We are having performance problems in the processing of inbound idocs. The message type is SHPCON, and transaction volume is very high. I am a functional consultant, not an ABAP developer, but will try my best to explain our current setup.
1)     We have a number of message variants for the inbound SHPCON message, almost all of which are set to trigger immediately upon receipt under the Processing by Function Module setting.
2)      For messages that fail to process on the first try, we have a batch job running frequently using RBDMANI2.
We are having some instances of the RBDMANI2 almost every day which get stuck running for a very long period of time. We frequently have multiple SHPCON idocs coming in containing the same material number, and frequently have idocs fail because the material in the idoc has become locked. Once the stuck batch job is cancelled and the job starts running again normally, the materials unlock and the failed idocs begin processing. The variant for the RBDMANI2 batch job is currently set with a packet size of 1 and without parallel processing enabled.
I am trying to determine the best practice for processing inbound idocs such as this for maximum performance in a very high volume system. I know that RBDAPP01 processes idocs in status 64 and 66, and RBDMANI2 is used to reprocess idocs in all statuses. I have been told that setting the messages to trigger immediately in WE20 can result in poor performance. So I am wondering if the best practice is to:
1)     Set messages in WE20 to Trigger by background program
2)     Have a batch job running RBDAPP01 to process inbound idocs waiting in status 64
3)     Have a periodic batch job running RBDMANI2 to try and clean up any failed messages that can be processed
I would be grateful if somebody more knowledgeable than myself on this can confirm the best practice for this process and comment on the correct packet size in the program variant and whether or not parallel processing is desirable. Because of the material locking issue, I felt that parallel processing was not desirable and may actually increase the material locking problem. I would welcome any comments.
This appeared to be the correct area for this discussion based upon other discussions. If this is not the correct area for this discussion, then I would be grateful if the moderator could re-assign this discussion to the correct area (if possible) or let me know the best place to post it. Thank you for your help.

Hi Bob,
Not sure if there is an official best practice, but the note 1333417 - Performance problems when processing IDocs immediately does state that for the high volume the immediate processing is not a good option.
I'm hoping that for SHPCON there is no dependency in the IDoc processing (i.e. it's not important if they're processed in the same sequence or not), otherwise it'd add another complexity level.
In the past for the high volume IDoc processing we scheduled a background job with RBDAPP01 (with parallel processing) and RBDMANIN as a second step in the same job to re-process the IDocs with errors due to locking issues. RBDMANI2 has a parallel processing option, but it was not needed in our case (actually we specifically wouldn't want to parallel-process the errors to avoid running into a lock issue again). In short, your steps 1-3 are correct but 2 and 3 should rather be in the same job.
Also I believe we had a designated server for the background jobs, which helped with the resource availability.
As a side note, you might want to confirm that the performance issues are caused only by the high volume. An ABAPer or a Basis admin should be able to run a performance trace. There might be an inefficiency in the process that could be adding to the performance issue as well.
Hope this helps.

Question regarding XI/PI and Idoc processing.

Hi,
I'm learning XI/PI and I have a question regarding Idoc processing in PI.
We need to configure communication between our BW system and our PI system using Idocs.
The Idocs are sent from BW to our PI systems and are then sent back to the BW system, there are no third system involved. The idocs are only between PI and BW.
Our BW system is already connected with many other R3 systems by using WE20 / WE21 and RFC's and everything works perfectly.
While I configure this communication between BW and PI it seems that PI is passing the Idoc to the Idoc adapter, converts it to xml and tries to find a receiver for the particular Idoc. I see the error "NO_RECEIVER_CASE_ASYNC" in SXMB_MONI.
Is this a normal behaviour in PI ? Why is PI thinking that the Idoc needs to be sent to another system when it is infact for itself ??
Thanks and regards
Remi

Hi
for error "NO_RECEIVER_CASE_ASYNC" in SXMB_MONI.
This problem may occur due to one of following reasons, so check
1 service is active in message? transaction SICF and activate service sap/xi/engine (right click, activate)
2 Is the port 8001 defined in the services on the smicm under services?
3 Check the roles assign PIDIRUSER
http://help.sap.com/saphelp_nw04/helpdata/en/56/361041ebf0f06fe10000000a1550b0/content.htm
role: SAP_XI_ID_SERV_USER attached to it
Also Check Whether PIDIRUSER has following role
SAP_SLD_CONFIGURATOR
SAP_XI_RWB_SERV_USER
SAP_XI_RWB_SERV_USER_MAIN
Regards
Abhishek

Performance improvement for ALE/IDOC processing

Dear experts,
Could you let me know any information to tune performance?
In our system (SAP R/3 Enterprise 6.20), material master data is distributed from one client to other clients in the same instance. It is because material master is maintained centrally, and is distributed to other clients for member companies.
During the night batch, distributing master data takes more than 2 hours. Although the distribution usually finishes without errors, we would like to explore ways to improve processing performance. Especially, program RBDMIDOC runs long time to create IDOC for MATMAS, even 0 master IDOC is set eventually.
OSS notes of the list for OS/DB/SAP parameters related to ALE/IDOC, tips in organizing batch jobs, etc, will be very appreciated.
Many Thanks,
Nori

I'd recommend to profile the program at least once to see where there's possible room for improvements. I.e. an ABAP runtime analysis and SQL trace would be good for a start. You can check out the links in thread Please Read before Posting in the Performance and Tuning Forum, which will give you some references if you need them. Once you have more details, you either know what you need to do or you can provide them and ask a more specific question (and thus you will receive much better answers).
As a general remark though I've seen often poor performance initially on the changer pointer selection, because there are too many entries in the table (due to system generating unnecessary change pointers, which should be disabled or/and lack of proper reorganization, i.e. deletion of old/processed change pointers via BD22). Sounds like this is most likely also the cause of your problem, because otherwise it's hard to explain long run times without generating any master IDocs. You can check the number of change pointers easily via view BDCPV or BDCP2 - it depends how you store your change pointers (most likely you find them via view BDCPV in a 6.20 system, unless somebody switched it to the newer BDCP2).
If you still have them in BDCPV (or the underlying tables to be more precise), check out [OSS note 305462 - MOD: Migration change pointer to table BDCP2|https://service.sap.com/sap/support/notes/305462], which will provide you a general hint how to do that (and thus also improve the performance). However, if you're currently not deleting any old change pointers, you should ensure that a regular job runs for transaction BD22 (program RBDCPCLR). You'll easily find other (possibly relevant) OSS notes by doing a search yourself...

IDOC Process Stops Due To System Warning

Similar Messages

Maybe you are looking for