Anonymous_User Absent Member.
Absent Member.
264 views

JDBC driver to MySQL hit Connection Timedout


Hi all,

Is there anyone hitting the same error in JDBC driver? People mentioned
to updated the 3rd party jar file and I did so. But the error still
persist.
Anyone can advise? My wait_timeout global variable in MySQL is setting
to 28800.


<nds dtdversion="2.0" ndsversion="8.x" xmlns:jdbc="urn:dirxml:jdbc">
<source>
<product build="20120601_0445" instance="AMBG-IDV_TO_IPF-UPP"
version="3.5.9">DirXML Driver for JDBC</product>
<contact>Novell, Inc.</contact>
</source>
<output>
<status
event-id="DVMPLX015#20150313021613#1#1:d3a628ef-60ce-4001-d89a-ef28a6d3ce60#0"
level="retry" type="app-connection">
<description>Unable to add object. Unable to insert row into
table/view 'ipfdb.sync_upp'. There is a connectivity-related
problem.</description>

<object-dn>O=AMBG\OU=AMB40000015330000000000\OU=EMPLOYEE\CN=10006717</object-dn>
<jdbc:exception
jdbc:class="com.mysql.jdbc.exceptions.jdbc4.CommunicationsException"
jdbc:error-code="0" jdbc:sql-state="08S01">
<jdbc:message>The last packet successfully received from the
server was 44,049,695 milliseconds ago. The last packet sent
successfully to the server was 44,049,696 milliseconds ago. is longer
than the server configured value of 'wait_timeout'. You should consider
either expiring and/or testing connection validity before use in your
application, increasing the server configured values for client
timeouts, or using the Connector/J connection property
'autoReconnect=true' to avoid this problem.</jdbc:message>
</jdbc:exception>
<operation-data>
<slot>ambgADAMBANKGROUP01</slot>

<dn>\AMBG-IDV\AMBG\AMB40000015330000000000\EMPLOYEE\10006717</dn>
<ops>add</ops>
</operation-data>
</status>
</output>
</nds>


--
kyin_ying
------------------------------------------------------------------------
kyin_ying's Profile: https://forums.netiq.com/member.php?userid=6787
View this thread: https://forums.netiq.com/showthread.php?t=53132

Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: JDBC driver to MySQL hit Connection Timedout

Perhaps post the driver startup trace from the Remote Loader (RL) side to
see if anything in that mentions this timeout.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: JDBC driver to MySQL hit Connection Timedout


ab;255402 Wrote:
> Perhaps post the driver startup trace from the Remote Loader (RL) side
> to
> see if anything in that mentions this timeout.
>
> --
> Good luck.
>
> If you find this post helpful and are logged into the web interface,
> show your appreciation and click on the star below...



Hi ab,

Driver connect directly to the database mentioned. No remote loader in
between.

Thanks.


--
kyin_ying
------------------------------------------------------------------------
kyin_ying's Profile: https://forums.netiq.com/member.php?userid=6787
View this thread: https://forums.netiq.com/showthread.php?t=53132

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: JDBC driver to MySQL hit Connection Timedout

You should always use a RL when possible, particularly when loading
third-party code as the JDBC shim does, but if you choose to do otherwise
it may still help to have the startup trace.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: JDBC driver to MySQL hit Connection Timedout

On 3/16/2015 10:04 PM, kyin ying wrote:
>
> Hi all,
>
> Is there anyone hitting the same error in JDBC driver? People mentioned
> to updated the 3rd party jar file and I did so. But the error still
> persist.
> Anyone can advise? My wait_timeout global variable in MySQL is setting
> to 28800.
>
>
> <nds dtdversion="2.0" ndsversion="8.x" xmlns:jdbc="urn:dirxml:jdbc">
> <source>
> <product build="20120601_0445" instance="AMBG-IDV_TO_IPF-UPP"
> version="3.5.9">DirXML Driver for JDBC</product>
> <contact>Novell, Inc.</contact>
> </source>
> <output>
> <status
> event-id="DVMPLX015#20150313021613#1#1:d3a628ef-60ce-4001-d89a-ef28a6d3ce60#0"
> level="retry" type="app-connection">
> <description>Unable to add object. Unable to insert row into
> table/view 'ipfdb.sync_upp'. There is a connectivity-related
> problem.</description>
>
> <object-dn>O=AMBG\OU=AMB40000015330000000000\OU=EMPLOYEE\CN=10006717</object-dn>
> <jdbc:exception
> jdbc:class="com.mysql.jdbc.exceptions.jdbc4.CommunicationsException"
> jdbc:error-code="0" jdbc:sql-state="08S01">
> <jdbc:message>The last packet successfully received from the
> server was 44,049,695 milliseconds ago. The last packet sent
> successfully to the server was 44,049,696 milliseconds ago. is longer
> than the server configured value of 'wait_timeout'. You should consider
> either expiring and/or testing connection validity before use in your
> application, increasing the server configured values for client
> timeouts, or using the Connector/J connection property
> 'autoReconnect=true' to avoid this problem.</jdbc:message>
> </jdbc:exception>
> <operation-data>
> <slot>ambgADAMBANKGROUP01</slot>
>
> <dn>\AMBG-IDV\AMBG\AMB40000015330000000000\EMPLOYEE\10006717</dn>
> <ops>add</ops>
> </operation-data>
> </status>
> </output>
> </nds>
>
>


The solution is in the error. Try setting the autoReconnect to true in the connection parameters.
You could also set the timeout to ensure it is defaulting to zero. Those settings can be found here:
http://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html


--
-----------------------------------------------------------------------
Will Schneider
Knowledge Partner http://forums.netiq.com

If you find this post helpful, please click on the star below.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.