[JBoss JIRA] (WFCORE-1979) Wildfly-openssl is missing 32 bits variant.
by Radim Hatlapatka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1979?page=com.atlassian.jira.plugi... ]
Radim Hatlapatka reassigned WFCORE-1979:
----------------------------------------
Assignee: Stuart Douglas (was: Jason Greene)
> Wildfly-openssl is missing 32 bits variant.
> -------------------------------------------
>
> Key: WFCORE-1979
> URL: https://issues.jboss.org/browse/WFCORE-1979
> Project: WildFly Core
> Issue Type: Bug
> Components: Security, Server
> Reporter: Radim Hatlapatka
> Assignee: Stuart Douglas
> Priority: Blocker
> Labels: wildfly-openssl
>
> There is missing wildfly-openssl build for 32 bits variants resulting in this exception:
> {noformat}
> 2016-10-25 14:35:27,732 ERROR [stderr] (MSC service thread 1-7) java.lang.reflect.InvocationTargetException
> 2016-10-25 14:35:27,734 ERROR [stderr] (MSC service thread 1-7) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2016-10-25 14:35:27,735 ERROR [stderr] (MSC service thread 1-7) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> 2016-10-25 14:35:27,736 ERROR [stderr] (MSC service thread 1-7) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> 2016-10-25 14:35:27,737 ERROR [stderr] (MSC service thread 1-7) at java.lang.reflect.Method.invoke(Method.java:508)
> 2016-10-25 14:35:27,738 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.openssl.SSL.init(SSL.java:73)
> 2016-10-25 14:35:27,738 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.openssl.SSL.getInstance(SSL.java:49)
> 2016-10-25 14:35:27,739 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.openssl.OpenSSLEngine.<clinit>(OpenSSLEngine.java:59)
> 2016-10-25 14:35:27,740 ERROR [stderr] (MSC service thread 1-7) at java.lang.Class.forNameImpl(Native Method)
> 2016-10-25 14:35:27,741 ERROR [stderr] (MSC service thread 1-7) at java.lang.Class.forName(Class.java:348)
> 2016-10-25 14:35:27,742 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.OpenSSLAlpnProvider$1.run(OpenSSLAlpnProvider.java:47)
> 2016-10-25 14:35:27,743 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.OpenSSLAlpnProvider$1.run(OpenSSLAlpnProvider.java:43)
> 2016-10-25 14:35:27,754 ERROR [stderr] (MSC service thread 1-7) at java.security.AccessController.doPrivileged(AccessController.java:594)
> 2016-10-25 14:35:27,755 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.OpenSSLAlpnProvider.<clinit>(OpenSSLAlpnProvider.java:43)
> 2016-10-25 14:35:27,756 ERROR [stderr] (MSC service thread 1-7) at java.lang.J9VMInternals.newInstanceImpl(Native Method)
> 2016-10-25 14:35:27,757 ERROR [stderr] (MSC service thread 1-7) at java.lang.Class.newInstance(Class.java:1899)
> 2016-10-25 14:35:27,758 ERROR [stderr] (MSC service thread 1-7) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:391)
> 2016-10-25 14:35:27,759 ERROR [stderr] (MSC service thread 1-7) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:415)
> 2016-10-25 14:35:27,760 ERROR [stderr] (MSC service thread 1-7) at java.util.ServiceLoader$1.next(ServiceLoader.java:491)
> 2016-10-25 14:35:27,776 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.ALPNManager.<init>(ALPNManager.java:40)
> 2016-10-25 14:35:27,777 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.ALPNManager.<clinit>(ALPNManager.java:35)
> 2016-10-25 14:35:27,778 ERROR [stderr] (MSC service thread 1-7) at io.undertow.server.protocol.http.AlpnOpenListener.<init>(AlpnOpenListener.java:64)
> 2016-10-25 14:35:27,779 ERROR [stderr] (MSC service thread 1-7) at io.undertow.server.protocol.http.AlpnOpenListener.<init>(AlpnOpenListener.java:83)
> 2016-10-25 14:35:27,780 ERROR [stderr] (MSC service thread 1-7) at io.undertow.server.protocol.http.AlpnOpenListener.<init>(AlpnOpenListener.java:75)
> 2016-10-25 14:35:27,781 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.extension.undertow.HttpsListenerService.createAlpnOpenListener(HttpsListenerService.java:101)
> 2016-10-25 14:35:27,782 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.extension.undertow.HttpsListenerService.createOpenListener(HttpsListenerService.java:86)
> 2016-10-25 14:35:27,783 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:158)
> 2016-10-25 14:35:27,784 ERROR [stderr] (MSC service thread 1-7) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> 2016-10-25 14:35:27,785 ERROR [stderr] (MSC service thread 1-7) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> 2016-10-25 14:35:27,789 ERROR [stderr] (MSC service thread 1-7) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> 2016-10-25 14:35:27,790 ERROR [stderr] (MSC service thread 1-7) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> 2016-10-25 14:35:27,791 ERROR [stderr] (MSC service thread 1-7) at java.lang.Thread.run(Thread.java:785)
> 2016-10-25 14:35:27,792 ERROR [stderr] (MSC service thread 1-7) Caused by: java.lang.UnsatisfiedLinkError: /tmp/tmp-317723765121491548openssl/libwfssl.so (/tmp/tmp-317723765121491548openssl/libwfssl.so: wrong ELF class: ELFCLASS64)
> 2016-10-25 14:35:27,794 ERROR [stderr] (MSC service thread 1-7) at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1344)
> 2016-10-25 14:35:27,794 ERROR [stderr] (MSC service thread 1-7) at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:1304)
> 2016-10-25 14:35:27,795 ERROR [stderr] (MSC service thread 1-7) at java.lang.System.loadLibrary(System.java:552)
> 2016-10-25 14:35:27,796 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.openssl.SSL$LibraryLoader.load(SSL.java:180)
> 2016-10-25 14:35:27,797 ERROR [stderr] (MSC service thread 1-7) ... 31 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1979) Wildfly-openssl is missing 32 bits variant.
by Radim Hatlapatka (JIRA)
Radim Hatlapatka created WFCORE-1979:
----------------------------------------
Summary: Wildfly-openssl is missing 32 bits variant.
Key: WFCORE-1979
URL: https://issues.jboss.org/browse/WFCORE-1979
Project: WildFly Core
Issue Type: Bug
Components: Server, Security
Reporter: Radim Hatlapatka
Assignee: Jason Greene
Priority: Blocker
There is missing wildfly-openssl build for 32 bits variants resulting in this exception:
{noformat}
[line 154] 2016-10-25 14:35:27,732 ERROR [stderr] (MSC service thread 1-7) java.lang.reflect.InvocationTargetException
[line 155] 2016-10-25 14:35:27,734 ERROR [stderr] (MSC service thread 1-7) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[line 156] 2016-10-25 14:35:27,735 ERROR [stderr] (MSC service thread 1-7) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
[line 157] 2016-10-25 14:35:27,736 ERROR [stderr] (MSC service thread 1-7) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
[line 158] 2016-10-25 14:35:27,737 ERROR [stderr] (MSC service thread 1-7) at java.lang.reflect.Method.invoke(Method.java:508)
[line 159] 2016-10-25 14:35:27,738 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.openssl.SSL.init(SSL.java:73)
[line 160] 2016-10-25 14:35:27,738 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.openssl.SSL.getInstance(SSL.java:49)
[line 161] 2016-10-25 14:35:27,739 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.openssl.OpenSSLEngine.<clinit>(OpenSSLEngine.java:59)
[line 162] 2016-10-25 14:35:27,740 ERROR [stderr] (MSC service thread 1-7) at java.lang.Class.forNameImpl(Native Method)
[line 163] 2016-10-25 14:35:27,741 ERROR [stderr] (MSC service thread 1-7) at java.lang.Class.forName(Class.java:348)
[line 164] 2016-10-25 14:35:27,742 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.OpenSSLAlpnProvider$1.run(OpenSSLAlpnProvider.java:47)
[line 165] 2016-10-25 14:35:27,743 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.OpenSSLAlpnProvider$1.run(OpenSSLAlpnProvider.java:43)
[line 166] 2016-10-25 14:35:27,754 ERROR [stderr] (MSC service thread 1-7) at java.security.AccessController.doPrivileged(AccessController.java:594)
[line 167] 2016-10-25 14:35:27,755 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.OpenSSLAlpnProvider.<clinit>(OpenSSLAlpnProvider.java:43)
[line 168] 2016-10-25 14:35:27,756 ERROR [stderr] (MSC service thread 1-7) at java.lang.J9VMInternals.newInstanceImpl(Native Method)
[line 169] 2016-10-25 14:35:27,757 ERROR [stderr] (MSC service thread 1-7) at java.lang.Class.newInstance(Class.java:1899)
[line 170] 2016-10-25 14:35:27,758 ERROR [stderr] (MSC service thread 1-7) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:391)
[line 171] 2016-10-25 14:35:27,759 ERROR [stderr] (MSC service thread 1-7) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:415)
[line 172] 2016-10-25 14:35:27,760 ERROR [stderr] (MSC service thread 1-7) at java.util.ServiceLoader$1.next(ServiceLoader.java:491)
[line 173] 2016-10-25 14:35:27,776 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.ALPNManager.<init>(ALPNManager.java:40)
[line 174] 2016-10-25 14:35:27,777 ERROR [stderr] (MSC service thread 1-7) at io.undertow.protocols.alpn.ALPNManager.<clinit>(ALPNManager.java:35)
[line 175] 2016-10-25 14:35:27,778 ERROR [stderr] (MSC service thread 1-7) at io.undertow.server.protocol.http.AlpnOpenListener.<init>(AlpnOpenListener.java:64)
[line 176] 2016-10-25 14:35:27,779 ERROR [stderr] (MSC service thread 1-7) at io.undertow.server.protocol.http.AlpnOpenListener.<init>(AlpnOpenListener.java:83)
[line 177] 2016-10-25 14:35:27,780 ERROR [stderr] (MSC service thread 1-7) at io.undertow.server.protocol.http.AlpnOpenListener.<init>(AlpnOpenListener.java:75)
[line 178] 2016-10-25 14:35:27,781 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.extension.undertow.HttpsListenerService.createAlpnOpenListener(HttpsListenerService.java:101)
[line 179] 2016-10-25 14:35:27,782 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.extension.undertow.HttpsListenerService.createOpenListener(HttpsListenerService.java:86)
[line 180] 2016-10-25 14:35:27,783 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:158)
[line 181] 2016-10-25 14:35:27,784 ERROR [stderr] (MSC service thread 1-7) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
[line 182] 2016-10-25 14:35:27,785 ERROR [stderr] (MSC service thread 1-7) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
[line 183] 2016-10-25 14:35:27,789 ERROR [stderr] (MSC service thread 1-7) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
[line 184] 2016-10-25 14:35:27,790 ERROR [stderr] (MSC service thread 1-7) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[line 185] 2016-10-25 14:35:27,791 ERROR [stderr] (MSC service thread 1-7) at java.lang.Thread.run(Thread.java:785)
[line 186] 2016-10-25 14:35:27,792 ERROR [stderr] (MSC service thread 1-7) Caused by: java.lang.UnsatisfiedLinkError: /tmp/tmp-317723765121491548openssl/libwfssl.so (/tmp/tmp-317723765121491548openssl/libwfssl.so: wrong ELF class: ELFCLASS64)
[line 187] 2016-10-25 14:35:27,794 ERROR [stderr] (MSC service thread 1-7) at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1344)
[line 188] 2016-10-25 14:35:27,794 ERROR [stderr] (MSC service thread 1-7) at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:1304)
[line 189] 2016-10-25 14:35:27,795 ERROR [stderr] (MSC service thread 1-7) at java.lang.System.loadLibrary(System.java:552)
[line 190] 2016-10-25 14:35:27,796 ERROR [stderr] (MSC service thread 1-7) at org.wildfly.openssl.SSL$LibraryLoader.load(SSL.java:180)
[line 191] 2016-10-25 14:35:27,797 ERROR [stderr] (MSC service thread 1-7) ... 31 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7569) Default certificate is generated on server boot
by Martin Choma (JIRA)
Martin Choma created WFLY-7569:
----------------------------------
Summary: Default certificate is generated on server boot
Key: WFLY-7569
URL: https://issues.jboss.org/browse/WFLY-7569
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Martin Choma
Assignee: Stuart Douglas
There is change of behavior of "SSL out of box" , AFAICT . Certificate is generated on boot, not on first access as intended.
* It slow down server start.
* contradicts {{WFLYDM0111: Keystore /wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost}}
Steps to reproduce:
1) build wildfly from master
2) unzip fresh distro
3) run ./standalone.sh
4) certificate is generated
full server log
{code}
[mchoma@localhost bin]$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/mchoma/workspace/eap-versions/wildfly-11.0.0.Alpha1-SNAPSHOT
JAVA: /usr/java/latest/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
15:01:54,487 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3
15:01:54,680 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final
15:01:54,739 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Core 3.0.0.Alpha11 "Kenny" starting
15:01:54,857 INFO [org.jboss.as.domain.management] (MSC service thread 1-2) WFLYDM0136: Registered OpenSSL provider
15:01:55,504 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-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 deprecation.
15:01:55,562 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
15:01:55,575 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.4.1.Final
15:01:55,582 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.4.1.Final
15:01:55,611 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
15:01:55,614 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
15:01:55,619 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
15:01:55,628 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
15:01:55,629 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
15:01:55,632 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
15:01:55,641 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
15:01:55,655 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.0.Alpha3
15:01:55,664 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
15:01:55,665 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
15:01:55,668 INFO [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
15:01:55,672 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.21.Final
15:01:55,679 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
15:01:55,688 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
15:01:55,719 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.4.Final starting
15:01:55,784 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path '/home/mchoma/workspace/eap-versions/wildfly-11.0.0.Alpha1-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
15:01:55,826 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
15:01:55,831 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
15:01:55,903 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
15:01:55,904 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
15:01:55,909 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
15:01:56,114 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
15:01:56,195 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none
15:01:56,220 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore /home/mchoma/workspace/eap-versions/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
15:01:56,231 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: Started FileSystemDeploymentService for directory /home/mchoma/workspace/eap-versions/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/deployments
15:01:56,364 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final
15:01:56,379 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,380 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,380 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,381 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,381 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,383 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,384 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,385 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,386 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,386 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,386 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,386 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,386 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:56,387 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
15:01:57,161 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0113: Generated self signed certificate at /home/mchoma/workspace/eap-versions/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/application.keystore. Please note that self signed certificates are not secure, and should only be used for testing purposes. Do not use this self signed certificate in production.
SHA-1 fingerprint of the generated key is c7:27:a2:1e:f5:86:77:47:f7:ac:01:f1:d3:54:ef:2c:a0:ed:ff:9c
SHA-256 fingerprint of the generated key is c9:69:8a:0d:3f:45:81:6f:42:be:2e:18:a8:ac:7f:d6:67:ea:60:3d:3e:53:67:f7:04:00:d0:cc:17:c4:94:3c
15:01:57,286 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
15:01:57,339 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.8)
15:01:57,439 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
15:01:57,440 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
15:01:57,440 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha11 "Kenny" started in 3168ms - Started 370 of 613 services (426 services are lazy, passive or on-demand)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-6971) MDB cannot be deployed after migration due to invalid cache configuration. Log a message in order to detect and reject any invalid configuration.
by Ladislav Thon (JIRA)
[ https://issues.jboss.org/browse/WFLY-6971?page=com.atlassian.jira.plugin.... ]
Ladislav Thon commented on WFLY-6971:
-------------------------------------
I realize I'm late to the party, this might have been mentioned elsewhere already once or twice, but I'll say it anyway:
1. If server configuration is migrated using Eduardo's JBoss Server Migration Tool, the tool actually rebuilds the relevant part of the configuration from scratch, so it's correct.
2. If server configuration is migrated purely by copying the old config file, starting a server in {{--admin-only}} and performing the {{:migrate}} operations, then the configuration of the {{ejb}} subsystem will be wrong. This is because there's no {{migrate}} operation for the {{ejb}} subsystem, so its "migration" consists only of parsing and serializing the old XML with a new XML parser/serializer.
I still believe that the fix should be like this: {{ejb}} subsystem's parser for old XML version will realize that the new server requires the configuration to look differently, emit a configuration that works and maybe log a message that it's being smart and configuration should probably be reviewed by a human.
> MDB cannot be deployed after migration due to invalid cache configuration. Log a message in order to detect and reject any invalid configuration.
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6971
> URL: https://issues.jboss.org/browse/WFLY-6971
> Project: WildFly
> Issue Type: Bug
> Components: EJB, JMS
> Affects Versions: 10.1.0.CR1
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
> Priority: Critical
> Attachments: mdb-1.0-SNAPSHOT.jar, standalone-full-ha.xml_eap6
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> If EAP 7 with (manually) migrated configuration from EAP 6.4.7.CP server is started then MDB deployment fails with:
> {code}
> 14:17:09,432 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".cache-dependencies-installer: org.jboss.msc.service.StartException in service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".cache-dependencies-installer: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_71]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_71]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_71]
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.infinispan.ejb."mdb-1.0-SNAPSHOT.jar".config is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.as.ejb3.cache.distributable.DistributableCacheFactoryBuilderService.installDeploymentUnitDependencies(DistributableCacheFactoryBuilderService.java:93)
> at org.jboss.as.ejb3.deployment.processors.CacheDependenciesProcessor$1.start(CacheDependenciesProcessor.java:50)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
> ... 3 more
> {code}
> Problem seems to be configuration of caches in ejb subsystem which looks like:
> {code}
> <subsystem xmlns="urn:jboss:domain:ejb3:4.0">
> ...
> <caches>
> <cache name="simple" aliases="NoPassivationCache"/>
> <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
> <cache name="clustered" passivation-store-ref="infinispan" aliases="StatefulTreeCache"/>
> </caches>
> ...
> </subsystem>
> {code}
> If any of lines:
> {code}
> <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
> <cache name="clustered" passivation-store-ref="infinispan"
> {code}
> is removed or I take default configuration from EAP 7:
> {code}
> <caches>
> <cache name="simple"/>
> <cache name="distributable" passivation-store-ref="infinispan" aliases="passivating clustered"/>
> </caches>
> {code}
> then MDB is deployed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (JBJCA-1329) No error message on concurrent processing of the same inflow transaction
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1329?page=com.atlassian.jira.plugin... ]
Stefano Maestri resolved JBJCA-1329.
------------------------------------
Resolution: Done
> No error message on concurrent processing of the same inflow transaction
> ------------------------------------------------------------------------
>
> Key: JBJCA-1329
> URL: https://issues.jboss.org/browse/JBJCA-1329
> Project: IronJacamar
> Issue Type: Bug
> Components: Core
> Affects Versions: WildFly/IronJacamar 1.3.4.Final
> Reporter: Ondra Chaloupka
> Assignee: Stefano Maestri
> Attachments: JcaInflowTransactionTestCase_multipleWorkSharedXidInBunch_jta_server.log
>
>
> I experience losing messages when they are received with the same xid when messages are received in parallel. This means case that prior message is not yet fully processed when meanwhile new message is promoted for being processed.
> This is the scenario which behaves wrong by my view
> * EIS passes a message with xid1 to RAR to be processed
> * first message is passed as work to be process (stays in progress)
> * EIS passes a second message with xid1 to RAR to be processed
> * the second message is forgotten. It will never reach a {{MessageListner}}
> ** no error is returned or shown in log
> Compared following scenario passes without a problem.
> * EIS passes a message with xid1 to RAR to be processed
> * first message is fully processed with {{MessageListner}} (it reaches the end of the _onMessage_ method)
> * EIS passes a second message with xid1 to RAR to be processed
> * second message is processed by {{MessageListener}}
> From logging I can see that work was cancelled [2] by call of WorkWrapper [1]. But any information is forgotten. There is no error message in the log and there is wrong type and listnener methods called ({{javax.resource.spi.work.WorkListener}} by {{workCompleted}} with work type defined with status 4) for such messages.
> If I do understand right the jca specification says that {{WorkCompletedException}} needs to be shown[3].
> [1] https://github.com/ironjacamar/ironjacamar/blob/1.3/core/src/main/java/or...
> [2]
> {code}
> 2016-08-25 09:28:32,688 TRACE [org.jboss.jca.core.workmanager.WorkWrapper] (default-threads - 4) Cancel work: WorkWrapper@1755d562[workManger=org.jboss.as.connector.services.workmanager.NamedWorkManager(a)dcb0b17[id=org.jboss.as.test.jbossts.crashrec.jca.rar.TestResourceAdapter-default name=default specCompliant=true shortRunningExecutor=org.jboss.jca.core.workmanager.StatisticsExecutorImpl@5c446e25 longRunningExecutor=org.jboss.jca.core.workmanager.StatisticsExecutorImpl@170ccc4f xaTerminator=org.jboss.jca.core.tx.jbossts.XATerminatorImpl@57da418e validatedWork=[org.jboss.as.test.jbossts.crashrec.jca.rar.TxnWork, org.jboss.as.test.jbossts.crashrec.jca.rar.TestResourceTxnWorkUnit] callbackSecurity=null securityIntegration=org.jboss.jca.core.security.picketbox.PicketBoxSecurityIntegration@78ad9dc3 resourceAdapter=org.jboss.as.test.jbossts.crashrec.jca.rar.TestResourceAdapter@fc1a5071 shutdown=false activeWorkWrappers=[WorkWrapper@5715513d] statistics=WorkManagerStatistics@71bdb84[active=1 successful=6 failed=0 doWorkAccepted=0 doWorkRejected=0 scheduleWorkAccepted=6 scheduleWorkRejected=0 startWorkAccepted=0 startWorkRejected=0]] work=org.jboss.as.test.jbossts.crashrec.jca.rar.TxnWork@241d1e13 xid=formatId=4660 gtrid(64)={0x7f00000100000000010000002a000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000} bqual(64)={0x7f00000100000000010000002a000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000} txTimeout=-1 workListener=org.jboss.as.test.jbossts.crashrec.jca.rar.TestResourceWorkListner@40b572b1 workContexts=null exception=javax.resource.spi.work.WorkCompletedException: ARJUNA016068: Work already active!, error code: 2]
> {code}
> [3]
> {quote}
> The application server must reject Work submissions for a transaction whosecompletion is in-progress, with a WorkCompletedException set to the errorcode WorkException.TX_CONCURRENT_WORK_DISALLOWED.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (DROOLS-1358) No sorting of the field names in the guided rules.
by Petr Farmakovsky (JIRA)
Petr Farmakovsky created DROOLS-1358:
----------------------------------------
Summary: No sorting of the field names in the guided rules.
Key: DROOLS-1358
URL: https://issues.jboss.org/browse/DROOLS-1358
Project: Drools
Issue Type: Bug
Components: kie server
Affects Versions: 6.3.0.Final
Reporter: Petr Farmakovsky
Assignee: Edson Tirelli
Attachments: Field names.gif
We use the Drools Workbench 6.3.0 Final. Our Data Object may consist of more than 20 fields. When writing rules, such as Guided Rules and when adding the object into the rule all fields are displayed unsorted: !Field names.gif!
We are aware of @org.kie.api.definition.type.Position parameter of the field in the Data Object, but it does not solve our problem.
How can we activate the sorting?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7210) Expose JAX-RS resources as children of the subsystem
by Guillermo González de Agüero (JIRA)
[ https://issues.jboss.org/browse/WFLY-7210?page=com.atlassian.jira.plugin.... ]
Guillermo González de Agüero commented on WFLY-7210:
----------------------------------------------------
Hi [~gaol]! I've tested WFLY-7024 from the latest build, but I think the current solution is too verbose, at least for the Web Console. See attached "after-wfly7024.png" file. That's for a resource with just 3 paths, one of them being a subresource locator.
What do you think about making resource-paths and subresource-locators children of rest-resource element? That way the current JSON could be transformed into attributes of the element. That would make it really easier to read and parse.
> Expose JAX-RS resources as children of the subsystem
> ----------------------------------------------------
>
> Key: WFLY-7210
> URL: https://issues.jboss.org/browse/WFLY-7210
> Project: WildFly
> Issue Type: Feature Request
> Components: REST
> Affects Versions: 10.1.0.Final
> Reporter: Guillermo González de Agüero
> Assignee: Lin Gao
> Attachments: after-wfly7024.png, hal-jaxrs.png
>
>
> Servlets, EJBs, WebSockets, JPA, etc expose its components as children of the subsystem in the management API. For example to list the stateless EJBs of a deployment:
> [standalone@localhost:9990 /] /deployment=cdivsejb.war/subsystem=ejb3:read-children-resources(child-type=stateless-session-bean)
> This makes it specially easy to navigate trough the web console (attached screenshot).
> To read JAX-RS resources, the command would be:
> [standalone@localhost:9990 /] /deployment=cdivsejb.war/subsystem=jaxrs:show-resources()
> I propose to make deprecate the show-resources operation and create a new "resources" child, containing the Rest resources.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months