[JBoss JIRA] Created: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
4:55 p.m.
Archive for remote GF-3.1 should not be saved to disk prior to deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm running
on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a root or
as the same user as the maven than there is no problem. But actually I run a Jenkins build
task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:25 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Pedro Kowalski commented on ARQ-569:
------------------------------------
I don't think that jersey-multipart has support for anything else than File based
DataBodyPart
(http://jersey.java.net/nonav/apidocs/1.0.3/contribs/jersey-multipart/com/...)
Even assuming that the archive is exported as OutputStream (by Shrinkwrap exporter),
sending it as a byte[] is rejected by the GF REST Admin.
Any ideas or more details from someone with more knowledge about GF Admin? :-)
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Pedro Kowalski edited comment on ARQ-569 at 9/3/11 8:34 AM:
------------------------------------------------------------
I don't think that jersey-multipart has support for anything else than File based
DataBodyPart
(http://jersey.java.net/nonav/apidocs/1.0.3/contribs/jersey-multipart/com/...)
Even assuming that the archive is exported as OutputStream (by Shrinkwrap exporter),
sending it as a byte[] is rejected by the GF REST Admin.
Any ideas or more details from someone with more knowledge about GF Admin? :-)
EDIT: we could go with simply adding write permission (others +w) to the exported archive
file, but this will not prevent any umask settings set on the parent directory.
was (Author: PedroKowalski):
I don't think that jersey-multipart has support for anything else than File based
DataBodyPart
(http://jersey.java.net/nonav/apidocs/1.0.3/contribs/jersey-multipart/com/...)
Even assuming that the archive is exported as OutputStream (by Shrinkwrap exporter),
sending it as a byte[] is rejected by the GF REST Admin.
Any ideas or more details from someone with more knowledge about GF Admin? :-)
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:51 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-569:
-----------------------------------
trying to get Jason Lee to comment on this, he should know a thing or two about the admin
apis.
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:50 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Jason Lee commented on ARQ-569:
-------------------------------
I talked to Jason Porter about this last night. It seems to be more of an issue with the
Jersey Client rather than GlassFish. On the GlassFish side, Jersey simply reads the bytes
from the HTTP message, without regard for where the data came from originally. The
problem, though, is the the Jersey Client API only allows Files (even in the recently
released 1.9). From the hip, I think your options are to use another client library, or
implement a suitable sublcass of FormDataBodyPart. Option B shouldn't be too
difficult, and I bet the Jersey guys would love the contribution. ;) If I find some time,
I'll see if I can implement it, but I can't promise how quickly I can get that
done.
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:50 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Pedro Kowalski commented on ARQ-569:
------------------------------------
"(...)implement a suitable sublcass of FormDataBodyPart. Option B shouldn't be
too difficult, and I bet the Jersey guys would love the contribution."
Challenge accepted ;-)
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:12 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Pedro Kowalski commented on ARQ-569:
------------------------------------
JIRA request for enhancement of the Jersey client:
http://java.net/jira/browse/JERSEY-777
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:49 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-569:
-----------------------------------
Wouldn't Stream support make more sense then byte[] ? Pass a InputStream to the
FormBodyPart and it will be streamed as the HTTP request goes along, instead of having to
'cache' it up memory before sending. ?
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:51 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen edited comment on ARQ-569 at 9/21/11 12:49 PM:
-------------------------------------------------------------
Wouldn't Stream support make more sense then byte[] ? Pass a InputStream to the
FormBodyPart and it will be streamed as the HTTP request goes along, instead of having to
'cache' it up in memory before sending ?
was (Author: aslak):
Wouldn't Stream support make more sense then byte[] ? Pass a InputStream to the
FormBodyPart and it will be streamed as the HTTP request goes along, instead of having to
'cache' it up memory before sending. ?
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:59 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Pedro Kowalski commented on ARQ-569:
------------------------------------
Hmm, I guess you're right - didn't think about that.
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:21 p.m.
New subject: [JBoss JIRA] (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Pedro Kowalski commented on ARQ-569:
------------------------------------
Enhancement published to Jersey repo:
http://java.net/projects/jersey/sources/svn/content/trunk/jersey/contribs...
I guess we just need to wait until the new version of contribs-multipart will be
released.
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
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
1:21 p.m.
New subject: [JBoss JIRA] (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Pedro Kowalski reassigned ARQ-569:
----------------------------------
Assignee: Pedro Kowalski
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
Assignee: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
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
9:54 p.m.
New subject: [JBoss JIRA] (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Pedro Kowalski updated ARQ-569:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
https://github.com/arquillian/arquillian-container-glassfish/pull/12
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
Assignee: Pedro Kowalski
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
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
10:02 p.m.
New subject: [JBoss JIRA] (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-569:
------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: glassfish_1.0.0.Final
Resolution: Done
pushed upstream
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Pedro Kowalski
Assignee: Pedro Kowalski
Fix For: glassfish_1.0.0.Final
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
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
11:52 p.m.
New subject: [JBoss JIRA] (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-569:
------------------------------
Fix Version/s: glassfish_1.0.0.CR3
(was: glassfish_1.0.0.Final)
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Piotr Nowicki
Assignee: Piotr Nowicki
Fix For: glassfish_1.0.0.CR3
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
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:14 a.m.
New subject: [JBoss JIRA] (ARQ-569) Archive for remote GF-3.1 should not be saved to disk prior to deployment
[
https://issues.jboss.org/browse/ARQ-569?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-569.
-----------------------------
Archive for remote GF-3.1 should not be saved to disk prior to
deployment
-------------------------------------------------------------------------
Key: ARQ-569
URL: https://issues.jboss.org/browse/ARQ-569
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR1
Environment: Ubuntu 11.04 x86, GlassFish Server Open Source Edition 3.1.1 (build
12)
Reporter: Piotr Nowicki
Assignee: Piotr Nowicki
Fix For: glassfish_1.0.0.CR3
When I build the deployment archive, it is saved it /tmp/ARCHIVE_FILENAME (I'm
running on GNU/Linux box) with chmod 444 (-r--r--r--). If I run the glassfish server as a
root or as the same user as the maven than there is no problem. But actually I run a
Jenkins build task (user: jenkins) and run the server as another user (user: pedro).
In such case, the Arquillian remote tests fail because the Glassfish cannot use the
/tmp/ARCHIVE_FILENAME (permission denied). If you change the chmod and give others the
write permission - it will work fine.
Aslak suggested avoiding the FileDataBodyPart during deployment.
--
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
4487
days inactive
4686
days old
arquillian-issues@lists.jboss.org
15 comments
7 participants
participants (7)
-
Aslak Knutsen (JIRA) -
Aslak Knutsen (Updated) (JIRA)
-
Jason Lee (JIRA)
-
Pedro Kowalski (Assigned) (JIRA)
-
Pedro Kowalski (Commented) (JIRA)
-
Pedro Kowalski (JIRA)
-
Pedro Kowalski (Updated) (JIRA)