This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Websphere and the fly likes Trouble Creating JMSProviders through JMX Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Trouble Creating JMSProviders through JMX" Watch "Trouble Creating JMSProviders through JMX" New topic
Author

Trouble Creating JMSProviders through JMX

Kensie Sturdevant
Greenhorn

Joined: May 02, 2011
Posts: 1
I am having trouble creating JMSProviders in WAS through JMX. When i try to create the config data on a Server object it gives an error saying attribute name not valid.

objectName = connection.createConfigData(parent, "JMSProvider","JMSProvider", attrList);

where parent is a Server ObjectName, connection is a wrapper for ConfigService that injects the Session as the first parameter, and attrList is an AttributeList that only contains the name attribute. I would include more code but it wouldn't help without more context. This is the stacktrace i get. it is was version


com.ibm.websphere.management.exception.InvalidAttributeNameException: ADMG0005E: The attribute name is not valid.
at com.ibm.ws.management.configservice.MOFUtil.getAttributeMetaObj(MOFUtil.java:823)
at com.ibm.ws.management.configservice.MOFUtil.getAttributeMetaObj(MOFUtil.java:101)
at com.ibm.ws.management.configservice.MOFUtil.validateAttributeList(MOFUtil.java:917)
at com.ibm.ws.management.configservice.MOFUtil.validateConfigData(MOFUtil.java:152)
at com.ibm.ws.management.configservice.MOFUtil.createRefObject(MOFUtil.java:366)
at com.ibm.ws.management.configservice.DocAccessor.createRootConfigObject(DocAccessor.java:227)
at com.ibm.ws.management.configservice.RootObjectDelegator.createConfigObject(RootObjectDelegator.java:318)
at com.ibm.ws.management.configservice.ResourceProviderDelegator.createConfigObject(ResourceProviderDelegator.java:57)
at com.ibm.ws.management.configservice.ConfigObjectDelegator.createConfigData(ConfigObjectDelegator.java:150)
at com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigDataByTemplate(ConfigServiceImpl.java:1461)
at com.ibm.ws.management.configservice.ConfigServiceImpl.createConfigData(ConfigServiceImpl.java:1499)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1092)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:973)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1139)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1032)
at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:139)
at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPConnector.java:361)
at com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java:217)
at com.ibm.ws.management.connector.soap.SOAPConnection.handleRequest(SOAPConnection.java:64)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:742)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:528)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
Caught: com.ibm.websphere.management.exception.InvalidAttributeNameException: ADMG0005E: The attribute name is not valid.

Thanks For any insight.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Trouble Creating JMSProviders through JMX