You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by Karl Wright <da...@gmail.com> on 2011/05/02 15:00:32 UTC
Re: Agent Process in Eclipse
If you have an eclipse settings file or documentation, please consider
contributing it! I know other people like and use eclipse, even
though I don't. ;-)
Karl
On Fri, Apr 29, 2011 at 8:12 PM, daddywri@gmail.com <da...@gmail.com> wrote:
> I am not sure but it is likely related to postgresql configuration. make sure you have more postgres connections than you need.
>
> Karl
>
> Sent from my Nokia phone
> -----Original Message-----
> From: hokie@farzad.net
> Sent: 29/04/2011, 12:41 PM
> To: connectors-dev@incubator.apache.org
> Subject: Re: Agent Process in Eclipse
>
>
> That did the trick, I wasn't pointing it to the properties file!!
> Thanks!!
>
> I had left the agent process running and this morning I got the
> following error: Any thoughts?
>
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database
> exception: Exception doing query: An I/O error occured while sending to
> the backend.
> Exception: java.net.SocketTimeoutException: Read timed out
> Stack Trace:
> java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> at
> org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:135)
> at
> org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:104)
> at
> org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:73)
> at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:255)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1165)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
> at
> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
> at
> t
> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
> End of Stack Trace
>
> at
> org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:461)
> at
> org.apache.manifoldcf.core.database.Database.executeUncachedQuery(Database.java:505)
> at
> org.apache.manifoldcf.core.database.Database$QueryCacheExecutor.create(Database.java:1131)
> at
> org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:144)
> at
> org.apache.manifoldcf.core.database.Database.executeQuery(Database.java:168)
> at
> org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.performQuery(DBInterfacePostgreSQL.java:809)
> at
> org.apache.manifoldcf.core.database.BaseTable.performQuery(BaseTable.java:229)
> at
> org.apache.manifoldcf.agents.agentmanager.AgentManager.getAllAgents(AgentManager.java:218)
> at
> org.apache.manifoldcf.agents.system.ManifoldCF.startAgents(ManifoldCF.java:103)
> at org.apache.manifoldcf.agents.AgentRun.doExecute(AgentRun.java:50)
> at
> org.apache.manifoldcf.agents.BaseAgentsInitializationCommand.execute(BaseAgentsInitializationCommand.java:37)
> at org.apache.manifoldcf.agents.AgentRun.main(AgentRun.java:77)
> Caused by: org.postgresql.util.PSQLException: An I/O error occured
> while sending to the backend.
> Exception: java.net.SocketTimeoutException: Read timed out
> Stack Trace:
> java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> at
> org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:135)
> at
> org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:104)
> at
> org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:73)
> at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:255)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1165)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
> at
> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
> at
> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
> End of Stack Trace
>
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
> at
> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
> at
> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
> PooledConnection.guardConnection(): found closed Connection. Statement
> information follows. Attempting to recover.
> PooledConnection.guardConnection: statement was null
> PooledConnection.guardConnection(): Recovered connection
> ERROR: transport error 202: recv error: Connection timed out
>
>
> On Fri, 29 Apr 2011 02:13:59 -0400, Karl Wright <da...@gmail.com>
> wrote:
>> Because the sync dir is used by ALL the running processes, it is not
>> safe to have just ONE clean up the area on startup or shutdown.
>>
>> My thought is that since the AgentStop process uses the synch area
>> too, you are neglecting to supply the correct
>> -Dorg.apache.manifoldcf.configfile switch to it so that it finds the
>> right properties.xml and can properly communicate with the running
>> Agents process. Registration commands etc also ought to be receiving
>> the same -D switch.
>>
>> Karl
>>
>>
>>
>> On Fri, Apr 29, 2011 at 12:11 AM, <ho...@farzad.net> wrote:
>>> I've got most of the pieces working in Eclipse. The one problem I'm
>>> working
>>> through is stopping the agent process. It seems that when the agent
>>> is
>>> running in Eclipse, it is not receiving the signal. Any thought as
>>> to what
>>> might be causing this?
>>>
>>> Noted in the docs says if you have to kill the agent, then call the
>>> LockClean command. Going through the code, it seems to just delete
>>> all the
>>> sync dirs, would I do this manually myself. Even better you I might
>>> have
>>> eclipse clean up the sync dir before starting the agent.
>>>
>>> Thanks!
>>>
>
Re: Agent Process in Eclipse
Posted by Karl Wright <da...@gmail.com>.
Sounds great! I'm looking forward to seeing all this come together.
Obviously you'll want to create a Jira ticket and go through the
normal patch process.
Karl
On Mon, May 2, 2011 at 12:20 PM, <ho...@farzad.net> wrote:
> Yes, I plan on contributing my work. I have successfully setup the war
> files and the agent code from within eclipse where I can break through any
> of the code!!! I need to sit down and write down the steps and capture a
> clean project structure, it took literally a week to figure it out. Once
> documented, thought we can create a folder in the Manifoldcf source called
> Eclipse and store the relevant parts in there that would go along with the
> documented setup steps.
>
> On Mon, 2 May 2011 09:00:32 -0400, Karl Wright <da...@gmail.com> wrote:
>>
>> If you have an eclipse settings file or documentation, please consider
>> contributing it! I know other people like and use eclipse, even
>> though I don't. ;-)
>>
>> Karl
>>
>> On Fri, Apr 29, 2011 at 8:12 PM, daddywri@gmail.com
>> <da...@gmail.com> wrote:
>>>
>>> I am not sure but it is likely related to postgresql configuration. make
>>> sure you have more postgres connections than you need.
>>>
>>> Karl
>>>
>>> Sent from my Nokia phone
>>> -----Original Message-----
>>> From: hokie@farzad.net
>>> Sent: 29/04/2011, 12:41 PM
>>> To: connectors-dev@incubator.apache.org
>>> Subject: Re: Agent Process in Eclipse
>>>
>>>
>>> That did the trick, I wasn't pointing it to the properties file!!
>>> Thanks!!
>>>
>>> I had left the agent process running and this morning I got the
>>> following error: Any thoughts?
>>>
>>> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database
>>> exception: Exception doing query: An I/O error occured while sending to
>>> the backend.
>>> Exception: java.net.SocketTimeoutException: Read timed out
>>> Stack Trace:
>>> java.net.SocketTimeoutException: Read timed out
>>> at java.net.SocketInputStream.socketRead0(Native Method)
>>> at java.net.SocketInputStream.read(Unknown Source)
>>> at
>>>
>>>
>>> org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:135)
>>> at
>>>
>>>
>>> org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:104)
>>> at
>>>
>>>
>>> org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:73)
>>> at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:255)
>>> at
>>>
>>>
>>> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1165)
>>> at
>>>
>>>
>>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
>>> at
>>>
>>> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
>>> at
>>> t
>>>
>>>
>>> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
>>> End of Stack Trace
>>>
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:461)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.database.Database.executeUncachedQuery(Database.java:505)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.database.Database$QueryCacheExecutor.create(Database.java:1131)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:144)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.database.Database.executeQuery(Database.java:168)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.performQuery(DBInterfacePostgreSQL.java:809)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.database.BaseTable.performQuery(BaseTable.java:229)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.agents.agentmanager.AgentManager.getAllAgents(AgentManager.java:218)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.agents.system.ManifoldCF.startAgents(ManifoldCF.java:103)
>>> at
>>> org.apache.manifoldcf.agents.AgentRun.doExecute(AgentRun.java:50)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.agents.BaseAgentsInitializationCommand.execute(BaseAgentsInitializationCommand.java:37)
>>> at org.apache.manifoldcf.agents.AgentRun.main(AgentRun.java:77)
>>> Caused by: org.postgresql.util.PSQLException: An I/O error occured
>>> while sending to the backend.
>>> Exception: java.net.SocketTimeoutException: Read timed out
>>> Stack Trace:
>>> java.net.SocketTimeoutException: Read timed out
>>> at java.net.SocketInputStream.socketRead0(Native Method)
>>> at java.net.SocketInputStream.read(Unknown Source)
>>> at
>>>
>>>
>>> org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:135)
>>> at
>>>
>>>
>>> org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:104)
>>> at
>>>
>>>
>>> org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:73)
>>> at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:255)
>>> at
>>>
>>>
>>> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1165)
>>> at
>>>
>>>
>>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
>>> at
>>>
>>> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
>>> End of Stack Trace
>>>
>>> at
>>>
>>>
>>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
>>> at
>>>
>>>
>>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
>>> at
>>>
>>> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
>>> at
>>>
>>>
>>> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
>>> PooledConnection.guardConnection(): found closed Connection. Statement
>>> information follows. Attempting to recover.
>>> PooledConnection.guardConnection: statement was null
>>> PooledConnection.guardConnection(): Recovered connection
>>> ERROR: transport error 202: recv error: Connection timed out
>>>
>>>
>>> On Fri, 29 Apr 2011 02:13:59 -0400, Karl Wright <da...@gmail.com>
>>> wrote:
>>>>
>>>> Because the sync dir is used by ALL the running processes, it is not
>>>> safe to have just ONE clean up the area on startup or shutdown.
>>>>
>>>> My thought is that since the AgentStop process uses the synch area
>>>> too, you are neglecting to supply the correct
>>>> -Dorg.apache.manifoldcf.configfile switch to it so that it finds the
>>>> right properties.xml and can properly communicate with the running
>>>> Agents process. Registration commands etc also ought to be receiving
>>>> the same -D switch.
>>>>
>>>> Karl
>>>>
>>>>
>>>>
>>>> On Fri, Apr 29, 2011 at 12:11 AM, <ho...@farzad.net> wrote:
>>>>>
>>>>> I've got most of the pieces working in Eclipse. The one problem I'm
>>>>> working
>>>>> through is stopping the agent process. It seems that when the agent
>>>>> is
>>>>> running in Eclipse, it is not receiving the signal. Any thought as
>>>>> to what
>>>>> might be causing this?
>>>>>
>>>>> Noted in the docs says if you have to kill the agent, then call the
>>>>> LockClean command. Going through the code, it seems to just delete
>>>>> all the
>>>>> sync dirs, would I do this manually myself. Even better you I might
>>>>> have
>>>>> eclipse clean up the sync dir before starting the agent.
>>>>>
>>>>> Thanks!
>>>>>
>>>
>
>
Re: Agent Process in Eclipse
Posted by ho...@farzad.net.
Yes, I plan on contributing my work. I have successfully setup the war
files and the agent code from within eclipse where I can break through
any of the code!!! I need to sit down and write down the steps and
capture a clean project structure, it took literally a week to figure it
out. Once documented, thought we can create a folder in the Manifoldcf
source called Eclipse and store the relevant parts in there that would
go along with the documented setup steps.
On Mon, 2 May 2011 09:00:32 -0400, Karl Wright <da...@gmail.com>
wrote:
> If you have an eclipse settings file or documentation, please
> consider
> contributing it! I know other people like and use eclipse, even
> though I don't. ;-)
>
> Karl
>
> On Fri, Apr 29, 2011 at 8:12 PM, daddywri@gmail.com
> <da...@gmail.com> wrote:
>> I am not sure but it is likely related to postgresql configuration.
>> make sure you have more postgres connections than you need.
>>
>> Karl
>>
>> Sent from my Nokia phone
>> -----Original Message-----
>> From: hokie@farzad.net
>> Sent: 29/04/2011, 12:41 PM
>> To: connectors-dev@incubator.apache.org
>> Subject: Re: Agent Process in Eclipse
>>
>>
>> That did the trick, I wasn't pointing it to the properties file!!
>> Thanks!!
>>
>> I had left the agent process running and this morning I got the
>> following error: Any thoughts?
>>
>> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database
>> exception: Exception doing query: An I/O error occured while
>> sending to
>> the backend.
>> Exception: java.net.SocketTimeoutException: Read timed out
>> Stack Trace:
>> java.net.SocketTimeoutException: Read timed out
>> at java.net.SocketInputStream.socketRead0(Native Method)
>> at java.net.SocketInputStream.read(Unknown Source)
>> at
>>
>> org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:135)
>> at
>>
>> org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:104)
>> at
>>
>> org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:73)
>> at
>> org.postgresql.core.PGStream.ReceiveChar(PGStream.java:255)
>> at
>>
>> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1165)
>> at
>>
>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
>> at
>>
>> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
>> at
>> t
>>
>> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
>> End of Stack Trace
>>
>> at
>>
>> org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:461)
>> at
>>
>> org.apache.manifoldcf.core.database.Database.executeUncachedQuery(Database.java:505)
>> at
>>
>> org.apache.manifoldcf.core.database.Database$QueryCacheExecutor.create(Database.java:1131)
>> at
>>
>> org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:144)
>> at
>>
>> org.apache.manifoldcf.core.database.Database.executeQuery(Database.java:168)
>> at
>>
>> org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.performQuery(DBInterfacePostgreSQL.java:809)
>> at
>>
>> org.apache.manifoldcf.core.database.BaseTable.performQuery(BaseTable.java:229)
>> at
>>
>> org.apache.manifoldcf.agents.agentmanager.AgentManager.getAllAgents(AgentManager.java:218)
>> at
>>
>> org.apache.manifoldcf.agents.system.ManifoldCF.startAgents(ManifoldCF.java:103)
>> at
>> org.apache.manifoldcf.agents.AgentRun.doExecute(AgentRun.java:50)
>> at
>>
>> org.apache.manifoldcf.agents.BaseAgentsInitializationCommand.execute(BaseAgentsInitializationCommand.java:37)
>> at
>> org.apache.manifoldcf.agents.AgentRun.main(AgentRun.java:77)
>> Caused by: org.postgresql.util.PSQLException: An I/O error occured
>> while sending to the backend.
>> Exception: java.net.SocketTimeoutException: Read timed out
>> Stack Trace:
>> java.net.SocketTimeoutException: Read timed out
>> at java.net.SocketInputStream.socketRead0(Native Method)
>> at java.net.SocketInputStream.read(Unknown Source)
>> at
>>
>> org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:135)
>> at
>>
>> org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:104)
>> at
>>
>> org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:73)
>> at
>> org.postgresql.core.PGStream.ReceiveChar(PGStream.java:255)
>> at
>>
>> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1165)
>> at
>>
>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
>> at
>>
>> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
>> at
>>
>> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
>> End of Stack Trace
>>
>> at
>>
>> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:337)
>> at
>>
>> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:329)
>> at
>>
>> org.apache.manifoldcf.core.database.Database.execute(Database.java:566)
>> at
>>
>> org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.run(Database.java:421)
>> PooledConnection.guardConnection(): found closed Connection.
>> Statement
>> information follows. Attempting to recover.
>> PooledConnection.guardConnection: statement was null
>> PooledConnection.guardConnection(): Recovered connection
>> ERROR: transport error 202: recv error: Connection timed out
>>
>>
>> On Fri, 29 Apr 2011 02:13:59 -0400, Karl Wright
>> <da...@gmail.com>
>> wrote:
>>> Because the sync dir is used by ALL the running processes, it is
>>> not
>>> safe to have just ONE clean up the area on startup or shutdown.
>>>
>>> My thought is that since the AgentStop process uses the synch area
>>> too, you are neglecting to supply the correct
>>> -Dorg.apache.manifoldcf.configfile switch to it so that it finds
>>> the
>>> right properties.xml and can properly communicate with the running
>>> Agents process. Registration commands etc also ought to be
>>> receiving
>>> the same -D switch.
>>>
>>> Karl
>>>
>>>
>>>
>>> On Fri, Apr 29, 2011 at 12:11 AM, <ho...@farzad.net> wrote:
>>>> I've got most of the pieces working in Eclipse. The one problem
>>>> I'm
>>>> working
>>>> through is stopping the agent process. It seems that when the
>>>> agent
>>>> is
>>>> running in Eclipse, it is not receiving the signal. Any thought
>>>> as
>>>> to what
>>>> might be causing this?
>>>>
>>>> Noted in the docs says if you have to kill the agent, then call
>>>> the
>>>> LockClean command. Going through the code, it seems to just
>>>> delete
>>>> all the
>>>> sync dirs, would I do this manually myself. Even better you I
>>>> might
>>>> have
>>>> eclipse clean up the sync dir before starting the agent.
>>>>
>>>> Thanks!
>>>>
>>