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.

Can Alfresco 3.4 deploy to 3.0-era File System Receivers?

tvaughan77

I have 2 Alfresco servers: a "prod" and a "dev".

Both servers started off as 3.0-labs installations and were deploying happily across my network to a variety of file system receivers set up on a variety of servers.

I upgraded my "dev" alfresco server to 3.4.b and I cannot get any deployments from a web project to work. Everything fails with a message like:

11060009 Could not connect to remote deployment receiver, transportName:default, hostName:foo.mycompany.com, port: 44100

#) I tried the hostName as an IP address and as a regular machine name.
#) I tried telnetting directly to the 44100 port and got a response
#) I verified the target file system receiver had the -Djava.rmi.server.hostname command line parameter

The full stack trace is below, but does anyone know if there were any backwards-incompatibilities or new configurations I need to add to get FSRs to be "seen" by my alfresco server?

org.alfresco.service.cmr.avm.AVMException: 11060010 Deployment exception, unable to deploy :
srcPathosnet:/www/avm_webapps/ROOT, target:boss02test, version:11, adapterName:default, hostName:foo.mycompany.com, port:44,100,
errorrg.alfresco.service.cmr.avm.AVMException: 11060009 Could not connect to remote deployment receiver, transportName:default, hostName:foo.mycompany.com, port: 44100 at
org.alfresco.repo.deploy.DeploymentServiceImpl.deployDifferenceFS(DeploymentServiceImpl.java:1275) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at
org.alfresco.repo.transaction.CheckTransactionAdvice.invoke(CheckTransactionAdvice.java:47) at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.alfresco.repo.transaction.RetryingTransactionAdvice$1.execute(RetryingTransactionAdvice.java:64) at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:377) at org.alfresco.repo.transaction.RetryingTransactionAdvice.invoke(RetryingTransactionAdvice.java:67) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) at $Proxy83.deployDifferenceFS(Unknown Source) at org.alfresco.repo.avm.actions.AVMDeployWebsiteAction.executeImpl(AVMDeployWebsiteAction.java:403) at org.alfresco.repo.action.executer.ActionExecuterAbstractBase.execute(ActionExecuterAbstractBase.java:133) at org.alfresco.repo.action.ActionServiceImpl.directActionExecution(ActionServiceImpl.java:749) at org.alfresco.repo.action.ActionServiceImpl.executeActionImpl(ActionServiceImpl.java:675) at org.alfresco.repo.action.AsynchronousActionExecutionQueueImpl$ActionExecutionWrapper$1$1.execute(AsynchronousActionExecutionQueueImpl.java:443) at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:377) at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:251) at org.alfresco.repo.action.AsynchronousActionExecutionQueueImpl$ActionExecutionWrapper$1.doWork(AsynchronousActionExecutionQueueImpl.java:452) at org.alfresco.repo.security.authentication.AuthenticationUtil.runAs(AuthenticationUtil.java:508) at org.alfresco.repo.action.AsynchronousActionExecutionQueueImpl$ActionExecutionWrapper.run(AsynchronousActionExecutionQueueImpl.java:455) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.alfresco.service.cmr.avm.AVMException: 11060009 Could not connect to remote deployment receiver, transportName:default, hostName:foo.mycompany.com, port: 44100 at org.alfresco.repo.deploy.DeploymentServiceImpl.getDeploymentReceiverService(DeploymentServiceImpl.java:940) at org.alfresco.repo.deploy.DeploymentServiceImpl.deployDifferenceFS(DeploymentServiceImpl.java:1130) … 28 more

Caused by: org.springframework.remoting.RemoteLookupFailureException: Lookup of RMI stub failed; nested exception is
java.rmi.ConnectException: Connection refused to host: foo.mycompany.com; nested exception is:
java.net.ConnectException: Connection refused at org.springframework.remoting.rmi.RmiClientInterceptor.lookupStub(RmiClientInterceptor.java:215) at org.springframework.remoting.rmi.RmiClientInterceptor.prepare(RmiClientInterceptor.java:147) at
org.springframework.remoting.rmi.RmiClientInterceptor.afterPropertiesSet(RmiClientInterceptor.java:135) at org.springframework.remoting.rmi.RmiProxyFactoryBean.afterPropertiesSet(RmiProxyFactoryBean.java:68) at org.alfresco.repo.deploy.DeploymentReceiverTransportAdapterRMI.getTransport(DeploymentReceiverTransportAdapterRMI.java:41) at org.alfresco.repo.deploy.DeploymentServiceImpl.getDeploymentReceiverService(DeploymentServiceImpl.java:931) … 29 more
Caused by: java.rmi.ConnectException: Connection refused to host: foo.mycompany.com; nested exception is:
java.net.ConnectException: Connection refused at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198) at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) at
sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) at
sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) at
java.rmi.Naming.lookup(Naming.java:84) at org.springframework.remoting.rmi.RmiClientInterceptor.lookupStub(RmiClientInterceptor.java:200) …
34 more Caused by: java.net.ConnectException: Connection refused at
java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at java.net.Socket.<init>(Socket.java:372) at java.net.Socket.<init>(Socket.java:186) at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22) at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128) at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595) … 40 more

Find more posts tagged with

Comments

tvaughan77

Maybe sort of answering my own question with a RTFM, but…

This picture from the 3.4.b docs:[img]http://www.alfresco.com/help/34/community/adminhelp/images/Deployment_Subsystem.GIF[/img]

Makes me think I'm trying to do the path on the right with the port reserved for the path on the left? I….guess I'm going to try to install a new-era FSR and see if I can connect my 3.4.b web project to it.

mrogers

While it is occasionally possible to deploy "across versions", it is never a supported or recommended approach. The upgrade advice is that all the versions need to match.

And in particular 3.0 and 3.4 are incompatible.

tvaughan77

Confirmed that an Alfresco 3.4.b installation with the WCM module cannot deploy to a 3.0-vintage FSR running on a remote server but can deploy to the 3.4-vintage FSR running on that same remote server.

I was able to setup 2 separate FSRs running on the same target server:
# instance 1 running the 3.0 era FSR bound to RMI port 44100 still being deployed to by my production 3.0-labs Alfresco WCM server
# instance 2 running the 3.4 era FSR bound to RMI port 50500 that I setup as a test to be deployed to by my dev 3.4.b Alfresco WCM server.

With the magic of symlinks, I'll be able to flip from the old 3.0-era FSR to the new 3.4-era FSR when I get to the point of upgrading the production server (the /etc/init.d script I wrote should be able to start either instance).

BTW, Alfresco guys – really good job improving the installation, layout and configuration of the FSR. The 3.0 zip felt a bit like a hack, but the 3.4 installation is much, much nicer.