Re: Reg. unstable Manifold instance

[Karl Wright]

Hosting on a different app server is something you could easily do.  Or,
since this takes many months before it appears, you might just live with it.
But first, there should be access logs the Jetty writes to.  It should be
possible for you to see what's happening from those logs if you can find
them.  It would be good to understand exactly what was going wrong, I'm
sure you would agree.  If running on unix, you could also monitor the jetty
process to see whether file handles appear to be leaking.
Karl


On Tue, Jul 16, 2019 at 2:25 PM Praveen Bejji 
wrote:

> @Michael,
>
> There are no error in the on the logs. The app just goes down abruptly.
>
> @Karl,
> Assuming that Jetty server has some issue, what do you suggest? Is hosting
> Manifold on some other server(say Tomcat ) an alternative?
>
>
> On Mon, Jul 15, 2019 at 9:04 AM Michael Cizmar 
> wrote:
>
>> Are there some errors or anything interest in the log?
>>
>>
>>
>> --
>>
>> Michael Cizmar
>>
>>
>>
>>
>>
>> *From: *Karl Wright 
>> *Reply-To: *"user@manifoldcf.apache.org" 
>> *Date: *Monday, July 15, 2019 at 7:56 AM
>> *To: *"user@manifoldcf.apache.org" 
>> *Subject: *Re: Reg. unstable Manifold instance
>>
>>
>>
>> I have heard of this issue before.  The app server is what is giving back
>> the 404 errors.  I wonder if the version of jetty we ship has a resource
>> leak of some kind.
>>
>>
>>
>> Karl
>>
>>
>>
>>
>>
>> On Sun, Jul 14, 2019 at 11:34 PM Praveen Bejji 
>> wrote:
>>
>> Hi,
>>
>>
>>
>> We have been running manifoldcf for almost 6 months now. We see that the
>> Web app goes down intermittently and gives an 404 error. However, we are
>> able to access the authority URL and could see that  jobs are running as
>> scheduled.
>>
>> Restarting Manifold fixes the issue but it appears again after couple of
>> weeks. This has been our routine for few months now.
>>
>>
>>
>> To give some background on our setup, Manifold is running in quick start
>> single process model on an Linux server. Linux server has a 8 Core CPU with
>> 16 Gig of RAM. Manilfold is  hosting a documentum connector and 2-3 custom
>> connectors.
>>
>>
>>
>> Any help will be  greatly appreciated.
>>
>>
>>
>> -PK
>>
>>

Re: Reg. unstable Manifold instance

[Praveen Bejji]

@Michael,

There are no error in the on the logs. The app just goes down abruptly.

@Karl,
Assuming that Jetty server has some issue, what do you suggest? Is hosting
Manifold on some other server(say Tomcat ) an alternative?


On Mon, Jul 15, 2019 at 9:04 AM Michael Cizmar 
wrote:

> Are there some errors or anything interest in the log?
>
>
>
> --
>
> Michael Cizmar
>
>
>
>
>
> *From: *Karl Wright 
> *Reply-To: *"user@manifoldcf.apache.org" 
> *Date: *Monday, July 15, 2019 at 7:56 AM
> *To: *"user@manifoldcf.apache.org" 
> *Subject: *Re: Reg. unstable Manifold instance
>
>
>
> I have heard of this issue before.  The app server is what is giving back
> the 404 errors.  I wonder if the version of jetty we ship has a resource
> leak of some kind.
>
>
>
> Karl
>
>
>
>
>
> On Sun, Jul 14, 2019 at 11:34 PM Praveen Bejji 
> wrote:
>
> Hi,
>
>
>
> We have been running manifoldcf for almost 6 months now. We see that the
> Web app goes down intermittently and gives an 404 error. However, we are
> able to access the authority URL and could see that  jobs are running as
> scheduled.
>
> Restarting Manifold fixes the issue but it appears again after couple of
> weeks. This has been our routine for few months now.
>
>
>
> To give some background on our setup, Manifold is running in quick start
> single process model on an Linux server. Linux server has a 8 Core CPU with
> 16 Gig of RAM. Manilfold is  hosting a documentum connector and 2-3 custom
> connectors.
>
>
>
> Any help will be  greatly appreciated.
>
>
>
> -PK
>
>

R: Documentum connection not working

[Bisonti Mario]

Hallo.
Thanks..I didn’t read the documentation about the sidecar documentum process.

Thanks a lot.



.

Da: Karl Wright 
Inviato: martedì 16 luglio 2019 13:20
A: user@manifoldcf.apache.org
Oggetto: Re: Documentum connection not working

Are you running the documentum connector sidecar processes?  You need to be 
running those, and the documentum_server process must include a valid DFC 
distribution with a valid configuration file.  This is where the documentum 
server name comes from.

The documentation for "how to build and deploy" describes all this.
Karl


On Tue, Jul 16, 2019 at 6:12 AM Bisonti Mario 
mailto:mario.biso...@vimar.com>> wrote:
Hallo.

I am using MCF 2.12
I would like to create a Repository connection to a Documentum Docbase

I obtain always the error:
Connection temporarily failed: Connection refused to host: 127.0.0.1; nested 
exception is: java.net.ConnectException: Connection refused (Connection refused)

I don’t understand if there is a problem about the webtop url?
docbasename=abc_test
webtopbaseurl=http://servenname.domain.net/documentale/component/main/
docbaseusername=documentum
domain=
docbasepassword=

Or is there any other issue about this?

Furthermore I was trying to create a Authority Connection to Documentum but I 
obtain the error:
Connection failed: Transient remote exception creating session: Connection 
refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: 
Connection refused (Connection refused)
In this case, I don’t see any field about the documentum server name:
docbasename=abc_test
docbaseusername=documentum
domain=
usernamecaseinsensitive=false
cachelifetimemins=1
cachelrusize=1000
usesystemacls=true
docbasepassword=

So how could it work?

Thanks a lot
Mario

Re: Documentum connection not working

[Karl Wright]

Are you running the documentum connector sidecar processes?  You need to be
running those, and the documentum_server process must include a valid DFC
distribution with a valid configuration file.  This is where the documentum
server name comes from.

The documentation for "how to build and deploy" describes all this.
Karl


On Tue, Jul 16, 2019 at 6:12 AM Bisonti Mario 
wrote:

> Hallo.
>
>
>
> I am using MCF 2.12
>
> I would like to create a Repository connection to a Documentum Docbase
>
>
>
> I obtain always the error:
>
> Connection temporarily failed: Connection refused to host: 127.0.0.1;
> nested exception is: java.net.ConnectException: Connection refused
> (Connection refused)
>
>
>
> I don’t understand if there is a problem about the webtop url?
>
> docbasename=abc_test
> webtopbaseurl=http://servenname.domain.net/documentale/component/main/
> docbaseusername=documentum
> domain=
> docbasepassword=
>
>
>
> Or is there any other issue about this?
>
>
>
> Furthermore I was trying to create a Authority Connection to Documentum
> but I obtain the error:
>
> Connection failed: Transient remote exception creating session: Connection
> refused to host: 127.0.0.1; nested exception is: java.net.ConnectException:
> Connection refused (Connection refused)
>
> In this case, I don’t see any field about the documentum server name:
>
> docbasename=abc_test
> docbaseusername=documentum
> domain=
> usernamecaseinsensitive=false
> cachelifetimemins=1
> cachelrusize=1000
> usesystemacls=true
> docbasepassword=
>
>
>
> So how could it work?
>
>
>
> Thanks a lot
>
> Mario
>

Documentum connection not working

[Bisonti Mario]

Hallo.

I am using MCF 2.12
I would like to create a Repository connection to a Documentum Docbase

I obtain always the error:
Connection temporarily failed: Connection refused to host: 127.0.0.1; nested 
exception is: java.net.ConnectException: Connection refused (Connection refused)

I don’t understand if there is a problem about the webtop url?
docbasename=abc_test
webtopbaseurl=http://servenname.domain.net/documentale/component/main/
docbaseusername=documentum
domain=
docbasepassword=

Or is there any other issue about this?

Furthermore I was trying to create a Authority Connection to Documentum but I 
obtain the error:
Connection failed: Transient remote exception creating session: Connection 
refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: 
Connection refused (Connection refused)
In this case, I don’t see any field about the documentum server name:
docbasename=abc_test
docbaseusername=documentum
domain=
usernamecaseinsensitive=false
cachelifetimemins=1
cachelrusize=1000
usesystemacls=true
docbasepassword=

So how could it work?

Thanks a lot
Mario