Even if I just have the answer and decide to stick with 2.4 for
now, I'd at least like to know :o)
Thanks,
-nicole
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Tony, Sebastien, List,
At 09:10 on Mar 11, Tony Reix shook the earth with:
> Hi Nicole,
>
> Would it be possible for you to extract the code that produces the
> problem and provide a very small program we could use in our labs
> in order to reproduce the problem with our enviro
I see on the
screen, or what argument I pass to the JVM.
I added the command line argument:
-XX:+AllowUserSignalHandlers
which also did not help.
I will be constructing a basic application that just does the signal
handling similar to my application so I can use it to test.
Thanks,
-
No, I haven't tried the IBM JVM. That's a good idea.
At 12:13 on Mar 16, Tony Reix shook the earth with:
> Hi Nicole,
>
> { ...
> { I will be constructing a basic application that just does the signal
> { handling similar to my application so I can use it to test.
>
Hi Nicole,
>
> { ...
> { I will be constructing a basic application that just does the signal
> { handling similar to my application so I can use it to test.
>
> Seems your problem is not easy to understand ...
> Let us know when you have built such a basic application. At
ested works fine on a 2.4 kernel.
Attached is the test code that I am using to test the signals.
Feedback welcome... otherwise I am most likely going to test and switch to
the IBM 1.3.1-6 JRE.
Thanks!
-nicole
At 16:52 on Mar 17, nicole shook the earth with:
> The IBM JRE did not appear to c
Huang shook the earth with:
> Hi Nicole,
>
> I tested your code. It works fine on my machine with 2.6.4. I
> tested Sun JDK 1.3.1fcs, 1.3.1_10, 1.3.1_11, 1.4.2fcs, 1.4.2_03
> and 1.5beta. SignalTest is able to catch HUP, TERM, INT.
>
> That said, I'd like to point out
Not sure where else to post this, I don't know of a lot of java
communities that have at least *some* activity ;o)
This one comes from my husband, who is working on attempting to connect
RMI (with backconnects) over one single port due to firewall constraints.
With the increasing prevalence of des
I (accidentally) upgraded my glibc a little too far with debian and I ran
into this problem with the blackdown JDK, so I would say that is a yes. I
am using j2sdk1.3 1.3.1-1. I would have to look at the glibc version I
upgraded to (I eventually downgraded).
-nicole
At 21:40 on Nov 7, Joseph
Check
/usr/lib/j2se/version/ (e.g. /usr/lib/j2se/1.3/)
or
/usr/lib/j2se/ (e.g. /usr/lib/j2se1.3)
At 10:33 on Jan 12, kjhbh hjhjh combined all the right letters to say:
> Hi all, I have just installed Blackdowns packages by following the
> instructions at
> http://www.debian.org/doc/manuals/debi
10 matches
Mail list logo