[deepamehta-devel] [Bug #12312] Re-publishing a topic map fails with client/server scenario

[admin at berlios.de]

Bug #12312, was updated on 2007-Nov-02 15:45
Here is a current snapshot of the bug.

Project: DeepaMehta
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 9
Submitted by: jri
Assigned to : jri
Summary: Re-publishing a topic map fails with client/server scenario

Details: Publishing a topic map fails if 2 conditions are met:
1) the topic map was already published
2) the client/server scenario is used (instead of the monolitic app)

Further investigation relvealed that the error happens since the introduction of the class CaseInsensitiveHashtable in revision 228. If in RelationalCorporateMemory.queryTopicData() the constructor call "new CaseInsensitveHashtable()" is replaced by "new Hashtable()" the error is gone".

The error message:
     [java] *** ApplicationService.executeTopicCommand(): Topic tt-ka-stadtplan:1 "Wedding" (t-4631:1) can't execute command "publishToGroup|t-4576|319|687" (error while writing directive of type 14 (java.lang.NullPointerException -- probably caused by wrong usage through application programmer))
     [java] de.deepamehta.DeepaMehtaException: error while writing directive of type 14 (java.lang.NullPointerException -- probably caused by wrong usage through application programmer)
     [java]     at de.deepamehta.service.CorporateDirectives.write(CorporateDirectives.java:626)
     [java]     at de.deepamehta.service.MessagingConnection.sendDirectives(MessagingConnection.java:124)
     [java]     at de.deepamehta.service.DeepaMehtaServer.sendDirectives(DeepaMehtaServer.java:83)
     [java]     at de.deepamehta.service.ApplicationService.broadcastSessions(ApplicationService.java:3763)
     [java]     at de.deepamehta.service.ApplicationService.broadcast(ApplicationService.java:3744)
     [java]     at de.deepamehta.topics.TopicMapTopic.publish(TopicMapTopic.java:1017)
...
...


For detailed info, follow this link:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=12312&group_id=5174