April 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-856) Embedded GlassFish adapter may use an incorrect HTTP port when a custom domain configuration XML file is used

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-856?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-856: ------------------------------ Fix Version/s: glassfish_1.0.0.CR4 > Embedded GlassFish adapter may use an incorrect HTTP port when a custom domain configuration XML file is used > ------------------------------------------------------------------------------------------------------------- > > Key: ARQ-856 > URL: https://issues.jboss.org/browse/ARQ-856 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: GlassFish Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: glassfish_1.0.0.CR4 > > > The embedded GlassFish container uses the default HTTP bind port of 8181, even though the user-supplied domain configuration XML file may specify a different HTTP port. This results in the following exception being thrown when the Arquillian client attempts to execute a test: > {code} > ... > INFO: WELD-000900 SNAPSHOT > 9 Apr, 2012 11:06:12 AM com.sun.enterprise.web.WebApplication start > INFO: WEB0671: Loading application [test] at [/test] > 9 Apr, 2012 11:06:13 AM org.glassfish.deployment.admin.DeployCommand execute > INFO: test was successfully deployed in 18,014 milliseconds. > java.net.SocketException: Unexpected end of file from server > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:769) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:766) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379) > at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.execute(ServletMethodExecutor.java:206) > at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.access$000(ServletMethodExecutor.java:43) > at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor$1.run(ServletMethodExecutor.java:99) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > {code} > Note that the deployment is successful, but the {{HTTPContext}} returned by the embedded GlassFish adapter contains the wrong port information. In this case, the http-listener-1/http-listener-2 combo was registered in domain.xml to listen on 8080/8181. When Arquillian established a connection to port 8181, the container obviously did not respond to plain text HTTP traffic, and quite obviously the client errored out. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-837) Managed GlassFish container does not shutdown correctly in a Maven build

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-837?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-837: ------------------------------ Fix Version/s: glassfish_1.0.0.CR4 > Managed GlassFish container does not shutdown correctly in a Maven build > ------------------------------------------------------------------------ > > Key: ARQ-837 > URL: https://issues.jboss.org/browse/ARQ-837 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR3 > Environment: Maven 3.0.3, Surefire 2.7.2 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: glassfish_1.0.0.CR4 > > > When a test errors out, Arquillian does not invoke the {{DeployableContainer.stop()}} implementation of the managed GlassFish container. The GlassFish container started by Arquillian continues to run, and the subsequent test execution produces the expected error message: > {quote} > The server is already running! Managed containers does not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. > To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration > {quote} > The GlassFish container implementation should incorporate a mechanism similar to the JBoss AS 7 managed container implementation, to execute the {{asadmin stop-domain}} command in a shutdown hook. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1211) Revisit the allowConnectToRunningServer flag for managed containers

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1211?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1211: ------------------------------- Fix Version/s: glassfish_1.0.0.CR4 > Revisit the allowConnectToRunningServer flag for managed containers > ------------------------------------------------------------------- > > Key: ARQ-1211 > URL: https://issues.jboss.org/browse/ARQ-1211 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: GlassFish Containers, WebLogic Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: glassfish_1.0.0.CR4 > > > Based on the discussion [here|https://github.com/arquillian/arquillian-container-glassfish/pull/19] and on IRC, we need to review the Managed container implementations that use the {{allowConnectToRunningServer}} configuration property. > If a managed container adapter connects to an already running instance, then it should not shut down that instance. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-796) Remove the GlassFishRestDeploymentAppender from the GlassFish container adapter

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-796?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-796: ------------------------------ Fix Version/s: glassfish_1.0.0.CR4 > Remove the GlassFishRestDeploymentAppender from the GlassFish container adapter > ------------------------------------------------------------------------------- > > Key: ARQ-796 > URL: https://issues.jboss.org/browse/ARQ-796 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: GlassFish Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: glassfish_1.0.0.CR4 > > > The GlassFishRestDeploymentAppender does not appear to serve any purpose. Although it is implemented as an auxiliary archive appender, it does not appear to be used to enhance the deployment archive. It assumes the responsibility of enhancing the archive with TestEnrichers, but this is already done by the TestEnricher extensions themselves. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1382) Prepare Glassfish 1.0.0.CR4

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1382: ---------------------------------- Summary: Prepare Glassfish 1.0.0.CR4 Key: ARQ-1382 URL: https://issues.jboss.org/browse/ARQ-1382 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: glassfish_1.0.0.CR4 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: glassfish_1.0.0.CR4 -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1381) Support Jacoco 0.6.2

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1381?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1381: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done https://github.com/arquillian/arquillian-extension-jacoco/commit/b05d871d... > Support Jacoco 0.6.2 > -------------------- > > Key: ARQ-1381 > URL: https://issues.jboss.org/browse/ARQ-1381 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Robert Panzer > Fix For: jacoco_1.0.0.next > > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1381) Support Jacoco 0.6.2

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1381: ---------------------------------- Summary: Support Jacoco 0.6.2 Key: ARQ-1381 URL: https://issues.jboss.org/browse/ARQ-1381 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha5 Reporter: Aslak Knutsen Assignee: Robert Panzer Fix For: jacoco_1.0.0.next -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1381) Support Jacoco 0.6.2

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1381?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1381: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/9 > Support Jacoco 0.6.2 > -------------------- > > Key: ARQ-1381 > URL: https://issues.jboss.org/browse/ARQ-1381 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Robert Panzer > Fix For: jacoco_1.0.0.next > > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-300) Guard Ajax ends with timeout exception

by Sona Jamborova (JIRA)

Sona Jamborova created ARQGRA-300: ------------------------------------- Summary: Guard Ajax ends with timeout exception Key: ARQGRA-300 URL: https://issues.jboss.org/browse/ARQGRA-300 Project: Arquillian Graphene Issue Type: Bug Reporter: Sona Jamborova When I use guard Ajax, then test ends with exception "Timed out after 7 seconds waiting for org.jboss.arquillian.graphene.guard.RequestGuardFactory". If I do not use guards, then this operation takes max. 2 seconds. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-296) Provide a way for checking whether an element is present

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-296?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-296: ------------------------------ Original Estimate: 2 hours Remaining Estimate: 2 hours > Provide a way for checking whether an element is present > -------------------------------------------------------- > > Key: ARQGRA-296 > URL: https://issues.jboss.org/browse/ARQGRA-296 > Project: Arquillian Graphene > Issue Type: Feature Request > Affects Versions: 2.0.0.Alpha4 > Reporter: Jan Papousek > Assignee: Jan Papousek > Priority: Minor > Fix For: 2.0.0.Alpha5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2013