[JBoss JIRA] (DROOLS-2458) [DMN Designer] Error while removing connected decision
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2458?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2458:
----------------------------------------
[~roger600] Yes makes sense (other than two number 1's in your comment.. but I'm being pedantic!)
> [DMN Designer] Error while removing connected decision
> ------------------------------------------------------
>
> Key: DROOLS-2458
> URL: https://issues.jboss.org/browse/DROOLS-2458
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Roger Martínez
> Priority: Critical
> Labels: Stunner
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-04-06 14-41-28.png, Screenshot from 2018-04-06 14-42-45.png
>
>
> If there are connected decisions, user is unable to delete them. Issue was found during JBPM-6777 review, however probably there is no relation.
> h2. Acceptance test
> Prepare DRG diagram with all combinations of connections, be sure all node types used, try to delete each node type in situation it is either source or target of connection.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2396) [DMN Designer] Cover dtable commands for non trivial index
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2396?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2396:
--------------------------------
Description:
Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*.
h3. Acceptance criteria
# AddInputClauseCommand (/)
# AddOutputClauseCommand (/)
# DeleteRuleCommand (/)
# DeleteInputClauseCommand (/)
# DeleteOutputClauseCommand (/)
was:
Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*.
h3. Acceptance criteria
# AddInputClauseCommand (/)
# AddOutputClauseCommand (/)
# DeleteRuleCommand (/)
# DeleteInputClauseCommand (/)
# DeleteOutputClauseCommand (?)
> [DMN Designer] Cover dtable commands for non trivial index
> ----------------------------------------------------------
>
> Key: DROOLS-2396
> URL: https://issues.jboss.org/browse/DROOLS-2396
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 7.8.0.Final
>
>
> Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*.
> h3. Acceptance criteria
> # AddInputClauseCommand (/)
> # AddOutputClauseCommand (/)
> # DeleteRuleCommand (/)
> # DeleteInputClauseCommand (/)
> # DeleteOutputClauseCommand (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-7860) Only import transactions lazily
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7860?page=com.atlassian.jira.plugin.... ]
Stuart Douglas updated WFLY-7860:
---------------------------------
Fix Version/s: 13.0.0.Beta1
> Only import transactions lazily
> -------------------------------
>
> Key: WFLY-7860
> URL: https://issues.jboss.org/browse/WFLY-7860
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 13.0.0.Beta1
>
>
> The EJB client/server protocol can perform many optimizations if a server can lazily import the transaction only if needed when an invocation arrives for processing.
> Unfortunately our CMTTxInterceptor infrastructure is built around the assumption that the transaction (if any) will resumed on the calling thread, which prevents the EJB transport protocol from reporting back that the transaction was not used.
> The CMTTxInterceptor and its subtypes must be modified to look for the transaction on the invocation object, rather than on the current thread. The local EJB invocation sources must suspend the transaction and install it on to the invocation context. CMTTxInterceptor would then assume that the current thread holds no transaction, resuming if necessary, instead of assuming that the current thread holds the inherited transaction and suspending if necessary.
> Once this is complete, org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor can be completely removed from the container.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10060) wsconsume script is not working on JDK9+
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10060?page=com.atlassian.jira.plugin... ]
Stuart Douglas commented on WFLY-10060:
---------------------------------------
I have merged the WF fix, however I have not closed this yet.
> wsconsume script is not working on JDK9+
> ----------------------------------------
>
> Key: WFLY-10060
> URL: https://issues.jboss.org/browse/WFLY-10060
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Web Services
> Affects Versions: 12.0.0.Final
> Reporter: Jan Blizňák
> Assignee: R Searls
> Priority: Blocker
> Attachments: mywsdl2java
>
>
> wsconsume script is not working on JDK9/10/11
> {code:java}
> [jbliznak@rh wildfly-13.0.0.Alpha1-SNAPSHOT]$ java -version
> java version "9.0.4"
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [jbliznak@rh wildfly-13.0.0.Alpha1-SNAPSHOT]$ bin/wsconsume.sh https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> Could not find log4j.properties or log4j.xml configuration, logging to console.
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector (jar:file:/tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/com/sun/xml/bind/main/jaxb-runtime-2.3.0.jar!/) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
> WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -compile -exsh false -d /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430 -verbose -classdir /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output -allowElementReferences https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> wsdl2java - Apache CXF 3.2.2
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:6: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebEndpoint;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:7: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebServiceClient;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:8: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebServiceFeature;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:9: error: package javax.xml.ws is not visible
> import javax.xml.ws.Service;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:3: error: package javax.jws is not visible
> import javax.jws.WebMethod;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:4: error: package javax.jws is not visible
> import javax.jws.WebParam;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:5: error: package javax.jws is not visible
> import javax.jws.WebResult;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:6: error: package javax.jws is not visible
> import javax.jws.WebService;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:7: error: package javax.jws.soap is not visible
> import javax.jws.soap.SOAPBinding;
> ^
> (package javax.jws.soap is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:72: error: cannot find symbol
> return super.getPort(EndpointInterfacePort, EndpointInterface.class);
> ^
> symbol: variable super
> location: class org.openuri._2004._04.helloworld.TestService
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:84: error: cannot find symbol
> return super.getPort(EndpointInterfacePort, EndpointInterface.class, features);
> ^
> symbol: variable super
> location: class org.openuri._2004._04.helloworld.TestService
> JBWS024002: Failed to invoke org.apache.cxf.tools.wsdlto.WSDLToJava
> org.apache.cxf.tools.common.ToolException: Failed to compile generated code
> at org.apache.cxf.impl//org.apache.cxf.tools.common.ClassUtils.compile(ClassUtils.java:125)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:303)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:412)
> at org.apache.cxf.impl//org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> at org.jboss.ws.jaxws-client//org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:313)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:298)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:108)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:96)
> at org.jboss.modules.Module.runMainMethod(Module.java:348)
> at org.jboss.modules.Module.run(Module.java:328)
> at org.jboss.modules.Main.main(Main.java:557)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-7860) Only import transactions lazily
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7860?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-7860.
----------------------------------
Assignee: David Lloyd
Resolution: Done
> Only import transactions lazily
> -------------------------------
>
> Key: WFLY-7860
> URL: https://issues.jboss.org/browse/WFLY-7860
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: David Lloyd
> Assignee: David Lloyd
>
> The EJB client/server protocol can perform many optimizations if a server can lazily import the transaction only if needed when an invocation arrives for processing.
> Unfortunately our CMTTxInterceptor infrastructure is built around the assumption that the transaction (if any) will resumed on the calling thread, which prevents the EJB transport protocol from reporting back that the transaction was not used.
> The CMTTxInterceptor and its subtypes must be modified to look for the transaction on the invocation object, rather than on the current thread. The local EJB invocation sources must suspend the transaction and install it on to the invocation context. CMTTxInterceptor would then assume that the current thread holds no transaction, resuming if necessary, instead of assuming that the current thread holds the inherited transaction and suspending if necessary.
> Once this is complete, org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor can be completely removed from the container.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2396) [DMN Designer] Cover dtable commands for non trivial index
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2396?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2396:
--------------------------------
Description:
Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*.
h3. Acceptance criteria
# AddInputClauseCommand (/)
# AddOutputClauseCommand (/)
# DeleteRuleCommand (/)
# DeleteInputClauseCommand (/)
# DeleteOutputClauseCommand (?)
was:
Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*.
h3. Acceptance criteria
# AddInputClauseCommand (/)
# AddOutputClauseCommand (/)
# DeleteRuleCommand (/)
# DeleteInputClauseCommand (?)
# DeleteOutputClauseCommand (?)
> [DMN Designer] Cover dtable commands for non trivial index
> ----------------------------------------------------------
>
> Key: DROOLS-2396
> URL: https://issues.jboss.org/browse/DROOLS-2396
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
>
> Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*.
> h3. Acceptance criteria
> # AddInputClauseCommand (/)
> # AddOutputClauseCommand (/)
> # DeleteRuleCommand (/)
> # DeleteInputClauseCommand (/)
> # DeleteOutputClauseCommand (?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10166) Xalan transformer creating invalid encoding for smiley
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-10166?page=com.atlassian.jira.plugin... ]
Chao Wang updated WFLY-10166:
-----------------------------
Summary: Xalan transformer creating invalid encoding for smiley (was: Upgrade Xerces so that DocumentBuilder can pase an emoji properly)
> Xalan transformer creating invalid encoding for smiley
> ------------------------------------------------------
>
> Key: WFLY-10166
> URL: https://issues.jboss.org/browse/WFLY-10166
> Project: WildFly
> Issue Type: Bug
> Components: XML Frameworks
> Affects Versions: 12.0.0.Final
> Reporter: Osamu Nagano
> Assignee: Jason Greene
> Attachments: testapp.zip, testappng.war
>
>
> An smiley face emoji, decimal code 😁, can be parsed properly by JDK's implementation (loaded by {{com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl}}) but failed with WildFly's implementation (xercesImpl-2.11.0.SP5.jar) which throws {{org.xml.sax.SAXParseException}}.
> {code}
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 84; Character reference "�" is an invalid XML character.
> at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:245)
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:298)
> at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
> at com.example.XMLTest.main(XMLTest.java:77)
> at com.example.XMLServlet.doRequest(XMLServlet.java:65)
> at com.example.XMLServlet.doGet(XMLServlet.java:38)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:67)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1526)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> This means a standalone Java application suddenly stops working on WildFly and need to be addressed. There is a workaround using files under {{META-INF/services}} and {{jboss-deployment-structure.xml}}. But the workaround is too mysterious for most of users. An out-of-the-box solution is expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBJCA-1373) MySQLValidConnectionChecker swallow a root cause of the exception
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1373?page=com.atlassian.jira.plugin... ]
Lin Gao moved JBEAP-14563 to JBJCA-1373:
----------------------------------------
Project: IronJacamar (was: JBoss Enterprise Application Platform)
Key: JBJCA-1373 (was: JBEAP-14563)
Workflow: classic default workflow (was: CDW with loose statuses v1)
Component/s: JDBC
(was: JCA)
Affects Version/s: (was: 7.1.0.GA)
Fix Version/s: (was: 7.1.3.GA)
> MySQLValidConnectionChecker swallow a root cause of the exception
> -----------------------------------------------------------------
>
> Key: JBJCA-1373
> URL: https://issues.jboss.org/browse/JBJCA-1373
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Reporter: Lin Gao
> Assignee: Petr Jurak
>
> When java.sql.SQLException is thrown, the root cause should be logged at the same time by MySQLValidConnectionChecker validation.
> ~~~
> WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (default task-1) IJ030027: Destroying connection that is not valid, due to the following exception: com.mysql.jdbc.JDBC4Connection@5d0ae267: java.sql.SQLException: Ping failed: java.lang.reflect.InvocationTargetException
> at org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker.isValidConnection(MySQLValidConnectionChecker.java:93)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:1272)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnectionFactory.getInvalidConnections(BaseWrapperManagedConnectionFactory.java:1085)
> ~~~
> However, the current code is :
> return new SQLException("Ping failed: " + e.toString());
> so this should be modified by:
> return new SQLException("Ping failed: " + e.toString(), e);
> and logged message with root cause.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months