Metamerge logo
Search

Advanced Search
*
*
*
* HOME DOCUMENTS & RESOURCES DOWNLOADS EARLY TECH ACCESS SUPPORT FAQ KNOWN ISSUES OLD VERSIONS
*

 

Fixed Issues 4.6

Script Libraries not available to Listeners

Listeners, or Simple EventHandlers do not have access to your Script Libraries.

Workaround:

  • Copy/Paste your script

  • Contact support@metamerge.com to get a set of new jar-files that fixes Timer and GenericThread listeners.

This bug is fixed in the next release, and will probably trigger a 4.6.8 release.

Logged in 4.6.7, present since 4.6, fixed in 4.6.8

 

JMS 1.13 can loose queue elements when Iterating

If you have an Iterator with a timeout, and the Timeout is reached (queue empty for more than the timeout value), then entries might get lost. You will loose the queue items if they are put in the queue after the timeout, but before the Connector has been properly closed.

Logged 2002-3-1 for ETA JMS version 1.13.  This bug does not apply to JMS versions delivered with Integrator 4.6 since it uses functionality new in 1.13.

There is no work-around for this bug but it will only show up if you use the timeout feature of JMS. 

 JMS MQ Series does not support  topics

When using IBM-MQ JMS you will get a null pointer exception when trying to connect. 

Logged in version 4.6.2

This issue is fixed by the new version of the JMS Connector 1.13 but a fix for the JMS Connector enclosed with the 4.6 release (JMS 1.12) is available through the documentation page of the Connector, 

NT/ADSI Connector can clear passwords during update

Any update operation that has not mapped the Password Attribute, will result in clearing the Password.

Logged in version 4.6.6.

Connectors: Override Add hook defect in Update and AddOnly modes

The work object is not available in the Override Add Hook

Fix: This will be fixed in 4.6.6.  If this bug hits you, download this  miserver.jar and put it in the jars/ directory.

Fixed in 4.6.6, Logged in version 4.6.5, present since 4.6.3

HTTP EventHandler using Auth Connector

An updated version of the HTTP EventHandler should have been included with version 4.6.3: If you use the Auth Connector with the HTTP EventHandler, you will get a java.lang.AbstractMethodError.

If you suspect this, go to the EventHandler templates and check the version of metamerge.HTPPEventHandler: Revision  1.3 of the HTTPEventHandler has this problem.

Fix:  Replace HTTPEventHandler.jar in the jars/eventhandlers directory with this HTTPEventHandler.jar 

Fixed in 4.6.6, Logged in version 4.6.5, present since 4.6.3

 

XML Parser limitations

The XML parser can have problems reading files larger that 4MB and writing files larger than 14MB. 

This is caused by JAVA not getting access to enough memory.  See the FAQ for a reply to this. 

Logged in version 4.6.5

Memory Leak

Each time an AssemblyLine is started, around 30k memory is 'lost'.  This is typically something that causes problems when you have a configuration file with an EventHandler starting AssemblyLines over and over.

Logged in 4.6.4, reduced in 4.6.5  to 2.5k

Running out of file handles

The log file is not closed properly after terminating an AssemblyLine.  This can cause you to run out of file handles if you start the AssemblyLine many times (for example from an EventHandler).

Workaround: Close down and restart the MIserver when you are getting low on file handles.  Fixed in  4.6.5.

If you use hhtps:/ as part of the url, the AssemblyLine will fail

This is due to an internal parser not being loaded. The error message you will get is:

ERROR> AssemblyLine xxx failed because unknown protocol: https

The situation will only occur when using the Run button in the admin-tool, not if you run your AssemblyLine from command-line or EventHandler.

Temporary fix / Workaround:

  1. In the Admin Tool, select View|Preferences.  
  2. In the Java Command box, type miserver (you might need to prefix this with the path of the miserver application)

Logged in version 4.6.2

In certain situations, the Lotus Domino Connector (and possibly some others) will not Run from the Admin Tool

The Lotus Domino Connector will in this situation give you a connection error.  You will know that you have encountered this issue if

  1. You are able to Connect button on  the Configuration|Attributes tab of the Connector.
  2. The AssemblyLine can be run through the miserver command

This is due to an internal parser not being loaded.

Temporary fix / Workaround:

  1. In the Admin Tool, select View|Preferences.  
  2. In the Java Command box, type miserver (you might need to prefix this with the path of the miserver application)

Logged in version 4.6.2

4.6 Installer fails for some systems

This is true for Solaris 2.6, Windows ME, Turbolinux, MacOS X.

The problem is traced back to the software building our Installer, expect a fix to be released by the end of October.

Logged in version 4.6.1

Backward Compatibility Issue:  If you use code that supplies an entry to be treated as the work-entry, it might fail.

(This issue is related to expert usage of the Integrator:  If the description below make no sense to you, you can probably ignore this issue all together).

Some methods, like rscTaskComponent.add  (usually called by connectorName.add() ) have an Entry object as a parameter.  That parameter will usually be the work entry, in which case there are no problems.  However, if you have created your own temporary Entry object and want the AL to treat it as the work entry, you could submit the temporary Entry object as a parameter. This has stopped working, as the global work entry will always be used.

Workaround:

Using the work object for passing the Entry values will get around this problem.  This issue still is a bug, and a patch will restore the backward compatibility.

Example:

We here assume that you have a connector called myConnector in AddOnly mode.

tempWork.addAttributeValue( "name", "John Doe");
myConnector.add( tempWork );

This code will currently fail, while

work.addAttributeValue( "name", "John Doe");
myConnector.add( work );

will perform correctly supposing that the other attributes of work does not create a problem.

Logged in version 4.6.2, fixed in 4.6.3

 

 

*
  Metamerge Integrator version 4.6 ©Copyright Metamerge AS 2000-2002 Last edited 2002-06-10 contact us