[JBoss JIRA] (WFLY-3900) Unable to inject EJB Context into CDI Interceptor
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3900?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3900:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1149644|https://bugzilla.redhat.com/show_bug.cgi?id=1149644] from MODIFIED to ON_QA
> Unable to inject EJB Context into CDI Interceptor
> -------------------------------------------------
>
> Key: WFLY-3900
> URL: https://issues.jboss.org/browse/WFLY-3900
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 9.0.0.Alpha1
> Reporter: Brad Maxwell
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Beta1
>
> Attachments: inject-ejb-context-into-cdi-interceptor.jar, server.log
>
>
> CDI Interceptor cannot inject EJB session context.
> If the Interceptor is changed to EJB interceptor by removing the @Interceptor on the interceptor and removing it from the beans.xml, and adding @Interceptors(...) to the EJB, then it is able to inject.
> See attached reproducer with source and log file.
> private @Resource SessionContext sessionContext;
> Caused by: javax.naming.NameNotFoundException: env/test.ServiceLoggedInterceptor/sessionContext -- service jboss.naming.context.java.comp.inject-ejb-context-into-cdi-interceptor.inject-ejb-context-into-cdi-interceptor.HelloEJB.env."test.ServiceLoggedInterceptor".sessionContext
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51]
> at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185)
> ... 127 more
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFCORE-205) ManagedDMRContentTypeResource does not use a map with consistent ordering for storing content
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-205?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-205:
------------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1078062|https://bugzilla.redhat.com/show_bug.cgi?id=1078062] from MODIFIED to ON_QA
> ManagedDMRContentTypeResource does not use a map with consistent ordering for storing content
> ---------------------------------------------------------------------------------------------
>
> Key: WFCORE-205
> URL: https://issues.jboss.org/browse/WFCORE-205
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha10
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Alpha11
>
>
> ManagedDMRContentTypeResource.content is used for generating an overall hash for the stored content, but it does not use consistent ordering (i.e. it needs to be a LinkedHashMap or perhaps a TreeMap.) The result is when another node in the domain receives an update it may calculate a different overall hash.
> This is surfacing as failures in https://bugzilla.redhat.com/show_bug.cgi?id=1078062 when the master and slave are running on different JVM releases. Different VM releases often have different ordering behavior when iterating over the unordered collections.
> I believe this is unlikely to result in real-world problems since any backup will persist its own version of the hash to its local copy of domain.xml, so there won't be any mismatch. The importance of the overall hash is that it allows the process to find the content in the repo when it is added.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFCORE-214) Missing jboss-threads in jboss-cli-client.jar
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-214?page=com.atlassian.jira.plugin... ]
Brian Stansberry closed WFCORE-214.
-----------------------------------
Resolution: Done
It's there. Never mind.
> Missing jboss-threads in jboss-cli-client.jar
> ---------------------------------------------
>
> Key: WFCORE-214
> URL: https://issues.jboss.org/browse/WFCORE-214
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
>
> The client jar jboss-cli-client.jar is missing the org.jboss.threads classes, even though those are a dep of ModelControllerClient.
> Perhaps the CLI's call paths don't use those classes, but that's an accident waiting to happen, plus it prevents use of this jar as a general purpose management client, when otherwise it could be used that way.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFCORE-214) Missing jboss-threads in jboss-cli-client.jar
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-214:
---------------------------------------
Summary: Missing jboss-threads in jboss-cli-client.jar
Key: WFCORE-214
URL: https://issues.jboss.org/browse/WFCORE-214
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The client jar jboss-cli-client.jar is missing the org.jboss.threads classes, even though those are a dep of ModelControllerClient.
Perhaps the CLI's call paths don't use those classes, but that's an accident waiting to happen, plus it prevents use of this jar as a general purpose management client, when otherwise it could be used that way.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFLY-1077) JDK ORB Subsystem
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-1077?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski commented on WFLY-1077:
--------------------------------------
JBoss EAP (Jacorb) <-> Wildfly (IIOP-OpenJDK) compatibility test
Configuration:
Web application consisting of secure servlet and transactional EJB deployed on server A.
EAR with transaction EJB deployed on server B.
Execution:
1. User opens web browser and authenicates using basic logging.
2. Bean on server A authenticates Principal.
3. Bean on server A starts JTS transaction.
4. Bean on server A invokes remotely (using iiop) bean on server B.
5. Bean on server B authenicates Principal.
6. Bean on server B checks that transaction is present.
Result:
I have run the test in both jboss-eap=A;wildfly=B and jboss-eap=B;wildfly=A configuration.
In both cases SASContext and transaction context are propagated correctly.
Principal and transaction are propagated to bean B.
> JDK ORB Subsystem
> -----------------
>
> Key: WFLY-1077
> URL: https://issues.jboss.org/browse/WFLY-1077
> Project: WildFly
> Issue Type: Feature Request
> Components: IIOP
> Reporter: Dimitris Andreadis
> Assignee: Tomasz Adamski
>
> Implement a JDK ORB subsystem that can act as a replacement for the JacORB subsystem.
> AFAIK, most/all JDK ORBs are based on the Sun ORB.
> Ideally the 2 ORBs (JDK & JacORB) would be both supported in case we need to go through a transition period, or we need to support a particular interop scenario for which interop communication has issues.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFCORE-213) Clean unreferenced items from the content repository
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-213?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet updated WFCORE-213:
-------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/284 (was: https://github.com/wildfly/wildfly-core/pull/237)
> Clean unreferenced items from the content repository
> ----------------------------------------------------
>
> Key: WFCORE-213
> URL: https://issues.jboss.org/browse/WFCORE-213
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Fix For: 1.0.0.Alpha11, 1.0.0.Beta1
>
>
> The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example:
> 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed.
> 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed.
> Note that the content repository can include things other than deployments. Currently it also includes management-client-content (specifically rollout plans) and can potentially include anything. This is why it's a "content repository" and not a "deployment repository." The solution for this needs to deal with all cases.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFLY-4044) Wildfly service will not start on fedora 20 - 64 bit
by Karl Nicholas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4044?page=com.atlassian.jira.plugin.... ]
Karl Nicholas commented on WFLY-4044:
-------------------------------------
I reinstalled Fedora, updated, and installed Wildfly 8.1.0.Final and ran it only with "sudo systemctl start wildfly" and it seems to be running fine. Not being able to run it standalone seems like a warning that should be pretty clearly stated somewhere obvious. Anyway, thanks for the assistance, I recommend closing this issue.
> Wildfly service will not start on fedora 20 - 64 bit
> ----------------------------------------------------
>
> Key: WFLY-4044
> URL: https://issues.jboss.org/browse/WFLY-4044
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.1.0.Final
> Environment: Fedora 20 - updates installed
> Reporter: Karl Nicholas
> Assignee: Marek Goldmann
>
> standalone.sh starts wildfly ok but systemctl start service fails:
> [root@localhost system]# yum install wildfly
> Loaded plugins: langpacks, refresh-packagekit
> Package wildfly-8.1.0-3.fc20.noarch already installed and latest version
> Nothing to do
> [root@localhost system]# systemctl start wildfly
> [root@localhost system]# systemctl status wildfly
> wildfly.service - The WildFly Application Server
> Loaded: loaded (/usr/lib/systemd/system/wildfly.service; disabled)
> Active: failed (Result: exit-code) since Sat 2014-11-01 15:50:40 PDT; 5s ago
> Process: 7658 ExecStart=/usr/share/wildfly/bin/launch.sh $WILDFLY_MODE $WILDFLY_CONFIG $WILDFLY_BIND (code=exited, status=1/FAILURE)
> Main PID: 7658 (code=exited, status=1/FAILURE)
> Nov 01 15:50:39 localhost.localdomain systemd[1]: Started The WildFly Application Server.
> Nov 01 15:50:40 localhost.localdomain systemd[1]: wildfly.service: main process exited, code=exited, status=1/FAILURE
> Nov 01 15:50:40 localhost.localdomain systemd[1]: Unit wildfly.service entered failed state.
> [root@localhost system]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFLY-4044) Wildfly service will not start on fedora 20 - 64 bit
by Karl Nicholas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4044?page=com.atlassian.jira.plugin.... ]
Karl Nicholas edited comment on WFLY-4044 at 11/3/14 12:31 PM:
---------------------------------------------------------------
Well, are you saying that since I ran wildfly in standalone mode it breaks the systemctl mode? That kinda sucks. Can I uninstall it and reinstall it?
journalctl: Nov 03 07:38:33 localhost.localdomain systemd[1]: Starting The WildFly Application Server...
Nov 03 07:38:33 localhost.localdomain systemd[1]: Started The WildFly Application Server.
Nov 03 07:38:40 localhost.localdomain systemd[1]: wildfly.service: main process exited, code=exited, status=1/FAILURE
Nov 03 07:38:40 localhost.localdomain systemd[1]: Unit wildfly.service entered failed state
was (Author: karlnicholas):
Well, are you saying that since I ran wildfly in standalone mode it breaks the systemctl mode? That kinda sucks. Can I uninstall it and reinstall it?
journalctl: Nov 03 07:38:33 localhost.localdomain systemd[1]: Starting The WildFly Application Server...
Nov 03 07:38:33 localhost.localdomain systemd[1]: Started The WildFly Application Server.
Nov 03 07:38:40 localhost.localdomain systemd[1]: wildfly.service: main process exited, code=exited, status=1/FAILURE
Nov 03 07:38:40 localhost.localdomain systemd[1]: Unit wildfly.service entered failed state
server.log:
2014-11-01 14:56:05,899 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
2014-11-01 14:56:06,279 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
2014-11-01 14:56:06,399 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.1.0.Final "Kenny" starting
2014-11-01 14:56:06,410 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties:
[Standalone] =
awt.toolkit = sun.awt.X11.XToolkit
file.encoding = UTF-8
file.encoding.pkg = sun.io
file.separator = /
java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.print.PSPrinterJob
java.class.path = /usr/share/wildfly/jboss-modules.jar
java.class.version = 51.0
java.endorsed.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/endorsed
java.ext.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
java.home = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre
java.io.tmpdir = /tmp
java.library.path = /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.net.preferIPv4Stack = true
java.runtime.name = OpenJDK Runtime Environment
java.runtime.version = 1.7.0_71-mockbuild_2014_10_15_17_02-b00
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.7
java.util.logging.manager = org.jboss.logmanager.LogManager
java.vendor = Oracle Corporation
java.vendor.url = http://java.oracle.com/
java.vendor.url.bug = http://bugreport.sun.com/bugreport/
java.version = 1.7.0_71
java.vm.info = mixed mode
java.vm.name = OpenJDK 64-Bit Server VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.7
java.vm.vendor = Oracle Corporation
java.vm.version = 24.65-b04
javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
jboss.home.dir = /usr/share/wildfly
jboss.host.name = localhost
jboss.modules.dir = /usr/share/wildfly/modules
jboss.modules.system.pkgs = org.jboss.byteman
jboss.node.name = localhost
jboss.qualified.host.name = localhost.localdomain
jboss.server.base.dir = /usr/share/wildfly/standalone
jboss.server.config.dir = /usr/share/wildfly/standalone/configuration
jboss.server.data.dir = /usr/share/wildfly/standalone/data
jboss.server.deploy.dir = /usr/share/wildfly/standalone/data/content
jboss.server.log.dir = /usr/share/wildfly/standalone/log
jboss.server.name = localhost
jboss.server.persist.config = true
jboss.server.temp.dir = /usr/share/wildfly/standalone/tmp
line.separator =
logging.configuration = file:/usr/share/wildfly/standalone/configuration/logging.properties
module.path = /usr/share/wildfly/modules
org.jboss.boot.log.file = /usr/share/wildfly/standalone/log/server.log
org.jboss.resolver.warning = true
org.xml.sax.driver = __redirected.__XMLReaderFactory
os.arch = amd64
os.name = Linux
os.version = 3.16.6-203.fc20.x86_64
path.separator = :
sun.arch.data.model = 64
sun.boot.class.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/classes
sun.boot.library.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/amd64
sun.cpu.endian = little
sun.cpu.isalist =
sun.io.unicode.encoding = UnicodeLittle
sun.java.command = /usr/share/wildfly/jboss-modules.jar -mp /usr/share/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/usr/share/wildfly -Djboss.server.base.dir=/usr/share/wildfly/standalone
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = UTF-8
sun.management.compiler = HotSpot 64-Bit Tiered Compilers
sun.os.patch.level = unknown
user.country = US
user.dir = /usr/share/wildfly/bin
user.home = /root
user.language = en
user.name = root
user.timezone = America/Los_Angeles
2014-11-01 14:56:06,414 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -agentpath:/usr/lib64/libabrt-java-connector.so=abrt=on -D[Standalone] -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/usr/share/wildfly/standalone/log/server.log -Dlogging.configuration=file:/usr/share/wildfly/standalone/configuration/logging.properties
2014-11-01 14:56:07,675 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
2014-11-01 14:56:07,701 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.2.2.Final
2014-11-01 14:56:07,715 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.2.2.Final
2014-11-01 14:56:07,768 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
2014-11-01 14:56:07,773 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
2014-11-01 14:56:07,791 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
2014-11-01 14:56:07,792 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
2014-11-01 14:56:07,817 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
2014-11-01 14:56:07,825 INFO [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
2014-11-01 14:56:07,827 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.3.Final
2014-11-01 14:56:07,856 INFO [org.jboss.as.security] (MSC service thread 1-7) JBAS013170: Current PicketBox version=4.0.21.Beta1
2014-11-01 14:56:07,874 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
2014-11-01 14:56:07,891 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
2014-11-01 14:56:07,892 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
2014-11-01 14:56:07,908 INFO [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)
2014-11-01 14:56:07,919 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = h2
2014-11-01 14:56:07,939 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
2014-11-01 14:56:08,000 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017502: Undertow 1.0.15.Final starting
2014-11-01 14:56:08,008 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.0.15.Final starting
2014-11-01 14:56:08,470 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path /usr/share/wildfly/welcome-content
2014-11-01 14:56:08,477 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017525: Started server default-server.
2014-11-01 14:56:08,508 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017531: Host default-host starting
2014-11-01 14:56:08,584 WARN [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015506: Cannot load WS deployment aspects from /META-INF/stack-specific-deployment-aspects.xml
2014-11-01 14:56:08,638 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
2014-11-01 14:56:08,714 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.0.Final
2014-11-01 14:56:08,934 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
2014-11-01 14:56:09,004 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory /usr/share/wildfly/standalone/deployments
2014-11-01 14:56:09,006 ERROR [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-5) JBAS015102: Unable to load console module for slot main, disabling console
2014-11-01 14:56:09,252 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
2014-11-01 14:56:09,254 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
2014-11-01 14:56:09,255 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 3762ms - Started 184 of 233 services (81 services are lazy, passive or on-demand)
2014-11-01 14:56:16,022 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
2014-11-01 14:56:16,025 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017532: Host default-host stopping
2014-11-01 14:56:16,034 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010418: Stopped Driver service with driver-name = h2
2014-11-01 14:56:16,038 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017521: Undertow HTTP listener default suspending
2014-11-01 14:56:16,039 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017520: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080
2014-11-01 14:56:16,041 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017506: Undertow 1.0.15.Final stopping
2014-11-01 14:56:16,052 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015950: WildFly 8.1.0.Final "Kenny" stopped in 40ms
2014-11-01 15:06:09,117 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
2014-11-01 15:11:07,061 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
2014-11-01 15:11:45,931 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
2014-11-01 15:15:58,565 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
2014-11-01 15:16:56,941 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
2014-11-01 15:17:03,849 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
> Wildfly service will not start on fedora 20 - 64 bit
> ----------------------------------------------------
>
> Key: WFLY-4044
> URL: https://issues.jboss.org/browse/WFLY-4044
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.1.0.Final
> Environment: Fedora 20 - updates installed
> Reporter: Karl Nicholas
> Assignee: Marek Goldmann
>
> standalone.sh starts wildfly ok but systemctl start service fails:
> [root@localhost system]# yum install wildfly
> Loaded plugins: langpacks, refresh-packagekit
> Package wildfly-8.1.0-3.fc20.noarch already installed and latest version
> Nothing to do
> [root@localhost system]# systemctl start wildfly
> [root@localhost system]# systemctl status wildfly
> wildfly.service - The WildFly Application Server
> Loaded: loaded (/usr/lib/systemd/system/wildfly.service; disabled)
> Active: failed (Result: exit-code) since Sat 2014-11-01 15:50:40 PDT; 5s ago
> Process: 7658 ExecStart=/usr/share/wildfly/bin/launch.sh $WILDFLY_MODE $WILDFLY_CONFIG $WILDFLY_BIND (code=exited, status=1/FAILURE)
> Main PID: 7658 (code=exited, status=1/FAILURE)
> Nov 01 15:50:39 localhost.localdomain systemd[1]: Started The WildFly Application Server.
> Nov 01 15:50:40 localhost.localdomain systemd[1]: wildfly.service: main process exited, code=exited, status=1/FAILURE
> Nov 01 15:50:40 localhost.localdomain systemd[1]: Unit wildfly.service entered failed state.
> [root@localhost system]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months