Install WildFly 9 failing to start
by Arun Gupta
Built the trunk using "mvn package"
Unzipped "target/wildfly-9.0.0.Alpha1-SNAPSHOT"
Started WildFly as "bin/standalone.sh"
Got the following error:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0
14:41:31,218 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.4.Final
14:41:31,681 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
14:41:31,748 INFO [org.jboss.as] (MSC service thread 1-5)
WFLYSRV0049: WildFly 1.0.0.Alpha5 "Kenny" starting
14:41:32,057 ERROR [org.jboss.as.server] (Controller Boot Thread)
WFLYSRV0055: Caught exception during boot:
org.jboss.as.controller.persistence.ConfigurationPersistenceException:
WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.as.server.ServerService.boot(ServerService.java:343)
[wildfly-server-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:260)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to
load module org.jboss.as.clustering.infinispan
at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:155)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:435)
[wildfly-server-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145)
[wildfly-server-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107)
[wildfly-server-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
[staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
[staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
... 3 more
Caused by: java.util.concurrent.ExecutionException:
javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load
module
at java.util.concurrent.FutureTask.report(FutureTask.java:122) [rt.jar:1.8.0]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) [rt.jar:1.8.0]
at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:147)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
... 9 more
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to
load module
at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:196)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.as.controller.parsing.ExtensionXml.access$000(ExtensionXml.java:69)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:127)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:124)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[rt.jar:1.8.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[rt.jar:1.8.0]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.1.1.Final.jar:2.1.1.Final]
Caused by: org.jboss.modules.ModuleLoadException: Error loading module
from /Users/arungupta/tools/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/as/clustering/infinispan/main/module.xml
at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:154)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:131)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.LocalModuleFinder$1.run(LocalModuleFinder.java:154)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.LocalModuleFinder$1.run(LocalModuleFinder.java:148)
[jboss-modules.jar:1.3.4.Final]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0]
at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:148)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:456)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:359)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:306)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:238)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:178)
[wildfly-controller-1.0.0.Alpha5.jar:1.0.0.Alpha5]
... 8 more
Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to
resolve artifact
'org.wildfly:wildfly-clustering-infinispan:9.0.0.Alpha1-SNAPSHOT'
(position: END_TAG seen
...org.wildfly:wildfly-clustering-infinispan:9.0.0.Alpha1-SNAPSHOT"/>...
@35:91)
at org.jboss.modules.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:752)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:647)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:445)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:264)
[jboss-modules.jar:1.3.4.Final]
at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:152)
[jboss-modules.jar:1.3.4.Final]
... 18 more
14:41:32,061 FATAL [org.jboss.as.server] (Controller Boot Thread)
WFLYSRV0056: Server boot has failed in an unrecoverable manner;
exiting. See previous messages for details.
14:41:32,073 INFO [org.jboss.as] (MSC service thread 1-6)
WFLYSRV0050: WildFly 1.0.0.Alpha5 "Kenny" stopped in 7ms
Do I need to install
feature-pack/target/wildfly-9.0.0.Alpha1-SNAPSHOT.zip ? How ?
Arun
--
http://blog.arungupta.me
http://twitter.com/arungupta
11 years, 12 months
Re: [wildfly-dev] Domain Overview design
by Liz Clayton
Hi,
----- Original Message -----
> From: wildfly-dev-request(a)lists.jboss.org
> To: wildfly-dev(a)lists.jboss.org
...
> ------------------------------
>
> Message: 8
> Date: Mon, 11 Aug 2014 22:41:51 +0200
> From: "Heiko W.Rupp" <hrupp(a)redhat.com>
> Subject: Re: [wildfly-dev] Domain Overview design
> To: WildFly Dev <wildfly-dev(a)lists.jboss.org>
> Message-ID: <E5287A20-C00A-4D5D-BC59-8D52A3F9EA3B(a)redhat.com>
> Content-Type: text/plain; charset=windows-1252
>
>
> Am 11.08.2014 um 22:09 schrieb Liz Clayton <lclayton(a)redhat.com>:
>
> >> http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002360.html
> >
> > Thanks for sending this pointer! I read through the thread and have a few
> > more questions:
> > - Sounds like there are some terminology issues to reconcile as part of
> > this?
> > - Should these shutdown states be represented in the visualization? If so,
> > do you think they should be represented as:
> > * A graduated scale of availability (shades of yellow/orange), to reflect
> > the various states of suspension or ?out of sync? ness?
> > - or -
> > * A single ?out of sync? (suspended?) state? If that were the case, perhaps
> > ?out of sync? could be represented as an intermediate (yellow/orange)
> > state between green and red. Details about the state could be presented in
> > a hover overlay, with a link to perform the action needed ("restart" for
> > example).
>
> I think the latter is the better, as both *_REQUIRED states are effectively
> still RUNNING, but with
> a configuration which is not the latest.
Great to know, thanks! I'll mockup future iterations with the latter, a single out of sync/yellow state.
> In RHQ we currently have UP/DOWN/UNKNOWN/ADMIN_DOWN (*) and are thinking of
> extending this to
>
> UP: Resource is available and working normally
> DOWN: Resource is at fault and not working normally
> MAINTENANCE: There is a scheduled maintenance period, availability may be UP
> or DOWN
> MISSING: The resource was recorded in inventory, but does not exist in
> reality (e.g. was deleted on file system)
> ADMIN_DOWN/DISABLED: The resource exists, but was disabled by the admin (e.g.
> a network interface on a 8 port card where only 1 cable is connected)
> UNKNOWN: Resource state can not be determined
>
> and also MIXED for groups of resources.
>
>
> *) e.g. a network interface exists, but has no cable connected on purpose
Thanks for the list of terms! I'm trying to understand the various terms used for availability monitoring.
Best,
Liz
12 years
jboss cli auth failure
by Claudio Miranda
Hi, just updated to latest in wildfly repo, started standalone and
tried to connect with an username, it fails
./jboss-cli.sh -c --user=admin
SaslException: Authentication failed: the server presented no
authentication mechanisms
It works with local authentication
./jboss-cli.sh -c
Users admin is added as
./add-user.sh -u admin -p admin123@
Also, it fails with ssl in management interface.
Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect
to https-remoting://localhost:9993. The connection failed
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
at
...
Caused by: java.nio.channels.ClosedChannelException
I configured ssl as described in [1]
1. http://claudius.com.br/2014/08/protect-wildfly-management-interface/
--
Claudio Miranda
claudio(a)claudius.com.br
http://www.claudius.com.br
12 years
build failure
by Claudio Miranda
Hi, just updated to latest of wildfly repo, there is a failing test
testDeploymentStreamApi(org.jboss.as.test.smoke.mgmt.servermodule.ServerInModuleDeploymentTestCase)
Time elapsed: 0.44 sec <<< FAILURE!
java.lang.AssertionError:
expected:<[fa0bc3e6f9cf0ca559f1ff45ffbac6e62c23d556,
fa128b7874e7ac4b155aa5f265d4eebbde471d3d]> but
was:<[fa0bc3e6f9cf0ca559f1ff45ffbac6e62c23d556]>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.jboss.as.test.smoke.mgmt.servermodule.ServerInModuleDeploymentTestCase.testDeployments(ServerInModuleDeploymentTestCase.java:614)
at org.jboss.as.test.smoke.mgmt.servermodule.ServerInModuleDeploymentTestCase.testDeploymentStreamApi(ServerInModuleDeploymentTestCase.java:93)
--
Claudio Miranda
claudio(a)claudius.com.br
http://www.claudius.com.br
12 years
Core and Full out of sync
by Stan Silvert
Build the latest WildFly Core master.
In WildFly Full master, change the root pom to use latest core:
<version.org.wildfly.core>1.0.0.Alpha5-SNAPSHOT</version.org.wildfly.core>
When you build full, you will get:
[WARNING] Rule 0:
org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with
message:
org.wildfly:wildfly-web-build:pom:9.0.0.Alpha1-SNAPSHOT
org.wildfly.core:wildfly-core-build:zip:1.0.0.Alpha5-SNAPSHOT:compile
has transitive dependencies:
org.wildfly.core:wildfly-launcher:jar:1.0.0.Alpha5-SNAPSHOT:compile
If you exclude the wildfly-launcher dependency, the build gets even uglier.
Should these two builds stay in sync somehow? For some features, we
need to be able to make changes to both builds at the same time and see
them work together.
Stan
12 years
Switching ARQ to the Launcher API
by James R. Perkins
In case anyone missed it there is a new launcher API in WildFly Core
(https://github.com/wildfly/wildfly-core/tree/master/launcher). It's
already being used for launching a standalone instance and a domain
instance in the core test suite. Once there is a new core release I'll
also use it in the maven plugin and in the new (barely started) Gradle
plugin.
I'm also thinking of changing Arquillian in WildFly to use the API
rather than the custom process launching it does now. I thought I post
this to the list to see if there are any objections or concerns with
doing this.
--
James R. Perkins
JBoss by Red Hat
12 years
What should the EJB3 StatefulSessionSynchronizationInterceptor.processInvocation() do for transactions that are already committed or rolled back
by Scott Marlow
I created WFLY-3731 for a "No transaction is running" ISE [1], that is
thrown when
org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation()
checks if the current transaction is not null and not STATUS_COMMITTED.
One obvious fix for WFLY-3731, would be to change
StatefulSessionSynchronizationInterceptor.processInvocation() to also
check for STATUS_ROLLEDBACK which would help my current case. Doing so
might defer clearing the transaction from the current thread, until we
later reached EJB container code (not really sure though, if we will
clear the ended tx).
But, what does it mean exactly for
StatefulSessionSynchronizationInterceptor.processInvocation() to see an
ended transaction? Seems to me that we missed our chance to register
the StatefulSessionSynchronization, so we won't run the
StatefulSessionSynchronization.beforeCompletion() and
StatefulSessionSynchronization.afterCompletion() methods which I think
skips other logic (beforeCompletionMethod/afterCompletionMethod).
Currently, it looks like we just continue with the invocation as if
there is no current transaction (SFSB level lock appears to be released
after the invocation instead of after the transaction ends). Which
makes some sense since the transaction already ended.
When running the test case [2], I also see a JPA (EE) container level
failure as well which is reported as WFLY-3730.
Scott
[1] http://fpaste.org/125252 show the exception that I see when the
transaction times out in a background (tm reaper) thread.
[2] test case is pushed to
https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut
12 years
