error connecting to jboss-admin concole [JBoss AS 7.0.2.Final "Arc"]

[dbhausen]

I have just installed JBoss AS 7.0.2.Final "Arc". Web console in not available and command line interface throws exception but does come to the command line.

tried editing jboss-admin.sh as follows but it did not help.

JAVA_OPTS="$JAVA_OPTS -Xmx950m"

[root@xxxxx bin]# ./jboss-admin.sh --connect

java.io.IOException: Cannot run program "sh": java.io.IOException: error=12, Cannot allocate memory

        at java.lang.ProcessBuilder.start(ProcessBuilder.java:459)

        at java.lang.Runtime.exec(Runtime.java:593)

        at java.lang.Runtime.exec(Runtime.java:466)

        at jline.UnixTerminal.exec(UnixTerminal.java:297)

        at jline.UnixTerminal.exec(UnixTerminal.java:282)

        at jline.UnixTerminal.stty(UnixTerminal.java:273)

        at jline.UnixTerminal.initializeTerminal(UnixTerminal.java:77)

        at jline.Terminal.setupTerminal(Terminal.java:75)

        at jline.Terminal.getTerminal(Terminal.java:26)

        at jline.ConsoleReader.<init>(ConsoleReader.java:191)

        at org.jboss.as.cli.CommandLineMain.initConsoleReader(CommandLineMain.java:529)

        at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:299)

        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.jboss.modules.Module.run(Module.java:272)

        at org.jboss.modules.Main.main(Main.java:313)

Caused by: java.io.IOException: java.io.IOException: error=12, Cannot allocate memory

        at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)

        at java.lang.ProcessImpl.start(ProcessImpl.java:65)

        at java.lang.ProcessBuilder.start(ProcessBuilder.java:452)

        ... 17 more

Connected to standalone controller at localhost:9999

[standalone@localhost:9999 /]

free memory while connected without change to JAVA_OPTS:

[root@xxxxx bin]# free

             total       used       free     shared    buffers     cached

Mem:       2097152    1650900     446252          0          0          0

-/+ buffers/cache:    1650900     446252

Swap:            0          0          0

free memory after closing:

[root@xxxx bin]# free

             total       used       free     shared    buffers     cached

Mem:       2097152     981220    1115932          0          0          0

-/+ buffers/cache:     981220    1115932

Swap:            0          0          0

[wdfink]

Looks like that java can not allocate enough memory.

Do you set -Xms?

Do you start the JBoss successful?

Can you start a different Java program in this situation?

[dbhausen]

Thanks Wolf-Dieter,

set to:

JAVA_OPTS="$JAVA_OPTS -Xms16m -Xmx32m"

Starts up ok with this setting. Not exactly sure what the optimal setting would be. However still not able to connect to web app:

http://xxx.com:9990/console

[wdfink]

Maybe your configuration is not correct or different to what you expect.

How do you install and start AS7?

Do you change the configuration? If not all connections are only available from localhost

[dbhausen]

I just downloaded the zip file, uinzipped and started with

./standalone.sh

Other than the change to jboss-admin.sh (thanks again for that) I have not changed anything.

I have a SSL certificate on this server. Do I need to do anything special because of that?

[wdfink]

If you not change the configuration and start standalone without any parameter you can only use the connections from localhost.

To use other binding you have to set:

-b <ip>

        this IP is used for all public ports like 8080

-Djboss.bind.address.management <ip>

        this IP is used for the management ports 9990 9999

as parameter when you start standalone.sh.

[dbhausen]

1. I edited  /var/jboss7/standalone/configuration/standalone.xml;
2. Accessed the web-console from my remote browser;
3. Stopped the server;
4. I then set it back so it can't be accessed by one of malicious intent.

If anyone is going to screw this server up I want it to be me. I think I am on a role now.

<!--

    <interfaces>

        <interface name="management">

            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>

      </interface>

        <interface name="public">

           <inet-address value="${jboss.bind.address:127.0.0.1}"/>

        </interface>

    </interfaces>

-->

    <interfaces>

        <interface name="management">

            <inet-address value="${jboss.bind.address.management:0.0.0.0}"/>

      </interface>

        <interface name="public">

           <inet-address value="${jboss.bind.address:0.0.0.0}"/>

        </interface>

    </interfaces>

[wdfink]

Good to hear

As I mentionend before, you might be able to set the IP without change to the config file.

If you see something like ${jboss.xyz.value:aValue} it mean that you can add the option -Djboss.xyz.value=myValue to the server (JVM start).

If there is no value set the default here will be the part after colon here 'aValue'.

[dbhausen]

I did not understand your earlier response. Yes, the following works.

If you start the server with:

./standalone.sh  -Djboss.bind.address.management=0.0.0.0

you can then access the console remotely at:

http://xxx.com:9990/console

without changing the stnadalone.xml