Kwiecień « 2016 « Różności …

Różności …

30 kwietnia 2016

weblogic: The task cannot be processed further until the current edit session is activated

Zaszufladkowany do: WebLogic — Tagi: — Jacek @ 10:43

That message is not an error. It means that you need to connect to the WebLogic Server Console and activate the changes.


Access the WebLogic Server Console and click on Activate Changes.

Confirm if your application shows in the WebLogic Server Console under “Deployments”.


[J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name:, exact-match: false]

Zaszufladkowany do: ADF,Programowanie — Tagi: — Jacek @ 06:07 [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name:, exact-match: false]
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(
at weblogic.application.internal.BaseDeployment$
at weblogic.application.utils.StateMachineDriver.nextState(
at weblogic.application.internal.BaseDeployment.prepare(
at weblogic.application.internal.EarDeployment.prepare(
Truncated. see log file for complete stacktrace

he ADF libraries in my domain were only targeted at the Admin Server, so when I tried to deploy my application to a Cluster of Managed Servers, it couldn’t see the ADF extensions.

So to get around this, log into the WebLogic console for your domain and do the following:

  • Click on Deployments.
  • Click on the ‘,’ library deployment.
  • Click on the Targets tab.
  • Select the Managed Server(s) or Cluster(s) to which your application is going to be deployed, leaving the AdminServer target still ticked.
  • Click on Save.

Then repeat the steps above for the following libraries:

  • jstl(1.2,
  • jsf(1.2,

Activate any changes (if running in Production Mode) and try deploying your application again ”</p

Claude E. Shannon

Zaszufladkowany do: Z sieci — Tagi: — Jacek @ 05:09

19 kwietnia 2016


Zaszufladkowany do: Oracle — Tagi: — Jacek @ 09:08

What will happen to rollback session if database shutdown immediate/abort?

Na to pytanie udzielono już odpowiedzi.

bk75 Newbie

bk75 2009-11-28 15:58

I have a long running rollback session after i killed it. The status of session is ‘KILLED’ and when I check the v$transaction, it will take almost 24hours to complete rollback. We cannot wait for so long because we have other dependencies job need the rollback to be completed faster. At the end, we plan to shutdown immediate. Will this help? What will happen to the rollback session if we issue shutdown immediate or shutdown abort? Will the rollback completed successfully?

Hemant K Chitale

Prawidłowa odpowiedź przez Hemant K Chitale dnia 2009-11-28 16:15
If you SHUTDOWN ABORT when there are very many active transactions or transactions being rolled back, then the default FAST_START_PARALLEL_ROLLBACK that occurs on the subsequent Instance Startup will actually mean that the Rollback is executed faster.
However, if it is a single large transaction such as a DELETE against a table with an Index, then it is better to disable FAST_START_PARALLEL_ROLLBACK before restarting the Instance immediately after a SHUTDOWN ABORT. The Parallel Rollback of a single large transaction with an Index can be slower !

FAST_START_PARALLEL_ROLLBACK is an instance parameter which default to LOW (ie a setting of 2 x CPU_COUNT) and can be set to HIGH or FALSE.

Note : If you SHUTDOWN ABORT and STARTUP the database, Oracle only has to do a Rollforward from Redo Logs (for database blocks that haven’t been updated) before it does an OPEN. This is generally a very fast operation. The Rollback of uncomitted transactions is a deferred operation — this means that the Rollback is initiated by SMON or the Parallel Slaves after the Database is OPEN. If a block containing a row that was updated and not committed is referenced by a database session after the OPEN but before it has been rolled back, Oracle does an expedited rollback for that row of the block and then continues doing the rollback of other rows in the background.

Thus, if the transaction had been on Table “A” and the database is SHUTDOWN ABORT and STARTUP, then users can continue accessing and updating all other tables other than Table “A” while the transaction is being rolled back, in the background, after the OPEN.

Hemant K Chitale


12 kwietnia 2016

ubuntu shutdown at specific time

Zaszufladkowany do: Linux — Tagi: — Jacek @ 21:55

To shutdown run the command

sudo shutdown -P 60

That is 60 mins.

You could do

sudo shutdown -P 1:00

to shutdown at 1am and

6 kwietnia 2016

usb bootable disk

Zaszufladkowany do: Linux — Tagi: — Jacek @ 10:20


linux temperature

Zaszufladkowany do: Linux — Tagi: — Jacek @ 10:06

apt-get install lm-sensors

# sensors-detect

sudo service kmod start

# modprobe coretemp
# modprobe i2c-i801

$ sensors

sudo apt-get install hddtemp
sudo hddtemp /dev/sda  

Strona startowa: