• 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

A communications error occurred when running GenPluginCfg.sh

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi i have installed
DB2, IBMHttp, Seurway, portal and app server and am having some problems!
when i run the GenPluginCfg.sh i get the following error.
[root@simshipdev bin]# ./GenPluginCfg.sh -adminNodeName simshipdev.cbs.ie
[5/12/03 16:10:06:938 CDT] 8b204bc AEGeneratePlu A SRVE0098I: Generating plug-in configuration for this node
[5/12/03 16:10:09:164 CDT] 8b204bc WsnInitCtxFac W NMSV0602E: Naming Service unavailable. A communications error occurred.
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
at com.ibm.CORBA.iiop.HTTPConnection.send(HTTPConnection.java:447)
at com.ibm.CORBA.iiop.HTTPConnection.locate(HTTPConnection.java:679)
at com.ibm.CORBA.iiop.GIOPImpl.locate(GIOPImpl.java:194)
at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1070)
at com.ibm.CORBA.iiop.InitialNamingClient.resolve(InitialNamingClient.java:372)
at com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:551)
at com.ibm.CORBA.iiop.ORB.resolve_initial_references_remote(ORB.java:1959)
at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:594)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:354)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:229)
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(WsnInitialContextFactory.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.websphere.plugincfg.tool.AEGeneratePluginCfg.generateCfg(AEGeneratePluginCfg.java:40)
at com.ibm.websphere.plugincfg.tool.AEGeneratePluginCfg.main(AEGeneratePluginCfg.java:112)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)

Have you any suggestions what is causing this?
Any help is much appreciated
Kevin
 
Ranch Hand
Posts: 399
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is the app server running (or the node manager, if using network deployment)?
 
Kevin Egan
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
I have a problem with my app server too, i cannot start it, it has a problem loading JDBC drivers - i followed troubleshooting guide but to no avail.
The exception on the GenPluginCfg.sh only occurred after adding fixpack 5 to WAS
i am new to websphere
 
John Dale
Ranch Hand
Posts: 399
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My limited experience is with WAS 5. I should have recognized that you are running WAS 4.x.
From the log fragment, it looks like the command is attempting to contact your JNDI server. I don't know where the name service runs in WAS 4. But wherever it runs, I think you need to get that part working before you try to generate the plug-in. (In WAS 5, it runs on the app server, or the node manager if using the Deployment Manager.)
From my limited experience, it probably makes sense to mess with the HTTP plugin only after you get the app server working. You can bypass the web server by using the addresses configured on the web server, i.e., 8080, instead of the address of the web server, e.g, 80.
As I understand it, WAS4 is dependent on the RDB for its its configuration information. If so, I wonder how far you can get if the JDBC is broken. Is anything working at all, aside from stuff independent of WAS, like the directory.
 
Kevin Egan
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the help
To top of a great day - db2 is not responding! - i think my best option is a complete clean down.
Thanks
for ur suggestions
 
John Dale
Ranch Hand
Posts: 399
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
 
Proudly marching to the beat of a different kettle of fish... while reading this tiny ad
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic