Bamboo Maven Glassfish Deploy - maven

I've been trying to set up continuous integration and deployment for a Java EE application.
Continuous integration is working however the deployment always fail.
I tried 3 things in the maven parameter ${local.glassfish.passfile}:
path to domain-password
path to.gfclient/pass
password string
One last thing I tried was:
hardcoded value inside pom.xml
Ear pom.xml configuration:
<plugin>
<groupId>org.glassfish.maven.plugin</groupId>
<artifactId>maven-glassfish-plugin</artifactId>
<version>2.1</version>
<configuration>
<glassfishDirectory>${local.glassfish.home}</glassfishDirectory>
<user>${local.glassfish.user}</user>
<passwordFile>${local.glassfish.passfile}</passwordFile>
<domain>
<name>${local.glassfish.domain}</name>
<adminPort>${local.glassfish.adminPort}</adminPort>
<httpPort>${local.glassfish.httpPort}</httpPort>
</domain>
<components>
<component>
<name>${project.artifactId}</name>
<artifact>target/${project.build.finalName}.ear</artifact>
</component>
</components>
<debug>true</debug>
<terse>false</terse>
<echo>true</echo>
</configuration>
</plugin>
Running mvn glassfish:deploy inside the ear folder via the terminal successfully deploys the ear artefact to the server.
Bamboo Error log:
[INFO] Scanning for projects...
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building ear 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-glassfish-plugin:2.1:undeploy (default-cli) # ear ---
[INFO] Deprecated syntax, instead use:
[INFO] asadmin --echo --terse=false --interactive=false --user admin --passwordfile /home/guest/.gfclient/pass --host localhost --port 55004 undeploy [options] ...
[INFO] asadmin --host localhost --port 55004 --user admin --passwordfile /home/guest/.gfclient/pass --interactive=false --echo=true --terse=false undeploy --keepreposdir=false --isredeploy=false --cascade=false --_ignorecascade=false --_classicstyle=false ear
[INFO] Command undeploy failed.
[ERROR] Authentication failed for user: admin
[ERROR] (Usually, this means invalid user name and/or password)
[ERROR] Undeployment of ear failed.
[ERROR] For more detail on what might be causing the problem try running maven with the --debug option
[ERROR] or setting the maven-glassfish-plugin "echo" property to "true".
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.699 s
[INFO] Finished at: 2014-03-06T17:39:50+00:00
[INFO] Final Memory: 8M/19M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.glassfish.maven.plugin:maven-glassfish-plugin:2.1:undeploy (default-cli) on project ear: Undeployment of ear failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Failing task since return code of [/home/guest/apache-maven-3.2.1/bin/mvn glassfish:undeploy] was 1 while expected 0
Finished task 'Maven Glassfish Undeploy'
Note that I ran the "asadmin login" command after I changed the admin password in order to update the pass file.
guest#foo:~$ asadmin --port 55004 login
Enter admin user name [Enter to accept default]> admin
Enter admin password>
Admin login information for host [localhost] and port [55004] is being overwritten with credentials provided. This is because the --savelogin option was used during create-domain command.
Login information relevant to admin user name [admin] for host [localhost] and admin port [55004] stored at [/home/guest/.gfclient/pass] successfully.
Make sure that this file remains protected. Information stored in this file will be used by administration commands to manage associated domain.
Command login executed successfully.
Also, Glassfish version is 4.0, Maven version is 3.2.1.

If you have used the asadmin login command you don't need to specify the user and password in the undeploy and deploy command as it will use the credentials that you've set using the login command.

There is a Bamboo plugin that allows to deploy an war file to Glassfish Application Server.
https://marketplace.atlassian.com/apps/1219234/tasks-for-glassfish-server

Related

How to use external sonar server for jHipster project

I am currently developing a spring boot application with jHipster and I want to use an existing sonar server from my company to analyze the code. JHipster only describes a way to use a build in sonar server from a docker container. Unfortunately that is not an option for me since my machine is running on Windows Server 2012, that is not supported by docker.
I already tried to start the maven build by adding the server url as a build parameter to the maven build, but it is ignoring it.
mvn clean test sonar:sonar -Dsonar.host.url=http://server-ip:server-port/ -Dsonar.login=login -Dsonar.password=pw
I am relatively new to the topic and was using the given command by the jhipster reference page (https://jhipster.github.io/code-quality/), so the test profile should be the correct one for this purpose.
When I run the command it ignores the given url paramter and still tries to use localhost where it expects the sonar in a docker container.
08:31:53.473 INFO - Create JDBC datasource for
jdbc:h2:tcp://localhost/sonar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 55.017 s
[INFO] Finished at: 2017-06-12T08:31:53+00:00
[INFO] Final Memory: 65M/392M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on project project: Fail to connect to database: Cannot load JDBC driver class 'org.h2.Driver' -> [
Help 1]
Since jHipster generates and configures a lot in the background I have no idea if I am missing something vital here. Maybe a configuration file I have to adjust? I really appreciate the help.
The pom.xml was generated by jHipster and the maven plugin is configured as followed:
<plugin>
<groupId>org.sonarsource.scanner.maven</groupId>
<artifactId>sonar-maven-plugin</artifactId>
<version>${sonar-maven-plugin.version}</version>
</plugin>
The version is set in the properties as:
<sonar-maven-plugin.version>3.2</sonar-maven-plugin.version>
I tried setting up my project on a linux vm with a running local docker sonar instance as suggested by the jHipster team and it was running fine, it is just very inconvenient for me since I have an available company sonar instance running in the intranet.
I also tried modifying my settings.xml as suggested and that was ignored, though it lead to a different looking error message:
[INFO] --- sonar-maven-plugin:3.2:sonar (default-cli) # project ---
[INFO] User cache: C:\Users\Administrator\.sonar\cache
[ERROR] SonarQube server [http://localhost:9000] can not be reached
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:12 min
[INFO] Finished at: 2017-06-14T11:29:22+00:00
[INFO] Final Memory: 57M/408M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on project project: Unable to execute SonarQube: Fail to download libraries from server: Status r
eturned by url [http://localhost:9000/batch_bootstrap/index] is not valid: [404] -> [Help 1]
Everything is explained in the sonar docs : https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Maven
You should edit the settings.xml file in you ~/.m2directory with the following:
<settings>
<pluginGroups>
<pluginGroup>org.sonarsource.scanner.maven</pluginGroup>
</pluginGroups>
<profiles>
<profile>
<id>sonar</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<!-- Optional URL to server. Default value is http://localhost:9000 -->
<sonar.host.url>
http://myserver:9000
</sonar.host.url>
</properties>
</profile>
</profiles>
</settings>
Try to add the following line into the properties section of your pom.xml file.
<sonar.host.url>http://1.2.3.4:9000/</sonar.host.url>
With the IP address corresponding to your sonarqube server.

Running mvn scm:status or release:prepare fails with RTC 4.x: "Error code for Jazz SCM status command - 54"

Both of these plugins fail the same way, which makes sense as the release plugin calls scm:status to ensure that there are no local modifications.
Here's the normal (short) error from running mvn release:prepare:
$ mvn -DworkingDirectory=/tmp/maven release:prepare release:perform
[INFO] Scanning for projects...
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building bar 2.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.5:prepare (default-cli) # bar ---
[INFO] Verifying that there are no local modifications...
[INFO] ignoring changes on: **/pom.xml.backup, **/release.properties, **/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
[INFO] Executing: /bin/sh -c cd /home/davisk/workspaces/foo/bar && scm status --username johndoe#us.ibm.com --password '*****'
[INFO] Working directory: /home/davisk/workspaces/foo/bar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.954 s
[INFO] Finished at: 2014-07-23T03:12:04-05:00
[INFO] Final Memory: 15M/481M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli) on project bar: Unable to check for local modi
fications
[ERROR] Provider message:
[ERROR] Error code for Jazz SCM status command - 54
[ERROR] Command output:
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Running mvn scm:status -X, I can get the full underlying error message (trimmed):
[DEBUG] Consumed line :Workspace: (1023) "bar" (This workspace is unreachable.)
[DEBUG] Consumed line : Could not determine the URI required to connect to the repository. The UUID of
[DEBUG] Consumed line : the repository is _t2J8kWECEeKBH6O9T2VOlA. If you know the repository URI run
[DEBUG] Consumed line : 'login' command providing the repository URI. If not, please contact your
[DEBUG] Consumed line : administrator.
Need to get this resolved.
From some research, it sounds like Maven's RTC/Jazz SCM provider may have been built against the RTC 3.0 command line interface.
Fortunately, there seems to be a perfectly usable workaround: login via RTC's scm login command line tool ahead of time:
$ scm login --repository-uri https://fizz.example.com:9443/ccm --username johndoe#us.ibm.com
Password (johndoe#us.ibm.com # https://fizz.example.com:9443/ccm):
Logged in to https://fizz.example.com:9443/ccm
After running this once, it seems the login is cached somewhere, and the mvn scm:status call then works as expected.

Where to keep a GPG secret key for Jenkins running on Windows?

I am attempting to release my artifacts to the OSS Sonatype Nexus Server using Jenkins. But I get the following error when the signing is attempted for the artifacts. I have generated my gpg keys and have it under C:/Users/Sara/AppData/Roaming/gnupg folder on my Windows machine. From another question Where to keep a GPG secret key for a Maven project in CI environment?, I could see the answer is for a Unix based environment. Can anybody shed light on where to place the secret keys for jenkins in a windows environment?
[INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) # StudentEnrollmentWithREST ---
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:27.647s
[INFO] Finished at: Mon Jan 20 12:12:27 CST 2014
[INFO] Final Memory: 22M/53M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.1:sign (sign-artifacts) on project StudentEnrollmentWithREST: Exit code: 2 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:45.118s
[INFO] Finished at: Mon Jan 20 12:12:33 CST 2014
[INFO] Final Memory: 8M/19M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on project StudentEnrollmentWithREST: Maven execution failed, exit code: '1' -> [Help 1]
[JENKINS] Archiving C:\Program Files (x86)\Jenkins\workspace\Upload REST Release Artifacts\pom.xml to com.github.elizabetht/StudentEnrollmentWithREST/1.3-SNAPSHOT/StudentEnrollmentWithREST-1.3-SNAPSHOT.pom
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
channel stopped
Skipping Cobertura coverage report as build was not UNSTABLE or better ...
Finished: FAILURE
According to the gpg:sign documentation.
The ${gpg.homedir} which defaults to ~/.gnupg or %APPDATA%/gnupg should be finding your keyring in the folder you have currently described.
The files named pubring.gpg and secring.gpg by default can also be configured.
Perhaps the issue is finding the right key, maven uses the 'default key' unless otherwise configured.
The first key in the keyring is the default.
Choosing a key - this might go in a project/parent or settings, or even on commandline
<properties>
<gpg.keyname>C78F3CC4</gpg.keyname>
</properties>
Some other configuration is more likely to be 'per host' , maybe a profile in your settings.xml
<profile>
<id>gpg-release</id>
<properties>
<gpg.passphrase>...</gpg.passphrase>
<gpg.useagent>true</gpg.useagent>
<!--
<gpg.defaultKeyring>false</gpg.defaultKeyring>
<gpg.homedir>/private/.../.gnupg</gpg.homedir>
<gpg.publicKeyring>/private/.../.gnupg/pubring.gpg</gpg.publicKeyring>
<gpg.secretKeyring>/private/.../.gnupg/secring.gpg</gpg.secretKeyring>
-->
</properties>
</profile>
If you use the command line with OSS Sonatype rather than in your settings xml, then it will need further gymnastics.
From OSS Sonatype documentation.
Because maven-release-plugin will start a new Maven instance, -Dgpg.passphrase=PASSPHRASE won't work in this case, instead, you should use
mvn release:perform -Darguments=-Dgpg.passphrase=PASSPHRASE
[and configure in the project pom usage of ${arguments}]
Adding the profile section as shown below in settings.xml worked
<profile>
<id>gpg-release</id>
<properties>
<gpg.passphrase>password</gpg.passphrase>
<gpg.useagent>true</gpg.useagent>
<gpg.defaultKeyring>false</gpg.defaultKeyring> <gpg.homedir>C:/Users/User/AppData/Roaming/gnupg</gpg.homedir> <gpg.publicKeyring>C:/Users/User/AppData/Roaming/gnupg/pubring.gpg</gpg.publicKe‌​yring> <gpg.secretKeyring>C:/Users/User/AppData/Roaming/gnupg/secring.gpg</gpg.secre‌​tKeyring> </properties>
</profile>
You can save your GPG key in Jenkins in the manage Jenkins/configure-system. There is an RPM signing key section where you can add your GPG keys. Before you should have added required plugin in Jenkins

Weblogic Maven Deploy

I am using weblogic 10.3.6.0 and maven 3. I want to deploy my project to weblogic server with maven plugin. I do same steps in this oracle documents
But when I build my project, I get this error
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss Portlet Bridge - JSF 2 Basic Portlet 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- weblogic-maven-plugin:2.9.5:deploy (default-cli) # TestWeblogic ---
[WARNING] The POM for weblogic:weblogic:jar:10.3.6 is missing, no dependency i information available
[WARNING] The POM for weblogic:webservices:jar:10.3.6 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.446s
[INFO] Finished at: Mon Jul 01 16:50:02 EEST 2013
[INFO] Final Memory: 7M/111M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:weblogic-maven-plugin:2.9.5:deploy ( (default-cli) on project TestWeblogic: Execution default-cli of goal org.codehaus.mojo:weblogic-maven-plugin:2.9.5:deploy failed: Plugin org.codehaus.mojo:weblogic-maven-plugin:2.9.5 or one of its dependencies could not be resolved: The following artifacts could not be resolved: weblogic:weblogic:jar:10.3.6, weblogic:webservices:jar:10.3.6: Failure to find weblogic:weblogic:jar:10.3.6 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch
[ERROR] Re-run Maven using the -X switch to enable full debug logging
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
My pom xml is here
<plugin>
<groupId>com.oracle.weblogic</groupId>
<artifactId>weblogic-maven-plugin</artifactId>
<version>10.3.6.0</version>
<configuration>
<adminurl>t3://localhost:7001</adminurl>
<user>username</user>
<password>password</password>
<upload>true</upload>
<action>deploy</action>
<remote>false</remote>
<verbose>true</verbose>
<source>${project.build.directory}/${project.build.finalName}.${project.packaging}</source>
<name>${project.build.finalName}</name>
</configuration>
</plugin>
I use weblogic server 10.3.6.0, eclipse juno , maven 3.0.4.
You need to import wlfullclient.jar and webservices.jar. I tried importing the weblogic.jar first, but maven threw a ClassCastException by weblogic.utils.Debug.
To build this client you need to execute: java -jar wljarbuilder.jar inside the WL_HOME/server/lib.
Once you are ready, import into the maven repository by executing the following commands:
mvn install:install-file -DgroupId=weblogic -DartifactId=weblogic
-Dversion=10.3.6 -Dpackaging=jar -Dfile=wlfullclient.jar
mvn install:install-file -DgroupId=weblogic -DartifactId=webservices -Dversion=10.3.6 -Dpackaging=jar -Dfile=webservices.jar
Looks like you are using JBoss, not Weblogic based on your logs:
Building JBoss Portlet Bridge

maven, maven-glassfish-plugin, domain creation

I try to create domain by maven
<plugin>
<groupId>org.glassfish.maven.plugin</groupId>
<artifactId>maven-glassfish-plugin</artifactId>
<version>2.1</version>
<configuration>
<glassfishDirectory>${glassfish.home}</glassfishDirectory>
<user>${glassfish.username}</user>
<adminPassword>${glassfish.password}</adminPassword>
<autoCreate>true</autoCreate>
<debug>true</debug>
<echo>true</echo>
<terse>true</terse>
<domain>
<name>${project.artifactId}</name>
<adminPort>4048</adminPort>
<httpPort>4080</httpPort>
<httpsPort>4043</httpsPort>
<iiopPort>4037</iiopPort>
<reuse>false</reuse>
</domain>
<components>
<component>
<name>${project.artifactId}</name>
<artifact>${project.build.directory}/${project.build.finalName}.war</artifact>
</component>
</components>
</configuration>
</plugin>
domain created but not started
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building EventLogger
[INFO] task-segment: [org.glassfish.maven.plugin:maven-glassfish-plugin:2.1:deploy]
[INFO] ------------------------------------------------------------------------
[INFO] [glassfish:deploy {execution: default-cli}]
[INFO] Domain event-logger isn't started. Starting it for you.
[INFO] Domain event-logger does not exist. Creating it for you.
[INFO] CLI031 Warning: Option "profile" is obsolete and will be ignored.
[INFO] asadmin --host localhost --port 4848 --user admin --passwordfile /tmp/mgfp1661748332213879832.tmp --interactive=false --echo=true --terse=true create-domain --adminport 4048 --profile developer --domaindir /home/makaka/glassfish3/glassfish/domains --instanceport 4080 --savemasterpassword=false --usemasterpassword=false --domainproperties http.ssl.port=4043:orb.listener.port=4037 --savelogin=false --nopassword=false --checkports=true event-logger
[INFO] The AS_ADMIN_ADMINPASSWORD option in the password file is deprecated.
[INFO] Use AS_ADMIN_PASSWORD instead.
[INFO] Distinguished Name of the self-signed X.509 Server Certificate is:
[INFO] [CN=ubuntu,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US]
[INFO] Distinguished Name of the self-signed X.509 Server Certificate is:
[INFO] [CN=ubuntu-instance,OU=GlassFish,O=Oracle Corporation,L=Santa Clara,ST=California,C=US]
[INFO] No domain initializers found, bypassing customization step
[INFO] Domain event-logger created.
[INFO] Domain event-logger admin port is 4048.
[INFO] Domain event-logger admin user is "admin".
[INFO] asadmin --host localhost --port 4848 --user admin --passwordfile /tmp/mgfp1661748332213879832.tmp --interactive=false --echo=true --terse=true start-domain --verbose=false --upgrade=false --debug=true --_dry-run=false --domaindir /home/makaka/glassfish3/glassfish/domains event-logger
[ERROR] The Master Password is required to start the domain. No console, no prompting possible. You should either create the domain with --savemasterpassword=true or provide a password file with the --passwordfile option.
[ERROR] Unable to start domain "event-logger".
[ERROR] For more detail on what might be causing the problem try running maven with the --debug option
[ERROR] or setting the maven-glassfish-plugin "echo" property to "true".
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to start domain "event-logger".
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14 seconds
[INFO] Finished at: Tue Nov 27 21:03:48 MSK 2012
[INFO] Final Memory: 4M/74M
[INFO] ------------------------------------------------------------------------
Right after creation I can manually start domain, but can't log in to admin panel - invalid password.
If after creation I manually reset the password - Maven still can't start domain. But I can manually start domain from command line and then login to admin panel...
I tried to use passwordFile instead of adminPassword. Nothing changed... Content of that file (I created it manually):
AS_ADMIN_MASTERPASSWORD myPass
AS_ADMIN_USERPASSWORD myPass
AS_ADMIN_ALIASPASSWORD myPass
Also I wonder why asadmin needs master password - it's not for autentification master pass description
Any ideas what's wrong?
P.S. I use ubunutu 12.10, glassfish 3.1.2.2, used developer profile to install glassfish
I had a wrong password file. It should contain
AS_MASTER_PASSWORD=myPass1
AS_ADMIN_PASSWORD=myPass2
AS_ADMIN_USERPASSWORD=myPass3

Resources