Exception in method process

Hi all,
I am configuring a scenario RFC -> XI -> Webservice. In my SOAP adapter trace, i found an error :
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any body please suggest me the possible reasons?
Thanks and best regards,
Kulwant

try this too
com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process
and this
com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process ?
Edited by: Lawrence on Apr 22, 2008 8:17 AM

Similar Messages

Xi 3.0: Mail adapter fails with "exception in method process"

Hi.
I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
I tried both async and sync case with the same result. In the sync case, the response contains:

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea???

Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
Anyway, in my server i get a 404 for the link you suggested.
In the async case i don't get any error on the SXMB_MONI but only on the A.F.
I attach the audit log for the async case:
Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
Time Stamp Status Thread ID Sequence No. Description
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
Total: 33 Entries 1020304050 messages displayed per page; this is page 1 of 1 page(s)

SOAP Adapter: Exception in method process

Hello Experts,
We are getting from time to time on the Receiver SOAP Communication Channels the folowing error:
Delivery of the message to the application using connection AFW failed, due to: Exception in method process.
We are getting this error on both types of messages - sync and async.
I did a search on SDN and Notes, but didn't found any description or solution for this error.
Can someone please help with this error?
Thanks in advance!

Here are some details extracted from the log:
Date : 07/30/2008
Time : 8:44:15:783
Message : Error during processing local bean: localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Severity : Error
Category :
Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
Application : sap.com/com.sap.aii.af.app
Thread : output
Datasource : 1217412862462:/usr/sap/xxx/xxx/j2ee/cluster/server1/log/defaultTrace.trc
Message ID : 001CC4B7988E00A5000268B100000CB3000453381549AFAE
Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
Argument Objs :
Arguments :
Dsr Component : xxx
Dsr Transaction : 989219405e0211ddc88b001cc4b7988e
Dsr User : Guest
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
ThreadObject : output
Transaction : SAP J2EE Engine JTA Transaction : [2dffffff91ffffffbdffffffe3040ffffffb0]
User : J2EE_GUEST
Hope this will help somebody to get the clue what is causing this error.

Non-application exception occurred while processing method createReportsExc

Hi,
Any one get the following exception
Non-application exception occurred while processing method createReportsExcelFile on bean BeanId(bsd#bsdejb.jar#ReportsDownload, null): java.lang.NoSuchMethodError: java.lang.RuntimeException: method <init>(Ljava/lang/Throwable;)V not found
 at jxl.write.biff.File.write(File.java(Compiled Code))
 at jxl.write.biff.SheetWriter.write(SheetWriter.java(Compiled Code))
 at jxl.write.biff.SheetWriter.write(SheetWriter.java(Compiled Code))
 at jxl.write.biff.WritableSheetImpl.write(WritableSheetImpl.java:1165)
 at jxl.write.biff.WritableWorkbookImpl.write(WritableWorkbookImpl.java:805)
 at com.bsdnet.ejb.report.ReportsDownloadEJB.writeToBUReportExcelFile(ReportsDownloadEJB.java(Compiled Code))
 at com.bsdnet.ejb.report.ReportsDownloadEJB.createBUReport(ReportsDownloadEJB.java:2151)
 at com.bsdnet.ejb.report.ReportsDownloadEJB.createReportsExcelFile(ReportsDownloadEJB.java:411)
 at com.bsdnet.ejb.report.EJSRemoteStatelessReportsDownload.createReportsExcelFile(EJSRemoteStatelessReportsDownload.java:49)
 at com.bsdnet.ejb.report._ReportsDownload_Stub.createReportsExcelFile(_ReportsDownload_Stub.java:258)
 at com.bsdnet.batch.report.ReportsJobProcessingThread.run(ReportsJobProcessing.java:282)
IF Yes, Then Please help me out asap.
Thanks,
Sumit Gupta

Since you want to use a class that is not part of your EJB environment you cant access it.
Like you said your ELUWS14 class is part of your web project, most likely to be inside a war. And the session bean inside an ear.
If you need that class on both environments (session beans and web components) the best approach is to create a JAR file and include it there. If it is going to change a lot then the best approach is to have it on your ear (EJB side), and your web components should call the session beans method to invoke operations.
Your business rules should not access your presentation layer:
EJB -> Web components Not a good idea
EJB <-> Web components Not a good idea
EJB <- Web components This is the way to go
So, web components should access classes from the ear, and not viceversa. This is why containers make ear classes accesible to web component, and not in the other way

Non-application exception occurred while processing method "fnExtRiskAccum"

I am getting the following error when starting the Server ?
Please help me to find out what it means
Non-application exception occurred while processing method "fnExtRiskAccum". Exception data: com.ibm.ejs.container.CreateFailureException: ; nested exception is:
 java.lang.reflect.InvocationTargetException
 at com.ibm.ejs.container.StatelessBeanO.<init>(StatelessBeanO.java:151)
 at com.ibm.ejs.container.CMStatelessBeanO.<init>(CMStatelessBeanO.java:53)
 at com.ibm.ejs.container.CMStatelessBeanOFactory.create(CMStatelessBeanOFactory.java:40)
 at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:666)
 at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:753)
 at com.ibm.ejs.container.activator.UncachedActivationStrategy.atActivate(UncachedActivationStrategy.java:78)
 at com.ibm.ejs.container.activator.Activator.activateBean(Activator.java:516)
 at com.ibm.ejs.container.EJSContainer.preInvoke_internal(EJSContainer.java:2762)
 at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2487)
 at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2472)
 at uw.EJSRemoteStatelessUWGC_ejbVERIFY_34c1773e.fnExtRiskAccum(EJSRemoteStatelessUWGC_ejbVERIFY_34c1773e.java:52)
 at uw._UWGC_ejbVERIFYRemote_Stub.fnExtRiskAccum(_UWGC_ejbVERIFYRemote_Stub.java:918)
 at ren.RNLB_cPL_MAIN.doGet(RNLB_cPL_MAIN.java:3045)
 at ren.RNLB_cPL_MAIN.doPost(RNLB_cPL_MAIN.java:65)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at ren.RNLB_cPL_MAIN.service(RNLB_cPL_MAIN.java:4055)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
 at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
 at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
 at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
 at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
 at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
 at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:983)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:564)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
 at common.UTIL_cENTRY.doGet(UTIL_cENTRY.java:84)
 at common.UTIL_cENTRY.doPost(UTIL_cENTRY.java:89)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
 at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
 at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
 at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
 at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
 at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
 at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:983)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:564)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
 at common.UTIL_cTUNNEL.doGet(UTIL_cTUNNEL.java:129)
 at common.UTIL_cTUNNEL.doPost(UTIL_cTUNNEL.java:151)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
 at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
 at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
 at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
 at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
 at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
 at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:983)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:564)
 at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
 at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
 at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
 at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
 at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
 at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
 at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
 at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
 at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
 at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:443)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
Caused by: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
 at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
 at com.ibm.ejs.container.StatelessBeanO.<init>(StatelessBeanO.java:144)
 ... 64 more
Caused by: javax.ejb.CreateException: Unable to create EJB: UWGC_ejbVERIFYBean.
 at uw.UWGC_ejbVERIFYBean.ejbCreate(UWGC_ejbVERIFYBean.java:100)
 ... 69 more

Since you want to use a class that is not part of your EJB environment you cant access it.
Like you said your ELUWS14 class is part of your web project, most likely to be inside a war. And the session bean inside an ear.
If you need that class on both environments (session beans and web components) the best approach is to create a JAR file and include it there. If it is going to change a lot then the best approach is to have it on your ear (EJB side), and your web components should call the session beans method to invoke operations.
Your business rules should not access your presentation layer:
EJB -> Web components Not a good idea
EJB <-> Web components Not a good idea
EJB <- Web components This is the way to go
So, web components should access classes from the ear, and not viceversa. This is why containers make ear classes accesible to web component, and not in the other way

Sender Mail Adapter Error: exception caught during processing mail message;

HI , I am configuring mail to file scenario. Need to read mail content (no need to capture From,TO or Subject details) and create a file with the content in the mail.
Need to read mails from microsoft outlook. Exchange server has been configured for POP3 protocol.
Following are the details provoding in sender mail adapter:
URL: provided url in the format: pop://<server name>
Authentication method: plain
provided user credinetions to access mails.
poll interval - 1min
content encoding none.
processing parameters : quality of service-exactly once
Since there is no need to capture From,TO or Subject details, didn't select the option - use mail package.
Verified for unread mails in the mail box and made sure that there are few unread mails.
Also, created data types and other components in IR and completed mapping.
But after starting sender mail communication channel, getting error "exception caught during processing mail message; java.lang.NullPointerException" in RWB-adapter-communication channel monitoring.
please let me know what needs to be done to resolve this error.
Thanks.

HI Stefan, i tried, but still it is giving same error. Yes, i am able to access outlook mail with the user credentials given in the communication channel to access exchange server.
I am using message protocol: xipayload . Also since i dont have to capture TO,from,subject details., created data type just with one element of type string, not in the standard format .Does this makes any difference.

Portal Runtime Error : An exception occurred while processing a request

Hello friends,
After upgradation of my portal to the following patch level, SAP J2EE 6.20:
Portal Version : EP 6 SP 2 patch 29 hotfix 0
Content Mgmt and Collaboration version : 6 SP2 patch 5
i faced many performance related issues. Portal seems to be very slow. After logging in, most of the time I get 2 errors:
Either
1> Iview remains blank.
Or
2> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
But when I refresh that particular iview, it works fine.
I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."Aug 18, 2005 6:07:42 PM # PRT-Async 2 Fatal Exception ID:06:07_18/08/05_0669
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
Component class : com.sapportals.portal.prt.pom.RootComponentNode
User : tempuser
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
 at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Help needed.(as i am helpless now.)
Regards,
Nilz

Anthony,
I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
I created like this
 project-> rightclick-> export-> par ->selecting project-> givint protal password-> and finish.
The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
but the par file is created in the NW studio Navigation bar.
Let me know any help regarding this
thanks
venkat

Exception CX_SY_MOVE_CAST_ERROR when Process Reassignments for Key Date Results

Hi Experts,
I got an exception error when process reassignments for key date results(transaction code /BA1/FG_PR_KR_REASS) in BANK ANALYZER, did anyone get the same problem before? any solutions?
the process sequences is listed below:
1,,Set SDL Timestamp,,              /BA1/B0_CLOSE_SDL
2,,Generate Positions,,              /BA1/F2_PB_PR
3,,Aggregate Financial Transactions,,,,          /BA1/FG_PR_FT
4,,Prepare Business Transactions for Aggregation,,    /BA1/FG_PR_BT_PRE
5,,Process Reassignments for Business Transactions,,    /BA1/FG_PR_RABT
6,,Aggregate Business Transactions,,/BA1/FG_PR_BT
7,,Process Reassignments for Key Date Results,,    /BA1/FG_PR_KR_REASS
7.a),,Subcomponent view,,subcomponent=S_SVAC01 ,,OK
7.b),,Subcomponent view,,subcomponent=S_SVFT01 ,,Exception
I nenver changed subcomponent settings, they are all SAP delivered.
Exception CX_SY_NO_HANDLER: An exception with the type
CX_SY_MOVE_CAST_ERROR occurred, but was neither handled locally, nor
declared in a RAISING clause
Message no. /BA1/AL_X0_M_H000
Exception CX_SY_MOVE_CAST_ERROR: Source type
\CLASS-POOL=/BA1/CL_AL_FG_MD_SUB_CMP_VIEW\CLASS=LCL_SCV_FT2AGGRO is not
compatible, forthe purposes of assignment, with target type \INTE
Message no. /BA1/AL_X0_M_H000
Thanks!

Hi Abhi,
in do_prepare_output you are getting mixed entity which is combination of bol entity and value node.
you can get the bol entity from mixed node by calling a method get_model_node similarly to get value node entity get_value mode method is available check the class CL_BSP_WD_MIXED_NODE methos, you will get an idea.
Cheers,
Sumit Mittal

Java Proxy error: Exception in method methodExists

Hello all!
We are doing the following synchronous scenario: CRM->XI->JavaProxy--->Third party....
Here is the process we are following to deploy our Proxy:
1.Created EJB Module Project in NWDS
2.Import the files generated by XI into ejbModule folder from ZIP file.
3.Renamed *PortTypeImpl.template to *PortTypeImpl.java
4.Compiled all code (no errors)
5.Added all the references to the SAP libraries required (taken from our XI server):
com.sap.aii.proxy.xiruntime
com.sap.xi.util.misc
com.sap.aii.messaging.runtime
com.sap.guid
6.Codified Java Proxy codified the method <interfacename> in the <intefacename>_PortTypeImpl class.
7.Edited ejb_jar.xml to add EJBs.
8.Provided a JNDI name in the file ejb-j2ee-engine.xml.
9.Built EJB archive (no errors).
10.Created a new Enterprise Application Project and pointed build path to our EJB Project.
11.Added our EJB to the Enterprise Application project.
12.Created the references to the SAP libraries in the Enterprise Application Project in the application-j2ee-engine.xml file:
com.sap.aii.proxy.xiruntime
com.sap.xi.util.misc
com.sap.aii.messaging.runtime
com.sap.guid
13.Within the Enterprise Application Project we built an EAR file.
14.We deployed our .ear file to the J2EE Engine via Visual Admin (no errors).
15.We registered our Java Proxy on the ProxyServer, using
/register?ns=<interface_namespace>&interface=<XI_Interface_Name>&bean=<EJB_JNDI_name> &method=<name of the method implemented by you on the _PortTypeImpl>
Actually, we did the following:
url for registering the EJB:
http://ithpsrq0:50200/ProxyServer/register?ns=http://banco.popular.com.pr/xi/crm&interface=mi_AccountInfo_is&bean=popularinc.com/MiAccountInfoIs_Default&method=miAccountInfoIs
Message displayed when listing interfaces (http://ithpsrq0:50200/ProxyServer/listAll)
http://banco.popular.com.pr/xi/crm#mi_AccountInfo_is = popularinc.com/MiAccountInfoIs_Default:miAccountInfoIs
1 interfaces found
When running the interface we get the following error:
com.sap.aii.af.ra.ms.api.DeliveryException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.
Does anyone have any suggestions?
What causes a "methodExists" Exception?
Please help us,
Thanks a lot!!!

Hi,
Is this a runtime of "com.sap.aii.proxy.xiruntime.core"
please check the jars used, adding this jars will solve this i guess.
aii_utilxi_misc.jar
ejb20.jar
exception.jar
jARM.jar
sapj2eeclient.jar
sapxmltoolkit.jar
aii_msg_runtime.jar
aii_proxy_xirt.jar
Also check, application-j2ee-engine.xml and see if,
com.sap.aii.proxy.xiruntime
com.sap.aii.messaging.runtime
com.sap.xi.util.misc
com.sap.guid
You wil get the jars in XI servers, you can ftp and get the jars, but you may need to search them.
Anotherthing, always take the jars from the xi servers to be sure you are compatible with the upgrades .
Hope this solves your problem.
Anirban.

Getting Inbound Java Proxy Exception in method "onMessage"

I have built an Inbound Java proxy, deployed the EJB, viewed it in the J2EE admin tool, registered the JPR settings (also listAll, reviewed results, looks OK), configure the XI scenario. When I run the XI scenario using the Runtime workbench I get the following error in the BPM Synchronous Send step (calling the Java Proxy)
"com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method onMessage".
Does anyone have any suggestions?
What causes an "onMessage" Exception?

Thanks Sudhir Here is the process I am following to deploy my Proxy, would you please validate it. Created EJB Project in NWDS, unziped XI gened proxies into ejbModule folder, renamed *PortTypeImpl.template to *PortTypeImpl.java (will add real code later), compiled all code (no errors), edited ejb_jar.xml to match your suggested format, can view EJB Candidates (and see my Proxy Bean), built EJB.JAR file (via Wizard), created new Enterprise Application Project and pointed build path to my EJB Project, within the Enterprise Application Project I built an EAR file (which includes the "EJB Project JAR File", Deployed Enterprise Application Project to the XI J2EE Engine. I can log into XI J2EE Admin and see my EJB Project and the Proxy Bean I am trying to execute. Is this the process you used to deploy the proxy bean?
Also you you turn on JPR Tracing to see what parameters are passed into the JPR engine?

Session bean "Exception in method create()"

Hello,
I have a session bean which is consuming entity bean and session bean is published as webService now when I call create method of entity bean from session bean it says "Exception in method com.syntel.exam_tool.entityBeans.tabExamTable.TabExamLocalHomeImpl0.create()."
But my create method of entity bean is blank I am not getting from where this exceptions is being thrown.
below is the code from session bean wehre I am calling entity bean
javax.naming.Context ctx;
ctx = new InitialContext();
TabExamLocalHome tabExamLocalHome = (TabExamLocalHome) ctx.lookup("java:comp/env/ejb/TabExamBean1");
TabExamLocal tabExam = tabExamLocalHome.create();
Please help me ins this problem.
Thanks

Hi Janeth,
below is the stack trace
com.syntel.exam_tool.entityBeans.tabExamTable.TabExamLocalHomeImpl0_0.create(TabExamLocalHomeImpl0_0.java:343)
com.syntel.exam_tool.sessionBeans.examTool.ExamToolBean.findByPassingScore(ExamToolBean.java:126)
com.syntel.exam_tool.sessionBeans.examTool.ExamToolLocalLocalObjectImpl0_0.findByPassingScore(ExamToolLocalLocalObjectImpl0_0.java:247)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:324)
com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
SoapServlet.doPost(SoapServlet.java:51)
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
please help me in this as I am not getting where the problem is
Edited by: new to netweaver on Sep 9, 2009 11:15 AM

Manager Self Service - An exception occurred while processing your request.

hi SAP Expert,
when i go to the Manager Self-Service > Team, Budget, Planning, the page was showing the error below :
Headcount
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 01:57_15/07/10_0059_29014050
Refer to the log file for details about this exception.
Headcount (FTE)
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 01:57_15/07/10_0060_29014050
Refer to the log file for details about this exception.
anyway i can solve the issue above, thanks.
Regards
Hariyono

here is the log details.
000D6017A6BB00730000041A00001A0400048B6A0B064F02#1279187474281#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#RONALD#11677##n/a##8132a1708ff611df8fcc000d6017a6bb#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#/System/Server#Java###Exception ID:05:51_15/07/10_0172_29014050
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.budget/com.sap.pct.erp.mss.budget_page/com.sap.pct.erp.mss.bw_cost_center
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : RONALD
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:523)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bw/BEx?sap-client=<System.client>&sap-language=<Request.Language>&accessibility=<User.Accessibility[SAP_BOOL]>&style_sheet=<LAF.StylesheetUrl[url_ENCODE]>&<TrayInformation[IF_true PROCESS_RECURSIVE]>&<Authentication>&<Report>&<BusinessParameters>&\#39;; the problem occured at position 82. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more

Tomcat : exception during startup processing

Hi !
I have this exception when trying to start Tomcat :
Starting service Tomcat-Standalone
Apache Tomcat/4.1-dev
Starting service Tomcat-Apache
Apache Tomcat/4.1-dev
Exception during startup processing
java.lang.reflect.InvocationTargetException:java.lang.NoSuchError:java.lang.Runtime: method addShutdownHook(java/lang/Thread;)V not found
at org.apache.catalina.startup.Catalina.start (Unknown source)
at org.apache.catalina.startup.Catalina.execute(Unknown source)
at org.apache.catalina.startup.Catalina.process(Unknown source)
at java.lang.reflect.Method.invoke (Native Method)
at java.lang.reflect.Method.invoke (Compiled Code)
at org.apache.catalina.startup.Bootstrap.main (Compiled Code)
I have imported the jdni.jar in my jdk 1.2.2, and set variables (PATH, JAVA_HOME, CATALINA_HOME, CLASSPATH), and I don't have Apache.
Please, help me if you have any idea !
Gaelle.

Hi,
I got this error too when I installed Tomcat 3.2.1 on JDK1.2.2. But when I changed by JDK to 1.3.1 and altered the tomcat.bat file to take JAVA_HOME to jdk1.3.1 path, it worked fine.
Change your JVM to JDK1.3.1 and this should get rid of the error.
Regards,
Seetesh

Exception caught during processing mail message

I am getting the following error in CC monitoring for my sender mail adpater:
exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 001I NO The requested item could not be found.
Please tell me how to resolve ?

NOw when i changed the protocol from IMap to POP3 the error is
exception caught during processing mail message[18]; com.sap.aii.af.mp.processor.ModuleProcessorException: Error during processing local bean: localejbs/AF_modules/MessageTransformBean caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at AF_modules, the whole lookup name is localejbs/AF_modules/MessageTransformBean.

System error in block parforEach: Exception why is process finished?

Hi everybody,
we split a message in BPM. Then we loop the multiline-container element.
For each line-item we call a WebService synchrounous.
We got a exception branch for system errors.
Now we got the following problem:
Our produces abount 3000 line-items.
While processing e.g. item 1000 we got a system error and the BPM jumped into the execption branch. After processing the exception branch the process FINISHED!
We assumed that the process would go on processing the remaining items!
Is there a workaroud, that the process does go on with processing the remaining items?
Regards Mario

Hi,
After handling the exception, the process will be continuing after that block. So you can try to put the block within a loop until all the line items get over.
Regards,
P.Venkat

Exception in method process

Similar Messages

Maybe you are looking for