Re: [JBoss-user] Embedd tomcat Mapping failure...

2002-02-15 Thread Dmitri Colebatch

Hi,

see  http://main.jboss.org/thread.jsp?forum=67&thread=7931

cheers
dim


- Original Message -
From: "Saimon Moore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 16, 2002 2:05 AM
Subject: [JBoss-user] Embedd tomcat Mapping failure...


> Hi,
>
> I've been trying out JBoss-2.4.4-Tomcat-4.0.1. JBoss is great.. ;)
>
> I started it up using the run_with_catalina.sh script. Everything seems to
> load up fine. i.e. no exception traces or anything. Seems quite normal
(I've
> included the log anyway
>
> But when I try to access http://127.0.0.1:8080 I get
>
> HTTP Status 500 - No Context configured to process this request
>
> and the following exception trace appears in the jboss terminal.
>
>
> If I individually startup Tomcat it loads up ok..but with the above
> script...I always get the following..
>
> Very strange.
>
> Hope someone can help me out on this one...
>
> Cheers
>
> Saimon
>
> Exception trace:
> ==
> [INFO,EmbeddedCatalinaServiceSX] StandardHost[localhost]: MAPPING
> configuration error for request URI
> [ERROR,EmbeddedCatalinaServiceSX] HttpProcessor[8080][4] process.invoke
> java.lang.NullPointerException
> at
>
org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDispatcherValve.
java:280)
> at
>
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:180)
> at
>
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
> at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170
)
> at
>
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
64)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
> at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
> at
>
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:163)
> at
>
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5
66)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
> at
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
> at
>
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
1011)
> at
>
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106
)
> at java.lang.Thread.run(Thread.java:484)
> 
>
> Startup Log:
> ===
> saimon@linux:~/JBoss-2.4.4_Tomcat-4.0.1/jboss/bin > sh
run_with_catalina.sh
> JBOSS_CLASSPATH=:/usr/java/jdk1.3/lib/tools.jar:run.jar:../lib/crimson.jar
> jboss.home = /home/saimon/JBoss-2.4.4_Tomcat-4.0.1/jboss
> Using JAAS LoginConfig:
> file:/home/saimon/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/catalina/auth.conf
> JBoss release: JBoss-2.4.4 CVSTag=JBoss_2_4_4
> JBoss version: 2.4.4.2001-12-29 02:04:40 PST
> Using configuration "catalina"
> [INFO,root] Started Log4jService,
>
config=file:/home/saimon/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/catalina/log4j.
properties
> [INFO,Info] Java version: 1.3.0,Sun Microsystems Inc.
> [INFO,Info] Java VM: Java HotSpot(TM) Server VM 1.3.0,Sun Microsystems
Inc.
> [INFO,Info] System: Linux 2.4.0-4GB,i386
> [INFO,Shutdown] Shutdown hook added
> [INFO,ServiceControl] Initializing 48 MBeans
> [INFO,WebService] Initializing
> [INFO,WebService] Initialized
> [INFO,NamingService] Initializing
> [INFO,NamingService] Initialized
> [INFO,JNDIView] Initializing
> [INFO,JNDIView] Initialized
> [INFO,TransactionManagerService] Initializing
> [INFO,TransactionManagerService] Initialized
> [INFO,ClientUserTransactionService] Initializing
> [INFO,ClientUserTransactionService] Initialized
> [INFO,JaasSecurityManagerService] Initializing
> [INFO,JaasSecurityManagerService] Initialized
> [INFO,JdbcProvider] Initializing
> [INFO,JdbcProvider] Loaded JDBC-driver:org.hsqldb.jdbcDriver
> [INFO,JdbcProvider] Initialized
> [INFO,HypersonicDatabase] Initializing
> [INFO,HypersonicDatabase] Initialized
> [INFO,DefaultDS] Initializing
> [INFO,DefaultDS] Initialized
> [INFO,ServerDataCollector] Initializing
> [INFO,ServerDataCollector] Initialized
> [INFO,ContainerFactory] Initializing
> [INFO,ContainerFactory] Initialized
> [INFO,EmbeddedCatalinaServiceSX] Initializing
> [INFO,EmbeddedCatalinaServiceSX] Initialized
> [INFO,JBossMQService] Initializing
> [INFO,JBossMQService] Initialized
> [INFO,StateManager] Initializing
> [INFO,StateManager] Initialized
> [INFO,PersistenceManager] Initializing
> [INFO,PersistenceManager] Initialized
> [INFO,JVMServerILService] Initializing
> [INFO,JVMServerILService] Initialized
> [INFO,RMIServerILService] Initializing
> [INFO,RMIServerILService] Initialized
> [INFO,OILServerILService] Initializing
> [INFO,OILServerILService] Initialized
> [INFO,UILServerILService] Initiali

Re: [JBoss-user] Embedd tomcat Mapping failure...

2002-02-15 Thread Saimon Moore

On Vie 15 Feb 2002 16:15, Michael Schulz wrote:

> > This has been discussed many times in the forums.

I'm sorry I didn't check the archives before...won't happen again..

> The default installation of JBoss 2.4.4/Tomcat 4.0.1 does not deploy any
> web app to the root context - so the mapping failure is not unexpected.  As
> the JBoss docs state, the correct URL to use is:
> http://127.0.0.1:8080/jboss. You could also deploy your own application in
> the root context to get rid of this error.
>
> Since this question comes up so frequently, I created an .ear file which
> deploys a web app to the root context.  I've attached it to this reply for
> your convenience.
>
> -Michael Schulz
>

Thanks a lot for your help...Much appreciated...

P.S. Could be an idea to update the Tomcat.html doc that comes with the 
binary dist to reflect this.

Thanks again...

Saimon

_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user