Brandon, just an idea, are you sure you use 10.8.2.2 jars also on
client accessing this Derby network server? Once I switched everything
to 10.8.2.2 I stopped seeing the errors on IBM J9.
On Wed, Apr 4, 2012 at 8:57 PM, Brandon L. Duncan
brandonl.dun...@gmail.com wrote:
Hi all,
I am seeing
Peter, definitely using the 10.8.2.2 jars. The scenario, which I'm in the
process of parsing down to share on JIRA is a single shell script called
from qsh to start the network server, run ij, and finally shutdown the
network server. The same classpath is shared through all three java calls.
On
On Wed, Apr 4, 2012 at 12:43 PM, Brandon L. Duncan
brandonl.dun...@gmail.com wrote:
Peter, definitely using the 10.8.2.2 jars. The scenario, which I'm in the
process of parsing down to share on JIRA is a single shell script called
from qsh to start the network server, run ij, and finally
On 4/4/2012 12:43 PM, Brandon L. Duncan wrote:
Peter, definitely using the 10.8.2.2 jars. The scenario, which I'm in
the process of parsing down to share on JIRA is a single shell script
called from qsh to start the network server, run ij, and finally
shutdown the network server. The same
Brandon, I run 10.8.2.2 with J9:
$ java -version
java version 1.6.0
Java(TM) SE Runtime Environment (build pap3260sr9fp2-20110627_03(SR9 FP2))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc-32
jvmap3260sr9-20110624_85526 (JIT enabled, AOT enabled)
J9VM - 20110624_085526
JIT -
Thanks Peter and Myrna for the feedback. Myrna, those Wiki links were
helpful; I did not even know they existed. I'm going to get a J9
environment setup with 10.8.2.2 in the next day or two and see how that
goes.
Thank you both again,
Brandon
On Tue, Mar 20, 2012 at 3:47 AM, Peter Ondruška
I have seen the same problem and resolved by upgrading Derby to 10.8.
There must be something strange in J9 and Derby coexistence. This
happened very random.
On Mon, Mar 19, 2012 at 4:55 PM, Brandon L. Duncan
brandonl.dun...@gmail.com wrote:
I was wondering if anyone came across this error
Thanks Peter.
Do you remember if you upgraded to 10.8.2.2 or 10.8.1.2? We do have a test
environment with 10.8.1.2, and are seeing similar results. I do agree that
it seems to be a strange coexistence with Derby and J9. The IBM Classic JVM
doesn't seem to have this issue, although IBM seems to
On Mon, Mar 19, 2012 at 10:18 AM, Brandon L. Duncan
brandonl.dun...@gmail.com wrote:
Thanks Peter.
Do you remember if you upgraded to 10.8.2.2 or 10.8.1.2? We do have a test
environment with 10.8.1.2, and are seeing similar results. I do agree that
it seems to be a strange coexistence with
