This discussion is archived
7 Replies Latest reply: Jan 9, 2013 9:50 AM by Kalyan Pasupuleti-Oracle RSS

HTTP 400

983478 Newbie
Currently Being Moderated
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.
  • 1. Re: HTTP 400
    Fabian Pro
    Currently Being Moderated
    Hi Philip,

    1)Check Whether ur Deployment of Application was Successfull on Managed Server.
    2) Check the state of ur deployment on weblogic console whether its at Active state.(From Weblogic Console-->Deployments)
    3) Cross check the url which ur using to connect the application.
    From Weblogic Console-->Deployments--><Your Deployments>-->Testing
    Here you will get the url.
    4) Try the above url from your server itself..if your server is windows box,try it from browser and if its linux box,open putty,connect to the server,then elinks url.

    Try the above 4 things,and let us know the result

    Regards,
    Fabian
  • 2. Re: HTTP 400
    983478 Newbie
    Currently Being Moderated
    Hi Fabian, my app is running in tomcat, this is working correctlly, I can see the servlet and process it. However, when it runs and attempts to hit the identity provider in weblogic I get the Http 400 error. The identity provider is an extension to weblogic but I cannot see the app in the deployments. It's simply an option which is configured and enabled, any ideas?
  • 3. Re: HTTP 400
    Kalyan Pasupuleti-Oracle Expert
    Currently Being Moderated
    Hi,

    Check what was there in server log provide error stack from logs.

    Regards,
    Kal
  • 4. Re: HTTP 400
    983478 Newbie
    Currently Being Moderated
    Hi,

    Unfortunately there is nothing in the server logs I have placed the logs below, no restart is required when the identity provider is started, it does not have any output in the logs.

    <09-Jan-2013 13:51:37 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
    <09-Jan-2013 13:51:37 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
    <09-Jan-2013 13:51:37 o'clock GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\Ad
    minServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.>
    <09-Jan-2013 13:51:37 o'clock GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\user_projects\domains\base_domain\servers
    \AdminServer\logs\AdminServer.log00004. Log messages will continue to be logged in C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\AdminSe
    rver.log.>
    <09-Jan-2013 13:51:37 o'clock GMT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\
    logs\AdminServer.log is opened. All server side log events will be written to this file.>
    <09-Jan-2013 13:51:43 o'clock GMT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <09-Jan-2013 13:51:50 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY.>
    <09-Jan-2013 13:51:50 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
    <09-Jan-2013 13:51:50 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 13:51:50 o'clock GMT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\ba
    se_domain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.>
    <09-Jan-2013 13:51:50 o'clock GMT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\user_projects\domains\base_domain\servers
    \AdminServer\logs\base_domain.log00004. Log messages will continue to be logged in C:\Oracle\Middleware\user_projects\domains\base_domain\servers\AdminServer\logs\base_do
    main.log.>
    <09-Jan-2013 13:51:50 o'clock GMT> <Notice> <Log Management> <BEA-170027> <The server has successfully established a connection with the Domain level Diagnostic Service.>

    <09-Jan-2013 13:51:51 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN.>
    <09-Jan-2013 13:51:51 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING.>
    <09-Jan-2013 13:51:51 o'clock GMT> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks key
    store file C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\DemoIdentity.jks.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\Demo
    Trust.jks.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\JDK160~1\jre\lib\security\
    cacerts.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:6c91:f5ed:c522:3837:7001 for protocols iiop, t3, ld
    ap, snmp, http.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Warning> <Server> <BEA-002611> <The hostname "*******", maps to multiple IP addresses: 172.23.11.168, fe80:0:
    0:0:6c91:f5ed:c522:3837%11.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on 127.0.0.1:7002 for protocols iiops, t3s, ldaps, https.>

    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on fe80:0:0:0:6c91:f5ed:c522:3837:7002 for protocols iiops,
    t3s, ldaps, https.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 172.23.11.168:7001 for protocols iiop, t3, ldap, snmp, http.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 172.23.11.168:7002 for protocols iiops, t3s, ldaps, https.>

    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on 0:0:0:0:0:0:0:1:7002 for protocols iiops, t3s, ldaps, ht
    tps.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.
    >
    <09-Jan-2013 13:51:54 o'clock GMT> <Notice> <WebLogicServer> <BEA-000331> <Started the WebLogic Server Administration Server "AdminServer" for domain "base_domain" runnin
    g in development mode.>
    <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.>
  • 5. Re: HTTP 400
    Kalyan Pasupuleti-Oracle Expert
    Currently Being Moderated
    Ok,

    Can you get into deployment and check where this application state currently.


    If it is prepared select that app and start it make it active.

    if it new then make sure that target option is select correctly.


    let me know what is state of the deployment of your app.

    Regards,
    Kal
  • 6. Re: HTTP 400
    983478 Newbie
    Currently Being Moderated
    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.>
  • 7. Re: HTTP 400
    Kalyan Pasupuleti-Oracle Expert
    Currently Being Moderated
    Hi,

    It is pretty much clear that your deployment get into failed state.

    clear tmp folder where this app is deployed server and also change context name while deployment through console.

    and check state of the deployment.

    Regards,
    Kal

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points