Bug 965130 - JBoss Fails to Start in Domain Mode on Fedora 18
Summary: JBoss Fails to Start in Domain Mode on Fedora 18
Keywords:
Status: CLOSED DUPLICATE of bug 965120
Alias: None
Product: Fedora
Classification: Fedora
Component: jboss-as
Version: 18
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Marek Goldmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-20 13:31 UTC by Mauricio Magnani Jr
Modified: 2013-05-21 10:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-21 10:42:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mauricio Magnani Jr 2013-05-20 13:31:37 UTC
Description of problem:

JBoss fails to start in domain mode.

Version-Release number of selected component (if applicable):

jboss-as.noarch 0:7.1.1-17.fc18

How reproducible:

performed the installation with the command:

$ sudo yum install jboss-as –y

Edit configuration file /etc/jboss-as/jboss-as.conf and do as below:

# The configuration you want to run
JBOSS_CONFIG=domain.xml
# The address to bind to
JBOSS_BIND=0.0.0.0

edit the file service /usr/lib/systemd/system/jboss-as.service and changing the attribute ExecStart to use the script domain.sh

ExecStart=/usr/share/jboss-as/bin/domain.sh -c $JBOSS_CONFIG -b $JBOSS_BIND

run the command to reload the service settings:

$ sudo systemctl --system daemon-reload

Restart the JBoss

$ sudo systemctl restart jboss-as.service

The exception is thrown:

INFO  [org.jboss.modules] (main) JBoss Modules version 1.1.1.GA
01:36:38,453 ERROR [stderr] (main) java.lang.IllegalStateException: JBAS015859: Could not create servers directory: /usr/share/jboss-as/domain/servers
01:36:38,456 ERROR [stderr] (main)      at org.jboss.as.host.controller.HostControllerEnvironment.<init>(HostControllerEnvironment.java:397)
01:36:38,459 ERROR [stderr] (main)      at org.jboss.as.host.controller.Main.determineEnvironment(Main.java:392)

temporary solution

Edit the file /usr/share/jboss-as/bin/domain.conf and add:

JAVA_OPTS="$JAVA_OPTS -Djboss.domain.servers.dir=/tmp"

problem solved:

jboss-as.service - The JBoss Application Server
Loaded: loaded (/usr/lib/systemd/system/jboss-as.service; disabled)
Active: active (running) since Sat, 2013-05-18 01:40:11 EDT; 36s ago
Main PID: 3279 (domain.sh)
CGroup: name=systemd:/system/jboss-as.service
â 3279 /bin/sh /usr/share/jboss-as/bin/domain.sh -c domain.xml -b 0.0.0.0
â 3317 java -D[Process Controller] -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=tru...
â 3329 java -D[Host Controller] -Dorg.jboss.boot.log.file=/usr/share/jboss-as/domain/log/host-controller.log -Dlogging.configuration=file:/usr/sh...
â 3377 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19.x86_64/jre/bin/java -D[Server:server-one] -XX:PermSize=256m -XX:MaxPermSize=256m -Xms64m -Xmx512m...
â 3392 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19.x86_64/jre/bin/java -D[Server:server-two] -XX:PermSize=256m -XX:MaxPermSize=256m -Xms64m -Xmx512m..

Actual results:

Failed to start

Expected results:

Success at startup

Comment 1 Marek Goldmann 2013-05-21 10:42:23 UTC

*** This bug has been marked as a duplicate of bug 965120 ***


Note You need to log in before you can comment on or make changes to this bug.