Error message, AEFA-000034 'Received message couldn't be written to a file' was reported by TIBCO ActiveMatrix Adapter for Files (Unix/Win) (FA) subscriber on a VMware Windows machine even though the Write Schema is valid.
book
Article ID: KB0087787
calendar_today
Updated On:
Products
Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for Files for Unix and Windows
-
Not Applicable
-
Description
Description: Description: =========
TIBCO ActiveMatrix Adapter for Files (Unix/Win)
(FA) subscriber throws the error, "AEFA-000034 'Received message
couldn't be written to a file'", while subscribing to a JMS Queue message
greater than 7 MB on a virtual Windows system, even when the Write Schema and other configurations are valid.
Example: When an FA Subscription Service is listening for
messages on a JMS queue, if publishing a message 9 MB in size on the JMS queue, the FA subscriber will throw the error, 'AEFA-000034'. But if publishing a message of 3 MB in size on the JMS queue, then the Adapter subscriber subscribes successfully. Symptoms: TIBCO ActiveMatrix Adapter for Files (Unix/Win) subscriber throws the error, "AEFA-000034 'Received message
couldn't be written to a file'" while subscribing to a JMS Queue message
(message size > 7 MB) on a virtual Windows system. Cause: The error occurs during subscribing a message greater than 7 MB on VMware Windows machine.
Issue/Introduction
Error message, AEFA-000034 'Received message couldn't be written to a file' was reported by TIBCO ActiveMatrix Adapter for Files (Unix/Win)
(FA) subscriber on a VMware Windows machine even though the Write Schema is valid.
Resolution
Reinstall TIBCO ActiveMatrix Adapter for Files (Unix/Win) (FA) 6.0.0 with Hotfix 05 on the VMware Windows machine. The FA subscriber will then be able to subscribe to larger messages.