我写了一个包含Glassfish域创建序列的小文件，如下所示：
create-domain --adminPort 4848 --instancePort 8080 pouet
start-domain pouet
create-jdbc-connection-pool --datasourceclassname=org.apache.derby.jdbc.ClientDataSource --restype=javax.sql.ConnectionPoolDataSource --validationmethod=meta-data --description="Client datasource using an external Derby instance" --property port=1527:password=pouet:user=pouet:serverName=localhost:databaseName=pouet:connectionAttributes=create\\=true jdbc/datasource/pouet
create-jms-resource --restype javax.jms.ConnectionFactory --description "Standard pouet connection factory" jms/pouet/ConnectionFactory
create-jms-resource --restype javax.jms.Topic --property Name=jms_CrudServiceNotifier jms/CrudServiceNotifier
create-jms-resource --restype javax.jms.Topic jms/TaskExecution
create-jms-resource --restype javax.jms.Topic jms/TaskExecution/InDesign
deploy --force "C:\\Documents and Settings\\ndx\\.m2\\repository\\com\\netoprise\\neo4j-connector\\0.1-SNAPSHOT\\neo4j-connector-0.1-SNAPSHOT.rar"
create-connector-connection-pool --raname=neo4j-connector-0.1-SNAPSHOT --connectiondefinition=com.netoprise.neo4j.connection.Neo4JConnectionFactory --property=xa=true:dir=\$\{com.sun.aas.instanceRoot\}/lib/databases/neo4j Neo4jPool
create-connector-resource --poolname=Neo4jPool neo4j/pool
我通常会通过Glassfish asadmin multimode执行所有步骤。
使用以下说明手动运行所有内容时
E:\java-ext\glassfish3\bin\asadmin.bat --user "pouet" --passwordfile src\main\config\glassfish.password multimode --file target\config\current\create-domain.txt
执行时间不到两分钟。
但是当使用以下pom配置通过maven运行时
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.2</version>
<executions>
<execution>
<id>create start and configure domain</id>
<phase>package</phase>
<goals>
<goal>exec</goal>
</goals>
</execution>
</executions>
<configuration>
<executable>${glassfish.asadmin}</executable>
<arguments>
<argument>--user</argument>
<argument>"${glassfish.user}"</argument>
<argument>--passwordfile</argument>
<argument>"${glassfish.passwordFile}"</argument>
<argument>multimode</argument>
<!-- - - file is a multimode subcommand parameter, and not an asadmin parameter -->
<argument>--file</argument>
<argument>"${user.glassfish.config.path}/create-domain.txt"</argument>
</arguments>
</configuration>
</plugin>
它在域启动时停滞不前，日志最后一行是
No domain initializers found, bypassing customization step
Domain pouet created.
Domain pouet admin port is 4848.
Domain pouet admin user is "pouet".
Command create-domain executed successfully.
Attempting to start pouet.... Please look at the server log for more details.....
Process Explorer表示，对于exec maven插件生成的所有进程，绝对没有CPU消耗。
此外，exec maven插件创建的命令行是
[DEBUG] Executing command line: cmd /c E:\java-ext\glassfish3\bin\asadmin.bat --user "pouet" --passwordfile "E:\JavaWorkspace\pouet\pouet-ear/src/main/config/glassfish.password" multimode --file "E:\JavaWorkspace\pouet\pouet-ear/target/config/current/create-domain.txt"
与我手工输入的完全相同。
那么......什么可能使这个过程挂起？我该怎么做才能解决这个问题？
[编辑] 在进程挂起以下内容之前，将--verbose标志添加到start-domain指令显示为最后一行：
4 août 2011 16:05:58 com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 16 msec.
[#|2011-08-04T16:06:03.078+0200|INFO|glassfish3.1|null|_ThreadID=1;_ThreadName=Thread-1;|Running GlassFish Version: GlassFish Server Open Source Edition 3.1 (build 43)|#]
[#|2011-08-04T16:06:03.156+0200|INFO|glassfish3.1|org.glassfish.ha.store.spi.BackingStoreFactoryRegistry|_ThreadID=10;_ThreadName=Thread-1;|Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry|#]
[#|2011-08-04T16:06:03.843+0200|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=27;_ThreadName=Thread-1;|Grizzly Framework 1.9.31 started in: 297ms - bound to [0.0.0.0:8181]|#]
[#|2011-08-04T16:06:03.859+0200|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=28;_ThreadName=Thread-1;|Grizzly Framework 1.9.31 started in: 266ms - bound to [0.0.0.0:4848]|#]
[#|2011-08-04T16:06:03.859+0200|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=32;_ThreadName=Thread-1;|Grizzly Framework 1.9.31 started in: 219ms - bound to [0.0.0.0:3700]|#]
[#|2011-08-04T16:06:03.859+0200|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=29;_ThreadName=Thread-1;|Grizzly Framework 1.9.31 started in: 391ms - bound to [0.0.0.0:8080]|#]
[#|2011-08-04T16:06:03.921+0200|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.services.impl|_ThreadID=35;_ThreadName=Thread-1;|Grizzly Framework 1.9.31 started in: 15ms - bound to [0.0.0.0:7676]|#]
[#|2011-08-04T16:06:04.109+0200|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=Thread-1;|GlassFish Server Open Source Edition 3.1 (43) startup time : Felix (3 360ms), startup services(1 656ms), total(5 016ms)|#]
[#|2011-08-04T16:06:05.281+0200|INFO|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=46;_ThreadName=Thread-1;|JMXStartupService: Started JMXConnector, JMXService URL = service:jmx:rmi://172.27.63.177:8686/jndi/rmi://172.27.63.177:8686/jmxrmi|#]
如果有人知道在JMX之后要启动什么，以及什么可能阻止它启动，我想，它会帮助我解决这个奇怪的错误。
答案 0 :(得分：1)
我做了比我想象的更多的maven katas，我现在找到了一个解决方案。这显然是maven-antrun-plugin方式。
使用so，我用以下maven antrun代码替换了maven exec配置
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>create start and configure domain</id>
<phase>process-resources</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<failOnError>true</failOnError>
<target>
<exec executable="${glassfish.asadmin}" dir="${glassfish.asadmin.path}"
failonerror="true" vmlauncher="false">
<arg value="--echo"/>
<arg value="true"/>
<arg value="--interactive"/>
<arg value="false"/>
<arg value="--user"/>
<arg value="${glassfish.user}"/>
<arg value="--passwordfile"/>
<arg value="${glassfish.passwordFile}"/>
<arg value="multimode"/>
<arg value="--printprompt=false"/>
<arg value="--file"/>
<arg value="${user.glassfish.config.path}/create-domain.txt"/>
</exec>
</target>
</configuration>
</execution>
</executions>
它完美无缺！