Hi!

Today I was trying again JBoss-4.0.4 and it runs much better than the
last time.  This DB problem is gone (mark, can you remember?), maybe
because a shutdown does not crash anymore, and it does not shutdown
itself anymore after running a few minutes.  And even the startup time
is faster with CACAO than Sun 1.5 (on x86_64):

Sun:

12:59:21,259 INFO  [Server] JBoss (MX MicroKernel) [4.0.4.GA (build:
CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 31s:847ms

CACAO:

13:00:10,791 INFO  [Server] JBoss (MX MicroKernel) [4.0.4.GA (build:
CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 20s:144ms

But after 2 minutes running I get this exception, every 5 seconds:

13:02:10,416 WARN  [URLDeploymentScanner] Scan URL, caught
java.io.IOException: Could not list directory
'/home/twisti/src/cacao/jboss/jboss-4.0.4.GA/server/default/deploy',
reason unknown

I thinks it's related to the number of open files.  Because, I tried to
run the jboss applet with gappletviewer after getting this exception and
got this exception from jboss:

13:05:29,510 ERROR [PoolTcpEndpoint] Endpoint
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080] ignored
exception: java.io.IOException: Too many open files
java.io.IOException: Too many open files
   at gnu.java.net.VMPlainSocketImpl.accept(Native Method)
   at gnu.java.net.PlainSocketImpl.accept(PlainSocketImpl.java:282)
   at java.net.ServerSocket.implAccept(ServerSocket.java:369)
   at java.net.ServerSocket.accept(ServerSocket.java:321)
   at 
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:60)
   at 
org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:407)
   at org.apache.tomcat.util.net.PoolTcpEndpoint.run(PoolTcpEndpoint.java:647)
   at java.lang.Thread.run(Thread.java:740)
   at java.lang.VMThread.run(VMThread.java:120)

Maybe we have a leak somewhere in closing files?

On shutdown I get a NPE:

13:07:37,901 WARN  [JRMPInvoker] Stopping failed
jboss:service=invoker,type=jrmp
java.lang.NullPointerException
   at 
java.rmi.server.UnicastRemoteObject.unexportObject(UnicastRemoteObject.java:240)
   at 
org.jboss.invocation.jrmp.server.JRMPInvoker.unexportCI(JRMPInvoker.java:457)
   at 
org.jboss.invocation.jrmp.server.JRMPInvoker.stopService(JRMPInvoker.java:386)
   at 
org.jboss.invocation.jrmp.server.JRMPInvoker$1.stopService(JRMPInvoker.java:154)
   at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
   at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
   at 
org.jboss.invocation.jrmp.server.JRMPInvoker.jbossInternalLifecycle(JRMPInvoker.java:645)
   at java.lang.reflect.Method.invokeNative(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:355)
   at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
   at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at 
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
   at $Proxy0.stop(Unknown Source)
   at org.jboss.system.ServiceController.stop(ServiceController.java:508)
   at java.lang.reflect.Method.invokeNative(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:355)
   at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
   at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
   at $Proxy4.stop(Unknown Source)
   at org.jboss.deployment.SARDeployer.stop(SARDeployer.java:336)
   at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:658)
   at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:631)
   at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:510)
   at java.lang.reflect.Method.invokeNative(Native Method)
   at java.lang.reflect.Method.invoke(Method.java:355)
   at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
   at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
   at 
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at 
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
   at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
   at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
   at 
org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:1050)
   at 
org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:1025)
   at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:988)
   at java.lang.VMThread.run(VMThread.java:120)

13:07:37,953 INFO  [Server] Shutdown complete
Shutdown complete
Halting VM

The jboss applet has a problem too.  It shows some strange artefacts on
the top and on the left (screenshot attached).  But the symbols appear
to the mouse as they are on the correct position.  Means, I have to
click into the top artefacts to open the Monitoring.  Ohh, I even just
noticed that the grey part above the artefacts belongs to the applet too
and is clickable.

Any hints and bugfixes are welcome :-)

TWISTI

Attachment: jboss-applet.png
Description: PNG image

Reply via email to