[JIRA] [core] (JENKINS-28576) WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

[bcoveny@nycm.com (JIRA)]

Bruce Coveny created an issue

Jenkins / JENKINS-28576 WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes Issue Type: Bug Assignee: Unassigned Components: core Created: 26/May/15 1:18 PM Environment: JENKINS WAR VERSION 1.612 - 1.615 WINDOWS SERVER 2008 R2 ENTERPRISE AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 4.0 GB RAM 64-BIT OPERATION SYSTEM WEBSPHERE APPLICATION SERVER 8.5.5.5 JAVA 1.7.1 Labels: com4j Priority: Blocker Reporter: Bruce Coveny WebSphere crashes when attempting to use newer versions of Jenkins built on Java 7. We have updated to all the latest patches of WebSphere 8.5.5.5 and to the newly released IBM JDK 1.7.1. IBM Support states they have seen similar things with com4j corruption. Is it possible for you to look into what IBM states? Here is IBM's last email. ---------- I have found a similar pattern of corruption like in the old PMRs which was due to the corruption by com4j and its relevant JNI modules. > j9javavm! | charsfrom !j9portlibrary | run | charsfrom !j9portlibraryglobaldata | run | grep corruptedMemoryBlock 0x0: void * corruptedMemoryBlock = !j9x 0x0000000022842120 > j9x 0x0000000022842120,50 0x22842120 : 00000000247781f0 0000000018868160 [ ..w$....´....... ] 0x22842130 : 0000455344740000 000000002351fbd8 [ ..tDSE....Q#.... ] >> 0x22842140 : 0000000000000000 0000000000000020 [ ........ ....... ] Corruption here. Can you please check with com4j and its relevant JNI modules to debug this issue further. --------- Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[dbeck@cloudbees.com (JIRA)]

Daniel Beck updated an issue

Jenkins / JENKINS-28576 WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

Change By: Daniel Beck Labels: com4j  java-ibm

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-28576

Re: WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes I don't think com4j is used anywhere in core. Are you using the Active Directory plugin?

Add Comment

[bcoveny@nycm.com (JIRA)]

Bruce Coveny commented on JENKINS-28576

Re: WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

Yes we do use active directory plugin.

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck updated an issue

Jenkins / JENKINS-28576

WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

Workaround then would be to try using the LDAP Plugin instead. Change By: Daniel Beck Component/s: active-directory-plugin Component/s: core

Add Comment

[bcoveny@nycm.com (JIRA)]

Bruce Coveny commented on JENKINS-28576

Re: WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes Removing the active directory settings made the server stable and not crash. It took some time to get the configuration setup for the LDAP plugin. We have successfully switched to the LDAP Plugin and the server is up and stable under JDK 1.7.

Add Comment

[bcoveny@nycm.com (JIRA)]

Bruce Coveny closed an issue as Fixed

No longer run on WebSphere and use internal server to run.

Jenkins / JENKINS-28576

WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes

Change By: Bruce Coveny Status: Open Closed Resolution: Fixed

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)