April 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1738) Liberty profile leave port 9080 hanging around after shutdown

by Alasdair Nottingham (JIRA)

[ https://issues.jboss.org/browse/ARQ-1738?page=com.atlassian.jira.plugin.s... ] Alasdair Nottingham commented on ARQ-1738: ------------------------------------------ I think what you need to do is update your httpEndpoint configuration thus: <httpEndpoint id="defaultHttpEndpoint"> <tcpOptions soReuseAddr="true"/> </httpEndpoint> This should have been fixed in the the latest beta http://wasdev.net/downloads/wasearlyaccess > Liberty profile leave port 9080 hanging around after shutdown > ------------------------------------------------------------- > > Key: ARQ-1738 > URL: https://issues.jboss.org/browse/ARQ-1738 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Environment: Fedora 20, Open JDK 7/8, Oracle JDK 7, WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639 > Reporter: Aslak Knutsen > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1738) Liberty profile leave port 9080 hanging around after shutdown

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1738?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-1738: ------------------------------ Assignee: (was: Gerhard Poul) > Liberty profile leave port 9080 hanging around after shutdown > ------------------------------------------------------------- > > Key: ARQ-1738 > URL: https://issues.jboss.org/browse/ARQ-1738 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Environment: Fedora 20, Open JDK 7/8, Oracle JDK 7, WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639 > Reporter: Aslak Knutsen > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1738) Liberty profile leave port 9080 hanging around after shutdown

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1738?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-1738: ------------------------------ Environment: Fedora 20, Open JDK 7/8, Oracle JDK 7, WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639 (was: Fedora 20, Open JDS 7/8, Oracle JDK 7, WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639) > Liberty profile leave port 9080 hanging around after shutdown > ------------------------------------------------------------- > > Key: ARQ-1738 > URL: https://issues.jboss.org/browse/ARQ-1738 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Environment: Fedora 20, Open JDK 7/8, Oracle JDK 7, WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1738) Liberty profile leave port 9080 hanging around after shutdown

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1738?page=com.atlassian.jira.plugin.s... ] Gerhard Poul commented on ARQ-1738: ----------------------------------- The TIME_WAITs in the netstat are not the core issue; there is something else. I can see those as well when I test with the IBM JDK, but the port is not blocked. When using the OpenJDK contained in the Fedora 19 package java-1.7.0-openjdk-devel-1.7.0.60-2.4.5.0.fc19.x86_64 I can reproduce this issue. > Liberty profile leave port 9080 hanging around after shutdown > ------------------------------------------------------------- > > Key: ARQ-1738 > URL: https://issues.jboss.org/browse/ARQ-1738 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Environment: Fedora 20, Open JDS 7/8, Oracle JDK 7, WebSphere Application Server 8.5.5.1/wlp-1.0.4.cl50120131011-1639 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1736) Make defaultServer the default serverName in WLP Managed

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1736?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-1736: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/17 > Make defaultServer the default serverName in WLP Managed > -------------------------------------------------------- > > Key: ARQ-1736 > URL: https://issues.jboss.org/browse/ARQ-1736 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > If serverName is missing from arquillian.xml, the container die with a NullPointerException in validate. Should default to 'defaultServer' for a better startup experience. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1624) Create a DeployableContainer integration for remote WAS V8.5

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1624?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-1624: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/17 > Create a DeployableContainer integration for remote WAS V8.5 > ------------------------------------------------------------ > > Key: ARQ-1624 > URL: https://issues.jboss.org/browse/ARQ-1624 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Reporter: Philippe Mazenauer > Assignee: Gerhard Poul > > Adding Websphere Application Server V8.5 to possible WAS Connectors by simply copying the WAS 8 Connector and changing the following section in the POM: > <dependency> > <groupId>com.ibm.websphere</groupId> > <artifactId>ws-admin-client</artifactId> > <version>8.5.0</version> > <scope>system</scope> <systemPath>${was_home}/runtimes/com.ibm.ws.admin.client_8.5.0.jar</systemPath> > </dependency> > And Probably making a proper release out of it, so you don't have to compile it local. > Thanks > Philippe Mazenauer -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1737) Missing Container Configuration cause NullPointerException in validate

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1737?page=com.atlassian.jira.plugin.s... ] Gerhard Poul commented on ARQ-1737: ----------------------------------- sharedLib is not in alpha2; let's address this directly in the pull request. I've addressed everything else in the pull request for this issue. > Missing Container Configuration cause NullPointerException in validate > ---------------------------------------------------------------------- > > Key: ARQ-1737 > URL: https://issues.jboss.org/browse/ARQ-1737 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > serverName, wlpHomeDir, sharedLib > httpPort should default to the default port used by wlp -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1737) Missing Container Configuration cause NullPointerException in validate

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1737?page=com.atlassian.jira.plugin.s... ] Gerhard Poul updated ARQ-1737: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/arquillian/arquillian-container-was/pull/17 > Missing Container Configuration cause NullPointerException in validate > ---------------------------------------------------------------------- > > Key: ARQ-1737 > URL: https://issues.jboss.org/browse/ARQ-1737 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > serverName, wlpHomeDir, sharedLib > httpPort should default to the default port used by wlp -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1737) Missing Container Configuration cause NullPointerException in validate

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1737?page=com.atlassian.jira.plugin.s... ] Gerhard Poul commented on ARQ-1737: ----------------------------------- serverName will be addressed by ARQ-1736 > Missing Container Configuration cause NullPointerException in validate > ---------------------------------------------------------------------- > > Key: ARQ-1737 > URL: https://issues.jboss.org/browse/ARQ-1737 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > serverName, wlpHomeDir, sharedLib > httpPort should default to the default port used by wlp -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1737) Missing Container Configuration cause NullPointerException in validate

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-1737?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1737 started by Gerhard Poul. > Missing Container Configuration cause NullPointerException in validate > ---------------------------------------------------------------------- > > Key: ARQ-1737 > URL: https://issues.jboss.org/browse/ARQ-1737 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebSphere Containers > Affects Versions: was_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Assignee: Gerhard Poul > > serverName, wlpHomeDir, sharedLib > httpPort should default to the default port used by wlp -- 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

10 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2014