May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1573) Docs 4.2.3.4. - Remove guidance on deleted maven features

by Russell Morrisey (JIRA)

Russell Morrisey created DROOLS-1573: ---------------------------------------- Summary: Docs 4.2.3.4. - Remove guidance on deleted maven features Key: DROOLS-1573 URL: https://issues.jboss.org/browse/DROOLS-1573 Project: Drools Issue Type: Enhancement Components: docs Environment: Google Chrome Reporter: Russell Morrisey Assignee: Mario Fusco According to the linked StackOverflow item, maven 3+ does not support the LATEST or RELEASE features. If this is true, the maven versioning guidance in the Drools docs should be updated accordingly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2859) Remove remaining deprecated ManagementResourceRegistration.Factory items

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2859: ---------------------------------------- Summary: Remove remaining deprecated ManagementResourceRegistration.Factory items Key: WFCORE-2859 URL: https://issues.jboss.org/browse/WFCORE-2859 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 4.0.0.Alpha1 Remove the few items that I decided not to remove in WFCORE-2831 because they hadn't been deprecated for a release yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1572) Figure 4.2. Example POM shows old maven group/artifactId

by Russell Morrisey (JIRA)

Russell Morrisey created DROOLS-1572: ---------------------------------------- Summary: Figure 4.2. Example POM shows old maven group/artifactId Key: DROOLS-1572 URL: https://issues.jboss.org/browse/DROOLS-1572 Project: Drools Issue Type: Enhancement Components: docs Affects Versions: 7.0.0.CR3, 6.5.0.Final Environment: Google Chrome Reporter: Russell Morrisey Assignee: Mario Fusco In the Drools documentation, figure 4.2 (*Example project layout and Maven POM*) shows the wrong groupId and artifactId. The correct artifact is: {code:java} org.kie:kie-maven-plugin:${runtime.version} {code} In addition, the new plugin causes an error in Eclipse unless a section is added to the POM for the eclipse lifecycle-mapping plugin. https://docs.jboss.org/drools/release/latest/drools-docs/html_single/#_bu... https://stackoverflow.com/questions/26122801/m2e-connector-for-kie-maven-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2858) Roll out READ_ONLY + RUNTIME_ONLY ops to the domain

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2858: ---------------------------------------- Summary: Roll out READ_ONLY + RUNTIME_ONLY ops to the domain Key: WFCORE-2858 URL: https://issues.jboss.org/browse/WFCORE-2858 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Required for WFCORE-389. OperationRouting currently treats all READ_ONLY ops on domain-wide resources as requiring local execution only (except those with the rare, kernel-only DOMAIN_PUSH_TO_SERVERS flag.) We need to change this so READ_ONLY ops that are also declared to be RUNTIME_ONLY go through the 2 -phase path. This may also require changes to ServerOperationsResolverHandler.getServerOperations which is doing a similar READ_ONLY && !DOMAIN_PUSH_TO_SERVERS check. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1186) Elytron - authentication fails when a realm name is not specified for DIGEST-MD5 mechanism on server side

by Josef Cacek (JIRA)

Josef Cacek created ELY-1186: -------------------------------- Summary: Elytron - authentication fails when a realm name is not specified for DIGEST-MD5 mechanism on server side Key: ELY-1186 URL: https://issues.jboss.org/browse/ELY-1186 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Blocker When a default configuration is used for DIGEST-MD5 SASL mechanism, then server suggest hostname as a realm name, but authentication fails because ServerAuthenticationContext checks mechanism configuration and fails with following exception: {code} @Message(id = 1092, value = "Invalid mechanism realm selection \"%s\"") IllegalArgumentException invalidMechRealmSelection(String realmName); {code} *Suggested fix:* If the server suggests realm name, then it should be able to consume it. Or if the realm name is really mandatory, then server should not suggest such a default value. IMO allowing such a default and simplifying configuration would have positive impact on user experience. The full stacktrace (hidden): {noformat} javax.security.sasl.SaslException: ELY05053: [DIGEST-MD5] Callback handler failed for unknown reason [Caused by java.lang.IllegalArgumentException: ELY01092: Invalid mechanism realm selection "localhost"] at org.wildfly.security.sasl.util.AbstractSaslParticipant.tryHandleCallbacks(AbstractSaslParticipant.java:105) at org.wildfly.security.sasl.digest.AbstractDigestMechanism.getPredigestedSaltedPassword(AbstractDigestMechanism.java:482) at org.wildfly.security.sasl.digest.DigestSaslServer.validateDigestResponse(DigestSaslServer.java:259) at org.wildfly.security.sasl.digest.DigestSaslServer.evaluateMessage(DigestSaslServer.java:355) at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180) at org.wildfly.security.sasl.digest.DigestSaslServer.evaluateResponse(DigestSaslServer.java:328) at org.wildfly.security.sasl.util.AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(AuthenticationCompleteCallbackSaslServerFactory.java:58) at org.wildfly.security.sasl.util.AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(AuthenticationTimeoutSaslServerFactory.java:106) at org.wildfly.security.sasl.util.SecurityIdentitySaslServerFactory$1.evaluateResponse(SecurityIdentitySaslServerFactory.java:57) at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245) at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217) at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:470) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:897) 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) Caused by: java.lang.IllegalArgumentException: ELY01092: Invalid mechanism realm selection "localhost" at org.wildfly.security.auth.server.ServerAuthenticationContext$InitialState.setMechanismRealmName(ServerAuthenticationContext.java:1615) at org.wildfly.security.auth.server.ServerAuthenticationContext.setMechanismRealmName(ServerAuthenticationContext.java:712) at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:927) at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:735) at org.wildfly.security.sasl.util.TrustManagerSaslServerFactory.lambda$createSaslServer$0(TrustManagerSaslServerFactory.java:96) at org.wildfly.security.sasl.util.AbstractSaslParticipant.tryHandleCallbacks(AbstractSaslParticipant.java:101) ... 15 more {noformat} Attached also server configuration and WireShark log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8432) Support socket-binding attribute "client-mapping" in messaging subsystem

by Heribert Steuer (JIRA)

[ https://issues.jboss.org/browse/WFLY-8432?page=com.atlassian.jira.plugin.... ] Heribert Steuer edited comment on WFLY-8432 at 5/22/17 3:34 PM: ---------------------------------------------------------------- Hello Bartosz, thanks alot for this patch, it pretty much solves the issue with the missing outbound mapping. I have successfully ran JMS through an Apache reverse proxy. Unfortunately it did not work when the proxy did SSL offloading, but thats another story. Thanks alot for your work, Cheers! was (Author: patronas): Hello Bartosz, thanks alot for this patch. I have applied your changed to the 10.x branch and did some tests to run the jmx quickstart project through the proxy. Running the test without the reverse proxy works well, after adding the appropriate client-mapping attribute to the socket-binding and looping traffic through the proxy leads to exceptions at the client level (see below). Is there probably anything missing in order to run JMS through a reverse proxy? After a successful looking up the queue using JNDI, the client throws the following exception: bq. Exception in thread "main" javax.jms.JMSRuntimeException: Failed to create session factory bq. at org.apache.activemq.artemis.jms.client.JmsExceptionUtils.convertToRuntimeException(JmsExceptionUtils.java:88) bq. at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:262) bq. at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:248) bq. at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.makeJmsCall(RemoteEJBClient.java:320) bq. at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:56) bq. Caused by: javax.jms.JMSException: Failed to create session factory bq. at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:727) bq. at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:255) bq. ... 3 more bq. Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] bq. at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:778) bq. at org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:724) bq. ... 4 more > Support socket-binding attribute "client-mapping" in messaging subsystem > ------------------------------------------------------------------------ > > Key: WFLY-8432 > URL: https://issues.jboss.org/browse/WFLY-8432 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jörg Bäsner > Assignee: Bartosz Spyrko-Śmietanko > Fix For: 11.0.0.Beta1 > > > The messaging subsystem doesn't take into account the "client-mapping" attribute of the <socket-binding> when creating a <http-connector>. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-1) [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-1?page=com.atlassian.jira.plug... ] Hayk Hovsepyan commented on HAWKULARQE-1: ----------------------------------------- Blocker issue was found: https://bugzilla.redhat.com/show_bug.cgi?id=1452118 > [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers > ---------------------------------------------------------------------------------- > > Key: HAWKULARQE-1 > URL: https://issues.jboss.org/browse/HAWKULARQE-1 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-111|https://issues.jboss.org/browse/JMAN4-111] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-6) [QE] - JMAN4-159 - OpenShift EAP 7 Docker image with Hawkular Agent

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-6?page=com.atlassian.jira.plug... ] Hayk Hovsepyan resolved HAWKULARQE-6. ------------------------------------- Release Notes Text: Test is done on a build brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7/eap70-openshift:1.5 No regression or any BZ was found. Resolution: Done > [QE] - JMAN4-159 - OpenShift EAP 7 Docker image with Hawkular Agent > ------------------------------------------------------------------- > > Key: HAWKULARQE-6 > URL: https://issues.jboss.org/browse/HAWKULARQE-6 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-159|https://issues.jboss.org/browse/JMAN4-159] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2857) Usage of wildfly.sasl.local-user.default-user in core configuration files

by Ken Wills (JIRA)

Ken Wills created WFCORE-2857: --------------------------------- Summary: Usage of wildfly.sasl.local-user.default-user in core configuration files Key: WFCORE-2857 URL: https://issues.jboss.org/browse/WFCORE-2857 Project: WildFly Core Issue Type: Task Components: Domain Management, Test Suite Reporter: Ken Wills Assignee: Ken Wills Fix For: 3.0.0.CR1 The property wildfly.sasl.local-user.default-user is present in some, commented out on other, and absent from some default configuation files in core. (the default host-slave.xml for example has it, but it appears to have no effect if removed). There is uneven usage of it throughout the testsuite config files. We should review and make the usage (or non-usage) consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-17) Automation Testcase

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-17?page=com.atlassian.jira.plu... ] Hayk Hovsepyan resolved HAWKULARQE-17. -------------------------------------- Release Notes Text: Automation test will be executed in a scope of task https://issues.jboss.org/browse/HAWKULARQE-11 Resolution: Done > Automation Testcase > ------------------- > > Key: HAWKULARQE-17 > URL: https://issues.jboss.org/browse/HAWKULARQE-17 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: hawkular-qe-automation > > * Automate openshift eap7 docker container starting in preparation scripts > * In CFME CI > * Add openshift into CFME > * Verify discovery of EAP7, run smoke set of tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2017