[
https://issues.apache.org/jira/browse/DERBY-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898250#action_12898250
]
Rick Hillegas commented on DERBY-4773:
--------------------------------------
Each generated class file represents the query plan for an SQL statement
processed by Derby's SQL interpreter. Those generated classes extend
BaseActivation and have names which look like the class names you are seeing.
Normally, the generated classes are internal to Derby. However, you can cause
Derby to dump the class files to disk by setting the following flag when you
start the VM:
-Dderby.debug.true=DumpClassFile
I don't know any other way to force Derby to dump those class files to disk. If
you figure out how you coaxed Derby into dumping those class files, that will
help us debug this problem. Thanks.
> Derby Network service mode creates a lot of generated classes (extends
> BaseActivation).
> ---------------------------------------------------------------------------------------
>
> Key: DERBY-4773
> URL: https://issues.apache.org/jira/browse/DERBY-4773
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.6.1.0
> Environment: Suse Linux 11, Hive 5.0, Hadoop v.20.1
> Reporter: Soundararajan Velu
> Fix For: 10.6.1.0
>
>
> When I run Derby as a Network service, due to some reason it created about
> 1800 generated calss files (ac0a3c3082x012ax5c4fx64fcx00004650e8f2b.class,
> extends BaseActivation), I am unable to figure out the reason and now unable
> to reproduce the situation again. Has anyone faced this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
