Big3 CMP Tutorial Execution Error (WAS 4.0)

[William H. Jackson Jr.]

Did anyone see the following error when running the Big3 Tutorial:

Dev.Aus.bj67606.C:\WebSphere\AppServer\installedApps>launchClient
Deployed_Big3.
ear 25
IBM WebSphere Application Server, Release 4.0
J2EE Application Client Tool, Version 1.0
Copyright IBM Corp., 1997-2001

WSCL0012I: Processing command line arguments.
WSCL0013I: Initializing the J2EE Application Client Environment.
WSCL0035I: Initialization of the J2EE Application Client Environment has
complet
ed.
WSCL0014I: Invoking the Application Client class Big3ClientApp
PROVIDER_URL string is iiop:///
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception
occurred wh
ile attempting to get an instance of the object for the specified
reference obje
ct. Root exception is javax.naming.NameNotFoundException:
com/ibm/ejb/cb/sample
s/big3/tier2/ProcessClaimHome
at
com.ibm.ejs.ns.jndi.CNContextImpl.doLookup(CNContextImpl.java:1246)
at
com.ibm.ejs.ns.jndi.CNContextImpl.lookup(CNContextImpl.java:981)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInsta
nce(IndirectJndiLookupObjectFactory.java:204)
at
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:3
08)
at
com.ibm.ws.naming.urlbase.UrlContextHelper.isReference(UrlContextHelp
er.java:116)
at
com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLooku
p(UrlContextHelper.java:236)
at
com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1140)
at
com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1112)
at
com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1163)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at Big3ClientApp.getProcessClaimHome(Big3ClientApp.java:65)
at Big3ClientApp.main(Big3ClientApp.java:26)
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.websphere.client.applicationclient.launchClient.createContain
erAndLaunchApp(launchClient.java:430)
at
com.ibm.websphere.client.applicationclient.launchClient.main(launchCl
ient.java:288)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:63)
startMeasIter is 10
java.lang.NullPointerException
at Big3ClientApp.main(Big3ClientApp.java:32)
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.websphere.client.applicationclient.launchClient.createContain
erAndLaunchApp(launchClient.java:430)
at
com.ibm.websphere.client.applicationclient.launchClient.main(launchCl
ient.java:288)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:63)
Dev.Aus.bj67606.C:\WebSphere\AppServer\installedApps>

Any ideas where this happens?

William Jackson

[William H. Jackson Jr.]

Would anyone care to comment?

//william.jackson

[William H. Jackson Jr.]

What is the JNDI Name that will work with this tutorial sample? The one
that the tutorial specifies does not seem to work.

William

"William H. Jackson Jr." wrote:

[David Artus]

Sorry, no time to reproduce this problem right now. Some
possibilities:

1). Is the EJB you're trying to contact running?

2). Would dumping the namespace help? You would
be able to determine which EJBs have registered names
in the global namespace. dumpNamespace in ${WASROOT}/bin
will do that.

[William H. Jackson Jr.]

Thanks for your reply. I did dump the namespace. All that was in there were
things in the installedApps subdirectory. This tutorial was from the
instruction in the InfoCenter Administratiion section. I suspect that there is
something afoul with the Application Assembly Tool.

I don't have the two samples that I did that work on the computer now. I will
have to recreate them to see if they appear in the namespace. I don't remember
if they referenced any EJBs.

Thanks again for your reply.

William

[David Artus]

launchClient is usually used to launch clients of EJBS.

The error message you are getting implies that the ejb name
is not found in the name space. This in turn may indicate that
the ejb is not running.

I would have expected to see use of SEAppInstall and startserver
(or equivalent) before starting the client. Is it possible that you
have missed a step?

[Ken Hygh]

The application assembly tool does not install/deploy the application. You have to
use the commandline (SEAppInstall) or the admin web interface to install. Your ear
will then be exploded into the installedApps directory.

Ken

[William H. Jackson Jr.]

One can either use SEAppInstall or the Administrative Console to deploy the
application. I chose to use the Administrative Console. Further, I used AAT to
assemble and generate the deployment code. Then I use the Administrative Console to
deploy it. I have not missed any steps.

There must be a problem with that Tutorial Sample or in the instructions. I
completed two other samples without this problem. I suspect there is either a
problem with that sample or a bug in AAT.

Although, I am quite the novice, I have repeated the instructions so many times that
I would have had to perform the instructions correctly at least once.

Would one of you do that sample and let me know the results? On a really fast
machine, it should less than 30 minutes to complete the sample.

Thanks,

William

[David Artus]

After using the admin console to install app, how do you start it?

Please post the the logs for the server up to the point of the
"open for e-business" message.

[William H. Jackson Jr.]

Thanks again for replying.

Log as requested. What normally follows this in the log is where I install the
application into WebSphere. This may entail removing the previous version of the
application (stopping and starting WebSphere if application is locked by WebSphere).

To start the client I usually type launchClient Deployed_Big3.ear 25 from the
\websphere\appserver\installedApps subdirectory.

Were you able to perform the steps of the "Enterprise bean (EJB1.1), assembly,
configuration and deployment tutorial"?

If you complete the aboveI suspect that you will either discover the problem or what I may
be doing wrong.

//william.jackson

=====================================================================================================================

IBM WebSphere Application Server, Release 4.0.0
Advanced Single Server Edition for Multiplatforms
Copyright IBM Corp., 1997-2001

************ Start Display Current Environment ************
WebSphere AEs 4.0.0 q0124.08 running with process name Default Server and process id 443
Host Operating System is Windows NT, version 4.0
Java version = J2RE 1.3.0 IBM build cn130-20010502w (JIT enabled: jitc), Java Compiler =
jitc
server.root = C:\WebSphere\AppServer
Java Home = C:\WebSphere\AppServer\java\jre
ws.ext.dirs =
C:\WebSphere\AppServer/java/lib;C:\WebSphere\AppServer/classes;C:\WebSphere\AppServer/lib;C:\WebSphere\AppServer/lib/ext;C:\WebSphere\AppServer/web/help;C:\WebSphere\AppServer/properties

Classpath = C:\WebSphere\AppServer/lib/bootstrap.jar;C:\WebSphere\AppServer/properties
Java Library path =
C:\WebSphere\AppServer\java\bin;.;C:\WINNT\System32;C:\WINNT;C:\WebSphere\AppServer/bin;C:\WebSphere\AppServer\java/bin;C:\WebSphere\AppServer\java/jre/bin;c:\Program
Files\ibm\gsk5\lib;C:\IBM Connectors\Encina\bin;c:\Program
Files\IBM\GSK\lib;C:\IBMDebug\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\system32\nls\ENGLISH;C:\WINNT\system32\nls;c:\jdk1.3\bin;c:\j2sdkee1.2.1\bin;C:\WebSphere\AppServer\bin;C:\IMNnq_NT;C:\PROGRAM
FILES\INFORMIX\BIN;C:\MQSeries\Java\lib;C:\SQLLIB\BIN;C:\SQLLIB\FUNCTION;C:\SQLLIB\SAMPLES\REPL;C:\SQLLIB\HELP;C:\WINNT\Profiles\bj67606\notes\data;C:\RESKIT;C:\WebSphere\AppServer\bin;C:\Microsoft
Visual Studio\Common\Tools\WinNT;C:\Microsoft Visual
Studio\Common\MSDev98\Bin;C:\Microsoft Visual Studio\Common\Tools;C:\Microsoft Visual
Studio\VC98\bin;C:\MSSQL\BINN;Z:.;Y:.;X:.;;C:\WebSphere\AppServer\bin
Current trace specification =
************* End Display Current Environment *************
[01.07.18 15:20:32:352 CDT] 362a76f8 Server U Version : 4.0.0
[01.07.18 15:20:32:502 CDT] 362a76f8 Server U Edition: AEs
[01.07.18 15:20:32:502 CDT] 362a76f8 Server U Build date: Wed Jun 20 00:00:00 CDT
2001
[01.07.18 15:20:32:502 CDT] 362a76f8 Server U Build number: q0124.08
[01.07.18 15:20:45:451 CDT] 362a76f8 DrAdminServer I WSVR0053I: DrAdmin available on port
7000
[01.07.18 15:20:45:771 CDT] 362a76f8 ResourceBinde I WSVR0049I: Binding Session
Persistence datasource as jdbc/Session
[01.07.18 15:20:46:111 CDT] 362a76f8 ResourceBinde I WSVR0049I: Binding
GettingStartedDataSource as jdbc/GsDataSource
[01.07.18 15:20:46:152 CDT] 362a76f8 ResourceBinde I WSVR0049I: Binding Increment Bean
Datasource as jdbc/SampleDataSource
[01.07.18 15:20:46:172 CDT] 362a76f8 ResourceBinde I WSVR0049I: Binding Samples IDB
Datasource as jdbc/sample
[01.07.18 15:20:53:502 CDT] 362a76f8 EJBEngine I WSVR0037I: Starting EJB jar:
Increment Bean Jar
[01.07.18 15:20:55:325 CDT] 362a76f8 SystemOut U Enhydra InstantDB - Version 3.26
[01.07.18 15:20:55:335 CDT] 362a76f8 SystemOut U
[01.07.18 15:20:55:335 CDT] 362a76f8 SystemOut U The Initial Developer of the Original
Code is Lutris Technologies Inc.
Portions created by Lutris are Copyright (C) 1997-2001 Lutris Technologies, Inc.
All Rights Reserved.
[01.07.18 15:20:58:529 CDT] 362a76f8 EJBEngine I WSVR0037I: Starting EJB jar:
C:\WebSphere\AppServer/installedApps\Samples.ear/TimeoutEJBean.jar
[01.07.18 15:21:02:295 CDT] 362a76f8 EJBEngine I WSVR0037I: Starting EJB jar:
Increment EJB Module
[01.07.18 15:21:02:856 CDT] 362a76f8 EJBEngine I WSVR0037I: Starting EJB jar: Hello
EJB Module
[01.07.18 15:21:04:788 CDT] 362a76f8 EJBEngine I WSVR0037I: Starting EJB jar: Account
And Transfer EJB Module
[01.07.18 15:21:07:723 CDT] 362a76f8 ServletEngine A SRVE0161I: IBM WebSphere Application
Server - Web Container. Copyright IBM Corp. 1998-2001
[01.07.18 15:21:07:823 CDT] 362a76f8 ServletEngine A SRVE0162I: Servlet Specification
Level: 2.2
[01.07.18 15:21:07:833 CDT] 362a76f8 ServletEngine A SRVE0163I: Supported JSP
Specification Level: 1.1
[01.07.18 15:21:08:253 CDT] 362a76f8 ServletEngine A Session Manager is Configured -
Initializing...
[01.07.18 15:21:09:515 CDT] 362a76f8 CacheManager A DYNA0011E: Servlet cache file
dynacache.xml not found; caching is disabled
[01.07.18 15:21:09:685 CDT] 362a76f8 ServletEngine A Loading Web Module: Default
Application
[01.07.18 15:21:10:537 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]: JSP 1.1
Processor: init
[01.07.18 15:21:10:657 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
InvokerServlet: init
[01.07.18 15:21:11:448 CDT] 362a76f8 ServletEngine A Loading Web Module: Examples
Application
[01.07.18 15:21:11:628 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]: JSP 1.1
Processor: init
[01.07.18 15:21:11:668 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
SimpleFileServlet: init
[01.07.18 15:21:12:229 CDT] 362a76f8 ServletEngine A Loading Web Module: admin
[01.07.18 15:21:12:770 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]: JSP 1.1
Processor: init
[01.07.18 15:21:12:810 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
SimpleFileServlet: init
[01.07.18 15:21:13:030 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]: action:
init
[01.07.18 15:21:15:344 CDT] 362a76f8 ServletEngine A Loading Web Module: YourCo Web
Application
[01.07.18 15:21:17:977 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]: JSP 1.1
Processor: init
[01.07.18 15:21:18:007 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
SimpleFileServlet: init
[01.07.18 15:21:18:037 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
InvokerServlet: init
[01.07.18 15:21:18:278 CDT] 362a76f8 ServletEngine A Loading Web Module: Samples Web
Application
[01.07.18 15:21:18:468 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]: JSP 1.1
Processor: init
[01.07.18 15:21:18:498 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
SimpleFileServlet: init
[01.07.18 15:21:18:518 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
InvokerServlet: init
[01.07.18 15:21:18:879 CDT] 362a76f8 ServletEngine A Loading Web Module: theme Web
Application
[01.07.18 15:21:18:979 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]: JSP 1.1
Processor: init
[01.07.18 15:21:19:039 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
SimpleFileServlet: init
[01.07.18 15:21:19:069 CDT] 362a76f8 WebGroup I SRVE0091I: [Servlet LOG]:
InvokerServlet: init
[01.07.18 15:21:19:359 CDT] 362a76f8 HttpTransport A Transport http is listening on port
9080
[01.07.18 15:21:23:455 CDT] 362a76f8 HttpTransport A Transport https is listening on port
9443
[01.07.18 15:21:23:475 CDT] 362a76f8 HttpTransport A Transport http is listening on port
9090
[01.07.18 15:21:23:485 CDT] 362a76f8 Server I WSVR0023I: Server Default Server open
for e-business

[William H. Jackson Jr.]

Thanks again for replying.

//william.jackson

=====================================================================================================================

[William H. Jackson Jr.]

Thanks again for replying.

//william.jackson

=====================================================================================================================

[David Artus]

I'm sorry, I meant the log from *after* you have restarted the
server *after* you installed the application. What I'm expecting
to see in the logs is some failure to start the EJBs perhaps because
a database is not working correctly.

As it's the weekend I may have that free 30 minutes to try this myself;
I'm not sure how our time zones overlap. If you do get a moment to
post the other logs that would be helpful.

[David Artus]

I have run the example. Must admit I didn't follow the instructions exactly.
I started with the supplied big3.ear and set up the jndi names and ejb
references directly in the ear rather than typing them in at install time.
I also had to specify a main-class for the client. This latter point I didn't
find expressed in the tutorial.

However, it does materially work.

[kamath]

"William H. Jackson Jr." <whja...@warpnotes.com> wrote in message news:<3B54A5DF...@warpnotes.com>...

kamath:
Am getting exavtly same error on webs 4.0 on linux

[kamath]

David Artus <art...@nospamuk.ibm.nospamcom> wrote in message news:<3B59EC02...@nospamuk.ibm.nospamcom>...

Kamath:
I get the same problem too. I did dump the name space and did find the entry
com/ibm/ejb/cb/samples/big3/tier2/ProcessClaimHome <mapped to>
com.ibm.ejb.samples.big3.tier2.EJSRemoteStatelessProcessClaimHome

where then is the problem ???

[kamath]

mska...@md3.vsnl.net.in (kamath) wrote in message news:<f6936ffb.01080...@posting.google.com>...

David,
I followed the instructions in nav_SysAdmGuide.pdf downloaded from the
infocentre and followed it exactly.In this write up the jndi(s) are
entered while assembling the app using the AAT. So when we run the
SEAppInstall.sh tool
the jndi's are already set and we just need to press enter. I saw only
one step in that tutorial which looks like an error. To run the client
the guide indicates use of SEAppInstall tool(only for UNIX !!). This
looks like an error and I changed this to use of launchClient.sh.

Can you tell me exactly what was it that you gave as an extra input
wrto the tutorial. Tr..
kamath

[m.marggraf]

Hi Kamath, David,
I also had this problem with following the instructions in
nav_SysAdmGuide.pdf under NT. I dumped the namespace with the
sun-browser. there i saw, that all names were registered right. but
the names of the samples are very short in comparision to big3-names.
ok - I changed the name in the sample to only ProcessClaimHome wihtout
the hole path in the beginning. with this change websphere found the
home interface.
but then came the next problem:

D:\big3>launchclient Big3.ear 25 localhost ProcessClaimHome

IBM WebSphere Application Server, Release 4.0
J2EE Application Client Tool, Version 1.0
Copyright IBM Corp., 1997-2001

WSCL0012I: Processing command line arguments.
WSCL0013I: Initializing the J2EE Application Client Environment.
WSCL0035I: Initialization of the J2EE Application Client Environment
has complet
ed.
WSCL0014I: Invoking the Application Client class Big3ClientApp

PROVIDER_URL string is : iiop://localhost:900
java.lang.ClassCastException: Unable to load class:
org.omg.stub.com.ibm.ejb.cb.
samples.big3.tier2._ProcessClaimHome_Stub
at com.ibm.rmi.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObjec
t.java:269)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:136)
at Big3ClientApp.getProcessClaimHome(Big3ClientApp.java:80)
at Big3ClientApp.main(Big3ClientApp.java:35)

at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.websphere.client.applicationclient.launchClient.createContain
erAndLaunchApp(launchClient.java:430)
at com.ibm.websphere.client.applicationclient.launchClient.main(launchCl
ient.java:288)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:63)

D:\big3>

for what reason the client searched for a class
"org.omg.stub.com.ibm.ejb.cb.samples.big3.tier2._ProcessClaimHome_Stub"
????

michael

[m.marggraf]

Hi Kamath, David,

i found out also this problem, where it would be possible that
it is only a windows-problem ...?

I stepped through the code and found out the following:
the client searched for
com.ibm.ejb.cb.samples.big3.tier2._ProcessClaimHome_Stub .
if the load of this class failed the client added "org.omg.stub" (in
Utility.class) .
if you follow the instructions the class
com.ibm.ejb.cb.samples.big3.tier2._ProcessClaimHome_Stub is located in
EJBBig3depl.jar and this jar-file is in Big3.ear .
but it seems, that java(client) is not able to find this jar-file in
the
ear-file. so I copied EJBBig3depl.jar to %WAS-ROOT%\lib\ext .
and then it worked.
question: is it neccessary to put the deployed-jar file in
classpath (or somewhere else where java will find it like lib/ext)?

michael

[m.marggraf]

hi Kamath, David,
this is the second try for this posting. i thing, that i solved the
problem:
during stepping the code i saw, that Utility.class added a
"org.omg.stub"
to the right class name
"com.ibm.ejb.cb.samples.big3.tier2._ProcessClaimHome_Stub" in the
case, that the class should not be found.
but the class was there, in the EJBBig3Depl.jar and this jar-file was
in the Big3.ear wich we started with launchclient.
it seemed that the client java should not be able to open the
EJBBig3Depl.jar in the Big3.ear . so I copied the EJBBig3Depl.jar to
lib/ext, one of the directories specified with -Dext.dirs in
launchclient. since this moment all is working fine...
question: is this a bug in java or should everyone add the ejb-jar to
the client classpath?

michael