nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Alfresco 2.1 on Tomcat5 Installation problem

s_seifried

Hi all,

I try to run Alfresco 2.1 with Tomcat5 on a CentOS 4.4 distribution. Unfortunately alfresco hangs on some point without notification.

I switched every log level at least to debug.

policy.PolicyComponentImpl] Bound Java method[class=org.alfresco.repo.version.VersionableAspect, method=onDeleteNode] t$
11:26:22,979 INFO  [org.alfresco.repo.policy.PolicyComponentImpl] Bound Java method[class=org.alfresco.repo.version.VersionableAspect, method=afterCreateVers$
11:26:22,986 INFO  [org.alfresco.repo.policy.PolicyComponentImpl] Bound Java method[class=org.alfresco.repo.version.VersionableAspect, method=onContentUpdate$
11:26:22,987 INFO  [org.alfresco.repo.policy.PolicyComponentImpl] Bound Java method[class=org.alfresco.repo.version.VersionableAspect, method=onCopy] to poli$
11:26:24,620 INFO  [org.springframework.web.context.support.XmlWebApplicationContext] Unable to locate MessageSource with name 'messageSource': using default$
11:26:24,629 INFO  [org.springframework.web.context.support.XmlWebApplicationContext] Unable to locate ApplicationEventMulticaster with name 'applicationEven$
11:26:24,644 INFO  [org.springframework.ui.context.support.UiApplicationContextUtils] Unable to locate ThemeSource with name 'themeSource': using default [or$
11:26:25,735 INFO  [org.springframework.scheduling.quartz.SchedulerFactoryBean] Loading Quartz config from [class path resource [alfresco/domain/quartz.prope$
11:26:26,090 DEBUG [org.alfresco.repo.workflow.jbpm.JBPMTransactionTemplate] jBPM persistence service present
11:26:26,091 DEBUG [org.alfresco.repo.workflow.jbpm.JBPMTransactionTemplate] creating hibernateTemplate based on jBPM SessionFactory
11:26:26,417 INFO  [org.springframework.beans.factory.support.DefaultListableBeanFactory] Pre-instantiating singletons in factory [org.springframework.beans.$
11:26:26,421 INFO  [org.springframework.remoting.rmi.RmiRegistryFactoryBean] Looking for RMI registry at port '50500'
‍‍‍‍‍‍‍‍‍‍‍‍‍‍

It seems that it cannot find the RMI registry at port 50500
a short check reveals this:

lsof -i :50500
COMMAND   PID   USER   FD   TYPE DEVICE SIZE NODE NAME
java    18827 tomcat  195u  IPv4  59160       TCP *:50500 (LISTEN)
java    18827 tomcat  201u  IPv4  59522       TCP 81.19.151.66:33299->root86.l                                    ocaldomain:50500 (SYN_SENT)
‍‍‍‍‍

I also noticed that there are no tables in the database, since it is the first time I try to install Alfresco I cannot tell if this is normal at this point of execution.

PS: This is a 'virgin' installation, so no other software should bother tomcat so far.

Thanks for your help

Find more posts tagged with

Comments

s_seifried

I just fugured out, that alfresco tries to generate a new RMI registry after 4 Minutes

11:32:51,190 INFO  [org.alfresco.repo.dictionary.DictionaryDAO] Registered namespace 'http://www.w3.org/XML/1998/namespace' (prefix 'xml')
11:32:51,326 INFO  [org.springframework.remoting.rmi.RmiServiceExporter] Looking for RMI registry at port '50500'
11:36:00,300 WARN  [org.springframework.remoting.rmi.RmiServiceExporter] Could not detect RMI registry - creating new one
11:36:00,311 INFO  [org.springframework.beans.factory.support.DefaultListableBeanFactory] Destroying singletons in {org.springframework.beans.factory.supp$
11:36:00,317 INFO  [org.springframework.jmx.export.MBeanExporter] Unregistering JMX-exposed beans on shutdown
‍‍‍‍‍‍

But ends up in a ObjID already in use error

00,409 INFO  [org.hibernate.impl.SessionFactoryImpl] closing
11:36:00,426 ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'avmRemoteService' defined in class path resource [alfresco/remote-ser$
Caused by:
java.rmi.server.ExportException: internal error: ObjID already in use
        at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:169)
        at sun.rmi.transport.Transport.exportObject(Transport.java:74)
        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:229)
        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
‍‍‍‍‍‍‍‍‍‍‍

s_seifried

I must admit that I should have paid closer attention to the other threads with similar problems. The final solution was a wrong entry in the /etc/hosts file.

# /etc/hosts
# Auto-generated file.  Keep your customizations at the bottom of this file.
127.0.0.1        localhost localhost.localdomain
xx.xx.151.66     root86.localdomain root86-eth0.localdomain root86-eth0
#xx.xx.148.53     root86.localdomain root86-eth0.localdomain root86-eth0
#END of auto-generated code.  Customize beneath this line.
‍‍‍‍‍‍‍‍

just double check your own ip with ifconfig 😎
see this thread for further information
http://forums.alfresco.com/viewtopic.php?t=5463&start=30

Note that DNS problems can be very subtle.
For example, if you try to run on a machine that is served by DHCP
that hard-codes an IP address in an /etc/hosts file, and that hard-coded
IP address happens to not match the one given to you by DHCP,
then Spring's RmiServiceExporter will end up trying to bind to
an IP address that may not correspond to a network device.
If that happens, then the bind will get refused, a registry at the
*default* RMI will get created because Spring's RmiServiceExporter
makes a "best faith effort" by failing over to localhost but it won't
get any of the other settings that prevent conflicts downstream.
When those conflicts occur, you'll get "ObjID already in use".
Whew!

When in doubt, check your network interface's ip address
using something like ifconfig on unix, then ping your hostname
and see if the addresses match. Also, remember to inspect
your process list for lingering Tomcat instances. Another useful
tool on unix if some other process is causing trouble is 'lsof'.

Thanks to jcox for his very helpful post