Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 53427 - JBoss does not shutdown properly
Summary: JBoss does not shutdown properly
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-09 09:23 UTC by Michael Labhard
Modified: 2004-07-22 23:02 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Labhard 2004-06-09 09:23:57 UTC 
goliath root # /etc/init.d/jboss restart
 * Stopping JBoss...
09:01:51,749 WARN  [NamingContext] Failed to connect to localhost:1099
javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:215)
        at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1181)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
        at javax.naming.InitialContext.lookup(InitialContext.java:347)
        at org.jboss.Shutdown.main(Shutdown.java:182)
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:190)
        ... 5 more
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:452)
        at java.net.Socket.connect(Socket.java:402)
        at java.net.Socket.<init>(Socket.java:309)
        at java.net.Socket.<init>(Socket.java:211)
        at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
        at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
        at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:186)
        ... 5 more
Exception in thread "main" javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
        at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1115)
        at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1192)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
        at javax.naming.InitialContext.lookup(InitialContext.java:347)
        at org.jboss.Shutdown.main(Shutdown.java:182)
Caused by: java.net.SocketTimeoutException: Receive timed out
        at java.net.PlainDatagramSocketImpl.receive(Native Method)
        at java.net.DatagramSocket.receive(DatagramSocket.java:711)
        at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1093)
        ... 5 more                                                         [ !! ]


Reproducible: Always
Steps to Reproduce:
1.
2.
3.




Portage 2.0.50-r7 (default-amd64-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040529-r0,
2.6.5-gentoo-r1)
=================================================================
System uname: 2.6.5-gentoo-r1 x86_64 5
Gentoo Base System version 1.4.15
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2 -fPIC"
CHOST="x86_64-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /etc/tomcat /opt/resin/conf /usr/X11R6/lib/X11/xkb
/usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config
/usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/lib/jboss /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -fPIC"
DISTDIR="/opt/no_archive/portage/distfiles"
FEATURES="autoaddcvs buildpkg ccache sandbox"
GENTOO_MIRRORS="http://128.213.5.34/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/opt/no_archive/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa amd64 apm arts avi berkdb cdr crypt doc encode esd foomaticdb gdbm
gif gnome gpm gtk gtk2 imlib java jpeg kde ldap libg++ libwww log4cpp mikmod
motif mozilla mpeg mysql nas ncurses nls nogcj oggvorbis opengl oss pam pdflib
perl plotutils png postgres python qt quicktime readline ruby sdl slang spell
ssl svg tcltk tcpd tetex truetype usb wxwindows xinerama xml2 xmms xv zlib"
Comment 1 Matthew Kennedy (RETIRED) gentoo-dev 2004-07-22 23:02:44 UTC 
net-www/jboss-3.2.5 has been added to portage.  It corrects the
/etc/conf.d/jboss file to include

   SERVER_SETTINGS="${SERVER_SETTINGS} -Djboss.server.blockingshutdown=true"

I think the omission of this option may have been causing a race
condition during shutdown.