cancel
Showing results for 
Search instead for 
Did you mean: 

Internal error when testing configuration

Former Member
0 Kudos

Dear experts,

we have moved to PI 7.3 and now we systematically have the following error when trying to test the configuration scenario in the Directory through test configuration tool :

Internal error on Receiver Determination Step

In the log of NWA we have the following :

null

Thrown:

java.lang.NumberFormatException: null

at java.lang.Integer.parseInt(Integer.java:417)

at java.lang.Integer.parseInt(Integer.java:499)

at com.sap.aii.ib.server.abapcache.logons.IS_LogonData.<init>(IS_LogonData.java:41)

at com.sap.aii.ibdir.server.simulation.AbapHttpTaskBroker.execute(AbapHttpTaskBroker.java:70)

at com.sap.aii.ibdir.core.simulation.task.plsrv.JavaPlsrvTaskImpl.execute(JavaPlsrvTaskImpl.java:89)

at com.sap.aii.ibdir.core.simulation.DefaultTaskBroker.execute(DefaultTaskBroker.java:240)

at com.sap.aii.ibdir.server.simulation.TaskQueryService.specialQuery(TaskQueryService.java:33)

at com.sap.aii.ib.server.query.SpecialQueryServiceProvider$SpecialQueryServiceImpl.specialQuery(SpecialQueryServiceProvider.java:63)

at com.sap.aii.ib.server.query.QueryServiceImpl.specialQuery(QueryServiceImpl.java:443)

at com.sap.aii.ib.server.query.QueryServiceBean.specialQuery(QueryServiceBean.java:112)

at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

at $Proxy1710.specialQuery(Unknown Source)

at sun.reflect.GeneratedMethodAccessor545.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:240)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:462)

at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)

at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)

at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Any help would be greatly appreciated.

BR,

Jamal

Accepted Solutions (1)

Accepted Solutions (1)

iaki_vila
Active Contributor
0 Kudos

Hi,

Are you using sender agreement?, because the sender agreement is not found as well. Have you filled in the test the sender and receirver fields?

Remember that this test doesnt work with the integrated configuration object, in the case if you are using it.

Finally, you could share a screenshoot of your objects and we could check them.

Regards.

Former Member
0 Kudos

Hi,

thanks for your reply

We are actually using ICO, so you are saying it is normal to have this error ?

Is there any way to test configuration with ICO ?

Thanks again,

Jamal

iaki_vila
Active Contributor
0 Kudos

Hi,

It's normal to get that error because that test tool is only available with the Integration engine (abap stack) and with the ICO object you are only working on AEX  level (java stack), therefore no connection with integration engine is needed.

I dont know a tool that "only" test the configuration for the ICO object.

You can test your scenario with the next tools:

(Sender SOAP)

WsNavigator (http://hostname:port/wsnavigator😞

Check Raj's blog http://scn.sap.com/people/rajasekhar.reddy14/blog/2011/03/03/testing-sender-web-service-interfaces-s...

External tool as SOAPui

From RWB in test tab in component monitoring.

Another adapters like File/FTP or JDBC sender, when you active the channel you can view in the RWB communication channel monitoring if you have any exception.

Regards.

Former Member
0 Kudos

Thanks!

Is there a way in 7.3 to 'test' messages ?

As it was in 7.1 : RWB -> component Monitoring -> Integration Engine -> Test message tab

Thanks again for your help

BR,

Jamal

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Jamal,

It seems your Interface name is not defined properly in IR. Can you check your interface name, namespace again

Regards,
Shradha