Acknowledgement errors in PI - JMS scenario

Hello,
We have a scenario R3 Idoc -> PI7.0 -> JMS. After the Idoc message is sent to PI, In the sxi_monitor, in acknowledgement status column, I normally see a red icon which says ack not possible. But for few JMS interfaces, I observe there is a green icon which says waiting for acknowledgement.
In the smq2 monitoring, I see queues for this acknowledgment message into error with IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY.
Did someone face a similar scenario. Even though the messages reach the third party via JMS queue, these messages are collected in queue with sysfail error. Please help how to get rid of this.
Regards,
Swapna

If you do not want to have acknoledgement, in your sender system, run ABAP program "IDX_NOALE"
In "Maintain Partner System Acknowledgment" screen, specify your Sender Port and client
Then you can turn off following acknowledgements:
System OK
System Error
Application OK
Application Error
Regards
Liang

Similar Messages

File to JMS Scenario - Error is Receiver JMS Adapter

Hi,
I am working on File to JMS scenario. I have deployed all required jars for MQ 6.0.2 in SDM. Create all MQ related objects. I am getting following error for Receiver JMS adapter in CC Monitoring.
Please let me know if I have missed anything. Is there anything to do in Visiual Administrator->JMS Provider or JMS Connector for these kind of Scenarios?
Thanks in Advance...
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

Hi,
I have made my Qmanager as default Qmgr. Now the error is :- Socket connection attempt refused
Recv JMS Communication Channel Error:-
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

Error while invoking a scenario from another scenario through ODIStartScen

hi,
my requirement is to call a scenario from another scenario. the main scenario contains an interface to get data from jms que and put that in DB and then invoke the inner scenario through ODIStartScen and am executing the scenario through an agent which is on another machine. when am trying to execute the main scenario then i get following error while invoking inner scenario in ODIStartScen step ....
ERROR:::::
oracle.odi.runtime.agent.invocation.InvocationException: HTTP/1.1 500 Internal Server Error
     at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:271)
     at oracle.odi.runtime.agent.invocation.support.InternalRemoteRuntimeAgentInvoker.invokeStartScenario(InternalRemoteRuntimeAgentInvoker.java:149)
     at com.sunopsis.dwg.tools.StartScen.actionExecute(StartScen.java:266)
     at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(SnpsFunctionBaseRepositoryConnected.java:155)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java:3185)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java:1414)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2785)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1818)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:559)
     at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:481)
     at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1040)
     at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
     at java.lang.Thread.run(Thread.java:662)
the error that is in ODI server log is:
Root cause of ServletException.
org.springframework.jdbc.CannotGetJdbcConnectionException: Create DwgConnectConnection to master repository failed; nested exception is java.sql.SQLException: Pool connect failed : java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers]
     at oracle.odi.core.persistence.dwgobject.DwgRepositoryConnectConnectionUtils.doGetMasterDwgConnectConnection(DwgRepositoryConnectConnectionUtils.java:93)
     at oracle.odi.core.persistence.dwgobject.DwgRepositoryConnectConnectionUtils.doGetMasterDwgConnectConnection(DwgRepositoryConnectConnectionUtils.java:49)
     at oracle.odi.core.persistence.dwgobject.DwgRepositoryConnectConnectionUtils.doGetMasterDwgConnectConnection(DwgRepositoryConnectConnectionUtils.java:58)
     at oracle.odi.core.security.SecurityManager.doODIInternalAuthentication(SecurityManager.java:348)
     at oracle.odi.core.security.SecurityManager.createAuthentication(SecurityManager.java:331)
     at oracle.odi.runtime.agent.servlet.AgentServlet.processRequest(AgentServlet.java:494)
     at oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:454)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.sql.SQLException: Pool connect failed : java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers]
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
     at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:113)
     at com.sunopsis.sql.SnpsConnection.createConnection(SnpsConnection.java:380)
     at com.sunopsis.sql.SnpsConnection.connect(SnpsConnection.java:338)
     at oracle.odi.core.persistence.dwgobject.DwgRepositoryConnectConnectionUtils.doGetMasterDwgConnectConnection(DwgRepositoryConnectConnectionUtils.java:88)
     at oracle.odi.core.persistence.dwgobject.DwgRepositoryConnectConnectionUtils.doGetMasterDwgConnectConnection(DwgRepositoryConnectConnectionUtils.java:49)
     at oracle.odi.core.persistence.dwgobject.DwgRepositoryConnectConnectionUtils.doGetMasterDwgConnectConnection(DwgRepositoryConnectConnectionUtils.java:58)
     at oracle.odi.core.security.SecurityManager.doODIInternalAuthentication(SecurityManager.java:348)
     at oracle.odi.core.security.SecurityManager.createAuthentication(SecurityManager.java:331)
     at oracle.odi.runtime.agent.servlet.AgentServlet.processRequest(AgentServlet.java:494)
     at oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:454)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.sql.SQLException: Pool connect failed : java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers]
     at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:258)
     at weblogic.jdbc.pool.Driver.connect(Driver.java:160)
     at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:652)
     at weblogic.jdbc.jts.Driver.connect(Driver.java:127)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
     at org.springframework.jdbc.datasource.UserCredentialsDataSourceAdapter.doGetConnection(UserCredentialsDataSourceAdapter.java:162)
     at org.springframework.jdbc.datasource.UserCredentialsDataSourceAdapter.getConnection(UserCredentialsDataSourceAdapter.java:133)
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter$ConnectionProcessor.run(LoginTimeoutDatasourceAdapter.java:217)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
Caused By: java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers]
     at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:835)
     at weblogic.security.service.IdentityUtility.authenticatedSubjectToIdentity(IdentityUtility.java:30)
     at weblogic.security.service.RoleManager.getRoles(RoleManager.java:183)
     at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:375)
     at weblogic.jdbc.common.internal.JDBCUtil.checkPermission(JDBCUtil.java:231)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:357)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:317)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:106)
     at weblogic.jdbc.pool.Driver.connect(Driver.java:149)
     at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:652)
     at weblogic.jdbc.jts.Driver.connect(Driver.java:127)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
     at org.springframework.jdbc.datasource.UserCredentialsDataSourceAdapter.doGetConnection(UserCredentialsDataSourceAdapter.java:162)
     at org.springframework.jdbc.datasource.UserCredentialsDataSourceAdapter.getConnection(UserCredentialsDataSourceAdapter.java:133)
     at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter$ConnectionProcessor.run(LoginTimeoutDatasourceAdapter.java:217)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
kindly help me out.
thanks in advance.

In the batch File write this way
cd E:\OraHome_ODI\oracledi\bin
E:
startscen EXT_DATA 002 GLOBAL In case you are providing the values (EXT_DATA 002 GLOBAL) as parameter
then call the startscen this way
cd E:\OraHome_ODI\oracledi\bin
E:
startscen %1 %2 %3

Receiving Acknowledgement error from SOAP application

Hi Everyone,
I am working on SAP-> PI -> SOAP scenario. The PI message shows Acknowledgment error
with the following error text :
"Adapter Framework caught exception: SOAP: response message contains an error
XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: javax.xml.rpc.soap.SOAPFaultException "
The message of the same scenario were processed successfully initially but today some of the message got
stucked with the Acknowledgement error from the receiver application.
I tried to resend the message from RWB but could not succeed.
Kindly guide to troubleshoot the issue.
Regards,
Robinson Thomas

Hi Robinson,
It's mean the Web Service Provider return you unknown message format. It can be due to error happening in the provider.
Youd should check with the provider what is the problem during that period.
Regards
Fernand

IDOC acknowlegment IDOC-PI-JMS Scenario

Hi,
I have a IDOC-PI-JMS scenario. (With msg branching, PI 7.1 EHP1)
The message are processing but it seems that there is no acknolegment sent back to the ECC system; the outbound IDOC remains in status 03.
By turning acknologement off in IDX_NOALE everything is OK except the IDOC remaining in status 03.
I found this how-to document for the IDOC-PI-IDOC scenario, but I need to configure IDOC acknowlegment for IDOC-PI-JMS scenario, someone can point to some guide/how-to? Do I need to still do all the ALE Audit configuration?
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
Thanks,
Martin

Hi Martin,
Please go this article [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true] and [http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm] for information about How to handle the Idocs acknowledgements.
Regards,
Kalpana.

ODI 20088:Error While Generating The Scenario

Hi,
Today I have change the name my logical file schema(name is change to lower to upper case).Then select the new schema from File Model (only it is using the File Schema).Then Try to generate the scenario again but getting an error like this:
ODI 20088:Error While Generating The Scenario
java.lang.NullPointerException
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.treatPopSourceSet(SnpGeneratorSQLCIT.java:7990)
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.treatJobPopCollectionBuild(SnpGeneratorSQLCIT.java:7726)
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.preComputePop(SnpGeneratorSQLCIT.java:7668)
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.treatJobPop(SnpGeneratorSQLCIT.java:7568)
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.treatPackageStep(SnpGeneratorSQLCIT.java:10477)
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.mainGenPackageScenario(SnpGeneratorSQLCIT.java:2883)
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.mainGenPackageScenario(SnpGeneratorSQLCIT.java:2817)
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.mainGenScenSourceScenario(SnpGeneratorSQLCIT.java:11481)
     at com.sunopsis.dwg.codeinterpretor.SnpGeneratorSQLCIT.mainGenScenSourceScenario(SnpGeneratorSQLCIT.java:11505)
     at com.sunopsis.graphical.dialog.SnpsDialogScen.generateScen(SnpsDialogScen.java:190)
     at com.sunopsis.graphical.scenario.DwgScenGeneratingWizard.generate(DwgScenGeneratingWizard.java:68)
     at oracle.odi.ui.action.SnpsPopupActionGenerateScenHandler.actionPerformed(SnpsPopupActionGenerateScenHandler.java:103)
     at oracle.odi.ui.SnpsActionControler.handleEvent(SnpsActionControler.java:86)
     at oracle.ide.controller.IdeAction.performAction(IdeAction.java:529)
     at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:897)
     at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:501)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
     at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
     at java.awt.Component.processMouseEvent(Component.java:6297)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3275)
     at java.awt.Component.processEvent(Component.java:6062)
     at java.awt.Container.processEvent(Container.java:2039)
     at java.awt.Component.dispatchEventImpl(Component.java:4660)
     at java.awt.Container.dispatchEventImpl(Container.java:2097)
     at java.awt.Component.dispatchEvent(Component.java:4488)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4575)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4236)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4166)
     at java.awt.Container.dispatchEventImpl(Container.java:2083)
     at java.awt.Window.dispatchEventImpl(Window.java:2489)
     at java.awt.Component.dispatchEvent(Component.java:4488)
     at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:668)
     at java.awt.EventQueue.access$400(EventQueue.java:81)
     at java.awt.EventQueue$2.run(EventQueue.java:627)
     at java.awt.EventQueue$2.run(EventQueue.java:625)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
     at java.awt.EventQueue$3.run(EventQueue.java:641)
     at java.awt.EventQueue$3.run(EventQueue.java:639)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:638)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Please Help
Thanks
Anindya

If you have not deleted the old file schema, then it should have been work but it seems to be theissues with the link between interface and model .
I cannot say this is the actual reason but it might be. Since you have draged the file datastore to interface, interface is probably pointing to old schema and file model is pointing new schema.
I guess you have to recreate the interface again. Let me know how it is going with you
Bhabani
http://dwteam.in

Error in file-file scenario: HTTP response contains status code 503

Hi folks,
I've encountered the foll error in file-file scenario:
Testing file-file scenario (followed the blog: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flatFILETOFLATFILE&)
Initially i was hving problems with recvr comm channel, which are now resolved. File is sent successfully but not recvd. I tried to modify the scenario above and change the file type to 'Text' but still got the same error.
I've checked SICF -->default_host/xi/engine , we dont maintain logon data there. when i test the default_host/xi/engine service, it resolves into an ip addr as follows:
http://<hostname>.<domain.com>:8001/sap/xi/engine?sap-client=<clientNo>
(Also, we hv a BW system running on the same server ,which uses a fully qualified domain, while we dont which is why we get the above domain. Im not sure if there are any issues with that.)
and we get the foll error:
Error Code 10060: Connection timeout
If i remove the domain manually, im prompted for userid/pwd and get the foll result:
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Pipeline specified in URL attribute (type) not existing</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code>
<SAP:P1>/sap/xi/engine?sap-client=<clientNo></SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Pipeline ID , which is expected as value of attribute "type" in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=811)</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
also, we dont hv any overload issues as this is dev env and not many of us are using the xi server. Would really appreciate if any of you can share your inputs on how to resolve this. Thanks!!
cheers
Prachi

Hi ,
Look in to this for all errors
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
Refer SAP Note 803145,807000,791655
<b>Award Points if found usefull.</b>

ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

Hi,
I got this error in FIle-IDOC scenario.
ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
Is there any other suggestions?

Hi aarthi,
I suggest u chk all d settings dat u hav done..
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 7)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
MenoN

How to Setup Forward Error Handling in PI Scenarios. Can you help me with the same with screen shots if possible?

Dear all
How to Setup Forward Error Handling in PI Scenarios. Can you help me with the same with screen shots if possible?
Thanks
Regards
karan

Hello
These are the following errors
1. Trace level="1" type="T">no interface action for sender or receiver found</Trace>
2. <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!
3.
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</
Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>Trace level="3" type="T">Error of the prevous version:</TraceTrace level="3" type="T">Error ID APPLICATION_ERROR</Trace>
tThere are repeating errors also.
TThanks
Regards
kkaran

Duplicate MessageID error in sender JMS

Hi,
could anyone provide some inputs in getting through the following error in sender JMS:
A duplicate JMS message was received. It was was received earlier and processed with the XI message ID 3fc663bf-c3ee-4eb8-179e-ad28e0ecde3a. It will be ignored and discarded from the JMS queue.
I have tried changing follwoign settings but still no use...
Under the PROCESSING tab, under XI SETTINGS
Time period for Duplicate Check for EO(IO) (secs) it was set to 86400
I have changed this to 300 seconds
Regards,
Chinna.

remove the duplicate entry from the java table XI_AF_SVC_ID_MAP

Proxy to JMS Scenario: switch from sync to async proxy,does it makes sense?

Hi @all,
i've implemented a sync proxy to JMS scenario that works well. Backend is ECC 6.0 and Middleware is PI 7.1.
Business Case: Run a request with a number and get a response back with a corresponding entry for the number. That means, there is always a response expected.
Now the following thing appears: the receiver system could not handle many calls at one time (200 calls are planned at each run), the calls reduces the performance. Now gys at receiver system likes to develope a buffer of 10 seconds between the requests to handle some kind of load balancing with that. That means for the request that it the response takes +10 seconds back to backend. It is also possible to handle that in SAP backend with a waiting-statement in coding, so there is no need to go from sync to async - but the customer requested us to implement this scenario in async.
JMS is always async, I know. But the Service Interfaces for Inbound and Outbound are of mode sync - so I can call my outbound Interface class in backend with Importing Output and Exporting Input.
My question is: makes it sense to go from sync to an async scenario?
And how looks the coding in backend for the response? I guess that it only makes sense to switch to async when no response entry is needed (example: for write operations).
Thanks in Advance,
Stefan

> But in case of switching, what is the best way?
> Should I implement 2 senarios? Or is it ok to switch the Inbound and Outbound Service Interface from sync to async?
I don't think you need 2 scenarios for this. Just one is enough with different RDs.
Over all in this case you have to re-create/modify the service interfaces and also you have to create 2 interface mappings. You have to also create the new inbound and outbound proxies since service interface mode will be changed. For outbound proxy the code can be reused and for inbound proxy also logic and code can be taken from your old code.

Query doesn't work in APD, Error: column store error: fail to create scenario: [340 2048

Hi Experts,
We got a problem here.
We have a query ran without any problems in RSRT. But when I try to put it as data sources(infoprovider) in APD.
I got following error:
column store error: fail to create scenario: [340 2048
We are in BW731006 & ABAP731006.
Any advise?
Thanks in advance!
Tengran

Hi,
Can you check this part in error mentioned by clicking as highlighted in red box. It will give you a correct idea about the issue ::
Also share the detailed error with us as well.
Best Regards,
Arpit

Error Destination in JMS Transport Configuration page (Proxy Services)

Hi, Can anybody provides me the sample of Error Destination in JMS Transport Configuration page (Proxy Services) .I need to know the format. I am using "jms://<host:port[,host:port]*/factoryJndiName/destJndiName>", but it does not work.
From Oracle webstie, http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html, the detail description of Error Destination is " In this field you can configure the name of the target destination for the messages, which have reached the maximum number of retry count. "

Can you provide the JNDI name of the error destination alone there ?

Regarding File to JMS scenario

Hi friends please help me on file 2 JMS scenario. send me the screen shots of the below scenario.

Hi
Refer to following blogs .
JMS Adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how%20to%20use%20the%20content%20conversion%20module%20with%20the%20xi%203%20j2ee%20jms%20adapter
/thread/217893 [original link is broken]
JMS adapter -Message format pre-requisites
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
Please go through the following links.....
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
First would be to deploy drivers for JMS scenarios - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
Secondly, to configure JMS adapters;
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
In case JMS scenario that you have is a sync one, in that case if you are below SP19 you might have to build a BPM - ref: http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
Else ref:
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
How to correlate JMS messages - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc983be70c0
How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Thanks!!

Rfc-xi-jms scenario

I have a rfc-xi-jms scenario. A message is triggered from ECC. HOw can I check whether
message is send from ECC ?? I mean ....I want to check in ECC system ?? Is there any Tcode
to see the success message or payload in ECC ?? In SXMB_MONI I am not able to see the RFC messages.
Regards
kumar

>we can see proxy messages in ECC system through sxmb_moni right ??
You are Right,
In Proxy there is no protocol conversion hence it might reflect in the Sxmb_moni.
> In ECC system why can't we see the messages in sxmb_moni ?? For RFC..
The protocol conversion happens and it is taken care by the adapters to XML Message.
Regards
Agasthuri Doss

Acknowledgement errors in PI - JMS scenario

Similar Messages

Maybe you are looking for