January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5484) Calling HttpServletRequest.logout() with single sign-on enabled only works every second time

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-5484?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-5484: -------------------------------------- I think Undertow 1.3.16.Final should fix this, but I have not been able to get a reproducer to work. > Calling HttpServletRequest.logout() with single sign-on enabled only works every second time > -------------------------------------------------------------------------------------------- > > Key: WFLY-5484 > URL: https://issues.jboss.org/browse/WFLY-5484 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Richard Janík > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 10.0.0.CR5 > > Attachments: reproducer-jbeap-1282.zip > > > See "Steps to Reproduce". Logging out from an application only works every second time, e.g. HttpRequestServlet.logout() has to be called twice in order to have any effect > This doesn't occur without <single-sign-on/> enabled - logout() has the expected effect. The issue is security related, thus I'm adding our security team members as watchers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-935) Wrong AdvancedADLdap mapping in ModulesMap

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-935?page=com.atlassian.jira.plug... ] Darran Lofthouse reopened SECURITY-935: --------------------------------------- > Wrong AdvancedADLdap mapping in ModulesMap > ------------------------------------------ > > Key: SECURITY-935 > URL: https://issues.jboss.org/browse/SECURITY-935 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > There is wrong AdvancedADLdap mapping in ModulesMap. > In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap". > https://github.com/jbossas/jboss-eap7/blob/7.x/security/subsystem/src/mai... > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > We suggest some like this for backward compatibility: > Add one extra mapping to ModulesMap with right mapping and leave there old mapping too. Some old app can use this old wrong mapping. > {code} > put("AdvancedAdLdap", AdvancedADLoginModule.class.getName()); > put("AdvancedADLdap", AdvancedADLoginModule.class.getName()); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-935) Wrong AdvancedADLdap mapping in ModulesMap

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-935?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on SECURITY-935: ------------------------------------------- Will fix. > Wrong AdvancedADLdap mapping in ModulesMap > ------------------------------------------ > > Key: SECURITY-935 > URL: https://issues.jboss.org/browse/SECURITY-935 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > There is wrong AdvancedADLdap mapping in ModulesMap. > In ModulesMap is "AdvancedAdLdap", but in documentation is "AdvancedADLdap". > https://github.com/jbossas/jboss-eap7/blob/7.x/security/subsystem/src/mai... > https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > We suggest some like this for backward compatibility: > Add one extra mapping to ModulesMap with right mapping and leave there old mapping too. Some old app can use this old wrong mapping. > {code} > put("AdvancedAdLdap", AdvancedADLoginModule.class.getName()); > put("AdvancedADLdap", AdvancedADLoginModule.class.getName()); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1334) Allow disabling audit log rotation

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1334?page=com.atlassian.jira.plugi... ] Tomas Hofman commented on WFCORE-1334: -------------------------------------- [~brian.stansberry] only now I noticed that audit log is deprecated in Wildfly. There is no ticket mentioned in the commit, does it have some replacement? Does it make sense to make improvements on it if it's going to be removed? > Allow disabling audit log rotation > ---------------------------------- > > Key: WFCORE-1334 > URL: https://issues.jboss.org/browse/WFCORE-1334 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Affects Versions: 2.0.7.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > https://bugzilla.redhat.com/show_bug.cgi?id=1301554 > org.jboss.as.controller.audit.FileAuditLogHandler always rotates audit-log.log at startup/reload. An option to disable log rotation is necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6077) Add auto-create|delete-jms-queues to address-settings resource

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6077?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reopened WFLY-6077: ------------------------------- > Add auto-create|delete-jms-queues to address-settings resource > -------------------------------------------------------------- > > Key: WFLY-6077 > URL: https://issues.jboss.org/browse/WFLY-6077 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.CR5 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6048) jboss-webservices.xml descriptor doesn't override @WebContext annotation

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6048?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov reassigned WFLY-6048: ---------------------------------------- Assignee: Dmitrii Tikhomirov (was: Alessio Soldano) > jboss-webservices.xml descriptor doesn't override @WebContext annotation > ------------------------------------------------------------------------ > > Key: WFLY-6048 > URL: https://issues.jboss.org/browse/WFLY-6048 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.2.Final > Environment: ubuntu 14.04, Java 7 > Reporter: Wojciech Oczkowski > Assignee: Dmitrii Tikhomirov > Priority: Minor > Attachments: ws-xml-override.zip > > > It seems that annotation WebConfig takes precedence over jboss-webservices.xml descriptor values. It doesn't seem right as you cannot override annotation values for test purposes for example. > Problematic code seems to be: > org.jboss.as.webservices.metadata.AbstractMetaDataBuilderEJB:159 > (should prefer JBossPortComponentMetaData over EJBEndpoint) > and > org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect:177 > (should prefer EJBSecurityMetaData over annotation value) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5081) WebSphere MQ 8 RA - [TCK] - Defining connection factory by @JMSConnectionFactoryDefinition annotation or in deployment descriptor fails

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5081?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-5081: ----------------------------------- I opened a PR for this and was able to modify the helloworld-mdb quickstart to send and receive messages using WSMQ 8 RA. The branch for this is at https://github.com/jmesnil/quickstart/tree/WFLY-5081_JMSConnectionFactory... (and the commit is https://github.com/jmesnil/quickstart/commit/601a1da2704d1e8543618a72df00...) Relevant bits are: {noformat} @JMSConnectionFactoryDefinition( name = "java:/jms/myCF1", interfaceName = "javax.jms.ConnectionFactory", resourceAdapter = "wmq.jmsra", properties = { "channel=CH", "hostName=10.16.88.195", "transportType=CLIENT", "queueManager=QM" } ) @JMSDestinationDefinitions( value = { @JMSDestinationDefinition( name = "java:/queue/HELLOWORLDMDBQueue", interfaceName = "javax.jms.Queue", className = "com.ibm.mq.connector.outbound.MQQueueProxy", destinationName = "HelloWorldMDBQueue", resourceAdapter = "wmq.jmsra", properties = { "baseQueueName=Q2", "baseQueueManagerName=QM" } ), @JMSDestinationDefinition( name = "java:/topic/HELLOWORLDMDBTopic", interfaceName = "javax.jms.Topic", className = "com.ibm.mq.connector.outbound.MQTopicProxy", destinationName = "HelloWorldMDBTopic", resourceAdapter = "wmq.jmsra", properties = { "baseTopicName=T1", "brokerPubQueueManager=QM" } ) }) {noformat} And this resource-adapters configuration in standalone-full.xml: {noformat} <subsystem xmlns="urn:jboss:domain:resource-adapters:4.0"> <resource-adapters> <resource-adapter id="wmq.jmsra"> <archive> wmq.jmsra.rar </archive> <transaction-support>XATransaction</transaction-support> </resource-adapter> </resource-adapters> </subsystem> {noformat} > WebSphere MQ 8 RA - [TCK] - Defining connection factory by @JMSConnectionFactoryDefinition annotation or in deployment descriptor fails > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5081 > URL: https://issues.jboss.org/browse/WFLY-5081 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Beta1 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Critical > > If WebSphere MQ 8 resource adapter is configured as default resource adapter for MDB in ejb subsystem and MDB is trying to deploy its connection factory like: > {code} > @JMSConnectionFactoryDefinition( > description="Define TopicConnectionFactory AppClientMyTestTopicConnectionFactory", > interfaceName="javax.jms.TopicConnectionFactory", > name="java:module/AppClientMyTestTopicConnectionFactory", > user = "j2ee", > password = "j2ee", > ) > {code} > then deployment fails with: > {code} > 11:18:37,471 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0001: Content added at location /home/mnovak/mnovak_home/tmp/tck7/work/jboss-eap-7.0/standalone/data/content/1d/4fbecb4dd1e3a9c03b791cd64c21cd6b7f49de/content > 11:18:37,475 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "mdb-1.0-SNAPSHOT.jar" (runtime-name: "mdb-1.0-SNAPSHOT.jar") > 11:18:37,499 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean 'SampleMdb' with 'wmq.jmsra' resource adapter > 11:18:37,501 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "mdb-1.0-SNAPSHOT.jar")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.app.\"mdb-1.0-SNAPSHOT\".AppClientMyTestQueueConnectionFactory is missing [jboss.connection-factory.reference-factory.jboss.naming.context.java.app.\"mdb-1.0-SNAPSHOT\".AppClientMyTestQueueConnectionFactory]"]} > 11:18:37,616 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "mdb-1.0-SNAPSHOT.jar" (runtime-name : "mdb-1.0-SNAPSHOT.jar") > 11:18:37,616 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0185: Newly corrected services: > service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".component.SampleMdb.CREATE (new available) > service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".component.SampleMdb.JndiBindingsService (new available) > service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".component.SampleMdb.START (new available) > service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".component.SampleMdb.VIEW.SampleMdb.MESSAGE_ENDPOINT (new available) > service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".component.SampleMdb.ejb.non-functional-timerservice (new available) > service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".jndiDependencyService (new available) > service jboss.deployment.unit."mdb-1.0-SNAPSHOT.jar".moduleDeploymentRuntimeInformation (new available) > service jboss.naming.context.java.app."mdb-1.0-SNAPSHOT".AppClientMyTestQueueConnectionFactory (new available) > service jboss.naming.context.java.app."mdb-1.0-SNAPSHOT".env (new available) > service jboss.naming.context.java.comp."mdb-1.0-SNAPSHOT"."mdb-1.0-SNAPSHOT".SampleMdb (new available) > service jboss.naming.context.java.comp."mdb-1.0-SNAPSHOT"."mdb-1.0-SNAPSHOT".SampleMdb.TransactionSynchronizationRegistry (new available) > service jboss.naming.context.java.comp."mdb-1.0-SNAPSHOT"."mdb-1.0-SNAPSHOT".SampleMdb.UserTransaction (new available) > service jboss.naming.context.java.module."mdb-1.0-SNAPSHOT"."mdb-1.0-SNAPSHOT".env (new available) > {code} > Customer impact: > Any deployment which needs to define its connection factory in deployment will fail. Customer cannot use @JMSConnectionFactoryDefinition to deploy connection factory. > Debugging showed that deployment of connection factory defined in @JMSConnectionFactoryDefinition is using messaging activemq extension integration. WebSphereMQ's managed connection factory cannot be added as pooled-connection-factory to messaging-activemq subsystem. > We need to provide a way 3rd party JMS managed connection factory will be created and registered to JNDI. > Failing TCK tests failing because of this issue: > {code} > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client.j... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jms/ee20/resourcedefs/descriptor/Client.ja... > {cdde} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1044) KieBase 'includes' does not handle the inclusion of KieBases that use the same package-names correctly.

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1044?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1044: ------------------------------------- The problem is a bit more complex because not only that the 2 KieBases have to declare the same package names, but also the 2 drl files have exactly the same name. I'm still investigating on this issue, but one possible workaround is to at least give 2 different name to the 2 drl files. > KieBase 'includes' does not handle the inclusion of KieBases that use the same package-names correctly. > ------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1044 > URL: https://issues.jboss.org/browse/DROOLS-1044 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Beta1 > Environment: Mac OS X 10.11.3, Oracle Hotspot 1.8.0_45 > Reporter: Duncan Doyle > Assignee: Mario Fusco > > KieBase 'includes' does not handle the inclusion of KieBases that use the same package-names correctly. > I define 2 KJARs, each with a kmodule.xml that defines a KieBase. KJAR1 has a dependency on KJAR2 in its pom.xml. > The KieBase defined in KJAR1 includes the KieBase defined in KJAR2. > If the KieBases get their Drools Resources (e.g. .drl) from different packages (e.g. 'rules' and 'rules2', everything works fine, e.g.: > KJAR1 kmodule.xml: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule"> > <kbase name="kbase1" equalsBehavior="equality" default="true" packages="rules" includes="kbase2"> > <ksession name="ksession1" default="true" type="stateful"/> > </kbase> > </kmodule> > {code} > KAJR2 kmodule.xml: > {code:xml} > <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule"> > <kbase name="kbase2" equalsBehavior="equality" default="false" packages="rules2"> > <ksession name="ksession2" default="false" type="stateful"/> > </kbase> > </kmodule> > {code} > However, when both KieBases use the same "packages" name (e.g. 'rules'), only one of the resources gets included in the final KieBase. > KJAR1 kmodule.xml: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule"> > <kbase name="kbase1" equalsBehavior="equality" default="true" packages="rules" includes="kbase2"> > <ksession name="ksession1" default="true" type="stateful"/> > </kbase> > </kmodule> > {code} > KAJR2 kmodule.xml: > {code:xml} > <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule"> > <kbase name="kbase2" equalsBehavior="equality" default="false" packages="rules"> > <ksession name="ksession2" default="false" type="stateful"/> > </kbase> > </kmodule> > {code} > Unit tests with reproducer can be found here: https://github.com/DuncanDoyle/drools-kiebase-include-issue -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1334) Allow disabling audit log rotation

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1334?page=com.atlassian.jira.plugi... ] Tomas Hofman updated WFCORE-1334: --------------------------------- Issue Type: Enhancement (was: Bug) > Allow disabling audit log rotation > ---------------------------------- > > Key: WFCORE-1334 > URL: https://issues.jboss.org/browse/WFCORE-1334 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Affects Versions: 2.0.7.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > https://bugzilla.redhat.com/show_bug.cgi?id=1301554 > org.jboss.as.controller.audit.FileAuditLogHandler always rotates audit-log.log at startup/reload. An option to disable log rotation is necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1334) Allow disabling audit log rotation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1334?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-1334: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1301554 Bugzilla Update: Perform > Allow disabling audit log rotation > ---------------------------------- > > Key: WFCORE-1334 > URL: https://issues.jboss.org/browse/WFCORE-1334 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Affects Versions: 2.0.7.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > https://bugzilla.redhat.com/show_bug.cgi?id=1301554 > org.jboss.as.controller.audit.FileAuditLogHandler always rotates audit-log.log at startup/reload. An option to disable log rotation is necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 January 2016