[ronen malka]

Hi

I’m trying to deploy the application to an WAS 6.1 but I get the following error:

WASX7017E: Exception received while running file “C:/Program Files/MyEclipse 6.1 Blue Edition – Milestone 1/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere61_6.0.300.zmyeclipse60300200802/installEAR.jacl”; exception information: com.ibm.ws.scripting.ScriptingException: WASX7111E: Cannot find a match for supplied option: “[Global
PAYplus, GPPWeb.war,WEB-INF/web.xml, default_host]” for task “MapWebModToVH”

Please advice.

Thank you in Advance,

[Greg]

Hello,

Blue edition M1 has an issue with EAR deployments when there is a web module whose <display-name> element contains spaces. We have already identified and fix this issue for the next release of 6.1 Blue edition GA which is due out for release next month.

However, to fix your current problem, go to your GPPWeb project, open the web.xml and in the top-level <display-name> element, remove any extra whitespace like spaces or newlines. Or you could just comment the entire <display-name> element out. Then deployment should succeed.

Once again this is just a temporary workaround that you will need to use until our next version is released where we have fixed this problem.

Thanks for reporting the issue. Hope this helps.

[JUL3P]

Hello,

I’m getting this error in MyEclipse Blue whenever I deploy my EAR project to WebSphere 6.1:

WASX7017E: Exception received while running file “C:/Program Files/MyEclipse 6.1 Blue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere61_6.1.0.zmyeclipse610200803/installEAR.jacl”; exception information: com.ibm.ws.scripting.ScriptingException: WASX7111E: Cannot find a match for supplied option: “[null, CWSWeb.war,WEB-INF/ibm-web-ext.xmi, AppDeploymentOption.Yes, 1]” for task “JSPReloadForWebMod”

What could be the cause of this deployment error?

I’m specifically using
MyEclipse Blue Edition Version: 6.1.0 GA Build id: 6.1.0-GA-20080314
WebSphere 6.1.0.13

Thanks for any help you can provide.

[Greg]

Can you try this deployment again in the latest release? MyEclipse Blue 6.5M1

Thanks

[JUL3P]

Greg,

I upgraded to MyEclipse Blue 6.5M1, Now I’m getting the error below whenever I do an “Add Deployment…”

-nodeployejb
WASX7017E: Exception received while running file “C:/Program-Files/MyEclipse-6_5M1-Blue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere61_6.4.100.zmyeclipse64100200805/installEAR.jacl”; exception information: com.ibm.ws.scripting.ScriptingException: WASX7111E: Cannot find a match for supplied option: “[GlobalWeb.war, GlobalWeb.war,WEB-INF/web.xml, default_host]” for task “MapWebModToVH”

[Greg]

What type of application are you deploying? An EAR with one or multiple Web modules?

Could you try to just create a simple test, since war or an EAR with a simple web module and try to deploy it? I just want to establish that you can deploy a simple ear/war and then we can diagnosis what could be wrong with this one application.

Also could you post your web.xml contents?

Thanks

[JUL3P]

Greg,

I’m deploying an EAR with multiple web modules.

I tried to update all the web.xml of all the Web modules to to have <display-name> values set according to the war names (w/o spaces) and it moved past MapWebModToVH.

Now, I’m getting an error in JSPReloadForWebMod, ie.
-nodeployejb
WASX7017E: Exception received while running file “C:/Program-Files/MyEclipse-6_5M1-Blue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere61_6.4.100.zmyeclipse64100200805/installEAR.jacl”; exception information: com.ibm.ws.scripting.ScriptingException: WASX7111E: Cannot find a match for supplied option: “[null, GlobalWeb.war,WEB-INF/ibm-web-ext.xmi, AppDeploymentOption.Yes, 1]” for task “JSPReloadForWebMod”

This error is the same error before I upgraded to MyEclipse Blue 6.5M1.

I analyzed your installEAR.jacl and see that your module/component that’s internally calling installEAR.jacl is passing “null” for the Web module field. This can be seen when tracing argv 6…ie..
argv6= {“null” “GlobalWeb.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1} {“null” “GlobalWebServices.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1} {“null” “CWSWeb.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}

I think that’s the cause of the error. Why is it “null” instead of the actual Web module name?

[JUL3P]

Greg,

Here are the contents of my web.xml……

<?xml version=”1.0″ encoding=”UTF-8″?>

<!DOCTYPE web-app PUBLIC “-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN” “http://java.sun.com/dtd/web-app_2_3.dtd”&gt;

<web-app id=”web-app_1″>

<display-name>GlobalWeb.war</display-name>
<description>Global Web Project</description>

<context-param>
<param-name>log4jFile</param-name>
<param-value>/glog4j.xml</param-value>
</context-param>

<!– tell the Spring context loader where to find the Spring config files –>
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>
classpath:g1-spring.xml
classpath:g2-spring.xml
classpath:g3-spring.xml
classpath*:gcustom-spring.xml
</param-value>
</context-param>

<!– This causes Spring to read the beanRefContext.xml to create a single, shared context –>
<context-param>
<param-name>parentContextKey</param-name>
<param-value>single-context</param-value>
</context-param>

<listener>
<listener-class>com.company1.common.web.listener.Listener1</listener-class>
</listener>

<!– Initialize the Spring services –>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>

<servlet>
<servlet-name>Servlet1</servlet-name>
<display-name>Servlet1</display-name>
<servlet-class>com.company1.common.servlets.servlet1</servlet-class>
</servlet>

<servlet>
<servlet-name>Servlet2</servlet-name>
<display-name>Servlet2</display-name>
<servlet-class>com.company1.common.servlets.servlet2</servlet-class>
</servlet>

<servlet>
<servlet-name>Servlet3</servlet-name>
<display-name>Servlet3</display-name>
<servlet-class>com.company1.common.servlets.servlet3</servlet-class>
</servlet>

<servlet>
<servlet-name>Servlet4</servlet-name>
<servlet-class>com.company1.common.servlets.servlet4</servlet-class>
</servlet>

<!–
route all JNLP file requests through the Servlet3 to
forward to a JSP so that we can embed logic in the JNLP file
–>
<servlet-mapping>
<servlet-name>Servlet3</servlet-name>
<url-pattern>*.jnlp</url-pattern>
</servlet-mapping>

<!– route all jar file requests through the Servlet4 so that
the packed jars are returned –>
<servlet-mapping>
<servlet-name>Servlet4</servlet-name>
<url-pattern>*.jar</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>Servlet1</servlet-name>
<url-pattern>/compservlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Servlet2</servlet-name>
<url-pattern>/Servlet2</url-pattern>
</servlet-mapping>

<!–
To specify mime mappings, create a file named mime-mappings.xml, put it in your project’s mergedir.
Organize mime-mappings.xml following this DTD slice:

<!ELEMENT mime-mapping (extension, mime-type)>
–>

<welcome-file-list>
<welcome-file>gapp.html</welcome-file>
<welcome-file>idximaging.html</welcome-file>
<welcome-file>idxview1.html</welcome-file>
</welcome-file-list>

<!–
To specify error pages, create a file named error-pages.xml, put it in your project’s mergedir.
Organize error-pages.xml following this DTD slice:

<!ELEMENT error-page ((error-code | exception-type), location)>
–>

<!–
To add taglibs by xml, create a file called taglibs.xml and place it
in your merge dir.
–>

<resource-ref id=”ResRef_1″>
<description><![CDATA[A JDBC resource]]></description>
<res-ref-name>jdbc/adb</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id=”ResRef_2″>
<description><![CDATA[B JDBC resource]]></description>
<res-ref-name>jdbc/bdb</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id=”ResRef_3″>
<description><![CDATA[C JDBC resource]]></description>
<res-ref-name>jdbc/cdb</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref id=”ResRef_4″>
<res-ref-name>img/ABC</res-ref-name>
<res-type>javax.resource.cci.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>

<!–
To set up security settings for your web app, create a file named web-security.xml, put it in your project’s mergedir.
Organize web-security.xml following this DTD slice:

<!ELEMENT security-constraint (display-name?, web-resource-collection+, auth-constraint?, user-data-constraint?)>
<!ELEMENT web-resource-collection (web-resource-name, description?, url-pattern*, http-method*)>
<!ELEMENT web-resource-name (#PCDATA)>
<!ELEMENT url-pattern (#PCDATA)>
<!ELEMENT http-method (#PCDATA)>
<!ELEMENT user-data-constraint (description?, transport-guarantee)>
<!ELEMENT transport-guarantee (#PCDATA)>

<!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)>
<!ELEMENT auth-method (#PCDATA)>
<!ELEMENT realm-name (#PCDATA)>
<!ELEMENT form-login-config (form-login-page, form-error-page)>
<!ELEMENT form-login-page (#PCDATA)>
<!ELEMENT form-error-page (#PCDATA)>
–>

</web-app>

[Greg]

The “null” parameter has worked in all of our development tests. Plus if “null” was incorrect it shouldn’t prevent deployment from succeeding. At the very worst it should just prevent JSP class reloading from working properly. So it looks like something more fundamental is wrong with your setup.

Here are some quick sanity checks that you could perform.

1. Ensure that you have configured Websphere 6.1.x and not some previous version like 6.0
2. Test deployment with just a simple EAR with one web module in it (just create blank projects from wizards) and try to deploy that

[JUL3P]

1. WebSphere version is 6.1.0.13

2. I created a simple EAR with one web module, deployed it in the same manner and it was deployed successfully.

.

[Greg]

So the problem isn’t with the “null” parameter. This is something else about your configuration that it doesn’t like.

Ok, I will need to ask a favor, which is tough because you have already been a big help with tracking down this problem.

If you can do the following, this will help us nail this problem down. You mentioned in your last post that a simple ear + web module deploys fine, so that confirms that there is nothing strange about your Websphere 6.1 or Blue setup. THe next thing to do is isolate what piece of your current application that is failling to deploy deviates from the simple case. So here is what I suggest:

1. Create a new EAR application that looks like a skeleton of your current application that is failling.
2. In an incremental fashion, add small pieces to this skeleton EAR and deploy to your server after adding each piece to make sure deployment still succeeds
3. Eventually you will add a piece to the new EAR from your existing application that will break the deployment. This will show us exactly what setting/configuration of your existing EAR that is causing deployment to fail.

I know that sounds like alot of work, but this is the only way I know how to proceed. Thanks for your patience with us while we try to sort this issue out.

[JUL3P]

Greg,

Here’s a “what if” scenario that just popped to my mind and tried it…

I deleted all the <display-name> and <description> on the web xmls of each web modules. Then I tried to do a deployment in the same manner as before.. This time it deployed successfully. It got past the error. I’m now testing the deployment.

[Greg]

Interesting. Could you replicate the error in deployment by putting a combination of the 2 <display name> and description into a web project? IF you figure out the combination, post it here and I’ll send to the dev team and they should be able to get a fix in for the next release.

[mst98sub]

Hi Greg,

I have the same problem with MyEclipse Blue Edition 6.1.0 GA while deploying a single web project to WAS6.1.
Probably it is still an open bug.

If the web.xml of version 2.3 contains a display-name tag, myeclipse does not create a META-INF directory for the surrounding enterprise archive.
As a result WAS is not able to install the application and the script installWebModul.jacl reports the following error message:

“WASX7111E: Cannot find a match for supplied option…”

The problem does not occur with version 2.4 web.xmls.

[Author]

Posts