199 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
java.sql.SQLException: IO Error: The Network Adapter could not establish the connection DSRA0010E: SQL State = 08006, Error Code = 17,002
Mon, Jul 24th 2017 27
Further adventures with Oracle database - ORA-01078 and LRM-00109
Mon, Jul 24th 2017 17
ilog.rules.teamserver.model.IlrConnectException Caused by: java.lang.NullPointerException
Sun, Jul 16th 2017 27
WebSphere Application Server - Transaction Logs - getting it wrong
Sun, Jul 16th 2017 35
XAException occurred. Error code is: XAER_RMERR (-3). Exception is:
Sun, Jul 16th 2017 33
TypeError: __add__ nor __radd__ defined for these operands
Fri, Jul 14th 2017 33
CWMCB0012W: An inconsistent configuration has been detected for data source jdbc/TeamWorksDB
Fri, Jul 14th 2017 27
Top 10
Transport Layer Security (TLS) 1.2 and SoapUI
Fri, Jun 12th 2015 49
Hmmm, macOS Sierra and XQuartz and X11
Thu, Oct 27th 2016 39
WebSphere Application Server - Transaction Logs - getting it wrong
Sun, Jul 16th 2017 35
Executing external Python/Jython scripts from within WebSphere Application Server's wsadmin tool
Thu, Feb 27th 2014 34
java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=com/davehay/EmployeeServlet, offset=6
Sat, Nov 8th 2014 34
IBM BPM - "CWSCA8095W: Unable to find class..." seen during serviceDeploy process
Fri, Jul 14th 2017 33
TypeError: __add__ nor __radd__ defined for these operands
Fri, Jul 14th 2017 33
XAException occurred. Error code is: XAER_RMERR (-3). Exception is:
Sun, Jul 16th 2017 33
Hmmmm, HTTP404 and SRVE0190E seen with IBM HTTP Server and WebSphere Application Server
Fri, Nov 14th 2014 30
java.sql.SQLException: Could not commit with auto-commit set on
Fri, Jul 14th 2017 29


Interesting, WebSphere Application Server 8.5.5.11 and Java 6
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
   

I saw this: -

ERROR: Support for using Java SE 6 with WebSphere Application Server ends in April 2018.

Java SE 8 is the recommended Java SDK because it provides the latest features and security updates. You can continue to use Java SE 6, but no service can be provided after the end of support date, which could expose your environment to security risks.

You must specify the default Java SDK version on the 'user.wasjava' property. 

To install the Java 8 SDK, specify '-properties user.wasjava=java8'. 

To install the Java 6 SDK, specify '-properties user.wasjava=java6'. 

whilst trying to install the latest WebSphere Application Server (WAS) version ( 8.5.5 Fixpack 11 aka 8.5.5.11 ) today, via this command: -

/opt/ibm/InstallationManager/eclipse/tools/imcl -input /mnt/hgfs/Software/Repo/ResponseFiles/installWAS855.rsp -acceptLicense

Given that I was using a response file, it was easy enough to fix, by adding an additional data.key to installWAS855.rsp: -

<profile id='IBM WebSphere Application Server V8.5' installLocation='/opt/ibm/WebSphere/AppServer'>
<data key='eclipseLocation' value='/opt/ibm/WebSphere/AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.os' value='linux'/>
<data key='cic.selector.arch' value='x86'/>
<data key='cic.selector.ws' value='gtk'/>
<data key='cic.selector.nl' value='en'/>
<data key='user.wasjava' value='java6'/>
</profile>


Note that I'm explicitly choosing to use Java6, other Java versions are available :-)

More background from this: -

<snip>

WebSphere Application Server v8.5 traditional

Starting in version 8.5.5.11, you must install either Java SE 6 or Java SE 8 as the version of Java SE contained in the /java and /java64 directories in WebSphere Application Server and used by default during server and node configuration. For existing installations that are being updated, your current Java level remains the same. For example, if you previously installed version 8.5.5.10 with Java SE 6, and you update to version 8.5.5.11, your Java version remains Java SE 6. For information about how to migrate to Java SE 8, see Migrating to Java Platform, Standard Edition 7 or 8.

You can install Java SE 8 by using the GUI, the command line or by using response files. To install Java SE 8 using the command line or response files, you must specify the Java version by using the user.wasjava property.
  • To install Java SE 8, specify -properties user.wasjava=java8.
  • To install Java SE 6, specify -properties user.wasjava=java6.

</snip>




---------------------
http://portal2portal.blogspot.com/2017/01/interesting-websphere-application.html
Jan 10, 2017
17 hits



Recent Blog Posts
27
java.sql.SQLException: IO Error: The Network Adapter could not establish the connection DSRA0010E: SQL State = 08006, Error Code = 17,002
Mon, Jul 24th 2017 3:56p   Dave Hay
I saw this: -The test connection operation failed for data source BPM Business Process Choreographer data source on server nodeagent at node Node1 with the following exception: java.sql.SQLException: IO Error: The Network Adapter could not establish the connection DSRA0010E: SQL State = 08006, Error Code = 17,002. View JVM logs for further details.whilst testing JDBC data sources configured to connect to a newly-minted Oracle 12c database.I checked the Oracle box to ensure that the listener was
17
Further adventures with Oracle database - ORA-01078 and LRM-00109
Mon, Jul 24th 2017 2:58p   Dave Hay
Having installed Oracle 12c ( 12.2.0.1.0 ) today, I was somewhat concerned when I tried to start my database: -sqlplus / as sysdbaSQL*Plus: Release 12.2.0.1.0 Production on Mon Jul 24 14:04:56 2017Copyright (c) 1982, 2016, Oracle. All rights reserved.Connected to an idle instance.SQL> startup ORA-01078: failure in processing system parametersLRM-00109: could not open parameter file '/home/oracle/app/oracle/product/12.2.0/dbhome_1/dbs/initorcl.ora'SQL> quitDisconnectedI checked the offen
27
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
35
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
33
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[
33
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
27
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
33
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
29
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 )
14
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




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