Now that I think about this a little more, this could be a filesystem
permissions error. When you started Resin, did you use an admin user, or did
you use a user with a lower level of permissions. It's possible that Resin
doesn't have write permissions on the Lock directory.
----- Original Message ----
From: Chris Pratt <[EMAIL PROTECTED]>
To: Robert MacGrogan <[EMAIL PROTECTED]>
Sent: Thursday, August 16, 2007 11:51:35 PM
Subject: Re: [SourceJammer-users] JDK 1.6 Issue
> The server issue sounds like it's probably unrelated to the new JRE. My guess
> is you got into some kind of race condition on the top-level folder when you
> restarted the server, and two threads tried to lock it at the same time. This
> happens from time to time when someone says "OK, I restarted it. Try it now!"
> and several people try to log in all together. Try restarting the SJ server
> and see if that fixes it. (I know, the lame old M$ solution to every problem,
> but it often works!)
I shut down the service and started resin in console mode, I made
sure to wait until it was up and stable then I tried it by myself
without anyone else on the system but I still get:
:: started session 2671005563055804635 for Chris
Deleting lock file: project.0
ERROR: ''
org.sourcejammer.server.security.ObjectLockingException: Unable to
obtain filesystem lock on the requested node.
at
org.sourcejammer.project.model.filesys.NodeLibraryFS.obtainLock(Unknown
Source)
at
org.sourcejammer.project.model.filesys.NodeLibraryFS.getProjectNode(Unknown
Source)
at
org.sourcejammer.project.controller.ProjectController.getRootProject(Unknown
Source)
at org.sourcejammer.project.view.MasterControlProgram.connect(Unknown
Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.soap.server.RPCRouter.invoke(RPCRouter.java:146)
at
org.apache.soap.providers.RPCJavaProvider.invoke(RPCJavaProvider.java:129)
at
org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:354)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:92)
at
com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChain.java:106)
at
com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:173)
at
com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:229)
at
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:274)
at com.caucho.server.port.TcpConnection.run(TcpConnection.java:511)
at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:516)
at com.caucho.util.ThreadPool.run(ThreadPool.java:442)
at java.lang.Thread.run(Thread.java:619)
Is there a way to manually reset the lock? Is there any information I
can pass on that would make this easier to diagnose? I'd really like
to get my SourceJammer back and I really don't want to have to
downgrade my server to do it. Thanks for a great tool, I hope I can
get it back up and running.
(*Chris*)
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for
today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SourceJammer-users mailing list
SourceJammer-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sourcejammer-users
