November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2435) Upgrade Generic JMS RA to 1.0.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2435?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2435: ----------------------------------------------- Dimitris Andreadis <dandread(a)redhat.com> made a comment on [bug 1026397|https://bugzilla.redhat.com/show_bug.cgi?id=1026397] Thanks Jeff. > Upgrade Generic JMS RA to 1.0.1.Final > ------------------------------------- > > Key: WFLY-2435 > URL: https://issues.jboss.org/browse/WFLY-2435 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2383) resource-adapter id attribute has to match ra name otherwise MDB is not deployed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2383?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2383: ----------------------------------------------- Dimitris Andreadis <dandread(a)redhat.com> made a comment on [bug 1012044|https://bugzilla.redhat.com/show_bug.cgi?id=1012044] Stefano, are you looking at it? This is the final week to get fixes for CR, which should hopefully be the last build. > resource-adapter id attribute has to match ra name otherwise MDB is not deployed > -------------------------------------------------------------------------------- > > Key: WFLY-2383 > URL: https://issues.jboss.org/browse/WFLY-2383 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > The resource-adapter id has to have the same name as the ra archive has. Otherwise the the MDB is not deployed. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-87) NDC formatting is wrong with AsyncHandler

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-87?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-87: ----------------------------------- Assignee: James Perkins (was: David Lloyd) > NDC formatting is wrong with AsyncHandler > ----------------------------------------- > > Key: LOGMGR-87 > URL: https://issues.jboss.org/browse/LOGMGR-87 > Project: JBoss Log Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Valter Karacek > Assignee: James Perkins > > NDC information is not logged when used with asynchronous log handler. > The problem appears to be with Formatters.ndcFormatStep that return the value from NDC class, instead getting from ExtLogRecord.getNdc(). > <pattern-formatter pattern="%d | %-5p | [%c] | (%t:%x) | %m%n"/> -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-87) NDC formatting is wrong with AsyncHandler

by Valter Karacek (JIRA)

Valter Karacek created LOGMGR-87: ------------------------------------ Summary: NDC formatting is wrong with AsyncHandler Key: LOGMGR-87 URL: https://issues.jboss.org/browse/LOGMGR-87 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Valter Karacek Assignee: David Lloyd NDC information is not logged when used with asynchronous log handler. The problem appears to be with Formatters.ndcFormatStep that return the value from NDC class, instead getting from ExtLogRecord.getNdc(). <pattern-formatter pattern="%d | %-5p | [%c] | (%t:%x) | %m%n"/> -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-752) Release PicketBox 4.0.20.Beta1

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/SECURITY-752?page=com.atlassian.jira.plug... ] Stefan Guilhen closed SECURITY-752. ----------------------------------- Resolution: Done PicketBox 4.0.20.Beta1 has been released and is available on Nexus. > Release PicketBox 4.0.20.Beta1 > ------------------------------ > > Key: SECURITY-752 > URL: https://issues.jboss.org/browse/SECURITY-752 > Project: PicketBox > Issue Type: Release > Security Level: Public(Everyone can see) > Components: JBossSX, Security SPI > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-475) Re-review CLI server certificate acceptance.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-475?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated WFLY-475: ---------------------------------- Parent: WFLY-1597 Issue Type: Sub-task (was: Task) > Re-review CLI server certificate acceptance. > -------------------------------------------- > > Key: WFLY-475 > URL: https://issues.jboss.org/browse/WFLY-475 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: CLI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Minor > Fix For: 8.0.0.CR1 > > > Can we remove the call loop and manage the user prompt and trust store replacement all within the trust manager? -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2207) CLI Unable to connect using https-remoting address.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2207?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2207: ----------------------------------- Parent: WFLY-1597 Issue Type: Sub-task (was: Bug) > CLI Unable to connect using https-remoting address. > --------------------------------------------------- > > Key: WFLY-2207 > URL: https://issues.jboss.org/browse/WFLY-2207 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: CLI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > > The CLI is failing to connect over https with the following: - > {code} > [disconnected /] connect https-remoting://localhost:9993 > The controller is not available at localhost:9993: java.net.ConnectException: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out > {code} -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2208) CLI over HTTP should switch to / be redirected to https automatically.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2208?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2208: ----------------------------------- Parent: WFLY-1597 Issue Type: Sub-task (was: Enhancement) > CLI over HTTP should switch to / be redirected to https automatically. > ---------------------------------------------------------------------- > > Key: WFLY-2208 > URL: https://issues.jboss.org/browse/WFLY-2208 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: CLI, Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > When using the native interface a TLS upgrade was already automatically in place once a keystore was added to the linked realm. > With the switch to http with an upgrade there is no automatic switch to https. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2154) http-interface is used instead of native-interface for native access

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2154?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2154: ----------------------------------- Parent: WFLY-1597 Issue Type: Sub-task (was: Bug) > http-interface is used instead of native-interface for native access > -------------------------------------------------------------------- > > Key: WFLY-2154 > URL: https://issues.jboss.org/browse/WFLY-2154 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Affects Versions: 8.0.0.Beta1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Steps to reproduce: > 1) create new Security Realm in standalone.xml: > <security-realm name="ManagementTestRealm"> > <authentication> > <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/> > </authentication> > </security-realm> > 2) make http-interface using this realm: > <http-interface security-realm="ManagementTestRealm" http-upgrade-enabled="true"> > <socket-binding http="management-http"/> > </http-interface> > 3) start standalone server > 4) run CLI with command ./jboss-cli.sh -c > You will ask for user and password for ManagementTestRealm but this realm is NOT used for native interface! It should still used ManagementRealm not ManagementTestRealm. If you add <local default-user="$local"/> to ManagementTestRealm Security Realm and run CLI again, it connect successfully. It looks like there is used http-interface instead of native-interface. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2211) NullPointerException in RemotingHttpUpgradeService if no http port.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2211?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2211: ----------------------------------- Parent: WFLY-1597 Issue Type: Sub-task (was: Bug) > NullPointerException in RemotingHttpUpgradeService if no http port. > ------------------------------------------------------------------- > > Key: WFLY-2211 > URL: https://issues.jboss.org/browse/WFLY-2211 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > > Starting with a HTTP port is not mandatory. > {code} > Caused by: java.lang.NullPointerException > at org.jboss.as.remoting.RemotingHttpUpgradeService.start(RemotingHttpUpgradeService.java:107) [wildfly-remoting-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > {code} -- 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

11 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2013