History | Log In     View a printable version of the current page.  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word | Printable)

Key: JRA-9085
Type: Third-party issue Third-party issue
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Major Major
Assignee: Unassigned
Reporter: Jeff Turner [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Error deploying data in Weblogic + JDK 1.4.2_08: "Signature did not verify properly"

Created: 18/Jan/06 08:07 PM   Updated: 22/Jan/06 04:28 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Environment:
Windows with Sun JDK 1.4.2_08-b03
Solaris with JDK 1.4.2_08

Participants: Jeff Turner [Atlassian] and Neal Applebaum
Since last comment: 120 weeks, 5 days ago
Resolution Date: 18/Jan/06 08:10 PM
Labels:


 Description  « Hide
Some people have reported errors when using Weblogic's bundled JDK 1.4.2_08. After importing data, JIRA breaks with a NullPointerException, and in the logs one finds: 
2006-01-18 13:00:55,697 WARN [atlassian.license.decoder.LicenseDecoder] Signature did not verify properly.
2006-01-18 13:00:57,509 INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Starting JIRA Professional Edition, Version: 3.1.1-#81
...
2006-01-18 13:01:23,322 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade...
2006-01-18 13:01:23,337 ERROR [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: null
java.lang.NullPointerException        
        at com.atlassian.jira.upgrade.UpgradeManagerImpl.getAllRelevantUpgradeBuildNumbers(UpgradeManagerImpl.java:136)
        at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:385)
        at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:340)
        at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:300)
        at com.atlassian.jira.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:65)
        at weblogic.servlet.internal.WebAppServletContext$FireContextListenerAction.run(WebAppServletContext.java:7044)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
        at weblogic.servlet.internal.WebAppServletContext.notifyCreated(WebAppServletContext.java:1753)
        at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3352)
        at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:6208)
        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:864)
        at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2134)
        at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2175)
        at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2122)
        at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3099)
        at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1768)
        at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:351)
        at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
        ...

If the data is already imported, JIRA may appear to become unlicensed, and updating the license will not work. In the logs, the same error occurs:

2005-11-18 18:25:05,704 WARN [atlassian.license.decoder.LicenseDecoder] Signature did not verify properly.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Jeff Turner [Atlassian] - 18/Jan/06 08:10 PM
Apparently using JDK 1.4.2_05 (recommended for WL8.1 SP4) will get JIRA working. The problem doesn't occur on linux.

If anyone has further information (eg. does 1.4.2_10 work? 1.5?), please could they add it here.


[ Permlink | « Hide ]
Neal Applebaum - 18/Jan/06 09:26 PM
Does this help?
Java Version 1.4.1_05
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.4.1_05-b01
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Server VM
User Name weblogic
System Encoding ISO646-US
Operating System SunOS 5.9
OS Architecture sparc
Application Server Container WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
Database type mssql
Edition Enterprise
Version 3.3.3
Build Number 99

[ Permlink | « Hide ]
Jeff Turner [Atlassian] - 19/Jan/06 05:43 PM
Thanks. Unfortunately SP5 is the latest for Websphere 8.1, and installing it automatically uses the 1.4.2_08 JDK, so the choice is switch JDKs or upgrade to Websphere 9.1.

[ Permlink | « Hide ]
Neal Applebaum - 20/Jan/06 08:46 AM
Was that a typo? I use Weblogic not Websphere. Anyway, I'll keep this issue in mind in case we have problems in the future.

[ Permlink | « Hide ]
Jeff Turner [Atlassian] - 22/Jan/06 04:28 PM
Yes thanks - s/sphere/logic/g


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.12.3-#302) - Bug/feature request - Atlassian news - Contact Administrators