APAR | Description |
---|---|
JR26373 | NameNotFoundException is thrown from Context. The JMS function of BTTEvent is turned on by default. So, if JMS queue is not configured in WebSphere® Application Server, exceptions are thrown. |
JR26375 | The getElementAt() API is missing from OperationStep. |
JR26378 | Several GUI problems are restricting the use of the application. When using the DSEGuiBeans for the Java™ client, frequent screen freezes and unexpected behaviour with text fields and combo boxes are encountered. |
JR26627 | ava.lang.ClassCastException is thrown when using org.apache.struts.ActionMapping and com.ibm.btt.struts.BTTActionMapping together in BTT 5.2.0. |
JR26283 | SYNC_GET_LOCAL_LU_NAME and SYNC_GET_PARTNER_LU_NAME
verbs added to get the LU name from an LU62 connection:
For the two new verbs, BTT will call SNA CPI-C APIs: Extract_Local_LU_Name and Extract_Partner_LU_Name by JNI call. Note: The two APIs only apply
to the Communication Server running on AIX® and Linux® systems.
The following
is the sample code for the two verbs:
Lu62InteractionSpec ixnSpec = new Lu62InteractionSpec(); Lu62Record outgoingData = new Lu62Record(); Lu62Record returnData = new Lu62Record(); ixnSpec.setInteractionVerb(ixnSpec.SYNC_GET_LOCAL_LU_NAME); connection.execute(ixnSpec, outgoingData, returnData); System.out.println("Local LU name :"+returnData.getData()); |
JR26917 | Java™ client side does not support failover in BTT 5.2.0. |
JR27142 | String leaks in the CHA EJB cache. |
JR27127 | In general, there are two ways to manage conversations when sending continuous messages. One is to establish a new conversation for every message. The other is to create a single conversation and reuse it for sending different messages. The second method results in better performance. This APAR provides support for the first conversation mode: the host closes the conversation used by each unsolicited message. |
JR27170 | This APAR provides two parameters to configure the length of a TID/thread name in trace. |
JR27198 | In a performance environment, there might be thousands of threads pending, which can cause an out of memory crash in WebSphere Application Server. Each thread is waitOn Semaphore in the receive() method. When the connection is terminated, the waiting thread cannot be notified on Semaphore. As a result, it cannot exit. This APAR changes the event notification method to avoid creating too many threads. |
JR27406 | BTT does not support Opera Browser. |
JR27597 | BTT provides an extension for WTS to implement the BTTRequestProcessorUtil.getProcessId (HttpServletRequest request) method. However, when processing a transaction request, createProcessorId() is invoked unexpectedly, which causes the BTT module to replace the original processor ID with a new one. As a result, a new context is created. This causes a memory leak. |
JR27322 | Referenced objects are reserved after the conversation/Lu62ManageConnection is terminated. These objects should be deleted, because this causes a memory leak. |
JR27685 | BTT LU62 JCA parameter "establishConversationRetries" does not work if its value is greater than 0. |
JR27954 | When BTT JCA deallocates LU conversation, a conversation object must be printed in the trace. However, before printing, the conversation object is set to null. After BTT JCA deallocates an LU conversation, the object in the conversation is accessed. This APAR fixed these two problems. |
JR28052 | Every time BTT JCA creates a conversation, it loads a library, which is time-consuming. |
JR28061 | When implementing an invoker class which extends com.ibm.btt.cs.invoker.base.BeanInvokerImpl, the reference to the CHA Instance Id from the HttpSession will be removed and the HttpSession will be invalidated. So when the BTT client application calls the logoff operation (BTTServerOperation) on the server, the IllegalStateException from http session will be thrown. |
JR28183 | Request WAS pool to destroy BTT JCA connection immediately. |
JR28225 | JCA Performance issue: Exception is thrown when server stops. |
JR27898 | Missing header message when LU62 Message has multiple frames. |
JR28208 | Request to add parameter in BTT LU0 JCA to control whether to send TERMSELF after timeout. |
JR28209 | Change Request: a new custom property "sendInitSelf" is provided in order to disable sending init-self. The default value is true. Set it to false to disable sending init-self. |
JR28345 | JCAERR00047R timeout problem. Convert the getListenThreadSem() method to a synchronized method to prevent JCA timeout problem. |
JR28687 | BTT JCA supports 64-bit AIX systems. |
JR28841 | LU API SYNC_GET_ACTUAL_LU_NAME does not work in version 5.2. |
JR28704 | Unknown corrupt trace message due to I18N problem. |
JR28375 | The establishSession is slow for the listen thread because run() is pending on sleep(timeBetweenBidRetry) if init() is not executed. |
IY43326f_1 | Session down is not correctly recovered when Lu0SnaSession is using a LU that belongs to a Communication Server pool. |
APAR | Description |
---|---|
IZ01114 | In the JCA clone environment, a new method in the BTT
LU0 service for closing an LU0 session established on anther clone. Currently
there is a method ccClose() which uses the user session ID, but customers
need the same method using the LU0 name, which is passed as a parameter. A
new API ccClose(String luName) is added to Lu0SnaSessionService and Lu0SnaSession
class. The method will call Communication Server NOF API deactive_lu0_to_3 to terminate the LU0 session for the specified LU name. On the other clone that has already established a session for the LU, it will receive an UN-BIND message from the host and terminate the session. |
JR26363 | Add a new method setInitSelfUserData in Lu0SnaSessionService to send user data to the host when BTT LU0 Connector send INIT-Self to establish LU0 session. |
JR24998 | Cannot establish conversation with host using LU6.2. |