Accessing jboss admin console returns "Http 400 Bad Request" error

[sasha77]

Hi,

I have recently installed Jboss AS version 4.2.3.GA on a Linux platform.

the server has started successfully without any errors, but trying to access either the jmx console app or jboss /status page is returning a Http 400 Bad Request page.

i have looked in both server and boot log but have not found anything which might help debug this issue.

struggling with this issue since last two days but still not been able to make any headway.

can someone please advise what might be the pottential issue leading to this.

Thanks in advance.

2013-06-06 05:21:12,558 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 17s:593ms

regards

Sunny

[sasha77]

Addition to the earlier update, i am running the server on address 0.0.0.0 to permit a remote connect.

[sasha77]

am i on a wrong forum, its been almost 12 hours but no response yet

[erasmomarciano]

Hi

How did you run JBoss?

[sasha77]

With the run.sh startup script. and port 0.0.0.0

[wdfink]

Hello Santosh,

a word regarding

am i on a wrong forum, its been almost 12 hours but no response yet

the forum is mostly driven by volunteers, there is no guarantee that someone respond, especially not with a small response time. If you need such response times you need to use a Red Hat subscription where you have such guarantees.

Regarding your questions.

Could you provide a bit more informations, I.e. the complete start command, the environment, the server.log and how do you connect the server?

Is it possible to connect 'localhost:8080' in a browser at the same system?

[sasha77]

the forum is mostly driven by volunteers, there is no guarantee that someone respond, especially not with a small response time. If you need such response times you need to use a Red Hat subscription where you have such guarantees.

Hi Wolf, Appreciate your efforts on this.

This is the startup script 

nohup ./run.sh -b 0.0.0.0 &

I am able to access the jboss index page using wget on this machine.

the logs are not indicating any errors.

I am running jboss on the following Red Hat version.

Red Hat Enterprise Linux Server release 6.3 (Santiago)

regards

Santosh

[jaikiran]

What exact URL gives you the 404 error?

[sasha77]

I mentioned, I am getting a Http 400 Bad Request error and not a 404.

http://<namedServerAddress>:8080/

[erasmomarciano]

May  you post last ten rows the server.log

[sasha77]

2013-06-10 07:50:52,074 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] No FacesServlet found in deployment descriptor - bypassing configuration

2013-06-10 07:50:52,075 DEBUG [org.jboss.web.tomcat.filters.ReplyHeaderFilter] Adding header name: X-Powered-By='Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0'

2013-06-10 07:50:52,083 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Initialized: {WebApplication: /home/msoft/Jboss/jboss-4.2.3.GA/server/default/deploy/jmx-console.war/, URL: file:/home/msoft/Jboss/jboss-4.2.3.GA/server/default/deploy/jmx-console.war/, classLoader: java.net.FactoryURLClassLoader@2798797:41518999} jboss.web:j2eeType=WebModule,name=//localhost/jmx-console,J2EEApplication=none,J2EEServer=none

2013-06-10 07:50:52,083 DEBUG [org.jboss.web.WebModule] Started jboss.web.deployment:war=jmx-console.war,id=-2123004132

2013-06-10 07:50:52,083 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.web.deployment:war=jmx-console.war,id=-2123004132 dependent components: []

2013-06-10 07:50:52,100 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jmx-console.war

2013-06-10 07:50:52,100 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/home/msoft/Jboss/jboss-4.2.3.GA/server/default/deploy/jmx-console.war/

2013-06-10 07:50:52,100 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/home/msoft/Jboss/jboss-4.2.3.GA/server/default/deploy/jmx-console.war/ -> file:/home/msoft/Jboss/jboss-4.2.3.GA/server/default/deploy/jmx-console.war/WEB-INF/web.xml

2013-06-10 07:50:52,106 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified that enabled: true

2013-06-10 07:50:52,106 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Started jboss.deployment:type=DeploymentScanner,flavor=URL

2013-06-10 07:50:52,106 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.deployment:type=DeploymentScanner,flavor=URL dependent components: []

2013-06-10 07:50:52,174 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml

2013-06-10 07:50:52,174 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/home/msoft/Jboss/jboss-4.2.3.GA/server/default/conf/jboss-service.xml

2013-06-10 07:50:52,175 DEBUG [org.jboss.web.tomcat.service.JBossWeb] Saw org.jboss.system.server.started notification, starting connectors

2013-06-10 07:50:52,181 INFO  [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080

2013-06-10 07:50:52,196 INFO  [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009

2013-06-10 07:50:52,205 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 18s:571ms

2013-06-10 07:50:52,205 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - first pass <Mon, 10 Jun 2013 07:50:52>

[wdfink]

As wget succeeds I suppose there is some network stuff in between that avoid a correct connection.

Could you describe a bit more or your network environment?

Are you able to use a browser on a machine which is connected to the same network?

[sasha77]

Hmm. convincing the network guys that this is a firewall issue is tough. But still i wanted to rule out all the options before i see guidance from them.

thanks for your help, will revert with update once i have a solutions.

cheers

Santosh

[trkant]

Santosh,

Hope doing great.

I am running into a similar issue. Could you please let me know how did you resolved this ?

Thanks,

Ravi

[mmusaji]

Ravi, this issue is over a year old running a very old version of JBoss. Can you create a new post with your issue and version of JBoss you are running please.

Thanks

Mustafa