Bug 1320042 - LinkageError when creating container
Summary: LinkageError when creating container
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Kie-Server
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER2
: 6.3.0
Assignee: Edson Tirelli
QA Contact: Karel Suta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 08:22 UTC by Karel Suta
Modified: 2020-03-27 20:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:10:50 UTC
Type: Bug


Attachments (Terms of Use)
stacktrace (12.47 KB, text/plain)
2016-03-22 08:22 UTC, Karel Suta
no flags Details

Description Karel Suta 2016-03-22 08:22:12 UTC
Created attachment 1138918 [details]
stacktrace

Description of problem:
When I create new container in Kie server on EAP then server log shows warning listed in attachment. This warning is shown just when creating first container and it doesn't seem to have any impact on functionality.


Version-Release number of selected component (if applicable):
Kie server 6.3.0ER1
EAP6.4


How reproducible:
Deploy Kie server on EAP. Create any container in Kie server.


Steps to Reproduce:
1.
2.
3.

Actual results:
Server log shows warning about LinkageError - ClassNotFoundException in nested exception.

Expected results:
Container deployment doesn't produce any warning.

Additional info:

Comment 2 Maciej Swiderski 2016-03-22 17:50:50 UTC
fixed by including guide-servlet dependency as otherwise EAP/wildfly is reporting LinkageError which is sort of expected though EAP does log it as warning

droolsjbpm-integration
master:
https://github.com/droolsjbpm/droolsjbpm-integration/commit/cfe07981252f45abba40997f894700b76952fbfb

6.4.x:
https://github.com/droolsjbpm/droolsjbpm-integration/commit/56776a5f8818f63c88ed612d16b4f3f1e5784569

Comment 3 Karel Suta 2016-03-24 09:30:41 UTC
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1318981

Comment 4 Karel Suta 2016-04-01 10:46:58 UTC
Verified in 6.3.0ER2


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