My Oracle Support Banner

Oracle Traffic Director-Random HTTP/1.1 400 Bad Request when Connecting JD Edwards JDE /Weblogic throu' OTD (Doc ID 2253433.1)

Last updated on AUGUST 14, 2024

Applies to:

Oracle Traffic Director - Version 12.2.1.0.0 to 12.2.1.0.0 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

When attempting to access the JDE Application thru' OTD using weblogic as front-end, the following error occurs:

HTTP/1.1 400 Bad Request

  

2017-02-07T14:58:08+01:00] [otd_instance] [NOTIFICATION:1] [OTD-11009] [] [ecid: <ECID>] [rid: 0] [pid: 2922] for host <IP> trying to POST /jde/E1VirtualClient.mafService?e1.mode=view&e1.namespace=&RENDER_MAFLET=E1Menu&e1.state=maximized&e1.service=E1VirtualClient, service-http reports: response headers received from origin server(<HOSTNAME>:<PORT>) :[[
HTTP/1.1 400 Bad Request
connection: close
]]

is a Bad Request, since http status is 400.

You would need to look at the corresponding entries in web logic/ origin server access logs and server.log for above request, preferably with ECID.

i.e.,the complete request, response flow for ONE request (which fails with 400 Bad Request) starting from client request till the client gets the response back.
which shows the application flow in between the client and the back-end server.

Changes

When connected to the weblogicserver directly, bypassing OTD the problem never occurs.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.