In 2.0 it is always happening in jetty6-jee5 server during
shutdown. In addition this trace is produced when attributes of
JavaCompContext (rmi-naming config) are viewed in jconsole.
I eliminated this NPE by hacking, it did not solve the following sql
problem:
SQL Exception: No current
Prasad,
I am hoping that the fix Dain promised for the branch might help
with this too..
I am waiting for it :)
On Dec 7, 2006, at 10:32 AM, Dain Sundstrom wrote:
We have an exception being thrown in shutdown from
GBeanBinding.removeBinding():159 and I'll fix that today.
On Dec 11, 2006, at 8:33 AM, anita kulshreshtha wrote:
Prasad,
I am hoping that the fix Dain promised for the branch might help
with this too..
I am waiting for it :)
On Dec 7, 2006, at 10:32 AM, Dain Sundstrom wrote:
We have an exception being thrown in shutdown from
I've been seeing it on all recent 2.0-SNAPSHOT assemblies.
Just hit cntlr+c in a running geronimo window or use the shutdown. The
geronimo.log would have the stacktrace or the window running the
server would, depending on how you started it.
Cheers
Prasad
On 12/11/06, Dain Sundstrom [EMAIL
I'm seeing the following stack trace when shutting down the jetty6
geronimo server in trunk. Anyone have a clue about why, if it is a
problem, and what we might do about it?
thanks
david jencks
Server shutdown begun
00:37:33,024 WARN [GeronimoConnectionEventListener]
I'm seeing the following stack trace when shutting down the jetty6
geronimo server in trunk. Anyone have a clue about why, if it is a
problem, and what we might do about it?
thanks
david jencks
Server shutdown begun
00:37:33,024 WARN [GeronimoConnectionEventListener]
Yes I am seeing this too. Still investigating..
Thanks
Anita
--- David Jencks [EMAIL PROTECTED] wrote:
I'm seeing the following stack trace when shutting down the jetty6
geronimo server in trunk. Anyone have a clue about why, if it is a
problem, and what we might do about it?
This trace is produced by geronimo-framework. The trace is produced
when attributes of JavaCompContext (rmi-naming) are viewed by jconsole.
Thanks
Anita
[*] 100% 4s Startup complete
Listening on Ports:
1099 0.0.0.0 RMI Naming
4242 0.0.0.0 Remote Login Listener
I get this error when shutting down jee5-jetty6 jee5-tomcat
Regards
Krish
On 12/7/06, anita kulshreshtha [EMAIL PROTECTED] wrote:
This trace is produced by geronimo-framework. The trace is produced
when attributes of JavaCompContext (rmi-naming) are viewed by jconsole.
Thanks
Anita
