February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-189) Missing license CDDL 1.1 in license file, wrong content of licenses tag in pom.xml

by Scott Marlow (JIRA)

Scott Marlow created JBEE-189: --------------------------------- Summary: Missing license CDDL 1.1 in license file, wrong content of licenses tag in pom.xml Key: JBEE-189 URL: https://issues.jboss.org/browse/JBEE-189 Project: JBoss JavaEE Spec APIs Issue Type: Task Reporter: Scott Marlow Assignee: Scott Marlow Update the License file and pom.xml for license correctness. Update: jboss-jaxb-api_2.2_spec jboss-saaj-api_1.3_spec jboss-jsp-api_2.3_spec jboss-servlet-api_3.1_spec jboss-servlet-api_4.0_spec jboss-jaspi-api_1.1_spec jboss-connector-api_spec jboss-rmi-api_1.0_spec jboss-j2eemgmt-api_1.1_spec jboss-jsf-api_2.2_spec jboss-el-api_3.0_spec jboss-ejb-api_3.2_spec -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3654) Import a certficate directly from a key-store resource, with no certificate file generation

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3654?page=com.atlassian.jira.plugi... ] Farah Juma reassigned WFCORE-3654: ---------------------------------- Assignee: Farah Juma (was: Darran Lofthouse) > Import a certficate directly from a key-store resource, with no certificate file generation > ------------------------------------------------------------------------------------------- > > Key: WFCORE-3654 > URL: https://issues.jboss.org/browse/WFCORE-3654 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Claudio Miranda > Assignee: Farah Juma > Priority: Minor > > Consider the following scenario, a host controller hc1 on machine-A and a slave host controller hc2 on machine-B, they do not share a filesystem. > Currently if an user wants to import a certificate from a /host=hc1/subsystem=elytron/key-store=ks1 to /host=hc2/subsystem=elytron/key-store=ks2 he should call export-certificate on ks1 and manually copy the generated file to hc2, this can present problem on cloud environments. > So I suggest to enhance the export/import certificate operations to import the certificate directly from a key-store resource, one example may be: > /host=hc2/subsystem=elytron/key-store=ks2:import-certificate(source-resource="/host=hc1/subsystem=elytron/key-store=ks1",alias=my_alias) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3654) Import a certficate directly from a key-store resource, with no certificate file generation

by Claudio Miranda (JIRA)

Claudio Miranda created WFCORE-3654: --------------------------------------- Summary: Import a certficate directly from a key-store resource, with no certificate file generation Key: WFCORE-3654 URL: https://issues.jboss.org/browse/WFCORE-3654 Project: WildFly Core Issue Type: Enhancement Components: Security Reporter: Claudio Miranda Assignee: Darran Lofthouse Priority: Minor Consider the following scenario, a host controller hc1 on machine-A and a slave host controller hc2 on machine-B, they do not share a filesystem. Currently if an user wants to import a certificate from a /host=hc1/subsystem=elytron/key-store=ks1 to /host=hc2/subsystem=elytron/key-store=ks2 he should call export-certificate on ks1 and manually copy the generated file to hc2, this can present problem on cloud environments. So I suggest to enhance the export/import certificate operations to import the certificate directly from a key-store resource, one example may be: /host=hc2/subsystem=elytron/key-store=ks2:import-certificate(source-resource="/host=hc1/subsystem=elytron/key-store=ks1",alias=my_alias) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3647) CLI multi page output does not work correctly on Cygwin

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3647?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3647: ----------------------------------------- Affects Version/s: 4.0.0.Alpha3 (was: 4.0.0.Beta1) > CLI multi page output does not work correctly on Cygwin > ------------------------------------------------------- > > Key: WFCORE-3647 > URL: https://issues.jboss.org/browse/WFCORE-3647 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha3 > Reporter: Erich Duda > Assignee: Jean-Francois Denise > > The Auto more/less in CLI for multi-page output (WFCORE-426) does not work correctly on Cygwin. Each key has to be pushed twice to interact. > It was hit on following Cygwin version. > {code} > $ uname -a > CYGWIN_NT-6.3 WIN-VSOI9S1FO1Q 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3647) CLI multi page output does not work correctly on Cygwin

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3647?page=com.atlassian.jira.plugi... ] Jean-Francois Denise edited comment on WFCORE-3647 at 2/26/18 12:03 PM: ------------------------------------------------------------------------ Yes, this has been introduced in 4.0.Alpha3 was (Author: jdenise): Yes, this has been introduced in 4.0.Beta1 > CLI multi page output does not work correctly on Cygwin > ------------------------------------------------------- > > Key: WFCORE-3647 > URL: https://issues.jboss.org/browse/WFCORE-3647 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha3 > Reporter: Erich Duda > Assignee: Jean-Francois Denise > > The Auto more/less in CLI for multi-page output (WFCORE-426) does not work correctly on Cygwin. Each key has to be pushed twice to interact. > It was hit on following Cygwin version. > {code} > $ uname -a > CYGWIN_NT-6.3 WIN-VSOI9S1FO1Q 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3647) CLI multi page output does not work correctly on Cygwin

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3647?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3647: ----------------------------------------- Affects Version/s: 4.0.0.Beta1 (was: 3.1.0.Final) > CLI multi page output does not work correctly on Cygwin > ------------------------------------------------------- > > Key: WFCORE-3647 > URL: https://issues.jboss.org/browse/WFCORE-3647 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Beta1 > Reporter: Erich Duda > Assignee: Jean-Francois Denise > > The Auto more/less in CLI for multi-page output (WFCORE-426) does not work correctly on Cygwin. Each key has to be pushed twice to interact. > It was hit on following Cygwin version. > {code} > $ uname -a > CYGWIN_NT-6.3 WIN-VSOI9S1FO1Q 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2253: -------------------------------- Which log statement (line,method)? > FD_SOCK is not working in AWS environment > ----------------------------------------- > > Key: JGRP-2253 > URL: https://issues.jboss.org/browse/JGRP-2253 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.10 > Environment: AWS - EC2 > Reporter: Sibin Karnavar > Assignee: Bela Ban > > We have our failure detection defined like below. > <FD_SOCK external_port="7804" /> > <FD timeout="3000" max_tries="3" /> > <VERIFY_SUSPECT timeout="3000" /> > Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing. > In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK. > We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port. > Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS. > Thanks, > Sibin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2310) After importing an example project you are no longer taken to Library screen

by Adriel Paredes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2310?page=com.atlassian.jira.plugi... ] Adriel Paredes resolved DROOLS-2310. ------------------------------------ Resolution: Done > After importing an example project you are no longer taken to Library screen > ---------------------------------------------------------------------------- > > Key: DROOLS-2310 > URL: https://issues.jboss.org/browse/DROOLS-2310 > Project: Drools > Issue Type: Bug > Components: Examples (Workbench) > Reporter: Michael Anstis > Assignee: Adriel Paredes > > When importing an example project into the workbench, older versions would automatically navigate the User to the Library screen. However in {{master}} (as of the date of this JIRA) after the import the User is left on the "Try example" screen. The User needs to manually click on the teams breadcrumb to get a list of projects. IDK if this is deliberate. > [~adriel.paredes] This may have nothing to do with the recent changes you made; in which case perhaps just reassign to [~paulovmr] for consideration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment

by Sibin Karnavar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ] Sibin Karnavar commented on JGRP-2253: -------------------------------------- Thank you, Thanks for your hints :) Your documents was really helpful. Do you think, you may need to log as WARN, when failed to establish a socket connection due to any reason? Even I found TCP has a default diagnostics_port. I just defined my own port and added that as well to security group. Thanks, Sibin > FD_SOCK is not working in AWS environment > ----------------------------------------- > > Key: JGRP-2253 > URL: https://issues.jboss.org/browse/JGRP-2253 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.10 > Environment: AWS - EC2 > Reporter: Sibin Karnavar > Assignee: Bela Ban > > We have our failure detection defined like below. > <FD_SOCK external_port="7804" /> > <FD timeout="3000" max_tries="3" /> > <VERIFY_SUSPECT timeout="3000" /> > Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing. > In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK. > We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port. > Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS. > Thanks, > Sibin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2253: -------------------------------- OK, I'm happy to see you found out the core issue even before I was able to tackle this issue! > FD_SOCK is not working in AWS environment > ----------------------------------------- > > Key: JGRP-2253 > URL: https://issues.jboss.org/browse/JGRP-2253 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.10 > Environment: AWS - EC2 > Reporter: Sibin Karnavar > Assignee: Bela Ban > > We have our failure detection defined like below. > <FD_SOCK external_port="7804" /> > <FD timeout="3000" max_tries="3" /> > <VERIFY_SUSPECT timeout="3000" /> > Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing. > In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK. > We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port. > Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS. > Thanks, > Sibin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018