Home › Forum › Allgemeines › Allgemeines zu Nuclos › Ressourcenplanung in 3.3beta
- Dieses Thema hat 2 Antworten und 2 Teilnehmer, und wurde zuletzt aktualisiert vor 11 Jahre, 3 Monaten von
Thomas Pasch.
-
AutorBeiträge
-
5 März 2012 um 14:37 Uhr #5125
Martin Schwärzel
TeilnehmerHallo
Hallo
Wenn ich eine neue Ressourcenplanung erstellen will, passiert am Schluss gar nichts. Die Planung wird nicht angezeigt2012-03-05 12:22:47,893 INFO [org.nuclos.client.jms.WeakReferenceMessageListener] onMessage: Received message from topic topic.heartBeat: ActiveMQTextMessage {commandId = 5, responseRequired = true, messageId = ID:NuclosBasis-1606-1330937557468-2:48:1:1:1, originalDestination = null, originalTransactionId = null, producerId = ID:NuclosBasis-1606-1330937557468-2:48:1:1, destination = topic://topic/heartBeat, transactionId = null, expiration = 0, timestamp = 1330946560406, arrival = 0, brokerInTime = 1330946560406, brokerOutTime = 1330946560406, correlationId = null, replyTo = null, persistent = true, type = null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, content = null, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 1024, properties = null, readOnlyProperties = true, readOnlyBody = true, droppable = false, text = 15}
for org.nuclos.client.jms.TopicNotificationReceiver$HeartBeatMessageListener@63f6ea
2012-03-05 12:22:47,894 INFO [org.nuclos.client.jms.TopicNotificationReceiver] onMessage: Received heartbeat message ActiveMQTextMessage {commandId = 5, responseRequired = true, messageId = ID:NuclosBasis-1606-1330937557468-2:48:1:1:1, originalDestination = null, originalTransactionId = null, producerId = ID:NuclosBasis-1606-1330937557468-2:48:1:1, destination = topic://topic/heartBeat, transactionId = null, expiration = 0, timestamp = 1330946560406, arrival = 0, brokerInTime = 1330946560406, brokerOutTime = 1330946560406, correlationId = null, replyTo = null, persistent = true, type = null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, content = null, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 1024, properties = null, readOnlyProperties = true, readOnlyBody = true, droppable = false, text = 15}
2012-03-05 12:23:58,327 INFO [org.nuclos.client.jms.WeakReferenceMessageListener] onMessage: Received message from topic topic.localizationChanges: ActiveMQTextMessage {commandId = 5, responseRequired = true, messageId = ID:NuclosBasis-1606-1330937557468-2:49:1:1:1, originalDestination = null, originalTransactionId = null, producerId = ID:NuclosBasis-1606-1330937557468-2:49:1:1, destination = topic://topic/localizationChanges, transactionId = null, expiration = 0, timestamp = 1330946630812, arrival = 0, brokerInTime = 1330946630812, brokerOutTime = 1330946630812, correlationId = ALL_USERS, replyTo = null, persistent = true, type = null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, content = null, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 1024, properties = null, readOnlyProperties = true, readOnlyBody = true, droppable = false, text = flush}
for org.nuclos.client.common.LocaleDelegate@1deadf0
2012-03-05 12:23:58,327 INFO [org.nuclos.client.common.LocaleDelegate] onMessage org.nuclos.client.common.LocaleDelegate@1deadf0 RESOURCE_BUNDLE=null
2012-03-05 12:23:58,327 INFO [org.nuclos.client.common.LocaleDelegate] onMessage: cleared cache org.nuclos.client.common.LocaleDelegate@1deadf0
2012-03-05 12:24:07,604 INFO [org.nuclos.client.common.LocaleDelegate] Updated ResourceBundle for cache org.nuclos.client.common.LocaleDelegate@1deadf0
2012-03-05 12:24:08,272 INFO [org.nuclos.client.main.MainController] Setup (refreshed) menu bar
Gruss Martin
5 März 2012 um 17:59 Uhr #5130Martin Schwärzel
TeilnehmerHallo
Anscheinend hat die Version 3.3 noch ein Aktualisierungsproblem. Nach dem Neustart sind plötzlich alle Entitäten vorhanden. :huh:
Problem erledigt.
Gruss Martin
6 März 2012 um 14:02 Uhr #5140Thomas Pasch
TeilnehmerHallo Martin,
dieses Problem konnte ich nachvollziehen und abstellen. Sollte in der nächsten Beta nicht mehr auftreten.
Vielen Dank für deinen Bug Report!
Gruß
aanno
-
AutorBeiträge