http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1113

*** shadow/1113 Mon Mar 26 05:02:41 2001
--- shadow/1113.tmp.12720       Mon Mar 26 05:02:41 2001
***************
*** 0 ****
--- 1,55 ----
+ +============================================================================+
+ | Using the args attribute in the wlrun task                                 |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 1113                        Product: Ant                     |
+ |       Status: NEW                         Version: 1.2                     |
+ |   Resolution:                            Platform: PC                      |
+ |     Severity: Minor                    OS/Version:                         |
+ |     Priority:                           Component: Optional Tasks          |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [EMAIL PROTECTED]                                   |
+ |  Reported By: [EMAIL PROTECTED]                                         |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Hi
+ 
+ Aside: Conor, you addressed a similar problem in the ant-user mail 
+ subject "wlrun task java 1.3 -server option"
+ 
+ It appears that if one uses the wlrun args attribute, the java command that 
is 
+ executed has these arguments AFTER the weblogic.server class and as such 
causes 
+ the server not to start, as illustrated below
+ 
+     [wlrun] Forking java 
-Dweblogic.class.path=T:\weblogic\lib\weblogic510sp8.ja
+ r;T:\weblogic\classes;T:\weblogic\license;T:\weblogic\lib\weblogicaux.jar 
-Djava
+ .security.manager -Djava.security.policy==T:\weblogic\weblogic.policy 
-Dweblogic
+ .system.home=T:\weblogic -Dweblogic.system.name=marraserverA 
-Dweblogic.system.p
+ ropertiesFile=weblogic.properties -ms64m -mx96m -classpath 
T:\weblogic\lib\weblo
+ 
gic510sp8boot.jar;T:\weblogic\classes\boot;T:\jdk1.3\jre\lib\rt.jar;T:\jdk1.3\jr
+ e\lib\i18n.jar;T:\jdk1.3\jre\lib\sunrsasign.jar;T:\jdk1.3\jre\classes 
weblogic.S
+ erver -Dweblogic.cluster.enable=true -Dweblogic.cluster.name=marracluster 
-Dwebl
+ ogic.system.bindAddr=192.168.3.72 
-Dweblogic.cluster.multicastAddress=225.0.0.45
+ 
+     [wlrun] Mon Mar 26 13:56:12 BST 2001:<I> <WebLogicServer> Read global 
proper
+ ties T:\weblogic\weblogic.properties
+     [wlrun] Unable to initialize server: 
weblogic.t3.srvr.T3Srvr$T3FatalInitiali
+ zationException: weblogic.system.name (marraserverA) is not a directory
+     [wlrun] fatal initialization exception
+     [wlrun] weblogic.t3.srvr.T3Srvr$T3FatalInitializationException: 
weblogic.sys
+ tem.name (marraserverA) is not a directory
+     [wlrun]     at weblogic.t3.srvr.T3Srvr.initializeNames(T3Srvr.java:535)
+     [wlrun]     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1072)
+     [wlrun]     at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
+     [wlrun]     at java.lang.reflect.Method.invoke(Native Method)
+     [wlrun]     at weblogic.Server.startServerDynamically(Server.java:99)
+     [wlrun]     at weblogic.Server.main(Server.java:65)
+     [wlrun]     at weblogic.Server.main(Server.java:55)
+ 
+ 
+ This problem can be overcome by putting all arguments into the wlrun 
attribute 
+ jvmargs. Note that this is also a problem in release 1.3
+ 
+ Mick

Reply via email to