Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2013-03-25T11:28:25Z by SystemAdmin
SystemAdmin
SystemAdmin
8523 Posts
ACCEPTED ANSWER

Pinned topic JMSConnectionFactory Initialization Exception in WAS8

‏2013-03-24T11:58:39Z |
I am trying to configure JMS connection factory in WAS 8 .Connection factory creation through admin console was successful
But the server start up failed with below error. "<channel name>" in below exception is the place holder for the MQ channel name.

[:] CWWMQ0035E: An attempt to set a property on a WebSphere MQ messaging provider connection factory failed with an error. The error message was 'JMSCC0005: The specified value <channel name> is not allowed for 'CHAN'.'. The property name was CHAN, with value <channel name> of type class java.lang.String. The Connection Factory was of type class com.ibm.mq.jms.MQXAConnectionFactory.

com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid configuration passed to resource binding logic. REASON: Failed to create connection factory: Error raised constructing AdminObject : JMSCC0005: The specified value <channel name> is not allowed for 'XMSC_WMQ_CHANNEL'.
at com.ibm.ejs.jms.JMSConnectionFactoryReferenceable.<init>(JMSConnectionFactoryReferenceable.java:209)
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createNonGenericConnectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:677)
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createNonGenericConnectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:642)
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createMQConnectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:564)
at com.ibm.ws.runtime.component.binder.MQConnectionFactoryBinder.getBindingObject(MQConnectionFactoryBinder.java:316)
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImpl.java:516)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:1545)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResource(ResourceMgrImpl.java:1391)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(ResourceMgrImpl.java:1330)
at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(ResourceMgrImpl.java:1070)
at com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrImpl.java:750)
at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:539)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:233)
at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:539)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:502)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:354)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:267)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:730)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:234)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:95)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:76)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:371)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:142)
Updated on 2013-03-25T11:28:25Z at 2013-03-25T11:28:25Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    8523 Posts
    ACCEPTED ANSWER

    Re: JMSConnectionFactory Initialization Exception in WAS8

    ‏2013-03-25T00:29:36Z  in response to SystemAdmin
    What value are you setting it to? It could contain invalid characters for MQ, or be blank or too long. MQ channel names must be 1 to 20 characters.
  • SystemAdmin
    SystemAdmin
    8523 Posts
    ACCEPTED ANSWER

    Re: JMSConnectionFactory Initialization Exception in WAS8

    ‏2013-03-25T11:28:25Z  in response to SystemAdmin
    Did you edit the exception text before posting it in this forum to change whatever your channel name actually was into the text "<channel name>" or is what we are seeing the actual exception text as it was shown?

    If the latter, then your "<channel name>" is indeed the problem - since the characters '<'>' and blank are all not allowed in the channel name.

    Cheers
    Morag