Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Linux \ JIRA 3.6.2 Upgrade from older version to the new version 6.0.8     - How to Install Focuswriter 1.4.5 (Linux)

- Oracle capability i / o (stress test database server i / o performance) (Database)

- B-tree - ideas and implementation of C language code (Programming)

- Ubuntu 12.04 64-bit installation Redmine + Git + ReviewBoard (Linux)

- Linux file system management partition, format, mount - label mount (Linux)

- Ganglia Python plug-in the process of writing notes (Linux)

- Linux mention the right notes (Linux)

- Ubuntu: HDF5 error: HDF5 header version does not match with the HDF5 library (Linux)

- C ++ constant definition (Programming)

- Android using SVG vector graphics to create cool animation effects (Programming)

- Manually create Oracle Database Explanations (Database)

- How to disable IPv6 in the CentOS 7 (Linux)

- Postgres-X2 deployment steps (Database)

- Nginx high concurrency optimization ideas (Server)

- Java uses JDBC connect database (Programming)

- RHEL7 Apache MPM configuration (Server)

- How to add and delete bookmarks in Ubuntu (Linux)

- Why JavaScript basic types can invoke methods (Programming)

- CentOS installation pycurl (Linux)

- Linux development environment to build and use the directory structure and file --Linux (Linux)

 
         
  JIRA 3.6.2 Upgrade from older version to the new version 6.0.8
     
  Add Date : 2018-11-21      
         
         
         
  Preface:

Atlassian JIRA is the company produced items and transaction tracking tools are widely used in bug tracking, customer service, requirements gathering, approval process, task tracking, project tracking and agility in the field of management.

The company had to use the JIRA 3.6.2 release, Atlassian official deprecated JIRA 4.4 the previous version, there are loopholes in the previous version also no longer being updated, colleagues have already installed the JIRA6.0.8 version, the new version of JIRA interface flat designed to support mobile client browser, it is consistent with the style of the mobile Internet business, now JIRA upgrade to a new version of JIRA 6.1.7, but the migration data, direct migration from 3.6.2 to 6.0.8 fails, google for a long time, only to find the need to convert the data in 4.4.5 above, look, look at this record data migration steps.

Ideas: (1) installation Jira4.4.5; (2), the Jira3.6.2 data into Jira4.4.5 before export; (3), and then export the data from the import 4.4.5 to 6.0.8 version This completes the migration of data, the upgrade is done.

Preparatory work, JIRA3.6.2 and JIRA6.0.8 has been installed, you also need to install an intermediate version 4.4.5 is over

1, download Jira4.4.5

Jira Download: http: //pan.baidu.com/s/1pJJltpD

2, the installation Jira4.4.5

[Root @ name01 ~] # tar -xvf atlassian-jira-4.4.5.tar.gz

[Root @ name01 ~] # cd atlassian-jira-4.4.5-standalone /

[Root @ name01 atlassian-jira-4.4.5-standalone] # find / -name start-jira.sh

/root/atlassian-jira-4.4.5-standalone/bin/start-jira.sh

[Root @ name01 atlassian-jira-4.4.5-standalone] #

[Root @ name01 atlassian-jira-4.4.5-standalone] #

[Root @ name01 atlassian-jira-4.4.5-standalone] # /root/atlassian-jira-4.4.5-standalone/bin/start-jira.sh

To run JIRA in the foreground, start the server with start-jira.sh -fg

Server startup logs are located in /root/atlassian-jira-4.4.5-standalone/logs/catalina.out

executing as current user

 

      MMMMMMMMMMM., MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMM. OMM. ~ MM .. MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMDMMZ7MMMMMMMMN7DMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMDMMMMMMMMMMMMMMMMMNMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMZ IMMM ..MMN =, 8MO 8 IN + DM8? MMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMM ..OI. 8I ... MMMO 8 IN M7, MMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMN,. + MMMMMO 8 IN = O M ~ ~ .. $ MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMM ~ ... + MMMMMMO 8 IN.. IN I .. + MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMMMI OMMMMMMMO 8 IN:. =, O = 8 MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMD ... .MMMMMMO 8 IN = O + .MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMM, = N .7MMMM ~ 8 IN = O:... = M .MMMMMMMMMMMMMMMMMMMMMMMM.

      . MMMMMMM, MMD + MMM =:.. $ M IN = O, IM: .MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

 

 __ __ __ _ __

 \ \ / / ___ __ __ / / __ _____ _ ____ (_) ___________ _____ _____ / /

  \ / __ \ / / / / / __ \ / __ `/ | / / _ \ / / ___ / ___ / / / / _ \ / ___ / /

  / / / _ / / / _ / / / / / / / _ / / | | / / __ / / (__ | __) / _ / / __ (__) _ /

 / _ / \ ____ / \ __, _ / / _ / / _ / \ __, _ / | ___ / \ ___ / / _ / ____ / ____ / \ __, _ / \ ___ / ____ (_)

 

JIRA Standalone Edition

  Version: 4.4.5

             

Detecting JVM PermGen support ...

PermGen switch is supported. Setting to 256m

 

If you encounter issues starting or stopping JIRA Standalone Edition, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide

 

Using CATALINA_BASE: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_HOME: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_TMPDIR: /root/atlassian-jira-4.4.5-standalone/temp

Using JRE_HOME: /usr/lib/jvm/jdk1.7.0_60/jre

Using CLASSPATH: /root/atlassian-jira-4.4.5-standalone/bin/bootstrap.jar

Using CATALINA_PID: /root/atlassian-jira-4.4.5-standalone/work/catalina.pid

[Root @ name01 atlassian-jira-4.4.5-standalone] #

3, Jira4.4.5 configuration

After installation you can directly access http://192.168.171.230:8080/ carried Jira configuration steps.

3.1 Access error problem

If you access this page appears, because we have not yet configured JIRA HOME path, you need to set java_home path, go see the next JAVA_HOME path:

[Root @ name01 atlassian-jira-4.4.5-standalone] # echo $ JAVA_HOME

/usr/lib/jvm/jdk1.7.0_60

[Root @ name01 atlassian-jira-4.4.5-standalone] #

Find jira profile

[Root @ name01 atlassian-jira-4.4.5-standalone] # find /root/atlassian-jira-4.4.5-standalone -name jira-application.properties

/root/atlassian-jira-4.4.5-standalone/atlassian-jira/WEB-INF/classes/jira-application.properties

[Root @ name01 atlassian-jira-4.4.5-standalone] #

[Root @ name01 atlassian-jira-4.4.5-standalone] # vim /root/atlassian-jira-4.4.5-standalone/atlassian-jira/WEB-INF/classes/jira-application.properties

# Do not modify this file unless instructed. It is here to store the location of the JIRA home directory only and is typically written to by the installer.

jira.home = /usr/lib/jvm/jdk1.7.0_60

 

In addition on the back jira.home = JAVA_HOME path, save the configuration file and then restart JIRA.

3.2, configure jira.home restarted Jira

[Root @ name01 atlassian-jira-4.4.5-standalone] # /root/atlassian-jira-4.4.5-standalone/bin/shutdown.sh

 

      MMMMMMMMMMM., MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMM. OMM. ~ MM .. MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMDMMZ7MMMMMMMMN7DMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMDMMMMMMMMMMMMMMMMMNMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMZ IMMM ..MMN =, 8MO 8 IN + DM8? MMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMM ..OI. 8I ... MMMO 8 IN M7, MMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMN,. + MMMMMO 8 IN = O M ~ ~ .. $ MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMM ~ ... + MMMMMMO 8 IN.. IN I .. + MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMMMI OMMMMMMMO 8 IN:. =, O = 8 MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMD ... .MMMMMMO 8 IN = O + .MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMM, = N .7MMMM ~ 8 IN = O:... = M .MMMMMMMMMMMMMMMMMMMMMMMM.

      . MMMMMMM, MMD + MMM =:.. $ M IN = O, IM: .MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

 

 __ __ __ _ __

 \ \ / / ___ __ __ / / __ _____ _ ____ (_) ___________ _____ _____ / /

  \ / __ \ / / / / / __ \ / __ `/ | / / _ \ / / ___ / ___ / / / / _ \ / ___ / /

  / / / _ / / / _ / / / / / / / _ / / | | / / __ / / (__ | __) / _ / / __ (__) _ /

 / _ / \ ____ / \ __, _ / / _ / / _ / \ __, _ / | ___ / \ ___ / / _ / ____ / ____ / \ __, _ / \ ___ / ____ (_)

 

JIRA Standalone Edition

  Version: 4.4.5

               

Detecting JVM PermGen support ...

PermGen switch is supported. Setting to 256m

 

If you encounter issues starting or stopping JIRA Standalone Edition, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide

 

Using CATALINA_BASE: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_HOME: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_TMPDIR: /root/atlassian-jira-4.4.5-standalone/temp

Using JRE_HOME: /usr/lib/jvm/jdk1.7.0_60/jre

Using CLASSPATH: /root/atlassian-jira-4.4.5-standalone/bin/bootstrap.jar

Using CATALINA_PID: /root/atlassian-jira-4.4.5-standalone/work/catalina.pid

[Root @ name01 atlassian-jira-4.4.5-standalone] #

Restart jira:

[Root @ name01 atlassian-jira-4.4.5-standalone] # /root/atlassian-jira-4.4.5-standalone/bin/start-jira.sh

 

To run JIRA in the foreground, start the server with start-jira.sh -fg

 

Server startup logs are located in /root/atlassian-jira-4.4.5-standalone/logs/catalina.out

executing as current user

 

      MMMMMMMMMMM., MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMM. OMM. ~ MM .. MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMDMMZ7MMMMMMMMN7DMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMDMMMMMMMMMMMMMMMMMNMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMZ IMMM ..MMN =, 8MO 8 IN + DM8? MMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMM ..OI. 8I ... MMMO 8 IN M7, MMMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMN,. + MMMMMO 8 IN = O M ~ ~ .. $ MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMM ~ ... + MMMMMMO 8 IN.. IN I .. + MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMMMI OMMMMMMMO 8 IN:. =, O = 8 MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMD ... .MMMMMMO 8 IN = O + .MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMM, = N .7MMMM ~ 8 IN = O:... = M .MMMMMMMMMMMMMMMMMMMMMMMM.

      . MMMMMMM, MMD + MMM =:.. $ M IN = O, IM: .MMMMMMMMMMMMMMMMMMMMMMMM

      MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

 

 __ __ __ _ __

 \ \ / / ___ __ __ / / __ _____ _ ____ (_) ___________ _____ _____ / /

  \ / __ \ / / / / / __ \ / __ `/ | / / _ \ / / ___ / ___ / / / / _ \ / ___ / /

  / / / _ / / / _ / / / / / / / _ / / | | / / __ / / (__ | __) / _ / / __ (__) _ /

 / _ / \ ____ / \ __, _ / / _ / / _ / \ __, _ / | ___ / \ ___ / / _ / ____ / ____ / \ __, _ / \ ___ / ____ (_)

 

JIRA Standalone Edition

  Version: 4.4.5

                 

Detecting JVM PermGen support ...

PermGen switch is supported. Setting to 256m

 

If you encounter issues starting or stopping JIRA Standalone Edition, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide

 

Using CATALINA_BASE: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_HOME: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_TMPDIR: /root/atlassian-jira-4.4.5-standalone/temp

Using JRE_HOME: /usr/lib/jvm/jdk1.7.0_60/jre

Using CLASSPATH: /root/atlassian-jira-4.4.5-standalone/bin/bootstrap.jar

Using CATALINA_PID: /root/atlassian-jira-4.4.5-standalone/work/catalina.pid

[Root @ name01 atlassian-jira-4.4.5-standalone] #

3.3, the database configuration jira

Access http://192.168.171.xxx:8080/ again

Click Next, enter the information, ready to create DB

3.4, the error message

Reclose start, given as follows:

......

Using CATALINA_BASE: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_HOME: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_TMPDIR: /root/atlassian-jira-4.4.5-standalone/temp

Using JRE_HOME: /usr/lib/jvm/jdk1.7.0_60/jre

Using CLASSPATH: /root/atlassian-jira-4.4.5-standalone/bin/bootstrap.jar

Using CATALINA_PID: /root/atlassian-jira-4.4.5-standalone/work/catalina.pid

Existing PID file found during start.

Tomcat appears to still be running with PID 32194. Start aborted.

[Root @ name01 logs] #

Kill off the already existing process 32194

[Root @ name01 logs] # kill -9 32194

[Root @ name01 logs] #

Jira then restart the process, start the following information:

Using CATALINA_BASE: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_HOME: /root/atlassian-jira-4.4.5-standalone

Using CATALINA_TMPDIR: /root/atlassian-jira-4.4.5-standalone/temp

Using JRE_HOME: /usr/lib/jvm/jdk1.7.0_60/jre

Using CLASSPATH: /root/atlassian-jira-4.4.5-standalone/bin/bootstrap.jar

Using CATALINA_PID: /root/atlassian-jira-4.4.5-standalone/work/catalina.pid

Existing PID file found during start.

Removing / clearing stale PID file.

[Root @ name01 logs] #

 

View the log file, the following information:

[Root @ name01 logs] # more catalina.out

September 11, 2014 5:41:41 PM org.apache.catalina.core.AprLifecycleListener init

Information: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: / usr / java / packages / lib / amd64: / usr / lib64: / l

ib64: / lib: / usr / lib

September 11, 2014 5:41:41 PM org.apache.coyote.http11.Http11Protocol init

Information: Initializing Coyote HTTP / 1.1 on http-8080

September 11, 2014 5:41:41 PM org.apache.catalina.startup.Catalina load

Information: Initialization processed in 1007 ms

September 11, 2014 5:41:41 PM org.apache.catalina.realm.JAASRealm setContainer

Information: Set JAAS app name Catalina

September 11, 2014 5:41:41 PM org.apache.catalina.core.StandardService start

Information: Starting service Catalina

September 11, 2014 5:41:41 PM org.apache.catalina.core.StandardEngine start

Information: Starting Servlet Engine: Apache Tomcat / 6.0.32

2014-09-11 17: 41: 43,504 main INFO [jira.config.database.SystemTenantDatabaseConfigurationLoader] Reading database configuration from / usr / lib / jvm / jdk1.7.0_60 / dbconfig.xml

2014-09-11 17: 41: 44,076 main INFO [atlassian.jira.startup.JiraStartupLogger]

Delete this dbconfig.xml, close jira, then restart, this time to start normal

See this page it means JIRA service normal start, followed by the process according to the installation wizard to configure the installation.

3.5, DB reconfiguration procedure

See Database Configuration, Internal and External have two options, we want to use External, select the external database.

First establish jira database and account password:

mysql>

mysql> create database jira445;

Query OK, 1 row affected (0.00 sec)

 

mysql>

. Mysql> GRANT ALL ON jira445 * TO jira_user @ '%' IDENTIFIED BY 'jira_user1809';

Query OK, 0 rows affected (0.16 sec)

mysql>

Interface configured database connection information

Readily Clicking on "Test Connection" testing the database connection, the connection is normal

Click the Next button, given as follows:

javax.servlet.ServletException: com.atlassian.util.concurrent.LazyReference $ InitializationException: com.opensymphony.module.propertyset.PropertyImplementationException: SQL Exception while executing the following: SELECT ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype FROM propertyentry WHERE ENTITY_NAME = ? AND ENTITY_ID =? (Table 'jira445.propertyentry' does not exist)

To download:

# Wget -c href = "http://cdn.mysql.com/Downloads/Connector-J/mysql-connector-java-5.1.29.tar.gz

# Tar zxvf mysql-connector-java-5.1.29.tar.gz

After extracting the directory mysql-connector-java-5.1.29-bin.jar copied to the lib directory /opt/atlassian-jira-4.4.5-standalone/lib/ in JIRA

Restart jira, or reported the same mistakes.

See jira to the error log information, see the following:

[Root @ name01 logs] # more /root/atlassian-jira-4.4.5-standalone/logs/catalina.out

......

CREATE TABLE portletconfiguration (ID DECIMAL (18,0) NOT NULL, PORTALPAGE DECIMAL (18,0), PORTLET_ID VARCHAR (255), COLUMN_NUMBER DECIMAL (9,0), positionseq DECIMAL (9,0), GADGET_XML TEXT, COLOR V

ARCHAR (255), CONSTRAINT PK_portletconfiguration PRIMARY KEY (ID))

Error was: java.sql.SQLException: The MySQL server is running with the --read-only option so it can not execute this statement

[] The database is not set to read-only manner.

mysql> set global read_only = 0;

Query OK, 0 rows affected (0.01 sec)

mysql>

After reconstruction jira445 library restart jira, re-initialize the database

On the next page, enter the code:

Authorization code:

AAABMQ0ODAoPeJxtUMlOwzAQvfsrLHF2laSlVStZwiQ + hGZTFlS4mTAFo8SJbKeif0 / StAcQ0lxm3

rxl5q4cABfQY3c91m652a022C9K7DnuCgVgai17KztFn8KcoS + pxSIZ2jfQ6bEyoA0lLvI1iGknE

BboRCTOlrhr5HfKitomogXaNxN3Fhhn8gTU6gFuOzwWsqFWthPd2breg + 3aRd21iJ9EM1zk6VE0B

maJSNagDJTnHi7yfhrHPPdDFv3C + bu8MHlS8jzLw4KjZkaex + wT4qHRWVlQQtXAv3upz / MZy + WGu

B7x7lHBE / qSVjhme45jjhkuWIAzlgRsgVL9IZQ0c8C + wRaMRQXoE + gwoI9pdSD8wPYkfQ0zcogyj

q7RRjQKg1v3v3M26PpTGPjz2B8tAYyAMCwCFGiKwG9qA + 2ksL7mkMIrV80z + un8AhRu0CryeqTv8

LIZstOPg / B3240BnQ == X02fb

Click the "Next" button, the next step, set the administrator account, the user name admin password admin

Next, temporarily set up e-mail notification

Click Next, being given as shown in Section 3.6

3.6, JIRA Access Constraints Error Handling

You can not access JIRA at present.

description

Time

Level

Exception

The current license is too old to install this version of JIRA (4.4.5)

Edit License or proceed under Evaluation Terms

Click Edit License or proceed under Evaluation Terms in, need to fill in an authorization code, re Proceed job

Enter https://my.atlassian.com/license/evaluation page, log in, select Licen go,

Select Jira (Server)

Then the next step, and then enter the value Server ID and the Organization Name, click the "Generate License" button to create the authorization code

After then generate an authorization code, Evaluations New Evaluation License, click on the back of New Evaluation License, go to the right to see the authorization code:

AAABBw0ODAoPeNptkFtLxDAQhd / zKwI + R9Kwy66FPKxthGhvtF0p4kuso0a6sUwvuP / edissyj4MD

HPOfHOYqzu0tICWeoJy4a + FzzkNwpIK7q1ICF2Ntu3tl5P3Ot89 + 1SNphnMPCEBwqkJTQ9y9jN + w

zxBPi2a68jW4DpQr / a0rZJS5VmuC0XOBNnjAH / s5bGFxBxABmkcqzzQu2jRTd3bEZaFZvE + AnYzR

JDYWNeDM64G9d1aPJ4TeXxOlOK7cbZbjrbNgkyGwwtg + rbvJpBkHikAR0Adytt0XzFV7R5Y + qQzV

kWZIoVK5FQsWq03YrvdkN / Ekz3S4SXlcpRswPrDdPD / aT + P1nzDMC0CFQCM9 + 0LlHVNnZQnSTwuR

O3eK + 2gVgIUCteTs4Q3khIgrnsY64hxYB / d8bM = X02dh

Then copy the license key to activate it, enter the authorization code input box, click the Proceed button, the following tips for success:

Update License

Your license has been successfully updated. Please restart your server so that all necessary changes can take effect.

Changes will not take place until server is restarted.

Click here when the server is restarted.

3.7 Access error

Restart jira, then enter http://192.168.171.xxx:8080/

View background tomcat to log

2014-09-12 16: 48: 46,012 main ERROR [atlassian.plugin.manager.PluginEnabler] Unable to enable plugin com.atlassian.sal.jira

java.lang.ClassCastException: [Ljava.lang.String; can not be cast to java.lang.Comparable

        at org.apache.felix.framework.resolver.CandidateComparator.compare (CandidateComparator.java:46)

        at org.apache.felix.framework.resolver.CandidateComparator.compare (CandidateComparator.java:26)

        at java.util.TreeMap.compare (TreeMap.java:1188)

        at java.util.TreeMap.put (TreeMap.java:531)

        at java.util.TreeSet.add (TreeSet.java:255)

        at java.util.AbstractCollection.addAll (AbstractCollection.java:342)

        at java.util.TreeSet.addAll (TreeSet.java:312)

        at org.apache.felix.framework.FelixResolverState.getCandidates (FelixResolverState.java:759)

Split command:

tar czvf jdk-6u35-linux-x64.bin.tar.gz jdk-6u35-linux-x64.bin

split -b 40M ./jdk-6u35-linux-x64.bin.tar.gz ./jdk-6u35-linux-x64.bin.tar.gz.

Combine command:

cat jdk-6u35-linux-x64.bin.tar.gz.a *> jdk-6u35-linux-x64.bin.tar.gz

tar xf jdk-6u35-linux-x64.bin.tar.gz

Increase the executable permissions

chmod + x jdk-6u35-linux-x64.bin

Unzip

./jdk-6u35-linux-x64.bin

Will extract good jdk1.6.0_35 copy the folder with the highest privilege to / usr / lib / jvm directory:

$ Sudo cp -R jdk1.6.0_35 / usr / lib / jvm

(note:

    If: jvm directory does not exist, please create the highest authority jvm directory:

        $ Sudo mkdir / usr / lib / jvm

)

Set the environment variable in the .profile file $ HOME JAVA_HOME:

$ Cd ~

$ Vi / etc / profile

(

Add to:

export JAVA_HOME = / usr / lib / jvm / jdk1.6.0_35

export JRE_HOME = $ {JAVA_HOME} / jre

export CLASSPATH =:. $ {JAVA_HOME} / lib: $ {JRE_HOME} / lib

export PATH = $ {JAVA_HOME} / bin: $ PATH)

Parameters take effect immediately

 source / etc / profile

Verify java version number

[Root @ name01 java] # java -version

java version "1.6.0_35"

Java (TM) SE Runtime Environment (build 1.6.0_35-b10)

Java HotSpot (TM) 64-Bit Server VM (build 20.10-b01, mixed mode)

[Root @ name01 java] # javac -version

javac 1.6.0_35

[Root @ name01 java] #

Jira then modify the jdk version jdk6:

[Root @ name01 java] # vim /root/atlassian-jira-4.4.5-standalone/atlassian-jira/WEB-INF/classes/jira-application.properties

# Do not modify this file unless instructed. It is here to store the location of the JIRA home directory only and is typically written to by the installer.

jira.home = /usr/lib/jvm/jdk1.6.0_35

~

Solve the JDK, repeat steps 3.1 to 3.7, the last few steps are as follows

3.8, log an error

The Gadget Dashboard bundled plugin is not available. To ensure the Gadget Dashboard plugin is enabled, please contact your < a href="/secure/ContactAdministrators!default.jspa"> JIRA administrators.

If you think this information is incorrect, please contact your administrator please contact your JIRA administrators {1} to obtain the required permissions.

Jira need to re-compile and install, that is before the jdk7 installed, and now for jdk version to jdk6, so jira also need to re-compile and install it, repeat all the steps before 1-> 3

3.9, JIRA restart error

The reason is that there is no use shutdown.sh to close jira, so it is best to use start-jira.sh start using shutdown.sh closed, the next time you start there would be no problem. If you can not find the installation directory .jira-home.lock file (not necessarily the directory where your installation path), you can use the search function to search for, as follows:

[Root @ name01 logs] # find / -name .jira-home.lock

/usr/lib/jvm/jdk1.6.0_35/.jira-home.lock

[Root @ name01 logs] #

[Root @ name01 logs] # rm -rf /usr/lib/jvm/jdk1.6.0_35/.jira-home.lock

[Root @ name01 logs] #

4, the backup JIRA3.6.2

4.1, select the backup path

Find data backup directory, each menu bar logged in user is not the same, I have here is the "Home" -> "Administration" -> "Backup", you enter the backup page, enter the backup file (put the full path), this jira server installation path in the above, linux server to use linux path /tmp/jira_pl_3.6.2.xml,windows server uses the path windows: D: \ jira_pl_3.6.2.xml.

4.2 Start Backup

Click the Backup button to start the backup, jira data many words, some long time, complete backup

5, the data on the recovery jira3.6.2 version 4.4.5

Step # 4 to copy the backup files to the next /usr/lib/jvm/jdk1.6.0_35/import directory, and then log into 4.4.5 jira panel, find the "System" -> "Restore System", enter the file path restoration and section 3.5 of the License, click on the "restore" button to start recovery.

Recovery given as follows:

< Span color: # 333333; "=" "style =" word-wrap: break-word; font-size: 10pt; "> Either create the paths shown below and reimport, or reimport using default paths.

error

- The index path /usr/lib/jvm/jdk1.6.0_35/D:\JIRA_file\index specified in the backup file is not valid.

- The attachment path /usr/lib/jvm/jdk1.6.0_35/D:\JIRA_file\attach specified in the backup file is not valid.

VIM backup of open files, find vim jira_pl_3.6.2.xml, find D: \ JIRA_file \ string into /usr/lib/jvm/jdk1.6.0_35/import/, as follows:

    < OSPropertyString id = "10006" value = "/ usr / lib / jvm / jdk1.6.0_35 / import / index" />

    < OSPropertyString id = "10007" value = "/ usr / lib / jvm / jdk1.6.0_35 / import / attach" />

< OSPropertyString id = "10009" value = "/ usr / lib / jvm / jdk1.6.0_35 / import / backUp" />

Then, build three directory

[Root @ name01 import] # mkdir /usr/lib/jvm/jdk1.6.0_35/import/index

[Root @ name01 import] # mkdir /usr/lib/jvm/jdk1.6.0_35/import/attach

[Root @ name01 import] # mkdir /usr/lib/jvm/jdk1.6.0_35/import/backUp

[Root @ name01 import] #

Then re-import, OK, no error message, slowly began to import data

6, the backup data 4.4.5 Import data 3.6.2 old version

After the last step has been imported, again in the new 4.4.5 version of the above data backup, enter

Backup completed

7 in 6.0.8 do jira recovery

Including data recovery and restore attachments

Data Recovery 7.1

The solution from the previous step jira_4.4.5.zip backup compression

[Root @ name01 export] # unzip jira_4.4.5.zip

Archive: jira_4.4.5.zip

  inflating: entities.xml

  inflating: activeobjects.xml

[Root @ name01 export] #

The unpacked xml backup file copy on the server Jira6.0.8, began to recover

Consuming about 40 minutes after recovery

7.2, Annex recovery

Go to "Administrator" -> "System"

After the opening, and then pull the bottom left, click on the "Accessories" option, you will see attachment path, the attachment file Jira3.6.2 version under the direct copy over to this directory

OK, finally, JIRA 6.0.8 upgrade from the old version to the new version 3.6.2 is complete.
     
         
         
         
  More:      
 
- Rely on IP chain established Linux firewall (Linux)
- How LUKS encrypted disk / partition to perform remote incremental backup (Linux)
- Oracle RAC node on the expulsion of the inspection process on OEL6.3 (Database)
- Use Markdown editor for document work under Linux (Linux)
- User and user group management Linux Command (Linux)
- Firewall settings oracle remote connection in Linux systems (Linux)
- Security basics: simple analytical framework for Linux system firewall (Linux)
- Several back door and log tool under Linux (Linux)
- Linux server is how to do after the invasion (Linux)
- Java factory pattern (Factory mode) (Programming)
- Linux configuration startup mount: fstab file (Linux)
- Atheros AR8161 / AR8162 network card driver problem solving in CentOS 6.4 (Linux)
- Spring-depth understanding of the various annotations (Programming)
- Create a custom pixel format based on an existing image data BufferedImage (Programming)
- Linux centos rm directory does not prompt (Linux)
- Build Docker based MongoDB replication cluster environment (Database)
- How to recover deleted files in Linux systems (Linux)
- Adjust the size of the hard disk VirtualBox (Linux)
- MySQL display operation control tips (Database)
- ORA-12537: TNS: connection closed error process (Database)
     
           
     
  CopyRight 2002-2020 newfreesoft.com, All Rights Reserved.