Good morning,
While attempting to install and startup Wildfly under F23, I encountered several packaging errors.
They are shown in https://bugzilla.redhat.com/show_bug.cgi?id=1226991.
I did apply the "fix" shown in comment #1 and comment #2.
Now Wildfly does start using "standalone.sh", but I get the following stacktrace:
11:13:18,174 ERROR [org.jboss.msc.service.fail] (MSC service thread 1- 2) MSC000001: Failed to start service jboss.ws.endpoint- config.Recording-Endpoint-Config: org.jboss.msc.service.StartException in service jboss.ws.endpoint-config.Recording-Endpoint-Config: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContro llerImpl.java:1904) [jboss-msc.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.ja va:1142) [rt.jar:1.8.0_65] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.j ava:617) [rt.jar:1.8.0_65] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65] Caused by: java.lang.NoSuchMethodError: org.jboss.wsf.spi.metadata.config.EndpointConfig: method <init>()V not found at org.jboss.as.webservices.service.ConfigService.start(ConfigService.java :65) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(Serv iceControllerImpl.java:1948) [jboss-msc.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceContro llerImpl.java:1881) [jboss-msc.jar:1.2.2.Final] ... 3 more
A little later in the log it says: 11:13:20,072 ERROR [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-2) JBAS015102: Unable to load console module for slot main, disabling console 11:13:20,078 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 11:13:20,771 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 11:13:20,866 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.ws.client-config.Standard-Client-Config: org.jboss.msc.service.StartException in service jboss.ws.client- config.Standard-Client-Config: Failed to start service service jboss.ws.endpoint-config.Standard-Endpoint-Config: org.jboss.msc.service.StartException in service jboss.ws.endpoint- config.Standard-Endpoint-Config: Failed to start service service jboss.ws.endpoint-config.Recording-Endpoint-Config: org.jboss.msc.service.StartException in service jboss.ws.endpoint- config.Recording-Endpoint-Config: Failed to start service
Wildfly seems to run as it answers web requests, but I cannot seem to deploy the helloworld quickstart. #mvn wildfly:deploy
[INFO] ---------------------------------------------------------------- -------- [INFO] BUILD FAILURE [INFO] ---------------------------------------------------------------- -------- [INFO] Total time: 8.124 s [INFO] Finished at: 2016-01-23T11:13:51-06:00 [INFO] Final Memory: 19M/281M [INFO] ---------------------------------------------------------------- -------- [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven- plugin:1.1.0.Alpha5:deploy (default-cli) on project jboss-helloworld: Please make sure a server is running before executing goal deploy on deployment /home/jwhimpel/Downloads/jboss-eap-quickstarts- 6.4.0.GA/helloworld/target/jboss-helloworld.war. Reason: java.net.ConnectException: WFLYPRT0053: Could not connect to http- remoting://192.168.1.188:9990. The connection failed: Connection refuse d -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/Conne ctException
Could the two be related?
I am using wildfly-8.1.0.3, I see "ausil" and "goldmann" have submitted subsequent builds for wilfly but are marked ad "Failed" in koji. What needs to be done to get a working package of wildfire into Fedora? I am not a packager, but am willing to test and assist in any manner that I can.
PS: Attempting to start Wildfly using systemd yields: #systemctl enable wildfly #systemctl start wildfly #journalctl --lines 10 Jan 23 11:35:24 dubby.jlhimpel.net systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount is masked. Jan 23 11:35:24 dubby.jlhimpel.net systemd[1]: Started The WildFly Application Server. Jan 23 11:35:24 dubby.jlhimpel.net systemd[1]: Starting The WildFly Application Server... Jan 23 11:35:24 dubby.jlhimpel.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=wildfl Jan 23 11:35:26 dubby.jlhimpel.net polkitd[1066]: Unregistered Authentication Agent for unix-process:22770:36862048 (system bus name :1.451, object pat Jan 23 11:35:26 dubby.jlhimpel.net systemd[1]: wildfly.service: Main process exited, code=exited, status=1/FAILURE Jan 23 11:35:26 dubby.jlhimpel.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=wildfly Jan 23 11:35:26 dubby.jlhimpel.net systemd[1]: wildfly.service: Unit entered failed state. Jan 23 11:35:26 dubby.jlhimpel.net systemd[1]: wildfly.service: Failed with result 'exit-code'.
Thanks for listening.
John
On 23 January 2016 at 17:45, John W. Himpel john@jlhimpel.net wrote:
Good morning,
While attempting to install and startup Wildfly under F23, I encountered several packaging errors.
Wildfly in Fedora is in not a very good condition these days, please read this post from last year: https://lists.stg.fedoraproject.org/archives/list/java-devel@lists.stg.fedor...
In the short term, you may have better luck with Marek's COPR repo: https://copr.fedorainfracloud.org/coprs/goldmann/wildfly/
I am using wildfly-8.1.0.3, I see "ausil" and "goldmann" have
submitted subsequent builds for wilfly but are marked ad "Failed" in koji. What needs to be done to get a working package of wildfire into Fedora?
To be honest, it needs someone to step up and help maintain it. Since Java people here tend to be stretched pretty thinly, if you'd like to become a packager and help out that would be most welcome!
java-devel@lists.fedoraproject.org