Bug 1314084 - protostream.javassist.NotFoundException when using ProtoSchemabuilder to register class
Summary: protostream.javassist.NotFoundException when using ProtoSchemabuilder to regi...
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ER1
: 6.6.1
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1309749 1345913 1312196 1354504
TreeView+ depends on / blocked
 
Reported: 2016-03-02 21:23 UTC by Van Halbert
Modified: 2020-10-20 21:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1345913 (view as bug list)
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Comment 13 Anna Manukyan 2016-08-10 11:55:33 UTC
Hi,

I have wrote a reproducer for this bug, but it didn't reproduce the issue. 

Wanted to clarify the steps that you did and got this failure:

1. Ran the jboss-datagrid-server-6.6.0.GA with standalone configuration;
2. Initialized your pojo with ProtoSchemaBuilder with client? 

Thanks in advance,
Anna.

Comment 14 Van Halbert 2016-08-10 12:17:48 UTC
This issue is when configuring JDV to connect to a JDG remote cache using Hot Rod EAP client modules.    As indicated in the initial comment #description, ProtoSchemaBuilder is called in the infinispan resource-adapter.  Its here that the attached exception is seen.    I've verified the initial patched resolved the issue, but haven't tried the latest official patch.

Comment 15 Anna Manukyan 2016-08-11 09:37:37 UTC
Hi,

thanks a lot for info Van. 

I was able to reproduce the issue with JDV JDG related quickstarts. 

The issue specified in this bug is fixed with ER1, but another issue appears which is described in https://bugzilla.redhat.com/show_bug.cgi?id=1364916 .

I have applied the fix done for https://bugzilla.redhat.com/show_bug.cgi?id=1364916 and after it the ProtoSchemaBuilder works and the queries are executed properly. 

So this bug will be fixed completely in ER2 with https://bugzilla.redhat.com/show_bug.cgi?id=1364916 one. 

Best regards,
Anna.


Note You need to log in before you can comment on or make changes to this bug.