0 Replies Latest reply on Aug 26, 2014 6:49 PM by Steve Cohen

    Can't get domain model working in EAP 6.2

    Steve Cohen Newbie

      I am prototyping a port of a system from WebLogic to JBoss.

       

      I'd originally started with the standalone model and that was easy enough.

       

      Now I've had to change to working with the domain model and weird things are happening.  Even though everything I've deployed can be displayed on the server using curl, it doesn't work remotely and I believe we've ruled out firewalls as the issue.

       

      One other point is worth mentioning.  On the temporary prototype server, Tomcat is also running something else and using port 8080.  This means that for my standalone server, I've had to add this to the configuration:

       

      <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:100}">.

       

      This makes the default web port 8180 and the default admin console port 10090.

       

      For the domain model, I modified the host.xml to define server-one with <socket-bindings port-offset="100"/>, server-two with <socket-bindings port-offset="200"/> and server-three with <socket-bindings port-offset="300"/>.  For this model we can leave the admin console port at 9990.

       

      I haven't got around to deploying database config, or applications on the domain model yet.  But I have put some Tattletale output (a directory tree of styled html files) into {JBOSS_EAP_HOME}/welcome-content.  This is renderable in the standalone model and should be renderable as well in the domain model.

       

      But I find the following:

      1) I cannot access the admin console at http://{ip of server}:9990/console/index.html .  However, from the server,

      curl http://localhost:9990/console/index.html shows the expected output.

       

      2) The output of http://{ip of server}:8180/index.html on the standalone server is the expected styled tattletale output and all of the links to other pages work. 

      When instead, I have the domain server running, at http://{ip of server}:8180/index.html, I see unstyled tattletale output (meaning the stylesheet can't be read) and none of the links on the page work.

       

      This seems like it should be a giant clue but I don't know what it means.

       

      Is there something else I need to do to get the domain model working right?  Is there better documentation than the official docs about domain model that would tell me.  I've looked at the official docs and haven't found what I needed.

       

      Thanks.