[
https://issues.apache.org/jira/browse/AXIS2-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574537#action_12574537
]
Davanum Srinivas commented on AXIS2-3377:
-----------------------------------------
Now it should print the stack trace too. (633109)
-- dims
> Exception message in ListenerManager.start() is empty
> -----------------------------------------------------
>
> Key: AXIS2-3377
> URL: https://issues.apache.org/jira/browse/AXIS2-3377
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Red Hat Enterprise Linux AS release 4 (Nahant)
> Kernel 2.6.9-5.ELsmp on an x86_64
> Reporter: Varun Vashisht
> Priority: Trivial
>
> Problem:
> The method start() of class ListenerManager logs e.getMessage() upon catching
> an Exception, but this message is an empty string.
> The bug lies in some other class, but I did not debug it further.
> Steps to reproduce:
> 1. Uncomment and modify the following configuration parameters for http
> transport receiver in $AXIS2_HOME/conf/axis2.xml:
> <parameter name="requestCoreThreadPoolSize">151</parameter>
> <parameter name="requestMaxThreadPoolSize">150</parameter>
> 2. Modify the $AXIS2_HOME/log4j.properties and uncomment the following line:
> log4j.rootCategory=INFO, CONSOLE, LOGFILE
> 3. Now start the axis2server with default options. Since the
> requestMaxThreadPoolSize > requestCoreThreadPoolSize, the server will not
> start, but it won't show the reason of failure on console, or log it properly
> in axs2.log. The log file thus created will only have this statement:
> 2007-11-30 14:05:58,651 [main] INFO org.apache.axis2.engine.ListenerManager
> -
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
