- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Distributed NetBeans 7.0 connection problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2013 06:38 AM
01-30-2013 06:38 AM
We've been using IDESERVER V6.52 for some time. Environmental information:
$ tcpip show version
HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.6 - ECO 5
on an HP rx2600 (1.50GHz/6.0MB) running OpenVMS V8.3-1H1
$ java -version
java version "1.6.0"
Java(TM) SE Runtime Environment "1.6.0-4"
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
This setup runs nicely.
On another machine I installed the recently released IDESERVER 7.0. Environment:
$ tcpip show version
HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 3
on an HP rx2660 (1.59GHz/12.0MB) running OpenVMS V8.3-1H1
$ java -version
java version "1.6.0"
Java(TM) SE Runtime Environment "1.6.0-4"
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
VMS on both machines is patched up to VMS831H1_UPDATE v11.
On the second machine the IDE$SERVER wouldn't start, logging in IDE$SERVER.LOG
Launching Distributed IDE Server on RMI port 1099
Error occurred during initialization of VM
Could not reserve enough space for object heap
We remedied this by upping the Pgflquo von 1500000 to 2000000 in both the IDE$SERVER account and the IDE$IDESTARTUP.COM file.
Now with the IDE$SERVER and IDE$RMIREG processes running, a NetBeans client hangs while connecting to the server, and the connection between the two server processes seems to be broke, too. The log has:
Launching Distributed IDE Server on RMI port 1099
2013/01/29 13:28:40 PM CET:ServerStarter starting... with RMI port(1099)
2013/01/29 13:28:45 PM CET:DistNBServerSocketFactory::createSocket:#1
2013/01/29 13:28:45 PM CET:DistNBServerSocketFactory::createSocket:#2
2013/01/29 13:28:46 PM CET:DistNBServerSocketFactory::createSocket:#3
2013/01/29 13:28:46 PM CET:Binding to DistNBRemoteLoginServer
2013/01/29 13:48:46 PM CET:DistNBRemoteLoginServer bound in registry
Notice the 20 minutes between "binding" and "bound". Looking at the source, we think we traced this to a 1 minute timeout while trying 20 times to connect to the RMI server process.
Has anyone experienced (or even better, remedied) this situation?
Thands in advance,
Martin
Solved! Go to Solution.
- Tags:
- Java
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2013 02:14 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2013 03:13 AM
02-01-2013 03:13 AM
Re: Distributed NetBeans 7.0 connection problem
>It seems that Java 1.6-4 has problems with PKCS#12...
Is my understanding correct that this is a Java problem and not a Java on OpenVMS problem?
Update 4 is a rather old update for Java 6. Do you know whether this is fixed in a more recent Java update? The current update for Java 6 seems to be 38. However, with having only update 4 for OpenVMS (and without known plans for Java 7, which may have a fix as well) this seems to turn into a Java on OpenVMS problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2013 05:42 AM
02-01-2013 05:42 AM
Re: Distributed NetBeans 7.0 connection problem
> Is my understanding correct that this is a Java problem and not a Java on OpenVMS problem?
Sorry if I have been unclear. The problem lies in the VMS kit JAVA60 V1.6-4, and was remedied by going back to JAVA60 V1.6-3_P1
The machine that NetBeans and the DistNB plugin runs on is a Mac with OS X 10.8.2 and Java 1.6.0_31 (I do have 1.7.0_11, too. But I thought it would be better if the Java client and server versions matched).
cu,
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2013 06:30 AM
02-01-2013 06:30 AM
Re: Distributed NetBeans 7.0 connection problem
> Update 4 is a rather old update for Java 6.
The page at http://h18012.www1.hp.com/java/download/ivms/1.6.0/index.html says, "The JDK 6.0-4 kit implements the Java SE 6.0 (a.k.a. 1.6.0), and is based on Oracle's Java™ Standard Edition 6.0_37 Solaris Reference Release." It looks like 6.0_38 is the latest release for other platforms and they've been coming out with new releases every few days recently so the OpenVMS release really isn't far behind for once. Whey they can't use the same version numbers everybody else uses is different question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2013 03:28 AM
02-02-2013 03:28 AM
Re: Distributed NetBeans 7.0 connection problem
Hmm, I should have known better. Yes, -4 is not Update 4. On the other hand, it's not obvious what a "6.0_37 Solaris Reference Release" is. Given that 1.6-4 was released after Java SE 6 Update 37, which was released in October 2012, these 37s are very likely the same. Obviously, using different version numbers creates confusion.
... and the current Java SE 6 Update is 39, release on 2013-02-01 (50 security fixes).