June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3441) Upgrade to JBoss Negotiation 2.3.3.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3441?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3441: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1104269|https://bugzilla.redhat.com/show_bug.cgi?id=1104269] from MODIFIED to ON_QA > Upgrade to JBoss Negotiation 2.3.3.Final > ---------------------------------------- > > Key: WFLY-3441 > URL: https://issues.jboss.org/browse/WFLY-3441 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3437) Upgrade HAL to 2.2.8.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3437?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3437: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1104216|https://bugzilla.redhat.com/show_bug.cgi?id=1104216] from MODIFIED to ON_QA > Upgrade HAL to 2.2.8.Final > -------------------------- > > Key: WFLY-3437 > URL: https://issues.jboss.org/browse/WFLY-3437 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWEB-299) Add support for OpenSSL syntax when defining ciphers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWEB-299?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWEB-299: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1078204|https://bugzilla.redhat.com/show_bug.cgi?id=1078204] from MODIFIED to ON_QA > Add support for OpenSSL syntax when defining ciphers > ---------------------------------------------------- > > Key: JBWEB-299 > URL: https://issues.jboss.org/browse/JBWEB-299 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: JBossWeb-7.2.1.GA > Reporter: Emmanuel Hugonnet > Assignee: Remy Maucherat > Attachments: bz-1078204.patch > > > SSL connector fails to start if cipher-suite="ALL" even though in the xsd schema it is defined as default value -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3366) Include version number in resteasy-spring jar

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3366?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3366: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1090053|https://bugzilla.redhat.com/show_bug.cgi?id=1090053] from ASSIGNED to MODIFIED > Include version number in resteasy-spring jar > --------------------------------------------- > > Key: WFLY-3366 > URL: https://issues.jboss.org/browse/WFLY-3366 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3211) java:app resources can not be shared between ejb and appclient modules

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3211?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3211: -------------------------------------- Actually ignore my last comment, just noticed that you added it in your branch. > java:app resources can not be shared between ejb and appclient modules > ---------------------------------------------------------------------- > > Key: WFLY-3211 > URL: https://issues.jboss.org/browse/WFLY-3211 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Eduardo Martins > > use case: > 1 ear composed of: > 1 appclient module that defines 2 JMS queues (one in java:app, the other in java:global) > 1 ejb modules with 2 MDBs (one listening to the java:app queue and the other to the java:global queue) > When the ear is deployed: > 1. the ejb module is deployed, the MDBs are created and wait for the creations of their respective queues (defined in the appclient module) > 2. the appclient module is deployed, its 2 queues are deployed > 3. the appclient main is run > When the appclient uses the java:global queue, it looks it up, sends the message and the corresponding MDB receives it fine. > When the appclient uses the java:app queue, it looks it up, sends the message but the corresponding MDB never receives it > => the MDB was never deployed because it did not see the java:app queue deployed from the appclient module. > Note that if I move the destination definitions to the ejb module, the MDBs are correctly activated but the appclient module is no longer deployed with errors: > {noformat} > [APPCLIENT-out] {"JBAS014771: Services with missing/unavailable dependencies" => [ > [APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInGlobal is missing [jboss.naming.context.java.global.jms.queu > e.queue1]", > [APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInApp is missing [jboss.naming.context.java.app.simple-jms-app > client-test.jms.queue.queue2]" > [APPCLIENT-out] ]} > {noformat} > Steps to reproduce: > 1. fetch git branch https://github.com/jmesnil/wildfly/tree/jms_appclient > 2. build WildFly > 3. run ./integration-tests.sh -Dts.basic -Dtest=org.jboss.as.test.integration.ee.appclient.jms.basic.SimpleJMSApplicationClientTestCase -DnoWebProfile -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3211) java:app resources can not be shared between ejb and appclient modules

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3211?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3211: -------------------------------------- I think the real issue here is that appclient.xml appears to be missing the messaging subsystem. > java:app resources can not be shared between ejb and appclient modules > ---------------------------------------------------------------------- > > Key: WFLY-3211 > URL: https://issues.jboss.org/browse/WFLY-3211 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Eduardo Martins > > use case: > 1 ear composed of: > 1 appclient module that defines 2 JMS queues (one in java:app, the other in java:global) > 1 ejb modules with 2 MDBs (one listening to the java:app queue and the other to the java:global queue) > When the ear is deployed: > 1. the ejb module is deployed, the MDBs are created and wait for the creations of their respective queues (defined in the appclient module) > 2. the appclient module is deployed, its 2 queues are deployed > 3. the appclient main is run > When the appclient uses the java:global queue, it looks it up, sends the message and the corresponding MDB receives it fine. > When the appclient uses the java:app queue, it looks it up, sends the message but the corresponding MDB never receives it > => the MDB was never deployed because it did not see the java:app queue deployed from the appclient module. > Note that if I move the destination definitions to the ejb module, the MDBs are correctly activated but the appclient module is no longer deployed with errors: > {noformat} > [APPCLIENT-out] {"JBAS014771: Services with missing/unavailable dependencies" => [ > [APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInGlobal is missing [jboss.naming.context.java.global.jms.queu > e.queue1]", > [APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInApp is missing [jboss.naming.context.java.app.simple-jms-app > client-test.jms.queue.queue2]" > [APPCLIENT-out] ]} > {noformat} > Steps to reproduce: > 1. fetch git branch https://github.com/jmesnil/wildfly/tree/jms_appclient > 2. build WildFly > 3. run ./integration-tests.sh -Dts.basic -Dtest=org.jboss.as.test.integration.ee.appclient.jms.basic.SimpleJMSApplicationClientTestCase -DnoWebProfile -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-820) Fix the fallback to form SSO handling in NegotiationAuthenticator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-820?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-820: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1099554, https://bugzilla.redhat.com/show_bug.cgi?id=1105330 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1099554) > Fix the fallback to form SSO handling in NegotiationAuthenticator > ----------------------------------------------------------------- > > Key: SECURITY-820 > URL: https://issues.jboss.org/browse/SECURITY-820 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Affects Versions: Negotiation_2_3_0_CR1 > Reporter: Derek Horton > Assignee: Derek Horton > Fix For: Negotiation_2_3_2_Final > > > Fix the fallback to form SSO handling in NegotiationAuthenticator -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3211) java:app resources can not be shared between ejb and appclient modules

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3211?page=com.atlassian.jira.plugin.... ] Eduardo Martins commented on WFLY-3211: --------------------------------------- Yes, and probably the best solution would be HornetQ SPI for WildFly to plug the needed logic to deal with JNDI properly. > java:app resources can not be shared between ejb and appclient modules > ---------------------------------------------------------------------- > > Key: WFLY-3211 > URL: https://issues.jboss.org/browse/WFLY-3211 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Eduardo Martins > > use case: > 1 ear composed of: > 1 appclient module that defines 2 JMS queues (one in java:app, the other in java:global) > 1 ejb modules with 2 MDBs (one listening to the java:app queue and the other to the java:global queue) > When the ear is deployed: > 1. the ejb module is deployed, the MDBs are created and wait for the creations of their respective queues (defined in the appclient module) > 2. the appclient module is deployed, its 2 queues are deployed > 3. the appclient main is run > When the appclient uses the java:global queue, it looks it up, sends the message and the corresponding MDB receives it fine. > When the appclient uses the java:app queue, it looks it up, sends the message but the corresponding MDB never receives it > => the MDB was never deployed because it did not see the java:app queue deployed from the appclient module. > Note that if I move the destination definitions to the ejb module, the MDBs are correctly activated but the appclient module is no longer deployed with errors: > {noformat} > [APPCLIENT-out] {"JBAS014771: Services with missing/unavailable dependencies" => [ > [APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInGlobal is missing [jboss.naming.context.java.global.jms.queu > e.queue1]", > [APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInApp is missing [jboss.naming.context.java.app.simple-jms-app > client-test.jms.queue.queue2]" > [APPCLIENT-out] ]} > {noformat} > Steps to reproduce: > 1. fetch git branch https://github.com/jmesnil/wildfly/tree/jms_appclient > 2. build WildFly > 3. run ./integration-tests.sh -Dts.basic -Dtest=org.jboss.as.test.integration.ee.appclient.jms.basic.SimpleJMSApplicationClientTestCase -DnoWebProfile -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3211) java:app resources can not be shared between ejb and appclient modules

by Wolfgang Knauf (JIRA)

[ https://issues.jboss.org/browse/WFLY-3211?page=com.atlassian.jira.plugin.... ] Wolfgang Knauf commented on WFLY-3211: -------------------------------------- Just want to ping that issue - Eduardo's comment about the "thread local state" sounds like it is a issue in HornetQ? > java:app resources can not be shared between ejb and appclient modules > ---------------------------------------------------------------------- > > Key: WFLY-3211 > URL: https://issues.jboss.org/browse/WFLY-3211 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Eduardo Martins > > use case: > 1 ear composed of: > 1 appclient module that defines 2 JMS queues (one in java:app, the other in java:global) > 1 ejb modules with 2 MDBs (one listening to the java:app queue and the other to the java:global queue) > When the ear is deployed: > 1. the ejb module is deployed, the MDBs are created and wait for the creations of their respective queues (defined in the appclient module) > 2. the appclient module is deployed, its 2 queues are deployed > 3. the appclient main is run > When the appclient uses the java:global queue, it looks it up, sends the message and the corresponding MDB receives it fine. > When the appclient uses the java:app queue, it looks it up, sends the message but the corresponding MDB never receives it > => the MDB was never deployed because it did not see the java:app queue deployed from the appclient module. > Note that if I move the destination definitions to the ejb module, the MDBs are correctly activated but the appclient module is no longer deployed with errors: > {noformat} > [APPCLIENT-out] {"JBAS014771: Services with missing/unavailable dependencies" => [ > [APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInGlobal is missing [jboss.naming.context.java.global.jms.queu > e.queue1]", > [APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInApp is missing [jboss.naming.context.java.app.simple-jms-app > client-test.jms.queue.queue2]" > [APPCLIENT-out] ]} > {noformat} > Steps to reproduce: > 1. fetch git branch https://github.com/jmesnil/wildfly/tree/jms_appclient > 2. build WildFly > 3. run ./integration-tests.sh -Dts.basic -Dtest=org.jboss.as.test.integration.ee.appclient.jms.basic.SimpleJMSApplicationClientTestCase -DnoWebProfile -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3457) Nginx + Wildfly 8.1 + Varnish

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3457?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-3457: ---------------------------------------- Start here http://wildfly.org/ lots of WildFly specific resources and follow the header to 'Get Help' > Nginx + Wildfly 8.1 + Varnish > ----------------------------- > > Key: WFLY-3457 > URL: https://issues.jboss.org/browse/WFLY-3457 > Project: WildFly > Issue Type: Support Request > Security Level: Public(Everyone can see) > Reporter: Thiago Hernandes > Assignee: Jason Greene > Labels: nginx, perfomrance, varnish > > Performance it´s more important in development web applications. > I´ve tested Python + Nginx + Tornado Web Server. It´s ok and worked. > is there any sugestion to configurate Nginx + Wildfly + Varnish??? > It could be in documentation of Wildfly with some examples or tutorials. > Is there somebody can be indicate or show any example? > I think, it´s one the best way to power of deploy applications Java with tecnologies i sad before. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

12 years, 1 month

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