<div dir="ltr">I've just downloaded Wildfly 10.0.0.Final and it's still not working 100%.<div><br></div><div>1 - Fill all the fields, but put some wrong information like password, ip, whatever</div><div>2 - Get to the last screen where you can test the connection</div><div>3 - Test the connection (and fails)</div><div>4 - Go back, fix the connection info with right information</div><div>5 - Test connection and still fails (it's using old credentials)</div><div><br></div><div>Btw I was also able to see org.jboss.msc.service.DuplicateServiceException when I was testing, though I don't have clear steps how to reproduce.</div><div>I don't believe the problem is in the web UI.</div><div><br></div><div>Another minor issue is that when it fails to test, most of the times (if not always), regardless of the type of error I get in the server, in web UI I always get same generic error message:</div><div><br></div><div>
<p><span>19:41:01,345 ERROR [org.jboss.as.controller.management-operation] (management task-5) WFLYCTL0013: Operation ("test-connection-in-pool") failed - address: ([</span></p>
<p><span> ("subsystem" => "datasources"),</span></p>
<p><span> ("data-source" => "MySqlDS")</span></p>
<p><span>]) - failure description: "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid"</span></p><p><span><br></span></p><p>And when I went to look in the server log:<br><br></p><p><span>Caused by: java.sql.SQLInvalidAuthorizationSpecException: Could not connect: Access denied for user 'admin'@'192.168.0.107' (using password: YES)</span></p><p><span><span> </span>at org.mariadb.jdbc.internal.util.ExceptionMapper.get(ExceptionMapper.java:121)</span></p><p><span><span> </span>at org.mariadb.jdbc.internal.util.ExceptionMapper.throwException(ExceptionMapper.java:69)</span></p><p><span><span> </span>at org.mariadb.jdbc.Driver.connect(Driver.java:110)</span></p><p><span><span> </span>at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:319)</span></p><p>
</p><p><span><span> </span>... 31 more</span></p></div><div><br></div><div>It would be nice to propagete the correct error to the web UI.</div><div><br></div><div>Thanks</div><div><br></div><div><br></div><div><br></div><div><br></div>
<div class="gmail_extra"><br clear="all"><div><div class="gmail_signature">Renann Prado</div></div>
<br><div class="gmail_quote">On Fri, Jan 29, 2016 at 7:22 AM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
On 29/01/16 02:07, Renann Prado wrote:<br>
> I'm pretty sure I reported same issue as yours.<br>
><br>
> See:<br>
> <a href="https://issues.jboss.org/browse/WFLY-6015" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/WFLY-6015</a><br>
><br>
> Seems to be fixed, but it's not clear to me whether it will be part of<br>
> Wildfly 10 Final or not.<br>
<br>
</span>Apart from the occasional mistake in Jira if the status is 'Resolved'<br>
the 'Fix Version/s' field shows the release the fix is or will be<br>
included in.<br>
<span><br>
> However you can easily work around: just add the datasource with with<br>
> your driver && config and DO NOT CLICK IN TEST CONNECTION, then while<br>
> EDITING the datasource you can test the connection as many times as you<br>
> want. I did that in Wildfly 10.0.0.CR5 and it worked just fine.<br>
><br>
> I wouldn't call that a blocker as there are couple of ways to create a<br>
> datasource.<br>
><br>
> Hope it helps.<br>
><br>
> Renann Prado<br>
><br>
> On Thu, Jan 28, 2016 at 11:58 PM, Danilo Cominotti Marques<br>
</span><span>> <<a href="mailto:dcominottim@gmail.com" target="_blank">dcominottim@gmail.com</a> <mailto:<a href="mailto:dcominottim@gmail.com" target="_blank">dcominottim@gmail.com</a>>> wrote:<br>
><br>
> Hello there,<br>
><br>
> I have seen the e-mail that listed the following issues as blockers<br>
> for WildFly 10 Final,<br>
><br>
> 1. <a href="https://issues.jboss.org/browse/WFLY-5480" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/WFLY-5480</a><br>
> 2. <a href="https://issues.jboss.org/browse/WFCORE-1277" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/WFCORE-1277</a><br>
><br>
> but I would clearly add the following one to that list,<br>
><br>
> 3. <a href="https://issues.jboss.org/browse/HAL-1030" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/HAL-1030</a><br>
><br>
> because my company certainly wouldn't deploy WildFly 10 Final before<br>
> this issue is solved.<br>
><br>
> Any chances of having somebody look into it before the final release?<br>
><br>
> Thanks.<br>
><br>
> Danilo Cominotti Marques<br>
><br>
><br>
> _______________________________________________<br>
> wildfly-dev mailing list<br>
</span>> <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a> <mailto:<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
<div><div>><br>
><br>
><br>
><br>
> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div></div>