I'm observing the same behavior and logging used to work before, I
think. I'm taking a look at this.
Ken Paulsen wrote:
>
> Hi Jan,
>
> I spoke with Ryan. He is also unable to get exceptions that he throws
> to appear in the log file. He even tried w/ a plain JSP and was
> unable to see the trace. I have also tried setting the JSF logger
> (and others) in the logging.properties file to FINEST... and that
> doesn't generate any extra messages in the log file -- there should be
> a lot. I suspect our logging system is not configured correctly (by
> me??) or is just plain broken. Any ideas on who I can talk to? Or
> where to look next?
>
> Thanks,
>
> Ken
>
> Jan.Luehe_at_Sun.COM wrote:
>> Ken,
>>
>> Ken Paulsen wrote:
>>
>>>
>>> I am unable to see stack traces that would help me debug. Here's
>>> what I see in the browser:
>>>
>>> javax.servlet.ServletException: Unable to determine parameter type
>>> 'com.sun.appserv.management.config.PropertiesAccess' for parameter
>>> named 'mbean'.
>>>
>>> *root cause*
>>>
>>> java.lang.RuntimeException: Unable to determine parameter type
>>> 'com.sun.appserv.management.config.PropertiesAccess' for parameter
>>> named 'mbean'.
>>>
>>> *root cause*
>>>
>>> java.lang.ClassNotFoundException:
>>> com.sun.appserv.management.config.PropertiesAccess
>>>
>>
>> we deliberately omit stacktraces in the responses to clients, as
>> requested
>> by the Netbeans folks (originally, stacktraces were included in the
>> response,
>> which was considered a usability issue).
>>
>> You should see stacktraces in the server.log, though.
>>
>>> In the console (w/ asadmin start-domain -v):
>>>
>>> SEVERE: JSF1054: (Phase ID: RESTORE_VIEW 1, View ID: /testIP.jsf)
>>> Exception thrown during phase execution:
>>>
>>> javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl_at_fa54fe]
>>>
>>>
>>> And the server.log file:
>>>
>>>
>>> [#|2008-03-11T23:18:46.158+0000|SEVERE|GlassFish10.0|javax.enterprise.resource.webcontainer.jsf.lifecycle|_ThreadID=20;_ThreadName=Thread-4;RESTORE_VIEW
>>>
>>>
>>> 1;/testIP.jsf;javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl_at_fa54fe];|JSF1054:
>>>
>>> (Phase ID: RESTORE_VIEW 1, View ID: /testIP.jsf) Exception thrown
>>> during phase execution:
>>>
>>> javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl_at_fa54fe]|#]
>>>
>>>
>>
>> I'll let the JSF team comment on this.
>>
>> Jan
>>
>>
>>> I also attempted to set the logging.properties log levels, but that
>>> did not do anything.
>>>
>>> In this case, I can guess what the problem is, although I would like
>>> to know why it's a problem b/c I shouldn't be accessing any of the
>>> server api's with the request I made. A simple stack trace would
>>> show me exactly what I'm not understanding and I could move on quickly.
>>>
>>> When is this going to be fixed? Is there something I am not
>>> configuring correctly that hides all errors for the user? Why? Why?
>>> Why? :) This is slowing down my development significantly.
>>>
>>> Ken
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net For
>>> additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>