Databases
StackOverflow2013
Postsdbo
PODeploy web app on JBoss AS 7 running on CentOS
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODeploy web app on JBoss AS 7 running on CentOS
    primarykey
    data
    text
    <p>Maybe this question is already asked, but I couldn't find. </p> <p>This is my first time, when I am launching a web app. I have a java web application that I want to deploy on JBoss AS 7 that is running on CentOS. I have configured standalone.xml with interface and standard sockets. I have opened ports in iptables. JBoss starts normally. Problem is that I can't access it from the internet. What else do I need?</p> <p>Here is my parts of standalone.xml</p> <p>interfaces:</p> <pre><code>&lt;interfaces&gt; &lt;interface name="management"&gt; &lt;inet-address value="${jboss.bind.address.management:127.0.0.1}"/&gt; &lt;/interface&gt; &lt;interface name="public"&gt; &lt;inet-address value="${jboss.bind.address:myIP}"/&gt; &lt;/interface&gt; &lt;/interfaces&gt; </code></pre> <p>standard sockets</p> <pre><code>&lt;socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"&gt; &lt;socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/&gt; &lt;socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/&gt; &lt;socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/&gt; &lt;socket-binding name="ajp" port="8009"/&gt; &lt;socket-binding name="http" port="9090"/&gt; &lt;socket-binding name="https" port="8443"/&gt; &lt;socket-binding name="osgi-http" interface="management" port="8090"/&gt; &lt;socket-binding name="remoting" port="4447"/&gt; &lt;socket-binding name="txn-recovery-environment" port="4712"/&gt; &lt;socket-binding name="txn-status-manager" port="4713"/&gt; &lt;outbound-socket-binding name="mail-smtp"&gt; &lt;remote-destination host="localhost" port="25"/&gt; &lt;/outbound-socket-binding&gt; &lt;/socket-binding-group&gt; </code></pre> <p>P.S I am deploying remotely.</p> <p><strong>Edit</strong></p> <p>P.S.S I have turned off the firewall. Still can't access.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStuazku
    1. UStuazku
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COstart jboss with binding on all IPs using jboss -b 0.0.0.0 and I think you should be through
      singulars
      1. PODeploy web app on JBoss AS 7 running on CentOS
      1. USSatya
    2. CO@Satya - No it's not working. iptables should be like this: ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:9090
      singulars
      1. PODeploy web app on JBoss AS 7 running on CentOS
      1. UStuazku
    3. COyour configuration looks ok. Are you sure you entered correct ip? Is jboss root available from localhost (http://127.0.0.1:9090)? Also you can try replace `<inet-address value="${jboss.bind.address:myIP}"/>` with `<any-address />`
      singulars
      1. PODeploy web app on JBoss AS 7 running on CentOS
      1. USsimkam
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload