June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1070) Add a redirect-socket configuration to the web connector config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1070?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1070: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 900786|https://bugzilla.redhat.com/show_bug.cgi?id=900786] from VERIFIED to CLOSED > Add a redirect-socket configuration to the web connector config > --------------------------------------------------------------- > > Key: WFLY-1070 > URL: https://issues.jboss.org/browse/WFLY-1070 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Support configuring a connector on the http socket and then redirect to the https socket without having to specify the actual port number outside of the socket-binding-group. > The referenced forum thread has an example that uses "redirect-port" for this, but a new attribute would be needed, since changing the meaning of "redirect-port" would be incompatible. > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3020) LogStoreProbeHandler overwrites the LogStoreResource root model

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3020?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3020: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1092198|https://bugzilla.redhat.com/show_bug.cgi?id=1092198] from VERIFIED to CLOSED > LogStoreProbeHandler overwrites the LogStoreResource root model > --------------------------------------------------------------- > > Key: WFLY-3020 > URL: https://issues.jboss.org/browse/WFLY-3020 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1, 8.1.0.Final > > > LogStoreProbeHandler replaces the 'delegate' held by LogStoreResource. Doing this removes any data from the existing delegate's 'model' field, i.e. the "type" attribute. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3374) Upgrade HAL to 2.2.7.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3374?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3374: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1099366|https://bugzilla.redhat.com/show_bug.cgi?id=1099366] from VERIFIED to CLOSED > Upgrade HAL to 2.2.7.Final > -------------------------- > > Key: WFLY-3374 > URL: https://issues.jboss.org/browse/WFLY-3374 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 8.1.0.Final > > > Fixes HAL-396 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3198) Reenabling an application prevents it from deployement after a restart

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3198?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3198: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1074999|https://bugzilla.redhat.com/show_bug.cgi?id=1074999] from VERIFIED to CLOSED > Reenabling an application prevents it from deployement after a restart > ---------------------------------------------------------------------- > > Key: WFLY-3198 > URL: https://issues.jboss.org/browse/WFLY-3198 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ConfigAdmin > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Fix For: 8.1.0.CR1, 8.1.0.Final > > > After disabling and then re-enabling the application, I don't see Application.war.deployed; I still see Application.war.undeployed. > That explains why it doesn't get deployed after restart. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3305) :deploy after :undeploy is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3305?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3305: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1074999|https://bugzilla.redhat.com/show_bug.cgi?id=1074999] from VERIFIED to CLOSED > :deploy after :undeploy is broken > ----------------------------------- > > Key: WFLY-3305 > URL: https://issues.jboss.org/browse/WFLY-3305 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.1.0.CR1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Fix For: 9.0.0.Alpha1 > > > When redeploying via :deploy an application previously undeployed via :undeploy, the deployment is deployed, then undeployed, then deployed again. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2987) RemoteDestinationOutboundSocketBindingService is not stopped when the resource is removed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2987?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2987: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1038465|https://bugzilla.redhat.com/show_bug.cgi?id=1038465] from VERIFIED to CLOSED > RemoteDestinationOutboundSocketBindingService is not stopped when the resource is removed > ----------------------------------------------------------------------------------------- > > Key: WFLY-2987 > URL: https://issues.jboss.org/browse/WFLY-2987 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.1.0.CR1, 8.1.0.Final > > > Steps to Reproduce: > 1. add remote-destination-outbound-socket-binding > ./jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)" > result is {"outcome" => "success"} > 3. remove remote-destination-outbound-socket-binding > ./bin/jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:remove" > result is {"outcome" => "success"} > 4. add remote-destination-outbound-socket-binding > ./jboss-cli.sh -c "/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-connection-war-ejb-1:add(host=localhost, port=4447)" > result is > { > "outcome" => "failed", > "failure-description" => "JBAS014749: Operation handler failed: Service jboss.outbound-socket-binding.remote-connection-war-ejb-1 is already registered", > "rolled-back" => true > } > Expected results: > {"outcome" => "success"} > Step 3 should either report reload required or should be fixed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-797) Authentication attempts will fail if the DatabaseRolesMappingProvider's rolesQuery returns an empty set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-797?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-797: -------------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1067610|https://bugzilla.redhat.com/show_bug.cgi?id=1067610] from VERIFIED to CLOSED > Authentication attempts will fail if the DatabaseRolesMappingProvider's rolesQuery returns an empty set > ------------------------------------------------------------------------------------------------------- > > Key: SECURITY-797 > URL: https://issues.jboss.org/browse/SECURITY-797 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: PicketBox_4_0_19.Final > Reporter: Derek Horton > Assignee: Stefan Guilhen > Attachments: SECURITY-797.patch > > > If the DatabaseRolesMappingProvider's rolesQuery returns an empty set, then the authentication attempts will fail. Seems like it should not cause the authentication attempt to fail, since this is about mapping/adding roles. > It looks like the code detects that the result set is empty, but then it tries to get the role from the empty set. This causes an exception which in turn causes the authentication attempt to fail. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2753) Workaround for auditlog syslog appName not being configurable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2753?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2753: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1053355|https://bugzilla.redhat.com/show_bug.cgi?id=1053355] from VERIFIED to CLOSED > Workaround for auditlog syslog appName not being configurable > ------------------------------------------------------------- > > Key: WFLY-2753 > URL: https://issues.jboss.org/browse/WFLY-2753 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kyle Lape > Assignee: Kyle Lape > Fix For: 8.0.0.Final > > > Use {{-Dorg.jboss.TEMP.audit.log.appName=customApp}} where the value is the {{app-name}} as mentioned in section 6.2.5 of RFC-5424 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3130) Add a custom RuntimeException to add-user utility.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3130?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3130: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1062595|https://bugzilla.redhat.com/show_bug.cgi?id=1062595] from VERIFIED to CLOSED > Add a custom RuntimeException to add-user utility. > -------------------------------------------------- > > Key: WFLY-3130 > URL: https://issues.jboss.org/browse/WFLY-3130 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.1.0.CR1, 8.1.0.Final > > > The add-user utility uses a RuntimeException to indicate failure in non-interactive mode, this does not look good so should switch it to a custom exception of our own. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2920) StackOverflowError when org.jboss.as.jacorb.rmi.InterfaceAnalysis is analyzing javax.ejb.EJBObject

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2920?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2920: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1064644|https://bugzilla.redhat.com/show_bug.cgi?id=1064644] from VERIFIED to CLOSED > StackOverflowError when org.jboss.as.jacorb.rmi.InterfaceAnalysis is analyzing javax.ejb.EJBObject > -------------------------------------------------------------------------------------------------- > > Key: WFLY-2920 > URL: https://issues.jboss.org/browse/WFLY-2920 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: IIOP > Affects Versions: 8.0.0.Final > Reporter: Osamu Nagano > Assignee: Stuart Douglas > Fix For: 8.1.0.CR1, 8.1.0.Final > > Attachments: td.dump > > > Depending on when a thread context switch happens, an IIOP enabled EJB fails to be deployed by throwing {{java.lang.StackOverflowError}}. Here is the stack trace from the attached thread dump. > {code} > "MSC service thread 1-7" prio=10 tid=0x00007f52e8001800 nid=0x4d12 at breakpoint[0x00007f534093f000] > java.lang.Thread.State: RUNNABLE > at org.jboss.as.jacorb.rmi.WorkCacheManager.getAnalysis(WorkCacheManager.java:105) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.getInterfaceAnalysis(InterfaceAnalysis.java:53) > at org.jboss.as.jacorb.rmi.Util.getTypeIDLName(Util.java:104) > at org.jboss.as.jacorb.rmi.ParameterAnalysis.<init>(ParameterAnalysis.java:50) > at org.jboss.as.jacorb.rmi.OperationAnalysis.<init>(OperationAnalysis.java:91) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.analyzeOperations(InterfaceAnalysis.java:116) > at org.jboss.as.jacorb.rmi.ContainerAnalysis.doAnalyze(ContainerAnalysis.java:186) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.doAnalyze(InterfaceAnalysis.java:62) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.as.jacorb.rmi.WorkCacheManager.doTheWork(WorkCacheManager.java:177) > at org.jboss.as.jacorb.rmi.WorkCacheManager.getAnalysis(WorkCacheManager.java:105) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.getInterfaceAnalysis(InterfaceAnalysis.java:53) > at org.jboss.as.jacorb.rmi.Util.getTypeIDLName(Util.java:104) > at org.jboss.as.jacorb.rmi.ParameterAnalysis.<init>(ParameterAnalysis.java:50) > at org.jboss.as.jacorb.rmi.OperationAnalysis.<init>(OperationAnalysis.java:91) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.analyzeOperations(InterfaceAnalysis.java:116) > at org.jboss.as.jacorb.rmi.ContainerAnalysis.doAnalyze(ContainerAnalysis.java:186) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.doAnalyze(InterfaceAnalysis.java:62) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > ... > at org.jboss.as.jacorb.rmi.WorkCacheManager.doTheWork(WorkCacheManager.java:177) > at org.jboss.as.jacorb.rmi.WorkCacheManager.getAnalysis(WorkCacheManager.java:105) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.getInterfaceAnalysis(InterfaceAnalysis.java:53) > at org.jboss.as.jacorb.rmi.Util.getTypeIDLName(Util.java:104) > at org.jboss.as.jacorb.rmi.ParameterAnalysis.<init>(ParameterAnalysis.java:50) > Locked ownable synchronizers: > - <0x00000000f9698790> (a java.util.concurrent.ThreadPoolExecutor$Worker) > {code} > The last part including {{Util.getTypeIDLName}} has been repeated as many as possible and the bottom of the stack has been lost. The same stack has been appeared in a different MSC service thread which is also executing an IIOP enabled EJB deployment. > The customer identified an improper synchronization in {{org.jboss.as.jacorb.rmi.WorkCacheManager#getAnalysis()}}. It is reproducible by manually controlling a thread context switch using a debugger. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

12 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 June 2014