Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 653
  • Last Modified:

Jboss web 404 error

Hi guys I have a Saba install which began having issues and now presents a 404 error after reboot. Can any one help me with the logs to see if you can spot an error.?

I have no knowledge of this Jboss/tomcat/apache so any clue or something to try would be appreciated!

Boot.log;

15:08:32,048 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
15:08:32,244 INFO  [xnio] XNIO Version 2.1.0.CR2
15:08:32,250 INFO  [nio] XNIO NIO Implementation Version 2.1.0.CR2
15:08:32,578 INFO  [remoting] JBoss Remoting version 3.1.0.Beta2
15:08:32,655 INFO  [TomcatDeployment] deploy, ctxPath=/
15:08:32,721 INFO  [TomcatDeployment] deploy, ctxPath=/aicc_bridge
15:08:32,744 INFO  [TomcatDeployment] deploy, ctxPath=/gatekeeper
15:08:32,760 INFO  [TomcatDeployment] deploy, ctxPath=/scorm_launch
15:08:32,821 INFO  [TomcatDeployment] deploy, ctxPath=/sababirt200
15:08:32,840 INFO  [TomcatDeployment] deploy, ctxPath=/sabareportxi
15:08:32,979 ERROR [STDERR] log4j:WARN No appenders could be found for logger (com.sun.faces.config.ConfigureListener).
15:08:32,980 ERROR [STDERR] log4j:WARN Please initialize the log4j system properly.
cheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

15:08:31,236 INFO  [StdSchedulerFactory] Quartz scheduler 'JBossQuartzScheduler' initialized from an externally opened InputStream.
15:08:31,237 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.8.3
15:08:31,237 INFO  [QuartzScheduler] Scheduler JBossQuartzScheduler_$_NON_CLUSTERED started.
15:08:31,329 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DemoSite-Report' to JNDI name 'java:DemoSite-Report'
15:08:31,366 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DemoSite' to JNDI name 'java:DemoSite'
15:08:31,403 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=SabaSite-Report' to JNDI name 'java:SabaSite-Report'
15:08:31,440 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=SabaSite' to JNDI name 'java:SabaSite'
15:08:31,851 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
15:08:32,048 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
15:08:32,244 INFO  [xnio] XNIO Version 2.1.0.CR2
15:08:32,250 INFO  [nio] XNIO NIO Implementation Version 2.1.0.CR2
15:08:32,578 INFO  [remoting] JBoss Remoting version 3.1.0.Beta2
15:08:32,655 INFO  [TomcatDeployment] deploy, ctxPath=/
15:08:32,721 INFO  [TomcatDeployment] deploy, ctxPath=/aicc_bridge
15:08:32,744 INFO  [TomcatDeployment] deploy, ctxPath=/gatekeeper
15:08:32,760 INFO  [TomcatDeployment] deploy, ctxPath=/scorm_launch
15:08:32,821 INFO  [TomcatDeployment] deploy, ctxPath=/sababirt200
15:08:32,840 INFO  [TomcatDeployment] deploy, ctxPath=/sabareportxi
15:08:32,979 ERROR [STDERR] log4j:WARN No appenders could be found for logger (com.sun.faces.config.ConfigureListener).
15:08:32,980 ERROR [STDERR] log4j:WARN Please initialize the log4j system properly.
15:08:33,902 INFO  [service] Removing bootstrap log handfdsf

# tail -f server.log
        at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]
        at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]
        at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]
        at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]
        at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]
        at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
        at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
        at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]

2013-06-08 15:08:33,995 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] (Thread-2) JBossAS [6.0.0.Final "Neo"] Started in 24s:578ms
0
Gaz124
Asked:
Gaz124
  • 2
  • 2
1 Solution
 
dpearsonCommented:
This part:

tail -f server.log
        at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]
        at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]

is showing part of a large exception.

You should look at server.log and find the top of the exception and post that.  It may give some indication as to the root cause of the problem.
0
 
ValeriCommented:
you can issue this command
tail -300 server.log > /home/errorLog.txt
and to post errorLog.txt file here...
0
 
Gaz124Author Commented:
Thanks guys, in the end it was the error log which was full, truncated and all is now well.


Thanks for your suggestions.
0
 
dpearsonCommented:
Haha - that's a nice one, a full error log causing issues.
0
 
Gaz124Author Commented:
Solved on my own, full error log
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now