Uncommissioned Space after recompile

Poster Content
nk4um User
Posts: 92
January 4, 2013 22:27Found the problem to uncommissioned space.

My mistake. We were checking in class files and I was using JDK1.6 and some colleagues were using jdk1.7. When some classes were in 1.6 compiled form and others were in 1.7 compiled form, then the recommission failed – although the restart worked.

We have resolved the problem by all getting on the same JDK version:)

Gary

Like · Post Reply
nk4um Moderator
Posts: 901
January 4, 2013 15:23

Hi Gary - Happy New Year. Thanks for sharing this. Are you using a dynamic import in the space that doesn't get commissioned? Do you see any warnings in the logs - possibly related to META requests?

Can you please share your module with us (send it in email). It would help us to be able to advise you and also Tony is currently doing a deep review of the commissioning life-cycle of modules, so it might be a corner case we can cover.

Cheers,

Peter

Like · Post Reply
nk4um User
Posts: 92
January 4, 2013 14:59Uncommissioned Space after recompile

Just recently I have been getting an error - Uncommissioned Space Attempted to access space Data Access - Componentization Module that is either uncommissioned or has been decommissioned. This happens after I recompile java classes or modify module.xml but I do not have a problem when making changes to other resources. It appears that the dynamic recommissioning of the space is not working. I do not see any errors in the standard out. This was working, but now every recompile means I have to restart NK. Restarting NK commissions the space correctly.

Any ideas?

Like · Post Reply