Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.

JBoss fails to start when deployed in Cloud enviroment


Level 1

Server specifications:

  • Windows Server 2008 R2 Standard
  • Processor: Intel (R) Xeon(R) CPU 2.6GHz 2.60 GHz
  • Installed memory (RAM): 52.0 GB (32.0 Gb usable)
  • Systems type: 64-bit OS

Adobe Experience Manager forms v 6.1.0

We have cloned our locally hosted server and deployed to a 'cloud server'. When we try to start the 'JBoss for Adobe Experience Manager forms' we get the following error:

ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public

    at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

    at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

Any ideas how to solve this issue?

3 Replies



Moving to Livecycle Forms as this is not related to Creative Cloud.

Discussion moved from Deployment for Creative Cloud for Team, Enterprise, & CS to LiveCycle Forms


Level 2

We faced a similar issue. In our case it turned out to be due to the IP references embeded in the Windows Svc for JBoss.

((these instructions are assuming that any other references to old IPs are already updated i.e. host.xml, domain.conf.bat, startLocator.bat, DB connectors under relevant config file under the Jboss/domain/configuration folder))

  1. Navigate to the JBoss directory /modules/system/layers/base/native/sbin
  2. In the service.bat file you might find further references which might still point to the IPs from your on-premise setup.
  3. After moving the servers to the cloud, make sure that all the IPs in this file are updated.

Now you must rebuild the windows service for Jboss. Or you can simply create a new service (that's what we did)

  1. Before creating a new svc, in the service.bat file update the values for SHORTNAME, DISPLAYNAME and DESCRIPTION,, since a svc with these properties already exists.
  2. After making the changes, simply open cmd prmpt and execute :    <service.bat install>
  3. open services.msc and you will notice a second Jboss svc will be created.
  4. Test the new svc, and once everything appears fine, you can disable and remove the old svc.