[JBoss JIRA] (WFLY-8141) CachedConnectionManager add operation excepts no parameters anymore
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8141?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-8141:
----------------------------------------
We are using this in quickstarts?
AIUI that op never worked. The subsystem adds the resource at boot so any subsequent invocation should have produced a failure.
> CachedConnectionManager add operation excepts no parameters anymore
> -------------------------------------------------------------------
>
> Key: WFLY-8141
> URL: https://issues.jboss.org/browse/WFLY-8141
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 11.0.0.Alpha1
> Reporter: Tomaz Cerar
> Assignee: Ingo Weiss
> Priority: Critical
>
> Fix for WFLY-2640 broke :add operation for cached-connection-manager
> scipts that do
> {noformat}
> /profile=default-web/subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true")
> {noformat}
> {noformat}
> /subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true")
> {noformat}
> now fail with
> {{Operation 'add' does not expect any property.}}
> This breaks our quickstarts
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1443) Improve effect of caching in ChainedProperties.
by Hans Lund (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1443?page=com.atlassian.jira.plugi... ]
Hans Lund commented on DROOLS-1443:
-----------------------------------
The strategy for caching is based on resource name and classloader. Very often the classloader is a ProjectClassLoader - almost always a new instance.
As the ProjectClassLoader do not implement equals and hashCode - the cache quickly runs full.
Implementing hashcode and equals on the ProjectClassLoader and the InMemoryResourceProvider have in test reduced the number of entries in the cache to less than 1% (from +8k entries to 64).
> Improve effect of caching in ChainedProperties.
> -------------------------------------------------
>
> Key: DROOLS-1443
> URL: https://issues.jboss.org/browse/DROOLS-1443
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Hans Lund
> Assignee: Mario Fusco
> Priority: Minor
>
> The ChainedProperties utility has a caching setting that will cache the classpath discovery of property resource - but not the parsing of these resources.
> This utility is a hot spot for the initialization of runtime environments - caching the parsed properties instead of the resource url will improve runtime performance.
> Changing the caching strategy will make hot changes to classpath property resources impossible. File based property files could be made safe cacheable by investigating file metadata and only read if changed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8142) Review & update ejb-multi-server documents
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFLY-8142:
---------------------------------
Summary: Review & update ejb-multi-server documents
Key: WFLY-8142
URL: https://issues.jboss.org/browse/WFLY-8142
Project: WildFly
Issue Type: Enhancement
Components: Quickstarts
Reporter: Tomaz Cerar
Assignee: Sande Gilda
Currently it references bunch of warnings / errors with its jiras.
But those jiras ware fixed and there is no need to keep that in docs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8141) CachedConnectionManager add operation excepts no parameters anymore
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8141?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-8141:
------------------------------
Component/s: Domain Management
JCA
> CachedConnectionManager add operation excepts no parameters anymore
> -------------------------------------------------------------------
>
> Key: WFLY-8141
> URL: https://issues.jboss.org/browse/WFLY-8141
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 11.0.0.Alpha1
> Reporter: Tomaz Cerar
> Assignee: Ingo Weiss
> Priority: Critical
>
> Fix for WFLY-2640 broke :add operation for cached-connection-manager
> scipts that do
> {noformat}
> /profile=default-web/subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true")
> {noformat}
> {noformat}
> /subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true")
> {noformat}
> now fail with
> {{Operation 'add' does not expect any property.}}
> This breaks our quickstarts
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8141) CachedConnectionManager add operation excepts no parameters anymore
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFLY-8141:
---------------------------------
Summary: CachedConnectionManager add operation excepts no parameters anymore
Key: WFLY-8141
URL: https://issues.jboss.org/browse/WFLY-8141
Project: WildFly
Issue Type: Bug
Reporter: Tomaz Cerar
Assignee: Ingo Weiss
Priority: Critical
Fix for WFLY-2640 broke :add operation for cached-connection-manager
scipts that do
{noformat}
/profile=default-web/subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true")
{noformat}
{noformat}
/subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true")
{noformat}
now fail with
{{Operation 'add' does not expect any property.}}
This breaks our quickstarts
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8141) CachedConnectionManager add operation excepts no parameters anymore
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8141?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-8141:
------------------------------
Affects Version/s: 11.0.0.Alpha1
> CachedConnectionManager add operation excepts no parameters anymore
> -------------------------------------------------------------------
>
> Key: WFLY-8141
> URL: https://issues.jboss.org/browse/WFLY-8141
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 11.0.0.Alpha1
> Reporter: Tomaz Cerar
> Assignee: Ingo Weiss
> Priority: Critical
>
> Fix for WFLY-2640 broke :add operation for cached-connection-manager
> scipts that do
> {noformat}
> /profile=default-web/subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true")
> {noformat}
> {noformat}
> /subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true")
> {noformat}
> now fail with
> {{Operation 'add' does not expect any property.}}
> This breaks our quickstarts
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (ELY-880) Unable to set IPv6 address in Elytron authentication context match-host rule
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/ELY-880?page=com.atlassian.jira.plugin.sy... ]
Ilia Vassilev reassigned ELY-880:
---------------------------------
Assignee: (was: Ilia Vassilev)
> Unable to set IPv6 address in Elytron authentication context match-host rule
> ----------------------------------------------------------------------------
>
> Key: ELY-880
> URL: https://issues.jboss.org/browse/ELY-880
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Affects Versions: 1.1.0.Beta18
> Reporter: Martin Choma
>
> Setting IPv6 address in wildfly-config.xml cause validation error.
> {code:xml|title=wildfly-config.xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <authentication-client xmlns="urn:elytron:1.0">
> <authentication-configurations>
> <configuration name="set-host-to-localhost">
> <set-host name="localhost"/>
> </configuration>
> </authentication-configurations>
> <authentication-rules>
> <rule use-configuration="set-host-to-localhost">
> <match-host name="::1"/>
> </rule>
> </authentication-rules>
> </authentication-client>
> {code}
> {code:title=server.log}
> java.lang.IllegalArgumentException: ELY01029: Invalid host specification "::1"
> at org.wildfly.security.auth.client.MatchHostRule.<init>(MatchHostRule.java:39)
> at org.wildfly.security.auth.client.MatchRule.matchHost(MatchRule.java:411)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAbstractMatchRuleType(ElytronXmlParser.java:701)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationRuleType(ElytronXmlParser.java:467)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseRulesType(ElytronXmlParser.java:484)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:241)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:169)
> at org.wildfly.security.auth.client.XmlConfigurationTest.testMatcHostRuleConfiguration(XmlConfigurationTest.java:175)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> {code}
> It is because of elytron validation [1]. However don't know if just allowing ":" in regexp is valid solution.
> [1] https://github.com/wildfly-security/wildfly-elytron/blob/7debbcabc7c20be5...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months