Hi, Are you using Derby stored procedure with user defined types as parameter(s)?, if this is the case the jar version using from derby is older, From which application you called this procedure?

I faced this error with my Derby network server frequently.

You can keep same jar file in you application as well and derby while booting up will solve this problem.