Binlog contains event bigger than max value of max_allowed_packet

[Iwan Aucamp]

binlog event details :

mysqlbinlog --start-position=31440700 --stop-position=31440800
/opt/csw/mysql5/var/mysql-bin.000002
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len:
1380272215, event_type: 48
DELIMITER ;
# End of log file
ROLLBACK /* added by mysqlbinlog */;
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;

Details for max_allowed_packet
Command Line Format --max_allowed_packet=#
Config File Format max_allowed_packet
Option Sets Variable Yes, max_allowed_packet
Variable Name max_allowed_packet
Variable Scope Both
Dynamic Variable Yes
Permitted Values Type numeric
Default 1048576
*Range 1024-1073741824**
*

Is there any good reason this is allowed to happen ? and how do i work
around it ?

Regards
*
*