[JBoss JIRA] (WFLY-11407) TCCL is not set to datasource module
by Bartosz Spyrko-Śmietanko (Jira)
[ https://issues.jboss.org/browse/WFLY-11407?page=com.atlassian.jira.plugin... ]
Bartosz Spyrko-Śmietanko reassigned WFLY-11407:
-----------------------------------------------
Assignee: Bartosz Spyrko-Śmietanko (was: Stefano Maestri)
> TCCL is not set to datasource module
> ------------------------------------
>
> Key: WFLY-11407
> URL: https://issues.jboss.org/browse/WFLY-11407
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 13.0.0.Final
> Reporter: Bartosz Spyrko-Śmietanko
> Assignee: Bartosz Spyrko-Śmietanko
> Priority: Major
>
> TCCL is not set to datasource module
> User has a datasource that uses ORB classes and is getting a ClassNotFound.
> If a 3rd party JDBC driver implementation is using e. g. CORBA, the class loader is not set and thus the CORBA classes got loaded from the 'org.jboss.as.connector' modules class loader.
> So the root cause is the Thread Context ClassLoader (TCCL) is not set to the classloader/module of the datasource driver module. The particular datasource driver is making using of ORB.init which is a JDK class that looks on the TCCL and other places to load the class specified in ORB.init, but JCA when running has not set the TCCL thus the classes cannot be found.
> Having the TCCL set to the application is how JEE handles related situations to load application classes, so it would make sense that when JCA is running the datasource that it would have the TCCL set to the module of the datasource or a delegate class loader that sees both the datasource module and any other class loader that JCA might need, JBossWS does something similar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3352) [DMN Designer] Some associations don't appear in third-party editors
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3352?page=com.atlassian.jira.plugi... ]
Michael Anstis resolved DROOLS-3352.
------------------------------------
Fix Version/s: 7.14.0.Final
Resolution: Done
> [DMN Designer] Some associations don't appear in third-party editors
> --------------------------------------------------------------------
>
> Key: DROOLS-3352
> URL: https://issues.jboss.org/browse/DROOLS-3352
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Fix For: 7.14.0.Final
>
> Attachments: thirdparty.png, wbdmn-debug-comments.dmn, wbdmn-fresh-ok.dmn, wbdmn.dmn, wbdmneditor.png
>
>
> This file was created in the Workbench DMN Editor:
> !wbdmneditor.png|thumbnail!
> (here's the DMN file: [^wbdmn.dmn])
> Then, it was imported in a third-party editor:
> !thirdparty.png|thumbnail!
> Notice that the association with the text notation cannot be seen.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3352) [DMN Designer] Some associations don't appear in third-party editors
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3352?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3352:
-----------------------------------
Affects Version/s: 7.13.0.Final
(was: 7.15.0.Final)
> [DMN Designer] Some associations don't appear in third-party editors
> --------------------------------------------------------------------
>
> Key: DROOLS-3352
> URL: https://issues.jboss.org/browse/DROOLS-3352
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Fix For: 7.14.0.Final
>
> Attachments: thirdparty.png, wbdmn-debug-comments.dmn, wbdmn-fresh-ok.dmn, wbdmn.dmn, wbdmneditor.png
>
>
> This file was created in the Workbench DMN Editor:
> !wbdmneditor.png|thumbnail!
> (here's the DMN file: [^wbdmn.dmn])
> Then, it was imported in a third-party editor:
> !thirdparty.png|thumbnail!
> Notice that the association with the text notation cannot be seen.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-3502) Fix debug options in test-runner
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFCORE-3502?page=com.atlassian.jira.plugi... ]
Marek Kopecký reassigned WFCORE-3502:
-------------------------------------
Assignee: (was: Marek Kopecký)
> Fix debug options in test-runner
> --------------------------------
>
> Key: WFCORE-3502
> URL: https://issues.jboss.org/browse/WFCORE-3502
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 4.0.0.Alpha5
> Reporter: Marek Kopecký
> Priority: Major
>
> Test-runner doesn't handle debug options correctly.
> If jdpa profile is used, surefire jvm uses this JVM attribute: {{-agentlib:jdwp=transport=dt_socket,address=$\{as.debug.port\},server=y,suspend=y}}.
> The same attribute is passed to started server. But server debugging should be set by {{wildfly.debug}} and {{wildfly.debug.port}} java properties. So if user wants to debug surefire with 8787 port and server with 8786 port, user uses jdpa profile, {{wildfly.debug}} property and {{wildfly.debug.port}} property and test fails:
> {{mvn test -DfailIfNoTests=false -DtestLogToFile=false -Dtest=CdTestCase -Djpda -Dwildfly.debug=true -Dwildfly.debug.port=8786}}
> {noformat}
> ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options.
> Error occurred during initialization of VM
> agent library failed to init: jdwp
> Running null
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months