January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBVFS-199) RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/JBVFS-199?page=com.atlassian.jira.plugin.... ] Enrique González Martínez updated JBVFS-199: -------------------------------------------- Git Pull Request: https://github.com/jbossas/jboss-vfs/pull/20, https://github.com/jbossas/jboss-vfs/pull/22 (was: https://github.com/jbossas/jboss-vfs/pull/20) > RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb > ------------------------------------------------------------------------------------------------------------------ > > Key: JBVFS-199 > URL: https://issues.jboss.org/browse/JBVFS-199 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.5.Final, 3.5.0.Alpha1 > Environment: Windows 64 bits > JDK 1.7.0_71 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 3.2.8.Final, 3.5.0.Alpha1 > > > In Wildfly, during jsp compilation the lookup function uses the Classloader::getResourceAsStream that relies on VFSResourceLoader for opening an InputStream. This function is working different due to windows file system (not case sensitive). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-491) Improve ManagedAuditLoggerImpl.log() performance when disabled

by James Livingston (JIRA)

James Livingston created WFCORE-491: --------------------------------------- Summary: Improve ManagedAuditLoggerImpl.log() performance when disabled Key: WFCORE-491 URL: https://issues.jboss.org/browse/WFCORE-491 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 1.0.0.Alpha15 Reporter: James Livingston Assignee: Brian Stansberry Priority: Minor org.jboss.as.controller.audit.ManagedAuditLoggerImpl.log/logJmxMethodAccess() does some work such as creating the log item which will just be thrown away if getLoggerStatus()==DISABLED. It may be worth checking if that is the case and skipping the work that will not be needed. If it was not for the applyHandlerUpdates() call, I think an "isDisabled" volatile flag could be used to avoid taking the lock at all there, which can be expensive due to it being a fair lock. This does not appear to show up as a issue unless you are performing a lot (thousands) of management operations in quick succession. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4213) LogViewer does not allow you to view server.log correctly

by Carlton Zachary (JIRA)

Carlton Zachary created WFLY-4213: ------------------------------------- Summary: LogViewer does not allow you to view server.log correctly Key: WFLY-4213 URL: https://issues.jboss.org/browse/WFLY-4213 Project: WildFly Issue Type: Bug Affects Versions: 8.2.0.Final Reporter: Carlton Zachary Assignee: Jason Greene The LogView does not allow you to page through the full server.log length. Also, when you click on the "Tail" button, it does not go to the end of the server.log. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-676) Optional SortedMap semantics for matching

by Paul Houle (JIRA)

Paul Houle created DROOLS-676: --------------------------------- Summary: Optional SortedMap semantics for matching Key: DROOLS-676 URL: https://issues.jboss.org/browse/DROOLS-676 Project: Drools Issue Type: Feature Request Affects Versions: 6.2.0.CR3 Environment: any Reporter: Paul Houle Assignee: Mark Proctor Drools uses a Map instead of a SortedMap to accelerate the matching of patterns that have an equality relationship. Performance-wise this is the right decision most of the time, but if one wanted to accelerate matching of patterns such as Person(age > 100) having a sorted index could be beneficial. In a case like that the object in question must implement Comparable or be associated with a Comparator. This behavior could be turned on for a particular field with @-annotation in either the DRL or Java file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-675) Query Optimization for RHS by changing pattern match order

by Paul Houle (JIRA)

Paul Houle created DROOLS-675: --------------------------------- Summary: Query Optimization for RHS by changing pattern match order Key: DROOLS-675 URL: https://issues.jboss.org/browse/DROOLS-675 Project: Drools Issue Type: Enhancement Affects Versions: 6.2.0.CR3 Environment: any Reporter: Paul Houle Assignee: Mark Proctor I've been using Drools for what I consider "small" semantic databases, right now in the range of 1M-10M facts but that could get bigger. One thing I notice is that performance is dependent on the order that I put patterns in the RHS; if the high selectivity patterns go first I am happy with the results but put them in the wrong order and gee wiz, I won't wait long enough for it to try all the matches that fail. I see Drools as competitive with products such as triple stores, deductive databases and many of them have this feature -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4209) My Netbeans IDE cannot find wildfly 8.2 final domain and the domain path wen adding wildfly 8.2 server to the NetBean IDE

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4209?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4209: --------------------------------- Assignee: Emmanuel Hugonnet (was: Jason Greene) > My Netbeans IDE cannot find wildfly 8.2 final domain and the domain path wen adding wildfly 8.2 server to the NetBean IDE > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4209 > URL: https://issues.jboss.org/browse/WFLY-4209 > Project: WildFly > Issue Type: Feature Request > Reporter: oma sung > Assignee: Emmanuel Hugonnet > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4209) My Netbeans IDE cannot find wildfly 8.2 final domain and the domain path wen adding wildfly 8.2 server to the NetBean IDE

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-4209?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-4209: ------------------------------------ Please create a discussion in the forums here https://developer.jboss.org/en/wildfly/content to discuss about this. > My Netbeans IDE cannot find wildfly 8.2 final domain and the domain path wen adding wildfly 8.2 server to the NetBean IDE > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4209 > URL: https://issues.jboss.org/browse/WFLY-4209 > Project: WildFly > Issue Type: Feature Request > Reporter: oma sung > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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 January 2015