-
1. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
sasha77 Jun 6, 2013 7:43 AM (in response to sasha77)Addition to the earlier update, i am running the server on address 0.0.0.0 to permit a remote connect.
-
2. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
sasha77 Jun 7, 2013 5:23 AM (in response to sasha77)am i on a wrong forum, its been almost 12 hours but no response yet
-
3. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
erasmomarciano Jun 7, 2013 6:19 AM (in response to sasha77)Hi
How did you run JBoss?
-
4. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
sasha77 Jun 10, 2013 1:48 AM (in response to sasha77)With the run.sh startup script. and port 0.0.0.0
-
5. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
wdfink Jun 10, 2013 2:15 AM (in response to sasha77)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?
-
6. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
sasha77 Jun 10, 2013 4:32 AM (in response to wdfink)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
-
7. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
jaikiran Jun 10, 2013 5:05 AM (in response to sasha77)What exact URL gives you the 404 error?
-
8. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
sasha77 Jun 10, 2013 6:10 AM (in response to jaikiran)I mentioned, I am getting a Http 400 Bad Request error and not a 404.
http://<namedServerAddress>:8080/
-
9. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
erasmomarciano Jun 10, 2013 6:26 AM (in response to sasha77)May you post last ten rows the server.log
-
10. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
sasha77 Jun 10, 2013 7:53 AM (in response to 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>
-
11. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
wdfink Jun 10, 2013 11:32 AM (in response to sasha77)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?
-
12. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
sasha77 Jun 12, 2013 2:11 PM (in response to wdfink)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
-
13. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
trkant May 17, 2014 3:40 AM (in response to sasha77)Santosh,
Hope doing great.
I am running into a similar issue. Could you please let me know how did you resolved this ?
Thanks,
Ravi
-
14. Re: Accessing jboss admin console returns "Http 400 Bad Request" error
mmusaji May 20, 2014 11:42 AM (in response to trkant)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