DEBUG MESSAGE: new exception propagation across deoptimization

Greetings,
we're detecting the following error in our server logs:
"DEBUG MESSAGE: new exception propagation across deoptimization has not been tested yet "
Has anybody seen this message before?
Could it be coming from the JVM?
Thanks and apologies in advance if this is not the appropriate forum for this question,
george.

"exception propagation across deoptimization" sounds like a very HotSpot VM-specific words, referring to some complex internal mechanisms that it uses. However, it's very surprising if a production JVM prints them for a production program. To make sure it's really emitting this message, you can probably download the JVM source code from JVM and grep it for this phrase...

Similar Messages

MD07 and new exception messages

Hello,
Is it possible to add the new exception messages in MD07 transaction (e.g. ND type materials).
Idea is to sort the materials with new sales order created. As of now I can sort materials below the safty stock and few others.
I have found FM
MD_STOCK_REQUIREMENTS_LIST_API and
Program: RMMD07EX and RMMD07DB
But still have to explore.
Please suggest !
regards,
JPS

Hi,
1. I dont think that you will be able to add any new exception messages.
2. Reg the Function MOdule
This will help you to fetch the details of the MD04 stock reqruiement list
3. Both the belwo program helps you to have different selection screen parameters than what we have in the standard MD05 / MD05 SCREENS.
RMMD07EX and RMMD07DB
Reg
Satheesh

Exception Propagation - Best Practises

Hello,
I was thinking what is the best practise for exception propogation.
The way I know and have been doing is to specify an error page in my web.xml and in that I get a request paramater from the sesion ( which I populate in the catch blocks across the various classes) and display it to the user and ask him to contact the admin. Ofcourse I log them using log4j.
I was wondering if there are other ways people do this (other than just displaying a "Sorry, Application Error" page and what do you think should be the best practise of exception handling and more importantly exception propagation.
Thanks in advance for your time
rgds,

Sarvananda wrote:
...what do you think should be the best practise of exception handling and more importantly exception propagation.The very best practice is to always handle the exception, that is to say: never use empty "catch blocks".
As already stated there are many correct ways to handle exceptions depending largely on the result you desire according to the exception. If you want feedback for debugging: I've made the errors descriptive... class/method and exception/error included in the message to the end user. This almost never works, since they never read it and if they report it, they just say: "I got this error thingy and it said to call you..." I got smarter the second time around and put the errors in logs, so when they actually called, then I could have them look up the error for me, or even better, just send me the log so I could see any other problems they didn't bother to report.
It sounds like you are doing web development, one thing I have done in the past is to just pop up an e-mail ready to go with all the info in it. All the end user had to do is hit send.

Is there an easy way to suppress debug messages from plugin.jar?

When using the plugin.jar library (included in JRE 1.4.2 and 1.5)
my Java Console is riddled with tons of debug messages like:
<<< ProxyClassLoader: defined LiveConnectProxy class. >>>
<<< Here're the permissions you've got: >>>
<<< java.security.Permissions@b614d0 (
(java.net.SocketPermission 127.0.0.1 connect,accept,resolve)
)I'm using the plugin.jar (replacing use of the old netscape.jar)
to bridge communication between Java Applets and JavaScript.
Each time the Applet calls back to the JavaScript side,
the callback JavaScript function makes a call to parseInt() to
convert one of the parameters passed from a string to an integer.
Each time parseInt() is called, the message above appears
in the Java Console.
I traced down the source code for this message to a debug()
statement inside the plugin.jar's class loader, but I'm not sure
how to suppress it easily.
Does anyone have any ideas I could try?
Here's the code from the Java-side:
synchronized( this )
     try
          final JSObject window = JSObject.getWindow( applet );
          if( window != null )
               final String[] stringArgs = new String[3];
               stringArgs[0] = labelName;
               stringArgs[1] = labelDisplayName;
               stringArgs[2] = labelValue;
               log.debug(stringArgs[0]);
               log.debug(stringArgs[1]);
               log.debug(stringArgs[2]);
               window.call("MyJavascriptCallback", stringArgs);
          else
               log.error("Javascript window unavailable.");
     catch( final JSException e )
          // Note: Occasionally, getWindow() will throw an exception
          // without any meaningful reason.
          // ( http://www.raditha.com/blog/archives/000938.html )
          // Possible cause: This can send updates at a fraction of a
          // second. This may be causing issues within the Plugin.jar
          // used to handle the JavaScript callback.
          log.debug("JSException", e);
}

Here's what I've found out...
The messages are coming from the MRJPlugin.jar provided by Firefox.
Within the netscape.oji.ProxyClassLoaderFactory class,
the following line...
System.out.println("<<< " + message + " >>>");
...appears to be the cause and cannot be turned off by a configuration setting.
The home URL for the MRJPlugin.jar is:
http://www.mozilla.org/oji/MRJPlugin.html
The last time this library had an update released was in 10/31/2000.
However, this is the Mozilla source; not Firefox.
Although changing the MRJPlugin.jar source to remove this line will appear
to fix the problem, I'm not sure of the best way to distribute the updated
MRJPlugin.jar without conflicting with Firefox's update process.
Any thoughts?

Message bridge exception when using bridging to MQ

          hi ... was wondering if anyone could suggest what might be causing this.
          I have a weblogic 8.1 queue bridged to a MQ5.3 queue. I was successfully able
          to put messages (using the container to handle the XA) into the weblogic Q and
          have the bridge successfully pass the msg onto the MQ Q. However I have started
          getting the following error msgs on random occasions.(and the bridge is not able
          to transfer the msgs across). Any suggestions as to what might be causing this?
          Please let me know if you need any additional info.
          thanks,
          Rajat
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200033> <Bridge "JeInputBridge"
          is obta
          ining connections to the two adapters.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200032> <Bridge "JeInputBridge"
          is conf
          igured to disallow degradation of its quality of service in cases where the configured
          quality of se
          rvice is unreachable.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200030> <Bridge "JeInputBridge"
          is conf
          igured to work in "Exactly-once" mode, and it is actually working in "Exactly-once"
          mode.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200028> <The bridge
          "JeInputBridge" has
          started transferring messages.>
          <Nov 14, 2003 11:10:08 AM EST> <Error> <MessagingBridge> <BEA-200015> <An error
          occurred in bridge "
          JeInputBridge" during the transfer of messages (javax.resource.ResourceException:
          Exception during e
          nListResource).>
          <Nov 14, 2003 11:10:08 AM EST> <Warning> <MessagingBridge> <BEA-200026> <Bridge
          "JeInputBridge" enco
          untered some problems in one of its adapters or underlying systems. It stopped
          transferring messages
          and will try to reconnect to the adapters shortly. (The exception caught was
          weblogic.jms.bridge.in
          ternal.MessagingBridgeException.)>
          <Nov 14, 2003 11:10:09 AM EST> <Info> <MessagingBridge> <BEA-200020> <Bridge "JeInputBridge"
          is stop
          ped.>


I suggest that you contact BEA Customer Support so that somebody can spend more time working
          directly with you and solving the problem.
          Sorry for not being able to help you more.
          Dongbo
          Rajat wrote:
          > hi Dongbo ... i checked the MQ error logs and found the followign error:
          >
          > ----- amqccita.c : 2758 -------------------------------------------------------
          > 11/17/03 10:33:24 AM
          > AMQ9208: Error on receive from host AHEWVTBHALLRA1-1 (169.242.174.24).
          >
          > EXPLANATION:
          > An error occurred receiving data from AHEWVTBHALLRA1-1 (169.242.174.24) over
          > TCP/IP. This may be due to a communications failure.
          > ACTION:
          > The return code from the TCP/IP (read) call was 131 (X'83'). Record these
          > values and tell the systems administrator.
          >
          > I did a test and found out that the error above is logged when i shut down the
          > WLS and NOT when i get the message bridge exception. The MQ system Admin feels
          > that there is bug in WLS as shuttting down WLS should gracefully terminate the
          > MQ connection and not throw any exceptions on MQ. So looks like this another thing
          > i would need your help on. Any other suggestions on what to do regarding the message
          > bridge exception ?
          >
          > Thanks,
          > Rajat
          >
          > Dongbo Xiao <[email protected]> wrote:
          > >Hi Rajat,
          > >Did you look at the log or tracing on the MQSeries side as I suggested?
          > >If you don't see any suspicious error messages on the MQSeries side,
          > >I would suggest that
          > >you contact the BEA Customer Support.
          > >Thanks,
          > >Dongbo
          > >
          > >Rajat wrote:
          > >
          > >> hi Dongbo,
          > >>
          > >> The problem occurs regardless of whether i stop the bridge and restart
          > >it. As
          > >> mentioned earlier, this problem does not occur all the time. This morning
          > >i started
          > >> up WLS and the it was giving the error. I then stopped it and restarted
          > >WLS ...it
          > >> started working fine. I then stopped the bridge and restarted the bridge..and
          > >> the errror happened. I then stopped the WLS and restarted it ...and
          > >the problem
          > >> was still there.... i then stopped and restarted WLS and everything
          > >started working
          > >> fine. On one occasion a few days ago... the bridge was working fine..and
          > >then
          > >> all of a sudden started giving this error...and after a while it started
          > >working
          > >> again. Pls suggest next steps.
          > >>
          > >> Thanks,
          > >> Rajat
          > >>
          > >> Dongbo Xiao <[email protected]> wrote:
          > >> >
          > >> >Hi Rajat,
          > >> >
          > >> >I have looked at your log file after Tom bought to me attention of
          > >the
          > >> >problem you are
          > >> >having.
          > >> >The error message regarding the adapter at the startup
          > >> >(NoSuchMethodException) is not a problem. It is just an info message.
          > >> >I also noticed that the Input bridge had been stopped and restarted
          > >before
          > >> >the error
          > >> >occurred. Did you get the same error if you did not stop and restart
          > >> >the bridge?
          > >> >Looks like the connection was somehow closed on the MQSeries side
          > >after
          > >> >the bridge
          > >> >established a connection to it but before the bridge sent any message
          > >> >over.
          > >> >If the problem only occurs after you stop and restart the bridge,
          > >it
          > >> >more likely is
          > >> >a bug on the WLS side. Otherwise, I would suggest that you check
          > >the
          > >> >log (or tracing)
          > >> >of the queue manager on the MQSeries side and see if you can spot
          > >some
          > >> >problem on the
          > >> >MQSeries side.
          > >> >
          > >> >Thanks,
          > >> >Dongbo
          > >> >
          > >> >Rajat wrote:
          > >> >
          > >> >> hi Tom... i looked over the FAQs but did not spot anything that
          > >i was
          > >> >doing wrong.
          > >> >> I have attatched the stack trace with the JMS debugging. (Sorry
          > >for
          > >> >the large
          > >> >> file... but i spotted some failure msgs regarding the adapter at
          > >startup
          > >> >and i
          > >> >> would like you to take a look ..). I have two bridges setup...
          > >> >> - JeInputBridge - connects weblogic Q to MQ Q
          > >> >> - JeReplyBridge - connects MQ Q to weblogic Q
          > >> >>
          > >> >> I am using the eis.jms.WLSConnectionFactoryJNDIXA adapter and am
          > >using
          > >> >the QOS
          > >> >> = "Exactly-Once"
          > >> >>
          > >> >> The weird thing is that the JeReplyBridge has never shown this error....
          > >> >but the
          > >> >> JeInput bridge sometimes works fine... then starts giving the error.
          > >> >On occassions,
          > >> >> it will keep trying and eventually start working... and sometimes
          > >i
          > >> >have to restart
          > >> >> the weblogic server several times before it starts working.
          > >> >>
          > >> >> Any suggestions/advice will be much appreciated.
          > >> >> Thanks,
          > >> >> Rajat
          > >> >>
          > >> >> Tom Barnes <[email protected]> wrote:
          > >> >> >The information below is too generic to interpret. Were stack
          > >traces
          > >> >> >printed out? Anyhow, I suggest that your start with the
          > >> >> >7.0 messaging bridge FAQ (it also applies to 8.1) to get
          > >> >> >more information about how to diagnose bridge issues:
          > >> >> >
          > >> >> >http://edocs.bea.com/wls/docs70/faq/msgbridge.html
          > >> >> >
          > >> >> >Rajat wrote:
          > >> >> >
          > >> >> >> hi ... was wondering if anyone could suggest what might be causing
          > >> >> >this.
          > >> >> >>
          > >> >> >> I have a weblogic 8.1 queue bridged to a MQ5.3 queue. I was successfully
          > >> >> >able
          > >> >> >> to put messages (using the container to handle the XA) into the
          > >> >weblogic
          > >> >> >Q and
          > >> >> >> have the bridge successfully pass the msg onto the MQ Q. However
          > >> >I
          > >> >> >have started
          > >> >> >> getting the following error msgs on random occasions.(and the
          > >bridge
          > >> >> >is not able
          > >> >> >> to transfer the msgs across). Any suggestions as to what might
          > >be
          > >> >causing
          > >> >> >this?
          > >> >> >> Please let me know if you need any additional info.
          > >> >> >>
          > >> >> >> thanks,
          > >> >> >> Rajat
          > >> >> >>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200033>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is obta
          > >> >> >> ining connections to the two adapters.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200032>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is conf
          > >> >> >> igured to disallow degradation of its quality of service in cases
          > >> >where
          > >> >> >the configured
          > >> >> >> quality of se
          > >> >> >> rvice is unreachable.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200030>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is conf
          > >> >> >> igured to work in "Exactly-once" mode, and it is actually working
          > >> >in
          > >> >> >"Exactly-once"
          > >> >> >> mode.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200028>
          > >> >> ><The bridge
          > >> >> >> "JeInputBridge" has
          > >> >> >> started transferring messages.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Error> <MessagingBridge> <BEA-200015>
          > >> >> ><An error
          > >> >> >> occurred in bridge "
          > >> >> >> JeInputBridge" during the transfer of messages (javax.resource.ResourceException:
          > >> >> >> Exception during e
          > >> >> >> nListResource).>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Warning> <MessagingBridge> <BEA-200026>
          > >> >> ><Bridge
          > >> >> >> "JeInputBridge" enco
          > >> >> >> untered some problems in one of its adapters or underlying systems.
          > >> >> >It stopped
          > >> >> >> transferring messages
          > >> >> >> and will try to reconnect to the adapters shortly. (The exception
          > >> >> >caught was
          > >> >> >> weblogic.jms.bridge.in
          > >> >> >> ternal.MessagingBridgeException.)>
          > >> >> >> <Nov 14, 2003 11:10:09 AM EST> <Info> <MessagingBridge> <BEA-200020>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is stop
          > >> >> >> ped.>
          > >> >> >
          > >> >>
          > >> >> ------------------------------------------------------------------------
          > >> >> Name: myserver.log
          > >> >> myserver.log Type: Text Document (application/x-unknown-content-type-txtfile)
          > >> >> Encoding: base64
          > >> >
          > >

Powerpivot - Can't insert formula that combines two or more different columns and keep getting message "unhandled exception has occurred in a component in your application...

I am using powerpivot v2 with excel 2010.
When I go to my excel file's powerpivot and I try to insert a formula in any column, I constantly get the following message:
"unhandled exception has occurred in a component in your application. If you click continue, the application will ignore this error and attempt to continue".
************** Exception Text **************
System.InvalidCastException: Return argument has an invalid type.
at System.Runtime.Remoting.Proxies.RealProxy.ValidateReturnArg(Object arg, Type paramType)
at System.Runtime.Remoting.Proxies.RealProxy.PropagateOutParameters(IMessage msg, Object[] outArgs, Object returnValue)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Office.Interop.Excel._Application.get_ActiveWorkbook()
at Microsoft.AnalysisServices.XLHost.Addin.GeminiRibbon.currentClientWindow_InFormulaBarChanged(Object sender, EventArgs e)
at Microsoft.AnalysisServices.Common.SandboxEditor.formulaBar_Leave(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.ContainerControl.UpdateFocusedControl()
Does anybody know how to fix this ?

Mark,
I used the Fix It found here:
http://support.microsoft.com/kb/2739501
I would have to ask my IT support person for more specifics, but as I understand the scenario with my particular laptop: the laptop came preloaded with RTM build of 2013. We used Control Panel to uninstall Office 2013, in order to install Office
2010. I installed PowerPivot add-in and used it successfully with no issues for several months. After attempting to install another program and encountering issues with apparent traces left behind of Office 2013 uninstall, I found the link above
and used the Fix It to attempt to remove all remaining traces of Office 2013. While it did appear to find and clean-up quite a bit left behind from the Office 2013 install, I was surprised to find an error upon entering my existing installation
of PowerPivot for 2010 and attempting to type new formulas into the formula bar.
My experience to-date is that an error message stating ""Return Argument Has an Invalid Type" appears anytime I select or modify a formula in the formula bar that would cause the intellisense to appear. For example, when I first click into the formula
bar, I do not get an error...but as soon as I type the first letter, before the intellisense appears, I get the error message. Throughout the remainder of the formula as I type, just prior to any time when the intellisense drop-down will appear
again, I get the same error message again (see details below).
At one time, although I can't reproduce it now, the error message did state ".Net Framework" in the menu bar of the error pop-up window. I can't get that to appear again, as it now only says "PowerPivot for Excel". Based on this, I had attempted
to see if I could repair my .NET framework install using the following tool:
http://www.microsoft.com/en-us/download/details.aspx?id=30135
I learned, however, that since I am running Windows 8 which comes with .NET 4.5 built-in to the OS, this tool does not yet cover that version for repair.
While the overall end-result of my PowerPivot models appear to be just the same, having to click through "Continue" on the error message multiple times each time I enter a new formula is a huge drain on productivity.
Let me know if you have any additional questions.
David
System.InvalidCastException: Return argument has an invalid type.
   at System.Runtime.Remoting.Proxies.RealProxy.ValidateReturnArg(Object arg, Type paramType)
   at System.Runtime.Remoting.Proxies.RealProxy.PropagateOutParameters(IMessage msg, Object[] outArgs, Object returnValue)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Office.Interop.Excel._Application.get_ActiveWorkbook()
   at Microsoft.AnalysisServices.XLHost.Addin.GeminiRibbon.currentClientWindow_InFormulaBarChanged(Object sender, EventArgs e)
   at Microsoft.AnalysisServices.Common.SandboxEditor.formulaBar_Leave(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.ContainerControl.UpdateFocusedControl()
David Duncan Consultant I.B.I.S., Inc.

Error : Old and new exceptions cannot be used at the same time.

HI ALL,
i build a new exception class with message class and i want to replace the
old exception that i had in the method ,what i did is delete the exception from the method
signature and add the exception class .
the problem is that when i try to activate the method i get error :
Old and new exceptions cannot be used at the same time.
CALL FUNCTION 'CALCULATE_HASH_FOR_CHAR'
      EXPORTING
        alg            = 'MD5'
        data           = iv_iss
      IMPORTING
        hash           = lv_issu
      EXCEPTIONS
        unknown_alg    = 1
        param_error    = 2
        internal_error = 3
        OTHERS         = 4.
    IF sy-subrc <> 0.
      RAISE EXCEPTION TYPE cx_user_mng EXPORTING
      textid = cx_user_mng=>wrong_isrs.
    ENDIF.
I want to use the new exception class ,
how can i avoid this error ?
Best Regards
Edited by: Joy Stpr on Jul 22, 2009 2:56 PM
Edited by: Joy Stpr on Jul 22, 2009 3:16 PM

Hi Joy,
Check this link.
[Old and New Exceptions Cannot be used at same time|Urgent problem, give me a hand;
Old and new exceptions cannot be used the same time, what does this mean???
Regards,
Lakshman.

Com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException in sap pi

Hi all,
I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The entire trace is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="3" type="T">Sender scheme external =</Trace>
<Trace level="3" type="T">Sender agency external =</Trace>
<Trace level="3" type="T">Sender party external =</Trace>
<Trace level="3" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Determining the sender agreement</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="1" type="T">Remote address = 10.66.10.160</Trace>
<Trace level="1" type="T">User = SFUSER</Trace>
<Trace level="1" type="T">Process ID: 760</Trace>
<Trace level="1" type="T">Work Process ID: 10</Trace>
<Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>
<Trace level="1" type="T">Hop engine type = IS</Trace>
<Trace level="1" type="T">Hop adapter name = XI</Trace>
<Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
<Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
<Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>
<Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>
<Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>
<Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>
<Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>
<Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message</Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Skip Inbound Validation =</Trace>
<Trace level="3" type="T">Skip Outbound Validation =</Trace>
<Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T

HI,
Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
Patch level of XIAF:
1. customers SAP PI level is
Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
2. our SAP PI level is
Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
What do you think ?
Thanks

Synchronous scenario(ABAP proxy to HTTP_AAE) getting error exception as "Message Expired Exception"

Dear All,
I have done all the configuration for ABAP proxy scenario using AAE/ICO as per the below "how to guide" using SOAP as sender adapter using xi protocol. My SAP PI is 7.4 dual stack system. here third party is not a webservice its HTTP based we server so no wsdl.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?overridelayout=t…
However after running the scenario from ECC I am getting the exception as "Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 53289257-97e0-06d0-e100-00000a70d384(OUTBOUND) expired.". I do not have any connection problem to third party(bank) URL. moreover I am able to get the response from bank using classical scenario s in PI, but the response message is not getting pushed to ECC, rather its reaming in PI SXMB_MONI with status "Log version".
Thats the reason I am trying to do using ICO, but using ICO PI is not even sending the request out of PI to bank. Please see the below receiver communication channel message log.
Thanks,
Farhan

Hi,
As per the log, the message has started 23:18:02 and failed at 23.23:02 it took 5min time, if message is not process certain time this kind of errors comes up. Have you changed adapter type for existing SOAP communication channel or created new? provide complete log of the message from starting time to ending time if possible.

Integrated Configurations com.sap.engine.interfaces.messaging.api.exception

Hi guys,
we are using PI 7.11.
With this release local processing on the advanced adapter engine is possible, when using integrated configurations.
This works fine.
Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.
I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.
Afterwards I treied to restart the message.
Following error occurs.
com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.
I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache
trying restart the failed message ends up in the error specified aboce.
Anyone faced the same issue already?
Kind regards
Jochen

HI Jochen,
I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.
To do a CPA Cache Refresh from the Adapter Engine:
To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:
http://<host>:<port>/CPACache/refresh?mode=delta|full
The Monitoring url is like this:
http://<host>:<port>/CPACache
Check this How-to Guide on Cache, it will be useful:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&overridelayout=true
Thanks
Dhwani

Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim

Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
     <gesellschaft>03</gesellschaft>
     <filiale>000</filiale>
     <satzart>11</satzart>
     <datum>00000000</datum>
     <kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim

Linked Server :: OLE DB provider "OraOLEDB.Oracle" for linked server "ABC" returned message "New transaction cannot enlist in the specified transaction coordinator. ".

Hello All,
As mentioned in title, i am stuck up with that articular error from last three days,
i have following scenario, my SQL server 2008, my oracle 10g are on both same machine with OS Windows Server 2008.
the following error generated on my management studio when i execute my procedure written in my SQL server. Following is original source code snippet after error massage.
OLE DB provider "OraOLEDB.Oracle" for linked server "ORCL" returned message "New transaction cannot enlist in the specified transaction coordinator. ".
Msg 50000, Level 16, State 2, Procedure PROC_MIGRATE_MST_FRM_ORA_SQLSERVER, Line 43
The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORCL" was unable to begin a distributed transaction.
BEGIN TRY
-- MIGRATION OF PR_COMPANY_MH START
BEGIN TRANSACTION T1
PRINT 'mILAN NNNNNNNNN 11'
INSERT INTO PROD.PR_COMPANY_MH
SELECT * FROM OPENQUERY(ORCL, 'SELECT * FROM PR_COMPANY_MH WHERE SQL_FLG = ''N'' ')
PRINT 'mILAN NNNNNNNNN 12'
UPDATE OPENQUERY(ORCL, 'SELECT SQL_FLG FROM PR_COMPANY_MH WHERE SQL_FLG = ''N''')
SET SQL_FLG = 'Y'
--EXECUTE ('UPDATE PROD.PR_COMPANY_MH SET SQL_FLG = ''Y'' ') AT [ORCL]
PRINT 'mILAN NNNNNNNNN 13'
COMMIT TRANSACTION T1
-- MIGRATION OF PR_COMPANY_MH END
END TRY
BEGIN CATCH
PRINT 'mILAN NNNNNNNNN 14'
ROLLBACK TRANSACTION T1
PRINT 'mILAN NNNNNNNNN 15'
SELECT
@ErrorNumber = ERROR_NUMBER(),
@ErrorSeverity = ERROR_SEVERITY(),
@ErrorState = ERROR_STATE(),
@ErrorLine = ERROR_LINE(),
@ErrorProcedure = ISNULL(ERROR_PROCEDURE(), '-');
PRINT 'mILAN NNNNNNNNN 16'
SELECT @ErrorMessage = ERROR_MESSAGE();
RAISERROR (@ErrorMessage, @ErrorSeverity, @ErrorState, @ErrorNumber, @ErrorProcedure)
PRINT 'mILAN NNNNNNNNN 17'
END CATCH
this perticular part is raising that error, and i had tried every configuartion on my local machine related to MS DTC.
When i remove my transaction code, its work just fine no exception raise, but when i use then i.e. BEGIN TRAN, COMMITE TRAN, AND ROLLBACK TRAN. its giving me error, other wise its fine.
Please Help or disscus or suggest why my transaction base code is not woking????
thanks in advance.
Regards,
Milan

Sorry again, I am new on any kind of forum, so i am learning now, following is the error massage generated by SQL Server. and its not
an architecture problem, i had just included my complete architecture to be more informative while asking for the solution or suggestion. My real problem is T-SQL, i think and its related to Distributed queries raise in SQL Server in Oracle Link Server.
OLE DB provider "OraOLEDB.Oracle"
for linked server "ORCL" returned message "New transaction cannot enlist in the specified transaction coordinator. ".
Msg 50000, Level 16, State 2, Procedure PROC_MIGRATE_MST_FRM_ORA_SQLSERVER,
Line 43
The operation could not be performed because OLE
DB provider "OraOLEDB.Oracle" for linked server "ORCL" was unable to begin a distributed transaction.

InitCVIRTE generates error message "Unhandled exception in "MyApp.exe": 0xC0000005: Access violation reading location 0x00000000."

Hi,
I have converted a LabWindows CVI project to Visual Studio 2005. When I start the application i debug mode I get the message "Unhandled exception at 0x685662ba in EE352-500V.exe: 0xC0000005: Access violation reading location 0x00000000."
It comes when the application calls: InitCVIRTE in this context:
int __stdcall WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpszCmdLine, int nCmdShow)
// Initialize LabWindows/CVI run-time library
if (InitCVIRTE (hInstance, 0, 0) == 0)
return -1; /* out of memory */
The debugger indicates that value of hInstance is 0x00400000 {unused=9460301}
Can someone give me a solution to this problem. I have done some search on the Web without success.
Thanks!

I think that exception might be coming from the data execution prevention service that is part of Win XP SP2. The OS thinks that you're somehow trying to execute in the data segment and kills the process. It's intended to catch worms and viruses.
You can turn this service off for non-Microsoft programs using the control panel.
Many pointer handling errors now report as this exception instead of as a memory violation exception. That looks like a null pointer derefence to me.
Menchar
Message Edited by menchar on 11-09-2007 07:12 PM

NO MORE DEBUG MESSAGES!

it is kind of hard to stay in the forum rules, specially the
insults part (is inept or negligent allowed by forum rules?), on
how i feel right now. why somebody in adobe thinks that a final
user cares about debug messages? i am using firefox i have many
tabs open, i am watching whatever and all the tabs get blocked
because somebody thinks is the job of the final user to debug
something he/she didnt make, specially the 'select code location',
which code?, so i keep getting a popup asking where to debug (if
local or to place the id of the code to debug). there are pages
that are so hard to watch because of this, are the adobe people so
(...)... ARGHHHHH!!!.. i keep disabling flash player because of
this, i only turn it on to rate songs in yahoo launchcast or watch
youtube videos or a few more pages, then i forget to disable it and
the problems begin ('something' reminds me to turn it off again),
if there is one of those popups asking the location of the code to
debug and disable the player without closing this message, adobe
offers me a nice browser crash. are they stupid or is the final
user the debug monkey for their products?, i mean, is not like it
does not happen all the time (either firefox or explorer), they see
by themselves something is just plain wrong, but does somebody else
has to tell them, yes it is wrong even tough you see it by
yourselves, please make it right? i mean, fix that stupid thing
once and for all, why do we care about debug code we didnt even
made ourselves, talk about 'user experience'

Originally posted by: cap_nemesis.hotmail.com
if there are more than one log4j.properties on different levels (server,
webapp) things can get confusing :-)
"Mark Daring" <[email protected]> schrieb im Newsbeitrag
news:drgpe7$1o0$[email protected]..
> How can I change the tomcat logging level, so no more messages like:
> "DEBUG [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
> (ManagerBase.java:653) - Start expire sessions StandardManager at ..." are
> sent to the console?
>
>

Display debugging message in jboss environment

Hi every body,
I am trying to plot a graph using jfreechart on jsp page. I want to debug because I fount the class cast exception error.
Can you tell me please that how can I dispaly debugging message using jboss environment.
Where can I look this message.
public Log logger=LogFactory.getLog(this.getClass());
logger.debug("Before calling pageno");
Thanks and best regards

Perhaps you have to look at Log4J: [http://logging.apache.org/guidelines.html].
The standard log directory should be: jboss-4.2.1.GA\server\default\log

DEBUG MESSAGE: new exception propagation across deoptimization

Similar Messages

Maybe you are looking for