August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2899) Implement infinite grid scrolling in Scenario Simulation Grid

by Daniele Zonca (JIRA)

Daniele Zonca created DROOLS-2899: ------------------------------------- Summary: Implement infinite grid scrolling in Scenario Simulation Grid Key: DROOLS-2899 URL: https://issues.jboss.org/browse/DROOLS-2899 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Gabriele Cardosi Implement infinite canvas scrolling for the Grid using the same/a similar approach of DMN Decision Table -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[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 managed to reproduce the issue with Arjuna traces - https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/mnovak-verifier-... > [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

1
0
0 / 0

[JBoss JIRA] (SECURITY-573) Improve handling of IOException thrown from NegotiationAuthenticator

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-573?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-573: ----------------------------------------- Assignee: (was: Darran Lofthouse) > Improve handling of IOException thrown from NegotiationAuthenticator > -------------------------------------------------------------------- > > Key: SECURITY-573 > URL: https://issues.jboss.org/browse/SECURITY-573 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_2.0.3.GA > Environment: JBoss EPP 5.1.GA with SPNEGO support, JBoss Negotiation 2.0.3, commons-http-client 3.1 used as HTTP client > Reporter: Marek Posolda > > Currently if IOException is thrown from NegotiationAuthenticator (For example from line 123 from statement: NegotiationMessage requestMessage = mf.createMessage(authTokenIS); ) > then this exception is never logged but it's catched and ignored in CoyoteAdapter.service. Result is that client receives response code 200 OK and emtpy HTTP response. And there is nothing in server log, which can be used to recognize error. So I need to debug if I want to find the real cause of IO issue. > Example for simulating of this issue can be using of Kerberos OID instead of SPNEGO OID as described in Jira SECURITY-572 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-573) Improve handling of IOException thrown from NegotiationAuthenticator

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-573?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-573: -------------------------------------- Fix Version/s: (was: Negotiation_2_1_7) > Improve handling of IOException thrown from NegotiationAuthenticator > -------------------------------------------------------------------- > > Key: SECURITY-573 > URL: https://issues.jboss.org/browse/SECURITY-573 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_2.0.3.GA > Environment: JBoss EPP 5.1.GA with SPNEGO support, JBoss Negotiation 2.0.3, commons-http-client 3.1 used as HTTP client > Reporter: Marek Posolda > > Currently if IOException is thrown from NegotiationAuthenticator (For example from line 123 from statement: NegotiationMessage requestMessage = mf.createMessage(authTokenIS); ) > then this exception is never logged but it's catched and ignored in CoyoteAdapter.service. Result is that client receives response code 200 OK and emtpy HTTP response. And there is nothing in server log, which can be used to recognize error. So I need to debug if I want to find the real cause of IO issue. > Example for simulating of this issue can be using of Kerberos OID instead of SPNEGO OID as described in Jira SECURITY-572 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-473) Add documentation for IBM JRE

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-473?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-473: ----------------------------------------- Assignee: (was: Darran Lofthouse) > Add documentation for IBM JRE > ----------------------------- > > Key: SECURITY-473 > URL: https://issues.jboss.org/browse/SECURITY-473 > Project: PicketBox > Issue Type: Task > Components: Documentation, Negotiation > Affects Versions: Negotiation_2.0.3.SP2 > Reporter: Darran Lofthouse > > Add documentation for IBM JRE > http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rz... > http://www.ibm.com/developerworks/java/jdk/security/50/secguides/jgssDocs... > Example: - > <application-policy name="host-ibm"> > <authentication> > <login-module code="com.ibm.security.auth.module.Krb5LoginModule" > flag="required"> > <module-option name="useKeytab">file:///home/darranl/src/negotiation-as/jboss-5.1.0.GA-vm137/bin/service.keytab</module-option> > <module-option name="principal">host/testserver(a)VM137DOMAIN.GSSLAB</module-option> > <module-option name="credsType">both</module-option> > > <module-option name="debug">false</module-option> > </login-module> > </authentication> > </application-policy> > Also see JBAS-4969 the property jboss.security.disable.secdomain.option=true needs to be set. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-473) Add documentation for IBM JRE

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-473?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-473: -------------------------------------- Fix Version/s: (was: Negotiation_2_1_7) > Add documentation for IBM JRE > ----------------------------- > > Key: SECURITY-473 > URL: https://issues.jboss.org/browse/SECURITY-473 > Project: PicketBox > Issue Type: Task > Components: Documentation, Negotiation > Affects Versions: Negotiation_2.0.3.SP2 > Reporter: Darran Lofthouse > > Add documentation for IBM JRE > http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rz... > http://www.ibm.com/developerworks/java/jdk/security/50/secguides/jgssDocs... > Example: - > <application-policy name="host-ibm"> > <authentication> > <login-module code="com.ibm.security.auth.module.Krb5LoginModule" > flag="required"> > <module-option name="useKeytab">file:///home/darranl/src/negotiation-as/jboss-5.1.0.GA-vm137/bin/service.keytab</module-option> > <module-option name="principal">host/testserver(a)VM137DOMAIN.GSSLAB</module-option> > <module-option name="credsType">both</module-option> > > <module-option name="debug">false</module-option> > </login-module> > </authentication> > </application-policy> > Also see JBAS-4969 the property jboss.security.disable.secdomain.option=true needs to be set. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-677) Remove JBoss Negotiation Toolkit

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-677?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-677: ----------------------------------------- Assignee: (was: Darran Lofthouse) > Remove JBoss Negotiation Toolkit > -------------------------------- > > Key: SECURITY-677 > URL: https://issues.jboss.org/browse/SECURITY-677 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > > JBoss Negotiation Toolkit is being moved to the quickstarts, so it does not need to be maintained in two different locations delete it from the Negotiation source tree. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-677) Remove JBoss Negotiation Toolkit

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-677?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-677: -------------------------------------- Fix Version/s: (was: Negotiation_2_2_11) > Remove JBoss Negotiation Toolkit > -------------------------------- > > Key: SECURITY-677 > URL: https://issues.jboss.org/browse/SECURITY-677 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > > JBoss Negotiation Toolkit is being moved to the quickstarts, so it does not need to be maintained in two different locations delete it from the Negotiation source tree. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-717) Get JBoss Negotiation into Maven Central

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-717?page=com.atlassian.jira.plug... ] Darran Lofthouse reassigned SECURITY-717: ----------------------------------------- Assignee: (was: Darran Lofthouse) > Get JBoss Negotiation into Maven Central > ---------------------------------------- > > Key: SECURITY-717 > URL: https://issues.jboss.org/browse/SECURITY-717 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > > This will allow the JBoss Negotiation Toolkit to be removed from the project and instead moved to the quick starts making it much easier for end users to deploy and test. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-717) Get JBoss Negotiation into Maven Central

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-717?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-717: -------------------------------------- Fix Version/s: (was: Negotiation_2_2_11) > Get JBoss Negotiation into Maven Central > ---------------------------------------- > > Key: SECURITY-717 > URL: https://issues.jboss.org/browse/SECURITY-717 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > > This will allow the JBoss Negotiation Toolkit to be removed from the project and instead moved to the quick starts making it much easier for end users to deploy and test. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 August 2018