Call adapter: Error exception retnr from pipeline processing

Hi!
I am facing with the following error in sxmb_moni by retrieving the message from business system A.
Errror in part Call adapter
System_Error: Error exception retnr from pipeline processing
Can some one help me tp solve this problem?
Thank you very much!
regards
Holger

Hi,
Mark RFC destination AI_RUNTIME_JCOSERVER as UNICODE
check this Error exception return from pipeline processing
Re: Queue problem ?
Thanks!
Edited by: Sudhir Tiwari on Dec 2, 2008 1:37 PM
Edited by: Sudhir Tiwari on Dec 2, 2008 1:37 PM

Similar Messages

"System_Error" Error exception return from pipeline processing!

Hi all,
I get this error everytime I click the red flag in sxmb_moni:
com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_CUST_TO_DFS_MM_: RuntimeException
in Message-Mapping transformatio~
When I go to TRACE of SOAP Header, I see this error:
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
The messages were not posted as 'Application document not posted' in we05: they cannot be seen in we05. Because of this, the number of IDOCS posted in we05 is not equal to the XMLs generated in sxmb_moni.
Please help.
Thanks.
Regards,
IX

CUST_TO_DFS_MM
Check this mapping...sometimes just testing in IR is not sufficient....error can also occur at runtime...so take the payload from SXMB_MONI and then test to see why it is failing....
Also there will be some more error text alongwith CUST_TO_DFS_MM...check it to drill down to the root cause...
Edited by: abhishek salvi on May 8, 2009 1:00 PM

Error exception return from pipeline processing

Hi Friends,
In my File to Proxy scenario, i am getting the following error:
"<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>".
The common error i received in the monitor is Message Mapping error.
But i have checked clearly in the IR, all the mappinngs are correct. While doing the test, it is going well.
I have gone through some sdn blogs, they have stated like cache refresh, but after doing cash refresh also i am getting the same error.
Can anyone give me suggestion?
Thanks in advance.
Regards
Bala

Hi Aashish Sinha,
I have checked the source code, it is fine. I am getting error in the target code. It is saying that particular filed cannot be mapped. But in the taget that field is existing.
Regards
Bala

XI - Call Adapter Error - HTTP client. Code 402 reason ICM_HTTP_TIMEOUT

I am using HTTP adapter to post XML PO to vendor's site. We are having this problem with one of our vendor when PO's has more than 15 line items. XI server is getting error-"Call Adapter Error - HTTP client. Code 402 reason ICM_HTTP_TIMEOUT". Actually PO is posted good for the first time on vendor's site but XI is getting above error message and it keeps posting it again. Is there anyway to stop it otherthan manually stopping the XI message? Is there anyway to increase the wait time of the XI server to get the message.
Thanks in advance.
Mrudula Patel

I'm getting the same issue "500 TIMEOUT error" in runtime work bench-->IE--->Test Message. When i manually trigger the file.
The issue is basically from 01-01-2015 02:00 pm to 02-01-2015 01:am , File is picked from source ftp folder and places in archive but xml messages are not reflecting in SXMB_MONI.
Today suddenly after 01:00 am messages are successfully processing.
Please help on this issue. Many Thanks.

Internal error: exception thrown from the servlet service function

when i invoke the servlet in unix iplanet server i got the error
Kindly let me get the solution .i am in 11th hour.
[06/Jan/2006:09:30:28] info (10646): Internal Info: loading servlet
/servlet/Ipl
XmlServlet
[06/Jan/2006:09:30:28] info (10646): /servlet/IplXmlServlet: init
[06/Jan/2006:09:30:28] failure (10646): Internal error: exception thrown
from the servlet service function (uri=/servlet/IplXmlServlet/):
java.lang.NullPointerException, stack: java.lang.NullPointerException
at IplXmlReqHandler.generateRsp(IplXmlReqHandler.java:452)
at IplXmlReqHandler.processRequest(IplXmlReqHandler.java:168)
at IplXmlServlet.processRequest(IplXmlServlet.java:219)
at IplXmlServlet.doGet(IplXmlServlet.java:184)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:701)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:826)
at
com.netscape.server.http.servlet.NSServletRunner.Service(NSServletRun
ner.java:513)
Thanking you
brindasanth

you are in the wrong forum for this kind of question/product,
goto:
http://swforum.sun.com/jive/forum.jspa?forumID=16
(in case you don't like "goto" - look at it like a "forward" :-) )
additionally don't forget to mention
- OS version
- WebServer version + SP
- .. the more the better
rgds.
/u

Internal error: exception thrown from the servlet service function (uri=/servlet/auth)

I am getting the follow error in my webserver error log very offen. I am running iPlanet Delegated Administrator 4.5 and iPlanet WebServer 4.1 SP5. Sometimes I have to stop and start the web server because users can no longer authenticate to Delegated Admin. Does anyone know what this means.
Internal error: exception thrown from the servlet service function (uri=/servlet/auth): javax.servlet.ServletException, Stack: javax.servlet.ServletException
at netscape.nda.servlet.NDAAuth.execute(NDAAuth.java, Compiled Code)
at netscape.nda.servlet.NDAServlet.doPost(NDAServlet.java, Compiled Code)
at netscape.nda.servlet.NDAServlet.doGet(NDAServlet.java, Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java, Compiled Code)
at com.netscape.server.http.servlet.NSServletRunner.Service(NSServletRunner.java, Compiled Code)"

Hi,
I hope below link will help you.
http://knowledgebase.iplanet.com/ikb/kb/articles/4761.html
Thanks,
Daks.

Internal error: exception thrown from the servlet service function (uri=/login))

I have done an install of iPlanet Portal Server on a Solaris 8 machine and when I try to access the main Page I get:
[26/Apr/2002:16:15:27] failure (21872): Internal error: exception thrown from the servlet service function
(uri=/login): java.lang.NullPointerException, stack: java.lang.NullPointerException
at com.iplanet.portalserver.auth.service.AuthD.isClientDetectionEnabled(AuthD.java:520)
at com.iplanet.portalserver.auth.service.AuthD.getClientType(AuthD.java:532)
at com.iplanet.portalserver.auth.service.AuthRequest.<init>(AuthRequest.java:102)
at com.iplanet.portalserver.auth.service.AuthRequest.getAuthRequest(AuthRequest.java:177)
at com.iplanet.portalserver.auth.service.LoginServlet.doGetPost(Compiled Code)
at com.iplanet.portalserver.auth.service.LoginServlet.doGet(LoginServlet.java:990)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:701)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:826)
at com.netscape.server.http.servlet.NSServletRunner.Service(NSServletRunner.java:507)
, root cause:
Suggestions? I have sucessfully installed IPS before, but I cannot figure out the cause of this error.
Mike

Looks like a patch conflict ..
Check /var/sadm/patch and see
if this patch 108875-07 is present, if you have a later patch than that then you might run into the above problem ..

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.

Call Adapter Error - 401 Unauthorized

Hi,
We are using Multi Mapping where it splits 1 message into n messages. The n messages split by this scenario in trun calls another scenario configured in the same PI server using SOAP Adapter.
The called scenario is SOAP --> Siebel using iWay Adapter.
When the number of messages split are huge in order of thousands, the server is going for a toss and the called scenaio is failing at Call Adapter Step in IE with HTTP Error 401 Unauthorized. Few of the messages manage to pass successfully.
Anticipating your valuable inputs.
Thanks.
Regards,
Sudharshan N A

Hi Sudharshan,
There can be different reasons for getting HTTP 401: Unauthorized error. As you said, few of the messages are being passed to the called application, I would request you to check the scalability of the Seibel Server.
Also if you are using a connections from a connection pool, then it may be that the pool itself is getting exhausted, though mostly we get Socket exception/Connection Exception/IO Errors in these cases.
The other reasons can be that the user you are using to connect Seibel dont have enough permissions. But it is ruled out as you said some messages have been processed.
If the Seibel server is SSL enabled, and your PI doesn't have any certificate configured, then also you may get such errors.
Regards,
Sugata

Call Adapter Error

Hello everybody,
I have a synchronous scenario ABAP Proxy->XI->RFC, the reason why we used XI it's beacuse by company politics any systems integration needs to go by SAP XI, and the reason why we used RFC in the receiver system it's because by company politics too we can't generate proxies in that system, so we decided to go by RFC, now the interface is working really fine, the abap proxy in the sender system is called by a Z program, so this program gives a report of every record, and the problem that I'm facing is that I need to give back to the sender systems errors like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Date '9999-12-32' has a wrong format at field VALIDA: Unparseable date: "9999-12-32"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
this error it's beacuse of the day 32 of the month december, we know that, but this error is only treated as exception CX_AI_SYSTEM_FAULT in the Proxy, and I need to pass the SAPAdditionalText of the error above to the sender system, is there a way to give back to the proxy this text so it will be more explicit in the error and not just a SYSTEM_FAULT???????, thanks in advance.
Regards,
Julio Cesar

Hello VJ,
Thanks for your answer, about the solution your are kindly giving me, it's not really clear to me in this point:
" When ever you get such exceptions, you need to catch them
in your RFC and fill your own exception object and throw it."
the exception I'm getting is a default by SAP, not one I could raise, maybe I'm not understanding right your proposal could you explain me more this part, do you mean that if I declare an exception in my RFC even if I'm not doing the RAISE is going to catch the exception I'm getting?, thanks a lot for your answer.
Regards,
Julio Cesar

Call adapter error --- BPM to RFC

Hi,
I'm calling a simple RFC from a bpm, and the rfc in turn calls a proxy.At the step where i pass the data from bpm to the RFC i get the following error at the call adapter step:
<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: Problem inserting a7f68d50-f88a-11db-ad02-001560a7b7a4(INBOUND) into the database: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column</SAP:AdditionalText>
this seems to be some database error, but i'm not insertinga ny data into any table.
Can anyone tell me about this.

Hi-
Check the Data types you have mentioned for attributes.

New problem calling PL/SQL based WS from BPEL process

I have created a webservice based on a PL/SQL package based function with JDeveloper and deployed the web service on the BPEL OC4J server.
Calling the web service endpoint directly from internet explorer works fine.
I have also created and deployed a BPEL process to call this web service. When i run the process it completes normally but returns an Oracle error in the out-variable: "Ora-06502 Numerical value error".
Through my PL/SQL logging i can see that the input-variable to the PL/SQL function is empty (so when i try to use this value it gives me the Ora-06502 error).
When i check the audit trail of the BPEL process instance i find that the assignment of the input variable is ok. This input variable is used in the invokation of the web service (and at this point still has the proper value).
What can be wrong? (the only part i cannot trace is the working of the Java stub created by JDeveloper).
Any ideas?
thanks, Bart

This is the complete stack trace:
<2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: CataLog
<2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> inputContainer: {InputParameters=<CATLOG xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/EBILLING/CATALOG/"><ID_AZIENDA>134</ID_AZIENDA><ID_PROGETTO>134</ID_PROGETTO><CAPTURE_DATETIME>1959</CAPTURE_DATETIME><FULLNAME>lkjh</FULLNAME><PATHNAME>kjsf</PATHNAME><FILENAME>kjsf</FILENAME><DESTINATION_PATH>kjsf</DESTINATION_PATH><MOVE_DATETIME>1959</MOVE_DATETIME><SIZE_BYTES>134</SIZE_BYTES><LAST_WRITE>1959</LAST_WRITE><ID_THOR>2345234</ID_THOR><SNAPSHOT_PATH>kjsf</SNAPSHOT_PATH></CATLOG>}
<2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> callProps: {is-initial-call=true, parentId=5602, process-id=StoredProcedure, rootId=5602, conversationId=bpel://localhost/default/StoredProcedure~1.0/5602-BpInv0-BpSeq0.3-3, location=null, priority=0, work-item-key=5602-BpInv0-BpSeq0.3-3, domain-id=default, revision-tag=1.0}
<2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl
<2004-12-01 10:48:52,014> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=CataLogportTypeQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_pttserviceQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog
<2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[{http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_ptt]: Locating jndiAdapterInstance eis/CatapultDBLog
<2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
<2004-12-01 10:48:52,016> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
<2004-12-01 10:48:52,234> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
<2004-12-01 10:48:52,235> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
<2004-12-01 10:48:52,294> <INFO> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Invoking JCA outbound Interaction
<2004-12-01 10:48:52,296> <DEBUG> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger log> client acquired
<2004-12-01 10:48:52,297> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
<2004-12-01 10:48:52,299> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
<2004-12-01 10:48:52,300> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happenned
ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more
<2004-12-01 10:48:52,302> <DEBUG> <default.collaxa.cube.ws> <BPELInvokeWMP::__invoke> Caught RemoteException
orabpel.apache.wsif.WSIFException: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA@788a7bhttp://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] : Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
; nested exception is:
ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:464)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: ORABPEL-11813
Encountered an unexpected exception while trying to execute the interaction.
An unexpected exception occurred while trying to execute the interaction for invoking the API.
Analyze and correct the error if possible. Contact oracle support if error is not fixable.
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
... 25 more
Caused by: java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.<init>(Integer.java:609)
at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
... 27 more

Adobe Form Call: System Error Exception

Hi,
I have created an Adobe Form for printing Invoices. When I call this form from print program using function module call "CALL FUNCTION fp_funcname" it throws Exception "System Error = 2". Can any one flash some light to resolve this issue.
Here I have given that function module call below.
CALL FUNCTION fp_funcname
EXPORTING
/1BCDWB/DOCPARAMS = fp_sfpdocparams
WA_HEADER         = wa_header
T_ITEM                   = t_item
EXCEPTIONS
USAGE_ERROR     = 1
SYSTEM_ERROR   = 2
INTERNAL_ERROR = 3
OTHERS                 = 4.
Thanks
Hari

Hi,
In your initialization use this class : cl_fp=>get_ads_connection( ).
you move this to a parameter fp_outputparams .
MOVE cl_fp=>get_ads_connection( ) TO p_conn.
where fp_outputparams   TYPE sfpoutputparams called in
CALL FUNCTION 'FP_JOB_OPEN'
    CHANGING
      ie_outputparams = fp_outputparams
    EXCEPTIONS
      cancel          = 1
      usage_error     = 2
      system_error    = 3
      internal_error = 4
      OTHERS          = 5.
Thanks
Dan

Message failing in SXMB_moni----Error while reading from the secure store

Hi,
The scenario is as below
A file is picked up from a folder and processed to enrich it.This enriched file is then written back in a different folder.
The message is failing in sxmb_moni while trying to write the file in the folder.
The PI system is a system copy of another system and few of the configuration objects are transported through a tpz file to this PI system.The file receiver channel used to write this file is also transported through this tpz file.
Below is the error seen in moni.:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText>Error while reading from the secure store: ERROR_U: No service user password found for Adapter Engine</SAP:AdditionalText><SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine
</SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
Below is Trace log:
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP"></Trace>
<Trace level="1" type="T">error reading secstore:Error while reading from the secure store: ERROR_UNKNOWN: System-dependent data for entry changed: / (SECSTORE,031) </Trace>
<Trace level="1" type="System_Error">Error while reading access data (URL, user, password) for the Adapter Engine </Trace>
</Trace>
</Trace>
<Trace level="1" type="System_Error">Error exception return from pipeline processing! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
Is this because PI system is a system copy of another system ?
Regards,
Sneha

Error while reading access data (URL, user, password) for the Adapter Engine
Check out Michal's reply:
Re: URL for Central Adapter Engine
As you said there was a system copy it may be the case that some things were not configured properly

In the pipeline service, when does call adapter mean

In the pipeline service, when the call adapter step execute, will it call the XI adapter or the outbound adapter

Hi,
It calls the outbound adapter.
So if your receiver SAP system using proxy/RFC adapter is down, you get a Call Adapter error in SXMB_MONI.
Regards,
Puloma.

Call adapter: Error exception retnr from pipeline processing

Similar Messages

Maybe you are looking for