March 2012 - jboss-jira - Jboss List Archives

[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

12 years, 3 months

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

12 years, 3 months

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

12 years, 3 months

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

12 years, 3 months

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

12 years, 3 months

3
5
0 / 0

[JBoss JIRA] (JBJCA-755) Exception during recovery

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-755: ------------------------------------- Summary: Exception during recovery Key: JBJCA-755 URL: https://issues.jboss.org/browse/JBJCA-755 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.1.0.Alpha6, 1.0.8.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.9.Final, 1.1.0.Alpha7 An exception is thrown (DEBUG) during recovery, since an incorrect method signature is used -- 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

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-4041) JDBDDriverAdd should not require driver-name param

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4041: ------------------------------------- Summary: JDBDDriverAdd should not require driver-name param Key: AS7-4041 URL: https://issues.jboss.org/browse/AS7-4041 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Brian Stansberry Assignee: Stefano Maestri Fix For: 7.1.2.Final The name of the a driver should be the value of the last PathElement in the driver resource's PathAddress. User's shouldn't have to specify a "driver-name" parameter. To maintain API compatibility, the attribute should be retained. But if users provide the parameter to "add" and it doesn't match the resource address, an OFE should be thrown. If they don't provide a driver-name param, the value from the resource address should be stored. -- 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

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3238) Convert CMP subsystem to i18n logging and exceptions messages as per ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Convert CMP subsystem to i18n logging and exceptions messages as per ANDIAMO-2 ------------------------------------------------------------------------------ Key: AS7-3238 URL: https://issues.jboss.org/browse/AS7-3238 Project: Application Server 7 Issue Type: Task Components: EJB Reporter: Brian Stansberry Assignee: John Bailey Fix For: 7.1.0.Final The CmpLogger and CmpMessages classes are currently empty shells. The INFO and above logging and any exception messages in the subsystem needs to be converted to use these classes. See EJB subsystem for an example. -- 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

12 years, 3 months

5
8
0 / 0

[JBoss JIRA] (AS7-4029) Clone/pull on windows fails

by Nicklas Karlsson (JIRA)

Nicklas Karlsson created AS7-4029: ------------------------------------- Summary: Clone/pull on windows fails Key: AS7-4029 URL: https://issues.jboss.org/browse/AS7-4029 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.1.1.Final Environment: Windows 7 Reporter: Nicklas Karlsson Assignee: Paul Gier cloning (or pulling updates from) the jboss-as repository results in fatal: cannot create directory at 'testsuite/integration/smoke/src/test/java/org /jboss/as/test/smoke/jms/aux': Invalid argument possible from a path that is too long? -- 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

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JASSIST-96) Publish javassist to Maven central

by Pete Muir (JIRA)

Publish javassist to Maven central ---------------------------------- Key: JASSIST-96 URL: https://jira.jboss.org/jira/browse/JASSIST-96 Project: Javassist Issue Type: Task Reporter: Pete Muir It would be nice if Javassist were published to Maven central regularly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2012