nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot connect JIRA to MySQL database

James Shablow_5a7y89

As part of a move/upgrade of data, I have been trying to set up a basic new database with an install of JIRA 4.0.2 following these and these instructions to get a handle on the process. However, when installing JIRA, it automatically starts the service, which leads me to this page. After following all of the instructions, and running the "startup_bundled_jre.bat" file, the resulting Tomcat window stops at "Running JIRA startup checks", as shown below. Any help would be greatly appreciated.

EDIT: It appears to have something to do with the jdbc driver, as modifying the line

 driverClassName="com.mysql.jdbc.Driver"

in server.xml produces the result below, but changing that to anything else produces a different result, where JIRA starts, but isn't connected to a database/can't be used.

Jun 27, 2018 8:56:10 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jun 27, 2018 8:56:10 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 300 ms
Jun 27, 2018 8:56:10 AM org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina
Jun 27, 2018 8:56:10 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jun 27, 2018 8:56:10 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.28
Jun 27, 2018 8:56:10 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
2018-06-27 08:56:12,060 main INFO [atlassian.jira.startup.JiraStartupLogger]

****************
JIRA starting...
****************

2018-06-27 08:56:12,220 main INFO [atlassian.jira.startup.JiraStartupLogger]

___ Environment ___________________

JIRA Build : 4.0.2#472
Build Date : Sun Feb 14 00:00:00 PST 2010
JIRA Installation Type : Standalone
Application Server : Apache Tomcat/5.5.28 - Servlet API 2.
4
Java Version : 1.6.0_11 - Sun Microsystems Inc.
Current Working Directory : C:\Program Files (x86)\Atlassian\JIRA
4.0.2
Maximum Allowable Memory : 739MB
Total Memory : 126MB
Free Memory : 120MB
Used Memory : 6MB
Memory Pool: Code Cache : Code Cache: init = 2359296(2304K) use
d = 804800(785K) committed = 2359296(2304K) max = 50331648(49152K)
Memory Pool: PS Eden Space : PS Eden Space: init = 11206656(10944K
) used = 2893912(2826K) committed = 11206656(10944K) max = 85786624(83776K)
Memory Pool: PS Survivor Space : PS Survivor Space: init = 1835008(179
2K) used = 1834200(1791K) committed = 1835008(1792K) max = 1835008(1792K)
Memory Pool: PS Old Gen : PS Old Gen: init = 119341056(116544K)
used = 1129320(1102K) committed = 119341056(116544K) max = 715849728(699072K)
Memory Pool: PS Perm Gen : PS Perm Gen: init = 16777216(16384K)
used = 8921856(8712K) committed = 16777216(16384K) max = 268435456(262144K)
JVM Input Arguments : -XX:MaxPermSize=256m -Xms128m -Xmx768
m -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_
BUFFER=true -Dmail.mime.decodeparameters=true -Djava.util.logging.manager=org.ap
ache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=C:\Program Files
(x86)\Atlassian\JIRA 4.0.2\conf\logging.properties -Djava.endorsed.dirs=C:\Prog
ram Files (x86)\Atlassian\JIRA 4.0.2\common\endorsed -Dcatalina.base=C:\Program
Files (x86)\Atlassian\JIRA 4.0.2 -Dcatalina.home=C:\Program Files (x86)\Atlassia
n\JIRA 4.0.2 -Djava.io.tmpdir=C:\Program Files (x86)\Atlassian\JIRA 4.0.2\temp

___ Java System Properties ______

atlassian.standalone : JIRA
awt.toolkit : sun.awt.windows.WToolkit
catalina.base : C:\Program Files (x86)\Atlassian\JIRA
4.0.2
catalina.home : C:\Program Files (x86)\Atlassian\JIRA
4.0.2
catalina.useNaming : true
common.loader : ${catalina.home}/common/classes,
${catalina.home}/common/i18n/*.jar,
${catalina.home}/common/endorsed/*.ja
r,
${catalina.home}/common/lib/*.jar
file.encoding : Cp1252
file.encoding.pkg : sun.io
java.awt.graphicsenv : sun.awt.Win32GraphicsEnvironment
java.awt.printerjob : sun.awt.windows.WPrinterJob
java.class.version : 50.0
java.home : C:\Program Files (x86)\Atlassian\JIRA
4.0.2\jre
java.io.tmpdir : C:\Program Files (x86)\Atlassian\JIRA
4.0.2\temp
java.naming.factory.initial : org.apache.naming.java.javaURLContext
Factory
java.naming.factory.url.pkgs : org.apache.naming
java.runtime.name : Java(TM) SE Runtime Environment
java.runtime.version : 1.6.0_11-b03
java.specification.name : Java Platform API Specification
java.specification.vendor : Sun Microsystems Inc.
java.specification.version : 1.6
java.util.logging.config.file : C:\Program Files (x86)\Atlassian\JIRA
4.0.2\conf\logging.properties
java.util.logging.manager : org.apache.juli.ClassLoaderLogManager

java.vendor : Sun Microsystems Inc.
java.vendor.url : http://java.sun.com/
java.vendor.url.bug : http://java.sun.com/cgi-bin/bugreport
.cgi
java.version : 1.6.0_11
java.vm.info : mixed mode
java.vm.name : Java HotSpot(TM) Server VM
java.vm.specification.name : Java Virtual Machine Specification
java.vm.specification.vendor : Sun Microsystems Inc.
java.vm.specification.version : 1.0
java.vm.vendor : Sun Microsystems Inc.
java.vm.version : 11.0-b16
mail.mime.decodeparameters : true
org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER : true
os.arch : x86
os.name : Windows Vista
os.version : 6.1
package.access : sun.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.tomcat.,
org.apache.jasper.,
sun.beans.
package.definition : sun.,
java.,
org.apache.catalina.,
org.apache.coyote.,
org.apache.tomcat.,
org.apache.jasper.
server.loader : ${catalina.home}/server/classes,
${catalina.home}/server/lib/*.jar
shared.loader : ${catalina.base}/shared/classes,
${catalina.base}/shared/lib/*.jar
sun.arch.data.model : 32
sun.boot.library.path : C:\Program Files (x86)\Atlassian\JIRA
4.0.2\jre\bin
sun.cpu.endian : little
sun.cpu.isalist : pentium_pro+mmx pentium_pro pentium+m
mx pentium i486 i386 i86
sun.desktop : windows
sun.io.unicode.encoding : UnicodeLittle
sun.java.launcher : SUN_STANDARD
sun.jnu.encoding : Cp1252
sun.management.compiler : HotSpot Tiered Compilers
sun.os.patch.level : Service Pack 1
tomcat.util.buf.StringCache.byte.enabled : true
user.country : US
user.dir : C:\Program Files (x86)\Atlassian\JIRA
4.0.2
user.home : C:\Users\<my_name>
user.language : en
user.name : <my_name>
user.timezone : America/Los_Angeles
user.variant :

2018-06-27 08:56:12,240 main INFO [atlassian.jira.startup.JiraStartupLogger]
Running JIRA startup checks.

Accepted answers

James Shablow_5a7y89

Thank everyone for the support. After a week off, I decided to delete everything on the test laptop and start over from scratch in creating the MySQL DB and connecting JIRA to it. After deleting everything and trying again, following the instructions to the letter (including using their example names) I got it to work, and successfully imported the old JIRA data into the test laptop install of JIRA. I did receive several errors during the process, but performing a re-index, and migrating the icons and attachments to the test laptop seems to have worked.

All comments

miikhy

Hi James,

Documentation (https://confluence.atlassian.com/display/JIRA040/Supported+Platforms) sugest a specific driver. Have you tried it?

Also, have you considered moving to an earlier version of Jira, it's not supported anymore and quite hard for us to suggest things as it's very old!

Cheers

miikhy

Specific steps for MySQL:

https://confluence.atlassian.com/display/JIRA040/Connecting+JIRA+to+MySQL

James Shablow_5a7y89

Hey Micky, I am using the recommended driver. The company I work for has been using this version since ~2010, and has not needed to consider upgrading. The server (a desktop) has since moved to a new facility, and a a real server was purchased with the hopes that we could move to the latest version. The end goal is to be running on the latest version of JIRA from the new server, but in order to migrate the data, I need to install the same version on which the data is currently being held, then upgrade to 4.4, then version 6.4, and then should be able to upgrade to the latest version.

As for the link you provided, those are some of the steps that I tried following, and the issue explained above is the result. I have also verified that I have the suggested versions of everything involved.

Andy Heinzer

Hi James,

Could you confirm the specific version of the jdbc driver you are using here? I ask because while that document states these versions of Jira need the 5.1 JDBC driver, I am afraid that the link being used on these old guides is now referring to a different MySQL driver. It seems that MySQL has rolled out the 8.0 version and used the same URL as the old 5.1 drivers were available on. I know that the 8.x jdbc versions won't work with even current versions of jira, much less these older versions of Jira. You can download the latest 5.1.x version from https://dev.mysql.com/downloads/connector/j/5.1.html

I'd be interested to see your $JIRAINSTALL/conf/server.xml as well as the $JIRAINSTALL/logs/catalina.out if Jira is still not starting up as expected here.

Alternative to trying to get this 4.0.x version working, you could instead install a newer version like 4.4.5 first. From there, you can use the Jira config tool in this version in order to configure how Jira will connect to your database. In 4.4.5 Jira uses the dbconfig.xml file instead of the server.xml to define the database connection. You do still need to manually install the MySQL 5.1.x jdbc driver for Jira, but this method could be a viable alternative. If you do try this, I would review the Jira 4.4. Upgrade notes. This version has a number of major changes to Jira, especially in terms of how database connections are made, and how users are managed in Jira, so there are a few extra considerations to make over other upgrades. However if you want to upgrade to the latest, you are going to have to go to a 4.4.x version before you can then upgrade to higher versions.

When Jira starts up connected to an older database version, it will perform the upgrade tasks needed in order to upgrade that database data.

James Shablow_5a7y89

Hello Andrew,

I downloaded version 5.1.46 (same as the link you provided), and copied mysql-connector-java-5.1.46-bin.jar to ..\Atlassian\JIRA 4.0.2\common\lib\ and ..\Atlassian\JIRA 4.0.2\atlassian-jira\WEB-INF\lib.

Below is the modified snip of server.xml:

<Context path="" docBase="${catalina.home}/atlassian-jira" reloadable="false">
 <Resource name="jdbc/JiraDS" auth="Container" type="javax.sql.DataSource"
 username="jirauser"
 password="password"
 driverClassName="com.mysql.jdbc.Driver"
 url="jdbc:mysql://localhost:8080/jiradb?useUnicode=true&amp;characterEncoding=UTF8"
 maxActive="20" 
 validationQuery="Select 1"/>

Below is the modified snip from entityengine.xml:

 <datasource name="defaultDS" field-type-name="mysql"
 helper-class="org.ofbiz.core.entity.GenericHelperDAO"
 check-on-start="true"
 use-foreign-keys="false"
 use-foreign-key-indices="false"
 check-fks-on-start="false"
 check-fk-indices-on-start="false"
 add-missing-on-start="true"
 check-indices-on-start="true">
 <jndi-jdbc jndi-server-name="default" jndi-name="java:comp/env/jdbc/JiraDS"/>

Below is a few minutes of data from catalina.out while it is stuck at 'Running JIRA startup checks.":

Jun 27, 2018 2:57:29 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jun 27, 2018 2:57:29 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 280 ms
Jun 27, 2018 2:57:29 PM org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina
Jun 27, 2018 2:57:29 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jun 27, 2018 2:57:29 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.28
Jun 27, 2018 2:57:29 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled

Thank you for the help. I am going to try installing a newer version and seeing if I can get the server working with the newer version to rule that out before installing the old version again.

Some other data I saw earlier in the log is as follows:

Jun 27, 2018 10:49:57 AM org.apache.coyote.http11.Http11BaseProtocol init
SEVERE: Error initializing endpoint
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
 at java.net.ServerSocket.bind(ServerSocket.java:319)
 at java.net.ServerSocket.<init>(ServerSocket.java:185)
 at java.net.ServerSocket.<init>(ServerSocket.java:141)
 at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:50)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:293)
 at org.apache.coyote.http11.Http11BaseProtocol.init(Http11BaseProtocol.java:139)
 at org.apache.catalina.connector.Connector.initialize(Connector.java:1017)
 at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
 at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:782)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
 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)
 at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:267)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Jun 27, 2018 10:49:57 AM org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
LifecycleException: Protocol handler initialization failed: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
 at org.apache.catalina.connector.Connector.initialize(Connector.java:1019)
 at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
 at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:782)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
 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)
 at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:267)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Jun 27, 2018 10:49:57 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 280 ms
Jun 27, 2018 10:49:57 AM org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina
Jun 27, 2018 10:49:57 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jun 27, 2018 10:49:57 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.28
Jun 27, 2018 10:49:57 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jun 27, 2018 10:52:09 AM org.apache.coyote.http11.Http11BaseProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Jun 27, 2018 10:52:10 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Jun 27, 2018 10:52:10 AM org.apache.catalina.core.StandardContext stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/] has not been started
Jun 27, 2018 10:52:10 AM org.apache.coyote.http11.Http11BaseProtocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Jun 27, 2018 10:52:16 AM org.apache.catalina.startup.Catalina stopServer
SEVERE: Catalina.stop: 
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at java.net.Socket.<init>(Socket.java:366)
 at java.net.Socket.<init>(Socket.java:180)
 at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:395)
 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)
 at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:344)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:435)
Jun 27, 2018 10:52:18 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jun 27, 2018 10:52:18 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 280 ms
Jun 27, 2018 10:52:18 AM org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina
Jun 27, 2018 10:52:18 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jun 27, 2018 10:52:18 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.28
Jun 27, 2018 10:52:18 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jun 27, 2018 10:52:31 AM org.apache.coyote.http11.Http11BaseProtocol init
SEVERE: Error initializing endpoint
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
 at java.net.ServerSocket.bind(ServerSocket.java:319)
 at java.net.ServerSocket.<init>(ServerSocket.java:185)
 at java.net.ServerSocket.<init>(ServerSocket.java:141)
 at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:50)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:293)
 at org.apache.coyote.http11.Http11BaseProtocol.init(Http11BaseProtocol.java:139)
 at org.apache.catalina.connector.Connector.initialize(Connector.java:1017)
 at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
 at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:782)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
 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)
 at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:267)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Jun 27, 2018 10:52:31 AM org.apache.catalina.startup.Catalina load
SEVERE: Catalina.start
LifecycleException: Protocol handler initialization failed: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
 at org.apache.catalina.connector.Connector.initialize(Connector.java:1019)
 at org.apache.catalina.core.StandardService.initialize(StandardService.java:578)
 at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:782)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:504)
 at org.apache.catalina.startup.Catalina.load(Catalina.java:524)
 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)
 at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:267)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Jun 27, 2018 10:52:31 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 280 ms
Jun 27, 2018 10:52:31 AM org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina
Jun 27, 2018 10:52:31 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jun 27, 2018 10:52:31 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.28
Jun 27, 2018 10:52:31 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jun 27, 2018 10:54:28 AM org.apache.catalina.startup.Catalina stopServer
SEVERE: Catalina.stop: 
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
 at java.net.Socket.connect(Socket.java:519)
 at java.net.Socket.connect(Socket.java:469)
 at java.net.Socket.<init>(Socket.java:366)
 at java.net.Socket.<init>(Socket.java:180)
 at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:395)
 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)
 at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:344)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:435)
Jun 27, 2018 10:54:31 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jun 27, 2018 10:54:31 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 290 ms
Jun 27, 2018 10:54:31 AM org.apache.catalina.realm.JAASRealm setContainer
INFO: Set JAAS app name Catalina

Andy Heinzer

Did some more research on this error and came across this post: https://stackoverflow.com/questions/3947555/java-net-socketexception-unrecognized-windows-sockets-error-0-jvm-bind-jboss

It appears that this can be a common error generated on system that have both IPv4 and IPv6 stacks in use. It might be that Jira is trying to use that ipv6 address and Java in that version is not yet ready to support that. The work-around is to set a JVM startup option of

-Djava.net.preferIPv4Stack=true

Steps on how you set this property can vary depending on how Jira is started (service vs bat file) Please see Setting properties and options on startup for details on where to set this.

James Shablow_5a7y89

Thank you for the help Andrew. I will try this today if I have time, otherwise I will try it when I get back from vacation over the 4th, and let you know.

James Shablow_5a7y89

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

tomcat

database

administration

mysql

startup