I am using RabbitMQ .net client library to publish the messages to a RabbitMQ node in the following manner.
var factory = new ConnectionFactory
{
HostName = "localhost",
Port = 5672,
UserName = "guest",
Password = "guest",
VirtualHost = @"/"
};
_conn = factory.CreateConnection();
_channel = _conn.CreateModel();
_properties = _channel.CreateBasicProperties();
And then the below is being called in a loop
using (var memStream = new MemoryStream())
{
var formatter = new BinaryFormatter();
formatter.Serialize(memStream, message);
var properties = _channel.CreateBasicProperties();
properties.Priority = Convert.ToByte((int) priority);
_channel.BasicPublish(String.Empty, _routeKey, properties, memStream.ToArray());
}
The above code is working fine with a medium load around 50-100 messages per second. But when I increase the number of messages to be published around 500 messages per second, the RabbitMQ node starts giving the below error and disconnects the channel.
Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 206, first 16 octets = <<31,0,60,0,40,0,0,6,115,101,110,115,111,114,16,115>>:
{invalid_frame_end_marker, 114}
", classId=0, methodId=0, cause=:
at RabbitMQ.Client.Impl.SessionBase.Transmit(Command cmd)
at RabbitMQ.Client.Impl.ModelBase.ModelSend(MethodBase method, ContentHeaderBase header, Byte[] body)
at RabbitMQ.Client.Impl.ModelBase.BasicPublish(String exchange, String routingKey, Boolean mandatory, Boolean immediate, IBasicProperties basicProperties, Byte[] body)
at RabbitMQ.Client.Impl.ModelBase.BasicPublish(String exchange, String routingKey, Boolean mandatory, IBasicProperties basicProperties, Byte[] body)
at RabbitMQ.Client.Impl.ModelBase.BasicPublish(String exchange, String routingKey, IBasicProperties basicProperties, Byte[] body)`
The size of the message with BinaryFormatter is around 5kb.
Description:
Service Control Audit Instance crashing on rabbitmq error invalid_frame_end_marker
ServiceControl Audit Instance Logs:
2019-10-11 14:59:34.8989|30|Warn|RabbitMQ.Client.IConnection|'Publish' connection shutdown: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
2019-10-11 14:59:36.6020|63|Error|NServiceBus.RecoverabilityExecutor|Moving message '272829b9-e638-4eb1-928d-aae30149792f' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:36.6020|78|Error|NServiceBus.RecoverabilityExecutor|Moving message 'e8d88131-536f-46ed-a801-aae301497a14' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:36.6177|78|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `e8d88131-536f-46ed-a801-aae301497a14`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:36.6177|63|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `272829b9-e638-4eb1-928d-aae30149792f`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.3990|87|Error|NServiceBus.RecoverabilityExecutor|Moving message 'e8d88131-536f-46ed-a801-aae301497a14' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.3990|87|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `e8d88131-536f-46ed-a801-aae301497a14`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4458|70|Error|NServiceBus.RecoverabilityExecutor|Moving message '272829b9-e638-4eb1-928d-aae30149792f' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4458|70|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `272829b9-e638-4eb1-928d-aae30149792f`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4458|79|Error|NServiceBus.RecoverabilityExecutor|Moving message '3f5d9b45-23f4-4a23-a3aa-aae30147879c' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4615|79|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `3f5d9b45-23f4-4a23-a3aa-aae30147879c`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4615|47|Error|NServiceBus.RecoverabilityExecutor|Moving message '85bd58a2-8205-4e58-af43-aae3014979dd' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4771|47|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `85bd58a2-8205-4e58-af43-aae3014979dd`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4927|50|Error|NServiceBus.RecoverabilityExecutor|Moving message '272829b9-e638-4eb1-928d-aae30149792f' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4927|50|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `272829b9-e638-4eb1-928d-aae30149792f`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.4927|73|Error|NServiceBus.RecoverabilityExecutor|Moving message '410b0ee3-764e-4cc2-88ec-aae301497a8e' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.5083|73|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `410b0ee3-764e-4cc2-88ec-aae301497a8e`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.5083|75|Error|NServiceBus.RecoverabilityExecutor|Moving message '272829b9-e638-4eb1-928d-aae30149792f' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.5083|75|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `272829b9-e638-4eb1-928d-aae30149792f`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.5708|91|Error|NServiceBus.RecoverabilityExecutor|Moving message '272829b9-e638-4eb1-928d-aae30149792f' to the error queue 'Particular.ServiceControl.real-prod.Audit.Errors' because processing failed due to an exception:
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
2019-10-11 14:59:38.6021|91|Fatal|NServiceBus|Failed to execute recoverability policy for message with native ID: `272829b9-e638-4eb1-928d-aae30149792f`
RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"?{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at NServiceBus.MoveToErrorsExecutor.MoveToErrorQueue(String errorQueueAddress, IncomingMessage message, Exception exception, TransportTransaction transportTransaction)
at NServiceBus.RecoverabilityExecutor.<MoveToError>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
Failed Audit Import File:
Exception:
Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text="FRAME_ERROR - type 3, first 16 octets = <<"{"Correlation">>: {invalid_frame_end_marker,
121}", classId=0, methodId=0, cause=
StackTrace:
at RabbitMQ.Client.Framing.Impl.Connection.EnsureIsOpen()
at RabbitMQ.Client.Framing.Impl.Connection.CreateModel()
at NServiceBus.Transport.RabbitMQ.ConfirmsAwareChannel..ctor(IConnection connection, IRoutingTopology routingTopology, Boolean usePublisherConfirms)
at NServiceBus.Transport.RabbitMQ.ChannelProvider.GetPublishChannel()
at NServiceBus.Transport.RabbitMQ.MessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, ContextBag context)
at ServiceControl.Audit.Auditing.AuditIngestor.<Ingest>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NServiceBus.Transport.RabbitMQ.MessagePump.<Process>d__29.MoveNext()
Source:
RabbitMQ.Client
TargetSite:
Void EnsureIsOpen()
Version:
4.3.3
-
#1
Trying to find a way to catch the esc key in a frame defined as a dialog-box. Thus far my efforts have either done nothing, or closed the entire application rather than just the immediate dialog box. I have tried ‘ON ESC OF FRAME Dialog-Frame’, ‘ON ENDKEY OF FRAME Dialog-Frame’, and ‘ON END-ERROR OF FRAME Dialog-Frame’.
TIA
Whwar9739
-
#2
What platform are you attempting to do this on?
Perhaps a snippet of sample code might be in order?
-
#3
Working with Progress 11.2.1. The frame is tied to an active window. Let’s see what I can for snippets of code, lol.
Code:
DEFINE FRAME Dialog-Frame
txtCopies AT ROW 2.43 COL 6.8 COLON-ALIGNED NO-LABEL
l-msg AT ROW 1.29 COL 6.2 COLON-ALIGNED NO-LABEL
copies AT ROW 2.43 COL 11.6 COLON-ALIGNED NO-LABEL
IMAGE-3 AT ROW 1 COL 1
SPACE(18.99) SKIP(1.56)
WITH VIEW-AS DIALOG-BOX KEEP-TAB-ORDER
SIDE-LABELS NO-UNDERLINE THREE-D SCROLLABLE
TITLE "Print".
ON WINDOW-CLOSE OF FRAME Dialog-Frame /* Print */
DO:
l-close = YES.
APPLY "END-ERROR":U TO SELF.
END.
ON ANY-PRINTABLE OF txtCopies IN FRAME Dialog-Frame
DO:
IF KEYFUNCTION(LASTKEY) = "0"
THEN DO:
ASSIGN txtCopies:SCREEN-VALUE = "0".
l-cancel = Yes.
PROCESS EVENTS.
END. /* IF KEYFUNCTION(LASTKEY) = "0" */
END.
ON LEAVE OF txtCopies IN FRAME Dialog-Frame
DO:
IF INT(txtCopies:SCREEN-VALUE) = 0
THEN DO:
l-cancel = Yes.
END. /* IF INT(txtCopies:SCREEN-VALUE) = 0 */
END.
To add to the complexity, txtCopies is not always available, and in fact the specific issue I am having is when it’s hidden attribute is set to YES.
When txtCopies is not hidden the esc key functions as expected and closes just the window and not the entire application.
Also most of this is code that built using the AppBuilder, not sure if that will make any difference or not.
-
#4
If any help, for dialog boxes I do something like this:
Code:
ON END-ERROR, ENDKEY OF FRAME Dialog-Frame
DO:
DISABLE ALL WITH FRAME Dialog-Frame.
HIDE FRAME Dialog-Frame NO-PAUSE.
RETURN NO-APPLY.
END.
-
#5
If any help, for dialog boxes I do something like this:
Code:
ON END-ERROR, ENDKEY OF FRAME Dialog-Frame DO: DISABLE ALL WITH FRAME Dialog-Frame. HIDE FRAME Dialog-Frame NO-PAUSE. RETURN NO-APPLY. END.
Ok I tried adding something extremely similar to this and still nothing. Below are snippets of the progress logs. First one is when the txtCopies is available and the second one is when the txtCopies is set to hidden. This does have the code from above in it, note the begin/end-trigger. Oh and I removed the program name.
***WITH txtCopies:HIDDEN = NO***
[13/09/04@15:19:54.732-0500] P-007472 T-006580 3 4GL PROEVENTS START GUI WM_KEYDOWN FILL-IN txtCopies
[13/09/04@15:19:54.732-0500] P-007472 T-006580 3 4GL PROEVENTS START GUI WM_CHAR ESC FILL-IN txtCopies
[13/09/04@15:19:54.732-0500] P-007472 T-006580 2 4GL PROEVENTS PUSH ESC (END-ERROR) FILL-IN txtCopies
[13/09/04@15:19:54.732-0500] P-007472 T-006580 2 4GL PROEVENTS PUSH ESC (END-ERROR) DIALOG-BOX Dialog-Frame Handle:10122
[13/09/04@15:19:54.732-0500] P-007472 T-006580 2 4GL PROEVENTS Begin-Trigger «ESC (END-ERROR) OF DIALOG-BOX Dialog-Frame» Handle:10122
[13/09/04@15:19:54.732-0500] P-007472 T-006580 2 4GL PROEVENTS End-Trigger «ESC (END-ERROR) OF DIALOG-BOX Dialog-Frame» Handle:10122
[13/09/04@15:19:54.732-0500] P-007472 T-006580 2 4GL PROEVENTS PRGS ESC (END-ERROR) DIALOG-BOX Dialog-Frame Handle:10122 discarded return no-apply
[13/09/04@15:19:54.732-0500] P-007472 T-006580 2 4GL PROEVENTS POP ESC (END-ERROR) DIALOG-BOX Dialog-Frame Handle:10122
[13/09/04@15:19:54.732-0500] P-007472 T-006580 2 4GL PROEVENTS PRGS ESC (END-ERROR) FILL-IN txtCopies discarded
[13/09/04@15:19:54.732-0500] P-007472 T-006580 2 4GL PROEVENTS POP ESC (END-ERROR) FILL-IN txtCopies
—————————-
***WITH txtCopies:HIDDEN = YES***
[13/09/04@15:19:56.909-0500] P-007472 T-006580 3 4GL PROEVENTS START GUI WM_KEYDOWN DIALOG-BOX Dialog-Frame Handle:10139
[13/09/04@15:19:57.418-0500] P-007472 T-006580 2 4GL PROEVENTS PROCESS EVENTS [print-doc]
[13/09/04@15:19:57.418-0500] P-007472 T-006580 3 4GL PROEVENTS START GUI WM_KEYDOWN DIALOG-BOX Dialog-Frame Handle:10139
[13/09/04@15:19:57.928-0500] P-007472 T-006580 2 4GL PROEVENTS PROCESS EVENTS [print-doc]
[13/09/04@15:19:57.928-0500] P-007472 T-006580 3 4GL PROEVENTS START GUI WM_KEYDOWN DIALOG-BOX Dialog-Frame Handle:10139
-
#6
Did you have the RETURN NO-APPLY line? I think this is important.
-
#7
What is the MAIN-BLOCK code like? Does it differ much from the standard AppBuilder code for dialog boxes which always seems to work okay when the Esc key is pressed?:
Code:
MAIN-BLOCK:
DO ON ERROR UNDO MAIN-BLOCK, LEAVE MAIN-BLOCK
ON END-KEY UNDO MAIN-BLOCK, LEAVE MAIN-BLOCK:
RUN enable_UI.
WAIT-FOR GO OF FRAME {&FRAME-NAME}.
END.
RUN disable_UI.
-
#8
I do not know if this is relevant, but from your Progress logs it appears the Esc key is being recorded as an END-ERROR event. In this simple test I tried in a standard AppBuilder Dialog Box creation the event says it is ENDKEY when I press the Esc key:
Code:
ON END-ERROR OF FRAME Dialog-Frame /* Dialog Box */
OR ENDKEY OF FRAME Dialog-Frame
DO:
MESSAGE LAST-EVENT:FUNCTION VIEW-AS ALERT-BOX INFORMATION.
RETURN NO-APPLY.
END.
-
#9
I do not know if this is relevant, but from your Progress logs it appears the Esc key is being recorded as an END-ERROR event. In this simple test I tried in a standard AppBuilder Dialog Box creation the event says it is ENDKEY when I press the Esc key:
Code:
ON END-ERROR OF FRAME Dialog-Frame /* Dialog Box */ OR ENDKEY OF FRAME Dialog-Frame DO: MESSAGE LAST-EVENT:FUNCTION VIEW-AS ALERT-BOX INFORMATION. RETURN NO-APPLY. END.
Yes it gets caught as an END-ERROR but only when the FILL-IN is *not* hidden.
-
#10
Did you have the RETURN NO-APPLY line? I think this is important.
Cringer, yes I did.
-
#11
What is the MAIN-BLOCK code like? Does it differ much from the standard AppBuilder code for dialog boxes which always seems to work okay when the Esc key is pressed?:
Code:
MAIN-BLOCK: DO ON ERROR UNDO MAIN-BLOCK, LEAVE MAIN-BLOCK ON END-KEY UNDO MAIN-BLOCK, LEAVE MAIN-BLOCK: RUN enable_UI. WAIT-FOR GO OF FRAME {&FRAME-NAME}. END. RUN disable_UI.
Similar except we have some additional business logic and no WAIT-FOR line.
-
#1
Good greetings!
While taking pictures with my F100, I noticed the «End» (i.e., End of Roll) error message after shooting the 15th frame. I was able to continue shooting by pushing the shutter a few times — the error message cleared, and all was well until frame 30. Now the «End» error is back, and the camera won’t let me take any more pictures. For whatever it’s worth, the film in the camera is Cinestill 800. I’ve put 1000 rolls through the camera, and this happened only once before — also with Cinestill 800!! My plan is to rewind the film prematurely and possibly never put Cinestill in this camera again?! Hopefully it’s the film and not the camera, but I wonder if any of you have any insight into my annoying situation?
Sincere thanks for your time and trouble!
-
#2
The usual question: Did you try fresh batteries?
-
#3
I had weird issues with an F100, similar IIRC. New battery fixed it. Not sure if that is case here.
-
#4
The usual question: Did you try fresh batteries?
You are a faster typist 
-
#5
Ha! Thank you Sirius and mshchem! Indeed I tried fresh batteries to no avail!
-
#6
You are a faster typist
I am also better looking. 
-
#7
I am also better looking.
this is a fun forum
-
#8
The problem you’re having is that Cinestill 800 cartridges are not DX coded so, you must set the ISO manually
-
#9
The problem you’re having is that Cinestill 800 cartridges are not DX coded so, you must set the ISO manually
I’m afraid not — I set the iso manually for every roll I put in the camera.
-
#10
I’m afraid not — I set the iso manually for every roll I put in the camera.
Back to square one… Like you say it may be best to avoid C800 then
-
#11
A explanation may be that the force needed to pull the film out of the cassette is at the verge of the winder switching off. But I would not know why.
Otherwise some bug at frame counting.
-
#12
The problem you’re having is that Cinestill 800 cartridges are not DX coded so, you must set the ISO manually
What bearing on the numbering of the exposure does the ISO setting have. That is one thing I have never heard of. The ISO setting is entirely seperate from the frame counter
-
#13
A advanced camera that reads the ISO from the cassette in addition reads its frame number. So the error in this case might not be a generic frame-counting error but instead a error related to a default setting for uncoded cassettes.
-
#14
According to the manual (page 34) with non-DX film the default is that an ERR message is shown only when first loading the film, but goes on to say this can be changed in Custom settings to show ERR briefly each time you switch the camera on. In the confusion when confronted with an ERR are you sure it’s not every time you switch the camera on, and the cause simply a Custom menu function? If it seems to appear randomly how many times do you look at the menu screen when you switch the power on before the message has time to disappear? Anyway just an idea, but FWIW it may be an idea to reset the Custom menu anyway.
-
#15
What bearing on the numbering of the exposure does the ISO setting have.
None. But I can’t tell you how many times my heart sank when I loaded my XPan with a non-DX coded canister and the camera went dead (because the ISO was set to DX). Now, I don’t remember ever trying to set the camera’s ISO to DX setting mid roll on a non-DX coded canister to see what happens, I guess you just don’t f*ck with this camera for no reason… 
Last edited: Aug 8, 2022
-
#16
A advanced camera that reads the ISO from the cassette in addition reads its frame number. So the error in this case might not be a generic frame-counting error but instead a error related to a default setting for uncoded cassettes.
I use plain black enamel painted metal re-loadable cassettes in both my F100 and F80 and never encountered a problem where it stopped winding after a less number of frames had been exposed that what I actually loaded into the cassette.
-
#17
I use plain black enamel painted metal re-loadable cassettes in both my F100 and F80 and never encountered a problem where it stopped winding after a less number of frames had been exposed that what I actually loaded into the cassette.
But that is most probably a totally different scenario (when no DX code at all is present) for the camera in question. DX code is not only for ISO, but also for number of exposures and exposure latitude properties of the film in the canister.
It might (and probably is) well be an intentionally programmed code path to throw an error when a canister with DX code for 24 exp. reaches 30th frame, because this should not happen. If Cinestill canisters are not DX-coded properly or there is a problem of reading their DX code in some cameras, this could trigger the error message.
I’ll try my F80 to see if I can get the camera to throw the same error with a 12/24 exp DX code after 15/30 shots…
-
#18
What bearing on the numbering of the exposure does the ISO setting have. That is one thing I have never heard of. The ISO setting is entirely seperate from the frame counter
Agreed, what I meant to say is that the none DX coded cartridges won’t tell the camera the ISO or how many exposures the roll has.
-
#19
I forget if the Cinestill 800 was DX coded when I used it. it is now according to their website:
800Tungsten High Speed Color Negative Film, 35mm
Motion picture film for still photographers! CINESTILL 800Tungsten is a unique color film for still photographers. This ISO 800 speed tungsten balanced color negative film is based on the same gold standard motion picture technology used by top cinematographers around the world. Designed for…
cinestillfilm.com
I stopped using it because my last few rolls came pre-fogged… Which was a bummer because I like the film. It did mess up the ISO reader on my M7- even though I set it manually it would flash a ISO 5000 (If i recall correctly) message as the markings on the cassette was throwing things off. Even though it flashed that message it still exposed correctly for the manually set ISO.
-
#20
The problem you’re having is that Cinestill 800 cartridges are not DX coded so, you must set the ISO manually
What’s the link between Cinestill 800 not being DX coded and an error at frame 30 in an F100?
This question is open to any others familiar with an F100
Thanks
pentaxuser
-
#21
I’ll try my F80 to see if I can get the camera to throw the same error with a 12/24 exp DX code after 15/30 shots…
Nikon F80 doesn’t read the number of exposures from DX code. If Nikon F100 is the same (only has one row of contacts for reading DX code), then this error is not related to DX code…
-
- Acere
- Deleted
- Aug 8, 2022
- Reason: none
-
#22
What’s the link between Cinestill 800 not being DX coded and an error at frame 30 in an F100?
This question is open to any others familiar with an F100
Thanks
pentaxuser
Because the DX code tells the camera how many exposures the roll is, without it the camera is blind to ISO & exposure information. So, the lack of a DX code maybe an issue don’t you think? BTW I do have an F100 an F80 and I’m just trying to be helpful.
-
#23
Because the DX code tells the camera how many exposures the roll is, without it the camera is blind to ISO & exposure information. So, the lack of a DX code maybe an issue don’t you think? BTW I do have an F100 an F80 and I’m just trying to be helpful.
OK thanks. I wasn’t implying your intentions were not of good intent, I was just curious about the F100’s internal link that was connected to the problem
I don’t have an F100 but in none of my cameras is there this link to frame counting and refusal to take the film further than frame 30
I can see why without a DX code a camera has to revert arbitrarily to say an ISO of 100 this rendering a problem with exposure if the owner doesn’t set the speed dial correctly for the film but stopping the film at frame 30 just doesn’t seem to be likely link. If it makes sense to Nikon to build in a mechanism to prevent wrong exposure by not allowing the film to be used then I wonder why it doesn’t stop the film at the start
None of it makes much sense to me if the F100 does what you think it does
Can any other F100 user chime in here to help settle the matter?
pentaxuser
-
#24
The only thing I see about DX coded reading error in the Customs Functions menu is #5 but this is just a warning when to alert the user of non DX coded films.
#5: DX reading error warning
0: After film loading (default)
1: when the power switch is on
Here’s a link to all of the F-100’s 22 custom functions
-
#25
If the F100 works fine with other films and only has problems with Cinestill, I’d just stop using Cinestill in that camera.