[Weblogic 9.2MP2] Error targetting WorkManagerMBean to an empty cluster

Our product installation creates Work Managers using the WLST command.

At the time that the Work Managers are created, we have the Domain, Cluster=
, and Admin Server created. However no Managed Servers yet (they are create=
d later).

The snippet of our WLST script is as follows:

clusterTarget =3D getMBean('/Clusters/myCluster')
ms2=3DgetMBean('/SelfTuning/HDMDomain/MaxThreadsConstraints/MaxThreadConstr=
aint_75')
if ms2 is None:
ms2 =3D cmo.createMaxThreadsConstraint('MaxThreadConstrain t_75')
ms2.setCount(75)
ms2.addTarget(clusterTarget)
else:
ms2.setCount(75)

wm1=3DgetMBean('/SelfTuning/myDomain/WorkManagers/hdm.ConnectionRequests')
if wm1 is None:
cd('/SelfTuning/HDMDomain/WorkManagers')
wm1 =3D cmo.createWorkManager('hdm.ConnectionRequests')
wm1.addTarget(clusterTarget)
wm1.setMaxThreadsConstraint(ms2)

We got the following error:

java.lang.IllegalArgumentException: WorkManagerMBean 'hdm.ConnectionRequest=
s' refers to a constraint or request class 'MaxThreadCons
traint_75' but they are deployed on targets that have no servers in common.=
Please deploy the mbeans such that they share atleast on
e server in common.
at weblogic.management.configuration.WorkManagerLegal Helper.validat=
eTargets(WorkManagerLegalHelper.java:66)=20
at weblogic.management.configuration.WorkManagerMBean Impl.setMaxThr=
eadsConstraint(WorkManagerMBeanImpl.java:480)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessor=
Impl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethod=
AccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.management.jmx.modelmbean.WLSModelMBean.s etAttribute(WL=
SModelMBean.java:620)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.setAtt ribute(Dynamic=
MetaDataImpl.java:180)
at com.sun.jmx.mbeanserver.MetaDataImpl.setAttribute( MetaDataImpl.j=
ava:206)
at com.sun.jmx.interceptor.DefaultMBeanServerIntercep tor.setAttribu=
te(DefaultMBeanServerInterceptor.java:737)
at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribut e(JmxMBeanServ=
er.java:722)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer InterceptorBas=
e.setAttribute(WLSMBeanServerInterceptorBase.java: 124)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer InterceptorBas=
e.setAttribute(WLSMBeanServerInterceptorBase.java: 124)
at weblogic.management.mbeanservers.edit.internal.Edi tLockIntercept=
or.setAttribute(EditLockInterceptor.java:95)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer InterceptorBas=
e.setAttribute(WLSMBeanServerInterceptorBase.java: 124)
at weblogic.management.mbeanservers.internal.Security Interceptor.se=
tAttribute(SecurityInterceptor.java:341)
at weblogic.management.mbeanservers.internal.Authenti catedSubjectIn=
terceptor$8.run(AuthenticatedSubjectInterceptor.ja va:300)
at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(Authent=
icatedSubject.java:363)
at weblogic.management.mbeanservers.internal.Authenti catedSubjectIn=
terceptor.setAttribute(AuthenticatedSubjectInterce ptor.ja
va:298)=20
at weblogic.management.jmx.mbeanserver.WLSMBeanServer .setAttribute(=
WLSMBeanServer.java:290)
at javax.management.remote.rmi.RMIConnectionImpl.doOp eration(RMICon=
nectionImpl.java:1431)
at javax.management.remote.rmi.RMIConnectionImpl.acce ss$100(RMIConn=
ectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$Priv ilegedOperatio=
n.run(RMIConnectionImpl.java:1245)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPr ivilegedOperat=
ion(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.setA ttribute(RMICo=
nnectionImpl.java:679)
at javax.management.remote.rmi.RMIConnectionImpl_WLSk el.invoke(Unkn=
own Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicS erverRef.java:=
550)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicSe rverRef.java:4=
40)
at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(Authent=
icatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Se curityManager.=
java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest (BasicServerRe=
f.java:436)
at weblogic.rmi.internal.BasicServerRef.access$300(Ba sicServerRef.j=
ava:58)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteR equest.run(Bas=
icServerRef.java:975)
at weblogic.work.ExecuteThread.execute(ExecuteThread. java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java :181)

java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: Wor=
kManagerMBean 'hdm.ConnectionRequests' refers to a constr
aint or request class 'MaxThreadConstraint_75' but they are deployed on tar=
gets that have no servers in common. Please deploy the mbeans such that the=
y share atleast one server in common.

My questions are:

1) Why is it prohibited that we create a WorkManager with MaxThreadsContrai=
nt both targeted at a Cluster, but no Managed Servers in the Cluster?

2) Say the Cluster has 1 Managed Server at the time the script is run. But =
months later, another Managed Server is added. Do I have to call addTarget(=
) again for the new Managed Server?

thanks,
-shinta

I believe this was a bug that is fixed in 10.3

You might try targeting in a different edit session and see if that
eliminates the validation error.

Peter

Shinta Smith wrote:
> Our product installation creates Work Managers using the WLST command.
>
> At the time that the Work Managers are created, we have the Domain, Cluster, and Admin Server created. However no Managed Servers yet (they are created later).
>
> The snippet of our WLST script is as follows:
>
> clusterTarget = getMBean('/Clusters/myCluster')
> ms2=getMBean('/SelfTuning/HDMDomain/MaxThreadsConstraints/MaxThreadConstraint_75')
> if ms2 is None:
> ms2 = cmo.createMaxThreadsConstraint('MaxThreadConstrain t_75')
> ms2.setCount(75)
> ms2.addTarget(clusterTarget)
> else:
> ms2.setCount(75)
>
> wm1=getMBean('/SelfTuning/myDomain/WorkManagers/hdm.ConnectionRequests')
> if wm1 is None:
> cd('/SelfTuning/HDMDomain/WorkManagers')
> wm1 = cmo.createWorkManager('hdm.ConnectionRequests')
> wm1.addTarget(clusterTarget)
> wm1.setMaxThreadsConstraint(ms2)
>
> We got the following error:
>
> java.lang.IllegalArgumentException: WorkManagerMBean 'hdm.ConnectionRequests' refers to a constraint or request class 'MaxThreadCons
> traint_75' but they are deployed on targets that have no servers in common. Please deploy the mbeans such that they share atleast on
> e server in common.
> at weblogic.management.configuration.WorkManagerLegal Helper.validateTargets(WorkManagerLegalHelper.java :66)
> at weblogic.management.configuration.WorkManagerMBean Impl.setMaxThreadsConstraint(WorkManagerMBeanImpl. java:480)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at weblogic.management.jmx.modelmbean.WLSModelMBean.s etAttribute(WLSModelMBean.java:620)
> at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.setAtt ribute(DynamicMetaDataImpl.java:180)
> at com.sun.jmx.mbeanserver.MetaDataImpl.setAttribute( MetaDataImpl..java:206)
> at com.sun.jmx.interceptor.DefaultMBeanServerIntercep tor.setAttribute(DefaultMBeanServerInterceptor.jav a:737)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribut e(JmxMBeanServer.java:722)
> at weblogic.management.jmx.mbeanserver.WLSMBeanServer InterceptorBase.setAttribute(WLSMBeanServerInterce ptorBase.java:124)
> at weblogic.management.jmx.mbeanserver.WLSMBeanServer InterceptorBase.setAttribute(WLSMBeanServerInterce ptorBase.java:124)
> at weblogic.management.mbeanservers.edit.internal.Edi tLockInterceptor.setAttribute(EditLockInterceptor. java:95)
> at weblogic.management.jmx.mbeanserver.WLSMBeanServer InterceptorBase.setAttribute(WLSMBeanServerInterce ptorBase.java:124)
> at weblogic.management.mbeanservers.internal.Security Interceptor.setAttribute(SecurityInterceptor.java: 341)
> at weblogic.management.mbeanservers.internal.Authenti catedSubjectInterceptor$8.run(AuthenticatedSubject Interceptor.java:300)
> at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(AuthenticatedSubject.java:363)
> at weblogic.management.mbeanservers.internal.Authenti catedSubjectInterceptor.setAttribute(Authenticated SubjectInterceptor.ja
> va:298)
> at weblogic.management.jmx.mbeanserver.WLSMBeanServer .setAttribute(WLSMBeanServer.java:290)
> at javax.management.remote.rmi.RMIConnectionImpl.doOp eration(RMIConnectionImpl.java:1431)
> at javax.management.remote.rmi.RMIConnectionImpl.acce ss$100(RMIConnectionImpl.java:81)
> at javax.management.remote.rmi.RMIConnectionImpl$Priv ilegedOperation.run(RMIConnectionImpl.java:1245)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.management.remote.rmi.RMIConnectionImpl.doPr ivilegedOperation(RMIConnectionImpl.java:1348)
> at javax.management.remote.rmi.RMIConnectionImpl.setA ttribute(RMIConnectionImpl.java:679)
> at javax.management.remote.rmi.RMIConnectionImpl_WLSk el.invoke(Unknown Source)
> at weblogic.rmi.internal.BasicServerRef.invoke(BasicS erverRef.java:550)
> at weblogic.rmi.internal.BasicServerRef$1.run(BasicSe rverRef.java:440)
> at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(AuthenticatedSubject.java:363)
> at weblogic.security.service.SecurityManager.runAs(Se curityManager.java:147)
> at weblogic.rmi.internal.BasicServerRef.handleRequest (BasicServerRef.java:436)
> at weblogic.rmi.internal.BasicServerRef.access$300(Ba sicServerRef..java:58)
> at weblogic.rmi.internal.BasicServerRef$BasicExecuteR equest.run(BasicServerRef.java:975)
> at weblogic.work.ExecuteThread.execute(ExecuteThread. java:209)
> at weblogic.work.ExecuteThread.run(ExecuteThread.java :181)
>
> java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: WorkManagerMBean 'hdm.ConnectionRequests' refers to a constr
> aint or request class 'MaxThreadConstraint_75' but they are deployed on targets that have no servers in common. Please deploy the mbeans such that they share atleast one server in common.
>
> My questions are:
>
> 1) Why is it prohibited that we create a WorkManager with MaxThreadsContraint both targeted at a Cluster, but no Managed Servers in the Cluster?
>
> 2) Say the Cluster has 1 Managed Server at the time the script is run. But months later, another Managed Server is added. Do I have to call addTarget() again for the new Managed Server?
>
> thanks,
> -shinta