April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6681) ClusteredSingleSignOn ClassCastException with non-distributable apps

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6681?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6681: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 920367|https://bugzilla.redhat.com/show_bug.cgi?id=920367] from MODIFIED to ON_QA > ClusteredSingleSignOn ClassCastException with non-distributable apps > -------------------------------------------------------------------- > > Key: AS7-6681 > URL: https://issues.jboss.org/browse/AS7-6681 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Dennis Reed > Assignee: Dennis Reed > Fix For: 8.0.0.Alpha1 > > Attachments: test.war > > > When ClusteredSingleSignOn is enabled, and a user has an active session in a non-distributable web application, invalidating any session in the same SSO from a different AS instance in the cluster causes the following exception (logged numerous times in various ways): > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-20,null) ISPN000136: Execution error: org.infinispan.CacheException: Caught exception [java.lang.ClassCastException] while invoking method [public void org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager.cacheEntryRemoved(org.infinispan.notifications.cachelistener.event.CacheEntryRemovedEvent)] on listener instance: org.jboss.as.clustering.web.sso.infinispan.SSOClusterManager@28e13c84 > ... > Caused by: java.lang.ClassCastException: org.apache.catalina.session.StandardSession cannot be cast to org.jboss.as.web.session.ClusteredSession > at org.jboss.as.web.sso.ClusteredSingleSignOn.deregisterLocal(ClusteredSingleSignOn.java:523) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] > ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6526) It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6526?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6526: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 928922|https://bugzilla.redhat.com/show_bug.cgi?id=928922] from MODIFIED to ON_QA > It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent > ----------------------------------------------------------------------------------------------------- > > Key: AS7-6526 > URL: https://issues.jboss.org/browse/AS7-6526 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The JBAS14143 message and other skip messages log the timer id, but this is not very helpful as it is complicated to find the related application bean if the timer is persistent or not possible if it is a non persistent timer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6780) Default config is not using most up to date schemas

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6780?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6780: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 926002|https://bugzilla.redhat.com/show_bug.cgi?id=926002] from MODIFIED to ON_QA > Default config is not using most up to date schemas > --------------------------------------------------- > > Key: AS7-6780 > URL: https://issues.jboss.org/browse/AS7-6780 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > We also need to add a test to prevent this from happening in future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6616) AS 8: Testsuite fails on Solaris SPARC 10

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6616?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6616: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 947954|https://bugzilla.redhat.com/show_bug.cgi?id=947954] from MODIFIED to ON_QA > AS 8: Testsuite fails on Solaris SPARC 10 > ----------------------------------------- > > Key: AS7-6616 > URL: https://issues.jboss.org/browse/AS7-6616 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 8.0.0.Alpha1 > Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41 > Reporter: Frank Langelage > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > Attachments: org.jboss.as.naming.InitialContextTestCase.txt, TEST-org.jboss.as.naming.InitialContextTestCase.xml > > > Compiling the current sources from github fails for me on this environment. > On Windows everything is fine. > Compiling 7.2.0.Final works in this environment. > But regarding this test, nothing seems to have changed in between. > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec > Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec > Running org.jboss.as.naming.InitialContextTestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE! > Running org.jboss.as.naming.InitialContextFactoryTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec > Running org.jboss.as.naming.NamingEventCoordinatorTestCase > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec > Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec > Running org.jboss.as.naming.InMemoryNamingStoreTestCase > Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec > Running org.jboss.as.naming.ObjectFactoryTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec > Running org.jboss.as.naming.NamingContextTestCase > Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec > Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec > Results : > Tests in error: > testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null > Tests run: 70, Failures: 0, Errors: 1, Skipped: 0 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s] > [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s] > [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s] > [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s] > [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s] > [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s] > [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s] > [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s] > [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s] > [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s] > [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s] > [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s] > [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s] > [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s] > [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s] > [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s] > [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s] > [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s] > [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s] > [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s] > [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s] > [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s] > [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s] > [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s] > [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED > [INFO] JBoss Application Server: EE ...................... SKIPPED > [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED > [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED > [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED > [INFO] JBoss Application Server: Clustering Server API ... SKIPPED > [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED > [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED > [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED > [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED > [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED > [INFO] JBoss Application Server: Clustered registry service SKIPPED > [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED > [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED > [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED > [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED > [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED > [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED > [INFO] JBoss Application Server: Config Assembly ......... SKIPPED > [INFO] JBoss Application Server: Command line interface .. SKIPPED > [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED > [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED > [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED > [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED > [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED > [INFO] JBoss Application Server: Clustered singleton services SKIPPED > [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED > [INFO] JBoss Application Server: Config Admin ............ SKIPPED > [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED > [INFO] JBoss Application Server: EE Deployment ........... SKIPPED > [INFO] JBoss Application Server: Embedded ................ SKIPPED > [INFO] JBoss Application Server: JAXR Client ............. SKIPPED > [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED > [INFO] JBoss Application Server: JPA SPI ................. SKIPPED > [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED > [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Weld Integration ........ SKIPPED > [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED > [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED > [INFO] JBoss Application Server: JDR ..................... SKIPPED > [INFO] JBoss Application Server: JSF ..................... SKIPPED > [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED > [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED > [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED > [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED > [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED > [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED > [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED > [INFO] JBoss Application Server: OSGi .................... SKIPPED > [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED > [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED > [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED > [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED > [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED > [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED > [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED > [INFO] JBoss Application Server: System JMX Module ....... SKIPPED > [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED > [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED > [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED > [INFO] JBoss Application Server: Build ................... SKIPPED > [INFO] JBoss Application Server: Build Modular ........... SKIPPED > [INFO] JBoss Application Server: Arquillian .............. SKIPPED > [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED > [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED > [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED > [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED > [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED > [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED > [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED > [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED > [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED > [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED > [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED > [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED > [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED > [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED > [INFO] JBoss Application Server: Distribution ............ SKIPPED > [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED > [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED > [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED > [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED > [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED > [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED > [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED > [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 6:36.380s > [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013 > [INFO] Final Memory: 122M/348M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures. > [ERROR] > [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :jboss-as-naming -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6935) Deploying dynamic VDB with invalid XML will cause incomprehensible error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6935?page=com.atlassian.jira.plugin.s... ] Steven Hawkins moved TEIID-2474 to AS7-6935: -------------------------------------------- Project: Application Server 7 (was: Teiid) Key: AS7-6935 (was: TEIID-2474) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.1.Final (was: 8.3) > Deploying dynamic VDB with invalid XML will cause incomprehensible error > ------------------------------------------------------------------------ > > Key: AS7-6935 > URL: https://issues.jboss.org/browse/AS7-6935 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Filip Nguyen > Assignee: Steven Hawkins > Priority: Trivial > Attachments: loop-vdb.xml > > > Deploying VDB with invalid XML (closed translator tag). Causes following error: > [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment standalone/deployments/loop-vdb.xml. Deployment changes will not be processed until all content is complete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6935) Deploying dynamic VDB with invalid XML will cause incomprehensible error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6935?page=com.atlassian.jira.plugin.s... ] Steven Hawkins updated AS7-6935: -------------------------------- Assignee: (was: Steven Hawkins) > Deploying dynamic VDB with invalid XML will cause incomprehensible error > ------------------------------------------------------------------------ > > Key: AS7-6935 > URL: https://issues.jboss.org/browse/AS7-6935 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Filip Nguyen > Priority: Trivial > Attachments: loop-vdb.xml > > > Deploying VDB with invalid XML (closed translator tag). Causes following error: > [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment standalone/deployments/loop-vdb.xml. Deployment changes will not be processed until all content is complete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1622) Add a commandline troubleshooting tool

by Ray Tsang (JIRA)

[ https://issues.jboss.org/browse/JGRP-1622?page=com.atlassian.jira.plugin.... ] Ray Tsang commented on JGRP-1622: --------------------------------- Manik mentioned there was a command line tool but it's no longer in the distro... Can it be added back? > Add a commandline troubleshooting tool > -------------------------------------- > > Key: JGRP-1622 > URL: https://issues.jboss.org/browse/JGRP-1622 > Project: JGroups > Issue Type: Feature Request > Reporter: Ray Tsang > Assignee: Bela Ban > > There is currently a troubleshooting tool called "draw" documented here: http://www.jgroups.org/tutorial-3.x/html/ch01.html#d0e130 > In many troubleshooting scenarios, however, command line only troubleshooting tool would be much easier to use (since a lot of troubleshooting occurs in a remote server anyways). > Proposing to create a commandline only tool that can probably simply echo what gets typed between nodes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-63) Add a flag to rotate files on boot for SizeRotatingFileHandler

by Dimitris Andreadis (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-63?page=com.atlassian.jira.plugin.... ] Dimitris Andreadis updated LOGMGR-63: ------------------------------------- Labels: eap62 (was: ) > Add a flag to rotate files on boot for SizeRotatingFileHandler > -------------------------------------------------------------- > > Key: LOGMGR-63 > URL: https://issues.jboss.org/browse/LOGMGR-63 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Labels: eap62 > Fix For: 1.4.2.Final > > > Generally speaking on-boot means when the file is set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1622) Add a commandline troubleshooting tool

by Ray Tsang (JIRA)

Ray Tsang created JGRP-1622: ------------------------------- Summary: Add a commandline troubleshooting tool Key: JGRP-1622 URL: https://issues.jboss.org/browse/JGRP-1622 Project: JGroups Issue Type: Feature Request Reporter: Ray Tsang Assignee: Bela Ban There is currently a troubleshooting tool called "draw" documented here: http://www.jgroups.org/tutorial-3.x/html/ch01.html#d0e130 In many troubleshooting scenarios, however, command line only troubleshooting tool would be much easier to use (since a lot of troubleshooting occurs in a remote server anyways). Proposing to create a commandline only tool that can probably simply echo what gets typed between nodes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6934) Update add-user utility to allow overrides of property file name.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-6934: ------------------------------------- Summary: Update add-user utility to allow overrides of property file name. Key: AS7-6934 URL: https://issues.jboss.org/browse/AS7-6934 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management, Scripts Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 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 April 2013