Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

JMSAdmin error

219 views
Skip to first unread message

Pravesh Godiyal

unread,
Apr 9, 2003, 7:04:15 AM4/9/03
to
I am trying to start JMSAdmin.bat and it is giving the following error. I am
using the websphere application developer 5.0 as my server fro IIOP. I don't
understand which library/jar file is missing.The stack trace is giving:

Exception in thread "main" java.lang.NoClassDefFoundError:
com/ibm/CORBA/iiop/GlobalORBExists
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:385)
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:259)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCt
xFactory.java
:166)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)
at com.ibm.ws.naming.util.WsnInitCtx.<init>(WsnInitCtx.java:79)
at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory
.java:137)
at
com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnIniti
alContextFact
ory.java:80)
at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:255)
at javax.naming.InitialContext.init(InitialContext.java:231)
at javax.naming.InitialContext.<init>(InitialContext.java:207)
at com.ibm.mq.jms.admin.AdminService.initJNDI(AdminService.java:188)
at com.ibm.mq.jms.admin.JMSAdmin.<init>(JMSAdmin.java:228)
at com.ibm.mq.jms.admin.JMSAdmin.main(JMSAdmin.java:1844)

The jmsadmin.config file has follwing entries:
INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory

PROVIDER_URL=iiop://localhost:2809/

thanks in advance

Pravesh


Francesco Cataudella

unread,
Apr 10, 2003, 4:50:58 AM4/10/03
to
Hi,
try with this environment:
1) crete and execute a bat file setenv.bat like this
set WAS_HOME=C:\Program Files\IBM\WebSphere Studio\runtimes\base_v5
set MQ_JAVA_INSTALL_PATH=C:\Pierluigi\JMSAdmin\Java
set JAVA_HOME=%WAS_HOME%\java\bin

set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\com.ibm.mq.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\com.ibm.mqjms.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\jms.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\j2ee.jar


set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\providerutil.jar


set WebsphereCP=%WAS_HOME%\lib\naming.jar;%WAS_HOME%\lib\namingclient.jar;%WAS_HOME%\lib\runtime.jar;

set path=C:\Program Files\IBM\WebSphere
Studio\runtimes\base_v5\java\bin;

set CLASSPATH=.;%MQ%;%WebsphereCP%;%CLASSPATH%;C:\Pierluigi\JMSAdmin\Java\lib


2)The file JMSAdminWAS.config like:
#
# This is the default configuration file for the MQSeries Classes for
# Java Message Service Administration Tool.
#
# 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:/JNDI-Directory
PROVIDER_URL=iiop://port-usai:2809/jms
#
# 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
#


3)The file JMSAdminWAS.bat like:

@echo off

rem ----------------------------------------------
rem IBM MQSeries JMS Admin Tool Execution Script
rem for Windows NT
rem
rem Note that the properties passed to the java
rem program are defaults, and should be edited
rem to suit your installation if necessary
rem ----------------------------------------------


java -DMQJMS_LOG_DIR="%MQ_JAVA_INSTALL_PATH%"\log
-DMQJMS_TRACE_DIR="%MQ_JAVA_INSTALL_PATH%"\trace
-DMQJMS_INSTALL_PATH="%MQ_JAVA_INSTALL_PATH%"
-Dserver.root="%WAS_HOME%" com.ibm.mq.jms.admin.JMSAdmin -cfg
JMSAdminWAS5.config


"Pravesh Godiyal" <pra...@hotmail.com> wrote in message news:<3e93fe2b$0$27769$afc3...@news.optusnet.com.au>...

Pravesh Godiyal

unread,
Apr 12, 2003, 2:21:20 AM4/12/03
to
Thanks Francesco,

It was the problem with my Classpath and Path variables setting, I tried
setting them as null and then putting the classpaths and paths of the files
required. It worked. Now I can run the JMSAdmin and can see the prompt for
Websphere Mq. I tried creating the context, using
define ctx(mq), it throw error , unable to create context.

I even treid to define queue and it gave unable to bind object. What could
be wrong. I am using the IIOP access to WSAD 5.0 (not 4.0). The port is
correct 2809 as mentioned in the server setting.

If you could let me know what is wrong, I will appreciate that. Thanks for
your previous reply.

Regards

Pravesh

"Francesco Cataudella" <francesco....@wintec.it> wrote in message
news:c05d3fa3.03041...@posting.google.com...

Francesco Cataudella

unread,
Apr 17, 2003, 5:57:04 AM4/17/03
to
Hi,
i have not an answer for you, my JMSAdmin works fine, but i don't
create a ctx.
For the protocol: you can use IIOP and CORBALOC but be careful with
port, because if you have a single installation of WAS 5.0 the port is
2809, but when you install WAS 5.0 ND, WebSphere change the value of
the port to use of the single installation, then you have to control
the valid number of port.
For more information you can download the redbook from the ibm site.


Regards,

Francesco

"Pravesh Godiyal" <pra...@hotmail.com> wrote in message news:<3e97b05c$0$1301$afc3...@news.optusnet.com.au>...

0 new messages