Work flow related transactions r not working

hi ppl,
I have been assigned in a new project. When i check out none of the workflow related transactions r working for me. When i informed my BASIS guy he is asking me for the list of transactions. Is there any specific role or access for me to ask so that all the work flow related tcodes can work in one shot.
Regards,
Dheepak

Refer this link, http://help.sap.com/erp2005_ehp_03/helpdata/EN/f4/4a5536ad3d2a17e10000009b38f839/frameset.htm
Select the one appropriate to you.
Regards, IA

Similar Messages

ST22 timeout for all LC related transactions LIVE cache start stop working from LC10

Hi Team
we are a getting a ST22 timeout for all LC related transactions LIVE cache start stop working from LC10
LC version 7.9
OS AIX
SAP SCM 7
SDBVERIFY giving the following error
Checking package Redist Python
Checking package Loader
Checking package ODBC
Checking package Messages
Checking package JDBC
Checking package DB Analyzer
ERR: Failed
ERR: Checking installation "Legacy" failed
ERR: Group of directory /sapdb/data/config/install changed [0 =>
sdbregview -l is showing good.
any idea what might went wrong.
trying to use sdbverify -repair_permissions , but not sure about the exact syntax to use.
and it is not related to timeout parameter, we tested with different timeout values, but still the same error.
thanks
Kishore Ch

Hello Kishore,
you could check the sizing of the liveCache data.
* Report /SAPAPO/TS_LCM_REORG_SNP has checks of the SNP planning areas for superfluous objects.
* Delete old/temporary APO data.
* /SAPAPO/TS_LCM_REORG report checked TS superfluous objects.
If you didn't create the planning versions, copy of planning versions & data load to liveCache, then create the SAP message to check your system on the question of the dataarea usage.
If you have the long running APO transactions => performance of the SCM system has to be checked.
If you have the bottleneck in liveCache & could not solve the case by yourself => create the SAP message to BC-DB-LVC and get SAP support.
Best regards, Natalia Khlopina

Session Bean Transaction Rollback not working for RuntimeException

Hi,
I am calling a number of JDBC create/update statements within a method in a container managed transaction stateless session bean with transaction attribute set to required. I am running the bean within the embedded OC4J supplied with JDeveloper 10g (10.1.2). For each JDBC call, i connect to a datasource via JNDI containg a pool of connections pointing to an Oracle 10g database (standard J2EE)
If i throw a runtime exception within the method the transaction is NOT rolled back as it should be according to the EJB spec. However, if i setRollbackOnly() on the session bean SessionContext the transaction does roll back.
Has anybody experienced this before?
Is this an OC4J bug?
Thanks
Dave

Generally, for urgent issues it's best to open a SR with Oracle Support rather than posting to the forums.
enlist=dynamic didnt exist in 10.2.0.2.20, but does now. I can't recall what specific version it was introduced though.
enlist=false prevents enlistment in MSDTC transactions, so thats why it's not rolling back in that case.
"transaction branch length 90 is illegal" was a known issue on Vista, is that the OS you're using? It takes a two part fix, and It is resolved by
1) getting up to 10204 ODP (apply the 10204 rdbms patch to your client install)
2) applying SP1 for Vista
Hope it helps,
Greg

RFC : Transaction Program not Registered

Hi Folks,
We have registered the server program from the middleware onto SAP R/3 System and is successfully registered as per the logs. As a next step, we have logged into R/3 System, SM59, in the RFC destination (Type TCP/IP) after specifying the registered program, we have tested it(Connectivity test). The test is positive and connectivity is established successfully.
The solution was working for months and suddenly connectivity is broken.
To restore the connection, we have repeated the steps, registered the server program, tested and everything is fine.
But when we have pushed a new message, then onwards the RFC destination shows an error. "TP is not registered", Return Code 679. That is when the first message is pushed, it is de-registering the server program and running into error. All the messages got stuck in SM58 with status 'Error when opening an RFC connection'.
RFC trace shows
ERVER> Caller transaction code: (Caller Program: SAPLQOWK)
ERVER> Called function module: ARFC_RUN_NOWAIT
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Transaction program not registered.
Please let me know for any inputs.
Thanks, Suraj

My problem got solved. In the middleware, when TRFC connection is made, it has created a lock entry during the time, system was brought down for maintenance activity. When the system is brought up, then as the connection lock entry is available, then it deregistered the server program and not able to establish further connection.
To resolve the issue, we have just deleted lock file and registered server program from middleware. This time the connection was established successfully and could able to restore the message flow.
Thanks, Suraj

[Urgent] Error: The transaction is not active

Our process encounters some errors when the execution time takes longer than normal, e.g. 5mins. Any help is much appreciated.
Process Flow:
The flow consists of 3 process, 1 long-lived process and 2 short-lived processes, let say process A, B and C
Long-lived process A call short-lived process B,
and then, short-lived process B call another short-lived process C.
There is a loop inside process B, so that process C would be called several times.
* Both invocation policy have been tested, including "Do not wait for response" and "Wait for response".
Problem:
Everything work fine when the whole process is within a short-period of time. e.g. 1-2 minutes
However, when the process takes longer, e.g. > 5mins, we got some error message in the sever log.
Server log:
2011-08-18 18:43:11,625 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterLocal.doRequiresNe w(com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.Transa ctionCallback) throws com.adobe.idp.dsc.DSCException, causedBy:
java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImp le.java:223)
at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:501)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:411)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy167.doRequiresNew(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:143)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:188)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:20 9)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.workflow.engine.PEUtil.invokeAction(PEUtil.java:886)
at com.adobe.workflow.engine.SynchronousBranch.handleInvokeAction(SynchronousBranch.java:510 )
at com.adobe.workflow.engine.SynchronousBranch.execute(SynchronousBranch.java:888)
at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBea n.java:2792)
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncInvokeProcessCommand(ProcessEngineBMT Bean.java:697)
at sun.reflect.GeneratedMethodAccessor1076.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:237)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:158)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:1 73)
at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:169)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy200.asyncInvokeProcessCommand(Unknown Source)
at com.adobe.idp.workflow.dsc.service.ProcessCommandExecutorService.invokeProcess(ProcessCom mandExecutorService.java:55)
at sun.reflect.GeneratedMethodAccessor3010.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
at com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker.invoke(WorkflowDSCInvoker.java:154)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.DocumentPassivationInterceptor.intercept(DocumentPassi vationInterceptor.java:53)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:357)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:227)
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:237)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:158)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:169)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:378)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy167.doSupports(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:165)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:20 9)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.workflow.engine.PEInvokeProcessCommand.execute(PEInvokeProcessCommand.java:126)
at com.adobe.workflow.workadapter.WorkflowCommandExecutionUnit.execute(WorkflowCommandExecut ionUnit.java:22)
at com.adobe.idp.dsc.workmanager.adapter.ManagedAsynchronousWorkAdapter.run(ManagedAsynchron ousWorkAdapter.java:70)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Unknown Source)

Hi Paul,
Thank you for your advice.
It seems that it is not a bug of Adobe Livecycle, but some kind of configuration problems. Since the problem does not occurs when the process implementation time is short, such as 1-3 minutes.

The sound quality of my speaker suddenly got really poor when playing music or videos. Sounds like an old AM radio or Sputnik. Pretty sure it's hardware related but maybe not. Thoughts on what the problem might be and if it can be repaired?

The sound quality of my speaker suddenly got really poor when playing music or videos. Sounds like an old AM radio or Sputnik. Pretty sure it's hardware related but maybe not. Thoughts on what the problem might be and if it can be repaired?

The batterys the ipods come with are very sensetive somtimes they dont react right to the first couple of charges. Try fully charging it and then leaving it on until its completely drained a few times. If that doesnt work it might be a lemon.

Error: failed to prepare transaction (could not satisfy dependencies)

Hi,
I was going to install a winff package (a GUI front end to ffmpeg for converting between video formats), but when I ran yaourt -S winff and tried to install it refused because it isn't for the x86_64 architecture. So I decided to edit the PKGBUILD and perhaps try to force it anyway, but then I saw that the PKGBUILD is actually getting the precompiled RPM package and as I checked, while there was no precompiled 64bit version of the RPM there was one for a deb version that is offered on winff site.
Since deb's are just archives I ended up, after a few tries, with this PKGBUILD which uses ar and tar commands to get to the binaries inside of the amd64 deb:
# Contributor: yugrotavele <[email protected]>
# Modified by libervisco for x86_64
pkgname=winff-amd64
pkgver=0.42
pkgrel=1
pkgdesc="GUI for ffmpeg"
url="http://www.winff.org"
license=('GPL')
depends=('ffmpeg gtk gdk-pixbuf')
makedepends=('')
source=('http://winff.googlecode.com/files/winff-0.42-amd64.deb')
arch=('x86_64')
md5sums=('1febf5fd19fa76bdc1da06d3e6c4d3b8')
build() {
ar vx winff-0.42-amd64.deb
tar xvzf data.tar.gz
install -Dm755 $startdir/src/usr/bin/winff $startdir/pkg/usr/bin/winff
install -Dm755 $startdir/src/usr/share/winff/presets.xml $startdir/pkg/usr/share/winff/presets.xml
install -Dm755 $startdir/src/usr/share/winff/winff.png $startdir/pkg/usr/share/winff/winff.png
So what I basically do is run yaourt -S winff and when it asks whether I want to edit it, I edit it and replace the original PKGBUILD content with above.
It successfully runs the build() commands, finds and installs the dependencies, but when it's time to install the actual new winff package is throws up this:
loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: winff: requires ffmpeg gtk gdk-pixbuf
I don't get it. It installed all the dependencies (and I even checked whether winff works in one of the earlier tries when I manually installed gdk-pixbuf when the binary asked for it). What does it want now?
Here is the whole process:
[daniel@memeport ~]$ yaourt -S winff
==> Downloading winff PKGBUILD from AUR...
Comment by: yugrotavele on 20080518 [04:36:56]
A nice GUI frontend for ffmpeg.
First Submitted: Sun, 18 May 2008 04:28:31 +0000
Last Updated: Mon, 30 Jun 2008 04:23:08 +0000
winff 0.42-1 (Unsupported): GUI for ffmpeg
==> winff dependencies:
- ffmpeg (already installed)
- rpmextract (already installed)
==> Edit the PKGBUILD (recommended) ? [Y/n] ("A" to abort)
==> ----------------------------------------------
==>y
Please add $EDITOR to your environment variables
for example:
==> Edit PKGBUILD with: (replace gvim with your favorite editor)
==> Edit ./PKGBUILD with: gedit
==> winff dependencies:
- ffmpeg (already installed)
- gtk (already installed)
- gdk-pixbuf (package found)
==> Continue the building of 'winff'? [Y/n]
==> ----------------------------------------------
==>y
==> Building and installing package
==> Making package: winff 0.42-1 (Tue Jul 1 21:34:12 CEST 2008)
==> Checking Runtime Dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for inter-conflicts...
Targets: gdk-pixbuf-0.22.0-4
Total Download Size: 0.00 MB
Total Installed Size: 0.70 MB
Proceed with installation? [Y/n]
checking package integrity...
(1/1) checking for file conflicts [############################################################] 100%
(1/1) installing gdk-pixbuf [############################################################] 100%
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Downloading winff-0.42-amd64.deb...
--2008-07-01 21:34:13-- http://winff.googlecode.com/files/winff-0.42-amd64.deb
Resolving winff.googlecode.com... 64.233.187.82
Connecting to winff.googlecode.com|64.233.187.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1383594 (1.3M) [application/x-archive application/x-debian-package]
Saving to: `winff-0.42-amd64.deb'
100%[=============================================================================>] 1,383,594 191K/s in 7.4s
2008-07-01 21:34:21 (183 KB/s) - `winff-0.42-amd64.deb' saved [1383594/1383594]
==> Validating source files with md5sums...
winff-0.42-amd64.deb ... Passed
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...
x - debian-binary
x - control.tar.gz
x - data.tar.gz
./usr/
./usr/bin/
./usr/bin/winff
./usr/share/
./usr/share/doc/
./usr/share/doc/winff/
./usr/share/doc/winff/copyright
./usr/share/doc/winff/winff.pdf
./usr/share/doc/winff/README.txt
./usr/share/doc/winff/README-Icons.txt
./usr/share/doc/winff/README-Presets.txt
./usr/share/doc/winff/changelog
./usr/share/applications/
./usr/share/applications/winff.desktop
./usr/share/winff/
./usr/share/winff/winff.png
./usr/share/winff/presets.xml
./usr/share/winff/languages/
./usr/share/winff/languages/winff.es.po
./usr/share/winff/languages/winff.nl.po
./usr/share/winff/languages/winff.fr.po
./usr/share/winff/languages/winff.pb.po
./usr/share/winff/languages/winff.tr.po
./usr/share/winff/languages/winff.de.po
./usr/share/winff/languages/winff.zh.po
./usr/share/winff/languages/winff.it.po
./usr/share/winff/languages/winff.pt.po
./usr/share/winff/languages/winff.pl.po
./usr/share/winff/languages/winff.bg.po
./usr/share/winff/languages/winff.po
==> Tidying install...
-> Removing info/doc files...
-> Compressing man pages...
-> Stripping debugging symbols from binaries and libraries...
==> Creating package...
-> Generating .PKGINFO file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: winff (Tue Jul 1 21:34:22 CEST 2008)
==> Continue installing 'winff'? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ----------------------------------------------
==>y
loading package data...
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: winff: requires ffmpeg gtk gdk-pixbuf
==> WARNING: Your package is saved in /tmp/winff-0.42-1-x86_64.pkg.tar.gz
I tried doing it without changing the package name to winff-amd64, but same thing happens. What's going on?

Ahh man, and that's it! It works.
I'm just wondering now how can I contribute this PKGBUILD to AUR, but I can read that in the wiki too.
Thanks!

Getting "JTA transaction is not present" error while updating db table.

Hi All,
In one of my BPEL process, In a loop, I am updating value of database column Flag from 0 to 1. It was working fine in dev environment, but failed in Prod with below errors, Can Any one suggest on this.
There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.
OPMN logs:
<2010-05-05 01:56:49,395> <ERROR> <gemptp.collaxa.cube.engine> The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Thanks in advance.

I can envisage this happening only in a case where the update is taking a longer time than the value of JTA transaction timeout.
Is this happening for all BPEL instances or some of them get thru succesfully ?
Are you EVER updating that particular row of your table ( before/after) ?
-Shishir

FI Business Flow related to BW/ BI

Hi SDN,
I need some information regarding the FI Business Flow related to BW/ BI. Any case studies or scenarios would be highly appreciated.
Thanks in Anticipation,
Ankit

Hi Ankit,
Not sure if you are looking for this..
In FI flow w.r.t. BI, basically there are 5 major topics/areas:
1. GL Accounting -related tables are SKA1, SKB1 Master dataBSIS and BSAS are the Transaction Data.
2. Account Receivables- related to Customer . All the SD related data when transfered to FI these are created. Related Tables BSID and BSAD.
3. Account Payable's - related Vendor. All the MM related documents data when transferred to FI these are created .
Related Tables BSIK and BSAKAll the above six tables data is present in BKPF and BSEG tables.You canalso link these tables with the help of BELNR and GJAHR and with Dates.
4. Special Purpose Ledger.
5. Asset Management- In CO there are Profit center Accounting and Cost center Accounting.
Cheers,
Tanish

Master-Detail Relation- Detail records not displaying

Hi All,
I am working forms(10g) customization for an oracle applications. our requirement is to develop a new window(screen) which should display all the related child records for the master record in the main form on a button press.
i have developed a new database block based on a vew and provided the relation with master block, and done the required customization.
But, when i run the form, and clicked on button, it is giving an error
FRM-40350 Query caused no records to be retrieved.below is the code that i have written on button click
BEGIN
          IF event = 'WHEN-BUTTON-PRESSED'
          THEN
          SHOW_VIEW('XXSCP_GBL_CUST_PEGGING_CON');
          SHOW_VIEW('XXSCP_GBL_CUST_PEGGING_STK');
          app_window.set_window_position('XXSCP_GBL_CUST_PEGGING_WIN',
                                         'CASCADE',
                                         'XXSCP_GBL_EXCEP_DETAILS_WIN');
      SET_BLOCK_PROPERTY('XXSCP_GBL_EXP_DETAIL_V',NEXT_NAVIGATION_BLOCK,'XXSCP_GBL_CUST_PEG_V');
      GO_BLOCK('XXSCP_GBL_CUST_PEG_V');
     -- fnd_message.DEBUG('before execute');
      EXECUTE_QUERY;
      :parameter.p_excep_detail := 'FALSE';
          ELSE
               NULL;
          END IF;
          EXCEPTION
               WHEN OTHERS
               THEN
               fnd_message.DEBUG('other error at button press'||SQLERRM);
          --     NULL;
END;I am able to query records in my view from database, but not working when i run the form.
ANy suggestion will be helpful.
Thanks in advance,
pavan

Duplicate post -- Re: Master-Detail Relation- Detail records not displaying

In MM related Transaction, trigger idoc

In MM related Transactions, MSC2N, MB1A etc trigger idoc for goods movement only after we enter plant and storage location.In the user exit i have written code to create an idoc and gave validations for plant, storage location it doesnt work.
Does anyone have an idea about how to restrict the batch for this condition.

Hi,
There are several user exits for MB1A Transac .
Exit Name           Description
MBCF0002            Customer function exit: Segment text in material doc. item
MBCF0005            Material document item for goods receipt/issue slip
MBCF0006            Customer function for WBS element
MBCF0007            Customer function exit: Updating a reservation
MBCF0009            Filling the storage location field
MBCF0010            Customer exit: Create reservation   BAPI_RESERVATION_CREATE1
MBCF0011            Read From RESB and RKPF For Print List in MB26
MBCFC003            Maintenance of batch master data for goods movements
MBCFC004            Maintenance of batch specifications for goods movements
It depends on what values u need from the screen.
Enhancement : MBCFC003 has the values of MATNR, WERKS, CHARG and also Material document header and item values.
The Userexit FM used is : EXIT_SAPMM07M_003.
Remember to check if the values are populated correctly before CALL CUSTOMER-FUNCTION '003' is called in the program. If those are the values u need then just write the code in the include of the exit.
Regards,
Ramya
Message was edited by:
        Ramya Kanakala

Transaction resources not released across program invocations using MVCC

I'm evaluating Berkley DB XML v2.4.13 for use in a new software product and have encountered problems with multiversion concurrency control.
I'm using the Java API and JRE 1.6.0_07. The platform is Windows XP Professional SP3.
When I create a transaction with snapshot isolation enabled, execute some XQueries that read/update the contents of a document and then commit or abort it, the resources allocated to the transaction do not appear to get released. I've used EnvironmentConfig.setTxnMaxActive() to increase the number of active transactions allowed but this just allows me to run my program more times before it eventually hangs.
When I set EnvironmentConfig.setTxnMaxActive() to a small number the program hangs before completing the first time I run it. When I set
EnvironmentConfig.setTxnMaxActive() to a high value then I can run my program several times before it hangs. Note that the program runs to
completion and exits cleanly. I used the task manager to verify that all processes started by the program are gone when it completes. So
it appears that the resources allocated to a transaction are persisted in the database across program invocations. As a result the program
eventually hangs after running it several times. The number of times it can be run before hanging is directly proportional to how many active
transactions I've set with EnvironmentConfig.setTxnMaxActive(). It appears as if I'm not shutting down the environment cleanly but I've
read the documentation several times and am following the examples exactly. I've committed every transaction and have closed the XmlContainer,
XmlManager and the Environment.
When I use read-uncommitted, read-committed or serializable transaction isolation everything works fine. I'm only seeing this problem when
I use snapshot isolation. Am I doing something wrong or is this a known problem? If this is a known problem is there a work around?
Here's a copy of the program source code. Thanks in advance for any help you can provide.
package dbxml;
import java.io.File;
import com.sleepycat.dbxml.*;
import com.sleepycat.db.*;
public class txn
public static void main(String args[])
double partId = Double.parseDouble(args[0]);
int partCnt = Integer.parseInt(args[1]);
XmlTransaction txn = null;
Environment myEnv = null;
XmlManager myManager = null;
XmlContainer parts = null;
XmlQueryExpression qe;
XmlResults results;
XmlQueryContext context;
String readQry = "collection('parts.dbxml')/part[@number=$partId]";
String updQry = "replace value of node collection('parts.dbxml')/part[@number=$partId]/description with $desc";
try
EnvironmentConfig envConf = new EnvironmentConfig();
// If the environment doesn't exist, create it.
envConf.setAllowCreate(true);
// Turn on the transactional subsystem.
envConf.setTransactional(true);
// Initialize the in-memory cache
envConf.setInitializeCache(true);
// Initialize the locking subsystem.
envConf.setInitializeLocking(true);
// Initialize the logging subsystem.
envConf.setInitializeLogging(true);
envConf.setLockDetectMode(LockDetectMode.MINWRITE);
envConf.setLockTimeout(5000);
envConf.setTxnMaxActive(200);
envConf.setCacheMax(10000);
envConf.setMaxLocks(10000);
envConf.setMaxLockers(10000);
envConf.setMaxLockObjects(10000);
File envHome = new File("./dbxml/src/dbxml/dbhome");
myEnv = new Environment(envHome, envConf);
XmlManagerConfig managerConfig = new XmlManagerConfig();
managerConfig.setAdoptEnvironment(true);
myManager = new XmlManager(myEnv, managerConfig);
XmlContainerConfig containerConf = new XmlContainerConfig();
containerConf.setTransactional(true);
containerConf.setAllowCreate(true);
// Turn on container-level multiversion concurrency control
containerConf.setMultiversion(true);
parts = myManager.openContainer("parts.dbxml", containerConf);
TransactionConfig txnConfig = new TransactionConfig();
// set the transaction isolation-level
txnConfig.setSnapshot(true);
for (int i = 0; i < partCnt; i++, partId++)
// start a transaction
txn = myManager.createTransaction(null, txnConfig);
context = myManager.createQueryContext();
context.setVariableValue("partId", new XmlValue(partId));
context.setVariableValue("desc", new XmlValue(System.currentTimeMillis()));
qe = myManager.prepare(txn, readQry, context);
results = qe.execute(txn, context);
while (results.hasNext())
String part = results.next().asString();
System.out.println(part);
results.delete();
qe.delete();
// Prepare (compile) the query
qe = myManager.prepare(txn, updQry, context);
results = qe.execute(txn, context);
txn.commit();
results.delete();
qe.delete();
txn.delete();
txn = myManager.createTransaction(null, txnConfig);
qe = myManager.prepare(txn, readQry, context);
results = qe.execute(txn, context);
while (results.hasNext())
String part = results.next().asString();
System.out.println(part);
txn.commit();
results.delete();
context.delete();
qe.delete();
txn.delete();
catch (Exception e)
try
if (txn != null)
txn.abort();
catch(XmlException xe)
xe.printStackTrace();
e.printStackTrace();
finally
try
System.out.println("Shutting Down ...");
if (parts != null)
System.out.println("Closing Container");
parts.close();
if (myManager != null)
System.out.println("Closing Manager");
myManager.close();
System.out.println("Shut Down Complete");
catch (Exception xe)
xe.printStackTrace();
}

From the documentation I linked for you:
The environment should also be configured for sufficient transactions
using [DB_ENV->set_tx_max|http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/env_set_tx_max.html]. The maximum number of transactions
needs to include all transactions executed concurrently by the
application plus all cursors configured for snapshot isolation.
Further, the transactions are retained until the last page they created
is evicted from cache, so in the extreme case, an additional transaction
may be needed for each page in the cache. Note that cache sizes under
500MB are increased by 25%, so the calculation of number of pages needs
to take this into account.As you can see, to calculate the maximum number of transactions you should configure for, you should use the following formula:
number_of_txns = cache_size / page_size + number_of_concurrently_active_transactionsThis will give you a worst case figure - in practice you may find that a lower number will suffice.
You'll also notice that transactions remain allocated "until the last page they created is evicted from the cache", so you should find that checkpointing will also reduce the number of transactions necessary at any one time.
Using snapshot semantics only on read-only operations will give you the full value provided by MVCC. This means that the read-only (snapshot) transactions will take copies (snapshots) of the pages that are write-locked, but the transactions that write will wait on the write-lock. Using snapshot semantics this way will reduce deadlocks as intended - using snapshot semantics for write transactions just introduces [a new way to get a deadlock|http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/txn_begin.html#DB_TXN_SNAPSHOT]:
The error DB_LOCK_DEADLOCK will be returned from update operations if a snapshot transaction attempts to update data which was modified after the snapshot transaction read it.John

EJB3 : suspend JTA transaction does not release the connection in the XA DS

Hi all,
I did a test and after suspending a JTA transaction I note that in the xa datasource the activeconnection = 1.
So is it normal because I was thinking that when I suspend the transaction the teh connection is released and then after a transaction resume I could continue the transaction with another connection of the xa datasource ?
Thank you for all..
Christophe.

It's a long time ago, but did you ever solve this problem?
I'm having the same issue with OSB writing to a WLS8.1 JMS queue.
I have a development OSB server which works fine.
Pete

Transaction is not rolling back

I have statefull session CMT bean and I have a method
public void meth1() {
try {
dao1.method1(connection);
dao2.method2(connection);
} catch (SQLException ex) {
sessioncontext.setRollbackOnly();
throw (application exception);
If dao2.method2 raises sqlexception then whatever happend in dao1.method1 is committed. I have "Required" as transaction attribute for this session method.
Also I cannot raise system exception as this removes the session bean instance. We are using j2ee 1.2.
How to rollback for application errors.
Thanks in advance

I've never used oracle, so I can't say what your setup should be, however...
databases can have transactions and the syntax is different between databases, e.g.
start {start the transaction}
update table X .....
rollback {rollback the transaction}
should not update the database
but if table X does not support transactions, you can't do this.
I had this problem with mysql, where everything worked fine until I had an exception or called setRollbackOnly. Some stuff would rollback (ovbiously cached in the app server), but other stuff wouldn't.
I configured the tables in mysql to support transactions and it all worked.

Transaction is not Rolling Back in Stateless Session Bean

          Hi,
          I am using UserTransaction in Stateless Session bean .
          Transaction is not rolling back.
          The following code is writen in stateless session bean. In UserTransaction i am
          calling Two methods of another stateless session bean.
          The problem is if doJob2() method fails, doJob1() method is rolling back. These
          two methods consist of SQL statement with different Connection Object from TXDataSource.And
          session bean(TestSession) is set to CMT, attribute as "Required".
          try{
          Context ictx=new InitialContext();
          TestHome home=(TestHome)ictx.lookup("TestSession");
               utx = sessionCtx.getUserTransaction();
               utx.begin();
          TestRemote remote=home.create();
               remote.doJob1();
               remote.doJob2();
               utx.commit();
          }catch(Exception e)
               try{
               utx.rollback();
          }catch(Exception ex)
               System.out.println("unable to rollback"+ex);
          if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
          in catch block. but SQL statements executed thru. doJob1() are not rolling back.
          what might be the reason?
          thanks
          Ranganath


          Thanx Priscilla ,
          Transaction is working.
          ranganath
          "Priscilla Fung" <[email protected]> wrote:
          >
          >In your ejb-jar.xml, you should specify <transaction-type> element to
          >be "Container"
          >for container-managed transaction. If you specified it to be "Bean" for
          >bean-managed
          >transaction, EJB ontainer will suspend the caller's transaction before
          >starting
          >a new transaction for your doJobX() methods. Thus, doJob1()nd doJob2()
          >will be
          >executing in different transactions, and thus rolling back doJob2()'s
          >transaction
          >will have no effect on work done and committed in doJob1()'s transaction.
          >
          >Regards,
          >
          >Priscilla
          >
          >
          >"Ranganath" <[email protected]> wrote:
          >>
          >>
          >>
          >>I am sending config.xml,deployment descriptors, code snippet for TestSession.
          >>i
          >>am using weblogic6.0sp2.
          >>if you need any aditional info. please let me know.
          >>
          >>thanks
          >>ranganath
          >>
          >>EJB-JAR.xml
          >>
          >><?xml version="1.0"?>
          >>
          >><!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
          >JavaBeans
          >>1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
          >>
          >><ejb-jar>
          >>     <enterprise-beans>
          >>     <session>
          >>          <ejb-name>TestSession</ejb-name>
          >>          <home>com.apar.sslbridge.test.TestHome</home>
          >>          <remote>com.apar.sslbridge.test.TestRemote</remote>
          >>          <ejb-class>com.apar.sslbridge.test.TestBean</ejb-class>
          >>          <session-type>Stateless</session-type>
          >>          <transaction-type>Bean</transaction-type>
          >>          <resource-ref>
          >>     <res-ref-name>jdbc/oraclePool</res-ref-name>
          >>     <res-type>javax.sql.DataSource</res-type>
          >>     <res-auth>Container</res-auth>
          >>          </resource-ref>
          >>     </session>
          >>     </enterprise-beans>
          >>     <assembly-descriptor>
          >>     <container-transaction>
          >>          <method>
          >>          <ejb-name>TestSession</ejb-name>
          >>          <method-intf>Remote</method-intf>
          >>          <method-name>*</method-name>
          >>          </method>
          >>          <trans-attribute>Required</trans-attribute>
          >>     </container-transaction>
          >> </assembly-descriptor>
          >></ejb-jar>
          >>
          >>
          >>TestSession CODE:
          >>
          >>
          >>     public void doJob1() throws RemoteException
          >>     {
          >>     Statement st = null;
          >>     String query=null;
          >>     try{
          >>     con=getConnection();
          >>     st=con.createStatement();
          >>     query="insert into x values("+x+++")";
          >>     System.out.println(query);
          >>     int rec=st.executeUpdate(query);
          >>     }catch(SQLException sqle)
          >>     {
          >>     System.out.println("SQL Exception "+sqle);
          >> throw new RemoteException("RemoteException*****SQLError");
          >>     } catch (Exception e) {
          >>     System.out.println("Exception "+e);
          >> throw new RemoteException("RemoteException*****GenralError");
          >> }
          >>}
          >>
          >>
          >> public void doJob2()throws RemoteException
          >> {
          >> Connection con=null;
          >> Statement st = null;
          >> String query=null;
          >> try{
          >> con=getConnection();
          >> st=con.createStatement();
          >> query="insert into y values("+x+++")";
          >> System.out.println(query);
          >> int rec=st.executeUpdate(query);
          >> }catch(SQLException sqle)
          >> {
          >> System.out.println("SQL Exception "+sqle);
          >> throw new RemoteException("RemoteException*****SQLError");
          >> } catch (Exception e) {
          >> System.out.println("Exception "+e);
          >> throw new RemoteException("RemoteException*****GenralError");
          >>}
          >>}
          >>private Connection getConnection(){
          >>try {
          >>Connection con = StaticParams.POOL_DATASOURCE.getConnection();
          >>return con;
          >>     } catch(Exception e) {
          >>     System.out.println("TestBean.getConnection() Unable to get get pool
          >>connection
          >>" + e);
          >>     }
          >>}
          >>
          >>
          >>
          >>
          >>"Priscilla Fung" <[email protected]> wrote:
          >>>
          >>>It should work if you are using TxDataSource. Could you post your
          >config.xml,
          >>>deployment descriptors, code snippet for TestSession?
          >>>
          >>>Regards,
          >>>
          >>>Priscilla
          >>>
          >>>"Ranganath" <[email protected]> wrote:
          >>>>
          >>>>Hi,
          >>>>
          >>>> I am using UserTransaction in Stateless Session bean .
          >>>> Transaction is not rolling back.
          >>>>
          >>>>The following code is writen in stateless session bean. In UserTransaction
          >>>>i am
          >>>>calling Two methods of another stateless session bean.
          >>>> The problem is if doJob2() method fails, doJob1() method is rolling
          >>>> back. These
          >>>>two methods consist of SQL statement with different Connection Object
          >>>>from TXDataSource.And
          >>>>session bean(TestSession) is set to CMT, attribute as "Required".
          >>>>
          >>>> try{
          >>>> Context ictx=new InitialContext();
          >>>> TestHome home=(TestHome)ictx.lookup("TestSession");
          >>>>     utx = sessionCtx.getUserTransaction();
          >>>>     utx.begin();
          >>>> TestRemote remote=home.create();
          >>>>     remote.doJob1();
          >>>>     remote.doJob2();
          >>>>     utx.commit();
          >>>> }catch(Exception e)
          >>>> {
          >>>>     try{
          >>>>      utx.rollback();
          >>>> }catch(Exception ex)
          >>>> {
          >>>>     System.out.println("unable to rollback"+ex);
          >>>>     }
          >>>> }
          >>>>if any SQL Exception as occured in doJob2(), its calling method utx.rollback()
          >>>>in catch block. but SQL statements executed thru. doJob1() are not
          >>rolling
          >>>>back.
          >>>>what might be the reason?
          >>>>
          >>>>thanks
          >>>>Ranganath
          >>>
          >>
          >

Work flow related transactions r not working

Similar Messages

Maybe you are looking for