March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-436) Cannot access to remote kie maven repository - Access denied

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-436?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-436: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1059584 > Cannot access to remote kie maven repository - Access denied > ------------------------------------------------------------ > > Key: DROOLS-436 > URL: https://issues.jboss.org/browse/DROOLS-436 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Environment: - Windows 7 64 bits > - JDK 1.7.0.45 > - Drools 6.0.1.Final > Reporter: Rogério Disciolli > Assignee: Mark Proctor > > - Start JBPM 6.0.1.Final binding a specific IP 192.168.0.10 > - Run maven in a remote machine with the pom.xml like this > <repository> > <id>guvnor-m2-repo</id> > <name>Guvnor M2 Repo</name> > <url>http://192.168.0.10:8080/jbpm-console/maven2/</url> > </repository> > Also having username/password in ~/.m2/settings.xml > <servers> > <server> > <id>guvnor-m2-repo</id> > <username>admin</username> > <password>admin</password> > </server> > </servers> > And returned "Access denied (401)" when try get maven-metadata.xml from project. > Can not authenticate at kie maven repository. > The same happens when try run Java Project with VM arguments "-Dkie.maven.settings.custom=settings.xml" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-439: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Package builder unable to find declared array class > --------------------------------------------------- > > Key: DROOLS-439 > URL: https://issues.jboss.org/browse/DROOLS-439 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Mark Sullivan > Assignee: Mario Fusco > > When declaring a fact type with an array field, where the array type is declared in the same package, for example: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > end > {code} > The following build error occurs: > {code} > [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0 > text=Unable to find class 'Owner']] > {code} > This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed. > PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types. > The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies: > {code} > for (TypeFieldDescr field : tdescr.getFields().values()) { > QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType()); > if (!hasCircularDependency(name, typeName, taxonomy)) { > supers.add(typeName); > } > } > {code} > However I don't think it correctly spots the dependency when the field type is an array. > This issue can be worked around by declaring an unused field of the same type as the array: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > _unused: Owner > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-439. -------------------------------- Resolution: Done > Package builder unable to find declared array class > --------------------------------------------------- > > Key: DROOLS-439 > URL: https://issues.jboss.org/browse/DROOLS-439 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Mark Sullivan > Assignee: Mario Fusco > > When declaring a fact type with an array field, where the array type is declared in the same package, for example: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > end > {code} > The following build error occurs: > {code} > [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0 > text=Unable to find class 'Owner']] > {code} > This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed. > PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types. > The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies: > {code} > for (TypeFieldDescr field : tdescr.getFields().values()) { > QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType()); > if (!hasCircularDependency(name, typeName, taxonomy)) { > supers.add(typeName); > } > } > {code} > However I don't think it correctly spots the dependency when the field type is an array. > This issue can be worked around by declaring an unused field of the same type as the array: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > _unused: Owner > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] Peter Skopek updated SECURITY-805: ---------------------------------- Fix Version/s: PicketBox_4_0_19.SP5 > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: PicketBox_4_0_21.Beta2, PicketBox_4_0_19.SP5 > > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-439: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1079950 > Package builder unable to find declared array class > --------------------------------------------------- > > Key: DROOLS-439 > URL: https://issues.jboss.org/browse/DROOLS-439 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Mark Sullivan > Assignee: Mark Proctor > > When declaring a fact type with an array field, where the array type is declared in the same package, for example: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > end > {code} > The following build error occurs: > {code} > [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0 > text=Unable to find class 'Owner']] > {code} > This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed. > PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types. > The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies: > {code} > for (TypeFieldDescr field : tdescr.getFields().values()) { > QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType()); > if (!hasCircularDependency(name, typeName, taxonomy)) { > supers.add(typeName); > } > } > {code} > However I don't think it correctly spots the dependency when the field type is an array. > This issue can be worked around by declaring an unused field of the same type as the array: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > _unused: Owner > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-439?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-439: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1079950|https://bugzilla.redhat.com/show_bug.cgi?id=1079950] from NEW to ASSIGNED > Package builder unable to find declared array class > --------------------------------------------------- > > Key: DROOLS-439 > URL: https://issues.jboss.org/browse/DROOLS-439 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Mark Sullivan > Assignee: Mark Proctor > > When declaring a fact type with an array field, where the array type is declared in the same package, for example: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > end > {code} > The following build error occurs: > {code} > [Message [id=1, level=ERROR, path=pets.drl, line=5, column=0 > text=Unable to find class 'Owner']] > {code} > This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed. > PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types. > The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies: > {code} > for (TypeFieldDescr field : tdescr.getFields().values()) { > QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType()); > if (!hasCircularDependency(name, typeName, taxonomy)) { > supers.add(typeName); > } > } > {code} > However I don't think it correctly spots the dependency when the field type is an array. > This issue can be worked around by declaring an unused field of the same type as the array: > {code} > declare Owner > name : String > end > declare Pet > owners : Owner[] > _unused: Owner > end > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-805) Overload SecurityVaultFactory.get() to be able to specify the classloader

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/SECURITY-805?page=com.atlassian.jira.plug... ] Peter Skopek resolved SECURITY-805. ----------------------------------- Fix Version/s: PicketBox_4_0_21.Beta2 Resolution: Done > Overload SecurityVaultFactory.get() to be able to specify the classloader > ------------------------------------------------------------------------- > > Key: SECURITY-805 > URL: https://issues.jboss.org/browse/SECURITY-805 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: PicketBox_4_0_21.Beta2 > > Attachments: SECURITY-805-2.diff, SECURITY-805.diff > > > To work better with modular class loading in WF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-4260) Occurences of "Exception acquiring ownership of X (via SharedLocalYieldingClusterLockManager)"

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-4260?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar commented on AS7-4260: ---------------------------------- [~vishalkumar375] so upgrade to newer version that has this fixed. > Occurences of "Exception acquiring ownership of X (via SharedLocalYieldingClusterLockManager)" > ---------------------------------------------------------------------------------------------- > > Key: AS7-4260 > URL: https://issues.jboss.org/browse/AS7-4260 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.1.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Labels: JBAS018080, as713tracking > Fix For: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > > Attachments: SessionTravel.gif, view-perf18.log, view-perf19.log, view-perf20.log, view-perf21.log > > > There are often occurrences of "Exception acquiring ownership of X": > During shutdown, using dist: > {noformat} > 13:09:28,290 WARN [org.apache.catalina.session.ManagerBase] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) JBAS018080: Standard expiration of session qLQps+CQJxEi6pJTBSzis0g3 failed; switching to a brute force cleanup. Problem is JBAS018060: Exception acquiring ownership of qLQps+CQJxEi6pJTBSzis0g3 > {noformat} > During server crash, using repl: > {noformat} > 12:55:49,556 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.ejb] (Incoming-2,null) JBAS010248: New cluster view for partition ejb: 6 (org.jboss.as.clustering.impl.CoreGroupCommunicationService$GroupView@327579f6 delta: -1, merge: false) > 12:55:49,557 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,null) ISPN000094: Received new cluster view: [perf21/ejb|6] [perf21/ejb, perf20/ejb, perf18/ejb] > 12:56:31,694 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20-10.16.90.58-8009-211) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of MvwC8KGWTuKPjD1-JjLW7URZ > at org.jboss.as.web.session.ClusteredSession.acquireSessionOwnership(ClusteredSession.java:528) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.web.session.ClusteredSession.expire(ClusteredSession.java:1260) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.web.session.ClusteredSession.isValid(ClusteredSession.java:1208) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.web.session.ClusteredSession.isValid(ClusteredSession.java:598) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.web.session.DistributableSessionManager.add(DistributableSessionManager.java:917) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.web.session.DistributableSessionManager.loadSession(DistributableSessionManager.java:1407) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:686) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:85) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.apache.catalina.connector.Request.doGetSession(Request.java:2618) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:841) [jbossweb-7.0.13.Final.jar:] > at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.getSession(LazySessionBeanStore.java:72) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.<init>(LazySessionBeanStore.java:58) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:31) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:16) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.jboss.weld.servlet.WeldListener.requestInitialized(WeldListener.java:134) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:445) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > Caused by: org.jboss.as.clustering.lock.TimeoutException: JBAS010223: Cannot acquire lock //default-host//clusterbench/MvwC8KGWTuKPjD1-JjLW7URZ from cluster > at org.jboss.as.clustering.lock.SharedLocalYieldingClusterLockManager.lock(SharedLocalYieldingClusterLockManager.java:439) > at org.jboss.as.clustering.web.infinispan.DistributedCacheManager.acquireSessionOwnership(DistributedCacheManager.java:372) > at org.jboss.as.web.session.ClusteredSession.acquireSessionOwnership(ClusteredSession.java:520) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > ... 23 more > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2957) Refactor the SSL services within the security realms so that key and trust managers are injected instead of stores.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2957?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-2957. ------------------------------------ Resolution: Done > Refactor the SSL services within the security realms so that key and trust managers are injected instead of stores. > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2957 > URL: https://issues.jboss.org/browse/WFLY-2957 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.1.Final > > > To cope with things like being able to reload trust stores after files have been modified some implementation details regarding file handling have leaked slightly into the SSLIdentityService which represents the servers identity - instead the key and trust manager instances should be injected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-447) Deadlock when marshalling session using WM listeners and fireUntilHalt

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-447?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-447. -------------------------------- Resolution: Won't Fix Invoking fireX inside an event is a bad practice and should be always avoided. In particular, since at the moment some WM events callback are invoked while holding locks on the WM, trying to execute any write operation of the WM itself can inevitably lead to a deadlock. > Deadlock when marshalling session using WM listeners and fireUntilHalt > ---------------------------------------------------------------------- > > Key: DROOLS-447 > URL: https://issues.jboss.org/browse/DROOLS-447 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final, 6.1.0.Beta1 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.1.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 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 March 2014