March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3998) Update Zanata plugin to 1.4.5.2

by Sean Flanigan (JIRA)

Sean Flanigan created AS7-3998: ---------------------------------- Summary: Update Zanata plugin to 1.4.5.2 Key: AS7-3998 URL: https://issues.jboss.org/browse/AS7-3998 Project: Application Server 7 Issue Type: Quality Risk Reporter: Sean Flanigan zanata-maven-plugin 1.4.5.1 has a bug which causes any unfinished "fuzzy" translations to be included in .properties files when pulling from the Zanata server. 1.4.5.2 has the fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-3933) modcluster subsystem doesn't properly encode expression values

by Heiko Braun (JIRA)

Heiko Braun created AS7-3933: -------------------------------- Summary: modcluster subsystem doesn't properly encode expression values Key: AS7-3933 URL: https://issues.jboss.org/browse/AS7-3933 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Web Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.2.Final See the "certificate-key-file" attribute: {noformat} [standalone@localhost:9999 /] /subsystem=modcluster/mod-cluster-config=configuration/ssl=configuration:read-resource { "outcome" => "success", "result" => { "certificate-key-file" => "${user.home}/.keystore", "key-alias" => "test", "password" => "changeit", "protocol" => "TLS" } } {noformat} it would need to be encoded as a DMR expression. The illegal character prevents any success reads of this resource -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-3791) Cannot add/remove stack protocols

by Heiko Braun (JIRA)

Heiko Braun created AS7-3791: -------------------------------- Summary: Cannot add/remove stack protocols Key: AS7-3791 URL: https://issues.jboss.org/browse/AS7-3791 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Richard Achmatowicz Fix For: 7.1.1.Final [standalone@localhost:9999 /] /subsystem=jgroups/stack=tcp/protocol=test:add { "outcome" => "failed", "failure-description" => "JBAS014739: No handler for add at address [ (\"subsystem\" => \"jgroups\"), (\"stack\" => \"tcp\"), (\"protocol\" => \"test\") ]", "rolled-back" => true } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
16
0 / 0

[JBoss JIRA] (AS7-3946) Upgrade to JBoss Metadata 7.0.1.Final

by Richard Opalka (JIRA)

Richard Opalka created AS7-3946: ----------------------------------- Summary: Upgrade to JBoss Metadata 7.0.1.Final Key: AS7-3946 URL: https://issues.jboss.org/browse/AS7-3946 Project: Application Server 7 Issue Type: Component Upgrade Reporter: Richard Opalka Assignee: Stuart Douglas Fix For: 7.1.1.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-3786) Some non-Arquillian TestCases are run against hard-coded 127.0.0.1

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-3786?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-3786: ------------------------------ Fix Version/s: 7.1.1.Final > Some non-Arquillian TestCases are run against hard-coded 127.0.0.1 > ------------------------------------------------------------------ > > Key: AS7-3786 > URL: https://issues.jboss.org/browse/AS7-3786 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.Final > Reporter: Pavel Janousek > Assignee: Pavel Janousek > Priority: Critical > Fix For: 7.1.1.Final > > > Some TestCases are hard bound to *127.0.0.1* IP address. I think, it is useless - especially testing in IPv6 environment is impossible in this case for a such TestCase(-s). > These classes aren't in integration testsuite part, it is in other places. > Some of them are (maybe I've overlooked some others): > - org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase > - org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase > - org.jboss.as.controller.test.RemoteProxyControllerProtocolTestCase > - org.jboss.as.controller.ModelControllerClientTestCase > - org.jboss.as.jmx.JMXSubsystemTestCase > - org.jboss.as.jmx.ModelControllerMBeanTestCase > Otherwise these tests are run *before* IP address transformation (usually used node0 variable and tranforms AS7 config file standalone-*.xml), so maybe there isn't present now any mechanism how to get/propagate proper (and wanted) IP address. > Also note - some of them are hardcoded to IP name alias *localhost* - see JBPAPP-8132 for localhost vs. localhost6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3786) Some non-Arquillian TestCases are run against hard-coded 127.0.0.1

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-3786?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-3786: ------------------------------ Summary: Some non-Arquillian TestCases are run against hard-coded 127.0.0.1 (was: Some TestCases are run against hard-coded 127.0.0.1) > Some non-Arquillian TestCases are run against hard-coded 127.0.0.1 > ------------------------------------------------------------------ > > Key: AS7-3786 > URL: https://issues.jboss.org/browse/AS7-3786 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > Priority: Critical > > Some TestCases are hard bound to *127.0.0.1* IP address. I think, it is useless - especially testing in IPv6 environment is impossible in this case for a such TestCase(-s). > These classes aren't in integration testsuite part, it is in other places. > Some of them are (maybe I've overlooked some others): > - org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase > - org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase > - org.jboss.as.controller.test.RemoteProxyControllerProtocolTestCase > - org.jboss.as.controller.ModelControllerClientTestCase > - org.jboss.as.jmx.JMXSubsystemTestCase > - org.jboss.as.jmx.ModelControllerMBeanTestCase > Otherwise these tests are run *before* IP address transformation (usually used node0 variable and tranforms AS7 config file standalone-*.xml), so maybe there isn't present now any mechanism how to get/propagate proper (and wanted) IP address. > Also note - some of them are hardcoded to IP name alias *localhost* - see JBPAPP-8132 for localhost vs. localhost6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3786) Some non-Arquillian TestCases are run against hard-coded 127.0.0.1

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-3786?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned AS7-3786: --------------------------------- Assignee: Pavel Janousek (was: Ondrej Zizka) Pavel, since we have AS7-3696 for Arquillian-based tests, could you please verify if there are still non-Arq tests with harcoded values? > Some non-Arquillian TestCases are run against hard-coded 127.0.0.1 > ------------------------------------------------------------------ > > Key: AS7-3786 > URL: https://issues.jboss.org/browse/AS7-3786 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.Final > Reporter: Pavel Janousek > Assignee: Pavel Janousek > Priority: Critical > > Some TestCases are hard bound to *127.0.0.1* IP address. I think, it is useless - especially testing in IPv6 environment is impossible in this case for a such TestCase(-s). > These classes aren't in integration testsuite part, it is in other places. > Some of them are (maybe I've overlooked some others): > - org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase > - org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase > - org.jboss.as.controller.test.RemoteProxyControllerProtocolTestCase > - org.jboss.as.controller.ModelControllerClientTestCase > - org.jboss.as.jmx.JMXSubsystemTestCase > - org.jboss.as.jmx.ModelControllerMBeanTestCase > Otherwise these tests are run *before* IP address transformation (usually used node0 variable and tranforms AS7 config file standalone-*.xml), so maybe there isn't present now any mechanism how to get/propagate proper (and wanted) IP address. > Also note - some of them are hardcoded to IP name alias *localhost* - see JBPAPP-8132 for localhost vs. localhost6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4016) EJB invocations from a remote server instance does not work properly

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-4016: ------------------------------------- Summary: EJB invocations from a remote server instance does not work properly Key: AS7-4016 URL: https://issues.jboss.org/browse/AS7-4016 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Ondřej Chaloupka Assignee: jaikiran pai It seems that the EJB invocations from a remote server instance does not work. In multinode part of testsuite does not work binding of local initial context on client server. It seems that it's returned remote context (of the second server) everytime. As well in case that lookup is made from injected InitialContext. {code} @Resource InitialContext ctx; {code} The mentioned test could be found here: https://github.com/ochaloup/jboss-as/commit/a5a5405894080dc01925a7d47640a... The second problem occurs on deploying app on "standalone" server (out of the testsuite). It seems that server does not see any other server and it binds local context instead of remote one. E.g. When I ran only one server and deployed application with jboss-ejb-client.xml pointing to outbound-connection it does not throw an exception that the outbound-connection can't be caught but it throw exception: {code} javax.ejb.EJBException: java.lang.RuntimeException: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:myejb,distinctname:] combination {code} which means that it found an context but didn't find a receiver. In fact it was found context of the running (local) server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] (AS7-3786) Some TestCases are run against hard-coded 127.0.0.1

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-3786?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3786: ----------------------------------- A lot of progress has been made, although we still have few "localhost" occurences. Today I've sent an email with this list challenging people to fix. > Some TestCases are run against hard-coded 127.0.0.1 > --------------------------------------------------- > > Key: AS7-3786 > URL: https://issues.jboss.org/browse/AS7-3786 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.Final > Reporter: Pavel Janousek > Assignee: Ondrej Zizka > Priority: Critical > > Some TestCases are hard bound to *127.0.0.1* IP address. I think, it is useless - especially testing in IPv6 environment is impossible in this case for a such TestCase(-s). > These classes aren't in integration testsuite part, it is in other places. > Some of them are (maybe I've overlooked some others): > - org.jboss.as.protocol.mgmt.RemoteChannelManagementTestCase > - org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase > - org.jboss.as.controller.test.RemoteProxyControllerProtocolTestCase > - org.jboss.as.controller.ModelControllerClientTestCase > - org.jboss.as.jmx.JMXSubsystemTestCase > - org.jboss.as.jmx.ModelControllerMBeanTestCase > Otherwise these tests are run *before* IP address transformation (usually used node0 variable and tranforms AS7 config file standalone-*.xml), so maybe there isn't present now any mechanism how to get/propagate proper (and wanted) IP address. > Also note - some of them are hardcoded to IP name alias *localhost* - see JBPAPP-8132 for localhost vs. localhost6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4025) resource-description for subsystem=jgroups not complete

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4025: ------------------------------- Summary: resource-description for subsystem=jgroups not complete Key: AS7-4025 URL: https://issues.jboss.org/browse/AS7-4025 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry read-resource shows a 'default-stack' that is not described [standalone@localhost:9999 subsystem=jgroups] :read-resource { "outcome" => "success", "result" => { "default-stack" => "udp", "stack" => {"udp" => undefined} } } [standalone@localhost:9999 subsystem=jgroups] :read-resource read-resource read-resource-description [standalone@localhost:9999 subsystem=jgroups] :read-resource-description { "outcome" => "success", "result" => { "description" => "The configuration of the jgroups subsystem.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:jgroups:1.1", "children" => {"stack" => { "description" => "The configuration of a jgroups protocol stack.", "min-occurs" => 1, "max-occurs" => 2147483647, "model-description" => {} }} } } One level deeper: [standalone@localhost:9999 stack=udp] :read-resource { "outcome" => "success", "result" => { "protocols" => [ "PING", "MERGE2", "FD_SOCK", "FD", "VERIFY_SUSPECT", "BARRIER", "pbcast.NAKACK", "UNICAST2", "pbcast.STABLE", "pbcast.GMS", "UFC", "MFC", "FRAG2", "pbcast.STATE_TRANSFER" ], "protocol" => { "PING" => undefined, "FD_SOCK" => undefined, "FD" => undefined, "VERIFY_SUSPECT" => undefined, "BARRIER" => undefined, "FRAG2" => undefined, "MERGE2" => undefined, "pbcast.GMS" => undefined, "pbcast.STATE_TRANSFER" => undefined, "UNICAST2" => undefined, "UFC" => undefined, "MFC" => undefined, "pbcast.NAKACK" => undefined, "pbcast.STABLE" => undefined }, "transport" => {"TRANSPORT" => undefined} } } [standalone@localhost:9999 stack=udp] :read-resource read-resource read-resource-description [standalone@localhost:9999 stack=udp] :read-resource-description { "outcome" => "success", "result" => { "description" => "The configuration of a jgroups protocol stack.", "children" => { "transport" => { "description" => "The configuration of a transport for a protocol stack.", "min-occurs" => 0, "max-occurs" => 1, "allowed" => ["TRANSPORT"], "model-description" => undefined }, "protocol" => { "description" => "The configuration of a protocol within a protocol stack.", "min-occurs" => 0, "max-occurs" => 2147483647, "model-description" => undefined } } } } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
5
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 March 2012