OSB-Faulthandling Framework

hi,
i know that there is a fault handling framework which has many fault policies in BPEL. By configuring it,(for eg: we can configure fault binding.xml file to handle many faults in BPEL) .we can reuse that framework in all BPEL process.
But now, is there any such faulthandling framework available for OSB which can be implemented and reused??
or do we need to define fault handling for each and every process?

But how to create a proxy which accepts all errors??When I say a proxy which accept all errors, means it could be a simple XML/SOAP/Messaging Type proxy which accept the error information in the format you want. Then in the message flow of that proxy you may apply the error handling logic you want.
To give example,
1. You may create a WSDL based SOAP proxy which accepts message for "HandleError" operation. Definitely it would act like a web service which would accept HandleError requests. Format of HandleErrorRequest can be customized by you. In the message flow of HandleError operation, just extract the information from incoming request SOAP message like error code, error message etc. and either store it in a DB or in a file to take actions later.
2. What you can do that from each and every error handler, publish a XML in pre-defined format to a JMS queue. The common error handler proxy will be a Messaging Type proxy which will accept XML as input. This Messaging Type proxy will poll the JMS Queue to pick the messages from there. Now in message flow of this JMS proxy do the required error handling processing.
Above two are just examples of what you may do. There may be other approaches as well.
Few things which you need to decide from business/functional point of view are -
1. Format of Error xml/document, which needs to be passed to common error handler proxy
2. Depending upon the input, type of proxy
3. Persistency required and if yes then whether file/DB
4. Whether Resubmission required
It totally depends on your business requirement and your solution design that how would you like to go about this.
Regards,
Anuj

Similar Messages

  • Clarification needed in the Fault Handling Framework(Error Hospital)

    Hi,
    I need some clarification on Fault Handling Framework...
    Scenario:
    My BPEL Process is Asynchronous.(10.1.3.3.1) and I tryed to invoke the another BPEL Process( which is used to select the Fname from the table using DB Adapter) . In the Main BPEL Process I have the Fault handling Framework and I done necessary changes in the bpel.xml. This is successfully working for Invoke Activity when ever an Remote or Binding Fault occurs in the Sub-BPEL Process and this Fault is send to Fault-Policy.xml in the server(bpel/domains/default/config/fault-Policy) and works accordingly to the action mentioned in the policy xml....( I have also made changes in the fault-bindings.xml ).
    How ever this Framework is working fine for every actions.
    Need Clarification:
    1) Only the Binding and Remote faults will work for the Fault handling Framework.
    2) can we use User defined faults (Buissness Faults,,,) for this........because I used the User defined faults to invoke the fault-policy.xml and it won't works....
    3)Only Invoke Activity can be handled for this Framework or any Other Activity........
    4)How to handle other Activity in the Fault-policy.xml...
    5)Any difference for Asynchronous or Synchronous in this Fault Handling Framework.......
    I also referred the Oracle SOA Suite New Feauters PDF .......
    Can any one send me the related documents and try to help me on this.
    Please help me on this.......
    Thanks,
    Ashok.

    Hi Chintan,
    You are saying that Custom faults are also supported for fault-Policy.xml.
    I can't understand that 2nd answer you said. can you please explain how to use the Custom faults in the FaultHandlingFramework..
    My Scenario:
    I have 2 BPEL Process, BPEL1 will invoke the BPEL2 and if any remote fault or binding faults occurs in the BPEL 2 its returning the same fault to BPEL1 and here I am using FaulthandlingFramework , this fault send to fault-policy.xml and necessary action is took place succesfuly...(like retry, human intervention.....)
    But when I throw some CustomFaults(userdefinedFaults)in the BPEL2 , its returning as a remotefault to BPEL1. I don't know how to use the customFaults in the Fault handling framework.......
    Can you explain me in detail how to use custom faults in faulthandling framework...............
    Send me some related documents for this.....

  • Throttling in OSB

    Hi,
    We are looking for Throttling in OSB, where in an OSB service should process only x requests at any given point of time. Work Manager maximum thread constraint is one way we found which enables throttling and can limit the number of threads processing the requests for a Proxy.
    Other way is to set throttling in business service, but it has limitation with the throtlling queues and issues of message getting discarded.
    Few questions on this approach are:
    1) Once max limit is reached OSB should return the denial of service request, how can it be done?
    2) How can we alert the max limit exceeding scenarios?
    3) Is there any other approach to achieve throttling?
    Thanks,
    Sowmya

    Hi Sowmya,
    First of all I would like to know why do you want to throttle inbound transactions to OSB? Which transport are you working with?
    1) Once max limit is reached OSB should return the denial of service request, how can it be done?Usually this is done at application server level instead of doing it at application level. In weblogic server, you may achieve it by setting value of "Maximum Open Sockets". You may also like to refer -
    http://www.ravisaraswathi.com/2010/03/configuring-weblogic-server-to-avoid.html
    2) How can we alert the max limit exceeding scenarios?You may use OSB alert framework -
    http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15867/monitoring_ops.htm#i1116097
    3) Is there any other approach to achieve throttling?same as 1st
    Regards,
    Anuj

  • How to get the input payload passed to the BPEL Process using java.

    Hi all,
    I am working on an application in which, if some fault occurs in the flow I need to insert the input payload that is being sent to the BPEL process into a Queue using Java. I have gone through the FaultHandling framework and failed to find the method by which we can get the input payload. Can someone kindly help me in getting the input payload. using the java.
    Regards

    Hi,
    Use method getVariableData with your input variable.
    Object getVariableData(String name, String part, String query)
    For example: getVariableData("input", "payload", "/");
    http://docs.oracle.com/cd/E17904_01/integration.1111/e10224/bp_java.htm
    Cheers,
    Vlad

  • Capability of File Adapter Framework in OSB

    Hi,
    Has anyone ever used the file adapter framework within Oracle Service Bus to capture data / transform using XSLT and then publish that data out to a service?
    Would greatly appreciate any experiences in this area, I know that this functionality exists in SOA suite and can be enhanced with BPEL.
    If anyone know of any limitations of OSB in this area that would also be good to know.
    Thanks
    K

    Hi,
    There's no problem in doing this. You can use a file adapter or the file transport.
    When using the file transport, it is possible to convert a flat-file structure to XML (and vice-versa) by using MFL. For more information on MFL: [http://biemond.blogspot.com/2008/12/flat-file-to-xml-with-oracle-service.html]

  • [OSB and OWSM] - External Web service stacks and frameworks

    Hi everyone ! I'm starting to read about OSB and OWSM and I'm having some doubts. I've some developments of Web services with external Stacks like CXF, JBossWS, Metro and I'd like to ask some questions:
    1- Will I be able to productively leverage all features of OSB and OWSM like creating a proxy service to add WS-* standards policies and features (WS-Security, for instance) even with these web services implemented in different stacks other than Weblogic's ?
    2- If it is possible, do these web services need to be deployed at the Weblogic server to enable the OWSM and OSB to work effectively ?
    3- Even if it is possible to use the OSB and OWSM nicely with webservices developed at external stacks and deployed at other application servers is there any reason to quit using these external web service stacks in favor of Weblogic's (like features only enabled on OSB/OWSM when the services use the Weblogic stack) ?
    I suppose that if I ignore the JAX-WS stack from Weblogic and use an external framework (like CXF) I'll lose most of the application server administration capabilities since the Weblogic server won't be able to recognize the CXF stack as it does with its own.But, the main doubt I'm in is, since OSB and OWSM might be used with external providers I probably won't need to develop my web services using the Weblogic implementation (which my team does not yet know) since there will be no features of the OSB and OWSM which can only be used with the Weblogic's stack. I would like, please, to know your oppinions about these considerations. Sorry about the long post and possible errors (I just started learning).
    Thank you!

    Hi Lupan,
    I can speak mostly to OWSM as my experience with OSB is small thus far.
    +1- Will I be able to productively leverage all features of OSB and OWSM like creating a proxy service to add WS-* standards policies and features (WS-Security, for instance) even with these web services implemented in different stacks other than Weblogic's ?+
    OWSM (10gR3) has two types of policy enforcement point (PEP) -- Gateway and Agent. The Gateway acts as a remote proxy and is neutral to the service implementation technology as long as it adheres to SOAP 1.1. In this regard you can use OWSM freely with CXF, MS implementations, etc. Agents run in-process with the service and thus have far greater restrictions on what service implementation frameworks and containers that are supported. There is some certification for AXIS 1.x running in OAS and Tomcat; but practically speaking, my recommendation for Agents is to only use within OAS 10gR3 where it is built in (and using OC4J Web Services through JAX-RPC).
    OWSM 11gR1 initially supports only agent-style (in process) PEP and is built-in to Fusion Middleware and WLS. It is only for Fusion and WLS Web Service implementations.
    OWSM is quite full-featured for WS-*.
    +2- If it is possible, do these web services need to be deployed at the Weblogic server to enable the OWSM and OSB to work effectively ?+
    "No" if using OWSM Gateway PEP. A qualified "Yes" if using OWSM Agent PEP.
    +3- Even if it is possible to use the OSB and OWSM nicely with webservices developed at external stacks and deployed at other application servers is there any reason to quit using these external web service stacks in favor of Weblogic's (like features only enabled on OSB/OWSM when the services use the Weblogic stack) ?+
    There is the manageability that you mention, but also there is the identity propagation scenario and tight security integration. Both OAS and WLS hosted services in the native stacks (JAX-RPC and JAX-WS) allow sophisticated and secure passing of identity in the request -- for instance, via SAML Assertions in the WS-Sec header -- and built-in capabilities to map the passed identity into the running service's Subject (i.e. enabling JAAS security etc.).
    In my experience this type of identity propagation functionality has either been absent or less complete in other typical implementation frameworks not closely aligned with the container security mechanisms.
    Hope this helps,
    Todd

  • Best practices or design framework for designing processes in OSB(11g)

    Hi all,
    We have been working in oracle 10g, now in the new project we are going to use Soa suite 11g.For 10g we designed our services very similar to AIA framework. But in 11g since OSB is introduced we are not able to exactly fit the AIA framework here because OSB has a structure different than ESB.
    Can anybody suggest best practices or some design framework for designing processes in OSB or 11g SOA Suite ?

    http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10223/04_osb.htm
    http://www.oracle.com/technology/products/integration/service-bus/index.html
    Regards,
    Anuj

  • Test framework for OSB

    Is there anything similar as the Test Suites in BPEL described here
    http://www.oracle.com/technology/oramag/oracle/07-nov/o67bpel.html
    for the OSB (formerly ALSB)??
    We are looking at some way to execute test cases for OSB flows just like you can in JDev for BPEL.
    thanks

    OSB does not have anything like "TestSuite" you described in above link. But some part of the use case can be accomplished by test console http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/testing.html#wp1052410. The testing can be done using Workshop for OSB (similar to JDEV for BPEL) http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/eclipsehelp/tasks.html#wp1151352. Even though documentation talks about split-join, the same can be applied to any Proxy/Business Service
    Thanks
    Manoj
    Edited by: mneelapu on Dec 22, 2009 9:22 AM

  • How can I monitor async requests in OSB

    Hello everybody,
    I have to set an async with response call to my legacy application. But as OSB does not support async calls with response yet, I'll use this approach described here: http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/jpdtransport/transport.html#wp1102152 that tells me to set up one proxy that will make the request to the legacy application, and another proxy to handle the callback (my application will call this one manually when it finishes the process).
    But, doing this, I'll have two distinct transactions, two distinct proxies, and no "natural" correlation between them. I need to set some correlation that allows me to create one SLA alert when the requisition takes more than X minutes. I already thought on sending the transaction id ($messageID) to my legacy application and have it returned to the response proxy. But doing this, I would still have no link between the information (when started, etc) of request proxy.
    Well, that is what I need to get done. Some way on measuring the execution time (in SLA Alerts) of my service. How this could be done?
    Thanks a lot guys.

    I have to set an async with response call to my legacy application. But as OSB does not support async calls with response yet, I'll use this approach described here: http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/jpdtransport/transport.html#wp1102152 that tells me to set up one proxy that will make the request to the legacy application, and another proxy to handle the callback (my application will call this one manually when it finishes the process).
    But, doing this, I'll have two distinct transactions, two distinct proxies, and no "natural" correlation between them. I need to set some correlation that allows me to create one SLA alert when the requisition takes more than X minutes. I already thought on sending the transaction id ($messageID) to my legacy application and have it returned to the response proxy. But doing this, I would still have no link between the information (when started, etc) of request proxy.
    Well, that is what I need to get done. Some way on measuring the execution time (in SLA Alerts) of my service. How this could be done?What would be the transport of communication with legacy system (JMS)?
    1) OSB is efficient in stateless point to point invocation/message enrichment but this problem appears to be use case in orchestration which is better addressed by BPEL.
    2) SLA alerts in OSB are designed to work at a single proxy level. Using SLA alert framework in OSB for your use case is not possible.
    3) At other level OSB also does not expose metrics (http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/jmx_monitoring/concepts.html) that will allow you to do this type of correlation using external java program.
    My two cents
    Manoj

  • OSB Log file

    OSB logging using message flow logs the messages to domain admin server log file.
    is it possible to route the OSB logs to a central logging system such as sys logs?

    You will need to create some Java classes that implement the log4j framework and expose some static methods that will have logger statements.
    For ex: Create One java class call SBLogger. This should have the implementation for a log4j logger by reading a log4j.xml or log4j.properties file. And create one static method like logMessage(str LoggerName, strLogMessage, strLogLevel). Inside this method create a logger with the strLoggerName and then have the corresponding logger.debug() or logger.info() type statements based on the log level. Or you can create different methods one each for debug, info , etc... log levels like logDebugMessage(message).
    Once you have tested this externally, create a jar file (with the *.class of the log4j implementation) and upload this to the osb console are jar. Ensure that you place the log4j properties file in the config folder of the osb domain, so that osb will be able to load it when it starts up. [After placing the log4j.xml file, you will need to restart the domain for it take effect]
    Now using java callout, you can invoke the corresponding logging methods, which will log into the files depending on the log4j.properties appender configuration.
    For changing the loglevels on the fly you can refer to a solution given by Ananth @ http://ananthkannan.blogspot.com/2009/10/how-to-change-log-levels-on-fly-using.html
    Hope this information will help you to proceed with the implementation. Do let me know in case you run into issues.
    Thanks,
    Patrick

  • OSB configuration exception

    Hello,
    I am getting following exception when creating a OSB configurations jar file using ant script.
    [java] java.io.FileNotFoundException: alsbdebug.xml (Permission denied)
    [java]      at java.io.FileOutputStream.open(Native Method)
    [java]      at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    [java]      at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
    [java]      at com.bea.wli.sb.debug.ALSBDebug.getDebugFlagsDocument(ALSBDebug.java:487)
    [java]      at com.bea.wli.sb.debug.ALSBDebug.flags(ALSBDebug.java:454)
    [java]      at com.bea.wli.sb.debug.ALSBDebug.getALSBDebuggerDebugLogger(ALSBDebug.java:393)
    [java]      at com.bea.wli.sb.debug.ALSBDebugLoggerService.<init>(ALSBDebugLoggerService.java:41)
    [java]      at com.bea.wli.sb.debug.ALSBDebugLoggerService.init(ALSBDebugLoggerService.java:84)
    [java]      at com.bea.alsb.core.internal.config.service.EclipseALSBStarter.initConfigService(Unknown Source)
    [java]      at com.bea.alsb.core.internal.config.service.AlsbConfigService.start(Unknown Source)
    [java]      at com.bea.alsb.core.AlsbCore.start(Unknown Source)
    [java]      at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
    [java]      at java.security.AccessController.doPrivileged(Native Method)
    [java]      at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
    [java]      at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
    [java]      at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
    [java]      at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
    [java]      at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
    [java]      at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
    [java]      at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:449)
    [java]      at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:211)
    [java]      at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:381)
    [java]      at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:457)
    [java]      at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
    [java]      at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
    [java]      at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
    [java]      at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    [java]      at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:326)
    [java]      at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231)
    [java]      at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193)
    [java]      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:160)
    [java]      at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:874)
    [java]      at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
    [java]      at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51)
    [java]      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:189)
    [java]      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    [java]      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    [java]      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
    [java]      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    [java]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java]      at java.lang.reflect.Method.invoke(Method.java:597)
    [java]      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
    [java]      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
    [java]      at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
    [java]      at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
    I am unable to find the file called "alsbdebug.xml" , Can someone tell me where is this file located ?
    Thanks & Regards,
    Prashant,

    Hi Prashant,
    You may find alsbdebug.xml inside your domain home i.e. $Middleware_Home\user_projects\domains\<Domain_Name> directory.
    Regards,
    Anuj

  • Error while OSB Building on UNIX Machine

    Hi All,
    I am building OSB Projects on OSB Server on UNIX Machine using ant scripts. The script runs properly on Windows. OSB Version being used is 11.1.1.4. I am getting the following error while creating sbconfig.jar:
    !SESSION 2011-09-05 11:26:40.424 -----------------------------------------------
    eclipse.buildId=M20100909-0800
    java.version=1.6.0_23
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
    Framework arguments: -application com.bea.alsb.core.ConfigExport -configProject OSB Configuration -configJar /var/build/osb_deployment/deployment/domains/osb/cz-osb-build.jar -configSubProjects Project_A,Project_B,Project_C -includeDependencies true
    Command-line arguments: -data /var/build/osb_deployment/temp -application com.bea.alsb.core.ConfigExport -configProject OSB Configuration -configJar /var/build/osb_deployment/deployment/domains/osb/cz-osb-build.jar -configSubProjects Project_A,Project_B,Project_C -includeDependencies true
    !ENTRY org.eclipse.osgi 4 0 2011-09-05 11:26:52.492
    !MESSAGE An error occurred while automatically activating bundle com.bea.alsb.core (768).
    !STACK 0
    org.osgi.framework.BundleException: Exception in com.bea.alsb.core.AlsbCore.start() of bundle com.bea.alsb.core.
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:806)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
         at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370)
         at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284)
         at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)
         at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:265)
         at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:106)
         at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:453)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
         at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:393)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:469)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)
         at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:232)
         at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1197)
         at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
         at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:904)
         at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
         at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
         at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
         at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
         at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
         at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
    Caused by: java.lang.NoClassDefFoundError: weblogic/descriptor/DescriptorManager
         at com.bea.alsb.core.AlsbCore.preStart(Unknown Source)
         at com.bea.alsb.core.AlsbCore.start(Unknown Source)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
         ... 34 more
    Caused by: java.lang.ClassNotFoundException: weblogic.descriptor.DescriptorManager
         at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:506)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         ... 39 more
    Root exception:
    java.lang.NoClassDefFoundError: weblogic/descriptor/DescriptorManager
         at com.bea.alsb.core.AlsbCore.preStart(Unknown Source)
         at com.bea.alsb.core.AlsbCore.start(Unknown Source)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
         at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370)
         at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284)
         at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)
         at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:265)
         at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:106)
         at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:453)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
         at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:393)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:469)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)
         at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:232)
         at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1197)
         at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
         at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:904)
         at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
         at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
         at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
         at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
         at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
         at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
    Caused by: java.lang.ClassNotFoundException: weblogic.descriptor.DescriptorManager
         at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:506)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         ... 39 more
    !ENTRY org.eclipse.osgi 4 0 2011-09-05 11:26:53.551
    !MESSAGE Application error
    !STACK 1
    org.eclipse.core.runtime.CoreException: Plug-in com.bea.alsb.core was unable to load class com.bea.alsb.core.internal.repositories.ConfigExportApplication.
         at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
         at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176)
         at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:904)
         at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
         at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
         at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
         at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
         at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
         at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
    Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle com.bea.alsb.core (768).
         at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:121)
         at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:453)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
         at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:393)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:469)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:338)
         at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:232)
         at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1197)
         at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
         ... 16 more
    Caused by: org.osgi.framework.BundleException: Exception in com.bea.alsb.core.AlsbCore.start() of bundle com.bea.alsb.core.
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:806)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
         at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370)
         at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284)
         at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417)
         at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:265)
         at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:106)
         ... 28 more
    Caused by: java.lang.NoClassDefFoundError: weblogic/descriptor/DescriptorManager
         at com.bea.alsb.core.AlsbCore.preStart(Unknown Source)
         at com.bea.alsb.core.AlsbCore.start(Unknown Source)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
         ... 34 more
    Caused by: java.lang.ClassNotFoundException: weblogic.descriptor.DescriptorManager
         at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:506)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
         at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
         at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         ... 39 more
    Please help!!
    Thanks in advance!!
    Regards,
    Karthik
    Edited by: Karthik Krishnamurthy on Sep 5, 2011 2:15 AM

    Hi Karthik
    Looking at the exception stack trace, looks like the root cause is this error: It is not able to find the class "weblogic/descriptor/DescriptorManager"
    java.lang.NoClassDefFoundError: weblogic/descriptor/DescriptorManager
    Well you need to set the .JAR that has this class in the classpath before you run your command or script. NOW you have to generate something called wlfullclient.jar.
    If you are using WLS 10.3.x, here is the link on how to generate a client jar file that has almost all the APIs from weblogic.jar and wls-api.jar etc etc. Most of the times, when we want to run WebServices, EJB clients etc as standalone, we need all these classes. So here is the link on how to generate something called "wlfullclient.jar" and put that in classpath or java build path etc.
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/jarbuilder.html (To create wlfullclient.jar)
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/t3.html
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/basics.html#wp1069994
    NOTE: I already generated this wlfullclient.jar and I do see the above missing class in this .jar file. So hopefully this should solve your issue.
    Thanks
    Ravi Jegga

  • Errors in direct binding invocation from BPEL to OSB

    Hi All,
    I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
    There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
    Any help about the management of this situation would be appreciated.
    Thanks,
    The log trace is the next one:
    [component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
    ORABPEL-05002
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
         at java.lang.Thread.run(Thread.java:662)
    And this is the payload from the instance details:
    <messages>
    <input>
    ... input data....
    </input>
    <fault>
    <exception class="com.collaxa.cube.engine.EngineException">
    JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
    <stack>
    <f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
    <f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
    <f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
    <f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
    <f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
    <f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
    <f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
    <f>...</f>
    </stack>
    </exception>
    <root class="oracle.fabric.common.FabricInvocationException">
    oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
    <stack>
    <f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
    <f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
    <f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
    <f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
    <f>java.security.AccessController.doPrivileged</f>
    <f>javax.security.auth.Subject.doAs#396</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
    <f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
    <f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
    <f>java.lang.reflect.Method.invoke#597</f>
    <f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
    <f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
    <f>...</f>
    </stack>
    </root>
    </fault>
    </messages>
    Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

    Hi All,
    I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
    There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
    Any help about the management of this situation would be appreciated.
    Thanks,
    The log trace is the next one:
    [component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
    ORABPEL-05002
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
    The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
    The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
    com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
         at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
         at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
         at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
         at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
         ... 15 more
    Consult the system administrator regarding this error.
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
         at java.lang.Thread.run(Thread.java:662)
    And this is the payload from the instance details:
    <messages>
    <input>
    ... input data....
    </input>
    <fault>
    <exception class="com.collaxa.cube.engine.EngineException">
    JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
    <stack>
    <f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
    <f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
    <f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
    <f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
    <f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
    <f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
    <f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
    <f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
    <f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
    <f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
    <f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
    <f>...</f>
    </stack>
    </exception>
    <root class="oracle.fabric.common.FabricInvocationException">
    oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
    <stack>
    <f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
    <f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
    <f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
    <f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
    <f>java.security.AccessController.doPrivileged</f>
    <f>javax.security.auth.Subject.doAs#396</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
    <f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
    <f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
    <f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
    <f>java.lang.reflect.Method.invoke#597</f>
    <f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
    <f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
    <f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
    <f>...</f>
    </stack>
    </root>
    </fault>
    </messages>
    Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

  • HAFileAdapter based OSB processing 1st file twice in 2 node cluster env

    Hi,
    I am trying my hands in OSB with HA File Adapter and came across a strange issue where in OSB service designed to pick up a message of "*.CSV" format and process it's record one at a time recursively as per below details:
    The reason I am saying it's been processed by 2 nodes of the cluster independently is because I can see 2 separate threads picking up same file at the same time on both the nodes in log files. I enabled the debugging property on managed servers.
    ----------------------------------------------------- Start Log Snippet -----------------------------------------------------
    Node 1 : ExecuteThread: '51'
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Translated inbound batch index "1" of fil
    e {CCISU_500.csv} sucessfully.>
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Publisher::publishMessage called with prim
    aryKey=[Qz6n0UOYTQ1oJ2QeawJThlv-jKbiLeH1Bkko5wHl1Lg.]>
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Sending batch to Adapter Framework for pos
    ting to BPEL engine: {
    batchId=_-H9OvOxmH30ZcxGkXWAK8mVTcajl3SHsnnVKxfsEBU., batchIndex=1, publishSize=1
    }>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699920> <BEA-000000> <Copying file :/FileAdapters/Input/CCISU_500.csv to user-defined archive directory for processed files :/FileAdapters/Archive>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699928> <BEA-000000> <Deleting/Soft deleting file : /FileAdapters/Input/CCISU_500.csv>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699928> <BEA-000000> <Deleting file : CCISU_500.csv>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699929> <BEA-000000> <Deleted file : true>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699929> <BEA-000000> <Poller has reached max raise size, will not raise anymore>
    Node 2 : ExecuteThread: '53'
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Translated inbound batch index "1" of file
    {CCISU_500.csv} sucessfully.>
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Publisher::publishMessage called with prima
    ryKey=[ODfzwSUr85GeHkzscyhXrh2URW1FEAposlikUkdTZL8.]>
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Sending batch to Adapter Framework for post
    ing to BPEL engine: {
    batchId=ZkZ5HZA43QtsPZFqU2prPmxVS83NBMHcZa5n76yKC-Q., batchIndex=1, publishSize=1
    }>
    ####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Def
    ault (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700939> <BEA-000000> <Since file could not be copied to specifi
    ed archive directory, file : CCISU_500.csv_CbOXCcnMsRq44Slx2jiJrbM5vvgER0M_cYJsXlmvzWU= is being copied to a default archive directory :/oracle/ofmw3u/admin/ofmw3u_doma
    in/mserver/ofmw3u_domain/fileftp/defaultArchive/>
    ####<Oct 17, 2012 3:21:40 PM EST> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.De
    fault (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700940> <BEA-000000> <Endpoint will shutdown process to preven
    t data loss as file :CCISU_500.csv could not be being copied to default archive : /oracle/ofmw3u/admin/ofmw3u_domain/mserver/ofmw3u_domain/fileftp/defaultArchive/. Plea
    se ensure that there is enough free space available to copy this file.
    java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or direct
    ory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:120)
    at oracle.tip.adapter.file.FileUtil.copyFile(FileUtil.java:1024)
    at oracle.tip.adapter.file.inbound.PostProcessor.defaultArchive(PostProcessor.java:300)
    at oracle.tip.adapter.file.inbound.PostProcessor.performArchival(PostProcessor.java:229)
    at oracle.tip.adapter.file.inbound.ProcessorDelegate.process(ProcessorDelegate.java:178)
    at oracle.tip.adapter.file.inbound.PollWork.publishFile(PollWork.java:1574)
    at oracle.tip.adapter.file.inbound.PollWork.processFilesInSameThread(PollWork.java:1001)
    at oracle.tip.adapter.file.inbound.PollWork.run(PollWork.java:335)
    at weblogic.work.ContextWrap.run(ContextWrap.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Oct 17, 2012 3:21:40 PM EST> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700940> <BEA-000000> <ProcessWork::run Fatal exception caught
    java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or directory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:120)
    at oracle.tip.adapter.file.FileUtil.copyFile(FileUtil.java:1024)
    at oracle.tip.adapter.file.inbound.PostProcessor.defaultArchive(PostProcessor.java:300)
    at oracle.tip.adapter.file.inbound.PostProcessor.performArchival(PostProcessor.java:229)
    at oracle.tip.adapter.file.inbound.ProcessorDelegate.process(ProcessorDelegate.java:178)
    at oracle.tip.adapter.file.inbound.PollWork.publishFile(PollWork.java:1574)
    at oracle.tip.adapter.file.inbound.PollWork.processFilesInSameThread(PollWork.java:1001)
    at oracle.tip.adapter.file.inbound.PollWork.run(PollWork.java:335)
    at weblogic.work.ContextWrap.run(ContextWrap.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Processer thread calling onFatalError with exception [java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or directory)]>
    ####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Unable to call onFatalError since the adapter could not find an endpoint>
    ####<Oct 17, 2012 3:21:40 PM EST> <Warning> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Poller::processFilesInSameThread will abort as the endpoint has been released>
    ----------------------------------------------------- End Log Snippet -----------------------------------------------------
    ----------------------------------------------------- Start Questions to the Gurus Out There -----------------------------------------------------
    1. Is there any property to make sure that only one activation agent is active at anytime in a cluster env ?
    2. Does JCA property "<property name="SingleThreadModel" value="true"/> holds good when used in OSB ? or it's just supported in composite ??
    3. Does both the nodes of cluster polls independently ? As I have seen in logs that node1 polling and complaining about time to live factor while the other node picking it before node1 completes another cycle of polling.
    4. In above log you can see that node1 processed all the records 1sec earlier than node2 in a race condition and as a result node2 completed about file not found exception?
    Gurus any help will be appriciated.
    ----------------------------------------------------- End Questions to the Gurus Out There -----------------------------------------------------
    ----------------------------------------------------- Start Details -----------------------------------------------------
    Protocol : jca
    Endpoint URI : jca://eis/FileAdapter
    Get All Headers : No Headers
    JCA: <adapter-config name="RequestHandler" adapter="File Adapter" wsdlLocation="RequestHandler.wsdl"; xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <connection-factory location="eis/HAFileAdapter" UIincludeWildcard="*.csv"/>
    <endpoint-activation portType="Read_ptt" operation="Read">
    <activation-spec className="oracle.tip.adapter.file.inbound.ScalableFileActivationSpec";>
    <property name="DeleteFile" value="true"/>
    <property name="MinimumAge" value="120"/>
    <property name="PhysicalDirectory" value="/FileAdapters/Input"/>
    <property name="PhysicalArchiveDirectory" value="/FileAdapters/Archive"/>
    <property name="PhysicalErrorArchiveDirectory" value="/FileAdapters/Error"/>
    <property name="Recursive" value="true"/>
    <property name="PublishSize" value="1"/>
    <property name="PollingFrequency" value="300"/>
    <property name="MaxRaiseSize" value="1"/>
    <property name="SingleThreadModel" value="true"/>
    <property name="IncludeFiles" value=".*\.csv"/>
    <property name="UseHeaders" value="false"/>
    </activation-spec>
    </endpoint-activation>
    </adapter-config>
    ----------------------------------------------------- End Detail -----------------------------------------------------
    Edited by: 964320 on Oct 17, 2012 10:58 PM

    You need to define the below property in composite.xml file of your bpel. This will allow only one adapter active and another passive to pick up the file.
    <activationAgents>
    <activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="PickupFile/FTPConsumer">
    *<property name="clusterGroupId">BPELProcessNameCluster</property>*
    <property name="portType">FTP/FileConsumer_Message_ptt</property>
    </activationAgent>
    </activationAgents>
    Thanks,
    Vijay

  • Problems starting Server on OSB 11g

    Hi Everybody,
    I have a problem, I just installed the Service Bus 11g on Red Hat and I have problems when I start the server.
    I particular first I start the Admin_Server without any exception and then I start the Server but I get this excedption:
    PATH=/app/olg/wlserver-10.3/wlserver_10.3/server/bin:/app/olg/wlserver-10.3/modules/org.apache.ant_1.7.1/bin:/app/jrmc-3.1.2-1.6.0//jre/bin:/app/jrmc-3.1.2-1.6.0//bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_14"
    Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
    BEA JRockit(R) (build R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32, compiled mode)
    Starting WLS with line:
    /app/jrmc-3.1.2-1.6.0//bin/java -jrockit -Xms256m -Xmx512m -Xmanagement -Dcom.sun.management.jmxremote -Djava.rmi.server.hostname=10.31.57.61 -Dcom.sun.management.jmxremote.port=17001 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder -Djava.awt.headless=true -Dweblogic.Name=Server_1 -Djava.security.policy=/app/olg/wlserver-10.3/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/app/olg/wlserver-10.3/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/app/olg/wlserver-10.3/wlserver_10.3 -Dwls.home=/app/olg/wlserver-10.3/wlserver_10.3/server -Dweblogic.home=/app/olg/wlserver-10.3/wlserver_10.3/server -Ddomain.home=/app/olg/bea-olgfwdomain/olgfwdomain -Dcommon.components.home=/app/olg/wlserver-10.3/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/app/olg/wlserver-10.3/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig -Doracle.server.config.dir=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/servers/Server_1 -Doracle.security.jps.config=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/carml -Digf.arisidstack.home=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/app/olg/wlserver-10.3/oracle_common/modules/oracle.ossoiap_11.1.1,/app/olg/wlserver-10.3/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=t3://10.31.57.61:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/olg/wlserver-10.3/patch_wls1033/profiles/default/sysext_manifest_classpath:/app/olg/wlserver-10.3/patch_ocp353/profiles/default/sysext_manifest_classpath weblogic.Server
    [JRockit] Management server started on port 17001, ssl=false, authenticate=false.
    <Dec 1, 2010 1:00:03 PM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>
    <Dec 1, 2010 1:00:05 PM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <Dec 1, 2010 1:00:07 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Dec 1, 2010 1:00:07 PM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Dec 1, 2010 1:00:07 PM CET> <Notice> <Log Management> <BEA-170019> <The server log file /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/logs/Server_1.log is opened. All server side log events will be written to this file.>
    <Dec 1, 2010 1:00:12 PM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Dec 1, 2010 1:00:14 PM CET> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_Server_1" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    <Dec 1, 2010 1:00:16 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Dec 1, 2010 1:00:16 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Dec 1, 2010 1:00:23 PM CET> <Warning> <Store> <BEA-280101> <The persistent file store "Reporting-FileStore_Server_1" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'ALSB Domain Singleton Marker Application' is not targeted>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'ALSB Domain Singleton Marker Application' is not targeted>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'Message Reporting Purger' is not targeted>
    <Dec 1, 2010 1:00:29 PM CET> <Alert> <OSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.>
    <Dec 1, 2010 1:00:30 PM CET> <Warning> <OSB Kernel> <BEA-398316> <Error getting the Result Cache /osb/service/ResultCache because the OSB Coherence Cache Provider has not been initialized.
    Additional error messages at server startup should point to the root cause for this error.>
    <Dec 1, 2010 1:00:30 PM CET> <Warning> <OSB Kernel> <BEA-398315> <Service Result Caching functionality is disabled because the result cache is unavailable.
    Additional error messages at server startup should point to the root cause for this. If you require Service Result Caching functionality, please fix the errors and restart the server.>
    <Dec 1, 2010 1:00:31 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: ftptransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Ftp Transport Provider/elek28]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:31 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: emailtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Email Transport Provider/tbi712]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: filetransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/File Transport Provider/qwi4ym]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: ejbtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/EJB Transport Provider/kyabv]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: tuxedotransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Tuxedo Transport Provider/9oa5mj/APP-INF/lib/tuxedo_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: aldsp_transport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALDSP Transport Provider/i3u01o/APP-INF/lib/aldsp_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: sftptransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/SFTP Transport Provider/d4v5rl]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: wstransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/WS Transport Provider/wuaaoy]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: flow-transport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/FLOW Transport Provider/kgaw7k]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: bpel10gtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/BPEL 10g Transport Provider/7iyhcx]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: jcatransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m], [Extension-Name: wsif, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m], [Extension-Name: JCAFrameworkImpl, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JCA Transport Provider' due to error java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType.
    java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType
    at com.bea.wli.sb.transports.jca.JCATransportProvider.loadAdapterList(JCATransportProvider.java:960)
    at com.bea.wli.sb.transports.jca.JCATransportProvider.getInstance(JCATransportProvider.java:80)
    at com.bea.wli.sb.transports.jca.JCATransportAppListener.preStart(JCATransportAppListener.java:16)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType
    at com.bea.wli.sb.transports.jca.JCATransportProvider.loadAdapterList(JCATransportProvider.java:960)
    at com.bea.wli.sb.transports.jca.JCATransportProvider.getInstance(JCATransportProvider.java:80)
    at com.bea.wli.sb.transports.jca.JCATransportAppListener.preStart(JCATransportAppListener.java:16)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: jejbtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JEJB Transport Provider/xyxmad], [Extension-Name: jejbtransport-jar, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JEJB Transport Provider/xyxmad]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JEJB Transport Provider' due to error weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
    at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
    at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: com.bea.wli.sb.transports.jejb.JEJBTransportAppListener
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:140)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: soatransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/SOA-DIRECT Transport Provider/16k7ar/APP-INF/lib/soa_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2], [Extension-Name: xbusrouting-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Routing' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c], [Extension-Name: xbustransform-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Transform' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3], [Extension-Name: xbuslogging-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Logging' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Test Framework' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: testfwk-l10n, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: testfwk-l10n, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Emergency> <Deployer> <BEA-149259> <Server 'Server_1' in cluster 'Cluster-1' is being brought up in administration state due to failed deployments.>
    Dec 1, 2010 1:00:37 PM oracle.dms.app.ServerInitializer oracle.dms.app.ServerInitializer
    INFO: DMS startup class is not started. DMS runs with reduced functionality.
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Ftp Transport Provider, EJBComponent: ftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.ftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.ftp, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Email Transport Provider, EJBComponent: emailtransport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.email. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.email, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: File Transport Provider, EJBComponent: filepoll.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.file. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.file, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: SFTP Transport Provider, EJBComponent: sftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.sftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.sftp, the provider URL is null>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster-1.>
    I tried to find something on internet but nothing suitable for me.
    Thanks

    From the error messages it does not seem to find any of the transport related jars (ftp, jca, email, etc..). Looks like there was an issue while creating the domain.
    Can you retry creating the domain and let us know if you are still getting the same error?
    Regards,
    Patrick

Maybe you are looking for

  • PLEASE HELP - I've tried everything

    Hello good people, My iPod nano connects and is visible in Device Manager yet invisible in My Computer and iTunes. I've tried everything I can possibly think of to try and solve this myself, all in vain. I've been using my nano 4G for quite some time

  • Using 2 ipods on same pc

    My dad has an existing 30GB ipod and has a lot of music in his library. I just bought a 30GB ipod for myself. When I connected it, all of the music in my dad's library was copied to my ipod. However, I can not access it from itunes. The text appears

  • Users logging on via CIF's lose login capability

    Multiple Netware 6.5 sp7 servers, with CIF's configured to offer windows shares to computers that do not use Novell Client. For years now, I've been able to set up XP Pro x64, Vista Business (x86 & x64) and Windows 7 (x86 & x64) systems so that they

  • Error while Installing Oracle Client 11g R2 64 bit on Windows 7 Enterprise 64

    I tried to install 32 bit drivers after installing the 64 bit drivers. The installer won't let me do it, claiming that [INS-32025] the chosen installation conflicts with software already installed in the given Oracle home. How can I get the 64 and 32

  • Payment list program default

    Hi Experts, I have developed a custom program to generate payment list / proposal list. Now I need to change the default program RFZALI20 during payment run - edit - payment list / proposal list. Anyone could help me ? Regards, Melissa