Skip to content
This repository has been archived by the owner on Mar 18, 2022. It is now read-only.

Inproper parsing of ORBTCPTimeouts #2

Closed
glassfishrobot opened this issue May 14, 2008 · 4 comments
Closed

Inproper parsing of ORBTCPTimeouts #2

glassfishrobot opened this issue May 14, 2008 · 4 comments

Comments

@glassfishrobot
Copy link
Contributor

When setting TCP timeouts per this article:
http://blogs.sun.com/ejcorba/entry/more_on_tcp_timeouts_in

By setting the setting the System property:
-Dcom.sun.corba.ee.transport.ORBTCPTimeouts=500:30000:20

Glassfish ORB throws an exception saying that the timeouts need to "3 positive
decimal integers separated by :"

I traced this exception down to line #61 in TcpTimeoutsImpl
(http://mercurial2.foundry.sun.com/corba/corba-gfv2-master/file/0fc818f2f9e5/src/share/classes/com/sun/corba/se/impl/transport/TcpTimeoutsImpl.java)

The conditional states:
if ((data.length <= 3) || (data.length > 4))

I think the '(data.length <= 3)' should be '(data.length < 3)' to allow for 3 or
4 arguments.

Environment

Operating System: All
Platform: All

@glassfishrobot
Copy link
Contributor Author

Reported by heartsjava

@glassfishrobot
Copy link
Contributor Author

kcavanaugh said:
I have already fixed this in the GlassFish v3 CORBA version.
We'll be integrating that ORB into GFv3 probably in the next
month or two.

@glassfishrobot
Copy link
Contributor Author

This issue was imported from java.net JIRA GLASSFISH_CORBA-2

@glassfishrobot
Copy link
Contributor Author

Closing this as this issue is migrated to eclipse-ee4j/orb#2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants