199 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
ilog.rules.teamserver.model.IlrConnectException Caused by: java.lang.NullPointerException
Sun, Jul 16th 2017 55
WebSphere Application Server - Transaction Logs - getting it wrong
Sun, Jul 16th 2017 54
XAException occurred. Error code is: XAER_RMERR (-3). Exception is:
Sun, Jul 16th 2017 84
TypeError: __add__ nor __radd__ defined for these operands
Fri, Jul 14th 2017 42
CWMCB0012W: An inconsistent configuration has been detected for data source jdbc/TeamWorksDB
Fri, Jul 14th 2017 35
IBM BPM - "CWSCA8095W: Unable to find class..." seen during serviceDeploy process
Fri, Jul 14th 2017 42
java.sql.SQLException: Could not commit with auto-commit set on
Fri, Jul 14th 2017 79
Top 10
XAException occurred. Error code is: XAER_RMERR (-3). Exception is:
Sun, Jul 16th 2017 84
java.sql.SQLException: Could not commit with auto-commit set on
Fri, Jul 14th 2017 79
ilog.rules.teamserver.model.IlrConnectException Caused by: java.lang.NullPointerException
Sun, Jul 16th 2017 55
WebSphere Application Server - Transaction Logs - getting it wrong
Sun, Jul 16th 2017 54
Transport Layer Security (TLS) 1.2 and SoapUI
Fri, Jun 12th 2015 44
IBM BPM - "CWSCA8095W: Unable to find class..." seen during serviceDeploy process
Fri, Jul 14th 2017 42
TypeError: __add__ nor __radd__ defined for these operands
Fri, Jul 14th 2017 42
CWMCB0012W: An inconsistent configuration has been detected for data source jdbc/TeamWorksDB
Fri, Jul 14th 2017 35
Executing external Python/Jython scripts from within WebSphere Application Server's wsadmin tool
Thu, Feb 27th 2014 34
Hmmm, macOS Sierra and XQuartz and X11
Thu, Oct 27th 2016 34


java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=com/ibm/rules/res/xu/spi/internal/XUResourceAdapter
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
   

Not sure why I've not seen this before, but that's a problem for another day.

During a build of an IBM Operational Decision Manager (ODM) 8.8.1 environment, I saw this: -

...
  [wsadmin] GBRPT0017I: Install resource adapter on the node: Node1 
  [wsadmin] WASX7017E: Exception received while running file "/opt/ibm/WebSphereProfiles/Dmgr01/bin/rules/configureDSRulesNetworkDeployer.py"; exception information: com.ibm.websphere.management.exception.ConfigServiceException
  [wsadmin] javax.management.MBeanException
  [wsadmin] com.ibm.websphere.management.exception.AdminException
  [wsadmin] java.lang.UnsupportedClassVersionError: java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=com/ibm/rules/res/xu/spi/internal/XUResourceAdapter, offset=6

  [wsadmin] Java Result: 105

BUILD SUCCESSFUL
Total time: 2 minutes 14 seconds

...

during the build of the Rule Execution Server (RES) cluster.

This is what I had installed: -

/opt/ibm/InstallationManager/eclipse/tools/imcl listAvailablePackages -repositories /mnt/disk1/WAS,/mnt/disk1/WASJDK7,/mnt/disk2/DecisionServerRules,/mnt/disk2/ProfileTemplateRules

com.ibm.websphere.ND.v85_8.5.5009.20160225_0435
com.ibm.websphere.IBMJAVA.v70_7.0.9030.20160224_1826
com.ibm.websphere.odm.ds.rules.v88_8.8.1000.20160527_0819
com.ibm.websphere.odm.pt.rules.v88_8.8.1000.20160527_0949


and this is how I was creating the cluster: -

export ODM_HOME=/opt/ibm/ODM881/
/opt/ibm/WebSphereProfiles/Dmgr01/bin/configureDSCluster.sh -dmgrAdminUsername wasadmin -dmgrAdminPassword passw0rd -clusterPropertiesFile ~/configureDSCluster.properties -targetNodeName Node1 -dmgrHostName `hostname` -dmgrPort 8879


Thankfully, the internet had the solution: -

which said, in part: -

<snip>
The problem occured because profiles are created by default with Java 6 and ODM 8.8 components require Java 7.

To make sure that WAS profiles are created by default with a given version use the managesdk command.

To check the default WAS profile Java version execute:

WAS_HOME/bin/managesdk -getNewProfileDefault

To set the default Java version to 1.7_4 execute:

WAS_HOME/bin/managesdk -setNewProfileDefault -sdkName 1.7_64

</snip>

Once I realised this, I added the following steps to my build: -

Check Default SDK

/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -getNewProfileDefault

CWSDK1007I: New profile creation SDK name: 1.6_64
CWSDK1001I: Successfully performed the requested managesdk task.


Set SDK to 1.7

/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -setNewProfileDefault -sdkName 1.7_64

CWSDK1022I: New profile creation will now use SDK name 1.7_64.
CWSDK1001I: Successfully performed the requested managesdk task.


Check Default SDK

/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -getNewProfileDefault

CWSDK1007I: New profile creation SDK name: 1.7_64
CWSDK1001I: Successfully performed the requested managesdk task.


Once done, my cluster magically created : -

...
  [wsadmin] GBRPT0019I: Start application jrules-ssp on server Node1-DSServer ...
  [wsadmin] GBRPT0019I: Start application jrules-res-management on server RulesMgrSrv ...
  [wsadmin] GBRPC0005I: Invoking synchronization for node Node1 ...
  [wsadmin] GBRPC0013I: Synchronization done.
  [wsadmin] GBRPC0028I: The cluster is up and running!

BUILD SUCCESSFUL
Total time: 5 minutes 24 seconds

...




---------------------
http://portal2portal.blogspot.com/2017/02/javalangunsupportedclassversionerror.html
Feb 12, 2017
14 hits



Recent Blog Posts
55
ilog.rules.teamserver.model.IlrConnectException Caused by: java.lang.NullPointerException
Sun, Jul 16th 2017 4:04p   Dave Hay
As one of my many spinning threads, I've been tinkering with the migration of an IBM Operational Decision Manager (ODM) environment from version 8.0 ( circa 2012 ) to version 8.9 ( circa 2017 ).In part, this involves running some SQL scripts to migrate the old data to the new environment.This is especially relevant for the Decision Center, which is the Rules authoring environment, aka the Source Code Management (SCM) system-of-record.The Decision Center, also known as the Team Server ( reflecti
54
WebSphere Application Server - Transaction Logs - getting it wrong
Sun, Jul 16th 2017 1:02p   Dave Hay
I do need to write a long-form article about this, but I've been on a voyage of discovery configuring AND testing WAS transaction recovery, by placing the transaction/compensation/partner logs in an Oracle 12c database.This is in the context of an IBM Business Process Manager Advanced environment.During the process, I saw this in the SupCluster logs ( specifically the second cluster member ) : -SupClusterMember2/SystemOut.log:[16/07/17 11:53:47:332 BST] 00000001 WASSessionCor I SessionPropertie
84
XAException occurred. Error code is: XAER_RMERR (-3). Exception is:
Sun, Jul 16th 2017 12:43p   Dave Hay
I'm tinkering with WebSphere Application Server, underlying IBM BPM Advanced, in the context of transaction/compensation/partner log recovery.In this scenario, I'm placing these logs into a database, Oracle 12c.It's been a useful - and interesting - learning curve, and I've pretty much proved/tested the concept.I did, however, see one issue today; specifically, these messages: -[16/07/17 13:34:06:748 BST] 00000074 XARecoveryDat A WTRN0151I: Preparing to call xa recover on XAResource: dave[
42
TypeError: __add__ nor __radd__ defined for these operands
Fri, Jul 14th 2017 8:02p   Dave Hay
Whilst scripting the configuration of the WebSphere Application Server transaction/compensation/partner logs into an Oracle database: -/opt/ibm/WebSphereProfiles/Dmgr01/bin/wsadmin.sh -lang jython -user wasadmin -password passw0rd -f tranlogs.jy I saw this: -WASX7209I: Connected to process "dmgr" on node Dmgr using SOAP connector; The type of process is: DeploymentManagerWASX7017E: Exception received while running file "tranlogs.jy"; exception information: com.ibm.bsf.BSFException: exceptio
35
CWMCB0012W: An inconsistent configuration has been detected for data source jdbc/TeamWorksDB
Fri, Jul 14th 2017 7:42p   Dave Hay
This follows on from an earlier post: -ORA-12514, TNS:listener does not currently know of service requested in connect descriptorHaving updated my JDBC data sources to reflect the correct Oracle service name: -jdbc:oracle:thin:@//bpm857.uk.ibm.com:1521/orcl.uk.ibm.comI'm now seeing the following warning: -[14/07/17 20:07:17:855 BST] 000000f5 ConfigReader W com.ibm.bpm.config.util.ws.ConfigReader getDatabaseInfo CWMCB0012W: An inconsistent configuration has been detected for data source jdbc/Te
42
IBM BPM - "CWSCA8095W: Unable to find class..." seen during serviceDeploy process
Fri, Jul 14th 2017 7:32p   Dave Hay
I'm tinkering with IBM BPM Advanced again, specifically taking an export of an SCA module, built using IBM Integration Designer and exported as a Project Interchange (PI) file, and attempting to "compile" it ready for deploying to an external IBM BPM 8.57 environment.Having exported the PI file, and made it available to the BPM box, I then ran serviceDeploy.sh against it: -/opt/ibm/WebSphere/AppServer/bin/serviceDeploy.sh OracleTest.zip which returned: -The workbench is starting in /home/wasa
79
java.sql.SQLException: Could not commit with auto-commit set on
Fri, Jul 14th 2017 7:16p   Dave Hay
I saw this earlier: -[14/07/17 20:00:02:593 BST] FFDC Exception:java.sql.SQLException SourceId:com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.commit ProbeId:587 Reporter:com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@964a1c09java.sql.SQLException: Could not commit with auto-commit set onin the FFDC logs for an IBM BPM 8.57 JVM: -view /opt/ibm/WebSphereProfiles/AppSrv01/logs/ffdc/AppClusterMember1_72d880eb_17.07.14_20.00.02.5935101433318572951378.txt I am using Oracle 12c ( specifically 12.2.0.1.0 )
29
Bootstrap cannot be run against WebSphere:cell=PSCell1,node=Node2,server=dmgr because it is not a BPM deployment target.
Tue, Jul 11th 2017 6:19a   Dave Hay
Another thing that makes me go "Hmmmm" …I'm running the process to bootstrap an IBM BPM 8.5.7 Process Server: -/opt/ibm/WebSphereProfiles/Dmgr01/bin/bootstrapProcessServerData.sh - clusterName AppClusterand I see this: -Bootstraping data for server at /opt/ibm/WebSphereProfiles/Dmgr01 and logging into /opt/ibm/WebSphereProfiles/Dmgr01/logs/bootstrapProcesServerData.logWASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application o
24
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
Tue, Jul 11th 2017 6:11a   Dave Hay
I'm tinkering with a new Oracle 12C build, using it as a database for an IBM BPM Advanced 8.5.7 environment.However, something seems to have gone awry with my WAS -> Oracle configuration, as I see this: -[11/07/17 06:58:16:482 BST] 000000f1 DataSourceCon E DSRA8040I: Failed to connect to the DataSource "". Encountered java.sql.SQLException: Listener refused the connection with the following error:ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
18
Tinkering with Oracle 12c on Linux - will the fun ever stop ?
Sat, Jul 8th 2017 8:53a   Dave Hay
I'm going back through the process of learning how to install Oracle 12c on Red Hat Enterprise Linux 7.3.One niggle that I saw post-install was this: -sqlplus / as sysdba;SQL*Plus: Release 12.1.0.2.0 Production on Sat Jul 8 05:23:05 2017Copyright (c) 1982, 2014, Oracle. All rights reserved.ERROR:ORA-12547: TNS:lost contactDuring the installation, I'd seen reference to a missing dependency: -/usr/bin/ld: cannot find -ljavavm12collect2: error: ld returned 1 exit statusmake: *** [/home/oracle/ap




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition