Cannot redeploy after upgrading 6.0sp1 -> 6.1

Brandon

unread,

Aug 10, 2001, 7:53:13 PM8/10/01

to

Hey,

I am getting the following exception whenever I try to redeploy. I have tried
touching REDEPLOY, using weblogic.deploy, and using the console. Has anyone else
had problems with redeployment on 6.1.

I never had any problem with redeployment on 6.0 sp1 except some erroneous error
about a missing ejb xml or sumpin.

<Aug 10, 2001 3:44:01 PM PDT> <Error> <J2EE> <Error undeploying application purgatory:
cannot remove the default match>
<Aug 10, 2001 3:44:01 PM PDT> <Error> <Management> <InvocationTargetException
setting attribute Deployed on MBean mrstock:Location=myserver,Name=purgatory,Type=ApplicationConfig
to value false. Method: public void weblogic.management.mbeans.custom.Application.setDeployed(boolean)
throws weblogic.management.DeploymentException,weblogic.management.UndeploymentExceptionjava.lang.IllegalArgumentException:
cannot remove the default match
at weblogic.servlet.utils.URLMatchMap.remove(URLMatchMap.java:290)
at weblogic.servlet.internal.ServletContextManager.removeContext(ServletContextManager.java:149)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:451)
at weblogic.j2ee.WebAppComponent.undeploy(WebAppComponent.java:86)
at weblogic.j2ee.Application.undeploy(Application.java:267)
at weblogic.j2ee.J2EEService.undeployApplication(J2EEService.java:225)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic

Thanks a lot people!

Brandon

Rob Woollen

unread,

Aug 10, 2001, 8:11:13 PM8/10/01

to

Can you explain some more about what you are deploying? Is it a WAR, EAR ,or JAR file? Is it exploded or archived?

-- Rob

firendpen

unread,

Aug 11, 2001, 7:49:12 PM8/11/01

to

Brandon,

It seems that you are trying to redeploy an exploded WebApp. Does this happen when you try to redeploy on the admin or managed
server?

Brandon

unread,

Aug 14, 2001, 4:52:04 PM8/14/01

to

Thanks Rob,

I get this exception regardless of whether it is for
an EAR, WAR, or EJB JAR. Also regardless of whether
I touch REDEPLOY, go through the console, or use
weblogic.deploy. I am using an exploded EAR, and archived
WAR, and JAR files.

Thanks very much for any help.

Brandon

Rob Woollen <rwoo...@nomail.com> wrote:
>Can you explain some more about what you are deploying? Is it a WAR,
>EAR ,or JAR file? Is it exploded or archived?
>
>-- Rob
>
>Brandon wrote:
>
>> Hey,
>>
>> I am getting the following exception whenever I try to redeploy. I
>have tried
>> touching REDEPLOY, using weblogic.deploy, and using the console. Has
>anyone else
>> had problems with redeployment on 6.1.
>>
>> I never had any problem with redeployment on 6.0 sp1 except some erroneous
>error
>> about a missing ejb xml or sumpin.
>>
>> <Aug 10, 2001 3:44:01 PM PDT> <Error> <J2EE> <Error undeploying application
>purgatory:
>> cannot remove the default match>
>> <Aug 10, 2001 3:44:01 PM PDT> <Error> <Management> <InvocationTargetException

>> setting attribute Deployed on MBean foo:Location=myserver,Name=purgatory,Type=ApplicationConfig

brandon

unread,

Aug 17, 2001, 2:54:09 PM8/17/01

to

Does anyone have any clue what this exception is talking about?

Ctrl-C ain't going to cut it for redeploying WebLogic. If this
problem can't be solved, I cannot recommend WebLogic to management
at my organization.

Redeploying was working fine in 6.0sp1.

Thanks for your help!

Brandon

Rob Woollen

unread,

Aug 17, 2001, 2:24:37 PM8/17/01

to

Are you deploying this from the applications directory or from a
separate directory?

Let's just try a simple case. Try re-deploying an ejb-jar that is in
the applications directory. I do this all the time with 6.1, and it
works fine for me. You should just copy a new jar file or touch the
existing jar file for redeployment to work.

If that works, let's try some more complex examples to get a better idea
of what is and is not working.

Also, you should open a case with sup...@bea.com

-- Rob

--

----------------------------------------------------------------------

AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server

by Michael Girdley, Rob Woollen, and Sandra Emerson

http://learnWebLogic.com

Gary Keim

unread,

Aug 17, 2001, 4:03:28 PM8/17/01

to

It's not an EJB issue but our servlet container is not allowing a servlet
which is the default servlet, meaning that it's match pattern is one of "/",
"/*", or "*" to be undeployed. I have no idea why we would do this.

The workaround is clearly to not define a default servlet. That is, change
the servlet mapping pattern to be some other than the ones listed above.
--
Gary

"brandon" <b...@nomail.com> wrote in message
news:3b7d5a41$1...@newsgroups.bea.com...

brandon

unread,

Aug 17, 2001, 9:34:21 PM8/17/01

to

Hey Rob,

Turns out it was a simple solution, one that I could have sworn
I already checked, but anywho...

There was a conflict between config.xml and application.xml,
regarding default web app in config.xml and module/web element
in application.xml with a context-root of '/'. This may be a bug,
whatever, we have a fix.

Thanks a lot for your assistance Rob.

Brandon

Gene Chuang

unread,

Sep 7, 2001, 6:57:52 PM9/7/01

to

Is there a fix for this in a future 6.1 service pack? I'm seeing the same error (stacktrace at
bottom), but simply from untargetting a war:

"web" is my exploded war, and is registered in applications.xml of my ear as:

I do not have a default servlet using servlet-mapping. My servlets registered in web.xml are:

<context-param>
<param-name>weblogic.httpd.defaultServlet</param-name>
<param-value>weblogic.servlet.FileServlet</param-value>
</context-param>
....
<servlet-mapping>
<servlet-name>BinaryServlet</servlet-name>
<url-pattern>/fdr/*</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>BinaryCardServlet</servlet-name>
<url-pattern>/file/*</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>StateMachineServlet</servlet-name>
<url-pattern>/main/*</url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name>CounterServlet</servlet-name>
<url-pattern>/cnt/*</url-pattern>
</servlet-mapping>

People on this thread suggest 3 possible culprits:

1) trying to redeploy/undeploy an exploded WAR
2) bad <context-root> in applications.xml
3) bad <servlet-mapping> or defaultServlet setting in web.xml

Which is it, and has BEA addressed this?

Gene

********************

<Sep 7, 2001 3:45:23 PM PDT> <Info> <HTTP> <[HTTP myserver] Unloading web app: web>
java.lang.IllegalArgumentException: cannot remove the default match

at weblogic.servlet.utils.URLMatchMap.remove(URLMatchMap.java:290)
at
weblogic.servlet.internal.ServletContextManager.removeContext(ServletContextManager.java:149)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:451)
at weblogic.j2ee.WebAppComponent.undeploy(WebAppComponent.java:86)

at weblogic.j2ee.Application.removeComponent(Application.java:182)
at weblogic.j2ee.J2EEService.removeDeployment(J2EEService.java:147)
at
weblogic.management.mbeans.custom.DeploymentTarget.removeDeployment(DeploymentTarget.java:368)
at
weblogic.management.mbeans.custom.DeploymentTarget.removeDeployment(DeploymentTarget.java:167)
at weblogic.management.mbeans.custom.WebServer.removeWebDeployment(WebServer.java:86)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy35.removeWebDeployment(Unknown Source)
at
weblogic.management.configuration.WebServerMBean_CachingStub.removeWebDeployment(WebServerMBean_Cach
ingStub.java:1115)
at
weblogic.management.mbeans.custom.DeploymentTarget.removeDeployment(DeploymentTarget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.removeDeployment(DeploymentTarget.java:167)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:4
82)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy19.removeDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1452)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:839)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:791)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:286)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:298)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:90)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:116)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:172)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:263)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2390)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1959)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Sep 7, 2001 3:45:23 PM PDT> <Info> <Management> <Configuration changes for domain saved to the
repository.>

"Brandon" <b...@transbay.net> wrote in message news:3b7465d9$1...@newsgroups.bea.com...