October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9427) JDBC_PING gets a NameNotFoundException when using jndi resource

by Alessandro Moscatelli (JIRA)

Alessandro Moscatelli created WFLY-9427: ------------------------------------------- Summary: JDBC_PING gets a NameNotFoundException when using jndi resource Key: WFLY-9427 URL: https://issues.jboss.org/browse/WFLY-9427 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.CR1 Reporter: Alessandro Moscatelli Assignee: Paul Ferraro Fix For: 11.0.0.Final JDBC_PING if configured with jndi resources will cause : IllegalArgumentException: Could not lookup datasource NameNotFoundException IllegalStateException The same jndi resource is correctly found and used by a deployed application. It seems the jndi resouce is not ready, yet, when JGROUPS needs it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-403) jbxb_1_0.xsd is invalid

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBMETA-403?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBMETA-403: ------------------------------------ Added a PR: https://github.com/jboss/metadata/pull/114 Bug found like validating all schema we add to jbosstools. > jbxb_1_0.xsd is invalid > ----------------------- > > Key: JBMETA-403 > URL: https://issues.jboss.org/browse/JBMETA-403 > Project: JBoss Metadata > Issue Type: Bug > Components: common > Reporter: Rob Stryker > > Steps to reproduce: > 1) Open https://github.com/jboss/metadata/blob/master/common/src/main/resources/s... > 2) Copy the text of the xsd > 3) Go to http://www.utilities-online.info/xsdvalidation/ > 4) Paste the xsd into the text box on the right > 5) Click the button under the text box on the right > 6) Note the errors > Not valid. > Error - Line 94, 47: org.xml.sax.SAXParseException; lineNumber: 94; columnNumber: 47; src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element. > Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve.4.2: Error resolving component 'jbxb:package'. It was detected that 'jbxb:package' is in namespace 'http://www.jboss.org/xml/ns/jbxb', but components from this namespace are not referenceable from schema document 'null'. If this is the incorrect namespace, perhaps the prefix of 'jbxb:package' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'null'. > Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve: Cannot resolve the name 'jbxb:package' to a(n) 'element declaration' component. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-403) jbxb_1_0.xsd is invalid

by Rob Stryker (JIRA)

Rob Stryker created JBMETA-403: ---------------------------------- Summary: jbxb_1_0.xsd is invalid Key: JBMETA-403 URL: https://issues.jboss.org/browse/JBMETA-403 Project: JBoss Metadata Issue Type: Bug Components: common Reporter: Rob Stryker Steps to reproduce: 1) Open https://github.com/jboss/metadata/blob/master/common/src/main/resources/s... 2) Copy the text of the xsd 3) Go to http://www.utilities-online.info/xsdvalidation/ 4) Paste the xsd into the text box on the right 5) Click the button under the text box on the right 6) Note the errors Not valid. Error - Line 94, 47: org.xml.sax.SAXParseException; lineNumber: 94; columnNumber: 47; src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element. Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve.4.2: Error resolving component 'jbxb:package'. It was detected that 'jbxb:package' is in namespace 'http://www.jboss.org/xml/ns/jbxb', but components from this namespace are not referenceable from schema document 'null'. If this is the incorrect namespace, perhaps the prefix of 'jbxb:package' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'null'. Error - Line 19, 77: org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 77; src-resolve: Cannot resolve the name 'jbxb:package' to a(n) 'element declaration' component. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1393) Allow match-host rule to match suffix wildcards and IP address ranges

by David Lloyd (JIRA)

David Lloyd created ELY-1393: -------------------------------- Summary: Allow match-host rule to match suffix wildcards and IP address ranges Key: ELY-1393 URL: https://issues.jboss.org/browse/ELY-1393 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.0.Beta6 It would be nice if the match host rule could be expanded to match patterns as follows: * Allow {{*}} to match everything (this is already supported) * Allow strings of the form {{*.myhost.com}} * Allow IP address matching (this is already supported) * Allow CIDR block matching e.g. {{10.54.0.0/16}} This would allow authentication rules to be much simpler in some cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3324) Add a commands line flag to disable request validation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3324?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3324: ------------------------------------- Issue Type: Feature Request (was: Enhancement) > Add a commands line flag to disable request validation > ------------------------------------------------------ > > Key: WFCORE-3324 > URL: https://issues.jboss.org/browse/WFCORE-3324 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Affects Versions: 3.0.3.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Minor > > While the CLI supports enabling/disabling request validation this behavior can't be set from the command line. A command line flag for this should be added. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-849: --------------------------------- Priority: Critical (was: Blocker) > Rename setMechanismProperties to setSaslMechanismProperties > ----------------------------------------------------------- > > Key: ELY-849 > URL: https://issues.jboss.org/browse/ELY-849 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta6 > > > If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties. > We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9426) ISPN000065 in ha-singleton-service QS

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9426?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved JBEAP-13434 to WFLY-9426: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9426 (was: JBEAP-13434) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Affects Version/s: (was: 7.1.0.CR2) > ISPN000065 in ha-singleton-service QS > ------------------------------------- > > Key: WFLY-9426 > URL: https://issues.jboss.org/browse/WFLY-9426 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: eap7.1-ok-for-cr3 > > Following error is logged when testing singleton service failover for the primary-only example: > {code} > ISPN000065: Exception while marshalling object: ExceptionResponse: org.infinispan.IllegalLifecycleStateException: Cache marshaller has been stopped > {code} > This is probably caused by Infinispan not shutting down gracefully as reported in JBEAP-8930. We should document this in the README with link to the functional bug as known issue when testing the failover scenarios for users to be aware they can see this message. > [~rhusar], I have seen this error message in primary-only example, but I think it can occur in the second one, too. What do you think? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3347) add-content operation of deployment resource contains alternative attributes that doesn't exist

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3347?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3347: ---------------------------------------- Assignee: (was: Brian Stansberry) There's a fair amount of reusing the same AttributeDefinition instances for different bits of the deployment management API, so I'm not surprised little inconsistencies like this creep in. > add-content operation of deployment resource contains alternative attributes that doesn't exist > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-3347 > URL: https://issues.jboss.org/browse/WFCORE-3347 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Priority: Minor > > add-content operation contains "content" attribute, > {code} > /deployment=*:read-operation-description(name=add-content) > {code} > "content" attribute it is a list of other attributes as: input-stream-index, hash, bytes, url. They themselves contains the alternatives metadata as > {code} > "url" => { > "type" => STRING, > "description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "alternatives" => [ > "input-stream-index", > "hash", > "bytes", > "path", > "relative-to", > "empty" > ], > "min-length" => 1L, > "max-length" => 2147483647L > }, > {code} > But the following attributes doesn't exist: path, relative-to, empty -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9424) Wildfly 10.1.0.Final - Very long deploy time on Windows 10

by Nándor Holozsnyák (JIRA)

[ https://issues.jboss.org/browse/WFLY-9424?page=com.atlassian.jira.plugin.... ] Nándor Holozsnyák updated WFLY-9424: ------------------------------------ Priority: Major (was: Minor) > Wildfly 10.1.0.Final - Very long deploy time on Windows 10 > ---------------------------------------------------------- > > Key: WFLY-9424 > URL: https://issues.jboss.org/browse/WFLY-9424 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Reporter: Nándor Holozsnyák > Assignee: Jason Greene > > I am having a really annoying "problem" with Wildfly. I have been using it for at least two years now and I really don't know what could be the problem. > So I have a fresh Windows 10 64 bit install, and then I started working on my projects as well which was started earlier and there were no problem with the deploy time. > I just pulled my stuff from VCS and then when I started to deploy it with Wildfly (as well as with Maven's Wildfly plugin and as well as put the .war into the deployments folder) the server prints out "Starting deployment ..." and then hangs for two minutes!! Always two minutes then deploy the application. It happens with no one project, with at least three, on my other laptop which has Windows 7 everything works fine. > I decided to download the wildfly quickstart repo and then try it out. With one EJB project it works well, deploy goes as a new Lambo. I tried to log the wildfly with trace to get some more information but nothing special came. Wildfly maven plugin was in debug too but no more information. Wildfly memory settings are upgraded to 1 GB, but no luck. I am going to write out a ticket, but it is a bit frustrating. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6777) Upgrade to OpenJPA impl compatible with JDK9

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6777?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6777: ---------------------------------------- [~smarlow] Can this be resolved? > Upgrade to OpenJPA impl compatible with JDK9 > -------------------------------------------- > > Key: WFLY-6777 > URL: https://issues.jboss.org/browse/WFLY-6777 > Project: WildFly > Issue Type: Sub-task > Components: JPA / Hibernate > Reporter: Tomaz Cerar > Assignee: Scott Marlow > Priority: Minor > > OpenJPA tests currently hang our testsuite as serp bytecode enhancer that OpenJPA uses hangs the deployment. > For now test is not run on JDK9, but this should be re-enabled once there is release of openjpa that works fine with jdk9 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 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 2017