December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3999) cli deployment-overlay --redeploy-affected should check subdeployments as well

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3999?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3999: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1151435|https://bugzilla.redhat.com/show_bug.cgi?id=1151435] from ON_QA to VERIFIED > cli deployment-overlay --redeploy-affected should check subdeployments as well > ------------------------------------------------------------------------------ > > Key: WFLY-3999 > URL: https://issues.jboss.org/browse/WFLY-3999 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 9.0.0.Beta1 > > > This issue has to be fixed in wildfly-core but the overlay tests are in the WildFly testsuite. This issue is for the tests covering this issue in WildFly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-659) Failed to read schema document 'drools-processes-5.0.xsd' in OSGi

by Peter Harsfalvi (JIRA)

Peter Harsfalvi created DROOLS-659: -------------------------------------- Summary: Failed to read schema document 'drools-processes-5.0.xsd' in OSGi Key: DROOLS-659 URL: https://issues.jboss.org/browse/DROOLS-659 Project: Drools Issue Type: Bug Affects Versions: 6.1.0.Final Environment: Apache Karaf 3.0.2 OSGi container Reporter: Peter Harsfalvi Assignee: Mark Proctor Using drools 5 knowledge api with Drools 6.1.0 under OSGi throws the following error. 2014-12-01 16:01:07,886 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 5, 158): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,886 [ERROR] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 5, 158): cvc-elt.1.a: Cannot find the declaration of element 'process'. 2014-12-01 16:01:07,888 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 7, 11): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,889 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 10, 10): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,891 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 11, 72): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,892 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 12, 70): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,893 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 13, 108): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,895 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 16, 16): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,896 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 17, 37): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,898 [WARN ] ExtensibleXmlParser [SpringOsgiExtenderThread-14] (null: 18, 36): schema_reference.4: Failed to read schema document 'drools-processes-5.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2014-12-01 16:01:07,901 [WARN ] RuleBaseConfiguration [SpringOsgiExtenderThread-14] Cannot find drools-reteoo.jar on the classpath, switching to phreak -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2646) Expose patch description through mgmt API

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFLY-2646?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber resolved WFLY-2646. --------------------------------------- Assignee: Emanuel Muckenhuber Resolution: Done > Expose patch description through mgmt API > ----------------------------------------- > > Key: WFLY-2646 > URL: https://issues.jboss.org/browse/WFLY-2646 > Project: WildFly > Issue Type: Feature Request > Components: Patching > Affects Versions: 8.0.0.CR1 > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 9.0.0.Beta1 > > > It should be possible to view the description of an installed patch through the mgmt API (maybe patch history). The information is stored as part of the backed up patch.xml. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4144) Clarification on the semantics of the pre-installed ExampleDS

by Lukas Eder (JIRA)

[ https://issues.jboss.org/browse/WFLY-4144?page=com.atlassian.jira.plugin.... ] Lukas Eder commented on WFLY-4144: ---------------------------------- No, I didn't do that. This is more a feature request from a first-time user experience perspective. I think that new users shouldn't be able to put their WildFly instance in such a state so easily. This is very confusing and completely misleading at the stage where one is evaluating WildFly > Clarification on the semantics of the pre-installed ExampleDS > ------------------------------------------------------------- > > Key: WFLY-4144 > URL: https://issues.jboss.org/browse/WFLY-4144 > Project: WildFly > Issue Type: Enhancement > Affects Versions: 8.2.0.Final > Reporter: Lukas Eder > Assignee: Jason Greene > > I'm a new user of WildFly, and I've spent quite a while figuring out that I apparently shouldn't delete the ExampleDS from my server instance. Once I deleted it: > - My own DataSources could no longer access the H2 driver > - My applications could no longer access their own datasources (even unmanaged ones) > - My applications could no longer be undeployed or redeployed > The only workaround I found was to completely re-install the entire server. > Now, I still don't completely understand the point of this ExampleDS, but I'll just leave it where it is and never touch it again. If this is some internal DataSource that is needed for JavaEE 7 compliance as suggested by Roberto Cortez in this Tweet: > https://twitter.com/radcortez/status/539394425370443776 > ... then I would suggest completely hiding it from the Web Console UI and making it an internal system thing that I'm not going to be concerned with. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4144) Clarification on the semantics of the pre-installed ExampleDS

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4144?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-4144: ------------------------------------ Thanks for the feedback. Did you remove the reference to ExampledDS in the EE subsystem? If so, and it still fails, could you attach any exceptions with stack traces to this issue? > Clarification on the semantics of the pre-installed ExampleDS > ------------------------------------------------------------- > > Key: WFLY-4144 > URL: https://issues.jboss.org/browse/WFLY-4144 > Project: WildFly > Issue Type: Enhancement > Affects Versions: 8.2.0.Final > Reporter: Lukas Eder > Assignee: Jason Greene > > I'm a new user of WildFly, and I've spent quite a while figuring out that I apparently shouldn't delete the ExampleDS from my server instance. Once I deleted it: > - My own DataSources could no longer access the H2 driver > - My applications could no longer access their own datasources (even unmanaged ones) > - My applications could no longer be undeployed or redeployed > The only workaround I found was to completely re-install the entire server. > Now, I still don't completely understand the point of this ExampleDS, but I'll just leave it where it is and never touch it again. If this is some internal DataSource that is needed for JavaEE 7 compliance as suggested by Roberto Cortez in this Tweet: > https://twitter.com/radcortez/status/539394425370443776 > ... then I would suggest completely hiding it from the Web Console UI and making it an internal system thing that I'm not going to be concerned with. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4144) Clarification on the semantics of the pre-installed ExampleDS

by Lukas Eder (JIRA)

Lukas Eder created WFLY-4144: -------------------------------- Summary: Clarification on the semantics of the pre-installed ExampleDS Key: WFLY-4144 URL: https://issues.jboss.org/browse/WFLY-4144 Project: WildFly Issue Type: Enhancement Affects Versions: 8.2.0.Final Reporter: Lukas Eder Assignee: Jason Greene I'm a new user of WildFly, and I've spent quite a while figuring out that I apparently shouldn't delete the ExampleDS from my server instance. Once I deleted it: - My own DataSources could no longer access the H2 driver - My applications could no longer access their own datasources (even unmanaged ones) - My applications could no longer be undeployed or redeployed The only workaround I found was to completely re-install the entire server. Now, I still don't completely understand the point of this ExampleDS, but I'll just leave it where it is and never touch it again. If this is some internal DataSource that is needed for JavaEE 7 compliance as suggested by Roberto Cortez in this Tweet: https://twitter.com/radcortez/status/539394425370443776 ... then I would suggest completely hiding it from the Web Console UI and making it an internal system thing that I'm not going to be concerned with. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4141) MySQLConnector/J version 5.1.34 not working on Wildfly8.2.final

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4141?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4141: --------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > MySQLConnector/J version 5.1.34 not working on Wildfly8.2.final > --------------------------------------------------------------- > > Key: WFLY-4141 > URL: https://issues.jboss.org/browse/WFLY-4141 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2.0.Final > Environment: Ubuntu 14.04.1, Oracle Java 8 update 25, Wildfly 8.2.final > Reporter: Mukund Rajamannar > Assignee: Heiko Braun > > In Wildfly 8.2 domain mode, I am not able to use MySQL Connector/J as a JDBC driver. This works on 8.1.final and it appears to be a regression introduced in 8.2. Please see the section on reproducing the bug for details. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4141) MySQLConnector/J version 5.1.34 not working on Wildfly8.2.final

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4141?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-4141: ------------------------------ Component/s: Web Console (was: Domain Management) > MySQLConnector/J version 5.1.34 not working on Wildfly8.2.final > --------------------------------------------------------------- > > Key: WFLY-4141 > URL: https://issues.jboss.org/browse/WFLY-4141 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2.0.Final > Environment: Ubuntu 14.04.1, Oracle Java 8 update 25, Wildfly 8.2.final > Reporter: Mukund Rajamannar > Assignee: Brian Stansberry > > In Wildfly 8.2 domain mode, I am not able to use MySQL Connector/J as a JDBC driver. This works on 8.1.final and it appears to be a regression introduced in 8.2. Please see the section on reproducing the bug for details. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4141) MySQLConnector/J version 5.1.34 not working on Wildfly8.2.final

by Mukund Rajamannar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4141?page=com.atlassian.jira.plugin.... ] Mukund Rajamannar commented on WFLY-4141: ----------------------------------------- I tried this out using the management web UI. I am not an expert with the CLI, but when I tried to see the list of JDBC drivers, I was only able to the see the default H2 drivers and not the MySQL driver. The deployment of the MySQL jar goes through fine. It doesn't seem to be picking it up as a JDBC driver. > MySQLConnector/J version 5.1.34 not working on Wildfly8.2.final > --------------------------------------------------------------- > > Key: WFLY-4141 > URL: https://issues.jboss.org/browse/WFLY-4141 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.2.0.Final > Environment: Ubuntu 14.04.1, Oracle Java 8 update 25, Wildfly 8.2.final > Reporter: Mukund Rajamannar > Assignee: Brian Stansberry > > In Wildfly 8.2 domain mode, I am not able to use MySQL Connector/J as a JDBC driver. This works on 8.1.final and it appears to be a regression introduced in 8.2. Please see the section on reproducing the bug for details. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4089) ServletContainerInitializerDeploymentProcessor does not handle comments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4089?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4089: ----------------------------------------------- Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 1164600|https://bugzilla.redhat.com/show_bug.cgi?id=1164600] from ON_QA to VERIFIED > ServletContainerInitializerDeploymentProcessor does not handle comments > ----------------------------------------------------------------------- > > Key: WFLY-4089 > URL: https://issues.jboss.org/browse/WFLY-4089 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.Alpha1 > Reporter: James Livingston > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > > ServletContainerInitializerDeploymentProcessor.loadSci() has code to read the service file, rather than using the JDK-provided mechanisms, and it does not handle comments. > The API documentation at https://docs.oracle.com/javase/7/docs/api/java/util/ServiceLoader.html says that the # symbols and all following characters on the line should be ignored. It also notes the file must be UTF-8 encoded, and ServletContainerInitializerDeploymentProcessor does not appear to force that either. > Log4j 2.1 triggers this bug (https://issues.apache.org/jira/browse/LOG4J2-890) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014