You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Paul Bakker (Created) (JIRA)" <ji...@apache.org> on 2011/10/19 21:45:11 UTC
[jira] [Created] (ACE-191) Provision Glassfish servers
Provision Glassfish servers
---------------------------
Key: ACE-191
URL: https://issues.apache.org/jira/browse/ACE-191
Project: Ace
Issue Type: New Feature
Reporter: Paul Bakker
It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACE-191) Provision Glassfish servers
Posted by "Denis Koelewijn (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137048#comment-13137048 ]
Denis Koelewijn commented on ACE-191:
-------------------------------------
The current composition of the ace-target-devserver always includes de amazon-nodelauncher. This component, on startup, always connects directly to amazon, with in my case, incorrect credentials. This gives a nasty and lengthy stacktrace in the logfile:
2011.10.27 14:24:29 WARNING - Bundle: org.apache.ace.nodelauncher.amazon - Invocation of 'start' failed. - org.jclouds.rest.AuthorizationException: POST https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 -> HTTP/1.1 401 Unauthorized
at org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.refineException(ParseAWSErrorFromXmlContent.java:117)
(....)
Is this as it should be ? I can image Ace being used without deployment to Amazon.... Is the idea to have a separate assembly for deployment to Amazon and for non-Amazon deployment, or will there be one Ace assembly for all kinds of deployments ? In the latter case, it might not be desirable to always connect directly to Amazon on the startup ?
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: ace-191-pom.patch, ace-nodelauncher-amazon-cfg.patch, glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ACE-191) Provision Glassfish servers
Posted by "Paul Bakker (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Bakker updated ACE-191:
----------------------------
Attachment: glassfish-aws.patch
Note that my previous two patches (from this morning) are also included in this patch. I discussed this with Marcel already.
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Attachments: glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (ACE-191) Provision Glassfish servers
Posted by "Denis Koelewijn (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135760#comment-13135760 ]
Denis Koelewijn edited comment on ACE-191 at 10/26/11 7:04 AM:
---------------------------------------------------------------
mvn clean install didn't work because glassfish launcher was build after the target-devserver.
Corrected in attached patch.
was (Author: denisk):
mvn clean install didn't work because glassfish launcher was build after de target-devserver.
Corrected in attached patch.
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: ace-191-pom.patch, glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ACE-191) Provision Glassfish servers
Posted by "Denis Koelewijn (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Koelewijn updated ACE-191:
--------------------------------
Attachment: ace-nodelauncher-amazon-cfg.patch
I've added default values for the new properties in the amazone-nodelaucher.cfg to prevent this exception and a similar one for the other config parameter:
2011.10.27 13:59:11 ERROR - Bundle: org.apache.felix.configadmin - [org.osgi.service.cm.ConfigurationAdmin] - [org.osgi.service.cm.ManagedService, id=43, bundle=29]: Updating configuration property additionalObrDownloads caused a problem: key missing - org.osgi.service.cm.ConfigurationException: additionalObrDownloads : key missing
at org.apache.ace.nodelauncher.amazon.AmazonNodeLauncher.getConfigProperty(AmazonNodeLauncher.java:303)
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: ace-191-pom.patch, ace-nodelauncher-amazon-cfg.patch, glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACE-191) Provision Glassfish servers
Posted by "Marcel Offermans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134784#comment-13134784 ]
Marcel Offermans commented on ACE-191:
--------------------------------------
Three comments after reviewing this:
Firstly, the ServerType (enum) class seems to be missing from this patch.
Secondly, right now, you more or less "hardcode" the server types by explicitly creating an enum for them. That means that every time we want to add a new server type, we need to modify this code. I think we should try to make the server types configurable.
Finally, there is a hardcoded link to an S3 file in the codebase right now. I understand that's where you now "parked" the GF zip file, but I think we should not hardcode such links. By solving remark #2 I'm hoping this one goes away as well.
WDYT?
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (ACE-191) Provision Glassfish servers
Posted by "Marcel Offermans (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans reassigned ACE-191:
------------------------------------
Assignee: Marcel Offermans
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ACE-191) Provision Glassfish servers
Posted by "Paul Bakker (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Bakker updated ACE-191:
----------------------------
Attachment: glassfish-aws-v2.patch
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACE-191) Provision Glassfish servers
Posted by "Paul Bakker (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135418#comment-13135418 ]
Paul Bakker commented on ACE-191:
---------------------------------
The configuration file has a few more options now:
aceLauncher (defaults to ace-launcher.jar) - The jar file to download from /obr/ and execute. A new launcher for GF is part of the patch.
additionalObrDownloads - Additional jar files to download from /obr/. Used for GF to download the ACE management agent bundle
externalDownloadUrls - Other files that should be download from any url before the launcher is executed.
Neither of the properties are required, if omitted, Ace will work as before.
So to test with GF this could be:
{code}
aceLauncher=ace-glassfish-launcher.jar
additionalObrDownloads=ace-managementagent.jar
externalDownloadUrls=http://amdatu.s3.amazonaws.com/glassfish.zip
{code}
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACE-191) Provision Glassfish servers
Posted by "Marcel Offermans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143865#comment-13143865 ]
Marcel Offermans commented on ACE-191:
--------------------------------------
Denis: no, it is started because the default configuration contains all necessary properties to try to connect to Amazon (but the values are placeholders, so they'll never work). I'll patch the default file to only contain commented out defaults, so this bundle won't try to start.
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: ace-191-pom.patch, ace-nodelauncher-amazon-cfg.patch, glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ACE-191) Provision Glassfish servers
Posted by "Marcel Offermans (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans resolved ACE-191.
----------------------------------
Resolution: Fixed
Applied the patch and:
a) added some try {} finally {} logic to ensure streams are always closed
b) added threads to read stdin/stderr when a new process is spawned to prevent lock-ups
c) some small reformatting and cleanup to better comply with coding style conventions
Please review.
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ACE-191) Provision Glassfish servers
Posted by "Paul Bakker (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135415#comment-13135415 ]
Paul Bakker commented on ACE-191:
---------------------------------
I agree this shouldn't be hardcode. After discussing some options today I changed the amazon launcher to have more configuration options. With these changes, the code is completely generic as before, but can now be configured to download extra files from either the ACE obr or any external url. This is sufficient to bootstrap Glassfish, and I expect most other servers too.
WDYT?
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ACE-191) Provision Glassfish servers
Posted by "Denis Koelewijn (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Koelewijn updated ACE-191:
--------------------------------
Attachment: ace-191-pom.patch
mvn clean install didn't work because glassfish launcher was build after de target-devserver.
Corrected in attached patch.
> Provision Glassfish servers
> ---------------------------
>
> Key: ACE-191
> URL: https://issues.apache.org/jira/browse/ACE-191
> Project: Ace
> Issue Type: New Feature
> Reporter: Paul Bakker
> Assignee: Marcel Offermans
> Attachments: ace-191-pom.patch, glassfish-aws-v2.patch, glassfish-aws.patch
>
>
> It should be possible to provision a Glassfish server instead of a pure Felix instance. Glassfish contains Felix and in recent versions you can directly deploy OSGI bundles as you would do in a normal OSGI container. There are some extra features however; for example you can use EJB, JPA and CDI from bundles and use the WAB as deployment type besides normal bundles. In the future we can also build towards clustering support on top of GF.
> I fixed this by creating a new Ace launcher specifically for Glassfish. It downloads and unzips GF, changes it's configuration files and installs the Ace Management Agent. GF is started using asadmin after that. Besides this I changed the Amazon Node Laucher. You can now configure a serverType to either DEFAULT or GLASSFISH. When the type is GLASSFISH it changes the startup script to download and use the new Glassfish launcher.
> At this moment Glassfish is downloaded from a S3 bucket that I created because the official download server is extremely slow. We have to come up with something better however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira