topic Re: Could not connect to JMX Server in Alfresco Archive

Could not connect to JMX Server

grumpy_burton — Tue, 27 Mar 2007 04:37:01 GMT

I seem to get these pretty often… and then I can't push content… any ideas?14:31:58,843 ERROR [alfresco.mbeans.VirtServerRegistry] Could not connect to JMX Server within remote virtualization server (this may be a transient error.)‍I also seem to get these pretty often…INFO: Connected to remote Alfr

Re: Could not connect to JMX Server

edgar — Tue, 27 Mar 2007 07:06:37 GMT

Same here. Logging out of Alfresco and back in again works as a workaround for me.

It seems that there is bug in Alfresco's caching system somewhere.

Maybe you can post these two issues (not sure if they are related) to Alfresco's JIRA (if they are not already there)?

http://issues.alfresco.com

Re: Could not connect to JMX Server

jcox — Tue, 27 Mar 2007 16:22:22 GMT

This has nothing to do with caching, despite the classname you're seeing.
Also, the problem has nothing to do with logging in or out, despite the
fact that it seems that logging out "fixes" things.

Actually, what *is* fixing things is the time it takes you to log out & back in.

Here's what's going on:

[1] The virt server started up before (or faster than) the alfresco webapp
[2] The virt server hang around waiting for the AVM to become available
[3] Warnings are emitted about not able to connect via JMX
[4] Someone tries to view content anyhow (but the server is not up yet)
[5] Anything that tries to access AVMRemote (e.g.: the CacheControlFilter) barfs
[6] Eventually, the Alfresco webapp is started (or becomes fully "up").
[7] The virt server registers itself with the alfresco webapp (now AVMRemote works).
[8] Now your webapp will function via the virt server

If you ever stop the alfresco webapp, the virt server will just start doing
a slow poll, waiting for it to come back up.   Thus, you *will* see some
funkiness during edge conditions like startup shutdown when one server
is not quite up yet (or when a re-poll has not occured yet).

I could make the error condition prettier, but the fundamental behavior
cannot change – there's simply nothing for the virt server to talk to on
the other end until the AVM is fully "up".

    I hope this helps,
    -Jon

Re: Could not connect to JMX Server

grumpy_burton — Wed, 28 Mar 2007 00:24:19 GMT

Actually… I am getting these AFTER both servers have been started and running successfully for a period of time (i.e. just then it happened after about 30mins of both running successfully…)

Seems to happen most often after a bulk import.

Re: Could not connect to JMX Server

edgar — Wed, 28 Mar 2007 04:41:18 GMT

Hi Jon,

thanks for the quick reply. I also see this problem after both servers have started up. I see this problem when the servers have been running for hours. I cannot tell you exactly when the problem occurs. I will keep an eye out.

About the start-up of Alfresco WCM that you wrote down. I am a little confused. I start Alfresco this way:
1. Alfresco ECMS Community Network -> Start Alfresco Server
2. Two Tomcat windows are opened. One repeatedly says: "WARNING: Retrying JNDI connection..". The other one "INFO: Deploying web application archive alfresco.war".
3. Once the deploying of the WAR has finished the first Tomcat is happy and the window is closed.
4. Only now I start Alfresco WCM.

In the first steps (ECMS) no Virtualization Server is started is there? Alfresco WCM is the Virtualization Server, right?

I am a bit confused because previous versions of Alfresco (like 2.0-preview) started up differently.

cheers,

Edgar

Re: Could not connect to JMX Server

jcox — Thu, 05 Apr 2007 14:51:58 GMT

Edgar,

I wanted to make sure you saw this post:
http://forums.alfresco.com/viewtopic.php?p=19322#19322

There's also been a bug filed for virt server's installer on Windows platforms:
http://issues.alfresco.com/browse/WCM-422

You don't have to wait for a patch; just install the virtualization
server as a service.