| Author |
Message
|
| kshah |
 Posted: Tue May 09, 2006 4:03 am Post subject: JMS Nodes configuration in Broker 6 |
 |
|
Novice
Joined: 13 Jun 2005
Posts: 23
|
I have a flow like
JMSInput > JMSMQTransform > MQOutput
I have created the required IntialContext factory changes,qcf and queues required for this.
I can deply the flow as well.
Whn i put a Jms message on the q..the JmsINPUT node tries to take the message but fails and i get following error message in Event Viewer
'' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''''. Location of the bindings = ''file:///C:\IBM\MQ6\Java\bin''. ConnectionFactory Name = ''qcf1''. JMS destination = ''publishqueue''. The JNDI exception text is : ''Cannot instantiate class: ''.
I have fscontext.jar in classpath and also Intial context Factory i mentioned on node is "com.sun.jndi.fscontext.RefFSContextFactory"
If anybody who have used this nodes and successfuily implemented them as well can helop me to resolve the error.It will b of great help.
I have read somewhere a fix was available for JMS thing if one can let me know more abt this it will be great. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 09, 2006 4:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Why does your file URL point to a directory, and not to the bindings file you created with JMSAdmin?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MSV |
| Posted: Tue May 09, 2006 7:49 am Post subject: |
|
|
Acolyte
Joined: 11 Apr 2006
Posts: 59
|
Make sure u had set the correct properties for the INITIAL_CONTEXT_FACTORY and PROVIDER_URL in the C:\IBM\MQ6\Java\bin\JMSAdmin.config file.
Also check out
->whether the resources are existing or not ?{(DIS CTX) in the batch file}
->In the JMSinput node basic properties(LOCATION JNDI-BINDINGS), give the path of the file system where the .bindings file is stored. |
|
| Back to top |
|
|
| kshah |
| Posted: Wed May 10, 2006 6:03 am Post subject: |
|
|
Novice
Joined: 13 Jun 2005
Posts: 23
|
Ya i have all the settings in place.
i have Intial Context Factory
i have queue connection factory
i have jms q
all this things i have done..
only problem i found is instead of fscontext.jar been in classpath( that i have verified by tyring to delete the fscontext.jar while broker is runnig n i was not able to delete it.Once i stop the brokr n config manager i am abe to deletre the jar.So it seems fscontext.jar is available to broker)
then i just want to know i am missingf out something else..or is htere ne fix pack fr JMS nodes..
i m using broker toolkit 6.0.0.1
people who have implemented JMS nOdes ealrier please help..
or even a workaround is welcomed
thanks for ur help guys..
KEEP..IBM UP...N...RUNNING:) |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Wed May 10, 2006 6:30 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi kshah,
Can you please post the changes that u have made in you JMSAdmin.config file, the objects created.....Also the properties that u have set in the JMS node.
Regards. |
|
| Back to top |
|
|
| kshah |
| Posted: Thu May 11, 2006 5:16 am Post subject: JMS nodes not working |
|
|
Novice
Joined: 13 Jun 2005
Posts: 23
|
following is the my JMSAdmin.config
| Code: |
# ------------------------------------------------------------
# IBM Websphere MQ Support for Java Message Service
# This is the default configuration file for the Websphere MQ Classes for
# Java Message Service Administration Tool.
#
# %PUB_START%
# Licensed Materials - Property of IBM
#
# 5724-H72, 5655-L82, 5724-L26
#
# (c) Copyright IBM Corp. 2002, 2005
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
# %PUB_END%
# ------------------------------------------------------------
#
# The following line specifies which JNDI service provider is in use.
# It currently indicates an LDAP service provider. If a different
# service provider is used, this line should be commented out and the
# appropriate one should be uncommented.
#
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
#
# The following line specifies the URL of the service provider's initial
# context. It currently refers to an LDAP root context. Examples of a
# file system URL and WebSphere's JNDI namespace are also shown, commented
# out.
#
#PROVIDER_URL=ldap://polaris/o=ibm,c=us
PROVIDER_URL=file:/C:/IBM/MQ6/Java/bin
#PROVIDER_URL=iiop://localhost/
#
# The following line specifies the security authentication model in use,
# and may be 'none' (for anonymous authentication), 'simple', or 'CRAM_MD5'.
#
SECURITY_AUTHENTICATION=none
#
# If you don't have SECURITY_AUTHENTICATION=none, then JMSAdmin will
# prompt you for the User DN and password. If you want to bypass these
# prompts then you can specify one or both of the values here. Since
# the password here is in cleartext this is not normally recommended
# except for testing. You should replace these values with your own.
#
#PROVIDER_USERDN=cn=Manager,o=ibm,c=uk
#PROVIDER_PASSWORD=secret
#
#
# The following line determines whether to use an InitialDirContext, or an
# InitialContext. Takes value of TRUE or FALSE.
#USE_INITIAL_DIR_CONTEXT=TRUE
#
# The following line specifies a prefix to add to names when carrying out operations such
# as lookup/bind.
#NAME_PREFIX=cn=
#
# The following line specifies a marker at which names will be truncated when viewing
# the contents of the Context.
#NAME_READABILITY_MARKER=..
#
# The three standard types of InitialContextFactory have the following defaults;
# Note that these defaults will be set automatically if the flags are not present, but
# will be overrided by including the flags.
#
# LDAP FSCONTEXT WEBSPHERE
# ------------------------------------------------------------------------------------
# USE_INITIAL_DIR_CONTEXT TRUE FALSE FALSE
# NAME_PREFIX cn= omitted omitted
# NAME_READABILITY_MARKER omitted omitted ..
# |
My JMSInput Node settigs are as folows:
Intial context factory: com.sun.jndi.fscontext.RefFSContextFactory
Location JNDI Bindings: file:///C:\IBM\MQ6\Java\bin
Connection Factory Name : qcf1
Ppoint to Point Soruce q : publishqueue
following is the output of commands entered in JMSAdmin console
Starting Websphere MQ classes for Java(tm) Message Service Administration
InitCtx> display qcf(*)
QCF(qcf1)
MSGRETENTION(YES)
QMANAGER(WMB)
TARGCLIENTMATCHING(YES)
SSLRESETCOUNT(0)
TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
USECONNPOOLING(YES)
POLLINGINT(5000)
RESCANINT(5000)
LOCALADDRESS()
TRANSPORT(CLIENT)
HOSTNAME(127.0.0.1)
TEMPQPREFIX()
CHANNEL(SYSTEM.DEF.SVRCONN)
SYNCPOINTALLGETS(NO)
CCSID(819)
CONNOPT(STANDARD)
SSLFIPSREQUIRED(NO)
PORT(1414)
VERSION(6)
MSGBATCHSZ(10)
FAILIFQUIESCE(YES)
InitCtx> display q(*)
Q(publishqueue)
FAILIFQUIESCE(YES)
QUEUE(PUBLISHQUEUE)
QMANAGER(WMB)
PERSISTENCE(APP)
CCSID(1208)
TARGCLIENT(JMS)
ENCODING(NATIVE)
PRIORITY(APP)
EXPIRY(APP)
VERSION(6)
InitCtx>
I hope this details..helps yoou to find out the answer to my misery..Thanks thanks a lot..for ur help:)[/img] |
|
| Back to top |
|
|
| Ric-Tic |
| Posted: Thu May 11, 2006 6:57 am Post subject: |
|
|
Apprentice
Joined: 18 Nov 2003
Posts: 38
Location: Zurich, Switzerland
|
| The issue with the JMS nodes has been fixed in FP1. And ensure that your toolkit is up to date |
|
| Back to top |
|
|
| vmurali_au |
| Posted: Thu May 11, 2006 10:09 am Post subject: |
|
|
Voyager
Joined: 26 Mar 2004
Posts: 76
|
|
| Back to top |
|
|
| kshah |
| Posted: Sun May 14, 2006 9:05 pm Post subject: |
|
|
Novice
Joined: 13 Jun 2005
Posts: 23
|
Hey guys...
Thanks for ur help ..especially Murali.
Issue is solved after instaling update for Broker..
its now on fixpack 6.0.0.1
so now tht my borker n toolkit both are at fixpack 6.0.0.1
my JMS Node works..completely fine..
Thanks once again..for ur help.. |
|
| Back to top |
|
|
|
|
