On Mon, Mar 1, 2010 at 17:42, Robert Eichinger <[email protected]> wrote: > "main" prio=10 tid=0x0000000040955800 nid=0x1276 runnable [0x00007ffb40756000] > java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) > at java.io.BufferedInputStream.read(BufferedInputStream.java:237) > - locked <0x00007ffb27d13438> (a java.io.BufferedInputStream) > at java.io.DataInputStream.readByte(DataInputStream.java:248) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:195) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142) > at > org.apache.jackrabbit.rmi.server.ServerNode_Stub.setProperty(Unknown Source) > at > org.apache.jackrabbit.rmi.client.ClientNode.setProperty(ClientNode.java:129) > at > org.apache.jackrabbit.rmi.client.ClientNode.setProperty(ClientNode.java:236) > at > de.it2m.tel.mediaproxy.ext.data.AdvertDAO.saveAdvert(AdvertDAO.java:87) > at de.it2m.tel.mediaproxy.ext.App.main(App.java:26)
This very much looks like the jcr-rmi client is waiting on response from the server. So either the upload isn't finished yet (how big is the file? how long is it blocked?) or the server has a problem or hangs w/o sending back an error over the rmi connection. A thread dump of the server at that point in time would be the next step. Regards, Alex -- Alexander Klimetschek [email protected]
