I have a callable web service that is installed on several clusters. All clusters give the proper response when sending a POST to the url, except for one cluster which gives a 400 Bad Request.

Having some issues troubleshooting this with Avaya and thought I'd come here to see if there is any guidance you can give on where to look for an issue? There are no entries in the logs for the service on the cluster other than the standard init/destroy messages.


url

http://ip/services/TestService/ws/ucid

relevant code

@Path("ucid")

public class GetUCID implements IConsentListener

{

...

Hi Michael,

Are you addressing the request to a node IP address or the cluster IP? Regarding the logs for TestService, I assume you enabled debug logging for your service (ce dlogon TestService)? Another thing you might do is "ce logon" followed by "ce logw". This will show you the WebSphere debug log, which is more interesting than the asm.log file for incoming HTTP. Let us know what you find out.

Using the cluster IP to call service and I'm SSHed into the active node in that cluster. I looked at ce logw, but I don't see any output that appears related to my request.

[10/10/18 8:31:29:538 EDT] 00000138 FailoverMgrIm 3 FailoverMgrImpl extractListenerAttribute SESSION_EXPIRATION_TIMER_TYPE doesnt hold a listener

[10/10/18 8:31:29:538 EDT] 00000138 DRS_SASAttrMg > DRS_SASAttrMgr remove ENTRY Id = local.1538466872957_240288 Info = com.ibm.ws.sip.container.servlets.WASXSipApplicationSessionImpl@cbdc6e60 SESSION_EXPIRATION_TIMER_TYPE

[10/10/18 8:31:29:538 EDT] 00000138 StandAloneSAS > StandAloneSASAttrRepoMgr get ENTRY Id = local.1538466872957_240288 Info = com.ibm.ws.sip.container.servlets.WASXSipApplicationSessionImpl@cbdc6e60 SESSION_EXPIRATION_TIMER_TYPE

[10/10/18 8:31:29:538 EDT] 00000138 StandAloneSAS < StandAloneSASAttrRepoMgr get RETURN SESSION_REFRESH_TIMER

[10/10/18 8:31:29:538 EDT] 00000138 StandAloneSAS > StandAloneSASAttrRepoMgr remove ENTRY Id = local.1538466872957_240288 Info = com.ibm.ws.sip.container.servlets.WASXSipApplicationSessionImpl@cbdc6e60 SESSION_EXPIRATION_TIMER_TYPE

[10/10/18 8:31:29:538 EDT] 00000138 StandAloneSAS < StandAloneSASAttrRepoMgr remove RETURN SESSION_REFRESH_TIMER

Also looked at asm.log, and all I see is

[SipContainerPool : 0] pfa.hmf.ZrSipMonitorDM WARN - AUS instance is null

Hi Michael,
I assume you have load balancer enabled and the request was sent to clusterIP. In that case, the request may not always arrive on the active node. You may need to look on other nodes in the cluster as well.
Based on the previous messages, it could be a deployment issue if you didn't experience problem with the same service on other clusters. Can you verify:
(1) any logging with the 400 error in /var/log/Avaya/asset/nginx_error.log
(2) whether the TestService was successfully deployed. You can try to re-deploy it via SMGR
(3) you try to send the request to eth1 on a specific node and run "traceHTTP" tool to monitor the flow
(4) enable the logs as Joel mentioned in the previous message

Let us know what you find out.

Someone from Avaya did manage to get it fixed, their resolution is below, thanks!

I think I found the issue as this cluster has Engagement Designer installed it has some authentication enabled for service by default.

I changed it and it seems to be working for now https as well.