October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5530) embed-server .cli script - data source enable no longer work

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5530?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5530: ---------------------------------------- Sure, no problem. I admit I have somewhat hijacked your issue. :) Thanks for the report, BTW; looking into it is what led me to see this problem. > embed-server .cli script - data source enable no longer work > ------------------------------------------------------------ > > Key: WFLY-5530 > URL: https://issues.jboss.org/browse/WFLY-5530 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.CR2, 10.0.0.CR3 > Environment: Linux (at least) > Reporter: Martin Miller > Assignee: Jason Greene > Labels: regression > Attachments: test.cli.txt > > > First time I report a problem, not sure if the specified the correct components.... > Seems like a regression from Version 9; I have a .cli script to configure wildfly using embed-server, and enabling a datasource doesn't work anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1877) Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1877?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-1877. ------------------------------------ Resolution: Won't Do Shifting the type away from long will break compatibility for readers even if we are forgiving for writes. Since all this started Jason and I have had a shift in values even more toward the sense that compatibility breakage is very strongly to be avoided, even between WF 9 and WF 10. That outweighs making the type consistent. > Make KeepAliveTimeAttributeDefinition deal with both a simple long and a complex attribute > ------------------------------------------------------------------------------------------ > > Key: WFLY-1877 > URL: https://issues.jboss.org/browse/WFLY-1877 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 10.0.0.CR4 > > > This attribute should support either a simple value or a complex one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5530) embed-server .cli script - data source enable no longer work

by Martin Miller (JIRA)

[ https://issues.jboss.org/browse/WFLY-5530?page=com.atlassian.jira.plugin.... ] Martin Miller commented on WFLY-5530: ------------------------------------- I think I see; I won't be much help for these additional issues, as my understanding and use of WildFly is very limited (I'm using the standalone full config). > embed-server .cli script - data source enable no longer work > ------------------------------------------------------------ > > Key: WFLY-5530 > URL: https://issues.jboss.org/browse/WFLY-5530 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.CR2, 10.0.0.CR3 > Environment: Linux (at least) > Reporter: Martin Miller > Assignee: Jason Greene > Labels: regression > Attachments: test.cli.txt > > > First time I report a problem, not sure if the specified the correct components.... > Seems like a regression from Version 9; I have a .cli script to configure wildfly using embed-server, and enabling a datasource doesn't work anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5530) embed-server .cli script - data source enable no longer work

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5530?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5530: ---------------------------------------- There's a problem with how the deprecation of 'enable' / 'disable' works in a managed domain. The WFLYJCA0093 failure message reported here is reported if the op is sent to a server, but on the domain controller the op is handled as a no-op locally, and then propagated on to the servers affected by the relevant profile. This has some incorrect effects. Let's assume for the sake of illustration that the datasource is currently configured as enabled in the domain wide config, and then the 'disable' op is sent. The effect of this is: 1) If the profile is used by a current version server, the op will fail on that server, with the same WFLYJCA0093 failure message. Whether that results in a rollback of the op on the domain controller and across the domain depends on the rollout plan in use. A rollout plan could be specified that allows the failures on the servers. If this is the case, the operation outcome will be reported as 'success' but no change will have been made to the domain wide configuration (since the DC handles this op locally as a no-op.) This is an unintuitive result, since the user will reasonably expect that a 'success' will mean a change to the domain wide configuration has occurred. In all other cases involving ops that change configuration, 'success' means this. 2) If the profile is only used by legacy servers, then those servers will update their running configuration to disable the datasource, but configuration on the DC will not reflect this change, again because on the DC the op is handled locally as a no-op. Again, the operation outcome will be reported as 'success' but no change will have been made to the domain wide configuration. Basically, allowing an op that has historically resulted in a config change to execute on the DC without actually changing the domain wide config is incorrect. > embed-server .cli script - data source enable no longer work > ------------------------------------------------------------ > > Key: WFLY-5530 > URL: https://issues.jboss.org/browse/WFLY-5530 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.CR2, 10.0.0.CR3 > Environment: Linux (at least) > Reporter: Martin Miller > Assignee: Jason Greene > Labels: regression > Attachments: test.cli.txt > > > First time I report a problem, not sure if the specified the correct components.... > Seems like a regression from Version 9; I have a .cli script to configure wildfly using embed-server, and enabling a datasource doesn't work anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5530) embed-server .cli script - data source enable no longer work

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5530?page=com.atlassian.jira.plugin.... ] Brian Stansberry reopened WFLY-5530: ------------------------------------ > embed-server .cli script - data source enable no longer work > ------------------------------------------------------------ > > Key: WFLY-5530 > URL: https://issues.jboss.org/browse/WFLY-5530 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.CR2, 10.0.0.CR3 > Environment: Linux (at least) > Reporter: Martin Miller > Assignee: Jason Greene > Labels: regression > Attachments: test.cli.txt > > > First time I report a problem, not sure if the specified the correct components.... > Seems like a regression from Version 9; I have a .cli script to configure wildfly using embed-server, and enabling a datasource doesn't work anymore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1071) Where a username terminates with a '\' add-user adds it multiple times to the properties file.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1071?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1071: ------------------------------------------ Also existing user detection fails for usernames containing a '\'. > Where a username terminates with a '\' add-user adds it multiple times to the properties file. > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1071 > URL: https://issues.jboss.org/browse/WFCORE-1071 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Scripts > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.CR8 > > > I have not debugged this yet but I would suspect this is actually happening during writing the file for a subsequent user added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-125) Log rotation fails on Windows if target already exists

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-125?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-125: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/88, https://github.com/jboss-logging/jboss-logmanager/pull/89 (was: https://github.com/jboss-logging/jboss-logmanager/pull/88) > Log rotation fails on Windows if target already exists > ------------------------------------------------------ > > Key: LOGMGR-125 > URL: https://issues.jboss.org/browse/LOGMGR-125 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Livingston > Assignee: James Perkins > Fix For: 2.0.4.Final, 2.1.0.Beta1 > > > PeriodicRotatingFileHandler (and others) use File.renameTo() to rename the file. That method is documented as having many implementation-defined aspects, see http://docs.oracle.com/javase/7/docs/api/java/io/File.html#renameTo%28jav... > One that can be a problem is that on Windows, it will fail if the target file already exists. If you use a ".dd" suffix, this will occur when it rolls over to a new month. It has rarely been a problem, since most people use the year month and day so they are unique. Files.move() can replace existing files, so may be better, and some of the costs of that are likely not to be a problem with how it is using here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-125) Log rotation fails on Windows if target already exists

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-125?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-125: --------------------------------- Fix Version/s: 2.0.4.Final > Log rotation fails on Windows if target already exists > ------------------------------------------------------ > > Key: LOGMGR-125 > URL: https://issues.jboss.org/browse/LOGMGR-125 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Livingston > Assignee: James Perkins > Fix For: 2.0.4.Final, 2.1.0.Beta1 > > > PeriodicRotatingFileHandler (and others) use File.renameTo() to rename the file. That method is documented as having many implementation-defined aspects, see http://docs.oracle.com/javase/7/docs/api/java/io/File.html#renameTo%28jav... > One that can be a problem is that on Windows, it will fail if the target file already exists. If you use a ".dd" suffix, this will occur when it rolls over to a new month. It has rarely been a problem, since most people use the year month and day so they are unique. Files.move() can replace existing files, so may be better, and some of the costs of that are likely not to be a problem with how it is using here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5518) Tests from XTS module fails with security manager

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5518?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved WFLY-5518. --------------------------------- Resolution: Done > Tests from XTS module fails with security manager > ------------------------------------------------- > > Key: WFLY-5518 > URL: https://issues.jboss.org/browse/WFLY-5518 > Project: WildFly > Issue Type: Bug > Components: Test Suite, XTS > Affects Versions: 10.0.0.CR2 > Reporter: Marek Kopecký > Assignee: Gytis Trikleris > Fix For: 10.0.0.CR4 > > Attachments: xts.module.txt > > > *Description of problem:* > Tests from XTS module fails with security manager. BAParticipantCompletionTestCase fails on maven timeout {{\[ERROR\] There was a timeout or other error in the fork}} > *How reproducible:* > Always > *Steps to Reproduce:* > # ./integration-tests.sh -Dmaven.repo.local=$MAVEN_REPO_LOCAL -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -Dmcast=$MCAST_ADDR -Djboss.dist=$JBOSS_DIST -Dsecurity.manager -Dts.xts > *Actual results:* > See attached file > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5501) JDBC Object Store problem with Mariadb55

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5501?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved WFLY-5501. --------------------------------- Resolution: Done > JDBC Object Store problem with Mariadb55 > ---------------------------------------- > > Key: WFLY-5501 > URL: https://issues.jboss.org/browse/WFLY-5501 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Hayk Hovsepyan > Assignee: Tom Jenkinson > Fix For: 10.0.0.CR4 > > Attachments: mariadb_jar.zip, server.log, standalone.xml > > > When configuring transactions to use Mariadb55 Datasource as a JDBC Object store, server fails to start with error: > {code} > 13:56:51,485 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.txn.ArjunaRecoveryManager" => "org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > Caused by: java.lang.NullPointerException"}} > {code} > Steps to reproduce: > 1. Create Mariadb55 JDBC driver module. Module archived directory is attached. > 2. Add driver into configuration xml. > 3. Create Datasource pointing to Mariadb55 database and using driver configured a a module. > 4. Configure transactions to use jdbc-store the added Datasource. standalone.xml is attached. > 5. Server fails to start. server.log is attached. > config xml file part: > {code} > <subsystem xmlns="urn:jboss:domain:datasources:4.0"> > <datasources> > <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true"> > <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url> > <driver>h2</driver> > <security> > <user-name>sa</user-name> > <password>sa</password> > </security> > </datasource> > <datasource jta="false" jndi-name="java:jboss/datasources/jdbc-store" pool-name="JDBCObjectStore" enabled="true" use-java-context="true"> > <connection-url>jdbc:mariadb://db22.mw.lab.eng.bos.redhat.com:3306/dballo17</connection-url> > <driver>module_mariadb.jar</driver> > <security> > <user-name>dballo17</user-name> > <password>dballo17</password> > </security> > </datasource> > <drivers> > <driver name="h2" module="com.h2database.h2"> > <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> > </driver> > <driver name="module_mariadb.jar" module="mariadb_jar"/> > </drivers> > </datasources> > </subsystem> > <subsystem xmlns="urn:jboss:domain:transactions:3.0"> > <core-environment> > <process-id> > <uuid/> > </process-id> > </core-environment> > <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/> > <coordinator-environment enable-tsm-status="true"/> > <jdbc-store datasource-jndi-name="java:jboss/datasources/jdbc-store"/> > </subsystem> > {code} > Attached necessary info: > 1. server.log > 2. Module zip to extract in $JBOSS_HOME/modules/system/layers/base > 3. standalone.xml > Notes: > The same steps works for other databases. > When step 4. is not executed server starts successfully, so module is recognized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 10 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 October 2015