Why can't deploy large amount of beans in one server?

[junli]

Hi,All:
I use weblogic6.0 sp1.Now,i met a strange problem.When I tried to deploy a new
beans to the weblogic server which had been deployed on a large amount of beans
(more then 30 beans,include sesssion beans and entity beans)already,the weblogic
will prompt error messages and the new deployment will not success,but when I
tried to deployed this new beans at an other weblogic server,which almost no already
existed beans on it,it success.it looks that the weblogic will deny the new deployment
when too many beans are there sometime,does weblogic "overflow" or "overload"
for beans? how can sloved this problem by config the related parameters at console?

[lijun]

this is the error message:

<2001/06/02 14:57:27:CST> <Error> <Management> <MBean mydomain:Name=ejbEItemidms
tInfo,Location=myserver,Type=ApplicationConfig &#12398;&#23646;&#24615; Deployed
&#12398;&#20516;&#12434; true &#12395;&#35373;
&#23450;&#12377;&#12427;&#38555;&#12395; InvocationTargetException &#12364;&#30330;&#29983;&#12375;&#12414;&#12375;&#12383;&#12290;&#12513;&#12477;&#12483;&#12489;:
public void weblo
gic.management.mbeans.custom.Application.setDeployed(boolean) throws weblogic.ma
nagement.DeploymentException,weblogic.management.UndeploymentException
weblogic.management.DeploymentException: Could not deploy: 'ejbEItemidmstInfo.ja
r'
Possible reasons include:
1. The bean or an interface class has been modified but
the deployment descriptor has not been updated
2. The database mappings in the deployment descriptor do not
match the database definition
3. The jar file is not a valid jar file
4. The jar file does not contain a valid bean
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
at weblogic.j2ee.Application.deploy(Application.java:167)
at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
ation.java:217)
at weblogic.management.mbeans.custom.Application.setDeployed(Application
java:187)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
anImpl.java:1136)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
anImpl.java:773)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
anImpl.java:750)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
igurationMBeanImpl.java:256)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1331)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
s(ConfigurationMBeanImpl.java:318)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
igurationMBeanImpl.java:259)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
ava:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:
291)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:173)
at $Proxy52.setDeployed(Unknown Source)
at weblogic.management.console.pages._panels._mbean._ejbcomponent._jspSe
rvice(_ejbcomponent.java:353)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:213)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:1265)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:1622)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

[Mike Mormando]

Are you sure that you're passing your bean through weblogic.ejbc?
When I forget that is when I see these errors.
hth
Mike

"lijun" <j...@netkiss.com.cn> wrote in message
news:3b188f32$1...@newsgroups.bea.com...