tracker issue : CF-3586644

select a category, or use search below
(searches all categories and all time range)
Title:

wsconfig does not configure Oracle iPlanet 7.0.9 or higher

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/

Reporter/Name(from Bugbase): David Epler / David Epler (David Epler)

Created: 06/27/2013

Components: Installation/Config, Connector

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 1

Problem Description:

On new install of ColdFusion 10 running Redhat 5.9 with Oracle iPlanet Web Server 7.0.15 connector script fails to install.

From {ColdFusion Dir}/cfusion/ConnectorInstall0.txt
-----------
os.name: Linux
os.version: 2.6.18-348.6.1.el5
os.arch: amd64
platform: intel-linux64
command line: -ws SunJWS -dir /opt/Webserver7/https-www/config -cfide /opt/coldfusion10/cfusion/wwwroot/CFIDE -v 
web server: SunJWS
web server directory: /opt/Webserver7/https-www/config
apialloc: false
force resource extract from jar: true
Version 7.0.15 is installed.  Supported versions are Sun Java System Web Server 7.0 upto updater 8

From {ColdFusion Dir}/config/wsconfig/wsconfig.log
-----------
06/27 13:45:11 info Tomcat Connector
06/27 13:45:11 debug command line: -ws SunJWS -dir /opt/Webserver7/https-www/config -cfide /opt/coldfusion10/cfusion/wwwroot/CFIDE -v 
06/27 13:45:11 error Version 7.0.15 is installed.  Supported versions are Sun Java System Web Server 7.0 upto updater 8
com.adobe.coldfusion.connector.connectorinstaller.WSVersionNotSupportedException: Version 7.0.15 is installed.  Supported versions are Sun Java System Web Server 7.0 upto updater 8
	at com.adobe.coldfusion.connector.connectorinstaller.SunJWSInstaller.installConnector(SunJWSInstaller.java:120)
	at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.installConnector(ConnectorInstaller.java:353)
	at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.doIt(ConnectorInstaller.java:297)
	at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.main(ConnectorInstaller.java:759)

Also tried wsconfig.jar from Update 10 and does not work either.

Any Workarounds:

wsconfig.jar inspects {Oracle iPlanet Dir}/setup/WebServer.inf for version information from PRODUCT_SP_VERSION and PRODUCT_FULL_VERSION.

Changed PRODUCT_SP_VERSION to 8 and PRODUCT_FULL_VERSION to 7.0.8

Re-ran connector script and successfully modified obj.conf, magnus.conf, and installed the connector. Connector script failed to restart Oracle iPlanet Web Server.

From {Oracle iPlanet Dir}/https-www/logs/errors 
-----------
[27/Jun/2013:16:20:46] info ( 1709): CORE1116: Oracle iPlanet Web Server 7.0.15 B04/19/2012 21:52
[27/Jun/2013:16:20:46] failure ( 1709): CORE2254: Error running Init function jk_init

From {ColdFusion Dir}/config/wsconfig/1/nsapi.log
-----------
[Thu Jun 27 16:20:46.169 2013] [1709:47371424999680] [error] jk_map_validate_property::jk_map.c (404): The attribute 'worker.cfusion
.max_reuse_connections' is not supported - please check the documentation for the supported attributes.

Modfied {ColdFusion Dir}/config/wsconfig/1/workers.properties to comment out worker.cfusion.max_reuse_connections.

Oracle iPlanet Web Server correctly starts and is able to connect to ColdFusion.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3586644

External Customer Info:
External Company:  
External Customer Name: David Epler
External Customer Email:

Attachments:

Comments:

Oracle iPlanet 7.0.17 connector fails with CF 10 on Red Hat linux 6.3 install.
Vote by External U.
15107 | July 15, 2013 01:48:19 PM GMT
ColdFusion 10 has been certified with Sun System 7 Web Server till update 8 (7.0.8), so updates greater than 8 might not work
Comment by Vamseekrishna N.
15103 | July 16, 2013 01:03:50 AM GMT
What I'm seeing in CF9 Enterprise is an inability to produce a 64-bit connector for iPlanet 7.0.15. /opt/ColdFusion9/runtime/lib/wsconfig/1/mod_jrun.so is a shared object, but it can only be created in 32 bit form, from my observations. From an upgrade install, CF9 will default to 32 bit when it makes mod_jrun.so. This throws errors in 64-bit iPlanet on Sun Solaris 10 SPARC. ./coldfusion wsconfig -ws ..... can you force a 64-bit connector?
Comment by External U.
15104 | August 16, 2013 06:06:41 PM GMT
Vamseekrishna: Sun System 7 Web Server ver 7.0.15 runs fine on CF8 Ent with Sun Solaris 10 SPARC. Could it be the adobe developers broke CF9? Maybe I should cancel that $7K support contract for CF9 and keep using CF8?
Comment by External U.
15105 | August 16, 2013 06:16:09 PM GMT
Redhat 6.2(64-bit)/Coldfusion10(64 bit)/Oracle Webserver7 Got it all working using this note plus some other important info that I could not find anywhere!. 1) It's easier to use wsconfig to config/unconfig the connector. 2) When you install the webserver it'll set up a default configuration. If you set up the CF connector using this config you should be fine. If you set up the cf connector using any other webserver7 configuration you will have problems. These problems can be resolved by editing server.xml under your webserver config dir. There's a section like this: <virtual-server> <name>main_webserver</name> <http-listener-name>http-listener-1</http-listener-name> <host>web5.example.com</host> <object-file>main_webserver_obj.conf</object-file> </virtual-server> That object-file section is added by the webserver7 admin server when you add a new configuration. Make sure that the object-file section points to the correct obj.conf file. In the default config it's obj.conf but if you add new webserver configs the object-file entry will correspond to that obj file like shown above. But wsconfig modified the obj.conf file and not main_webserver_obj.conf. So that's the disconnect. I actually just changed my object-file section to look like: <object-file>obj.conf</object-file> Don't know if this will cause problems later on but it's working right now. We're going to test this setup and I'll try and post back here if I find anything else. The real solution might be to leave server.xml alone and slice the changes that the connector makes to obj.conf into the new obj.conf(main_webserver_obj.conf). Hope this helps someone.
Comment by External U.
15106 | February 17, 2014 01:34:34 PM GMT