[JBoss JIRA] (WFLY-12458) WebServices tests failing in IBM JDK8
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12458?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-12458:
---------------------------------
Fix Version/s: (was: 18.0.0.Final)
> WebServices tests failing in IBM JDK8
> -------------------------------------
>
> Key: WFLY-12458
> URL: https://issues.jboss.org/browse/WFLY-12458
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Environment: java version "1.8.0_211"
> Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled)
> OpenJ9 - 46e57f9
> OMR - 06a046a
> IBM - 0b909bf)
> JCL - 20190409_01 based on Oracle jdk8u211-b25
> Reporter: Richard Opalka
> Assignee: Jim Ma
> Priority: Major
>
> [ERROR] EJBSignTestCase.signedRequest:86 » SOAPFault MustUnderstand headers: [{http://...
> [ERROR] SignTestCase.signedRequest:88 » SOAPFault MustUnderstand headers: [{http://doc...
> [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:90 » SOAPFault
> [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:102 » SOAPFault
> [ERROR] EJBSignEncryptTestCase.encryptedAndSignedRequest:88 » SOAPFault MustUnderstand...
> [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:91 » SOAPFault
> [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:103 » SOAPFault
> [ERROR] SignEncryptTestCase.encryptedAndSignedRequest:90 » SOAPFault MustUnderstand he...
> [ERROR] WSBearerElytronSecurityPropagationTestCase.testBearer:133 » SOAPFault MustUnde...
> [ERROR] WSBearerSecurityPropagationTestCase.testBearer:133 » SOAPFault MustUnderstand ...
> [ERROR] WSTrustTestCase.test:319 » SOAPFault MustUnderstand headers: [{http://docs.oas...
> [ERROR] WSTrustTestCase.testActAs:442 » SOAPFault MustUnderstand headers: [{http://doc...
> [ERROR] WSTrustTestCase.testBearer:553 » SOAPFault MustUnderstand headers: [{http://do...
> [ERROR] WSTrustTestCase.testHolderOfKey:494 » SOAPFault MustUnderstand headers: [{http...
> [ERROR] WSTrustTestCase.testNoClientCallback:384 » SOAPFault MustUnderstand headers: [...
> [ERROR] WSTrustTestCase.testNoSignatureUsername:415 » SOAPFault MustUnderstand headers...
> [ERROR] WSTrustTestCase.testOnBehalfOf:469 » SOAPFault MustUnderstand headers: [{http:...
> [ERROR] WSTrustTestCase.testPicketLink:526 » SOAPFault MustUnderstand headers: [{http:...
> [ERROR] WSTrustTestCase.testUsingEPR:351 » SOAPFault MustUnderstand headers: [{http://...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-12085) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ]
James Perkins resolved WFLY-12085.
----------------------------------
Fix Version/s: 18.0.0.Final
Resolution: Done
> java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12085
> URL: https://issues.jboss.org/browse/WFLY-12085
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 17.0.0.Alpha1, 17.0.0.Final
> Environment: Red Hat JBoss Enterprise Application Platform
> 7.2.1
> Microsoft Windows 10
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Labels: downstream_dependency
> Fix For: 18.0.0.Final
>
>
> There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup:
> {noformat}
> 2019-05-13 11:45:11,419 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parse(URI.java:3058)
> at java.net.URI.<init>(URI.java:588)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369)
> at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544)
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481)
> at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206)
> at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65)
> at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {noformat}
> This issue only affects Microsoft Windows platform.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-10968) Backup doesn't activate after shared store is reconnected
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10968?page=com.atlassian.jira.plugin... ]
James Perkins resolved WFLY-10968.
----------------------------------
Fix Version/s: 18.0.0.Final
Resolution: Done
> Backup doesn't activate after shared store is reconnected
> ---------------------------------------------------------
>
> Key: WFLY-10968
> URL: https://issues.jboss.org/browse/WFLY-10968
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 14.0.0.Final
> Environment: NFS configuration
> {noformat}
> messaging-10.jbm.lab.bos.redhat.com:/hornetq on /mnt/hornetq/client type nfs4 (rw,nosuid,nodev,relatime,sync,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,soft,noac,nosharecache,proto=tcp,timeo=50,retrans=5,sec=sys,clientaddr=10.16.100.40,lookupcache=none,local_lock=none,addr=10.16.100.24)
> {noformat}
> Java version
> {noformat}
> java version "1.8.0_151"
> Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode
> {noformat}
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 18.0.0.Final
>
>
> *Scenario*
> # Start live backup server pair in dedicated topology with shared store HA, with journal located on NFS
> # NFS mounted on backup server fails
> # Reconnect NFS on backup server
> # Try to shut down live EAP server
> # Backup doesn't activate
> *What happens*
> Backup is waiting for live to fail by checking its file lock. In case the connection to shared storage fails, backup logs following error.
> {noformat}
> 05:50:57,896 ERROR [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=836c9b1e-f067-11e7-8763-001b21862475) AMQ224000: Failure in initialisation: java.io.IOException: Input/output error
> at sun.nio.ch.FileDispatcherImpl.lock0(Native Method) [rt.jar:1.8.0_151]
> at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:90) [rt.jar:1.8.0_151]
> at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1115) [rt.jar:1.8.0_151]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.tryLock(FileLockNodeManager.java:299) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.lock(FileLockNodeManager.java:316) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.FileLockNodeManager.awaitLiveNode(FileLockNodeManager.java:127) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation.run(SharedStoreBackupActivation.java:77) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:2496) [artemis-server-1.5.5.008-redhat-1.jar:1.5.5.008-redhat-1]
> {noformat}
> Exception is caught in {{SharedStoreBackupActivation.run}}, and causes termination of backup activation process.
> In case the NFS is reconnected later, backup server doesn't continue in activation process and it doesn't wait for live to fail. In case the live fails, backup doesn't activate, even though it has a connection to shared storage.
> Backup should retry checking live lock even in case the storage is unavailable. It should log warning/error messages that storage is unavailable, but it should not terminate the activation process. This would allow backup to continue its duties when the storage is reconnected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4565) MVELDialectRuntimeData is not thread safe
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4565?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-4565.
---------------------------------
Resolution: Done
Fixed by https://github.com/kiegroup/drools/commit/cf0adb03130b1db34725ce3330630c5...
> MVELDialectRuntimeData is not thread safe
> -----------------------------------------
>
> Key: DROOLS-4565
> URL: https://issues.jboss.org/browse/DROOLS-4565
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.16.0.Final
> Environment: Java 11.0.2
> Different OS
> Reporter: Timo Gutjahr
> Assignee: Mario Fusco
> Priority: Major
> Attachments: ForkJoinPool-1-worker-1.txt, NPE.txt, main.txt
>
>
> MVELDialectRuntimeData#mvelReaders is accessed concurrently but is not thread safe due to the usage of a HashSet. This may cause lost updates. (See [^ForkJoinPool-1-worker-1.txt] and [^main.txt] )
> If this happens and the kie base is serialized and deserialized it results in a NullPointerException at runtime. (See [^NPE.txt] )
> We observed that the entries in this Set (mvelReaders) are serialized and important for the deserialization step because they contain information about transient objects that have to be re-initialized after deserialization.
> While losing this information due to concurrent access does not cause problems during compilation, serialization and deserialization of a kie base, they may cause NullPointerExceptions at runtime when transient fields remain uninitialized.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (LOGMGR-124) Add marker support
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ]
James Perkins commented on LOGMGR-124:
--------------------------------------
Unfortunately this has not yet been looked at due to it's large impact. The log manager itself would require marker support. Then JBoss Logging would need to be updated to support it in a way which does not break compatibility. Our fork of log4j would need to be updated as well followed by the slf4j bridge. Again both of those would need to done in a way to not break backwards compatibility.
As far as changing the log manager implementation in WildFly. It _may_ be possible, but I haven't tried it. You'd need to remove the logging subsystem. Then you'd need to edit the {{jboss-logmanager-*.jar}} and remove the {{META-INF/services/java.util.logging.LogManager}} service file. You'd then need to ensure that somehow the new log manager ends up visible. It would likely have to be on the boot class path would be my guess. If this works it would only work for standalone as well. Domain mode requires the JBoss Log Manager.
> Add marker support
> ------------------
>
> Key: LOGMGR-124
> URL: https://issues.jboss.org/browse/LOGMGR-124
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Components: core
> Affects Versions: 2.0.2.Final
> Reporter: Rob Heine
> Priority: Optional
>
> The logging engine currently (talking about the one included in WF-9) does not support Markers (like in implementations like "logback" and/or "log4j2").
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years