• 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Tim Cooke
  • Paul Clapham
  • Devaka Cooray
  • Bear Bibeault
  • Junilu Lacar
  • Knute Snortum
  • Liutauras Vilda
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Piet Souris
  • salvin francis
  • Carey Brown
  • Frits Walraven

Java InitialContext failure in 1.6

Posts: 1840
Eclipse IDE Ruby Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm working on a project that is using Java 1.6 and Weblogic 10.3. The application involves a swing client that connects to weblogic via weblogic's t3 protocol (and is launched via a JNLP link from a page in the web application). We have several instances of the application running on different servers. You can log into the web application from a machine on the same network domain and from a machine on a different network domain. However, the swing client can only connect to a server on the same network domain. We get a java.io.IOException: Write not supported error wrapped in a CORBA error.

I've managed to isolate this through using a dummy client that just tries to create an InitialContext; it fails when creating the InitialContext for servers not on the same domain as the client (either for a server running WEblogic 10.3 or for ones running the previous version of our application and Weblogic 8.1). However, the same dummy client, when run with java 1.4, has no problems connecting -- to either 10.3 or 8.1.

Does anybody have any idea what might be causing this? As I said, it works fine for machines running on the same network domain, but our business model has cases where the server is on a different domain from the client.
Posts: 17346
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Does the jndi.properties file need to have a different URL property value to connect from outside your network?

I am thinking this is where it is failing, and just a guess. Though that is the first place I would look.

Is there a multicast IP address that you need? Is the app server behind a Firewall that someone outside has to get through to reach the App Server?

I'd appreciate it if you pronounced my name correctly. Pinhead, with a silent "H". Petite ad:
Java file APIs (DOC, XLS, PDF, and many more)
    Bookmark Topic Watch Topic
  • New Topic