OSB ERROR

Hello All,
I am trying to clean the tapes on the library and i am using this command:
ob> clean drive dell-tape1 force --use 4
but getting this error:
Error: can't execute command - could not find a usable cleaning tape
please help
Regads
Wessam

Hi,
There is [url http://forums.oracle.com/forums/forum.jspa?forumID=264]Secure Backup that has been created to discuss Oracle's new tape backup software, Oracle Secure Backup (OSB) and Oracle Secure Backup Express ... I hope it can help you.
Cheers
Legatti

Similar Messages

OSB Error codes

What OSB error codes,I have to handle in the error handler stage when a route node finds that the given end point is not available and also when the end system is timing out.
Is it BEA-38000?
Thanks.

You should test various scenarios in your setup and check which errors you get in different scenarios. There can be many and the error codes will depend on type of transport as well (HTTP, FTP, FIle etc)
In case of Server found but service not available, you should get BEA-380000 error code with Not Found in description:
<con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:reason>Not Found</con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>response-pipeline</con:path>
     </con:location>
     </con:fault>In case server not running on same port:
<con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:reason>General runtime error: Socket Closed</con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>In case of Timeout set on Business Service triggering (Target service still processing and Socket gets closed because of preconfigured timeout value on BS), you should get BEA-380000 error code with SocketTimeOut exception stacktrace in Description.
<con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:reason>
     [WliSbTransports:381304]Exception in HttpOutboundMessageContext.RetrieveHttpResponseWork.run: java.net.SocketTimeoutException
java.net.SocketTimeoutException
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse$SocketTimeoutNotification.<clinit>(AsyncResponseHandler.java:551)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse.handleTimeout(AsyncResponseHandler.java:396)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse.timeout(AsyncResponseHandler.java:502)
at weblogic.socket.SocketMuxer$TimerListenerImpl.timerExpired(SocketMuxer.java:1052)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
     </con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>response-pipeline</con:path>
     </con:location>
     </con:fault>In case of Timeout while obtaining connection to remote server:
          <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:reason>General runtime error: connect timed out</con:reason>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>

OSB Error handling

Hi,
Could you point me to some OSB error handling examples? I am trying to understand how to handle errors at OSB. We are planning to build a number of message flows into OSB and trying to figure out the best way to handle errors.
Thank you

Hi
From the main entry point of a proxy service you can create an error handler (as well as stages, routing nodes etc).
In the Error Handlers you get the BEA error code which is sometimes helpful and sometimes not.
For example, if I have a validate node in my main flow that cause an XML validation error, that is easy recognisable so an 'if then' node will be able to route to the appropriate error handling logic. If the proxy service calls another service which throws a SOAP fault back, things get a little trickier as all you get back from the container is a BEA-380001 error code - basically an 'Internal Server Error'. So to sort this out you need an 'if then' node to trap this error code and then include a nested 'if then' node to look for the real error. The nest if statement condition would look something like "$body/soap-env:Fault/detail/mf:MyFault/mf:MyFaultcode = ERROR_CODE". Notice here, the way to get the actual fault it to use XPath to traverse the actual message returned and not use the $fault variable provided by the container.
I also suggest you create your own Fault type in an xsd so that the OSB always returns a consistent fault format.
In each of the 'if then' condition branches in the error handler I have an assign which creates the SOAP fault using the user defined fault type, a sanitised example of which is shown below.
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:gn="http://www.mycompany.com/wsdl/path/notification/1.0">
     <soapenv:Fault>
          <faultcode>gn:MyException</faultcode>
          <faultstring/>
          <detail>
          <fault:Fault xmlns:fault="http://www.mycompany.com/schema/fault/1.0">
               <fault:code>10000</fault:code>
               <fault:message>System Returned Error:
                    Details are:
                    Error Code - {fn:string($body/soap-env:Fault/detail/ser:ServiceException/ser:faultCode)}
                    Error Message - {fn:string($body/soap-env:Fault/detail/ser:ServiceException/ser:message)}
               </fault:message>
               <fault:processId>{fn:string($body/ns1:Type/ns2:id)}</fault:processId>
               <fault:shortMessage>system Returned Error</fault:shortMessage>
               <fault:time>{fn:current-dateTime()}</fault:time>
          </fault:Fault>
          </detail>
     </soapenv:Fault>
</soapenv:Body>
Notice how my fault type is populated in the detail stanza of the overall SOAP fault message.
This XML just gets assigned to body.
the very last thing in the error handler is to add a reply node "with failure" if you wish to return a soap fault or "with success" if you have handled the error and don't need tot return a fault.
Hope this at least points you in the right direction.
Cheers
MAtt

Query regarding handling and monitoring of OSB Errors in a specific manner

Hi,
I'm using
- OSB 10gR3 (10.3.1)
Context
To give some context, the setup I currently have a proprietory frontend client that is making XML/HTTP requests to OSB
which in turn is getting info from downstream systems.
I have no control over the behaviour/logic of the frontend client .. apart from knowing that it has a specific
request/response format.
So now to the issue..
The issue I'm facing is regarding handling of errors. Based on my knowledge of OSB, the error handling of the transaction has been
built along these lines
(Within the stage) If an error scenario's occurred, error is being thrown
(Within the error handler stage) Logging the error (using the 'Log' function .. with severity 'Error')
(Within the error handler stage) The response payload is being built .. so that the error can be reported to the frontend client
(Within the error handler stage) I'm doing a 'Reply with Success'
Now this does give me the expected behavior from the frontend client's perspective (... i.e. it receives the payload and displays whatever error that's occurred)
However from OSB's perspective, because I have done a 'Reply with success', the OSB Service Health Page ... (screenshot below) does not
increment the 'Errors' count for the respective proxy service ....
[OSB Service Health Page|http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/monitoring.html#wp1107685] (Looking at Figure 3-8)
The only way I could achieve this was to set the error handler stage to 'Reply with Failure' (which would return HTTP 500) ...
The issue however is that, the proprietory frontend simply sees the incoming HTTP 500 code and doesn't read the return XML payload (containing the error details ..)
which beats the whole idea of being able to maintain some sort of traceability for the failed transactions.
So what I'm basically trying to find is .. that when an error occurs
- Some 'call' to make the during the error handler stage so that it registers as an error in the OSB Service Health Page.. and I can clearly
see the error count, etc for each of the proxy services
- After that being able to still use 'Reply with Success' ... so that the payload is being returned with HTTP 500 code...
so the frontend can read the payload ...
............. in essence, the idea being to register errors so that they can be monitored via the Service Health Dashboard ..but at the same time
being able to return the 'error details' payload successfully
With my limited (but growing) knowledge of OSB .. I've tried quite a few ways to achieve this with no success...
Would very much appreciate any help here ...
Lastly, if there is some way of achieving what I'm trying to get to above through different means, I'm open
to trying out alternate stuff.
Regards,
Himanshu

Hi Atheek,
Many thanks for the reply. Does appear to be a pretty neat way of doing it ..
One more clarification I'd like on this however ....
Given that I have a set up like this below
[External frontend client] <------> (1 Parent Service) <------> (2 Child Service)
(1 Parent Service) .... has error handler .. and all it does is 'Reply with success'
(2 Child Service) .... has error handler for particular stage
so...
2 Child Service - is doing the actual work (has error handler where custom error msg is being populated in $body)
1 Parent Service - is the one that is getting called by the external client (has error handler .. and all it does is 'Reply with success')
What I currently have is ..once the error occurs, I'm populating $body ... with the custom error message within the error handler
Previously I had 'Reply with Success' in the 2 Child Service's error handler and the custom error message would get returned to the external client.
Now, with the error handler only creating the custom error msg.... and 1 Parent service doing the 'Reply with Success' .. it doesn't appear
to return the $body .. with the custom msg that I'd populated .. in 2 Child Service's error handler.
Are the $body contents populated in 2 Child Service's error handler lost ...once the error propagates up to 1 Parent service's error handler ?
If yes... is there way of getting around it ? I could see for instance that the $fault message context has a 'user populated' Details variable
but the documentation covering this is sparse.
Regards,

OSB Error in deploying a project with jca file adapter

Hi,
I am facing an issue where I am getting an error when deploying a service from Eclipse. I am using OSB/SOA 11.1.1.5 2 node cluster. I have an OSB service where I am writing to a file and am using file adapater. I created a composite with file adapter to write a file then imported .jac, .wsdl and composite into eclipse and generated a business service out of .jca file. When I deploy the project from eclipse I am getting the below error and am not able to deploy the project.
Conflicts found during publish.
Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
I have FileAdapter deployed and pointed to OSB manage servers cluster. Here is a snippet of config.xml.
<app-deployment>
    <name>FileAdapter</name>
    <target>SOA_Cluster,OSB_Cluster</target>
    <module-type>rar</module-type>
    <source-path>/app/oracle/fmw/Oracle_SOA1/soa/connectors/FileAdapter.rar</source-path>
    <deployment-order>321</deployment-order>
    <plan-dir xsi:nil="true"></plan-dir>
    <plan-path>/app/oracle/shared/SOA_Cluster/dp/FileAdapterPlan.xml</plan-path>
    <security-dd-model>DDOnly</security-dd-model>
    <staging-mode>nostage</staging-mode>
</app-deployment>
Also inside console -> deployments -> FileAdapter -> Targets and OSB_Cluster is checked also.
Here is the .jca file
<adapter-config name="writeFile" adapter="File Adapter" wsdlLocation="writeFile.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/HAFileAdapter"/>
<endpoint-interaction portType="Write_ptt" operation="Write">
    <interaction-spec className="oracle.tip.adapter.file.outbound.FileInteractionSpec">
      <property name="PhysicalDirectory" value="C:\ORACLE"/>
      <property name="Append" value="false"/>
      <property name="FileNamingConvention" value="a_%SEQ%.doc"/>
      <property name="NumberMessages" value="1"/>
    </interaction-spec>
</endpoint-interaction>
</adapter-config>
Any idea what might be wrong.
Thanks.

I already have the fileAdapter JNDI is already configured in console. The error I am getting is during the deployment
Conflicts found during publish.
Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
Thanks

OSB Error in Eclipse: The JCA dependency is not configured.

Hi All,
I am trying to use db adapter in OSB and I created the adapter in jdev and imported it in Eclipse.
I have installed Weblogic,OSB and configired the domain for osb, I can login to OSB and weblogic console.
I followed these steps to get there and now the db.jca file shows errors The JCA dependency is not configured.
http://guidoschmutz.wordpress.com/2010/08/08/oracle-service-bus-11g-and-db-adapter-a-different-more-integrated-approach/
Few of the things I noticed:
when I tried to copy the adapter from eclipse/plugin/*.jca/Dbadapter to Jdev/integration/lib/Dbadapter
I dint find one in eclipse/plugin/*.jca/Dbadapter
I created a OSB Configuration Project and not sure if it was created correctly and affecting this, as a matter of fact
are there any configurations I am missing to start.
I have like tight schedules and would really appreciate any help.
Thanks a lot again..

Yeah I checked that the wsdl is present.
One more thing I am noticing is the wsdl created in Jdev 11.1.1.4 doesnt show the binding and port when imported in the OSB Project resources.
Is there a way we can fix this?
Thanks.

OSB Error using Database JCA Adapter

I had a project working with a business service in OSB using JCA Adapter Service, after i inactivated the datasource to do unit case testing, the following error started appearing. I have recreated the datasource, the database adapter config and the have reinstalled the database adapter with no luck, the same error keeps showing: java.lang.IllegalStateException: Cause already initialized
have changed the <java:alsb-jca-framework-adapter-debug>true</java:alsb-jca-framework-adapter-debug> in alsbdebug.xml file but the onlly trace shown in the log is:
####<May 11, 2011 6:38:22 PM GMT-04:30> <Error> <JCATransport> <sapl953> <osb_server1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <ac651b1b82eb3313:-2f05eee:12fe1116dce:-7fff-0000000000000128> <1305155302965> <BEA-381967> <Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: java.lang.IllegalStateException: Cause already initialized
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: java.lang.IllegalStateException: Cause already initialized
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:155)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:571)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at $Proxy133.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:597)
at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: oracle.tip.adapter.sa.api.JCABindingException: java.lang.IllegalStateException: Cause already initialized
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:263)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:571)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at $Proxy133.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:597)
at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.IllegalStateException: Cause already initialized
at java.lang.Throwable.<init>(Throwable.java:67)
at java.lang.Throwable.initCause(Throwable.java:270)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:361)
at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:316)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:359)
at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:257)
at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:571)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
at $Proxy133.sendMessageAsync(Unknown Source)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:597)
at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:501)
at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:128)
at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Generally when you delete the data source, you will need to restart the server. I ran into a similar issue (but not the exact error) when I deleted a data source and was trying to create another with the same name without a restart. The issues got resolved once I restarted the server after the deletion of the data source and then recreated the data source after restart .
The com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: java.lang.IllegalStateException: Cause already initialized might be due to the same reason.
Can you do this and see it resolves your issue?
Thanks,
Patrick

OSB error "Pending resource availability " please reply ASAP

I have the problem with OSB 10.2. I can not get the file system backup and
I get following error.
"Pending resource availability "
Oracle Secure Backup

I have the problem with OSB 10.2. I can not get the file system backup and
I get following error.
"Pending resource availability "
Oracle Secure Backup

How to use Request header in the OSB error handler

Hi
I have a scenario where OSB proxy service accptes the payload and routes to the target service
and before routing, I'm generating UUId and inserting in to the request header and publishing the request payload along with UUID to another service.
when the target service is thrown some business fault,i need to publish the fault along with the header(which has UUID).since my target service sends only fault body,header is getting emptied in the error hanlder section.
How can I use the requestheader in the error handler section. Any help is highly appreciated.
Thanks,
N
Edited by: user13154768 on Sep 23, 2010 3:25 AM
Edited by: user13154768 on Sep 23, 2010 3:26 AM

Just assign your request header ($header) to your variable (e.g. $myRequestHeader) and than use this variable in your error handler. Fault response will override your $header but can't override $myRequestHeader.

OSB Error handlers..

Hi,
I have a problem in error handlers in catching errors. I have a proxy service and have configured message flows in which i have request audit stage, validate stage etc. Each stage has been configured with a stage error handler where i have configured email destinations to send alerts to. In request audit stage, i report the consumer's IP and other important request params. When everything is fine, i can see the params are reported in Dashboard and in the two tables. But when something is wrong, for example, i change the username/pw for the connection pool to connect to the database, the request audit stage is not able to report the request params as it couldn't connect to DB. So, I expect the request audit stage error handler to kick-in and send out email. But everything works fine and no email is sent out and i get the response. What type of errors the error handlers can handle? Does this include everything from java.lang.Exception?
Thanks in advance for your reply.
Kuppusamy.V.,

Ideally it should work. I did a quick test using a sample DB provider available on Oracle site.
I used the DB adapters given in :
http://www.oracle.com/technology/sample_code/products/osb/samples/OSB-DB-ADAPTER.zip
Created a new Proxy Service.
It has one Stage in request pipeline.
There is one Publish action which calls the DatabaseOutbound business service.
QoS is set to Exactly Once.
I have not created the Datasource and connection pool so my BS always errors out.
In the stage error handler I log the error and reply with failure.
When I run the above setup I see the log entries which I am doing in the error handler, so the flow is reaching the error handler and the logs also show that it is properly capturing the JCA errors.
Here is a cut form the debug window:
Stage Error Handler
$fault:
     <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380002</con:errorCode>
     <con:reason>
     Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/db/DatabaseOutbound_abstract [ DatabaseOutbound_ptt::insert(CustomerCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by java.sql.SQLException: The Network Adapter could not establish the connection.
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore....Can you try doing this using the DB adapter provided in the link? Just to rule out any JCA related issues.
Also what is the value of Transaction Required and Same Transaction For Response in your Proxy Service configuration?

Import config file on new OSB - error

Hi,
I used python scripts to import sbconfig.jar on OSB, and on previous version of OSB they worked perfectly.
Now they don't. I tried to integrate them with TeamCity, and when launching script I get
[11:17:54]: [java] Problem invoking WLST - Traceback (innermost last):[11:17:54]: [java] File "D:\TeamCity\buildAgSmith\BuildAgent\work\19084524096e640\osb_cofiguration\scripts\import_export_config_from_osb\import\import.py", line 203, in ?[11:17:54]: [java] File D:\TeamCity\buildAgSmith\BuildAgent\work\19084524096e640\osb_cofiguration\scripts\import_export_config_from_osb\import\import.py", line 44, in importToALSBDomain[11:17:54]: [java] File "D:\TeamCity\buildAgSmith\BuildAgent\work\19084524096e640\osb_cofiguration\scripts\import_export_config_from_osb\import\import.py", line 193, in getSessionManagementMBean
[11:17:54]: [java] File "<iostream>", line 1162, in findService
[11:17:54]: [java]      at weblogic.management.jmx.MBeanServerInvocationHandler.newProxyInstance(MBeanServerInvocationHandler.java:621)
[11:17:54]: [java]      at weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:418)
[11:17:54]: [java]      at $Proxy11.findService(Unknown Source)
[11:17:54]: [java]      at weblogic.management.scripting.WLScriptContext.findService(WLScriptContext.java:209)
[11:17:54]: [java]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[11:17:54]: [java]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[11:17:54]: [java]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[11:17:54]: [java]      at java.lang.reflect.Method.invoke(Method.java:597)
[11:17:54]: [java] java.lang.RuntimeException: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.bea.wli.sb.management.configuration.DelegatedSessionManagementMBean
[11:17:55]: [java] Java Result: 1
The error happens here:
print 'Read file', importJar
sessionName = createSessionName()
print 'Created session', sessionName
SessionMBean = getSessionManagementMBean(sessionName)
print 'SessionMBean started session'
ALSBConfigurationMBean = findService(String("ALSBConfiguration.").concat(sessionName), "com.bea.wli.sb.management.configuration.ALSBConfigurationMBean")
print "ALSBConfiguration MBean found", ALSBConfigurationMBean
log is :
Read file D:\TeamCity\buildAgSmith\BuildAgent\work\19084524096e640\osb_cofiguration\config_file\sbconfig.jar
[11:17:54]: [java] Created session SessionScript1275898674802
[11:17:54]: [java] Unexpected error: java.lang.RuntimeException
[11:17:54]: [java] Unexpected error: java.lang.RuntimeException
[11:17:54]: [java] No stack trace available.
The strangest that I couldnt find anything about this com.bea.wli.sb.management.configuration.DelegatedSessionManagementMBean.
Any help appreciated. Thanks.
UPDATE: Is there any possibility to import configuration project on 11g OSB?
Edited by: frf on 7/6/2010 3:21

http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15022/app_config.htm#i1012336
http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e15033/toc.htm
To upgrade AquaLogic Service Bus (2.6 and 3.0) and Oracle Service Bus (10.3.1.0) configuration to Oracle Service Bus 11g Release 1 (11.1.1.3) -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15032/upgrade.htm#sthref11
The ALSBConfigurationMBean Interface in the com.bea.wli.sb.management.configuration package in the Oracle Fusion Middleware Java API Reference for Oracle Service Bus includes example code illustrating how to import and export Oracle Service Bus configurations, how to change environment values, how to query resources, and so on. Please find it here -
http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e15033/toc.htm
Regards,
Anuj
Edited by: Anuj Dwivedi, TCS on Jun 7, 2010 5:02 PM

OSB error Pending resource availability

In Oracle Secure backup getting error Pending resource availability while starting the backup.
but restoration is working fine with the same tape..
Please help me ASAP.
Thanks & Regards,
Maruthi.G,
*** phone number removed by moderator - this is not an official support channel and personal contact details should not be included ***

Hi.
When I try to start a backup schedule, the catxcr command show the message : "No volume could be found in lib1 (for drive tape1) to use for job admin/7.1."
I don´t know the reason, because I insert a volume.
Please help.
root@bgtd T4# lsvol -L SL150 -l
bash: lsvol: command not found
root@bgtd T4# obtool lsvol -L SL150 -l
Oracle Secure Backup 10.4.0.3.0
Warning: auto-login failed - login token has expired
login: admin
Password:
Inventory of library SL150:
    in    1:             volume OSB-CATALOG-MF-000001, barcode JK1145L5, oid 100, 1480140800 kb remaining, expires 2015/03/12.15:20, mediainfo hw encryptable
    in    2:             volume OSB-CATALOG-MF-000001, barcode JK1145L5, oid 100, 1480140800 kb remaining, expires 2015/03/12.15:20, mediainfo hw encryptable
    in    3:             volume OSB-CATALOG-MF-000001, barcode JK1145L5, oid 100, 1480140800 kb remaining, expires 2015/03/12.15:20, mediainfo hw encryptable
    in    4:             volume OSB-CATALOG-MF-000001, barcode JK1145L5, oid 100, 1480140800 kb remaining, expires 2015/03/12.15:20, mediainfo hw encryptable
    in    5:             vacant
in
dte:
vacant
ob> lsdev --long SL150
SL150:
Device type:
library
Model:
[none]
Serial number:
[none]
In service:
yes
Debug mode:
no
Barcode reader:
default (hardware-selected)
Barcodes required:
no
Auto clean:
no
Clean interval:
(not set)
Clean using emptiest:   no
Ejection type:
auto
Min writable volumes:   0
UUID:
3d467542-9944-1032-9254-c8c374159d95
Attachment 1:
Host:
bgtd
Raw device:
/dev/scsi/changer/c4t500104F000D7B072d1
tape1:
Device type:
tape
Model:
[none]
Serial number:
[none]
In service:
yes
Library:
SL150
DTE:
1
Automount:
yes
Error rate:
8
Query frequency:
[undetermined]
Debug mode:
no
Blocking factor:
(default)
Max blocking factor:
(default)
Current tape:
[unknown]
Use list:
all
Drive usage:
23 seconds
Cleaning required:
no
UUID:
71373288-9944-1032-9254-c8c374159d95
Attachment 1:
Host:
bgtd
Raw device:
/dev/scsi/sequential/c4t500104F000D7B072d0
ob>

OSB Error propagation not propagating the original error

Hi,
I'm having trouble with understanding how to propagate error from inner to outer flow.
This is the scenario:
I have a flow listening on MQ queue, and in turn performs callouts to 3 inner flow's (protocol is local).
Inside the inner flows there is no error handler, and all the handling is performed at the outer flow.
The problem is that the error that is being caught is not the one I throw, instead I get a general BEA-380000 error.
(when I put an error handler at the inner flow and print $fault I see the real error).
Also I cannot put any "reply" operations inside any error handler because this will commit the XA transaction, and will prevent the message from going to backout queue - which I need to happen.
How can I make the error propagate correctly?

that's because the service error handler will wrap the fault in his own format
so in each service error handler you need to recreate the soap fault with the error stack, and reply that back to the calling service, otherwise you will loose the error details already in the proxy service in which the fault occures.
propagating the error without build the logic in each proxy service won't work if you ask me (and there also isn't a simple checkbox to enable anything on this)

OSB error while generating business service for FTP adapter Sync Get File

Hi All
I am trying to generate a business service from SOA Suite JCA FTP adapter Sync Get File, but i am getting this exception for no reasons (Rest operations list file, get file and put file are working)
Invalid JCA transport endpoint configuration, exception: java.lang.NullPointerException     Unknown ALSB Conflict.
Is this a bug in eclipse, can any body help me. Thanks
Sorry Forgot to mention eclipse version...
Eclipse Platform
Version: 3.6.2
Build id: M20110210-1200

Ok,
bcoz of this issue, i had to code the entire interface in OSB console. It runs fine in OSB console (i was able to test it successfully).
Is this a bug in eclipse or only i am facing this issue? Has anybody tried to create a business service from JCA FTP Get Synchronous jca file?
<adapter-config name="FTPReadMOMFileOnRMSDB" adapter="FTP Adapter"
     wsdlLocation="../wsdl/FTPReadMOMFileOnRMSDB.wsdl"
     xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
     <connection-factory location="eis/ftp/RMSDBFtpAdapter" />
     <endpoint-interaction portType="SynchRead_ptt"
          operation="SynchRead">
          <interaction-spec
               className="oracle.tip.adapter.ftp.outbound.FTPReadInteractionSpec">
               <property name="DeleteFile" value="true" />
               <property name="PhysicalDirectory" value="/MOMFiles/output" />
               <property name="FileName" value="*" />
               <property name="FileType" value="binary" />
          </interaction-spec>
     </endpoint-interaction>
</adapter-config>
One more doubt? The PhysicalArchiveDirectory path can be on the FTP server something like: /MOMFiles/archive. Or do i have to use the Put operation to move it to /MOMFiles/archive directory. Currently OSB console and eclipse do not accept FTP path for this parameter and want me to specify a local directory on server. Thanks

OSB-error on message reports

Hi,
In operations>Message Reports, when i select it, i get this error 'Message The server encountered an unexpected condition which prevented it from fulfilling the request.'
What could be the solution as i want to see the messages....
Thank You.

Make sure that wlsbjmsrpDataSource data source is up and running on weblogic admin console.
Regards,
Anuj

OSB ERROR

Similar Messages

Maybe you are looking for