«

I am on HP UNIX 11.2 which is 64 bit operating system. I am using JDK
1.5 and using Java's File i/o to write my trace information to a file.
I noticed that even though my program is running, it stopped writing
any more information once trace file became 2GB.

It cannot be HP UNIX limitation which is 64 bit, also file systems
have been set to allow files larger than 2GB. I am surprise that
java's i/o is 32 bit (yes java's version is most likely 32 bit).

On Fri, 16 Sep 2011 12:18:16 -0700 (PDT), zigzagdna
<> wrote, quoted or indirectly quoted someone who
said :

>It cannot be HP UNIX limitation which is 64 bit, also file systems
>have been set to allow files larger than 2GB. I am surprise that
>java's i/o is 32 bit (yes java's version is most likely 32 bit).

hmm. Java itself uses longs (64 bits) for file offsets. There is some
native code that java.io. uses to hook into the OS. It might be
designed for an older 32-bit HP API. Or it may be that partitions are
old, 32-bit even under the new 64-bit os. You may have to reformat
them to free up 64 bit power.

Try an experiment with C to see if it too has this limit on that
partition.

Consider that Java 1.5 has been declared obsolete for quite some time
now. JDK 1.7 is out. Try your code with 1.7 and see how it works.
--
Roedy Green Canadian Mind Products
http://mindprod.com
Your top priority should be fixing bugs. If you carry on development,
you are just creating more places you will have to search for them.

On Fri, 16 Sep 2011 12:18:16 -0700, zigzagdna wrote:

> I am on HP UNIX 11.2 which is 64 bit operating system. I am using JDK
> 1.5 and using Java's File i/o to write my trace information to a file. I
> noticed that even though my program is running, it stopped writing any
> more information once trace file became 2GB.
>
> It cannot be HP UNIX limitation which is 64 bit, also file systems have
> been set to allow files larger than 2GB. I am surprise that java's i/o
> is 32 bit (yes java's version is most likely 32 bit).

Is there a process limit in force? What does ulimit -a say ?

On 9/16/2011 5:28 PM, Roedy Green wrote:
> On Fri, 16 Sep 2011 12:18:16 -0700 (PDT), zigzagdna
> <> wrote, quoted or indirectly quoted someone who
> said :
>
>> It cannot be HP UNIX limitation which is 64 bit, also file systems
>> have been set to allow files larger than 2GB. I am surprise that
>> java's i/o is 32 bit (yes java's version is most likely 32 bit).
>
> hmm. Java itself uses longs (64 bits) for file offsets. There is some
> native code that java.io. uses to hook into the OS. It might be
> designed for an older 32-bit HP API. Or it may be that partitions are
> old, 32-bit even under the new 64-bit os. You may have to reformat
> them to free up 64 bit power.
>
> Try an experiment with C to see if it too has this limit on that
> partition.
>
> Consider that Java 1.5 has been declared obsolete for quite some time
> now. JDK 1.7 is out. Try your code with 1.7 and see how it works.

HP-UX != Windows

HP-UX Java 1.5 is not obsolete. I don't even think HP has announced an
EOL date. HP-UX Java 1.4.2 will be obsolete May 1st 2012.

http://bizsupport2.austin.hp.com/bc/.../c02690385.pdf

HP-UX Java 1.7 is not available yet.

Arne

On 19/09/2011 10:08 PM, Arne Vajhøj wrote:
> On 9/16/2011 5:28 PM, Roedy Green wrote:
>> Consider that Java 1.5 has been declared obsolete for quite some time
>> now. JDK 1.7 is out. Try your code with 1.7 and see how it works.
>
> HP-UX != Windows
>
> HP-UX Java 1.5 is not obsolete. I don't even think HP has announced an
> EOL date. HP-UX Java 1.4.2 will be obsolete May 1st 2012.

That just means that HP-UX is behind the times, not that Java 1.5 isn't.

On 9/21/2011 6:24 PM,
supercalifragilisticexpialadiamaticonormalizeringe limatisticantations wrote:
> On 19/09/2011 10:08 PM, Arne Vajhøj wrote:
>> On 9/16/2011 5:28 PM, Roedy Green wrote:
>>> Consider that Java 1.5 has been declared obsolete for quite some time
>>> now. JDK 1.7 is out. Try your code with 1.7 and see how it works.
>>
>> HP-UX != Windows
>>
>> HP-UX Java 1.5 is not obsolete. I don't even think HP has announced an
>> EOL date. HP-UX Java 1.4.2 will be obsolete May 1st 2012.
>
> That just means that HP-UX is behind the times, not that Java 1.5 isn't.

It means that Java 1.5 is not obsolete and fully supported by the
vendor on HP-UX.

Which is the relevant facts.

Arne

Arne Vajhøj wrote:
> supercalifragilisticexpialadiamaticonormalizeringe limatisticantations wrote:
>> Arne Vajhøj wrote:
>>> Roedy Green wrote:
>>>> Consider that Java 1.5 has been declared obsolete for quite some time
>>>> now. JDK 1.7 is out. Try your code with 1.7 and see how it works.
>>>
>>> HP-UX != Windows
>>>
>>> HP-UX Java 1.5 is not obsolete. I don't even think HP has announced an
>>> EOL date. HP-UX Java 1.4.2 will be obsolete May 1st 2012.
>>
>> That just means that HP-UX is behind the times, not that Java 1.5 isn't.
>
> It means that Java 1.5 is not obsolete and fully supported by the
> vendor on HP-UX.
>
> Which is the relevant facts.

Oracle has declared only their own version of Java 5 obsolete. Other vendors are free to do otherwise. Arne is, as usual, correct.

--
Lew

On 22/09/2011 9:13 AM, "Jane Doe", an obvious murphy sock, wrote:
NaN> Newsgroups: comp.lang.java.programmer

NaN> You ever find Derbysire (Seamus) being solid on Fact?

Who is "Derbyshire (Seamus)", murphy? There is nobody in this newsgroup
using that alias.

NaN> I will save you the keystrokes.

What does your classic erroneous presupposition that you're saving
people keystrokes by adding one more off-topic article for them to mark
read or hit control-K on have to do with Java, murphy?

NaN> No.

What does your denial have to do with Java, murphy?

"I had 'volunteered (years back) to support those who do endeavor
to provide free Free Usenet access, support those who offered
subscription based Free Usenet access, nothing more than
cooperation expected in return for what has been many
thousands of hours of work. I note most of those I joined with
are either deceased, severely disabled, or plain ole' MIA..
now it is my Time. ...

You just read my last. ...

For those who think they see me in future times I can only wish
you severe Tinnitus in your dreams. For those who know me
well (eMail, whatever) and see me, know I will be smiling also.
It is to you I say "adieu mein frenz and adios .. grazie' [hugs]
for all the Good Times! May you and yours always bear well
with all Life brings you".

/0ut"
--murphy

http://www.uffnet.com/kookkamp/goodbye.htm

And people wonder why I call them Famous Last Words.

P.S. You forgot to include a copy of your famous paranoid "Lits o' Haet"
in your post, murphy. Still suffering from memory problems, murphy?

On 21/09/2011 8:25 PM, Arne Vajhøj wrote:
> supercalifragilisticexpialadiamaticonormalizeringe limatisticantations
>> On 19/09/2011 10:08 PM, Arne Vajhøj wrote:
>>> HP-UX Java 1.4.2 will be obsolete May 1st 2012.
>>
>> That just means that HP-UX is behind the times, not that Java 1.5 isn't.
>
> It means that Java 1.5 is not obsolete and fully supported by the
> vendor on HP-UX.

Which just means that that vendor is behind the times. Of course, since
it's a proprietary Unix vendor, that's hardly surprising.

Arne Vajhøj <>, wrote:

>On 9/21/2011 6:24 PM,
>supercalifragilisticexpialadiamaticonormalizering elimatisticantations wrote:
>> On 19/09/2011 10:08 PM, Arne Vajhøj wrote:
>>> On 9/16/2011 5:28 PM, Roedy Green wrote:
>>>> Consider that Java 1.5 has been declared obsolete for quite some time
>>>> now. JDK 1.7 is out. Try your code with 1.7 and see how it works.
>>>
>>> HP-UX != Windows
>>>
>>> HP-UX Java 1.5 is not obsolete. I don't even think HP has announced an
>>> EOL date. HP-UX Java 1.4.2 will be obsolete May 1st 2012.
>>
>> That just means that HP-UX is behind the times, not that Java 1.5 isn't.
>
>It means that Java 1.5 is not obsolete and fully supported by the
>vendor on HP-UX.
>
>Which is the relevant facts.
>
>Arne

You ever find Derbysire (Seamus) being solid on Fact?
I will save you the keystrokes.

No.