[
https://issues.apache.org/jira/browse/KAFKA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594131#comment-13594131
]
Colin B. commented on KAFKA-104:
--------------------------------
I am unable to reproduce this issue.
It is likely this was fixed in another issue such as:
https://issues.apache.org/jira/browse/KAFKA-495
> Invalid topics prevent broker start-up
> --------------------------------------
>
> Key: KAFKA-104
> URL: https://issues.apache.org/jira/browse/KAFKA-104
> Project: Kafka
> Issue Type: Bug
> Reporter: Joel Koshy
> Priority: Minor
>
> Excerpt from a trace we saw today. If there is a topic directory with an
> invalid name, then the registerMBean call throws an exception which
> eventually results in a start failure. Also, if you try sending messages with
> an invalid topic to a broker, the broker's logs get flooded with these
> exceptions. Easy fix is to wrap the registerMBean with Utils.swallow; and
> probably prevent ProducerRequest from accepting invalid topics.
> 2011/08/15 20:43:50.834 FATAL [KafkaServer] [main] [kafka]
> javax.management.MalformedObjectNameException: Invalid character '"' in value
> part of property
> at javax.management.ObjectName.construct(ObjectName.java:602)
> at javax.management.ObjectName.<init>(ObjectName.java:1403)
> at kafka.utils.Utils$.registerMBean(Utils.scala:372)
> at kafka.log.Log.<init>(Log.scala:120)
> at kafka.log.LogManager$$anonfun$2.apply(LogManager.scala:70)
> at kafka.log.LogManager$$anonfun$2.apply(LogManager.scala:65)
> at
> scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:34)
> at scala.collection.mutable.ArrayOps.foreach(ArrayOps.scala:34)
> at kafka.log.LogManager.<init>(LogManager.scala:65)
> at kafka.server.KafkaServer.startup(KafkaServer.scala:60)
> at
> kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:46)
> at com.linkedin.kafka.KafkaStartable.start(KafkaStartable.java:54)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
