Maven 2.x WebSphere 6 Plugin

wsStartApp and wsStopApp throwing WASX7025E exception.

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0
  • Fix Version/s: 1.2
  • Labels:
    None
  • Environment:
    was 6.0.2.19, linux
  • Number of attachments :
    3

Description

The the /tmp/wsant21486jacl is being created by the plugin. No manual intervention here.

The file is attached. Its contents are only the following 2 lines.

set am [$AdminControl queryNames "WebSphere:*,type=ApplicationManager,process=server1"]
$AdminControl invoke $am "stopApplication" "fdproxyear"

[INFO] [wsadmin] WASX7209I: Connected to process "WebSphere_Portal" on node developer1 using SOAP connector; The type of process is: UnManagedProcess
[INFO] [wsadmin] WASX7017E: Exception received while running file "/tmp/wsant21486jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7025E: Error found in String ""; cannot create ObjectName.
[INFO]
[ERROR]
[ERROR] BUILD FAILED
[ERROR] file:/root/IBM/rationalsdp7.0/workspace/fdproxy-module/../fdproxy-ear/target/was6-maven-plugin/was6plugin-build.xml:33: Java returned: 105
[ERROR] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:110)
[ERROR] at com.ibm.websphere.ant.tasks.WsAdmin.execute(WsAdmin.java:397)
[ERROR] at com.ibm.websphere.ant.tasks.StopApplication.execute(StopApplication.java:176)
[ERROR] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
[ERROR] at org.apache.tools.ant.Task.perform(Task.java:341)
[ERROR] at org.apache.tools.ant.Target.execute(Target.java:309)
[ERROR] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[ERROR] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[ERROR] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
[ERROR] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[ERROR] at org.apache.tools.ant.Main.start(Main.java:196)
[ERROR] at org.apache.tools.ant.Main.main(Main.java:235)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:391)
[ERROR] at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
[ERROR] at java.lang.Thread.run(Thread.java:570)

  1. Text File
    wsant21486jacl.txt
    23/Jan/09 7:24 PM
    0.1 kB
    Venkat K
  2. Text File
    testoutput.txt
    26/Jan/09 6:15 PM
    169 kB
    Venkat K
  3. Text File
    strippeddownpom.txt
    26/Jan/09 6:15 PM
    3 kB
    Venkat K

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David J. M. Karlsen added a comment -

Please provide a stripped down pom and output from running maven with the -X argument.

Show
David J. M. Karlsen added a comment - Please provide a stripped down pom and output from running maven with the -X argument.
Hide
Permalink
Venkat K added a comment -

I am running the following file from the module project. I hope I took care of the -X argument for the maven command.

I attached the stripped down pom as well.

echo $basedir
mvn -U -X clean install -Dm2repo=/root/.m2/repository -Dtargeturl=localhost -Dsoapport=10033 -Dwas60home=/opt/IBM/WebSphere/AppServer -Dtargetuser=wasadm -Dtargetpassword=wasadm

Show
Venkat K added a comment - I am running the following file from the module project. I hope I took care of the -X argument for the maven command. I attached the stripped down pom as well. echo $basedir mvn -U -X clean install -Dm2repo=/root/.m2/repository -Dtargeturl=localhost -Dsoapport=10033 -Dwas60home=/opt/IBM/WebSphere/AppServer -Dtargetuser=wasadm -Dtargetpassword=wasadm
Hide
Permalink
apache maillist added a comment -

we use targetServer=WebSphere_MyServer specified in the pom.xml which does not seem to be passed to the wsStartApp jacl script that was6 plugin generated. below is the output ran manually from wsadmin

wsadmin>$AdminControl queryNames "WebSphere:*,type=ApplicationManager,process=WebSphere_MyServer"
WebSphere:platform=dynamicproxy,cell=cell01,version=6.0.2.25,name=ApplicationManager,mbeanIdentifier=ApplicationManager,type=ApplicationManager,node=mynode,process=WebSphere_MyServer

wsadmin>$AdminControl queryNames "WebSphere:*,type=ApplicationManager,process=server1"

wsadmin>

Show
apache maillist added a comment - we use targetServer=WebSphere_MyServer specified in the pom.xml which does not seem to be passed to the wsStartApp jacl script that was6 plugin generated. below is the output ran manually from wsadmin wsadmin>$AdminControl queryNames "WebSphere:*,type=ApplicationManager,process=WebSphere_MyServer" WebSphere:platform=dynamicproxy,cell=cell01,version=6.0.2.25,name=ApplicationManager,mbeanIdentifier=ApplicationManager,type=ApplicationManager,node=mynode,process=WebSphere_MyServer wsadmin>$AdminControl queryNames "WebSphere:*,type=ApplicationManager,process=server1" wsadmin>
Hide
Permalink
Venkat K added a comment -

For the installApp and wsStartApp the configuration elements for server and node are different.

installApp needs

<targetNode> and <targetServer>

but

wsStartApp needs just

<node> and <server>

So for stopApp and startApp to run 'along with' installApp, we need to add the following to the configuration
in addtion to <targetNode> and <targetServer>.

<node>$

{targetNode}

</node>
<server>$

{targetServer}

</server>

so that wsStartApp gets the configuration values it needs. The plugin needs to change so that
this need not be done.

Show
Venkat K added a comment - For the installApp and wsStartApp the configuration elements for server and node are different. installApp needs <targetNode> and <targetServer> but wsStartApp needs just <node> and <server> So for stopApp and startApp to run 'along with' installApp, we need to add the following to the configuration in addtion to <targetNode> and <targetServer>. <node>$ {targetNode} </node> <server>$ {targetServer} </server> so that wsStartApp gets the configuration values it needs. The plugin needs to change so that this need not be done.
Hide
Permalink
Javier Murciego added a comment -

Now installApp and stopApp/startApp goals use the same attributes (without "target" prefix). Cell and cluster attributes have been also updated.

Show
Javier Murciego added a comment - Now installApp and stopApp/startApp goals use the same attributes (without "target" prefix). Cell and cluster attributes have been also updated.
Hide
Permalink
Javier Murciego added a comment -

Preparing 1.2 version release

Show
Javier Murciego added a comment - Preparing 1.2 version release

People

  • Assignee:
    Javier Murciego
    Reporter:
    Venkat K
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: