HTTP 400

I have created an application which is supposed to connect to the identity provider app in weblogic, however, when connecting to a url for the app I get a http 400 error. How do I diagnose the error, I see nothing in the logs.

Hi,
I attempted to deploy the application using the war but this failed as shown below because it is already installed internally but not visible. The app is a weblogic app which is already up and running so I cannot process it. I get a http 400 error when I attempt to hit the apps url, the question is why, I cannot see why as the output from the app cannot be found
<09-Jan-2013 13:51:54 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>
<09-Jan-2013 13:51:54 o'clock GMT> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
<09-Jan-2013 17:23:16 o'clock GMT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element "web-app" in the deployment descriptor C:\Oracle\Middlew
are\user_projects\domains\base_domain\servers\AdminServer\tmp\.appmergegen_1357752196435_saml2.war/WEB-INF/web.xml. A version attribute is required, but this version of t
he WebLogic Server will assume that the latest version is used. Future versions of WebLogic Server will reject descriptors that do not specify the Java EE version. To eli
minate this warning, add an appropriate "version=" to element "web-app" in the deployment descriptor.>
<09-Jan-2013 17:23:49 o'clock GMT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element "web-app" in the deployment descriptor C:\Oracle\Middlew
are\user_projects\domains\base_domain\servers\AdminServer\tmp\.internal\saml2.war/WEB-INF/web.xml. A version attribute is required, but this version of the WebLogic Serve
r will assume that the latest version is used. Future versions of WebLogic Server will reject descriptors that do not specify the Java EE version. To eliminate this warni
ng, add an appropriate "version=" to element "web-app" in the deployment descriptor.>
<09-Jan-2013 17:23:50 o'clock GMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID "1357752229493" for task "0". Error is
: "weblogic.application.ModuleException: Context path '/saml2' is already in use by the module: saml2.war application: saml2"
weblogic.application.ModuleException: Context path '/saml2' is already in use by the module: saml2.war application: saml2
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:732)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
Truncated. see log file for complete stacktrace
Caused By: weblogic.application.ModuleException: Context path '/saml2' is already in use by the module: saml2.war application: saml2
at weblogic.servlet.internal.WebAppModule.validateContextPath(WebAppModule.java:1392)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:1238)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:723)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
Truncated. see log file for complete stacktrace
>
<09-Jan-2013 17:23:50 o'clock GMT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application "saml2-1".>
<09-Jan-2013 17:23:50 o'clock GMT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Context path '/saml2' is already in use by the module: saml2.war application: saml2
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:732)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
Truncated. see log file for complete stacktrace
Caused By: weblogic.application.ModuleException: Context path '/saml2' is already in use by the module: saml2.war application: saml2
at weblogic.servlet.internal.WebAppModule.validateContextPath(WebAppModule.java:1392)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:1238)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:723)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
Truncated. see log file for complete stacktrace
>
<09-Jan-2013 17:23:50 o'clock GMT> <Error> <Console> <BEA-240003> <Administration Console encountered the following error: weblogic.application.ModuleException: Context p
ath '/saml2' is already in use by the module: saml2.war application: saml2
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:732)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:167)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
at weblogic.application.internal.flow.ModuleStateDriver.prepare(ModuleStateDriver.java:38)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:139)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:55)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:706)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:237)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:48)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:96)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:229)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: weblogic.application.ModuleException: Context path '/saml2' is already in use by the module: saml2.war application: saml2
at weblogic.servlet.internal.WebAppModule.validateContextPath(WebAppModule.java:1392)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:1238)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:723)
>
<09-Jan-2013 17:23:50 o'clock GMT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_p
ageLabel=WebAppApplicationOverviewPage&WebAppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3Dsaml2-1%2CType%3DAppDeploy
ment%22%29.>

Similar Messages

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request

Hi,
We are doing File to WCF Scenario( SOAP ). I am trying to post the Data to WCf usingf SOAP Reciver Adapter.
Getting the Following error.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
Thanks in advance

>>> Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
Answer: Use the third party wsdl in SOAP UI or any soap client tool and send the request and see the response. The problem here is the message structure mismatch between your request to the webservice and webservice expecting...
Possible 2 reasons:
1) You are not creating the target message based on the wsdl structure or not configured soap receiver properly.
or
2 ) Your wsdl is not latest or updated one or some changes have happened in the third party webservice hosting side.

Message succesfully processed but still http 400 response at sender side

Hi,
I have the following scenario 3rd-party-application -> http -> PI 7.11 -> proxy -> ECC 6.0
If i send a message from the 3rd-party-application it is sent asynchronous to PI.
In PI i see it is succesfully processed.
In ECC i see it is also succesfully processed.
BUT in the sender system 3rd-party-application i still receive an http 400 message:
"Execution failure of HTTP POST: HTTP/1.1 400 Bad Request"
I do not expect this error message if the message itself is succesfully processed.
Anyone knows what can be happening here?
thx
Robert

Hi Chi,
I dont think your explanation can be correct.
We are on Development still, only sending few messages, and those messages are very small too.
However i found something else:
The error message from the 3rd party seems to indicate that they use http 1.1 protocol where as PI uses http 1.0 transport protocol.
I'm checking it with them now.
Still open for further ideas.
Kr
Robert

Error handling HTTP 400 in WCF-WebHttp adapter BizTalk 2013

Hi!
Does anyone knows how to catch HTTP errors when using WCF-WebHttp REST adapter in BizTalk 2013? I've looked into the article BizTalk
Server: REST Services Error Handling, but that is for BizTalk 2010 using the WCF-Custom adapter.
What I want is to catch the exception in an orchestration, and do some actions dependent on which HTTP error it is, i.e. HTTP 400.
Idar H.

Hi Idar,
Welcome to BizTalk forum.
From your description above, I don't have exact same scenario like yours, this scenario exposes a BizTalk Orchestration as a RESTful webservice using WCF-WebHttp, perhaps it will be good reference for you. See:
http://blog.tallan.com/2014/09/29/wcf-webhttp-and-custom-json-error-messages/
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

HTTP 400 Bad Request

Hello All,
I'm up against a show stopper. I have a simple region (lets call it the "Quote Region") of type SQL Query that returns rows from a table which I will need tp update. Occasionally the query will return a large number of rows, depending on the size of the customer's quote. My problem is when the quote is large (somewhere around 200 rows) and I perform an update I get HTTP 400 Bad Request "the webpage cannot be found", the URL says something about 7779/pls/apex/wwv_flow.accept.
The update is simple, it takes values that a user enters in another region and does a mass update to the lines in the Quote Region. The lines in the Quote region that are updated are determined by the user selecting them in a shuttle with the shuttle returning the line_id. For small quotes and even quotes with up to 195 lines everything works fine but I need this to work for large quotes! Does anyone know what's going on here???
I'm on version 3.1.2.00.02
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
I don't think it's my code, but here is the mass update anonymous block for review...
DECLARE
l_selected APEX_APPLICATION_GLOBAL.VC_ARR2;
x PLS_INTEGER := 1;
c_loopcount NUMBER := 0;
c_labelcount NUMBER := 0;
l_records VARCHAR2(32000);
l_line_id NUMBER;
BEGIN
-- Check that the shuttle has values
If :P3_APPLY_TO_LINES = 'NA' Then
RAISE_APPLICATION_ERROR( -20110, 'At least one line is required.' );
End If;
-- Convert the colon separated string of values in the shuttle into
-- a PL/SQL array
l_selected := APEX_UTIL.STRING_TO_TABLE(:P3_APPLY_TO_LINES);
FOR i IN 1.. NVL(l_selected.count,0) LOOP
l_line_id := l_selected (i);
c_loopcount := c_loopcount +1;
-- loop through each of the label values that have been entered by the user
FOR i IN 1 .. apex_application.g_f11.COUNT LOOP
c_labelcount := c_labelcount +1;
-- Update the transaction table with the provided value
UPDATE forx_label_transactions
SET value = apex_application.g_f01 (i) -- the user supplied value
,last_update_date = sysdate
,last_updated_by = :P3_LAST_UPDATED_BY
,last_update_login = :P3_LAST_UPDATE_LOGIN
WHERE label_id = apex_application.g_f11 (i) -- the hidden label id that is the foreign key
AND source_transaction_id = l_line_id; -- the line id of the quote line
--AND source_transaction_id = 1074016;
END LOOP;
l_records := l_records||l_selected (i);
END LOOP;
:p3_labelcount := c_labelcount;
:p3_loopcount := c_loopcount;
:p3_selected := (l_records);
END;
Edited by: blue4speed on Oct 7, 2010 8:54 PM
Edited by: blue4speed on Oct 7, 2010 9:04 PM

When submitting a page there is some limit about the page size (I think 32K) after that it throws HTTP 400. We were also facing the same problem in our large tabular form. You can use Pagination to limit the rows displayed in a page to avoid this error.
But when using pagination you will face another issue. Let's say you have 100 rows and pagination is displaying only 10 rows. If you update some rows and press navigation button (Next/Previous) the changes you have made are lost and not saved. I also have a workaround for this if you are interested please let me know. I will post you if you need it.

HTTP 400 Bad Request when accessing Oracle XE/Apex from the Internet

I have Oracle Express Edition upgraded to Apex 3.2. I can access everything (SQL prompt, Apex HTTP) from my local machine. I have configured the server for remote access on a non-default (not 8080) port.
I have executed: exec dbms_xdb.setListenerLocalAccess(false);
I can access the server using:
http://coyote:9977/apex (brings me to Application Express Administration Services login screen)
(where "coyote" is the local machine name of my Windows Vista box, where the Oracle/Apex server is installed.)
But when I try:
http://internet_server_name:9977/apex
(where "internet_server_name" is the internet DNS name visible of my machine visible from the internet.)
I get "HTTP 400 Bad Request"
I know the request is hitting the Oracle Listener (getting through firewalls, cable modem router, etc) since the http attempt causes the entry:
20-MAR-2009 20:36:53 * http * (ADDRESS=(PROTOCOL=tcp)(HOST=68.189.244.22)(PORT=52540)) * handoff * http * 0
to be made in the C:\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
An attempt using the local (Windows) machine name makes a similar entry in the listener log:
20-MAR-2009 20:47:35 * http * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.7)(PORT=52811)) * handoff * http * 0
This seems like a security issue of some kind (is the server dropping a request from "outside" the local domain?)
I'm new to Oracle so I am not familiar with how to debug this sort of connectivity issue. In case it helps:
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
Start Date 20-MAR-2009 19:27:00
Uptime 0 days 1 hr. 30 min. 59 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File C:\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
Listener Log File C:\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=coyote)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=coyote)(PORT=9977))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "XE_XPT" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
The command completed successfully
Any help appreciated,
john

Hans Forbrich wrote:
CoyoteTech wrote:
I have tried running with the firewall (F-Secure) completely disabled, but it made no difference. I do see the request hit the listener, and the handoff appears to be successful, but it goes silent from there. I also have a cable modem router that has the port forwarding set, but maybe there are other handoff ports besides the initial one (e.g. 8080) that need to be forwarded?Please also check the Windows firewall is off as well. Yes, Windows Firewall is disabled as well. See my previous post to Tyler - I'm pretty sure the reqwuest makes it through the firewall/router layer, since it causes an entry in Listener.log
Is your problem through the router only? In other words, if you try from a second machine that is on the same side as your XE, are you working OK? (My home ISP blocks a bunch of ports. Including SMTP, FTP, Telnet. And 8080 since that is a traditional default for many Java 'servers'.)
Yes, it appears to be related to a non-local IP address. I'm sure it makes it through the router - I also have several other ports that make it through (e.g. port 80).
I have poked around the DBMS_EPG docs, and ran a few of the commands there (list DADS etc). DBMS_EPG was first 'released' to us in 10gR2. As far as I'm concerned, XE is the public 'beta' or 'release candidate'. (This is supported by Oracle's docs that state that Apex using DBMS_EPG is first supported using 10.2.0.3 or 11g.) There are known bugs and there is no way to patch XE to fix them. However, I do not know whether you are hitting those bugs.
http://www.astral-consultancy.co.uk/cgi-bin/hunbug/doco.cgi?11410 provides some good notes.
Interesting. I will check out these docs later today.
>>
What happens when the listener hands off to a registered handler?
http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/concepts.htm#i1049597 gives a good description.
Thanks.
How do I pick up the [log] trail from there?I'm thniking that the listener's log is still the primary way to go. You may need to increase the log or trace level. I have not investigated how to gen or access logs inside EPG.I tried Tyler's trace but did not seem to add additional info to the Listener.log.

HTTP 400 Bad Request Error

Application Express 3.1.1.00.09
We have some users who are experiencing what appears to be a browser problem in one of our APEX applications.
When clicking on any button that does an insert or update to the database some users get an HTTP-400 Bad Request error message. The database does not get updated and anything they click on after that shows that message. In most cases we have been able to restore the user’s browser to the default settings and the issue is resolved. However, we were not able to isolate which browser setting is causing the issue. We have seen the issue in IE 6, IE 7 and IE 8.
Here’s the error we see in the Apache server error log (minus the date time stamp and IP addresses):
mod_plsql: /pls/ax_tastest/wwv_flow.accept HTTP-400 Invalid name
Does anyone else have a solution for this? Know what's causing it?

HTTP 400 Bad Request Error from APEX 3.1.1.00.09.
We were able to determine that only PCs which had the Google toolbar installed were getting the HTTP 400 Bad Request Error from a particular page in one of our applications. Further testing revealed that turning off the ‘auto-fill’ feature of the Google toolbar would prevent the error from occurring and the application would behave normally. We were able to identify a specific item on the page that was the root cause. The item was using the type “Text area with HTML Editor” which has been deprecated. We changed the page item type to “HTML editor standard” and this has resolved the issue with or without the Google Toolbar and auto-fill feature enabled.
Summary:
•     Browser setting: Google toolbar enabled with auto-fill enabled.
Apex page item of type: ‘Text area with HTML Editor’.
When a user clicks on a button in the page, that executes a page process, it results in HTTP 400 error.
•     Browser setting: Google toolbar enabled with auto-fill disabled.
Apex page item of type: ‘Text area with HTML Editor’.
When a user clicks on a button in the page, everything goes through correctly and there is no error.
•     Browser setting: Google toolbar enabled with auto-fill disabled or enabled.
Apex page item of type: ‘HTML Editor Standard’.
When a user clicks on a button in the page, everything goes through correctly and there is no error.

Error: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request

Hi Gurus,
i am hardly fighting with this error in Communication Channel Monitoring:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
This is my scenario.
I do a File to SOAP Scenario. in SXI_MONITOR everything is fine.
My CommChan is a SOAP Receiver
HTTP
SOAP 1.1
Central Adapter Engine
Target URL is https --> i check url for correctness
Configure User Authentication is checked and username and pw are given and are correct.
Configure Certificate Authentication is checked are working
Configure Proxy is checked and Host and port are povided.
SOAP Action is provided
In Tab Module
if have this Processing Sequence
1     localejbs/AF_Modules/MessageTransformBean     Local Enterprise Bean     transform
2     sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean     Local Enterprise Bean     1
and this Module configuration (and only this)
transform     Transform.ContentType     text/xml;charset=utf-8
(according to /people/sobhithalaxmi.kata/blog/2009/07/21/cost-free-edi-integration-using-message-transformation-bean)
As far as i understand that my http header should have Content-Type: text/xml;charset=utf-8 now. I don't understand why Communication Channel Monitoring shows an error according to content TEXT/HTML.
Can anyone help me with that?
Is it possible that Transform.ContentType does not work for SOAP Receiver Adapter?
is there any chance to view the HTTP-Header of the outgoing SOAP Request (with PI Transaction / Java Enironment) to convince myself that the HTTP Header is text/xml?
Thank you in advance and Best Regards
Udo

Hi Thanks for your fast replies.
The Provider of the Endpoint tells me that he needs text/xml as content-type. When I sent a message to the given Endpoint via SOAP UI I can see in the HTTP LOG of SOAP UI that the Endpoint is also sending text/xml back.
Below you find the Details log out of the CommChan Monitoring.
2011-04-29 11:37:45 Information The message status was set to TBDL.
2011-04-29 11:37:45 Information Retrying to deliver message to the application. Retry: 3
2011-04-29 11:37:45 Information The message was successfully retrieved from the receive queue.
2011-04-29 11:37:45 Information The message status was set to DLNG.
2011-04-29 11:37:45 Information Delivering to channel: getxxxxx_In <---- name of my SOAP Receiver CommChan
2011-04-29 11:37:45 Information Transform: using Transform.Class: $identity
2011-04-29 11:37:45 Information Transform: transforming the payload ...
2011-04-29 11:37:45 Information Transform: successfully transformed
2011-04-29 11:37:45 Information SOAP: request message entering the adapter with user J2EE_GUEST
2011-04-29 11:37:46 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
2011-04-29 11:37:46 Information SOAP: sending a delivery error ack ...
2011-04-29 11:37:46 Information SOAP: sent a delivery error ack
2011-04-29 11:37:46 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
2011-04-29 11:37:46 Error Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
2011-04-29 11:37:46 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request.
2011-04-29 11:37:46 Error The message status was set to NDLV.
What i am missing is a hint on the Message Transform Bean and a on a successfull sending process.
What i also tried already:
i also activated the checkbox "Do not use SOAP Envelop" in CommChan Configuration. The Result you see below (the last log entry is on first line - so read from bottom to top)
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
error in response
call completed
request entering
Message processing started
As you can see there is a "call completed" and "error in response" log entry. This is missing in in the first Log. So i guess the error is still in the sending process.
Installing additional Software on the PI and use them to find out what the HTTP Request is is not possible as system access is very strict and limited :/

APEX 3.1.1.00.09 – HTTP-400 Bad Request

We have some users who are experiencing what appears to be a browser problem in one of our APEX applications.
When clicking on any button that does an insert or update to the database some users get an HTTP-400 Bad Request error message. The database does not get updated and anything they click on after that shows that message. When this happens we have been able to restore the user’s browser to the default settings and the issue is resolved. However, we were not able to isolate which browser setting is causing the issue.
We have seen the issue in IE 6, IE 7 and IE 8. IE 6 must be upgraded and then reset, for 7 and 8 just a reset to default fixes the problem.
Here’s the error we see in the Apache server error log:
mod_plsql: /pls/ax_tastest/wwv_flow.accept HTTP-400 Invalid name
We’d like to determine which of the many browser settings could be causing this.

We got this error when upgrading from Apex 3.1 to 3.2 for our applications that use SSO authentication. This was our resolution (thanks to Scott):
Create schema apex_sso
Install the sso sdk into apex_sso schema (run the loadsdk script)
Connect as SYS from the apex core directory and run:
alter session set current_schema=apex_sso
grant execute on wwsec_sso_enabler_private to apex_030200
grant select on wwsec_enabler_config_info$ to apex_030200
alter session set current_schema=apex_030200
create synonym wwsec_enabler_config_info$ for apex_sso.wwsec_enabler_config_info$
create synonym wwsec_sso_enabler_private for apex_sso.wwsec_sso_enabler_private
drop public synonym wwv_flow_custom_auth_sso
@custom_auth_sso_902.sql
@custom_auth_sso_902.plb
create public synonym wwv_flow_custom_auth_sso for apex_030200.wwv_flow_custom_auth_sso
grant execute on wwv_flow_custom_auth_sso to public
copy rows from wwsec_enabler_config_info$ in flows_030100 table to the same table in apex_sso

Invalid request in SOAP Scenario - "HTTP 400 Bad Request"

Hi,
By sending request to a Webservice thorugh XI ,I am getting an error as "HTTP 400 Bad Request" in MONI and the response payload looks like this
"Request Error (invalid_request)
Your request could not be processed. Request could not be handled
This could be caused by a misconfiguration, or possibly a malformed request.
For assistance, contact your network support team."
I copy pasted the request payload in SOAP UI, there its working fine.I don't know where it goes wrong.
Please help me in that...
Thanks & Regards,
Yuga

Hi Yugapreetha,
Error: HTTP 400- Bad Request- ICM_HTTP_CONNECTION_FAILED
Description: The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
Possible Tips: May be because of huge message flow. Related SAP Notes-824554, 906435, 783515, 910649, 706563 If it is because of Queue problems have a look into SMQ2 .
And also here are a list of possible reasons for your problem with solutions.
It could be that it cannot find your file adapter.
1. Have you specified your hostname or IP address? Often the server cannot resolve the ip address for the hostname of your PC.
2. Is the path and port in the directory the same as the path and port of your file adapter?
3. Try question 14 (integration engine section)
/people/mark.finnern/blog/2006/01/12/finally-best-of-sdn-2005
4. also question 11 (in the same section)
5. if the avove will not fix it open XI config guide and
have a look at section
"Connecting Business Systems with an Integration Engine to the Central Integration Server"
6. Your error code is 400, so check this link,
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
For http 400 - its a bad request.
'The request could not be understood by the server due to malformed syntax.'
If you have the XI trouble shooting guide see from page 54,and also try:
1.Check that the port really is the ICM HTTP Port (transaction
SMICM) and not the J2EE port
2.If the port is wrong, change the pipeline URL in the SLD in
the business system of the Integration Server
3.Restart the J2EE Engine to reset the SLD buffer of the
Adapter Engine
Source- "XI troubleshooting guide"
Check out this SAP Note- 824554
Also this links
ICM_HTTP_CONNECTION_FAILED
Cache Refresh~
https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Reprocessing failed XI messages:
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Vinod.

Mod_plsql: /pls/orasso/ORASSO.wwsso_app_admin.fapp_process_login HTTP-400

Hi,
i write role in httpd.conf, to redirect to an external application, as this:
ProxyPass /pippo/ http://<myhost>:7777/pls/orasso/ORASSO.wwsso_app_admin.fapp_process_login?p_app_id=DF435C2A789ACE9C183480A1A6A982CD
ProxyPassReverse /pippo/ http://<myhost>:7777/pls/orasso/ORASSO.wwsso_app_admin.fapp_process_login?p_app_id=DF435C2A789ACE9C183480A1A6A982CD
bun when i try to access at <myhost>/pippo/ i receive the follow http error:
mod_plsql: /pls/orasso/ORASSO.wwsso_app_admin.fapp_process_login
HTTP-400 Name "ORASSO.wwsso_app_admin.fapp_process_login?p_app_id=DF435C2A789ACE9C183480A1A6A982CD" is longer than 30 chars
Is this a problem of mod_plsql or an Apache (Proxypass)?
Are somebody resolve it?
Thanks a lot to all!!!
Stefano

Yes Frank, I'm using DAS.
I found the problem, There was a previous SSO server installation and It was causing a conflict.
Now I have fixed the error running SSOREG script, the problem now is when accessing with a valid user the Apache.exe dies. The OID seems to be working fine since any wrong user is rejected, but when valid user the apache dies.
I'm looking for information about this error.
Any Idea?

Mod_plsql: /pls/apex/wwv_flow.accept HTTP-400 Too many arguments passed in.

Hi All ,
I want one solution i have a report which fectches the ppt that r stored in db,If i search more results it errors out so i have reduced the results and it was working fine.Now i see it is giving the same error(as below) althorugh it was working fine by reducing results in query.Can anybody please help me in this.
the error is
Bad Request
Your browser sent a request that this server could not understand.
mod_plsql: /pls/apex/wwv_flow.accept HTTP-400 Too many arguments passed in. Got 3250 parameters. Upper limit is 2000
Oracle-Application-Server-10g/10.1.3.1.0 Oracle-HTTP-Server Server at insightapps.oraclecorp.com Port 80

Section 1.10 of the Oracle HTTP Server mod_plsql User's Guide states the following
The total number of name value pairs that can be passed to a PL/SQL procedure is 2000.
mod_plsql limits the total number of parameters that can be passed to a single procedure to 2000.
mod_plsql limits the size of a single parameter that can be passed to a procedure to 32000 bytes.
It would be helpful to know how each of these apply in the APEX context
Varad

ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad request

Hi Folks ,
Error : "com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad request"
Scenario : Webservice --> XI (ccBPM) -->SAP (By verfying the response from SAP and if the data holds any error it will sends mail to SAP & webservice Admin thru mail Adapter)
1. Webservice will send the update Message to ccBPM asynchronously via XML Gateway
2. ccBPM will call RFC on SAP R/3 synchronously.
3. If R/3 response contains an application error XI will send the error message to SAP and Webservice administrators using Mail Adapter
As per our analyzation error might be if the target message is not creating based on the wsdl structure or if soap receiver not configured properly.
Could you please let me know the actual root cause and suggest me the solution ..
Thanks in Advance..
Regards,
Sekhar

Hello,
This error is for SAP PI,
Please post it in the under PI in NetWeaver Forum, for quick replies.
Regards,
Abhishek

Set Rendered on a 'Add' button to False has caused HTTP 400 error

Hi,
I am trying to personalise in Manager SS a custom version of seeded 'Documents of Record' function HR_DOR_SS to make the Add Record button non-display on the Documents of Record table. I changed Rendered to False, got the 'Setting this item to false may hide this item and its children' message but went ahead and did it anyway.
Outcome is that I can see the records in the table but can no longer view, update or delete existing records. I get a http 400 bad request page. I changed the 'Add' button back to Rendered True, but problem persists. Get the error also when I try to create a new record using the now re-instated button. Imported the personalization from another environment where it's working fine, bounced apache, clear cache etc and still problem persists.
Also if no record exists for employee, Add button works fine and I can create a record but from that point on cannot do anything with it.
Any help v much appreciated.
Thx

Yes, I've seen similar links/posts about how to activate buttons in the header of a table, but those do it by adding listeners to the renderer. My buttons would be directly in the CellRendererPane that is the container for the table header. I would have thought that by putting the button directly in the Cell RendererPane that it would have nothing to do with the rest of the table header. CellRendererPane extends Container. Is it not possible to put a JButton in a Container? JFrame extends indirectly from Container and you can add buttons to that.
Edited by: Bob.B on Oct 28, 2009 10:57 PM

HTTP-400 Too many arguments passed error

I am getting the following error when using a multiselect list item to select/update data in the tabular form.
Bad Request
Your browser sent a request that this server could not understand.
mod_plsql: /pls/otn/wwv_flow.accept HTTP-400 Too many arguments passed in. Got 2346 parameters. Upper limit is 2000
Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server Server at apex.oracle.com Port 80
I have built this prototype application on the Oracle’s hosted apex.oracle.com site.
The application page has three sections. Section 1 is an HTML region with the multiselect list. Section 2 is an HTML region with 20 text items. Section 3 has the tabular form with 25 columns that are used to update the data. The tabular form pagination values “Number of Row” and “Maximum Row Count” are set to 500.
Up until now, the multiselect list in the Section 1 was just a simple select list and I never had any issues. I guess the number of arguments passed was low. Per our customer requirement, I had to change the simple select list to a multiselect list. Now, If I select multiple values in the select list, I get the above mentioned error. But, it does not seem to happen all the time. For example, the first time I select 3 values in the multiselect list, the page renders fine, and I am able to enter/save data in the tabular form. Then, I select two other values in the multiselect list, I would get the error.
I am getting this error on the Oracle’s hosted apex.oracle.com site where my prototype application exists. And, according to the error oracle is using 10g/10.1.2.3.0. Is there any way to circumvent this issue so I can demo my application to the customer using the multiselect list?
I found several threads on this forum regarding the same error and it seems that there was a bug in the older versions of Oracle Application server. Also, there were discussions about setting the PlsqlMaxParameters.
Our dev/test/prod environment would be set up using the Oracle Application Server-10g/10.1.3. The question is would we need to add a line to set the PlsqlMaxParameters value in the plsql.conf file? In addition, what is the maximum value that it can be set to?
Please forgive me for the longwinded description and the question - only way I could describe the situation.
Thanks,
DP

Varad and Sc0tt,
Thank you both for your responses.
Varad – Yes, I can/will reduce the amount of data so it does not cause the tabular form to go over the 2000 field limit. If that is not possible, I will at least make the users aware of this issue. Since the same data is used for the other pages in the application, the users might want to keep all the data.
Sc0tt – thanks for providing the information for your environment and settings. To plan for the future, we will have to set the value to something high also, around 8-10K range, and adjust later if we have to.
Thank you both, I will mark both of your answers as helpful and the question as being answered.
DP
(Have either of you used the jquery datepicker solution? If yes, can you please take a look at my thread: Thread: Jquery Datepicker calendar problem with page scrolling
Jquery Datepicker calendar problem with page scrolling

Mod_plsql: /pls/apex/f HTTP-400 Missing '=' in query string or post form

This is the message when I click the logout button. It destroys the session though. It should redirect to login page after clicking logout button.
We are on Apex 4.1
Bad Request
Your browser sent a request that this server could not understand.
mod_plsql: /pls/apex/f HTTP-400 Missing '=' in query string or post form
Oracle-Application-Server-10g/10.1.2.2.0 Oracle-HTTP-Server Server at xxxx.xxxxx.edu Port 443
Edited by: 965704 on Oct 30, 2012 11:42 AM

It has been fixed but the new problem is: After signout, if I move back to previous page and click some link using <- sign then I suppose to get the login page, but i am getting
ORA-44004: invalid qualified SQL name error message.
The source for my login page is
wwv_flow_custom_auth_std.login(
P_UNAME => :P101_USERNAME,
P_PASSWORD => :P101_PASSWORD,
P_SESSION_ID => v('APP_SESSION'),
P_FLOW_PAGE => :APP_ID||':1'
);

HTTP 400

Similar Messages

Maybe you are looking for