cancel
Showing results for 
Search instead for 
Did you mean: 

NW Log Error

sidnooradarsh
Contributor
0 Kudos

Hello,

We are on MII 12.1.7 build 47

I am getting below errors in NW logs (Default trace view) not sure what is it that causing these errors but I am afraid these errors might impact us sooner or later..

Any suggestions/recommendations will be of great help!!

com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://gpiptcxmdev01:50000/uddi/api/publish/> returned message <Unauthorized>.

[EXCEPTION]

com.sap.esi.esp.lib.mm.config.exceptions.SRTechnicalExceptioncom.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://gpiptcxmdev01:50000/uddi/api/publish/> returned message <Unauthorized>.

at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.saveClassificationSystem(SOACentralSRPublisherImpl.java:1296)

at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publishServiceDefinitions(PublishRulesHandler.java:484)

at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:448)

at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:385)

at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.run(SOATimeoutListenerImpl.java:222)

at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:126)

at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:95)

at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:71)

at com.sap.engine.frame.core.thread.Task.run(Task.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)

Caused by: com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishClassificationSystemsFault123: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://gpiptcxmdev01:50000/uddi/api/publish/> returned message <Unauthorized>.

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:494)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.deserializeException(JAXWSUtil.java:402)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.processFault(JAXWSUtil.java:372)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1115)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:779)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:746)

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167)

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120)

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)

at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)

at $Proxy477.publishClassificationSystems(Unknown Source)

at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystems(ServicesRegistryProxyFacade.java:333)

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

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

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

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

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:177)

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

Regards,

Adarsh

Accepted Solutions (0)

Answers (1)

Answers (1)

sidnooradarsh
Contributor
0 Kudos

Hello MII experts please throw some light on this issue....

agentry_src
Active Contributor
0 Kudos

Hi Adarsh,

What roles are assigned to the user that is triggering these error messages?

What version of the JRE is running on the machine accessing MII?

What process is being performed at the time of the error messages?

Regards,

Mike

sidnooradarsh
Contributor
0 Kudos

Hi Mike,

Thanks for your response.

What roles are assigned to the user that is triggering these error messages?

This is our new development server and we have migrated stuff from 11.5 to 12.1 and there are only 8 users on this system and all of them are super admins but of those I am the only one using the system currently and I am not sure it is being generated by any of our 8 users because the interesting point is this error generates on every 49th minute of hour (for eg, 10:49, 11:49, 12:49 and so on) and along with I see two more errors "SR Log error" occurring on same time.

These are the only three errors I see repeating every hour and no other errors.

What version of the JRE is running on the machine accessing MII?

On client machines we have JRE 1.5 update 22 and on server we have JRE 1.5 update 21

What process is being performed at the time of the error messages?

No background jobs are scheduled and even if I don't run any programs still I can see this error on every hour

Regards,

Adarsh

agentry_src
Active Contributor
0 Kudos

You may want to check the system jobs, but that is kind of odd type of error behavior.

Also look at NW to see there is anything there running on a regular basis.