Wednesday, January 30, 2013

Webcenter install : java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup

I did a fresh install of Web Center and was starting up my managed server through the console: [Windows]
I got a bunch of errors in my log file and the deployment failed.

java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup

 Find your -should be [Weblogic Dir]\wlserver_10.3\common\nodemanager
 Change the line StartScriptEnabled=false to StartScriptEnabled=true.
  Everything should work

If not check that you have the JFR stuff installed.

Monday, January 28, 2013

Redhat: Heirloom mail config

I wanted to add an account in mailx for my Nagios setup.
Could not find any docs on it (maybe I didnt search enough) but here we go:

The config file: /etc/mail.rc
Just added an new account to the end of the file like such

account newsmtp {
set record=+Sent
set from="Administrator "
set smtp=smtp://

Viola I can now in my commands.cfg config of nagios:
(/usr/local/nagios/etc/objects) just add the -A projsmtp to use this account in the mail setup

# 'notify-host-by-email' command definition
define command{
command_name notify-host-by-email
command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /bin/mail -A newsmtp -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$

# 'notify-service-by-email' command definition
define command{
command_name notify-service-by-email
command_line /usr/bin/printf "%b" "***** Nagios *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /bin/mail -A newsmtp -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$

Friday, January 25, 2013

Oracle WebCenter licenses

After a long time trawling the internet for details on how web center licenses work (what products you can use with each license) I spotted my mistake.
DONT search for WebCenter licenses search for Fusion Middleware licenses. Makes all the difference.

And for the lazy (

Hudson vs Jenkins: Phase 2

Ok so in a earlier post I made a choice to go with Hudson over Jenkins for various reasons:

But now the decision is back and I have decided to install Jenkins this time and so far so good.

JIRA: Exception caught in 500 page null : java.lang.NullPointerException

I imported my buzilla database into JIRA and could not search on external id field after the import.
I was getting the following error in the logs:

        at com.atlassian.jira.issue.customfields.searchers.transformer.FreeTextCustomFieldSearchInputTransformer.validateParams(

Step 1 was to remove the Freetext search from the External ID custom field.
I then added the freetext search back to the custom field.
I then reindexed and like magic my error went away.

Thursday, January 24, 2013

Change of jira context : Confluence sharing database

Ok so I changed my context on my jira server to /jira (I had to authenticate a number of time and it was annoying me).

NOTE: My jira and confluence are installed on the same machine and use the JIRA authentication database.

When restarting confluence I could not log in.. bummer

I updated the JIRA reference in the admin console and still no joy so I looked in the logs: /var/atlassian/application-data/confluence/logs for me.

I was getting this error:

com.atlassian.crowd.exception.InvalidCrowdServiceException: The following URL does not specify a valid Crowd User Management REST service: http://server:8080/rest/usermanagement/1/event

So I logged into the db and changed in the ATTRIBUTE_VALUE column to the correct new server context  http://server:8080/jira in CWD_DIRECTORY_ATTRIBUTE table where the ATTRIBUTE_NAME was crowd.server.url.

Fixed my problem right up.

Tuesday, January 15, 2013

Weblogic: Authentication denied: Boot identity not valid

When I changed my admin password and tried to start up my managed servers I got the following (admin server was working fine): Weblogic 10.3.6

Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file ( is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.


Stop you managed server

rename \data\ldap to \data\ldap

Restart managed servers.

Worked for me

Thursday, January 10, 2013

ADF: Upgrade issues from to

Firs thing I encountered was that our menu was not refreshing as it had been : as soon as we clicked on the custom menu the normal menu would no longer refresh.

This is the code that was causing the problem:

So once we had done a code RichTreeTable.setValue on the tree the EL item would no longer be executed after this point.

Makes sense so I just removed the setValue and perform everything through EL.

Monday, January 7, 2013

WARNING: oracle.webcenter.lifecycle.exception.LifecycleLockedException: A lock exists that prevents the export set import.

Ok, so this is and expected error in the logs, although not nice it can be ignored (IN A CLUSTER).

Taken from the oracle documentation: (

This is expected behavior. When you deploy your application, the producer metadata exported into the EAR file (as a MAR file) needs to be imported into an MDS schema for use in the production environment. Importing the metadata occurs automatically during deployment. This import only needs to happen with one node in the cluster, so a lock is created to prevent other nodes in the cluster trying to perform the same operation.

Wednesday, January 2, 2013

ADF - MDS-00521 error while reading document metadata repository

MDS-00569 unable to read document

I got this error when deploying my Web Center app. All it was was a small spelling error in the partition name.

There are other reasons that this happens but copying and pasting the name from another environment helped.