Skip to Main Content
Forums

Java Programming

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

JNLP extension and associations

3346449Nov 14 2016 — edited Nov 24 2016

First of all apologies for the potential for dumbassery in this question. I am totally new to the JRE and am struggling with one particular aspect...

A legacy system is currently running on JRE6u43 but the system admin wants to upgrade to JRE8u66 which in theory is no problem. I've worked out how uninstall the 6u43 and install 8u66 in a silent fashion and everything seemed ok.

The system is launched by clicking on and running a JNLP file. It looks, however, like when I uninstall the JRE6u43 all the file associations, settings and even the .JNLP extension is being deleted from the PC. The JRE8u66 installer then doesn't seem to recreate these associations and the extension. Therefore when you attempt to fire up the jnlp file it moans and asks for the associated application.

I can browse and select the javaws.exe file and tick the 'always use this program' option but I need to somehow include the associations and extension creation in my deployment script because, this manual selection will be beyond the ability of the end users.

Is my deduction that the JRE installer no longer creates the relevant extension(s) and associations or is this some kind of bug? I tried the latest JRE installer and it still fails to create them.

I tried setting the JNLP File/MIME Association to ALWAYS in the Java Control Panel > Advanced Settings. Is this setting supposed to somehow set the JNLP file extension and associations. All it seemed to do was add the line deployment.javaws.associations=ALWAYS in the deployment.properties file but does it didn't seem to do much else.

Do I need to now manually create the JNLP extension in Windows and then associate it with the javaws.exe program? Or am I missing something else?

If I do have to create the extension and associations is there any doc that shows how to do this?

Thanks for any help as it's driving me absolutely nuts...

Comments

PS_orclNerd

when you used iscsi for your devices, did you used oracleasm to name that devices? because if you did not oracleasm configure -i oracleasm createdisk you will not see them.. then you can use other ways how to name the devices like udev.. then you can use it in your diskstring and you will see them when you start asmca

Royce Daniel

I have used the  below steps

yum install oracleasm

yum install kmod-oracleasm

yum install oracleasm-support

rpm -ivh oracleasmlib-2.0.12-1.el7.x86_64.rpm

which oracleasm

returned  /usr/sbin/oracleasm

oracleasm configure -i

oracleasm init

/etc/init.d/oracleasm createdisk OCR /dev/sdb1

/etc/init.d/oracleasm createdisk FRA /dev/sdb2

/etc/init.d/oracleasm createdisk DATA /dev/sdb3

Murali9231

Paste the output of /usr/sbin/oracleasm configure

You may not choosen for ASM SCAN BOOT -- YES.

Regards

Murali

PS_orclNerd

I have used once oracleasm and the /etc/init.d/oracleasm failed to create the disks with the /usr/sbin/oracleasm it worked. Somehow only with one if them it worked.

I would rather use udev (this is my udev file from yesterdays installation) and I think a lot of deployments don't use oracleasm for naming the disks..

[root@rac1 rpm]# cat /etc/udev/rules.d/99-oracle.rules

KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VB2709a858-60625687", SYMLINK+="asm-disk1", OWNER="grid", GROUP="asmadmin", MODE="0660"

KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VBf189f74c-ae118012", SYMLINK+="asm-disk2", OWNER="grid", GROUP="asmadmin", MODE="0660"

KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VB8e629c0a-30334875", SYMLINK+="asm-disk3", OWNER="grid", GROUP="asmadmin", MODE="0660"

sky_yow

Hi Royce,

The steps look good for me assuming you have set asm scan boot to yes to scan disks every time when you boot the system.

You can verify the setting in the /etc/sysconfig/oracleasm file .

One more thing to look is to verify the ASMlib is coming after iscsi and have the devices attached to the system.

Cheers,

Gleb

Royce Daniel

No I have turned on

PFA

pastedImage_0.png

Royce Daniel

yes I have  set scan boot to yes

Alok_Dwivedi

Hi Royce,

The oracleasm scans /proc/partitions and expects devices to be available in /dev. If the device doesn't exist in /dev it will fail to open the device.

RHEL/OL5 does not create dm-xx devices in /dev by default.

Comment out the following line in file /etc/udev/rules.d/50-udev.rules.

In latest versions of RHEL/OL5, the udev rule has been moved to file /etc/udev/rules.d/90-dm.rules.

#KERNEL=="dm-[0-9]*", ACTION=="add", OPTIONS+="ignore_device"

Regards,

Alok

juamd

Hi,

Have you tried using udev rules ? always ASMLib is my first option to mark asm disks but I have faced issues with it, so if you are getting errors that has no sense try udev rules to mark asm disks

Check this out:

Best regards.

1 - 9

Post Details

Added on Nov 14 2016
#java-8-questions
1 comment
2,839 views