[JBoss JIRA] (WFLY-5570) Connection validation is now default
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-5570?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen reassigned WFLY-5570:
-------------------------------------
Assignee: Stefano Maestri (was: Jesper Pedersen)
VALIDATE_ON_MATCH and BACKGROUNDVALIDATION must both be FALSE by default
> Connection validation is now default
> ------------------------------------
>
> Key: WFLY-5570
> URL: https://issues.jboss.org/browse/WFLY-5570
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.CR3
> Reporter: Ståle Pedersen
> Assignee: Stefano Maestri
> Priority: Blocker
>
> In previous version the validation of connections was either off or set to be run in the background. In WF10RC2 connections are validated when they are fetched from the pool, the connection is validated before it is leased. This cause a huge contention on moderate to heavy db load and should not be the default behaviour.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 10 months
[JBoss JIRA] (WFCORE-1029) ManagedSocketFactory doesn't work for client sockets
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1029?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1029:
------------------------------------------
I'll keep this open because at a minimum UnnamedBindingRegistry should have javadoc declaring that the sockets and channels passed into the various register methods must be bound. Using something other than InetSocketAddress as the map key may be fine too. The basic goal here is to record all the sockets the server is opening so we can provide a comprehensive management view, so forcing people to bind before registering just gets in the way of them using the registry and may cause them to skip it. The main criteria should be "only register something you intend to bind."
> ManagedSocketFactory doesn't work for client sockets
> ----------------------------------------------------
>
> Key: WFCORE-1029
> URL: https://issues.jboss.org/browse/WFCORE-1029
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.0.CR5
> Reporter: Dennis Reed
> Assignee: Brian Stansberry
>
> SocketBindingManagerImpl does not work with client sockets.
> It adds sockets to a map based on local address. Client sockets that have not been bound yet do not have a local address.
> This breaks the JGroups subsystem's ManagedSocketFactory, which uses SocketBindingManagerImpl for both server and client sockets.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 10 months
[JBoss JIRA] (WFLY-5570) Connection validation is now default
by Ståle Pedersen (JIRA)
Ståle Pedersen created WFLY-5570:
------------------------------------
Summary: Connection validation is now default
Key: WFLY-5570
URL: https://issues.jboss.org/browse/WFLY-5570
Project: WildFly
Issue Type: Bug
Components: JCA
Affects Versions: 10.0.0.CR3
Reporter: Ståle Pedersen
Assignee: Jesper Pedersen
Priority: Blocker
In previous version the validation of connections was either off or set to be run in the background. In WF10RC2 connections are validated when they are fetched from the pool, the connection is validated before it is leased. This cause a huge contention on moderate to heavy db load and should not be the default behaviour.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 10 months
[JBoss JIRA] (ELY-343) Add a basic but configrable CredentialMapper implementation
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-343:
------------------------------------
Summary: Add a basic but configrable CredentialMapper implementation
Key: ELY-343
URL: https://issues.jboss.org/browse/ELY-343
Project: WildFly Elytron
Issue Type: Enhancement
Components: Passwords
Reporter: Darran Lofthouse
Fix For: 1.1.0.Alpha3
Our subsystem is going to require definitions for the credential mapping rules, however the implementation behind that mapping can live in the Elytron project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 10 months
[JBoss JIRA] (DROOLS-913) Memory leak when deleting a tuple from an unlinked segment
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-913?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-913:
------------------------------------------------
Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1263495|https://bugzilla.redhat.com/show_bug.cgi?id=1263495] from ON_QA to VERIFIED
> Memory leak when deleting a tuple from an unlinked segment
> ----------------------------------------------------------
>
> Key: DROOLS-913
> URL: https://issues.jboss.org/browse/DROOLS-913
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.3.0.Final
>
>
> When deleting an object from a session all references to the object itself and the fact handle holding it should disappear. Unfortunately, as demonstrated by the test case below, in some case the deleted fact can remain as a deleted left tuple in the memory of an unlinked segment.
> {code}
> @Test
> public void testBetaMemoryLeakOnFactDelete() {
> String drl =
> "rule R1 when\n" +
> " $a : Integer(this == 1)\n" +
> " $b : String()\n" +
> " $c : Integer(this == 2)\n" +
> "then \n" +
> "end\n" +
> "rule R2 when\n" +
> " $a : Integer(this == 1)\n" +
> " $b : String()\n" +
> "then \n" +
> "end\n";
> KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL )
> .build()
> .newKieSession();
> FactHandle fh1 = ksession.insert(1);
> FactHandle fh2 = ksession.insert("test");
> ksession.fireAllRules();
> ksession.delete(fh1);
> ksession.delete(fh2);
> ksession.fireAllRules();
> NodeMemories nodeMemories = ((InternalWorkingMemory) ksession).getNodeMemories();
> for (int i = 0; i < nodeMemories.length(); i++) {
> Memory memory = nodeMemories.peekNodeMemory( i );
> if ( memory != null && memory.getSegmentMemory() != null ) {
> SegmentMemory segmentMemory = memory.getSegmentMemory();
> System.out.println( memory );
> LeftTuple deleteFirst = memory.getSegmentMemory().getStagedLeftTuples().getDeleteFirst();
> System.out.println( deleteFirst );
> assertNull( deleteFirst );
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 10 months
[JBoss JIRA] (ELY-294) Formal definition of credential names
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-294?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse commented on ELY-294:
--------------------------------------
Although the title is 'Formal' definition this is really central definition of the names used by default within Elytron.
> Formal definition of credential names
> -------------------------------------
>
> Key: ELY-294
> URL: https://issues.jboss.org/browse/ELY-294
> Project: WildFly Elytron
> Issue Type: Task
> Components: API / SPI
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Alpha2
>
>
> ELY-282 switches the realm APIs so that credentials are queried based on names - these names at the very least form a part of our default API so we need to ensure they are defined somewhere.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 10 months
[JBoss JIRA] (DROOLS-945) Rule propagation
by Sante Stanisci (JIRA)
[ https://issues.jboss.org/browse/DROOLS-945?page=com.atlassian.jira.plugin... ]
Sante Stanisci closed DROOLS-945.
---------------------------------
Release Notes Text: i not have replaced case. i close issue for new test
Resolution: Won't Do
> Rule propagation
> ----------------
>
> Key: DROOLS-945
> URL: https://issues.jboss.org/browse/DROOLS-945
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: Sante Stanisci
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: correct rule.drl, rule.drl, RuleTester.java, WdtbOrdr.java, WdtbOrdt.java
>
>
> I have annotate class with @propertyreactive. If i set a property that fire another rule, it no fire.
> i use this StatelessKieSession and execute on class with
> ksession.execute(instance)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 10 months
[JBoss JIRA] (DROOLS-964) Kie Drools WB - Startup error(org.eclipse.jgit.util.FS.readPipe)
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-964?page=com.atlassian.jira.plugin... ]
Michael Anstis commented on DROOLS-964:
---------------------------------------
Hi Michael,
It's not urgent and does not impact operation. It was observed by a community user.
We'd need to build all the way to kie-wb-distributions and test on Windows (that doesn't have git installed)..
Personally, I'd opt to try by overriding first... as if it causes more pain than we have time to fix at the moment we can probably live with the older version for now.
> Kie Drools WB - Startup error(org.eclipse.jgit.util.FS.readPipe)
> ----------------------------------------------------------------
>
> Key: DROOLS-964
> URL: https://issues.jboss.org/browse/DROOLS-964
> Project: Drools
> Issue Type: Bug
> Components: tools
> Affects Versions: 6.3.0.Final
> Environment: Tomcat 7 / 8
> 6.3.0.Final
> Reporter: Jebuselwyn Martin
> Assignee: Michael Biarnes Kiefer
> Priority: Minor
>
> Issue in startup of DroolsWB + Drools Execution Server
> 23-Oct-2015 15:40:18.898 SEVERE [localhost-startStop-1] org.eclipse.jgit.util.FS.readPipe Caught exception in FS.readPipe()
> java.io.IOException: Cannot run program "bash" (in directory "C:\Users\selwyn.martin"): CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at org.eclipse.jgit.util.FS.readPipe(FS.java:431)
> at org.eclipse.jgit.util.FS_Win32.discoverGitPrefix(FS_Win32.java:113)
> at org.eclipse.jgit.util.FS.gitPrefix(FS.java:517)
> at org.eclipse.jgit.util.SystemReader$Default.openSystemConfig(SystemReader.java:92)
> at org.eclipse.jgit.internal.storage.file.FileRepository.<init>(FileRepository.java:171)
> at org.eclipse.jgit.lib.BaseRepositoryBuilder.build(BaseRepositoryBuilder.java:577)
> at org.eclipse.jgit.api.InitCommand.call(InitCommand.java:113)
> at org.uberfire.java.nio.fs.jgit.util.JGitUtil.newRepository(JGitUtil.java:104)
> at org.uberfire.java.nio.fs.jgit.JGitFileSystemProvider.rescanForExistingRepositories(JGitFileSystemProvider.java:407)
> at org.uberfire.java.nio.fs.jgit.JGitFileSystemProvider.<init>(JGitFileSystemProvider.java:371)
> at org.uberfire.java.nio.fs.jgit.JGitFileSystemProvider.<init>(JGitFileSystemProvider.java:343)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at java.lang.Class.newInstance(Class.java:442)
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
> at org.uberfire.java.nio.file.api.FileSystemProviders.buildProviders(FileSystemProviders.java:65)
> at org.uberfire.java.nio.file.api.FileSystemProviders.setup(FileSystemProviders.java:48)
> at org.uberfire.java.nio.file.api.FileSystemProviders.resolveProvider(FileSystemProviders.java:104)
> at org.uberfire.java.nio.file.FileSystems.newFileSystem(FileSystems.java:117)
> at org.uberfire.java.nio.file.FileSystems.newFileSystem(FileSystems.java:83)
> at org.uberfire.io.impl.AbstractIOService.newFileSystem(AbstractIOService.java:241)
> at org.uberfire.backend.server.cdi.SystemConfigProducer$2.create(SystemConfigProducer.java:252)
> at org.uberfire.backend.server.cdi.SystemConfigProducer$2.create(SystemConfigProducer.java:187)
> at org.jboss.weld.context.AbstractContext.get(AbstractContext
> https://groups.google.com/forum/#!topic/drools-setup/qCMYwdOiBAI
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 10 months