[JBoss JIRA] (WFCORE-4049) Deactivate modular jdk properties we used in the past for workarounds.
by Richard Opalka (JIRA)
Richard Opalka created WFCORE-4049:
--------------------------------------
Summary: Deactivate modular jdk properties we used in the past for workarounds.
Key: WFCORE-4049
URL: https://issues.jboss.org/browse/WFCORE-4049
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: 6.0.0.CR3
In the past we used the following properties:
-Dsun.util.logging.disableCallerCheck=true
-Djdk.attach.allowAttachSelf=true
to activate some workarounds on modular JDKs.
These workarounds are not needed anymore.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1639:
-----------------------------------
I can confirm I am able to perform 2-way SSL handshake in FIPS mode using PKCS11 with <key-store-ssl-certificate algorithm="SunX509" key-store-name="keystore" /> With and without alias.
There is still one "but", but I will create another issue for that as it seems is distinct problem.
> FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used
> -------------------------------------------------------------
>
> Key: ELY-1639
> URL: https://issues.jboss.org/browse/ELY-1639
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Blocker
> Attachments: cli-wildfly-config.xml
>
>
> Fix of ELY-1622 introduced regression. It is not possible to do 1 way ssl (no key-store-ssl-certificate in wildfly-config.xml) with exception
> {code}
> 14:13:56,143 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45)
> at org.jboss.modules.Module.run(Module.java:352)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:593)
> Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost'
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328)
> ... 5 more
> Caused by: java.io.IOException: Failed to obtain SSLContext
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156)
> at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222)
> ... 8 more
> Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used
> at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149)
> at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66)
> at javax.net.ssl.SSLContext.init(SSLContext.java:282)
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53)
> at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221)
> at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208)
> at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153)
> ... 10 more
> {code}
> It is because after fix Fix of ELY-1622 custom keymanager is used. But it is forbidden by jdk FIPS PKCS11.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-12) [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1
by Martin Styk (JIRA)
[ https://issues.jboss.org/browse/WFWIP-12?page=com.atlassian.jira.plugin.s... ]
Martin Styk closed WFWIP-12.
----------------------------
Resolution: Done
> [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1
> -------------------------------------------------------------------------------------------
>
> Key: WFWIP-12
> URL: https://issues.jboss.org/browse/WFWIP-12
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis, JMS
> Reporter: Martin Styk
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
> Original Estimate: 2 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> Output of CLI operations in messaging subsystem's server element changed and it is is missing some attributes it used to display in EAP 7.1.
> _Affected operations_
> *list-all-consumers-as-json* and *list-consumers-as-json*
> Missing attributes
> * destinationName
> * destinationType
> * durable
> {noformat:title="7.1.0.GA"}
> Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"-733935378\",\"sessionID\":\"fede1b60-04e9-11e8-9641-cc3d825a3be2\",\"queueName\":\"testSubscriberClientId-hornetqCliOperations.testSubscriber-hqServerCliOperations\",\"browseOnly\":false,\"creationTime\":1517226368495,\"destinationName\":\"testTopic\",\"destinationType\":\"topic\",\"durable\":true}]"}
> {noformat}
> {noformat:title="Wildfly latest with artemis 2.x"}
> Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"784f1287\",\"sessionID\":\"f146b48e-04e3-11e8-bb50-cc3d825a3be2\",\"queueName\":\"jms.queue.testQueue\",\"browseOnly\":false,\"creationTime\":1517223768695,\"deliveringCount\":8}]"}
> {noformat}
> *list-connections-as-json*
> Missing attributes
> * clientID
> {noformat:title="7.1.0.GA"}
> "result" => "[{\"connectionID\":\"1343044951\",\"clientAddress\":\"/127.0.0.1:57038\",\"creationTime\":1517303830995,\"clientID\":\"testSubscriberClientId-hornetqCliOperations\"},{\"connectionID\":\"2052915500\",\"clientAddress\":\"/127.0.0.1:57040\",\"creationTime\":1517303831216},{\"connectionID\":\"668896556\",\"clientAddress\":\"/127.0.0.1:57042\",\"creationTime\":1517303831210},{\"connectionID\":\"2096792561\",\"clientAddress\":\"/127.0.0.1:57044\",\"creationTime\":1517303831223,\"clientID\":\"testPublisherClientId\"}]"
> {noformat}
> {noformat:title="Wildfly latest with artemis 2.x"}
> "result" => "[{\"connectionID\":\"a8842f44\",\"clientAddress\":\"/127.0.0.1:55938\",\"creationTime\":1517298838294,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"c515bc06\",\"clientAddress\":\"/127.0.0.1:55936\",\"creationTime\":1517298837454,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"b9a9153f-0592-11e8-80ff-54ee7547c83e\",\"clientAddress\":\"invm:0\",\"creationTime\":1517298837312,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"fe42578a\",\"clientAddress\":\"/127.0.0.1:55944\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"cde89186\",\"clientAddress\":\"/127.0.0.1:55940\",\"creationTime\":1517298838493,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"480099e7\",\"clientAddress\":\"/127.0.0.1:55942\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2}]"
> {noformat}
> This is compatibility issue, as some scripts may depend on missing attributes. Customer's tooling which used to work with 7.1 may not work now.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-12) [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1
by Martin Styk (JIRA)
[ https://issues.jboss.org/browse/WFWIP-12?page=com.atlassian.jira.plugin.s... ]
Martin Styk commented on WFWIP-12:
----------------------------------
I've tested with [~ehugonnet]'s branch https://github.com/ehsavoie/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_... and it works now.
> [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1
> -------------------------------------------------------------------------------------------
>
> Key: WFWIP-12
> URL: https://issues.jboss.org/browse/WFWIP-12
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis, JMS
> Reporter: Martin Styk
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
> Original Estimate: 2 hours
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> Output of CLI operations in messaging subsystem's server element changed and it is is missing some attributes it used to display in EAP 7.1.
> _Affected operations_
> *list-all-consumers-as-json* and *list-consumers-as-json*
> Missing attributes
> * destinationName
> * destinationType
> * durable
> {noformat:title="7.1.0.GA"}
> Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"-733935378\",\"sessionID\":\"fede1b60-04e9-11e8-9641-cc3d825a3be2\",\"queueName\":\"testSubscriberClientId-hornetqCliOperations.testSubscriber-hqServerCliOperations\",\"browseOnly\":false,\"creationTime\":1517226368495,\"destinationName\":\"testTopic\",\"destinationType\":\"topic\",\"durable\":true}]"}
> {noformat}
> {noformat:title="Wildfly latest with artemis 2.x"}
> Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"784f1287\",\"sessionID\":\"f146b48e-04e3-11e8-bb50-cc3d825a3be2\",\"queueName\":\"jms.queue.testQueue\",\"browseOnly\":false,\"creationTime\":1517223768695,\"deliveringCount\":8}]"}
> {noformat}
> *list-connections-as-json*
> Missing attributes
> * clientID
> {noformat:title="7.1.0.GA"}
> "result" => "[{\"connectionID\":\"1343044951\",\"clientAddress\":\"/127.0.0.1:57038\",\"creationTime\":1517303830995,\"clientID\":\"testSubscriberClientId-hornetqCliOperations\"},{\"connectionID\":\"2052915500\",\"clientAddress\":\"/127.0.0.1:57040\",\"creationTime\":1517303831216},{\"connectionID\":\"668896556\",\"clientAddress\":\"/127.0.0.1:57042\",\"creationTime\":1517303831210},{\"connectionID\":\"2096792561\",\"clientAddress\":\"/127.0.0.1:57044\",\"creationTime\":1517303831223,\"clientID\":\"testPublisherClientId\"}]"
> {noformat}
> {noformat:title="Wildfly latest with artemis 2.x"}
> "result" => "[{\"connectionID\":\"a8842f44\",\"clientAddress\":\"/127.0.0.1:55938\",\"creationTime\":1517298838294,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"c515bc06\",\"clientAddress\":\"/127.0.0.1:55936\",\"creationTime\":1517298837454,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"b9a9153f-0592-11e8-80ff-54ee7547c83e\",\"clientAddress\":\"invm:0\",\"creationTime\":1517298837312,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"fe42578a\",\"clientAddress\":\"/127.0.0.1:55944\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"cde89186\",\"clientAddress\":\"/127.0.0.1:55940\",\"creationTime\":1517298838493,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"480099e7\",\"clientAddress\":\"/127.0.0.1:55942\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2}]"
> {noformat}
> This is compatibility issue, as some scripts may depend on missing attributes. Customer's tooling which used to work with 7.1 may not work now.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-21) [Artemis 2.x upgrade] Lost message when MDB is resending messages under high load
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFWIP-21?page=com.atlassian.jira.plugin.s... ]
Erich Duda commented on WFWIP-21:
---------------------------------
I can see this issue with last provided build. The issue appeared in test {{Lodh5DoubleSendToDbTestCase#testORACLE11GR2MdbShutdownLargeMessages}}. The test failed because there was one missing record in the DB. See \[1\] for details.
\[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag...
> [Artemis 2.x upgrade] Lost message when MDB is resending messages under high load
> ---------------------------------------------------------------------------------
>
> Key: WFWIP-21
> URL: https://issues.jboss.org/browse/WFWIP-21
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> Test scenario:
> * Start cluster A of nodes node-1, node-3
> * Start cluster B of nodes node-2, node-4
> * Send messages to queue on node-1
> * Deploy mdbs to servers in cluster A. This mdb reads messages from local queue, sends them to remote queue on cluster B and inserts them into database
> * Deploy mdbs to servers in cluster B. This mdb reads messages from local queue and inserts them into database
> * Cause CPU overload (for 5 min) on server node-2 when mdbs on cluster1 and 2 are processing mesages
> * Restart failed server
> * Let MDBs to process remaining messages
> Pass Criteria: Number of sent message is equal number of records(lines) in database and messages in
> Actual Result:
> Sometimes happens that one record is missing in database which means that one message was not processed be MDB in cluster 2.
> This looks like broker related regression against Artemis 1.5.
> Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a)
> Artemis tag 2.5.0.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months