• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

launchClient Naming Exceptions

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I just created my first Application Client Module in WSAD and got it to launch on my local server using the launch tool in WSAD. I wrote a script to launch it on our dev Unix box and the thing blows up giving me the error message below. I am utilizing the launchClient.sh script on the Unix machine to launch the appClient main class. My client app makes a couple calls to a web module in the same ear. I don't know if that would cause a problem (it didn't on my local machine), but thought I would mention it. I found a couple articles on IBM's website about this error and they mentioned starting the app server, having the correct bootstrap host, etc. I have checked and rechecked the suggestions regarding this error and can't see anything I am doing wrong.
I suspect that the error has something to do with the -CCclasspath entries I am using when launching the app. I ran into this error initially when I was working on launching it from my local server. I had to add a few jars to the runtime classpath:
jconn2.jar
classes12.zip
and some other mq jars
Anyone got any ideas on this one? Let me know if you need more detail.
Thanks
init(): javax.naming.CommunicationException: Caught CORBA.COMM_FAILURE when resolving initial reference=WsnNameService. Root exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No
 
Ranch Hand
Posts: 1551
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Have you tested your server with the dumpnamespace -host -port utility?
[ April 08, 2004: Message edited by: Rufus BugleWeed ]
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm with Rufus. From what's happening it looks like you're not even reaching the naming service on your server at all. Is there a possibility there's a firewall between the two machines? Failing that, I'm thinking it's a problem with specifying a wrong port.
Can you show us the entire contents of your script to use launchClient?
Kyle
 
Brian Sykes
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Kyle,
You are the man. It was indeed related to the port. Once I added the -CCBootstrapPort arg for the WAS instance of the app it ran fine. What is strange is we have some other scripts on this machine that launch without specifying the BootstrapPort. All in all I just had to keep throwing different options in to get it to work. The BootstrapPort ended up being the answer.
Thanks all.
Brian
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Glad you figured it out.
Kyle
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic