Weblogic Business Services Truncating XML Payload

I’m not even sure how to explain this issue other than…

  1. Using a web service proxy BSSV to send a XML file to an outside vendor was getting truncated for some unknown reason
  2. It was very difficult to track down
    1. The following startup argument came is very handy
  3. Oracle Support said that it is a custom process and therefore is not supported
  4. It finally got resolved by using 3 Weblogic startup arguments that bypass the JRockit SSL handler and force the use of the native Sun/Oracle SSL handler

Hope this helps someone.

Do you have any Weblogic Server Start Arguments that you use to get by issues that have come up?

Oracle Weblogic 12.1.2 Node Manager Bug – FORCE_SHUTTING_DOWN

There is a bug in the Weblogic 12.1.2 Node Manager that reports the managed server in a FORCE_SHUTTING_DOWN status when there is no PID.

It is explained more completely here: Weblogic 12.1.2 Node Manager Bug

RESOLUTION: Delete the managed server’s “.state” file which is usually located here:

SQL Used to compare records in tables

I have been using this little SQL quite a bit lately. It is very handy in finding records that are in one table but not in the same table in a different environment.

It can also be used to do the insert of those records that are missing by adding an INSERT INTO statement.

Empty All User’s Recycle Bins

Use the command below to empty the Recycle Bins of all users on a PC.

Related Post: Safely Delete Files From WINSXS

Better Performance On Work with Payroll Transaction Ledger (P050999) With An Index On F0618

We have been getting complaints about the Work with Payroll Transaction Ledger (P050999) grid loading performance.  So, I decided to take a look.  What I found was that upon entering the application it does an automatic find on the grid using the following SQL statement with the current G/L date in the WHERE clause.

As you can see, this SQL statement is returning every record in the F0618 that has a G/L Date less than or equal to the system’s current G/L Date.  I don’t know about your installation but the one that I was working on had 17+ million records.  Why the heck would it need to return all that?

That screen was taking 8+ minutes to present information to the user.

With the help of my coworker Geordy and Technet, I came up with an index on the F0618 that didn’t make the SQL statement finish any quicker, but it does present the user the first page of data extremely fast (LESS THAN 3 SECONDS!).

You can see from the index that all I did was create an index over the field that the SQL was sorting on (YTDWK or Date of Work) and included the rest of the fields that were in the query.

There must be other little tricks with indexes in EnterpriseOne.  Have you found any?