With the release of JIRA 4.4, we'll close the EAP issue. Thanks everyone for your feedback!

@rambanam: The NullPointerException you're seeing is indeed a bug. I've raised JRA-25147 to track this. Thanks for reporting! In the meantime you should be able to work around this by making sure your issues have a "watches" value set in the database (set it to 0 if they don't have a value).

Hi Andrey,

It might also help you to know that if you do not wish to specify the InnoDB database storage engine at a global level (for your MySQL database server), you can specify it just for your individual JIRA database by adding the following parameter to your database URL in JIRA 4.4's dbconfig.xml file:

• sessionVariables=storage_engine=InnoDB

Please see Connecting JIRA to MySQL Manually (for JIRA 4.4) for details.

Cheers,
Giles.

Hi @Chris Lee, the INST project is private, so please continue add comments to this ticket. Apologies for the confusion.

@Mark, thanks for point.

Hi,

i am getting nullpointer exception at following line
watcherManager.startWatching(localUser, issue.getGenericValue());
parameters are valid and not null

watchermanager getting as follows
WatcherManager watcherManager = ComponentManager.getInstance().getWatcherManager();

i am using jira 4.4rc1.

log shows
java.lang.NullPointerException
at com.atlassian.jira.issue.watchers.DefaultWatcherManager.isWatching(DefaultWatcherManager.java:133)
at com.atlassian.jira.issue.watchers.DefaultWatcherManager.updateWatch(DefaultWatcherManager.java:171)
at com.atlassian.jira.issue.watchers.DefaultWatcherManager.startWatching(DefaultWatcherManager.java:50)
at com.moto.jira.gadget.AddWatchers.addWatcher(AddWatchers.java:126)
at com.moto.jira.gadget.AddWatchers.addWatchers(AddWatchers.java:88)
at com.moto.jira.gadget.AddWatchers.getMessage(AddWatchers.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

@Andrey

Looks like you are using the wrong MySQL Storage Engine.
See http://confluence.atlassian.com/pages/viewpage.action?pageId=213059554

Please use the InnoDB storage engine as prescribed in installation docs:
http://confluence.atlassian.com/display/JIRA043/Connecting+JIRA+to+MySQL

Hi Chris,

Regarding your comment:

...er, there doesn't appear to be an INST project - or at least I don't have permission to it.

Please ignore the last paragraph of my previous comment. For the time being, please continue to add any further feedback to this issue.

Cheers,
Giles.

We are trying to upgrade from 4.2.1 to 4.4-rc1 and see in logs next messages:

2011-07-18 12:48:03,308 [main] [@] ERROR o.ofbiz.core.entity.jdbc.DatabaseUtil - Could not create missing indices for entity "GroupAttribute"
2011-07-18 12:48:03,308 [main] [@] ERROR o.ofbiz.core.entity.jdbc.DatabaseUtil - SQL Exception while executing the following:
CREATE INDEX idx_group_attr_dir_name_lval ON cwd_group_attributes (directory_id, attribute_name, lower_attribute_value)
Error was: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes
SQL Exception while executing the following:
CREATE UNIQUE INDEX uk_group_attr_name_lval ON cwd_group_attributes (group_id, attribute_name, lower_attribute_value)
Error was: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes
2011-07-18 12:48:03,309 [main] [@] ERROR o.ofbiz.core.entity.jdbc.DatabaseUtil - Could not create missing indices for entity "Membership"
2011-07-18 12:48:03,309 [main] [@] ERROR o.ofbiz.core.entity.jdbc.DatabaseUtil - SQL Exception while executing the following:
CREATE INDEX idx_mem_dir_parent_child ON cwd_membership (lower_parent_name, lower_child_name, membership_type, directory_id)
Error was: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes
2011-07-18 12:48:03,309 [main] [@] ERROR o.ofbiz.core.entity.jdbc.DatabaseUtil - Could not create missing indices for entity "UserAttribute"
2011-07-18 12:48:03,309 [main] [@] ERROR o.ofbiz.core.entity.jdbc.DatabaseUtil - SQL Exception while executing the following:
CREATE INDEX idx_user_attr_dir_name_lval ON cwd_user_attributes (directory_id, attribute_name, lower_attribute_value)
Error was: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes

Our DBA said what this index will created normaly if encoding of text fields will 7bit length. But in our case there are UTF-8 encoding and it doesn't fit maximum index length for MySQL 5.1.48.

I would like to get a feedback on my comments from 7/Jul/11 and 10/Jul/11. Since now I don't see any progress concerning these issues (most of them are focusing on usability).

Kind regards
Holger