Re: Non standart characters in computer name block activemq

[Kai-ssi <pr...@ssi-schaefer-noell.com>]

I have a similar problem with activemq-5.2-20080803.231633-26 and the kaha
store. An object message from the client "meißen" works fine until it will
bre read from the kaha store. The broker says:

The client says:
ERROR 2008-08-21 12:14:10.906       AbstractStoreCursor - Failed to fill
batch
java.io.IOException: Failed to read to journal for: offset = 4770274, file =
9, size = 2317, type = 0. Reason: java.io.UTFDataFormatException: bad string
  at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
  at
org.apache.activemq.store.amq.AMQPersistenceAdapter.createReadException(AMQPersistenceAdapter.java:637)
 ...
Caused by: java.io.UTFDataFormatException: bad string
  at
org.apache.activemq.util.DataByteArrayInputStream.readUTF(DataByteArrayInputStream.java:286)
  at
org.apache.activemq.openwire.v3.BaseDataStreamMarshaller.looseUnmarshalString(BaseDataStreamMarshaller.java:572)
...

The client says:
ERROR 2008-08-21 12:14:20.593 ehouseMessageReceiverImpl                               
- Could not create consumer for internal SAL queue: DataWarehouseManag
er! Problem: javax.jms.JMSException: java.lang.RuntimeException:
java.io.IOException: Failed to read to journal for: offset = 4770274, file =
9, size = 2317,
 type = 0. Reason: java.io.UTFDataFormatException: bad string
javax.jms.JMSException: java.lang.RuntimeException: java.io.IOException:
Failed to read to journal for: offset = 4770274, file = 9, size = 2317, type
= 0. Re
ason: java.io.UTFDataFormatException: bad string
  at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)

The problem is, that the produce gets no error message at all and it was
difficult to find out which message corrupts the kaha store, which now
blocks all messages not only messages from "meißen".
The environment is a Windows 2003 Server and a Windows XP client.


keneida wrote:
> 
> I spoted it in version 4.1.1 I'm not sure if call it a bug but:
> When amq library connets to amq server. The name of the connection gets an
> id. It is in pattern of ID + computer_name + some string
> When the computer has non standart characters like ą ł ę in the name
> (windows computer name,  I did not test it on Linux) the queue recives the
> report and after whole activemq is blocked.
> LocalTransaction               - POST COMMIT FAILED:
> java.lang.RuntimeException: java.io.IOException: Failed to broker message:
> "id of the broker" in container: java.io.UTFDataFormatException: bad
> string
> 

-- 
View this message in context: http://www.nabble.com/Non-standart-characters-in-computer-name-block-activemq-tp13110343p19140983.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.