October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2222) SecurityExceptions when starting server with signed jars in an exploded app deployment

by Matt Fluet (JIRA)

Matt Fluet created WFLY-2222: -------------------------------- Summary: SecurityExceptions when starting server with signed jars in an exploded app deployment Key: WFLY-2222 URL: https://issues.jboss.org/browse/WFLY-2222 Project: WildFly Issue Type: Bug Components: Class Loading Reporter: Matt Fluet Assignee: David Lloyd Priority: Critical This issue is directly related to https://issues.jboss.org/browse/AS7-2724, where signed jars are sometimes throwing a security exception when the server starts up and then classes cannot be loaded out of certain packages (appears to be some sort of a concurrency issue). The fix for that issue was applied to JarFileResourceLoader here: https://github.com/jboss-modules/jboss-modules/commit/8cf33f5c02c0c4bf6f9... However, our application is exploded, so the VFSResourceLoader needs a similar fix. I will attach a git patch file with the change we're proposing. To test the theory, we applied the patch to one server and left another as is as a control...we then left a process running that continually restarted the server for 3 days. The control server hit the SecurityException problem 5 times, and the patched server didn't show it at all. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2216) include-all role mappings don't work in domain

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2216?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2216: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 1015493|https://bugzilla.redhat.com/show_bug.cgi?id=1015493] from ASSIGNED to POST > include-all role mappings don't work in domain > ---------------------------------------------- > > Key: WFLY-2216 > URL: https://issues.jboss.org/browse/WFLY-2216 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Ladislav Thon > Assignee: Darran Lofthouse > Labels: rbac-filed-by-qa > Fix For: 8.0.0.Beta1 > > > If I understand correctly, roles that have {{include-all=true}} in their role mappings should be added to all authenticated users. In my tests, though, this only works in standalone mode. > In domain mode, if I set a role mapping to {{include-all}}, this setting is not reflected (at least not immediately; maybe it would work after restart, but that's wrong anyway). It doesn't matter which role is set to be {{include-all}} -- in my tests, I use both standard roles and scoped roles and it consistently doesn't work. There's probably some wrong caching going on. > The failing test case is in my pull request https://github.com/wildfly/wildfly/pull/5166 (it's the _RBAC tests for include-all role mappings in domain_ commit). If it's more convenient, the pull request is the same as my _rbac_ branch (https://github.com/Ladicek/wildfly/commits/rbac). > Darran, I'm not sure if you are the right assignee -- please reassign if needed. Thanks. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-76) JBoss Logging Processor should support WSDLException

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-76?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGTOOL-76: -------------------------------------- Looking at the code this won't quite work. Mainly because of the way the exception constructor signature is defined. The code generator assumes the first string type in the constructor is the message. In the case of a {{WSDLException}} the first constructor parameter seems to be the code. I'm not sure whether it's worth exploring the ability to express more meta data about a constructor or now. For now the only solution would be for the message to be returned as a string type then create the exception manually. {code:java} /** * couldNotFindServiceInTheWSDL method definition. * @param portName the portName * @param definitionDocumentBaseURI definitionDocumentBaseURI * @return the error message */ @Message(id = 35436, value = "Could not find service %s in the WSDL %s") String couldNotFindServiceInTheWSDL(String portName, String definitionDocumentBaseURI); {code} Then create the exception something like: {code:java} throw new WSDLException(faultCode, MESSAGES.couldNotFindServiceInTheWSDL(portName, definitionDocumentBaseURI); {code} > JBoss Logging Processor should support WSDLException > ---------------------------------------------------- > > Key: LOGTOOL-76 > URL: https://issues.jboss.org/browse/LOGTOOL-76 > Project: Log Tool > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tom Cunningham > Assignee: David Lloyd > > This is a jboss-logging-processor issue - javax.wsdl.WSDLException has constructors : > public WSDLException(java.lang.String faultCode, > java.lang.String msg, > java.lang.Throwable t) > public WSDLException(java.lang.String faultCode, > java.lang.String msg) > When I try to localize with this : > /** > * couldNotFindServiceInTheWSDL method definition. > * @param portName the portName > * @param definitionDocumentBaseURI definitionDocumentBaseURI > * @return WSDLException > */ > @Message(id = 35436, value = "Could not find service %s in the WSDL %s") > WSDLException couldNotFindServiceInTheWSDL(String portName, String definitionDocumentBaseURI); > I see compilation errors because jboss-logging-processor doesn't know how to support the WSDLException constructors. We should support them. > Failure: > [ERROR] /Users/tcunning/src/switchyard/cunningt/components/soap/src/main/java/org/switchyard/component/soap/SOAPMessages.java:[189,18] MessageMethod does not have an usable constructor for the return type javax.wsdl.WSDLException. > [ERROR] /Users/tcunning/src/switchyard/cunningt/components/soap/src/main/java/org/switchyard/component/soap/SOAPMessages.java:[197,18] MessageMethod does not have an usable constructor for the return type javax.wsdl.WSDLException. > [ERROR] /Users/tcunning/src/switchyard/cunningt/components/soap/src/main/java/org/switchyard/component/soap/SOAPMessages.java:[206,18] MessageMethod does not have an usable constructor for the return type javax.wsdl.WSDLException. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-260) Drools not writing calendars when marshalling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-260: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> made a comment on [bug 1007385|https://bugzilla.redhat.com/show_bug.cgi?id=1007385] I couldn't reproduce this issue on the master. Very likely it was related by this issue: https://issues.jboss.org/browse/DROOLS-260 that has been fixed with this commit: https://github.com/droolsjbpm/drools/commit/39276fea9209353bf3704663da0b0... > Drools not writing calendars when marshalling > --------------------------------------------- > > Key: DROOLS-260 > URL: https://issues.jboss.org/browse/DROOLS-260 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Demian Calcaprina > Assignee: Mario Fusco > Fix For: 6.0.0.CR5 > > > When serializing Rule class, https://github.com/droolsjbpm/drools/blob/5.5.x/drools-core/src/main/java..., the write and read external methods does not write and read calendars properties. > This causes that, if there is a rule which has a calendar in guvnor, for example, > rule "CalendarTest" > calendars "my cal" > no-loop true > dialect "mvel" > when > then > System.out.println("CALENDAR IS FIRIUNG!!!"); > end > when rule is retrieved, calendars are not took into account. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-260) Drools not writing calendars when marshalling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-260: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1007385|https://bugzilla.redhat.com/show_bug.cgi?id=1007385] from ASSIGNED to MODIFIED > Drools not writing calendars when marshalling > --------------------------------------------- > > Key: DROOLS-260 > URL: https://issues.jboss.org/browse/DROOLS-260 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Demian Calcaprina > Assignee: Mario Fusco > Fix For: 6.0.0.CR5 > > > When serializing Rule class, https://github.com/droolsjbpm/drools/blob/5.5.x/drools-core/src/main/java..., the write and read external methods does not write and read calendars properties. > This causes that, if there is a rule which has a calendar in guvnor, for example, > rule "CalendarTest" > calendars "my cal" > no-loop true > dialect "mvel" > when > then > System.out.println("CALENDAR IS FIRIUNG!!!"); > end > when rule is retrieved, calendars are not took into account. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-260) Drools not writing calendars when marshalling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-260: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1007385 > Drools not writing calendars when marshalling > --------------------------------------------- > > Key: DROOLS-260 > URL: https://issues.jboss.org/browse/DROOLS-260 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Demian Calcaprina > Assignee: Mario Fusco > Fix For: 6.0.0.CR5 > > > When serializing Rule class, https://github.com/droolsjbpm/drools/blob/5.5.x/drools-core/src/main/java..., the write and read external methods does not write and read calendars properties. > This causes that, if there is a rule which has a calendar in guvnor, for example, > rule "CalendarTest" > calendars "my cal" > no-loop true > dialect "mvel" > when > then > System.out.println("CALENDAR IS FIRIUNG!!!"); > end > when rule is retrieved, calendars are not took into account. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-260) Drools not writing calendars when marshalling

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-260?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-260. -------------------------------- Fix Version/s: 6.0.0.CR5 Resolution: Done > Drools not writing calendars when marshalling > --------------------------------------------- > > Key: DROOLS-260 > URL: https://issues.jboss.org/browse/DROOLS-260 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Demian Calcaprina > Assignee: Mario Fusco > Fix For: 6.0.0.CR5 > > > When serializing Rule class, https://github.com/droolsjbpm/drools/blob/5.5.x/drools-core/src/main/java..., the write and read external methods does not write and read calendars properties. > This causes that, if there is a rule which has a calendar in guvnor, for example, > rule "CalendarTest" > calendars "my cal" > no-loop true > dialect "mvel" > when > then > System.out.println("CALENDAR IS FIRIUNG!!!"); > end > when rule is retrieved, calendars are not took into account. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1871) CLI module command doesn't allow cross platform resource paths

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/WFLY-1871?page=com.atlassian.jira.plugin.... ] Stan Silvert updated WFLY-1871: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/4915, https://github.com/wildfly/wildfly/pull/5219 (was: https://github.com/wildfly/wildfly/pull/4915) > CLI module command doesn't allow cross platform resource paths > -------------------------------------------------------------- > > Key: WFLY-1871 > URL: https://issues.jboss.org/browse/WFLY-1871 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 8.0.0.Beta1 > > > The CLI module command has an argument called "resources". This argument allows you to specify one or more resources separated by the platform-specific path separator. The problem with this is that you can not create a platform-independent script that uses this resources argument. > I have not found a universal path separator character that would work. However, since the creator of the script knows the characters used in his path, we can allow him to specify his own separator. > As an enhancement, I propose to add an argument called "resourceDelimiter". If present, the ASModuleHandler class will use the user-defined delimiter instead of the platform-specific path separator character. > Example usage: > {noformat} > module add --name=org.foo --resources=firstResource.jar:secondResource.jar --resourceDelimiter=: --module-xml=foo-module.xml > {noformat} > The above command would work on Unix, Windows, or any other platform. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-286) Sliding Windows do not discard events correctly when used with entry-points

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-286: ------------------------------------- Summary: Sliding Windows do not discard events correctly when used with entry-points Key: DROOLS-286 URL: https://issues.jboss.org/browse/DROOLS-286 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical Fix For: 5.5.1.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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-286) Sliding Windows do not discard events correctly when used with entry-points

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-286?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-286: --------------------------------------- Already fixed in 5.6 > Sliding Windows do not discard events correctly when used with entry-points > --------------------------------------------------------------------------- > > Key: DROOLS-286 > URL: https://issues.jboss.org/browse/DROOLS-286 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.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, 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 2013