September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7217) Adapt servlet-security example to use Elytron

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-7217?page=com.atlassian.jira.plugin.... ] Ingo Weiss moved JBEAP-6201 to WFLY-7217: ----------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7217 (was: JBEAP-6201) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Documentation (was: Quickstarts) > Adapt servlet-security example to use Elytron > --------------------------------------------- > > Key: WFLY-7217 > URL: https://issues.jboss.org/browse/WFLY-7217 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Ingo Weiss > Assignee: Sande Gilda > Priority: Minor > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7194) Simplify creation of trust/key-manager in elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7194?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7194: ---------------------------------- *Part 3* was already done as part of other PR. *Part 4* - password is required by KeyManager, on the other side it will be deprecated and replaced "as to be supplied by the vault". For now I can set it required, can be made optional when the vault alternative will be implemented. > Simplify creation of trust/key-manager in elytron > ------------------------------------------------- > > Key: WFLY-7194 > URL: https://issues.jboss.org/browse/WFLY-7194 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > > If I want to setup TLS [1], I have to create key manager with CLI command > {code} > /subsystem=elytron/key-managers=httpsKM:add(key-store=httpsKS,algorithm="SunX509") > {code} > 1. It seems to me {{algorithm}} can be optional. If not set {{TrustManagerFactory.getDefaultAlgorithm()}} can be used. > 2. Also, please, enhance xsd/model documentation with clear statement that this {{password}} attribute is in fact "key password" . Or probably better rename attribute from {{password}} to {{key-password}} to make it absolutely clear to everyone. > 3. {{key-store}} attribute is declared optional in xsd . In model it is properly declared as required. Please change XSD to express it is required. > {code} > <xs:attribute name="key-store" type="xs:string" use="optional"> > <xs:annotation> > <xs:documentation> > Reference to the KeyStore to use with the KeyManager. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} > 4.{{password}} attribute is optional, probably should be required > {code} > "password" => { > "type" => STRING, > "description" => "The password to use when initialising the underlying KeyManagerFactory.", > "expressions-allowed" => true, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "1.0.0", > "reason" => "Will be updated to use proper CredentialStore references." > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7216) Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final

by Lin Gao (JIRA)

Lin Gao created WFLY-7216: ----------------------------- Summary: Valid Wildfly 10.0.0.Final DataSource fails in Wildfly 10.1.0.Final Key: WFLY-7216 URL: https://issues.jboss.org/browse/WFLY-7216 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 10.1.0.Final Reporter: Lin Gao Assignee: Lin Gao My current Wildfly 10.0.0.Final (Non-XA) Datasource configuration will not work for Wildfly 10.1.0.Final. See the "Steps to Reproduce" section. The stacktrace points to here: * https://source.jboss.org/browse/IronJacamar/adapters/src/main/java/org/jb... * https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.4.Final/a... h3. The work-around h3. Wildfly 10.1.0.Final Datasource configuration via CLI {code} # No parameter to set a connection property value. {code} h3. Wildfly 10.1.0.Final Datasource configuration via XML (standalone-full.xml) Note the addition of {{<connection-property name="databaseName">myapp</connection-property>}} {code:xml} <subsystem xmlns="urn:jboss:domain:datasources:4.0"> <datasources> <datasource jndi-name="java:/MY_APP_DS" pool-name="Postgres_MY_APP_DS"> <connection-url>jdbc:postgresql://localhost:5432/myapp</connection-url> <connection-property name="databaseName">myapp</connection-property> <driver>postgres</driver> <security> <user-name>myapp</user-name> <password>myapp</password> </security> <validation> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/> </validation> </datasource> <drivers> <driver name="postgres" module="org.postgres"> <driver-class>org.postgresql.Driver</driver-class> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class> <datasource-class>org.postgresql.ds.PGSimpleDataSource</datasource-class> </driver> </drivers> </datasources> </subsystem> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7210) Expose JAX-RS resources as children of the subsystem

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-7210?page=com.atlassian.jira.plugin.... ] Marek Kopecký commented on WFLY-7210: ------------------------------------- Upgrade of show-resources operation is covered by WFLY-7024. I recommend to close this jira as duplicite of WFLY-7024. > Expose JAX-RS resources as children of the subsystem > ---------------------------------------------------- > > Key: WFLY-7210 > URL: https://issues.jboss.org/browse/WFLY-7210 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 10.1.0.Final > Reporter: Guillermo González de Agüero > Assignee: Stuart Douglas > Attachments: hal-jaxrs.png > > > Servlets, EJBs, WebSockets, JPA, etc expose its components as children of the subsystem in the management API. For example to list the stateless EJBs of a deployment: > [standalone@localhost:9990 /] /deployment=cdivsejb.war/subsystem=ejb3:read-children-resources(child-type=stateless-session-bean) > This makes it specially easy to navigate trough the web console (attached screenshot). > To read JAX-RS resources, the command would be: > [standalone@localhost:9990 /] /deployment=cdivsejb.war/subsystem=jaxrs:show-resources() > I propose to make deprecate the show-resources operation and create a new "resources" child, containing the Rest resources. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1680) RDMA based transport

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1680?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1680: -------------------------------- Look into accelio [1] / JXIO [2] [1] www.github.com/accelio [2] https://github.com/accelio/JXIO > RDMA based transport > -------------------- > > Key: JGRP-1680 > URL: https://issues.jboss.org/browse/JGRP-1680 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.1 > > > Investigate whether an RDMA based transport makes sense. > Advantages: > * Speed, low latency (TCP/IP is bypassed entirely) > * Low CPU usage > Disadvantages: > * JNI/C code > ** Such a transport implementation would have to live outside of the JGroups repo > ** Maintainability nightmare: the C code would also have to be ported to various OSes > *** Investigate Java based libs (IBM's jVerbs) and C based libs (Apache Portable Runtime?) > * High memory use, growing with cluster size: similarly to TCP, a 'group multicast' would involve N-1 sends. RDMA requires a Queue Pair (QP) for each destination. Each QP requires pinned memory (receive and send buffer), so each node would have to reserve (pin) N-1 memory buffers [1] > ** OTOH, we may not use many group multicasts, e.g. with Infinispan's partial replication (DIST mode) > * High cost of RDMA adapters, NICs and wiring: only a very small fraction of users would run such a transport. > [1] http://www.hpcwire.com/hpcwire/2006-08-18/a_critique_of_rdma-1.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7101) Wildfly 10.1.0 blocks calls to Singleton EJBs in PostConstruct

by Dietrich Schmidt (JIRA)

[ https://issues.jboss.org/browse/WFLY-7101?page=com.atlassian.jira.plugin.... ] Dietrich Schmidt commented on WFLY-7101: ---------------------------------------- I'd be happy to get feedback: is this a bug or not? > Wildfly 10.1.0 blocks calls to Singleton EJBs in PostConstruct > -------------------------------------------------------------- > > Key: WFLY-7101 > URL: https://issues.jboss.org/browse/WFLY-7101 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.Final > Environment: Wildfly 10.1.0 running under Windows 10 with Java 1.8.0_91 > Reporter: Dietrich Schmidt > Assignee: Jason Greene > Attachments: Verklemmung.zip > > > Wildfly 8.2.0 and 10.0.0 work fine with a Singleton Bean, which has a @Postconstruct method and in this method several threads are created with the ManagedExecutorService. These threads call a method in another Singleton EJB, which has been injected. > This call is blocked in Wildfly 10.1.0 until the Prostconstruct thread has ended. > I assume that the behaviour of Wildfly 8.2.0 + 10.0.0 is correct and the behaviour of Wildfly 10.1.0 is a bug. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7215) Reintroduce JNDI over HTTP/HTTPS capability

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-7215: ------------------------------------ Summary: Reintroduce JNDI over HTTP/HTTPS capability Key: WFLY-7215 URL: https://issues.jboss.org/browse/WFLY-7215 Project: WildFly Issue Type: Feature Request Reporter: Stuart Douglas Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1331) Use connection-url to get database connection when connection properties for datasource-class is empty

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1331?page=com.atlassian.jira.plugin... ] Lin Gao commented on JBJCA-1331: -------------------------------- PR sent at: https://github.com/ironjacamar/ironjacamar/pull/575 > Use connection-url to get database connection when connection properties for datasource-class is empty > ------------------------------------------------------------------------------------------------------ > > Key: JBJCA-1331 > URL: https://issues.jboss.org/browse/JBJCA-1331 > Project: IronJacamar > Issue Type: Task > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.4.Final > Reporter: Lin Gao > Assignee: Lin Gao > > Fixes of JBJCA-1312 will fail the old configuration where the connection-url is used. > In the compatibility point of view, we should try to use {{connection-url}} & {{driver-class}} to get the database connection if the connection properties are empty && datasource-class != null. A warning message should be printed to encourage users to use DataSource for database connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1331) Use connection-url to get database connection when connection properties for datasource-class is empty

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1331?page=com.atlassian.jira.plugin... ] Lin Gao updated JBJCA-1331: --------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/575 > Use connection-url to get database connection when connection properties for datasource-class is empty > ------------------------------------------------------------------------------------------------------ > > Key: JBJCA-1331 > URL: https://issues.jboss.org/browse/JBJCA-1331 > Project: IronJacamar > Issue Type: Task > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.4.Final > Reporter: Lin Gao > Assignee: Lin Gao > > Fixes of JBJCA-1312 will fail the old configuration where the connection-url is used. > In the compatibility point of view, we should try to use {{connection-url}} & {{driver-class}} to get the database connection if the connection properties are empty && datasource-class != null. A warning message should be printed to encourage users to use DataSource for database connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7213) IllegalStateException to run test-connection-in-pool() for datasource with same jndi-name as previous failed datasource

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-7213?page=com.atlassian.jira.plugin.... ] Lin Gao deleted WFLY-7213: -------------------------- > IllegalStateException to run test-connection-in-pool() for datasource with same jndi-name as previous failed datasource > ----------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7213 > URL: https://issues.jboss.org/browse/WFLY-7213 > Project: WildFly > Issue Type: Bug > Reporter: Lin Gao > Assignee: Jesper Pedersen > > If a DataSource was failed to be added, like adding a DataSource using {{datasource-class}} without specifying any {{connection-properties}}: > {code:} > /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, datasource-class=XXX,driver-name=h2) > {code} > or adding a DataSource using {{driver-class}} without specifying {{connection-url}}: > {code:} > /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2) > {code} > It can be corrected afterwards by specifying correct information with same {{jndi-name}}, like: > {code:} > /subsystem=datasources/data-source=XXX:add(jndi-name=java:/XXX, driver-name=h2,connection-url="jdbc:h2:xxx") > {code} > after the DataSource created, the {{test-connection-in-pool()}} operation will fail with {{IllegalStateException}} > {code:} > /subsystem=datasources/data-source=XXX:test-connection-in-pool() > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016