February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6615) Invalid definition for HC root resource remote domain controller

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6615: ------------------------------------- Summary: Invalid definition for HC root resource remote domain controller Key: AS7-6615 URL: https://issues.jboss.org/browse/AS7-6615 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.2.0.Alpha1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.3.0.Alpha1 HostResourceDefinition.DC_REMOTE does not include the security-realm and username fields. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-38) Check that deployment was actually successful

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-38?page=com.atlassian.jira.plugin.... ] James Perkins resolved JBASMP-38. --------------------------------- Fix Version/s: (was: 7.4.Final) Resolution: Rejected Fix for JBASMP-35 fixed this. > Check that deployment was actually successful > --------------------------------------------- > > Key: JBASMP-38 > URL: https://issues.jboss.org/browse/JBASMP-38 > Project: JBoss AS Maven Plugins > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > > Currently failures are only reported if the deployment throws an exception. Verify the deployment exists and it's status. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-38) Check that deployment was actually successful

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-38?page=com.atlassian.jira.plugin.... ] James Perkins closed JBASMP-38. ------------------------------- > Check that deployment was actually successful > --------------------------------------------- > > Key: JBASMP-38 > URL: https://issues.jboss.org/browse/JBASMP-38 > Project: JBoss AS Maven Plugins > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > > Currently failures are only reported if the deployment throws an exception. Verify the deployment exists and it's status. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-5612) Add clear cache operation on cache container and cache (accessible via admin console)

by Guillaume Grossetie (JIRA)

[ https://issues.jboss.org/browse/AS7-5612?page=com.atlassian.jira.plugin.s... ] Guillaume Grossetie updated AS7-5612: ------------------------------------- Git Pull Request: https://github.com/jbossas/jboss-as/pull/3101 > Add clear cache operation on cache container and cache (accessible via admin console) > ------------------------------------------------------------------------------------- > > Key: AS7-5612 > URL: https://issues.jboss.org/browse/AS7-5612 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console, Domain Management > Affects Versions: 7.1.1.Final > Reporter: Guillaume Grossetie > Assignee: Guillaume Grossetie > Fix For: Open To Community > > > Add operation on infinispan subsystem to clear cache at cache container level (ie. clear all caches for the container) and at cache level. > The implementation of the clear operation just calls the method #clear() on the org.infinispan.Cache interface. If needed we can clear the associated CacheStore (make it optional ?) and handle more complex cases. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6565) single jdbc driver deployed inside ear takes name of ear

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ] Frank Langelage commented on AS7-6565: -------------------------------------- The name of this issue mentions drivers inside ear. But with this source changes also drivers deployed as single jar files get this new naming scheme. Having these files -rw-r--r-- 1 jboss informix 869737 Jul 6 2012 ifxjdbc_all.jar -rw-r--r-- 1 jboss informix 2714016 Aug 23 2011 ojdbc6.jar -rw-r--r-- 1 jboss informix 584207 Mar 1 2012 sqljdbc4.jar in deployments folder I get [standalone@localhost:10699 /] /subsystem=datasources:installed-drivers-list { "outcome" => "success", "result" => [ { "driver-name" => "sqljdbc4.jar_com.microsoft.sqlserver.jdbc.SQLServerDriver_4_0", "deployment-name" => "sqljdbc4.jar_com.microsoft.sqlserver.jdbc.SQLServerDriver_4_0", "driver-module-name" => undefined, "module-slot" => undefined, "driver-datasource-class-name" => undefined, "driver-xa-datasource-class-name" => undefined, "driver-class-name" => "com.microsoft.sqlserver.jdbc.SQLServerDriver", "driver-major-version" => 4, "driver-minor-version" => 0, "jdbc-compliant" => true }, { "driver-name" => "ojdbc6.jar_oracle.jdbc.OracleDriver_11_2", "deployment-name" => "ojdbc6.jar_oracle.jdbc.OracleDriver_11_2", "driver-module-name" => undefined, "module-slot" => undefined, "driver-datasource-class-name" => undefined, "driver-xa-datasource-class-name" => undefined, "driver-class-name" => "oracle.jdbc.OracleDriver", "driver-major-version" => 11, "driver-minor-version" => 2, "jdbc-compliant" => true }, { "driver-name" => "ifxjdbc_all.jar_com.informix.jdbc.IfxDriver_3_70", "deployment-name" => "ifxjdbc_all.jar_com.informix.jdbc.IfxDriver_3_70", "driver-module-name" => undefined, "module-slot" => undefined, "driver-datasource-class-name" => undefined, "driver-xa-datasource-class-name" => undefined, "driver-class-name" => "com.informix.jdbc.IfxDriver", "driver-major-version" => 3, "driver-minor-version" => 70, "jdbc-compliant" => true } ] } In server.log I see only 23:07:12,008 INFO [org.jboss.as.server#handleResult] JBAS018559: Deployed "sqljdbc4.jar" (runtime-name : "sqljdbc4.jar") 23:07:12,010 INFO [org.jboss.as.server#handleResult] JBAS018559: Deployed "ojdbc6.jar" (runtime-name : "ojdbc6.jar") 23:07:12,011 INFO [org.jboss.as.server#handleResult] JBAS018559: Deployed "ifxjdbc_all.jar" (runtime-name : "ifxjdbc_all.jar") which means I have to know, that the driver name is different. I have to put for instance this <driver>ifxjdbc_all.jar_com.informix.jdbc.IfxDriver_3_70</driver> into my *-ds.xml file. In my eyes an awful change. Prior to this change I had <driver>ifxjdbc_all.jar</driver> in my *-ds.xml files, simply the name of the jar containing the driver. At least the second goal "2. driver name (as to be used in datasource definition) should be logged with the log message above." is not covered. > single jdbc driver deployed inside ear takes name of ear > -------------------------------------------------------- > > Key: AS7-6565 > URL: https://issues.jboss.org/browse/AS7-6565 > Project: Application Server 7 > Issue Type: Feature Request > Components: JCA > Affects Versions: 7.1.1.Final, 8.0.0.Alpha1 > Reporter: Tom Eicher > Assignee: Stefano Maestri > > We need to always give service name for jdbdriver as > {code} > deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion > {code} > even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names. > Original description was: > Including a JDBC driver, in this case PostgreSQL, in an ear like > {code} > myapp.ear: > lib/postgresql-9.1-901.jdbc4.jar > {code} > does deploy the driver: > {code} > 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) > {code} > however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected, > but it's {{myapp_ear}}. > (Seen in admin console, and this is the only value accepted in my -ds.xml file.) > 1. JDBC driver service should pick name of innermost jar, not of containing ear > 2. driver name (as to be used in datasource definition) should be logged with the log message above. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-38) Check that deployment was actually successful

by James Perkins (JIRA)

James Perkins created JBASMP-38: ----------------------------------- Summary: Check that deployment was actually successful Key: JBASMP-38 URL: https://issues.jboss.org/browse/JBASMP-38 Project: JBoss AS Maven Plugins Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins Fix For: 7.4.Final Currently failures are only reported if the deployment throws an exception. Verify the deployment exists and it's status. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6614) A write-config operation

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6614: ------------------------------------- Summary: A write-config operation Key: AS7-6614 URL: https://issues.jboss.org/browse/AS7-6614 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Operation to force the server to write its config file, without making any actual config change. One use case mentioned was to get the config file updated to the latest xml namespaces following an upgrade. This should be trivial to implement with an operation step handler that simply does context.readResourceForUpdate(PathAddress.EMPT_ADDRESS); context.stepCompleted(); That handler would be registered on: 1) The root resource for a non-managed-domain server (for standalone.xml). 2) The host=* resource on any HostController (for host.xml). 3) The root resource on a HostController that is the master (for domain.xml). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-1833) CLI usability: operations that shutdown the server-side management interface result in "Communication error"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-1833?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-1833: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 914817|https://bugzilla.redhat.com/show_bug.cgi?id=914817] The upstream issue AS7-1833 is resolved against the AS7 Fix Version that is the basis for EAP 6.1.0.DR4. However, subsequent testing for the one-off-patch variant of this (see https://bugzilla.redhat.com/show_bug.cgi?id=910122) has shown remaining work needs to be done. Said work is in progress and seems to be progressing well. This issue is to ensure this work gets into EAP 6.1.0.Final. > CLI usability: operations that shutdown the server-side management interface result in "Communication error" > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-1833 > URL: https://issues.jboss.org/browse/AS7-1833 > Project: Application Server 7 > Issue Type: Enhancement > Components: CLI > Affects Versions: 7.0.0.Final, 7.0.1.Final > Reporter: Radoslav Husar > Assignee: Alexey Loubyansky > Priority: Critical > Labels: eap6-ux > Fix For: 7.2.0.Alpha1 > > > If you shutdown the server, you get an error: > {code} > [standalone@localhost:9999 /] :shutdown > Communication error: Channel closed > Closed connection to localhost:9999 > {code} > Even though its considered by this comment clean - https://issues.jboss.org/browse/AS7-689?focusedCommentId=12614756&page=co... - I is not really clean as you get an error but termination of the channel can be anticipated. Users might be confused now knowing if its an actual error or not. For example take a look at SSH. > The same basic issue exists for the :reload operation. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6390) Problem with jboss versions of xerces and xalan: XML Parsing Error: duplicate attribute in wsdl definitions

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-6390?page=com.atlassian.jira.plugin.s... ] Paul Gier commented on AS7-6390: -------------------------------- Related mailing list discussion: http://lists.jboss.org/pipermail/jboss-as7-dev/2013-February/007582.html > Problem with jboss versions of xerces and xalan: XML Parsing Error: duplicate attribute in wsdl definitions > ----------------------------------------------------------------------------------------------------------- > > Key: AS7-6390 > URL: https://issues.jboss.org/browse/AS7-6390 > Project: Application Server 7 > Issue Type: Bug > Components: Web Services > Affects Versions: 7.1.1.Final > Reporter: Michael Vetter > > We are using a feature (SimpleWsdl11Definition) of spring ws (version 1.5.9) to serve wsdl files to the browser or to a client. > Our wsdl file has custom namespace prefixes like this: > <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:bsf="http:/... > > It works in JBoss 5.1 and eap 6.0.0 but with JBoss 7.1.1 or the current 7.2 snapshot I get the following error when I enter the wsdl URL in the browser: > XML Parsing Error: duplicate attribute > Location: http://localhost:8080/sc-webservices/service/loginServiceWS.wsdl > Line Number 1, Column 671:<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:bsf="http:// > The wsdl served to the browser contains duplicates of the custom namespace prefixes defined in the original wsdl file packaged in a war inside an ear. > While debugging I only saw classes from jboss versions of xerces and xalan parsing the wsdl and serving the result to the client. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-1833) CLI usability: operations that shutdown the server-side management interface result in "Communication error"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-1833?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-1833: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=910122, https://bugzilla.redhat.com/show_bug.cgi?id=914817 (was: https://bugzilla.redhat.com/show_bug.cgi?id=910122) > CLI usability: operations that shutdown the server-side management interface result in "Communication error" > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-1833 > URL: https://issues.jboss.org/browse/AS7-1833 > Project: Application Server 7 > Issue Type: Enhancement > Components: CLI > Affects Versions: 7.0.0.Final, 7.0.1.Final > Reporter: Radoslav Husar > Assignee: Alexey Loubyansky > Priority: Critical > Labels: eap6-ux > Fix For: 7.2.0.Alpha1 > > > If you shutdown the server, you get an error: > {code} > [standalone@localhost:9999 /] :shutdown > Communication error: Channel closed > Closed connection to localhost:9999 > {code} > Even though its considered by this comment clean - https://issues.jboss.org/browse/AS7-689?focusedCommentId=12614756&page=co... - I is not really clean as you get an error but termination of the channel can be anticipated. Users might be confused now knowing if its an actual error or not. For example take a look at SSH. > The same basic issue exists for the :reload operation. -- 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, 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 February 2013