MySql reading BYTE datatype as String in Java

[Dan]

Hello.

I have recently tried upgrading the MySql connector for my servlet
from 2.0.4 to 3.0.9. I have found a minor limitation in 2.0.4 and was
hoping that 3.0.9 would fix it. However, now I am having a serious
problem with the latest connector. During login, it seems to me that
when validating the password, which is stored as a byte array in the
database, the MySql connector is passing back the password info as a
Byte. The exception I receive is the following:

Error while processing request: java.lang.IllegalArgumentException
at sun.reflect.UnsafeObjectFieldAccessorImpl.set(Unsa feObjectFieldAccessorImpl.java:63)
at java.lang.reflect.Field.set(Field.java:519)
at nurse.servlet.DBServer.get(DBServer.java:206)
at nurse.servlet.SQLTables.getEmployee(SQLTables.java :94)
at nurse.servlet.MainServlet.doPost(MainServlet.java: 112)
at javax.servlet.http.HttpServlet.service(HttpServlet .java)
at javax.servlet.http.HttpServlet.service(HttpServlet .java)
at org.apache.tomcat.facade.ServletHandler.doService( ServletHandler.java:574)
at org.apache.tomcat.core.Handler.invoke(Handler.java :322)
at org.apache.tomcat.core.Handler.service(Handler.jav a:235)
at org.apache.tomcat.facade.ServletHandler.service(Se rvletHandler.java:485)
at org.apache.tomcat.core.ContextManager.internalServ ice(ContextManager.java:917)
at org.apache.tomcat.core.ContextManager.service(Cont extManager.java:833)
at org.apache.tomcat.modules.server.Http10Interceptor .processConnection(Http10Interceptor.java:176)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(P oolTcpEndpoint.java:494)
at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:516)
at java.lang.Thread.run(Thread.java:536)

However, when I trace through the code, I find that it is crashing
when it reads the password field by mapping it as a String rather than
a BYTE.

It crashes in the following code:
Object val = recs.get(j);

....

if (val==null)
f.set(answers[i], null);

....

else if (val instanceof byte[]) {
Object o = null;
try {
ObjectInputStream in = new ObjectInputStream(new
ByteArrayInputStream((byte[])val));
o = in.readObject();
in.close();
}
catch (Exception e) {
if (!(answers[i] instanceof LogRecord))
throw e;
}
f.set(answers[i], o);
}
else
f.set(answers[i], val); <--- CRASHES HERE

The problem is that it should get caught in the else if just above the
last else. Now, the old mySql connector works fine, so I am curious
if something happened in the newer version. This is just a strange
problem. Does anyone have any ideas as to where to look to fix it?

Thanks in advance
Dan

[Lukas Bradley]

I need more Java code.

What are f and answers declared as? What does the f.set() method do?

I need to see the query, and the code where you are getting it out of the
database.

Lukas

"Dan" <zh******@yahoo.com> wrote in message
news:75**************************@posting.google.c om...

Hello.

I have recently tried upgrading the MySql connector for my servlet
from 2.0.4 to 3.0.9. I have found a minor limitation in 2.0.4 and was
hoping that 3.0.9 would fix it. However, now I am having a serious
problem with the latest connector. During login, it seems to me that
when validating the password, which is stored as a byte array in the
database, the MySql connector is passing back the password info as a
Byte. The exception I receive is the following:

Error while processing request: java.lang.IllegalArgumentException
at sun.reflect.UnsafeObjectFieldAccessorImpl.set(Unsa feObjectFieldAccessorImpl.
java:63) at java.lang.reflect.Field.set(Field.java:519)
at nurse.servlet.DBServer.get(DBServer.java:206)
at nurse.servlet.SQLTables.getEmployee(SQLTables.java :94)
at nurse.servlet.MainServlet.doPost(MainServlet.java: 112)
at javax.servlet.http.HttpServlet.service(HttpServlet .java)
at javax.servlet.http.HttpServlet.service(HttpServlet .java)
at org.apache.tomcat.facade.ServletHandler.doService( ServletHandler.java:574) at org.apache.tomcat.core.Handler.invoke(Handler.java :322)
at org.apache.tomcat.core.Handler.service(Handler.jav a:235)
at org.apache.tomcat.facade.ServletHandler.service(Se rvletHandler.java:485) at org.apache.tomcat.core.ContextManager.internalServ ice(ContextManager.java:91
7) at org.apache.tomcat.core.ContextManager.service(Cont extManager.java:833)
at org.apache.tomcat.modules.server.Http10Interceptor .processConnection(Http10I
nterceptor.java:176) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(P oolTcpEndpoint.java:494) at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.jav
a:516) at java.lang.Thread.run(Thread.java:536)

However, when I trace through the code, I find that it is crashing
when it reads the password field by mapping it as a String rather than
a BYTE.

It crashes in the following code:
Object val = recs.get(j);

...

if (val==null)
f.set(answers[i], null);

...

else if (val instanceof byte[]) {
Object o = null;
try {
ObjectInputStream in = new ObjectInputStream(new
ByteArrayInputStream((byte[])val));
o = in.readObject();
in.close();
}
catch (Exception e) {
if (!(answers[i] instanceof LogRecord))
throw e;
}
f.set(answers[i], o);
}
else
f.set(answers[i], val); <--- CRASHES HERE

The problem is that it should get caught in the else if just above the
last else. Now, the old mySql connector works fine, so I am curious
if something happened in the newer version. This is just a strange
problem. Does anyone have any ideas as to where to look to fix it?

Thanks in advance
Dan

[Lukas Bradley]

I need more Java code.

What are f and answers declared as? What does the f.set() method do?

I need to see the query, and the code where you are getting it out of the
database.

Lukas

"Dan" <zh******@yahoo.com> wrote in message
news:75**************************@posting.google.c om...

Hello.

I have recently tried upgrading the MySql connector for my servlet
from 2.0.4 to 3.0.9. I have found a minor limitation in 2.0.4 and was
hoping that 3.0.9 would fix it. However, now I am having a serious
problem with the latest connector. During login, it seems to me that
when validating the password, which is stored as a byte array in the
database, the MySql connector is passing back the password info as a
Byte. The exception I receive is the following:

Error while processing request: java.lang.IllegalArgumentException
at sun.reflect.UnsafeObjectFieldAccessorImpl.set(Unsa feObjectFieldAccessorImpl.
java:63) at java.lang.reflect.Field.set(Field.java:519)
at nurse.servlet.DBServer.get(DBServer.java:206)
at nurse.servlet.SQLTables.getEmployee(SQLTables.java :94)
at nurse.servlet.MainServlet.doPost(MainServlet.java: 112)
at javax.servlet.http.HttpServlet.service(HttpServlet .java)
at javax.servlet.http.HttpServlet.service(HttpServlet .java)
at org.apache.tomcat.facade.ServletHandler.doService( ServletHandler.java:574) at org.apache.tomcat.core.Handler.invoke(Handler.java :322)
at org.apache.tomcat.core.Handler.service(Handler.jav a:235)
at org.apache.tomcat.facade.ServletHandler.service(Se rvletHandler.java:485) at org.apache.tomcat.core.ContextManager.internalServ ice(ContextManager.java:91
7) at org.apache.tomcat.core.ContextManager.service(Cont extManager.java:833)
at org.apache.tomcat.modules.server.Http10Interceptor .processConnection(Http10I
nterceptor.java:176) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(P oolTcpEndpoint.java:494) at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.jav
a:516) at java.lang.Thread.run(Thread.java:536)

However, when I trace through the code, I find that it is crashing
when it reads the password field by mapping it as a String rather than
a BYTE.

It crashes in the following code:
Object val = recs.get(j);

...

if (val==null)
f.set(answers[i], null);

...

else if (val instanceof byte[]) {
Object o = null;
try {
ObjectInputStream in = new ObjectInputStream(new
ByteArrayInputStream((byte[])val));
o = in.readObject();
in.close();
}
catch (Exception e) {
if (!(answers[i] instanceof LogRecord))
throw e;
}
f.set(answers[i], o);
}
else
f.set(answers[i], val); <--- CRASHES HERE

The problem is that it should get caught in the else if just above the
last else. Now, the old mySql connector works fine, so I am curious
if something happened in the newer version. This is just a strange
problem. Does anyone have any ideas as to where to look to fix it?

Thanks in advance
Dan