May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8767) Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-8767?page=com.atlassian.jira.plugin.... ] Lin Gao moved JBEAP-10899 to WFLY-8767: --------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8767 (was: JBEAP-10899) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) Affects Version/s: (was: 7.0.5.GA) > Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-8767 > URL: https://issues.jboss.org/browse/WFLY-8767 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: Lin Gao > Labels: downstream_dependency > Original Estimate: 2 days > Remaining Estimate: 2 days > > In EAP domain mode, when changing the max-pool-size attribute of a datasource via CLI, the response does not indicate that a reload is required. However, reading the statistics of that datasource does not reflect the Available count as per the new max pool value until a restart of the server is performed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-215) Allow for configuration of transaction-retry

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/JBMETA-215?page=com.atlassian.jira.plugin... ] Carlo de Wolf reassigned JBMETA-215: ------------------------------------ Assignee: (was: Carlo de Wolf) > Allow for configuration of transaction-retry > -------------------------------------------- > > Key: JBMETA-215 > URL: https://issues.jboss.org/browse/JBMETA-215 > Project: JBoss Metadata > Issue Type: Feature Request > Components: ejb > Reporter: Carlo de Wolf > > The @TransactionRetry annotation must have an equivalent configuration option in descriptors. > @TransactionRetry(numRetries=4, waitTime=1, waitTimeUnit=TimeUnit.SECONDS) > <assembly-descriptor> > <transaction-retry> >  > <method> > <ejb-name>*</ejb-name> > <method-name>...</method-name> > </method> > ... > <num-retries>4</num-retries> > <wait-time>1</wait-time> > <wait-time-unit>SECONDS</wait-time-unit> > </transaction-retry> > </assembly-descriptor> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-383) Create test to guard against schema and dtd changes

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/JBMETA-383?page=com.atlassian.jira.plugin... ] Carlo de Wolf closed JBMETA-383. -------------------------------- Resolution: Done > Create test to guard against schema and dtd changes > --------------------------------------------------- > > Key: JBMETA-383 > URL: https://issues.jboss.org/browse/JBMETA-383 > Project: JBoss Metadata > Issue Type: Task > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > > {quote} > On 01/09/2015 09:55 AM, Max Rydahl Andersen wrote: > Now what is important for EAP and WF team to realize is that they must ensure these schemas stays the same and compatible with both...and if something need to divert it needs to get a different versioned name (which I honestly hope will never happen) > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1154) Update CredentialStore API to take Supplier<Provider[]>

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1154: ------------------------------------- Summary: Update CredentialStore API to take Supplier<Provider[]> Key: ELY-1154 URL: https://issues.jboss.org/browse/ELY-1154 Project: WildFly Elytron Issue Type: Enhancement Components: Credential Store Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta43 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1034) Build option to exclude Jacorb / IIOP

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-1034?page=com.atlassian.jira.plugin.... ] Carlo de Wolf closed WFLY-1034. ------------------------------- Resolution: Out of Date > Build option to exclude Jacorb / IIOP > ------------------------------------- > > Key: WFLY-1034 > URL: https://issues.jboss.org/browse/WFLY-1034 > Project: WildFly > Issue Type: Enhancement > Components: IIOP > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1010) Build option to exclude the openjpa module

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-1010?page=com.atlassian.jira.plugin.... ] Carlo de Wolf closed WFLY-1010. ------------------------------- Resolution: Out of Date > Build option to exclude the openjpa module > ------------------------------------------ > > Key: WFLY-1010 > URL: https://issues.jboss.org/browse/WFLY-1010 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Paul Gier > Assignee: Carlo de Wolf > > It would be good to have a command line build option which could be used to not include the openjpa components. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2691) Elytron modifiable realms should show existing identities in subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2691?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-2691: ------------------------------- Git Pull Request: https://github.com/wildfly-security-incubator/wildfly-core/pull/150, https://github.com/wildfly/wildfly-core/pull/2420 (was: https://github.com/wildfly-security-incubator/wildfly-core/pull/150) > Elytron modifiable realms should show existing identities in subsystem > ---------------------------------------------------------------------- > > Key: WFCORE-2691 > URL: https://issues.jboss.org/browse/WFCORE-2691 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta15 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Labels: filesystem-realm, security-realm > Fix For: 3.0.0.Beta22 > > > Elytron {{filesystem-realm}} should load existing identities from file system. The steps to reproduce results in: > {noformat} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:read-identity > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"elytron\"), > (\"filesystem-realm\" => \"realm\"), > (\"identity\" => \"user\") > ]' not found", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:add > { > "outcome" => "failed", > "failure-description" => "WFLYELY01000: Identity with name [user] already exists.", > "rolled-back" => true > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2170) GOOGLE_PING2

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2170?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2170. ---------------------------- Resolution: Done > GOOGLE_PING2 > ------------ > > Key: JGRP-2170 > URL: https://issues.jboss.org/browse/JGRP-2170 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.1 > > > New version of GOOGLE_PING based on the official Google Cloud Storage APIs [1]. The existing GOOGLE_PING protocol extends S3_PING which I want to deprecate, so creating GOOGLE_PING2 is a prerequisite to that. > Hosting will be at jgroups-extras: https://github.com/jgroups-extras/jgroups-google > [1] https://cloud.google.com/storage/docs/apis -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2170) GOOGLE_PING2

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2170?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2170: --------------------------- Fix Version/s: 4.0.4 > GOOGLE_PING2 > ------------ > > Key: JGRP-2170 > URL: https://issues.jboss.org/browse/JGRP-2170 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.1, 4.0.4 > > > New version of GOOGLE_PING based on the official Google Cloud Storage APIs [1]. The existing GOOGLE_PING protocol extends S3_PING which I want to deprecate, so creating GOOGLE_PING2 is a prerequisite to that. > Hosting will be at jgroups-extras: https://github.com/jgroups-extras/jgroups-google > [1] https://cloud.google.com/storage/docs/apis -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8678) Re-enable tests temporarily disabled in -Delytron run.

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8678?page=com.atlassian.jira.plugin.... ] Jan Kalina edited comment on WFLY-8678 at 5/15/17 5:27 AM: ----------------------------------------------------------- Unignored and no failure. (except one random race condition, which seem to be unrelated as it is different testcase - no possibility to be caused by test from basic) was (Author: honza889): Unignored and no failure. (except one which seem to be unrelated...) > Re-enable tests temporarily disabled in -Delytron run. > ------------------------------------------------------ > > Key: WFLY-8678 > URL: https://issues.jboss.org/browse/WFLY-8678 > Project: WildFly > Issue Type: Task > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Fix For: 11.0.0.Beta1 > > > The following tests are temporarily ignored: - > Tests in error: > ExportImportJournalTestCase.testExportImportJournal:136->sendMessage:77 » Communication > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSQueueManagementTestCase.addQueues:105 » Communication WFNAM00018: Failed to... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > JMSTopicManagementTestCase.before:89 » Communication WFNAM00018: Failed to con... > PooledConnectionFactoryStatisticsTestCase.testStatistics:83 » Communication WF... > RemoteNamingEjbTestCase.testDeploymentBinding:140 » Communication WFNAM00018: ... > RemoteNamingEjbTestCase.testIt:99 » Communication WFNAM00018: Failed to connec... > RemoteNamingTestCase.testNestedLookup:109 » Communication WFNAM00018: Failed t... > RemoteNamingTestCase.testRemoteContextLookup:97 » Communication WFNAM00018: Fa... > RemoteNamingTestCase.testRemoteLookup:85 » Communication WFNAM00018: Failed to... > TransactionInflowTestCase.inflowTransactionCommit:138 » IllegalState EJBCLIENT... > TransactionInflowTestCase.inflowTransactionRollback:156 » IllegalState EJBCLIE... > Investigation needs to continue as it actually appears something running before these tests is the cause as running these tests in isolation does not cause a failure. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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