[JBoss JIRA] (ARQ-2125) Adding wait option for Glassfish container
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-2125:
-----------------------------------
Summary: Adding wait option for Glassfish container
Key: ARQ-2125
URL: https://issues.jboss.org/browse/ARQ-2125
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.Final
Reporter: Bartosz Majsak
It seems arquillian conatiner is looking for glassfish even before glassfish has started properly.
Adding some wait time to resolve the issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 10 months
[JBoss JIRA] (ARQ-2124) Proper way of passing arguments to glassfish cli
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-2124:
-----------------------------------
Summary: Proper way of passing arguments to glassfish cli
Key: ARQ-2124
URL: https://issues.jboss.org/browse/ARQ-2124
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.Final
Reporter: Bartosz Majsak
Replace the empty list implementation with a full list implementation to remove
the unsupported operation exceptions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 10 months
[JBoss JIRA] (ARQ-2123) Support for starting derby database automatically
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-2123?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak updated ARQ-2123:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Support for starting derby database automatically
> -------------------------------------------------
>
> Key: ARQ-2123
> URL: https://issues.jboss.org/browse/ARQ-2123
> Project: Arquillian
> Issue Type: Enhancement
> Components: GlassFish Containers
> Reporter: Bartosz Majsak
> Fix For: glassfish_1.0.0.Final
>
>
> t would be very handy to let the derby database start automatically (on demand) in the managed environment.
> I was forced to bump the glassfish version used for testing from 4.0-b72 to 4.1.1. This was due to a bug that refused me to start the derby database failing with this error:
> {{AccessControlException: access denied ("java.net.SocketPermission" "localhost:1527" "listen,resolve")}}
> The configuration option in the arquillian.xml is startDerby = true/false
> Generally glassfish 3 has exactly the same feature. The error is the bug that I've mentioned in the initial comment. You can see more output be dafining outputToConcoleto true. Here are more details about the bug in glassfish:
> https://java.net/jira/browse/GLASSFISH-21004
> and the root cause form the bundled derby
> https://issues.apache.org/jira/browse/DERBY-6438
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 10 months
[JBoss JIRA] (ARQ-2123) Support for starting derby database automatically
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-2123?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak updated ARQ-2123:
--------------------------------
Description:
t would be very handy to let the derby database start automatically (on demand) in the managed environment.
I was forced to bump the glassfish version used for testing from 4.0-b72 to 4.1.1. This was due to a bug that refused me to start the derby database failing with this error:
{{AccessControlException: access denied ("java.net.SocketPermission" "localhost:1527" "listen,resolve")}}
The configuration option in the arquillian.xml is startDerby = true/false
Generally glassfish 3 has exactly the same feature. The error is the bug that I've mentioned in the initial comment. You can see more output be dafining outputToConcoleto true. Here are more details about the bug in glassfish:
https://java.net/jira/browse/GLASSFISH-21004
and the root cause form the bundled derby
https://issues.apache.org/jira/browse/DERBY-6438
> Support for starting derby database automatically
> -------------------------------------------------
>
> Key: ARQ-2123
> URL: https://issues.jboss.org/browse/ARQ-2123
> Project: Arquillian
> Issue Type: Enhancement
> Components: GlassFish Containers
> Reporter: Bartosz Majsak
> Fix For: glassfish_1.0.0.Final
>
>
> t would be very handy to let the derby database start automatically (on demand) in the managed environment.
> I was forced to bump the glassfish version used for testing from 4.0-b72 to 4.1.1. This was due to a bug that refused me to start the derby database failing with this error:
> {{AccessControlException: access denied ("java.net.SocketPermission" "localhost:1527" "listen,resolve")}}
> The configuration option in the arquillian.xml is startDerby = true/false
> Generally glassfish 3 has exactly the same feature. The error is the bug that I've mentioned in the initial comment. You can see more output be dafining outputToConcoleto true. Here are more details about the bug in glassfish:
> https://java.net/jira/browse/GLASSFISH-21004
> and the root cause form the bundled derby
> https://issues.apache.org/jira/browse/DERBY-6438
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 10 months