[JBoss JIRA] (WFLY-9427) JDBC_PING gets a NameNotFoundException when using jndi resource
by Alessandro Moscatelli (JIRA)
[ https://issues.jboss.org/browse/WFLY-9427?page=com.atlassian.jira.plugin.... ]
Alessandro Moscatelli updated WFLY-9427:
----------------------------------------
Description:
JDBC_PING if configured with jndi resources will cause :
IllegalArgumentException: Could not lookup datasource
NameNotFoundException
IllegalStateException
The same jndi resource is correctly found and used by a deployed application.
It seems the jndi resouce is not ready, yet, when JGROUPS needs it.
{quote}2017-10-09 17:32:48,695 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final
2017-10-09 17:32:49,479 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
2017-10-09 17:32:49,724 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: {color:#14892c}WildFly Full 11.0.0.CR1{color} (WildFly Core 3.0.1.Final) starting
2017-10-09 17:32:54,695 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-i
nterface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2017-10-09 17:32:54,758 INFO [org.wildfly.security] (ServerService Thread Pool -- 10) ELY00001: WildFly Elytron version 1.1.1.Final
2017-10-09 17:32:54,824 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 33) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=d
efault-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecat
ion.
2017-10-09 17:32:54,891 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 8) WFLYCTL0028: Attribute 'socket-binding' in the resource at address '/subsystem=jgroups/stack=jdbc
/protocol=FD_SOCK' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2017-10-09 17:32:55,665 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 27) WFLYDR0001: Content added at location /opt/wildfly/standalone/data/content/93/8e4c4a161a44fd84a305161a786cc43453d82b/c
ontent
2017-10-09 17:32:55,727 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
2017-10-09 17:32:55,803 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.5.1.Final
2017-10-09 17:32:55,829 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.5.1.Final
2017-10-09 17:32:55,952 INFO [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
2017-10-09 17:32:55,985 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 61) WFLYNAM0001: Activating Naming Subsystem
2017-10-09 17:32:56,008 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 49) WFLYIIOP0001: Activating IIOP Subsystem
2017-10-09 17:32:56,011 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 3.6.13
2017-10-09 17:32:56,017 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
2017-10-09 17:32:55,948 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for en
vironments running multiple servers. Please make sure the attribute value is unique.
2017-10-09 17:32:55,965 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
2017-10-09 17:32:56,029 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
2017-10-09 17:32:55,980 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.0.24.Final
2017-10-09 17:32:56,063 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 47) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available proc
essors
2017-10-09 17:32:56,350 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Final
2017-10-09 17:32:56,456 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.18.Final starting
2017-10-09 17:32:56,489 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.2.Final
2017-10-09 17:32:56,552 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)
2017-10-09 17:32:56,806 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 12.1)
2017-10-09 17:32:56,794 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
2017-10-09 17:32:56,844 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2017-10-09 17:32:56,935 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
2017-10-09 17:32:56,962 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
2017-10-09 17:32:57,452 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs
on this host.
2017-10-09 17:32:57,467 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker poo
l sizing.
2017-10-09 17:32:57,556 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'fal
se', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2017-10-09 17:32:57,732 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = oracle
2017-10-09 17:32:58,002 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql
2017-10-09 17:32:58,020 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
2017-10-09 17:32:59,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
2017-10-09 17:32:59,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
2017-10-09 17:32:59,609 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8180
2017-10-09 17:32:59,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8109
2017-10-09 17:32:59,682 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
2017-10-09 17:32:59,703 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started
2017-10-09 17:32:59,716 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000001: Initializing mod_cluster version 1.3.7.Final
2017-10-09 17:32:59,738 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
2017-10-09 17:32:59,749 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/wildfly/standalone/configuration/application.keystore not found, it will be auto gene
rated on first use with a self signed certificate for host localhost
2017-10-09 17:32:59,775 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
2017-10-09 17:32:59,801 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "OptoPlusServices-ear-1.0.0.ear" (runtime-name: "OptoPlusServices-ear-1.0.0.ear")
2017-10-09 17:32:59,825 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
2017-10-09 17:33:00,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8543
2017-10-09 17:33:01,121 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException
in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:436)
at org.jgroups.protocols.JDBC_PING.init(JDBC_PING.java:129)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
... 5 more
Caused by: {color:#d04437}javax.naming.NameNotFoundException: jdbc/db_optoplus [Root exception is java.lang.IllegalStateException]
{color} at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:423)
... 10 more
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:142)
at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
... 18 more
2017-10-09 17:33:01,294 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
2017-10-09 17:33:01,303 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2017-10-09 17:33:01,304 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [{color:#d04437}java:/jdbc/db_optoplus{color}]
{quote}
was:
JDBC_PING if configured with jndi resources will cause :
IllegalArgumentException: Could not lookup datasource
NameNotFoundException
IllegalStateException
The same jndi resource is correctly found and used by a deployed application.
It seems the jndi resouce is not ready, yet, when JGROUPS needs it.
{quote}2017-10-09 17:32:48,695 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final
2017-10-09 17:32:49,479 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
2017-10-09 17:32:49,724 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.1.Final) starting
2017-10-09 17:32:49,729 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:
[Standalone] =
awt.toolkit = sun.awt.X11.XToolkit
file.encoding = ANSI_X3.4-1968
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 = /opt/wildfly/jboss-modules.jar
java.class.version = 52.0
java.endorsed.dirs = /opt/jdk1.8.0_144/jre/lib/endorsed
java.ext.dirs = /opt/jdk1.8.0_144/jre/lib/ext:/usr/java/packages/lib/ext
java.home = /opt/jdk1.8.0_144/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 = Java(TM) SE Runtime Environment
java.runtime.version = 1.8.0_144-b01
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.8
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.8.0_144
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.8
java.vm.vendor = Oracle Corporation
java.vm.version = 25.144-b01
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.bind.address = 0.0.0.0
jboss.bind.address.management = 0.0.0.0
jboss.home.dir = /opt/wildfly
jboss.host.name = 94a2ac364002
jboss.modules.dir = /opt/wildfly/modules
jboss.modules.system.pkgs = org.jboss.byteman
jboss.node.name = 94a2ac364002
jboss.qualified.host.name = 94a2ac364002
jboss.server.base.dir = /opt/wildfly/standalone
jboss.server.config.dir = /opt/wildfly/standalone/configuration
jboss.server.data.dir = /opt/wildfly/standalone/data
jboss.server.deploy.dir = /opt/wildfly/standalone/data/content
jboss.server.log.dir = /opt/wildfly/standalone/log
jboss.server.name = 94a2ac364002
jboss.server.persist.config = true
jboss.server.temp.dir = /opt/wildfly/standalone/tmp
line.separator =
logging.configuration = file:/opt/wildfly/standalone/configuration/logging.properties
module.path = /opt/wildfly/modules
org.jboss.boot.log.file = /opt/wildfly/standalone/log/server.log
org.jboss.resolver.warning = true
org.xml.sax.driver = __redirected.__XMLReaderFactory
os.arch = amd64
os.name = Linux
os.version = 4.9.43-17.39.amzn1.x86_64
path.separator = :
sun.arch.data.model = 64
sun.boot.class.path = /opt/jdk1.8.0_144/jre/lib/resources.jar:/opt/jdk1.8.0_144/jre/lib/rt.jar:/opt/jdk1.8.0_144/jre/lib/sunrsasign.jar:/opt/jdk1.8.0_144/jre/lib/jsse.jar:/opt/jdk1.8.0_144/jre/lib/jce
.jar:/opt/jdk1.8.0_144/jre/lib/charsets.jar:/opt/jdk1.8.0_144/jre/lib/jfr.jar:/opt/jdk1.8.0_144/jre/classes
sun.boot.library.path = /opt/jdk1.8.0_144/jre/lib/amd64
sun.cpu.endian = little
sun.cpu.isalist =
sun.io.unicode.encoding = UnicodeLittle
sun.java.command = /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -b 0.0.0.0 -bmanagement
=0.0.0.0
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = ANSI_X3.4-1968
sun.management.compiler = HotSpot 64-Bit Tiered Compilers
sun.os.patch.level = unknown
user.country = US
user.dir = /run/s6/services/wildfly
user.home = /root
user.language = en
user.name = root
user.timezone = Etc/UTC
2017-10-09 17:32:49,729 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -D[Standalone] -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djbo
ss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.pr
operties
2017-10-09 17:32:54,695 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-i
nterface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2017-10-09 17:32:54,758 INFO [org.wildfly.security] (ServerService Thread Pool -- 10) ELY00001: WildFly Elytron version 1.1.1.Final
2017-10-09 17:32:54,824 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 33) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=d
efault-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecat
ion.
2017-10-09 17:32:54,891 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 8) WFLYCTL0028: Attribute 'socket-binding' in the resource at address '/subsystem=jgroups/stack=jdbc
/protocol=FD_SOCK' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2017-10-09 17:32:55,665 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 27) WFLYDR0001: Content added at location /opt/wildfly/standalone/data/content/93/8e4c4a161a44fd84a305161a786cc43453d82b/c
ontent
2017-10-09 17:32:55,727 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
2017-10-09 17:32:55,803 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.5.1.Final
2017-10-09 17:32:55,829 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.5.1.Final
2017-10-09 17:32:55,952 INFO [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
2017-10-09 17:32:55,985 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 61) WFLYNAM0001: Activating Naming Subsystem
2017-10-09 17:32:56,008 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 49) WFLYIIOP0001: Activating IIOP Subsystem
2017-10-09 17:32:56,011 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 3.6.13
2017-10-09 17:32:56,017 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
2017-10-09 17:32:55,948 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for en
vironments running multiple servers. Please make sure the attribute value is unique.
2017-10-09 17:32:55,965 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
2017-10-09 17:32:56,029 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
2017-10-09 17:32:55,980 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.0.24.Final
2017-10-09 17:32:56,063 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 47) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available proc
essors
2017-10-09 17:32:56,350 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Final
2017-10-09 17:32:56,456 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.18.Final starting
2017-10-09 17:32:56,489 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.2.Final
2017-10-09 17:32:56,552 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)
2017-10-09 17:32:56,806 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 12.1)
2017-10-09 17:32:56,794 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
2017-10-09 17:32:56,844 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2017-10-09 17:32:56,935 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
2017-10-09 17:32:56,962 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
2017-10-09 17:32:57,452 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs
on this host.
2017-10-09 17:32:57,467 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker poo
l sizing.
2017-10-09 17:32:57,556 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'fal
se', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2017-10-09 17:32:57,732 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = oracle
2017-10-09 17:32:58,002 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql
2017-10-09 17:32:58,020 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
2017-10-09 17:32:59,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
2017-10-09 17:32:59,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
2017-10-09 17:32:59,609 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8180
2017-10-09 17:32:59,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8109
2017-10-09 17:32:59,682 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
2017-10-09 17:32:59,703 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started
2017-10-09 17:32:59,716 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000001: Initializing mod_cluster version 1.3.7.Final
2017-10-09 17:32:59,738 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
2017-10-09 17:32:59,749 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/wildfly/standalone/configuration/application.keystore not found, it will be auto gene
rated on first use with a self signed certificate for host localhost
2017-10-09 17:32:59,775 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
2017-10-09 17:32:59,801 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "OptoPlusServices-ear-1.0.0.ear" (runtime-name: "OptoPlusServices-ear-1.0.0.ear")
2017-10-09 17:32:59,825 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
2017-10-09 17:33:00,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8543
2017-10-09 17:33:01,121 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException
in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:436)
at org.jgroups.protocols.JDBC_PING.init(JDBC_PING.java:129)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
... 5 more
Caused by: javax.naming.NameNotFoundException: jdbc/db_optoplus [Root exception is java.lang.IllegalStateException]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:423)
... 10 more
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:142)
at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
... 18 more
2017-10-09 17:33:01,294 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
2017-10-09 17:33:01,303 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2017-10-09 17:33:01,304 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/jdbc/db_optoplus]
{quote}
> JDBC_PING gets a NameNotFoundException when using jndi resource
> ---------------------------------------------------------------
>
> Key: WFLY-9427
> URL: https://issues.jboss.org/browse/WFLY-9427
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Alessandro Moscatelli
> Assignee: Paul Ferraro
> Fix For: 11.0.0.Final
>
>
> JDBC_PING if configured with jndi resources will cause :
> IllegalArgumentException: Could not lookup datasource
> NameNotFoundException
> IllegalStateException
> The same jndi resource is correctly found and used by a deployed application.
> It seems the jndi resouce is not ready, yet, when JGROUPS needs it.
> {quote}2017-10-09 17:32:48,695 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final
> 2017-10-09 17:32:49,479 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
> 2017-10-09 17:32:49,724 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: {color:#14892c}WildFly Full 11.0.0.CR1{color} (WildFly Core 3.0.1.Final) starting
> 2017-10-09 17:32:54,695 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-i
> nterface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 2017-10-09 17:32:54,758 INFO [org.wildfly.security] (ServerService Thread Pool -- 10) ELY00001: WildFly Elytron version 1.1.1.Final
> 2017-10-09 17:32:54,824 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 33) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=d
> efault-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecat
> ion.
> 2017-10-09 17:32:54,891 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 8) WFLYCTL0028: Attribute 'socket-binding' in the resource at address '/subsystem=jgroups/stack=jdbc
> /protocol=FD_SOCK' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 2017-10-09 17:32:55,665 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 27) WFLYDR0001: Content added at location /opt/wildfly/standalone/data/content/93/8e4c4a161a44fd84a305161a786cc43453d82b/c
> ontent
> 2017-10-09 17:32:55,727 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 2017-10-09 17:32:55,803 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.5.1.Final
> 2017-10-09 17:32:55,829 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.5.1.Final
> 2017-10-09 17:32:55,952 INFO [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
> 2017-10-09 17:32:55,985 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 61) WFLYNAM0001: Activating Naming Subsystem
> 2017-10-09 17:32:56,008 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 49) WFLYIIOP0001: Activating IIOP Subsystem
> 2017-10-09 17:32:56,011 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 3.6.13
> 2017-10-09 17:32:56,017 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
> 2017-10-09 17:32:55,948 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for en
> vironments running multiple servers. Please make sure the attribute value is unique.
> 2017-10-09 17:32:55,965 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 2017-10-09 17:32:56,029 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
> 2017-10-09 17:32:55,980 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.0.24.Final
> 2017-10-09 17:32:56,063 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 47) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available proc
> essors
> 2017-10-09 17:32:56,350 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Final
> 2017-10-09 17:32:56,456 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.18.Final starting
> 2017-10-09 17:32:56,489 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.2.Final
> 2017-10-09 17:32:56,552 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)
> 2017-10-09 17:32:56,806 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 12.1)
> 2017-10-09 17:32:56,794 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
> 2017-10-09 17:32:56,844 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 2017-10-09 17:32:56,935 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
> 2017-10-09 17:32:56,962 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 2017-10-09 17:32:57,452 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs
> on this host.
> 2017-10-09 17:32:57,467 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker poo
> l sizing.
> 2017-10-09 17:32:57,556 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'fal
> se', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 2017-10-09 17:32:57,732 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = oracle
> 2017-10-09 17:32:58,002 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql
> 2017-10-09 17:32:58,020 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
> 2017-10-09 17:32:59,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
> 2017-10-09 17:32:59,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
> 2017-10-09 17:32:59,609 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8180
> 2017-10-09 17:32:59,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8109
> 2017-10-09 17:32:59,682 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> 2017-10-09 17:32:59,703 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started
> 2017-10-09 17:32:59,716 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000001: Initializing mod_cluster version 1.3.7.Final
> 2017-10-09 17:32:59,738 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
> 2017-10-09 17:32:59,749 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/wildfly/standalone/configuration/application.keystore not found, it will be auto gene
> rated on first use with a self signed certificate for host localhost
> 2017-10-09 17:32:59,775 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
> 2017-10-09 17:32:59,801 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "OptoPlusServices-ear-1.0.0.ear" (runtime-name: "OptoPlusServices-ear-1.0.0.ear")
> 2017-10-09 17:32:59,825 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
> 2017-10-09 17:33:00,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8543
> 2017-10-09 17:33:01,121 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException
> in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
> at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:436)
> at org.jgroups.protocols.JDBC_PING.init(JDBC_PING.java:129)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
> at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
> ... 5 more
> Caused by: {color:#d04437}javax.naming.NameNotFoundException: jdbc/db_optoplus [Root exception is java.lang.IllegalStateException]
> {color} at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:423)
> ... 10 more
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:142)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
> at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
> ... 18 more
> 2017-10-09 17:33:01,294 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 2017-10-09 17:33:01,303 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 2017-10-09 17:33:01,304 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [{color:#d04437}java:/jdbc/db_optoplus{color}]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-9427) JDBC_PING gets a NameNotFoundException when using jndi resource
by Alessandro Moscatelli (JIRA)
[ https://issues.jboss.org/browse/WFLY-9427?page=com.atlassian.jira.plugin.... ]
Alessandro Moscatelli updated WFLY-9427:
----------------------------------------
Description:
JDBC_PING if configured with jndi resources will cause :
IllegalArgumentException: Could not lookup datasource
NameNotFoundException
IllegalStateException
The same jndi resource is correctly found and used by a deployed application.
It seems the jndi resouce is not ready, yet, when JGROUPS needs it.
{quote}2017-10-09 17:32:48,695 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final
2017-10-09 17:32:49,479 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
2017-10-09 17:32:49,724 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.1.Final) starting
2017-10-09 17:32:49,729 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:
[Standalone] =
awt.toolkit = sun.awt.X11.XToolkit
file.encoding = ANSI_X3.4-1968
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 = /opt/wildfly/jboss-modules.jar
java.class.version = 52.0
java.endorsed.dirs = /opt/jdk1.8.0_144/jre/lib/endorsed
java.ext.dirs = /opt/jdk1.8.0_144/jre/lib/ext:/usr/java/packages/lib/ext
java.home = /opt/jdk1.8.0_144/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 = Java(TM) SE Runtime Environment
java.runtime.version = 1.8.0_144-b01
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.8
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.8.0_144
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.8
java.vm.vendor = Oracle Corporation
java.vm.version = 25.144-b01
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.bind.address = 0.0.0.0
jboss.bind.address.management = 0.0.0.0
jboss.home.dir = /opt/wildfly
jboss.host.name = 94a2ac364002
jboss.modules.dir = /opt/wildfly/modules
jboss.modules.system.pkgs = org.jboss.byteman
jboss.node.name = 94a2ac364002
jboss.qualified.host.name = 94a2ac364002
jboss.server.base.dir = /opt/wildfly/standalone
jboss.server.config.dir = /opt/wildfly/standalone/configuration
jboss.server.data.dir = /opt/wildfly/standalone/data
jboss.server.deploy.dir = /opt/wildfly/standalone/data/content
jboss.server.log.dir = /opt/wildfly/standalone/log
jboss.server.name = 94a2ac364002
jboss.server.persist.config = true
jboss.server.temp.dir = /opt/wildfly/standalone/tmp
line.separator =
logging.configuration = file:/opt/wildfly/standalone/configuration/logging.properties
module.path = /opt/wildfly/modules
org.jboss.boot.log.file = /opt/wildfly/standalone/log/server.log
org.jboss.resolver.warning = true
org.xml.sax.driver = __redirected.__XMLReaderFactory
os.arch = amd64
os.name = Linux
os.version = 4.9.43-17.39.amzn1.x86_64
path.separator = :
sun.arch.data.model = 64
sun.boot.class.path = /opt/jdk1.8.0_144/jre/lib/resources.jar:/opt/jdk1.8.0_144/jre/lib/rt.jar:/opt/jdk1.8.0_144/jre/lib/sunrsasign.jar:/opt/jdk1.8.0_144/jre/lib/jsse.jar:/opt/jdk1.8.0_144/jre/lib/jce
.jar:/opt/jdk1.8.0_144/jre/lib/charsets.jar:/opt/jdk1.8.0_144/jre/lib/jfr.jar:/opt/jdk1.8.0_144/jre/classes
sun.boot.library.path = /opt/jdk1.8.0_144/jre/lib/amd64
sun.cpu.endian = little
sun.cpu.isalist =
sun.io.unicode.encoding = UnicodeLittle
sun.java.command = /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -b 0.0.0.0 -bmanagement
=0.0.0.0
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = ANSI_X3.4-1968
sun.management.compiler = HotSpot 64-Bit Tiered Compilers
sun.os.patch.level = unknown
user.country = US
user.dir = /run/s6/services/wildfly
user.home = /root
user.language = en
user.name = root
user.timezone = Etc/UTC
2017-10-09 17:32:49,729 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -D[Standalone] -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djbo
ss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.pr
operties
2017-10-09 17:32:54,695 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-i
nterface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2017-10-09 17:32:54,758 INFO [org.wildfly.security] (ServerService Thread Pool -- 10) ELY00001: WildFly Elytron version 1.1.1.Final
2017-10-09 17:32:54,824 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 33) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=d
efault-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecat
ion.
2017-10-09 17:32:54,891 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 8) WFLYCTL0028: Attribute 'socket-binding' in the resource at address '/subsystem=jgroups/stack=jdbc
/protocol=FD_SOCK' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2017-10-09 17:32:55,665 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 27) WFLYDR0001: Content added at location /opt/wildfly/standalone/data/content/93/8e4c4a161a44fd84a305161a786cc43453d82b/c
ontent
2017-10-09 17:32:55,727 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
2017-10-09 17:32:55,803 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.5.1.Final
2017-10-09 17:32:55,829 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.5.1.Final
2017-10-09 17:32:55,952 INFO [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
2017-10-09 17:32:55,985 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 61) WFLYNAM0001: Activating Naming Subsystem
2017-10-09 17:32:56,008 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 49) WFLYIIOP0001: Activating IIOP Subsystem
2017-10-09 17:32:56,011 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 3.6.13
2017-10-09 17:32:56,017 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
2017-10-09 17:32:55,948 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for en
vironments running multiple servers. Please make sure the attribute value is unique.
2017-10-09 17:32:55,965 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
2017-10-09 17:32:56,029 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
2017-10-09 17:32:55,980 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.0.24.Final
2017-10-09 17:32:56,063 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 47) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available proc
essors
2017-10-09 17:32:56,350 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Final
2017-10-09 17:32:56,456 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.18.Final starting
2017-10-09 17:32:56,489 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.2.Final
2017-10-09 17:32:56,552 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)
2017-10-09 17:32:56,806 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 12.1)
2017-10-09 17:32:56,794 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
2017-10-09 17:32:56,844 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2017-10-09 17:32:56,935 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
2017-10-09 17:32:56,962 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
2017-10-09 17:32:57,452 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs
on this host.
2017-10-09 17:32:57,467 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker poo
l sizing.
2017-10-09 17:32:57,556 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'fal
se', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2017-10-09 17:32:57,732 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = oracle
2017-10-09 17:32:58,002 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql
2017-10-09 17:32:58,020 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
2017-10-09 17:32:59,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
2017-10-09 17:32:59,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
2017-10-09 17:32:59,609 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8180
2017-10-09 17:32:59,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8109
2017-10-09 17:32:59,682 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
2017-10-09 17:32:59,703 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started
2017-10-09 17:32:59,716 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000001: Initializing mod_cluster version 1.3.7.Final
2017-10-09 17:32:59,738 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
2017-10-09 17:32:59,749 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/wildfly/standalone/configuration/application.keystore not found, it will be auto gene
rated on first use with a self signed certificate for host localhost
2017-10-09 17:32:59,775 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
2017-10-09 17:32:59,801 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "OptoPlusServices-ear-1.0.0.ear" (runtime-name: "OptoPlusServices-ear-1.0.0.ear")
2017-10-09 17:32:59,825 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
2017-10-09 17:33:00,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8543
2017-10-09 17:33:01,121 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException
in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:436)
at org.jgroups.protocols.JDBC_PING.init(JDBC_PING.java:129)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
... 5 more
Caused by: javax.naming.NameNotFoundException: jdbc/db_optoplus [Root exception is java.lang.IllegalStateException]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:423)
... 10 more
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:142)
at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
... 18 more
2017-10-09 17:33:01,294 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
2017-10-09 17:33:01,303 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2017-10-09 17:33:01,304 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/jdbc/db_optoplus]
{quote}
was:
JDBC_PING if configured with jndi resources will cause :
IllegalArgumentException: Could not lookup datasource
NameNotFoundException
IllegalStateException
The same jndi resource is correctly found and used by a deployed application.
It seems the jndi resouce is not ready, yet, when JGROUPS needs it.
> JDBC_PING gets a NameNotFoundException when using jndi resource
> ---------------------------------------------------------------
>
> Key: WFLY-9427
> URL: https://issues.jboss.org/browse/WFLY-9427
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.CR1
> Reporter: Alessandro Moscatelli
> Assignee: Paul Ferraro
> Fix For: 11.0.0.Final
>
>
> JDBC_PING if configured with jndi resources will cause :
> IllegalArgumentException: Could not lookup datasource
> NameNotFoundException
> IllegalStateException
> The same jndi resource is correctly found and used by a deployed application.
> It seems the jndi resouce is not ready, yet, when JGROUPS needs it.
> {quote}2017-10-09 17:32:48,695 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final
> 2017-10-09 17:32:49,479 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
> 2017-10-09 17:32:49,724 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 11.0.0.CR1 (WildFly Core 3.0.1.Final) starting
> 2017-10-09 17:32:49,729 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:
> [Standalone] =
> awt.toolkit = sun.awt.X11.XToolkit
> file.encoding = ANSI_X3.4-1968
> 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 = /opt/wildfly/jboss-modules.jar
> java.class.version = 52.0
> java.endorsed.dirs = /opt/jdk1.8.0_144/jre/lib/endorsed
> java.ext.dirs = /opt/jdk1.8.0_144/jre/lib/ext:/usr/java/packages/lib/ext
> java.home = /opt/jdk1.8.0_144/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 = Java(TM) SE Runtime Environment
> java.runtime.version = 1.8.0_144-b01
> java.specification.name = Java Platform API Specification
> java.specification.vendor = Oracle Corporation
> java.specification.version = 1.8
> 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.8.0_144
> java.vm.info = mixed mode
> java.vm.name = Java HotSpot(TM) 64-Bit Server VM
> java.vm.specification.name = Java Virtual Machine Specification
> java.vm.specification.vendor = Oracle Corporation
> java.vm.specification.version = 1.8
> java.vm.vendor = Oracle Corporation
> java.vm.version = 25.144-b01
> 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.bind.address = 0.0.0.0
> jboss.bind.address.management = 0.0.0.0
> jboss.home.dir = /opt/wildfly
> jboss.host.name = 94a2ac364002
> jboss.modules.dir = /opt/wildfly/modules
> jboss.modules.system.pkgs = org.jboss.byteman
> jboss.node.name = 94a2ac364002
> jboss.qualified.host.name = 94a2ac364002
> jboss.server.base.dir = /opt/wildfly/standalone
> jboss.server.config.dir = /opt/wildfly/standalone/configuration
> jboss.server.data.dir = /opt/wildfly/standalone/data
> jboss.server.deploy.dir = /opt/wildfly/standalone/data/content
> jboss.server.log.dir = /opt/wildfly/standalone/log
> jboss.server.name = 94a2ac364002
> jboss.server.persist.config = true
> jboss.server.temp.dir = /opt/wildfly/standalone/tmp
> line.separator =
> logging.configuration = file:/opt/wildfly/standalone/configuration/logging.properties
> module.path = /opt/wildfly/modules
> org.jboss.boot.log.file = /opt/wildfly/standalone/log/server.log
> org.jboss.resolver.warning = true
> org.xml.sax.driver = __redirected.__XMLReaderFactory
> os.arch = amd64
> os.name = Linux
> os.version = 4.9.43-17.39.amzn1.x86_64
> path.separator = :
> sun.arch.data.model = 64
> sun.boot.class.path = /opt/jdk1.8.0_144/jre/lib/resources.jar:/opt/jdk1.8.0_144/jre/lib/rt.jar:/opt/jdk1.8.0_144/jre/lib/sunrsasign.jar:/opt/jdk1.8.0_144/jre/lib/jsse.jar:/opt/jdk1.8.0_144/jre/lib/jce
> .jar:/opt/jdk1.8.0_144/jre/lib/charsets.jar:/opt/jdk1.8.0_144/jre/lib/jfr.jar:/opt/jdk1.8.0_144/jre/classes
> sun.boot.library.path = /opt/jdk1.8.0_144/jre/lib/amd64
> sun.cpu.endian = little
> sun.cpu.isalist =
> sun.io.unicode.encoding = UnicodeLittle
> sun.java.command = /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -b 0.0.0.0 -bmanagement
> =0.0.0.0
> sun.java.launcher = SUN_STANDARD
> sun.jnu.encoding = ANSI_X3.4-1968
> sun.management.compiler = HotSpot 64-Bit Tiered Compilers
> sun.os.patch.level = unknown
> user.country = US
> user.dir = /run/s6/services/wildfly
> user.home = /root
> user.language = en
> user.name = root
> user.timezone = Etc/UTC
> 2017-10-09 17:32:49,729 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -D[Standalone] -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djbo
> ss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.pr
> operties
> 2017-10-09 17:32:54,695 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-i
> nterface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 2017-10-09 17:32:54,758 INFO [org.wildfly.security] (ServerService Thread Pool -- 10) ELY00001: WildFly Elytron version 1.1.1.Final
> 2017-10-09 17:32:54,824 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 33) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=d
> efault-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecat
> ion.
> 2017-10-09 17:32:54,891 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 8) WFLYCTL0028: Attribute 'socket-binding' in the resource at address '/subsystem=jgroups/stack=jdbc
> /protocol=FD_SOCK' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 2017-10-09 17:32:55,665 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 27) WFLYDR0001: Content added at location /opt/wildfly/standalone/data/content/93/8e4c4a161a44fd84a305161a786cc43453d82b/c
> ontent
> 2017-10-09 17:32:55,727 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
> 2017-10-09 17:32:55,803 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.5.1.Final
> 2017-10-09 17:32:55,829 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.5.1.Final
> 2017-10-09 17:32:55,952 INFO [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem
> 2017-10-09 17:32:55,985 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 61) WFLYNAM0001: Activating Naming Subsystem
> 2017-10-09 17:32:56,008 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 49) WFLYIIOP0001: Activating IIOP Subsystem
> 2017-10-09 17:32:56,011 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 3.6.13
> 2017-10-09 17:32:56,017 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension
> 2017-10-09 17:32:55,948 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for en
> vironments running multiple servers. Please make sure the attribute value is unique.
> 2017-10-09 17:32:55,965 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
> 2017-10-09 17:32:56,029 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.
> 2017-10-09 17:32:55,980 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.0.24.Final
> 2017-10-09 17:32:56,063 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 47) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available proc
> essors
> 2017-10-09 17:32:56,350 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.0.Final
> 2017-10-09 17:32:56,456 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.18.Final starting
> 2017-10-09 17:32:56,489 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.2.Final
> 2017-10-09 17:32:56,552 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)
> 2017-10-09 17:32:56,806 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 12.1)
> 2017-10-09 17:32:56,794 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
> 2017-10-09 17:32:56,844 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 2017-10-09 17:32:56,935 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
> 2017-10-09 17:32:56,962 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 2017-10-09 17:32:57,452 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs
> on this host.
> 2017-10-09 17:32:57,467 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker poo
> l sizing.
> 2017-10-09 17:32:57,556 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'fal
> se', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
> 2017-10-09 17:32:57,732 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = oracle
> 2017-10-09 17:32:58,002 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql
> 2017-10-09 17:32:58,020 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
> 2017-10-09 17:32:59,265 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
> 2017-10-09 17:32:59,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
> 2017-10-09 17:32:59,609 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8180
> 2017-10-09 17:32:59,623 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on 0.0.0.0:8109
> 2017-10-09 17:32:59,682 INFO [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
> 2017-10-09 17:32:59,703 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started
> 2017-10-09 17:32:59,716 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000001: Initializing mod_cluster version 1.3.7.Final
> 2017-10-09 17:32:59,738 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
> 2017-10-09 17:32:59,749 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/wildfly/standalone/configuration/application.keystore not found, it will be auto gene
> rated on first use with a self signed certificate for host localhost
> 2017-10-09 17:32:59,775 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
> 2017-10-09 17:32:59,801 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "OptoPlusServices-ear-1.0.0.ear" (runtime-name: "OptoPlusServices-ear-1.0.0.ear")
> 2017-10-09 17:32:59,825 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
> 2017-10-09 17:33:00,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8543
> 2017-10-09 17:33:01,121 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException
> in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:104)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.IllegalArgumentException: Could not lookup datasource java:/jdbc/db_optoplus
> at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:436)
> at org.jgroups.protocols.JDBC_PING.init(JDBC_PING.java:129)
> at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:861)
> at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:831)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:108)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:102)
> ... 5 more
> Caused by: javax.naming.NameNotFoundException: jdbc/db_optoplus [Root exception is java.lang.IllegalStateException]
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at org.jgroups.protocols.JDBC_PING.getDataSourceFromJNDI(JDBC_PING.java:423)
> ... 10 more
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:142)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
> at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
> ... 18 more
> 2017-10-09 17:33:01,294 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)
> 2017-10-09 17:33:01,303 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
> 2017-10-09 17:33:01,304 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/jdbc/db_optoplus]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (ELY-1394) ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1394?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1394:
----------------------------------
Component/s: Authentication Client
> ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1394
> URL: https://issues.jboss.org/browse/ELY-1394
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Affects Versions: 1.2.0.Beta5
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Fix For: 1.2.0.Beta6
>
>
> ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
> When you define clear-text password with "<key-store-clear-password password=\"Elytron\"/>\n"
> instead of credential-store clear-text password then everything works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (ELY-1394) ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1394?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1394:
----------------------------------
Affects Version/s: 1.2.0.Beta5
> ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1394
> URL: https://issues.jboss.org/browse/ELY-1394
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.2.0.Beta5
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Fix For: 1.2.0.Beta6
>
>
> ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
> When you define clear-text password with "<key-store-clear-password password=\"Elytron\"/>\n"
> instead of credential-store clear-text password then everything works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (ELY-1394) ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1394?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1394:
----------------------------------
Fix Version/s: 1.2.0.Beta6
> ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1394
> URL: https://issues.jboss.org/browse/ELY-1394
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.2.0.Beta5
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Fix For: 1.2.0.Beta6
>
>
> ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
> When you define clear-text password with "<key-store-clear-password password=\"Elytron\"/>\n"
> instead of credential-store clear-text password then everything works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-9424) Wildfly 10.1.0.Final - Very long deploy time on Windows 10
by Nándor Holozsnyák (JIRA)
[ https://issues.jboss.org/browse/WFLY-9424?page=com.atlassian.jira.plugin.... ]
Nándor Holozsnyák closed WFLY-9424.
-----------------------------------
Resolution: Done
Sorry for the long issue, but I was really sad about this problem and I wanted to get over it.
Today the problem was solved, one of my mate payed attention to the Windows Defender (we are still on Windows 10), which use approximately 20-30 % CPU time on Maven build and Wildfly deploy. After we switched off the Realtime Defending in Windows Defender the problem is gone and the build and deploy time is almost 80% faster than before.
We just can't beleive it.
TL;DR;
Turn off Windows Defender's Realtime Defending and then the problem will gone. (Tested on Windows 10 just)
> Wildfly 10.1.0.Final - Very long deploy time on Windows 10
> ----------------------------------------------------------
>
> Key: WFLY-9424
> URL: https://issues.jboss.org/browse/WFLY-9424
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Nándor Holozsnyák
> Assignee: Jason Greene
>
> I am having a really annoying "problem" with Wildfly. I have been using it for at least two years now and I really don't know what could be the problem.
> So I have a fresh Windows 10 64 bit install, and then I started working on my projects as well which was started earlier and there were no problem with the deploy time.
> I just pulled my stuff from VCS and then when I started to deploy it with Wildfly (as well as with Maven's Wildfly plugin and as well as put the .war into the deployments folder) the server prints out "Starting deployment ..." and then hangs for two minutes!! Always two minutes then deploy the application. It happens with no one project, with at least three, on my other laptop which has Windows 7 everything works fine.
> I decided to download the wildfly quickstart repo and then try it out. With one EJB project it works well, deploy goes as a new Lambo. I tried to log the wildfly with trace to get some more information but nothing special came. Wildfly maven plugin was in debug too but no more information. Wildfly memory settings are upgraded to 1 GB, but no luck. I am going to write out a ticket, but it is a bit frustrating.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (ELY-1394) ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-1394:
---------------------------------
Summary: ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
Key: ELY-1394
URL: https://issues.jboss.org/browse/ELY-1394
Project: WildFly Elytron
Issue Type: Bug
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
ElytronClient - sslContext cannot use credential-store-reference clear-text password for key-store-ssl-certificate.
When you define clear-text password with "<key-store-clear-password password=\"Elytron\"/>\n"
instead of credential-store clear-text password then everything works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (WFLY-9074) NPE o.j.a.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation()
by Darryl Miles (JIRA)
[ https://issues.jboss.org/browse/WFLY-9074?page=com.atlassian.jira.plugin.... ]
Darryl Miles commented on WFLY-9074:
------------------------------------
[~tomekadamski] Trying to build a testcase ? The project is complex (3 WARs, 12+ EJBs, 6+ JPAs, various others, around a 40Mb deployable EAR)
I still see this issue, but its intermittent and even for me not reproducible on demand.
I do not observe the issue for a while (many days), then it will occur and I think only on a few occasions in many months have I seen two such issues in a row.
It may help to throttle the test machine CPU, as I think it is some interaction with race condition where the code throwing the NPE gets to some point first, before something else should have happened.
Is it possible to at least log all the module checkpoints to some file in the log directory ? I don't want it in the main server output, all the output must go to some other file in log directory. Something I can permanently enable ?
The log file will record the deploying unitname, thread id, timestamp, name of checkout passed, status of deployment unit ?
This was I can run deployment over and over, with varying machine background load overnight. Then fish out the failures, then fish out the matching deployment checkpoint log for that attempt to bootup the EAR.
This is the only way I can thing to find this one. Compare a successful deployment with a failed one and see what things did not happen on other threads before the problematic.
If I can anonimize it (rename my deployment names) I can even send you the full output to perform analyse.
Then you can patch with some suggestion from you, that inserts a Thread.sleep() in the part, to force a 100% reproduable issue with a simple project (maybe byteman can help also?).
This is all I can suggest.
> NPE o.j.a.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation()
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-9074
> URL: https://issues.jboss.org/browse/WFLY-9074
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.1.0.Final
> Reporter: Darryl Miles
> Assignee: Tomasz Adamski
>
> https://issues.jboss.org/browse/WFLY-6663 (see fix for this other bug, maybe the 1 line wait method is needed somewhere else too?)
> Much more intermittent matter (I guess the time window is smaller).
> 16:14:04,428 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 19) MSC000001: Failed to start service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134)
> at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88)
> at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124)
> at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> ... 6 more
> Caused by: javax.ejb.EJBException: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb
> at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterceptor.java:83)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:91)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:106)
> at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:58)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
> ... 11 more
> Caused by: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:319)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:97)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:103)
> ... 28 more
> Caused by: javax.naming.NameNotFoundException: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb [Root exception is java.lang.IllegalStateException: WFLYEE0046: Failed to instantiate component view]
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:316)
> ... 45 more
> Caused by: java.lang.IllegalStateException: WFLYEE0046: Failed to instantiate component view
> at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:58)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:143)
> ... 50 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3.component.stateful.StatefulComponentSessionIdGeneratingInterceptor.processInvocation(StatefulComponentSessionIdGeneratingInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$DefaultViewInstanceFactory.createViewInstance(ViewService.java:305)
> at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:184)
> at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:174)
> at org.jboss.as.ee.component.ViewManagedReferenceFactory.getReference(ViewManagedReferenceFactory.java:56)
> ... 51 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (WFCORE-3348) Minor optimizations in RunningStateJmx registration
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-3348:
----------------------------------------
Summary: Minor optimizations in RunningStateJmx registration
Key: WFCORE-3348
URL: https://issues.jboss.org/browse/WFCORE-3348
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management, JMX
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
While crawling over code for speed/memory reduction for WF 11 I noticed the RunningStateJmx.registerMBean stuff was a bit more complex than needed.
This is really minor. Eliminate an inner class used for an enum switch, avoid some simple calculations when the result is statically known.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (WFCORE-3073) Handle TERM gracefully
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3073?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3073:
------------------------------------------
Since a proper attribute isn't really required for the target use case, for now I think I want to defer adding one. I started looking at adding one today and while it's easy to stick an attribute somewhere (e.g. subsystem=core-management), the resource to contain it, the name etc are not blindingly obvious. I don't want to create a half-assed API for just this one attribute and then later we find there are other related attributes for which my half-assed API is a poor fit, and then we need to retrofit.
> Handle TERM gracefully
> ----------------------
>
> Key: WFCORE-3073
> URL: https://issues.jboss.org/browse/WFCORE-3073
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Ben Parees
> Assignee: Brian Stansberry
> Fix For: 4.0.0.Alpha1
>
>
> The wildfly server currently terminates immediately in response to a TERM signal. To achieve a clean shutdown requires invoking the CLI tooling. This is particularly problematic in container environments like kubernetes where the container process (wildfly in this case) is going to get a TERM signal when the container needs to be moved.
> While it's possible to wrapper the process and handle the TERM and then invoke the CLI, it would be preferable for the server process itself to cleanly handle a TERM signal by waiting for in-flight requests to complete (w/ some grace period of course).
> Having this as configurable behavior would be good if there are backwards compatibility concerns about introducing this behavior change.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
- 1
- 0