📄 releasenotes.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<HEAD>
<TITLE>
SAP Java Connector 3.0 Release notes
</TITLE>
<LINK REL ="stylesheet" TYPE="text/css" HREF="./sap.css" TITLE="Style">
<SCRIPT type="text/javascript">
function windowTitle()
{
parent.document.title="SAP Java Connector 3.0 Configuration and Requirements";
}
</SCRIPT>
<NOSCRIPT>
</NOSCRIPT>
</HEAD>
<BODY BGCOLOR="white" onload="windowTitle();">
<!-- ========= START OF TOP NAVBAR ======= -->
<A NAME="navbar_top"><!-- --></A>
<A HREF="#skip-navbar_top" title="Skip navigation links"></A>
<TABLE BORDER="0" WIDTH="800" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
<TR>
<TD COLSPAN=2 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_top_firstrow"><!-- --></A>
<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
<TR ALIGN="center" VALIGN="top">
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="intro.html"><FONT CLASS="NavBarFont1"><B>Home</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="installation.html"><FONT CLASS="NavBarFont1"><B>Installation</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="useful.html"><FONT CLASS="NavBarFont1"><B>Configuration</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="index.html" target="_blank"><FONT CLASS="NavBarFont1"><B>API Documentation</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="examples.html"><FONT CLASS="NavBarFont1"><B>Examples</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1Rev"> <FONT CLASS="NavBarFont1Rev"><B>Release Notes</B></FONT> </TD>
</TR>
</TABLE>
</TD>
</TR>
<TR>
<TD COLSPAN=2 BGCOLOR="white" CLASS="NavBarCell2"> </TD>
</TR>
<TR><TD>
<HR>
<CENTER>
<H1>SAP Java Connector 3.0</H1>
</CENTER>
</TD>
</TR>
<tr><td> </td></tr>
<tr><td> </td></tr>
<tr><td><FONT SIZE="+1"><B>Release notes 3.0.2</B></FONT></td></tr>
<tr><td> </td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>New APIs</b></td></tr>
<tr><td>
New APIs are available for general use:
<code>
<ul>
<li>JCoCustomDestination.setTrace()
<li>JCoCustomDestination.setCodepage()
<li>JCoAttributes.getOwnBytesPerChar()
<li>JCoAttributes.getPartnerBytesPerChar()
<li>Environment.isDestinationDataProviderRegistered()
<li>Environment.isServerDataProviderRegistered()
<li>Environment.isSessionReferenceProviderRegistered()
<li>Environment.isClientPassportManagerRegistered()
<li>Environment.isServerPassportManagerRegistered()
</ul>
</code>
See API Documentation for details.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for hanging <code>JCoServer</code> if connections were set to stateful</b></td></tr>
<tr><td>
See also note <a href="http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1298438">1298438</a>.
When setting its connections to stateful, a <code>JCoServer</code> could hang completely when the gateway on which the server has been registered is
sending a ping to the server connection because the ABAP client has not been sending requests for a while. The JCoServer connection then
ends up in a call stack for server threads in a thread dump that looks similar to the following one:
<pre>
"sap.rfc.Listener SAPBC 10.20.3.20" cpu=136953.28 [reset 136953.28] ms allocated=30367383456 B (28.28 GB) [reset 30367383456 B (28.28 GB)] prio=6 tid=0x0000000015328b50 nid=0x1960 runnable [0x000000001922f000..0x000000001922f7d0]
java.lang.Thread.State: RUNNABLE
at com.sap.conn.rfc.driver.CpicDriver.nativeCpic_coxread([BI[B[I)I(Native Method)
at com.sap.conn.rfc.driver.CpicDriver.cpic_coxread(I[B[I)I(CpicDriver.java:692)
at com.sap.conn.rfc.driver.RfcTypeRegisterCpic.listen([BI[II)I(RfcTypeRegisterCpic.java:70)
- locked <0x000000018b411e68> (a com.sap.conn.rfc.driver.RfcTypeRegisterCpic)
at com.sap.conn.rfc.engine.RfcIoOpenCntl.ab_rfclisten(I)I(RfcIoOpenCntl.java:1293)
at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcListen(I)I(RfcIoOpenCntl.java:2194)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(Lcom/sap/conn/jco/rt/ServerWorker;)V(MiddlewareJavaRfc.java:2060)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch()V(DefaultServerWorker.java:259)
at com.sap.conn.jco.rt.DefaultServerWorker.loop()V(DefaultServerWorker.java:321)
at com.sap.conn.jco.rt.DefaultServerWorker.run()V(DefaultServerWorker.java:220)
at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run()V(TimeWrappingProvider.java:40)
at com.wm.pkg.sap.rfc.ListenerThread.run()V(ListenerThread.java:70)
- locked <0x000000017757a778> (a java.lang.Thread for sap.rfc.Listener BCSAPPRD 172.27.1.23)
</pre>
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix in treatment of one-digit BCD value</b></td></tr>
<tr><td>
BCD fields were filled incorrectly if a one-digit value was set (e.g. 4 or 7). The resulting value was always 0 (or 0.0 - with n 0 after the dot if the number of decimals is n in the metadata definition).
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for exception group in case of wrong credentials</b></td></tr>
<tr><td>
Error group <code>JCO_ERROR_CANCELLED</code> was used instead of <code>JCO_ERROR_LOGON_FAILURE</code>, moreover the error message was misleading.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfixes in session context handling</b></td></tr>
<tr><td>
<ul>
<li>It was possible that the context that timed out was not removed from the list of existing contexts
by the session timeout checker. This could create unnecessary checks for sessions that have already
been cleaned up.</li>
<li>Contexts that have been initiated by a stateful JCo server were not removed immediately after the connection
had been closed by the ABAP client</li>
</ul>
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for clear-text password in trace</b></td></tr>
<tr><td>
The trace file of could contain a trace entry, in which you find the string
'jco.destination.repository.passwd=' followed by the password for the
repository user, i.e. the user with which metadata information is looked
up in the SAP system.
See also security note <a href="http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1312880">1312880</a>
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for stateful <code>JCoServer</code> connections</b></td></tr>
<tr><td>
Stateful server connections could not be set to stateless again.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for session events triggered by <code>JCoServer</code> connections</b></td></tr>
<tr><td>
The events for sessions started by a <code>JCoServer</code> could be triggered more often than necessary. In particular, this was
true for the <code>jcoServerSessionStarted()</code> event, for which then there did not exist a corresponding <code>jcoServerSessionFinished()</code>
event. As a consequence too many idling sessions were created in the runtime environment.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for <code>JCoServerMonitor</code> information</b></td></tr>
<tr><td>
Under very high load both <code>getUsedServerThreadCount()</code> and <code>getMaximumUsedServerThreadCount()</code> were increasing above
the configured maximum until the load was lower again and then remained at the wrong high level.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix in numeric handling of signed or empty field values</b></td></tr>
<tr><td>
A <code>ConversionException</code> might be thrown when trying to get an empty or signed value
from a field of type <code>CHAR</code> as a converted numeric value. The following <code>JCoRecord</code>
methods were affected: <code>getInt()</code>, <code>getShort()</code>, <code>getLong()</code>,
<code>getBigInteger()</code>, <code>getDouble()</code>, <code>getFloat()</code> and <code>getBigDecimal()</code>.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix in repository for nested vector types</b></td></tr>
<tr><td>
Table types that referred to a table type as line type which itself refers again to a table type as line type and
table types that referred to a table type as line type which referse to a domain as line type were not correctly
stored in the repository, when being looked up from an ABAP system. As a consequence function modules that had parameters
of such a type could not be processed correctly.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for <code>java.lang.UnsatisfiedLinkError</code></b></td></tr>
<tr><td>
A <code>java.lang.UnsatisfiedLinkError</code> occurred with the message <code>com.sap.i18n.cp.ConverterJNI.ConvertCToXArrR([B[CII[BII[I)I</code>, when a blended
codepage such as 6100 is used.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for starting SAP GUI on Unix and MacOS</td></tr>
<tr><td>
If the path to the SAP GUI contained blanks, starting the Java GUI failed. On MacOS, in addition some startup parameters
needed to be adopted.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for tables in changing parameter lists</b></td></tr>
<tr><td>
If a table was part of the changing parameter list, and was not containing any row when executing the function module, then
the table was always returned empty.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Enhancement for destination and server configuration management</b></td></tr>
<tr><td>
If a configuration was updated, and someone uses a cached instance of a JCoServer or JCoDestination, an exception will be thrown to signal
that this instance is outdated.
</td></tr>
<tr><td> </td></tr>
<tr><td> </td></tr>
<tr><td><FONT SIZE="+1"><B>Release notes 3.0.1</B></FONT></td></tr>
<tr><td> </td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Improved documentation</b></td></tr>
<tr><td>
An example for CustomDestinationProvider has been added.
<p>API Documentation has been extended and improved.</p>
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>New APIs</b></td></tr>
<tr><td>
New APIs are available for general use:
<code>
<ul>
<li>JCo.getTraceLevel()
<li>JCo.getTracePath()
<li>JCoConnectionData.getSystemID()
</ul>
</code>
See API Documentation for details.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Support for SAPGUI</b></td></tr>
<tr><td>
<p>JCo is now able to start a SAP GUI on the local machine and associate it with a newly opened RFC connection. The backend prerequisites for this new feature are listed in
note <a href="http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1258724">1258724</a>. Starting
the SAP GUI can be controlled by the additional destination parameter <code>jco.client.use_sapgui</code>.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix in dispatcher worker thread</b></td></tr>
<tr><td>
The dispatcher worker thread might have been finished after errors occurring under heavy load. The thread dump
does not contain a thread called <code>JCoDispatcherWorkerThread</code> in this case.
<p>
The dispatcher worker thread might be started more than once due to insufficient synchronization. The thread dump
contains more than one thread called <code>JCoDispatcherWorkerThread</code> in this case.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for functions containing more than 127 non-scalar parameters</b></td></tr>
<tr><td>
<p>Functions with more than 127 non-scalar parameters caused an <code>ArrayIndexOfBoundsException</code>. The fix required a change for the
serial version UID of many data containers and metadata instances so that serialized instances of these classes can no longer be exchanged
with previous releases.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for <code>ArrayIndexOutOfBoundsException</code> on receive</b></td></tr>
<tr><td>
<p><code>ArrayIndexOutOfBoundsExceptions</code> might be thrown while receiving data (output parameters in client scenario or
input parameters in server scenario). The exception is thrown if the ABAP side has extended the data strcutures used
by the current function module compared to JCo's own metadata definition.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for <code>JCO_ERROR_DSR_PASSPORT_NOT_RECEIVED</code></b></td></tr>
<tr><td>
<p>A <code>JCoException</code> with the key <code>JCO_ERROR_DSR_PASSPORT_NOT_RECEIVED</code> was thrown in a JCo server on second
and subsequent stateful requests.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix in treatment of default BCD value</b></td></tr>
<tr><td>
<p>BCD fields were filled incorrectly if the default values was set. On the ABAP side the incorrect content of the BCD
field caused short dumps (ABAP runtime error BCD_BADDATA).
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix in firing of server events</b></td></tr>
<tr><td>
<p>The event <code>ALIVE</code> was not fired by the JCo runtime, if the ABAP system/gateway hase gone online when
the server was in the state <code>DEAD</code>. That might cause that the server application remained in the
the waiting state.
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for native crash during stateful server communication</b></td></tr>
<tr><td>
A native crash occurred on stateful requests from ABAP to Java
<ul>
<li>on the second or any subsequent request during a stateful server communication
<li>and if the request data volume was greater than 16000 bytes in the internal RFC representation
</ul>
</td></tr>
<tr BGCOLOR="#CCCCFF" CLASS="TableHeadingColor"><td><b>Bugfix for server connection leak</b></td></tr>
<tr><td>
<p>The JCo server did not release the internal connection handle properly, if the gateway was protected
with an ACL and the connection was declined. After a while all internal handles were used and either an <code>ArrayIndexOutOfBoundsException: 10000</code> was thrown and
logged to dev_jco_rfc.trc each time a new connection was required. <br>
This is the same issue like described in note <a href="http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1252962">1252962</a>
</td></tr>
<TR>
<TD>
<hr>
</TD>
</TR>
<TR>
<TD>
<i >Copyright © 2008 SAP AG. All Rights Reserved.</i>
</TD>
</TR>
</BODY>
</HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -