cancel
Showing results for 
Search instead for 
Did you mean: 

Programmatic access using AVMRemote API not working in lates

harrymoore
Champ in-the-making
Champ in-the-making
I found that tomcat\webapps\alfresco\WEB-INF\classes\alfresco\alfresco-shared.properties is wrong in the newer builds.

It looks like this:
# Name of the host running AVM
avm.remote.host=localhost

# AVMRemote API
avm.remote.port=50500


But it should look like this:
# Name of the host running AVM
avm.remote.host=localhost

# AVMRemote API
avm.remote.port=1313

# MBeanServer registry port  (JMX over RMI)
avm.jmxrmi.port=50500
3 REPLIES 3

harrymoore
Champ in-the-making
Champ in-the-making
Not so fast….

Now my virtualization server doesn't start. So I can either have my virtualization server or I can deploy my content. But not both. My customer would like both. Please advise!

britt
Champ in-the-making
Champ in-the-making
The shipped configuration is correct, as far as our testing has gone.  The RMI ports for jmx and and our own remote RMI interface are merged into one.  What exactly is not working?

harrymoore
Champ in-the-making
Champ in-the-making
Fixed!

I should have taken the port number setting at face value. I just changed the port number in my context file from 1313 to 50500 and it worked.

Thanks, Britt!
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.