October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1740) ManagedSocketBinding class Impossible cast from java.net.InetAddress to java.net.InetSocketAddress

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1740?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1740: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017747|https://bugzilla.redhat.com/show_bug.cgi?id=1017747] from MODIFIED to ON_QA > ManagedSocketBinding class Impossible cast from java.net.InetAddress to java.net.InetSocketAddress > -------------------------------------------------------------------------------------------------- > > Key: WFLY-1740 > URL: https://issues.jboss.org/browse/WFLY-1740 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0.0.Alpha4 > Reporter: Cheng Fang > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.CR1 > > > Reported by FindBugs: > Impossible cast from java.net.InetAddress to java.net.InetSocketAddress > Class: > ManagedSocketBinding (org.jboss.as.network) line 55 > Method: > getBindAddress (org.jboss.as.network.ManagedSocketBinding.getBindAddress()) > Priority: > High Confidence Correctness > > Problem classification: > Correctness (Bad casts of object references) > BC_IMPOSSIBLE_CAST (Impossible cast) > Notes: > Actual type java.net.InetAddress > Expected java.net.InetSocketAddress > Return value of Class.cast(Object) > FindBadCast2 (BC|NP) -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1499) Clustering tests intermittently fail mainly because they do not clean their deployments properly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1499?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1499: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 998371|https://bugzilla.redhat.com/show_bug.cgi?id=998371] from MODIFIED to ON_QA > Clustering tests intermittently fail mainly because they do not clean their deployments properly > ------------------------------------------------------------------------------------------------ > > Key: WFLY-1499 > URL: https://issues.jboss.org/browse/WFLY-1499 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha4 > > > Almost all clustering tests from the testsuite deploys what they need to perform the test, but almost none of those tests do undeploy of their deployments. Then, if the tests are run in an unexpected order (different JVM) or if some of them fail their deployments keeps at servers and often cause a failure of subsequent tests. > For example {{RemoteStatelessFailoverTestCase(ejb3)}} stops {{CONTAINER-1}} in the middle of a testLoadBalance method and never tries to undeploy DEPLOYMENT_1 from it. So if it hits any failure in the subsequent {{this.establishView(listener, NODES[1]);}} the {{CONTAINER-1}} will never be started up again by RemoteStatelessFailoverTestCase and hence will never be cleaned up by Arquillian which normally undeploys all deployments from the running custom containers on after-class event. And then StatefulFailoverTestCase fails with > {noformat} > org.jboss.as.test.clustering.ViewChangeListenerServlet threw exception: > java.lang.InterruptedException: Cluster 'ejb' failed to establish view [node-1/ejb] within 15000 ms. Current view is: [node-0/ejb, node-1/ejb] > {noformat} > Another frequent issue with clustering tests is that they blindly deploy the same deployments manytimes which leads to duplicate deploy failures. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1458) Allow specifying timeout for org.jboss.as.arquillian.container.ManagementClient.isServerInRunningState()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1458?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1458: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1021487|https://bugzilla.redhat.com/show_bug.cgi?id=1021487] from MODIFIED to ON_QA > Allow specifying timeout for org.jboss.as.arquillian.container.ManagementClient.isServerInRunningState() > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-1458 > URL: https://issues.jboss.org/browse/WFLY-1458 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Richard Achmatowicz > Assignee: Ladislav Thon > Fix For: 8.0.0.CR1 > > Attachments: thread.dump.txt > > > When deploying a container, Arquillian will use a management client to connect to the deployed container to see if it is in a running state. If the management address and management port are incorrect, the connection to the container hangs indefinitely. > Please allow configuration of a timeout so that if the connection paramaters are not correct, at least the container deployment will fail with a meaningful error. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2278) Deployer can't modify data source when datasources set as application resources

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2278?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2278: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017786|https://bugzilla.redhat.com/show_bug.cgi?id=1017786] from MODIFIED to ON_QA > Deployer can't modify data source when datasources set as application resources > ------------------------------------------------------------------------------- > > Key: WFLY-2278 > URL: https://issues.jboss.org/browse/WFLY-2278 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Ladislav Thon > Assignee: Brian Stansberry > Labels: rbac-filed-by-qa > Fix For: 8.0.0.CR1 > > > When data sources are made application resources, deployer should be able to modify them. This doesn't work, as opposed to e.g. mail sessions. For example: > {code} > /core-service=management/access=authorization/constraint=application-classification/type=datasources/classification=data-source:write-attribute(name=configured-application, value=true) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:write-attribute(name=jndi-name, value="java:jboss/datasources/ExampleDS_XXX"){roles=deployer} > { > "outcome" => "failed", > "failure-description" => "JBAS013456: Unauthorized to execute operation 'write-attribute' for resource '[ > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"ExampleDS\") > ]' -- \"JBAS013475: Permission denied\"", > "rolled-back" => true > } > [standalone@localhost:9990 /] /core-service=management/access=authorization/constraint=application-classification/type=mail/classification=mail-session:write-attribute(name=configured-application, value=true) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=mail/mail-session=java\:jboss\/mail\/Default:write-attribute(name=jndi-name, value="java:jboss/mail/Default_XXX"){roles=deployer} > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > I have a test case for this as a last commit in my branch https://github.com/Ladicek/wildfly/commits/rbac (that is the commit called _RBAC test case for application types_). > Brian, in case you are not the right assignee, please reassign. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-758) AdvancedLdapLoginModule doesn't isn't mapping nested roles

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-758?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-758: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017974|https://bugzilla.redhat.com/show_bug.cgi?id=1017974] from MODIFIED to ON_QA > AdvancedLdapLoginModule doesn't isn't mapping nested roles > ---------------------------------------------------------- > > Key: SECURITY-758 > URL: https://issues.jboss.org/browse/SECURITY-758 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_2_5 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_6 > > > The recursive role searching is currently broken, believed to be caused by the introduction of quotes for a previous role searching fix. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1094) Use own JSSE Provider for http Connector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1094?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1094: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 956391|https://bugzilla.redhat.com/show_bug.cgi?id=956391] from MODIFIED to ON_QA > Use own JSSE Provider for http Connector > ---------------------------------------- > > Key: WFLY-1094 > URL: https://issues.jboss.org/browse/WFLY-1094 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (JBoss Web) > Affects Versions: 8.0.0.Alpha1 > Reporter: Hauke Mehrtens > Assignee: Tomaz Cerar > Labels: https, jsse, ssl > Fix For: 8.0.0.Alpha1 > > Attachments: ssl-protocol.patch > > > We are using our own JSSE Provider implementation for TLS to add support for HTTPS with preshared key to one http connector, while the others still use the default JSSE provider. > In JBoss 5 we added sslProtocol="RFC4279", while RFC4279 is the name of our provider, to one Connector entry in the file server/default/deploy/jbossweb.sar/server.xml. This option is not available in JBoss 7.1 any more and we could not find a way to make one connector use our provider while the others are using the default one. > To fix this issue for use we used the attached patch. We would like to get this patch into the next version of JBoss, so we do not have to modify the source code by our self any more. This patch was tested with JBoss 7.1.2, but it still applies against the master branch. If we should do any changed to the patch or if you want to get it in an other form please inform us. > With this patch we are able to specify our JSSE provider like this: > {code:xml} > <connector name="httpspsk" protocol="HTTP/1.1" scheme="https" socket-binding="httpspsk" secure="true"> > <ssl name="ssl" key-alias="intended purpose ssl test from bremen online services" password="123456" certificate-key-file="${jboss.server.config.dir}/governikus_ssl.jks" protocol="ALL" keystore-type="JKS" ssl_protocol="RFC4279"/> > </connector> > {code} > This is related to Red Hat Customer Portal support case 00721624 "Additional JSSE Provider on socket bindings and connectors" -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-74) REMJMX-65 Overzealous disabling local authentication

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-74?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-74: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1021630|https://bugzilla.redhat.com/show_bug.cgi?id=1021630] from MODIFIED to ON_QA > REMJMX-65 Overzealous disabling local authentication > ---------------------------------------------------- > > Key: REMJMX-74 > URL: https://issues.jboss.org/browse/REMJMX-74 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.2.Final, 2.0.0.CR4 > > > REMJMX-65 is overzealous at disabling local authentication, if a username and credential is supplied in the environment then it does make sense to disable local authentication - however the availability of a callback handler is not a sufficient flag to also disable it. > In the case of the callback handler the user may still only want to be prompted if the other mechanisms fail. > This issue will remove the disabling of local authentication based on the presence of a callback handler and will instead add a configuration option that can be set on the environment. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-88) Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-88?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-88: --------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 952746|https://bugzilla.redhat.com/show_bug.cgi?id=952746] from MODIFIED to ON_QA > Recovery not fully triggered when distributed transaction falls down at prepare phase of 2PC > -------------------------------------------------------------------------------------------- > > Key: WFLY-88 > URL: https://issues.jboss.org/browse/WFLY-88 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, Remoting > Reporter: Ivo Studensky > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > Attachments: logs_prepareHaltClient.tgz > > > It looks like recovery process is not fully triggered on a distributed transaction when the transaction falls down at prepare phase of 2PC. In the new crash recovery tests over propagated transactions only one of two servers recovers from the crash, but the other keeps an unfinished tx in its tx log. > It corresponds to prepareHaltClient and prepareHaltServer test methods of org.jboss.as.test.jbossts.crashrec.txpropagation.TxPropagationCrashRecoveryTestCase, see JBQA-2604 for general description of the new tests. The prepareHaltClient test crashes the server which initiated the transaction, while as the prepareHaltServer test crashes the second server. > The tests are written against EAP6.x branch, so for reproducing this it is needed a built server from the 7.1 branch of AS7. > Steps to reproduce. > 1. git clone -b as7 git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-transactions.git > 2. cd eap-tests-transactions > 3. git checkout tx_propag_crashrec_tests > 4a. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltClient -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > or > 4b. mvn clean verify -Dtest=TxPropagationCrashRecoveryTestCase#prepareHaltServer -Djboss.dist=<path to jboss-as-7.1.3.Final-SNAPSHOT> > The logs of prepareHaltClient run attached to this jira. -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-761) Release JBoss Negotiation 2.2.6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-761?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-761: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017974|https://bugzilla.redhat.com/show_bug.cgi?id=1017974] from MODIFIED to ON_QA > Release JBoss Negotiation 2.2.6 > ------------------------------- > > Key: SECURITY-761 > URL: https://issues.jboss.org/browse/SECURITY-761 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_6 > > -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-760) Make the JBoss Negotiation dependency on JBoss Web - Provided

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-760?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-760: -------------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1022679|https://bugzilla.redhat.com/show_bug.cgi?id=1022679] from MODIFIED to ON_QA > Make the JBoss Negotiation dependency on JBoss Web - Provided > ------------------------------------------------------------- > > Key: SECURITY-760 > URL: https://issues.jboss.org/browse/SECURITY-760 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_6 > > -- 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

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013