• 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

Websphere Application Server V6.1 connection problem with DB2 V8.1

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hii everybody,

i have installed
* Websphere Application Server V6.1 on Linux Red Hat V4
* DB2 V8.1 on other machine with Linux Red Hat V5

I have deployed one application on the WAS. I want to connect WAS with DB2.

When i try to connect i get the following error:

La connexion test pour la source de donn�es Veratone Data Source sur le serveur server1 au noeud bpa-srv-05Node01 a �chou� avec l'exception suivante : java.lang.Exception: java.sql.SQLException: java.net.NoRouteToHostException : Error opening socket to server bpa-srv-06/192.168.4.245 on port 50000 with message : Aucun chemin d'acc�s pour atteindre l'h�te cible DB2ConnectionCorrelator: nullDSRA0010E: Etat SQL = null, Code d'erreur = -4 499. Consultez les journaux JVM pour obtenir plus de d�tails.

Seems like network problem but i am able to ping/telnet the other machine (DB2) from WAS machine.
can anyone help me out from this .
thanks for any help or hint

with regards

mayur
 
Ranch Hand
Posts: 3389
Mac MySQL Database Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As you say you are able to ping from your WAS machine to DB2,i think it must be with the IP Address Vs DNS name conflict.

I also really don't know, but sometimes trying out with the IP Address instead of the hostname works! Can you please try this option?

Also, pinging is different from connecting to an application which is running on a specific port (in this case DB2 which listens on port# 50000).

Can you also please check in the DB2 machine whether the 'Remote access' (accessing from remote machine) is enabled in the DB2 Server Configuration?
 
mayur shah
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
thanks raghavan but i have sorted it out.

The problem was related to network configuration ie Firewall related.

anyways thanks

mayur
 
reply
    Bookmark Topic Watch Topic
  • New Topic