Issue 11667

Summary: Java error when call made from OOo to libawt.so
Product: gsl Reporter: alex.thurgood
Component: codeAssignee: Frank Schönheit <frank.schoenheit>
Status: CLOSED IRREPRODUCIBLE QA Contact: issues@gsl <issues>
Severity: Trivial    
Priority: P3 CC: issues, issues
Version: 644   
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
JVM error log file none

Description alex.thurgood 2003-02-20 08:08:54 UTC 
I've noticed a log being thrown up by my JVM that is being caused by OOo644.
I've also noticed that I have similar logs for 1.0.1 too, that I hadn't noticed
before. As I don't understand what's going on, I can't explain the phenomenon.
It may have something to do with trying to access a MySQL database via JDBC, or
else trying to load an applet. These are the only Java things that I've tried
doing on OOo at all. Can anyone shed some light here ?

I've attached the error message log.

Alex
Comment 1 alex.thurgood 2003-02-20 08:09:46 UTC 
Created attachment 4804 [details]
JVM error log file
Comment 2 christof.pintaske 2003-02-20 12:02:52 UTC 
cp->fs: seems to be a jdbc issue. But is there really a problem ?
Comment 3 Frank Schönheit 2003-02-20 12:47:13 UTC 
> seems to be a jdbc issue. But is there really a problem ?

? I don't have the slightest idea what a "Signal 11" is, so I don't
have an idea what could cause it ...

Alex, from your description it's not really clear to me what's your
problem: Does OOo crash? Or is it just that you found this log telling
about an exception, without any negative effect?

> It may have something to do with trying to access a MySQL database
> via JDBC, or else trying to load an applet.

Can you try to determine which of both applies?

Can you tell us more about your environment? Which Linux distro? From
the log, I assume you have Java SDK 1.4.0_02 - is this correct? Do you
have the chance to try another version?
Comment 4 alex.thurgood 2003-02-20 13:17:03 UTC 
OK, now that we think it's a JDBC issue, the problem must be when I
try to create and access a mysql datasource via JDBC and the
mm.gjt.mysql.org driver. I've rechecked and recorrected the
mm.gjt.mysql.org.Driver JDBC driver parameters and it was these that
were throwing the exception and causing OOo to barf. Now I can connect
and see my tables, but I can't edit them. I guess this must be a
rights issue, so I'm changing this to a resolved. Sorry for all the
hassle I've caused everyone.
Comment 5 Frank Schönheit 2003-02-20 13:44:53 UTC 
closing WORKSFORME

Alex, you might want to look through http://dba.openoffice.org/FAQ/
for your MySQL privileges problem ...