Blazeds Proxy Service Error

Trying to call an http service through a blazeds proxy
service and getting this error
faultCode = "Client.Error.MessageSend"
faultDetail = "Channel.Connect.Failed error
NetConnection.Call.BadVersion:
anyone see this b4?

Hi,
Can you please share the code? See if you can find any errors
in your stdout log file of your web server. If you find any errors
and cannot fix it, please share the code and the errors from the
log file.
Hope this helps.

Similar Messages

  • ALSB Proxy Service error calling Business service

    I have an external webservice on Weblogic 8.1 SP5, and I configured Business Service in ALSB 2.6, that is able to invoke the external webservice. But When I create Proxy Service based on the existing Business service and try to invoke the proxy service I get "no SOAP Action Header" error in WebLogic 8.1 SP5 External webservice.
    AxisFault
    faultCode: {http://xml.apache.org/axis/}Client.NoSOAPAction
    faultSubcode:
    faultString: no SOAPAction header!
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}stackTrace:no SOAPAction header!
    at org.apache.axis.transport.http.AxisServlet.getSoapAction(AxisServlet.java:1004)
    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    {http://xml.apache.org/axis/}hostname:ossinv1d
    no SOAPAction header!
    at org.apache.axis.transport.http.AxisServlet.getSoapAction(AxisServlet.java:1004)
    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:678)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Also I get
    com.bea.wli.sb.pipeline.PipelineException in the ALSB.
    Is it a known issue ?

    The back end service basically complains the SOAPAction http header was not included in the request. Typically this header is added automatically by ALSB if the proxy is of type SOAP and the wsdl contain the SOAPAction value for the operation invoked.
    Alternatively you can force the SOAPAction header to be set to the correct value by adding a transport header action in the request part of the routing node.
    Gregory Haardt
    ALSB Prg. Manager
    [email protected]

  • Issue in Proxy service Error Handler.

    Hi,
    Is it possible to reset or clear all variables used in a proxy service in error handler.

    Hi,
    You cannot delete all the variables at once.
    Please refer to the below link.
    http://docs.oracle.com/cd/E21764_01/doc.1111/e15867/proxy_actions.htm#i1316125
    Thanks,
    Durga.

  • Blazeds proxy service and failover

    Hello everyone,
    I've been using Blazeds for web services proxying. It's working great so far, but I'd like to add some failover mechanism.
    here below is a bird view of my architecture
    And what I'd like is to be able to support failover on business layer webservices, something like :
    I don't know if it's possible or not and if it is how I can achieve it. I was thingking about some failover tag in the proxy-config.xml to set several wsdl entries (URI-master, URI-slave...) but I didn't find nothing about that in the documentation. But maybe the solution is something drastically different .Anyway I hope that there is a way to make this possible
    Thank you in advance for your help.
    Olivier

    Hi,
    Can you please share the code? See if you can find any errors
    in your stdout log file of your web server. If you find any errors
    and cannot fix it, please share the code and the errors from the
    log file.
    Hope this helps.

  • Proxy-Service without a proxy-service.xml

    HI all,
    I'm trying to use the BlazeDS proxy-service to proxy my Web Service calls through so I can avoid the security issues of directly speaking to a remote SOAP Service.
    I am using Spring-Actionscript on the client now so I can externalize all of the server config into config files instead of code. I've been really frustrated at trying to do this for the SOAP Proxy-service. No matter what destination, channelset or remote url I set, the runtime insists on loading the destination channel information from the ServerConfig class.
    Is there no way around this hardcoded implementation? I've thought of exposing the services-config.xml and me downloading the file as the first thing I do in my flex app, or of bypassing the proxy service altogether and use RemoteObjects for Flex - Remote communication and let the RemoteObject deal with talking to the Web Service.
    Has anyone ever solved this problem? I'm wondering if Adobe will solve this in BlazeDS 4....
    Thanks for your help!!
    Ronak Patel

    Alex,
    I've been able to do this for RemoteObjects based on what Spring-Actionscript allows me to do.
    However from what I've seen in the stack trace from Flex...
    [MessagingError message='Destination 'point.service' either does not exist or the destination has no channels defined (and the application does not define any default channels.)']
    at mx.messaging.config::ServerConfig$/internalGetChannelSet()[C:\autobuild\3.5.0\frameworks\ projects\rpc\src\mx\messaging\config\ServerConfig.as:661]
    at mx.messaging.config::ServerConfig$/getChannelSet()[C:\autobuild\3.5.0\frameworks\projects \rpc\src\mx\messaging\config\ServerConfig.as:265]
    at mx.messaging::MessageAgent/initChannelSet()[C:\autobuild\3.5.0\frameworks\projects\rpc\sr c\mx\messaging\MessageAgent.as:1165]
    at mx.messaging::MessageAgent/internalSend()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\ mx\messaging\MessageAgent.as:1106]
    at mx.messaging::Producer/internalSend()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\m essaging\Producer.as:147]
    at mx.messaging::AbstractProducer/send()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\m essaging\AbstractProducer.as:507]
    at mx.rpc::AsyncRequest/invoke()[C:\autobuild\3.5.0\frameworks\projects\rpc\src\mx\rpc\Async Request.as:133]
    at services.pointclouddelivery::BasePointCloudDeliveryService/call()[E:\eclipse\workspace\li dar\lidar.client\src\main\flex\services\clouddelivery\BaseCloudDeliveryService.as:290]
    It is not even checking the channelSet that the Service class maintains...the code is generated by Flex Builder 3 to go directly to the services-config.xml.
    How can I break that dependency in the generated code?
    I know Flex 4 does some other stuff for Web Services with the RDS Servlet. Would this be better suited for XML configuration?

  • Report and Alert don't executed in the error handler with a JMS proxy service

    Hi,
    I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
    My error handler contains two main elements :
    - a Report action
    - an Alert with a JMS destination defined
    When the business service failed the message remain in the queue. It's the expected behavior.
    The problem is :
    - the report is missing
    - the alert is raised but missing in the JMS destination defined in the Alert setting.
    I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
    Unfortunately the message don't remain in the JMS queue.
    What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
    I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
    This solution is not convenient and I hope another solution is possible.

    Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
    wiki article on preparing your workgroup environment may require you to visit each machine individually.
    For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
    on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
    but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
    As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
    Please remember to click "Mark as Answer" on the post that helps you, and to click
    "Unmark as Answer" if a marked post does not actually answer your question. Please
    VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

  • Error while deploying polling dbadapter as proxy service in osb console

    Hi all,
    I have created a db adapter in Jdeveloper and imported it into oepe. I have create a proxy service from that . Which i have just deployed to verify on doing so i am getting the following execption.
    <Internal error occured in OSBConsole : null
    java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    Caused By: java.lang.NoClassDefFoundError: oracle/tip/adapter/api/NeedRARClassLoader
        at oracle.tip.adapter.sa.impl.meta.JCABindingEndpointMetadataHelper.validateJCAOperationSpecProperties(JCABindingEndpointMetadataHelper.java:272)
    I have admin server and no other managed servers. I have configured the Dbadapter and redeployed the adapter. I have tested the connection using a sample BPEL and it's working fine. Any suggestions......
    Thanks

    Hi Vladodias,
    Thanks for the reply. My dbadapter is active and is deployed to admin server i have checked it twice . I have no managed servers as all of them were in development mode . I have targeted the db adapter to the admin server.
    Here are the versions i am using
    Jdev 11.1.7
    WLS 10.6
    SOA Suite 11.1.6
    OSB 11.1.7
    Thanks....

  • Error while executing the proxy service

    Hi,
    I have a procedure which uses a database link to access my tables. And business service will invoke this procedure through JCA.
    We have created a datasource (Driver : non - XA for Service connections). However, while executing the proxy service it gives me below error.
    Do i need to change the type of driver. Can anybody please help me on this.
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Header xmlns:com1="com:gm:vehicleengineering:engineeringworkorder:ewostatus:types:ewostatusschema:1:0" xmlns:com="com:gm:common:utilities:types:servicecontrol:1:0">
    <com:ServiceControl>
    <com:Service>EWOStatus</com:Service>
    <com:Version>1.0</com:Version>
    <com:ConsumerID>CID</com:ConsumerID>
    <com:MessageID>MID</com:MessageID>
    <com:SentTimeStamp>2008-09-28T21:49:45</com:SentTimeStamp>
    </com:ServiceControl>
    </soapenv:Header>
    <soapenv:Body>
    <soapenv:Body>
    <com:ServiceFault xmlns:com="com:gm:common:utilities:types:servicefault:1:0">
    <com:FaultCode>SOAFLT-999</com:FaultCode>
    <com:FaultString>GeneralError</com:FaultString>
    <com:FaultActor>Server</com:FaultActor>
    <com:FaultDetail>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/VehicleEngineering/EngineeringWorkOrder/EWOStatus/V1/WSDL/jcaEWOStatus_1_0_0 [ GetEWOStatus_ptt::GetEWOStatus(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'GetEWOStatus' failed due to: Interaction processing error.
    Error while processing the execution of the SP_GETEWOSTATUS API interaction.
    An error occurred while processing the interaction for invoking the SP_GETEWOSTATUS API. Cause: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLException: Internal error: Cannot obtain XAConnection java.lang.ClassCastException: oracle.jdbc.driver.T4CConnection
         at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1684)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
         at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:126)
         at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:94)
         at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.connectInternal(DatasourceAccessor.java:327)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.connectInternal(DatabaseAccessor.java:295)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.reconnect(DatasourceAccessor.java:558)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1437)
         at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.incrementCallCount(DatasourceAccessor.java:303)
         at oracle.tip.adapter.db.DBConnection.getTopLinkSQLConnection(DBConnection.java:335)
         at oracle.tip.adapter.db.transaction.DBTransaction.beginInternal(DBTransaction.java:126)
         at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:93)
         at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:248)
         at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:534)
         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:572)
         at sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
         at $Proxy142.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:152)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:560)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
         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.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:591)
         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.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.CoLocatedMessageContext$1.run(CoLocatedMessageContext.java:164)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at com.bea.wli.sb.util.security.SecurityUtils.runAs(SecurityUtils.java:58)
         at com.bea.wli.sb.transports.CoLocatedMessageContext.send(CoLocatedMessageContext.java:157)
         at com.bea.wli.sb.transports.http.wls.HttpTransportProvider.sendMessageAsync(HttpTransportProvider.java:215)
         at sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
         at $Proxy122.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:152)
         at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:560)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
         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.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:591)
         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.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase$1.run(RequestHelperBase.java:152)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.transports.http.generic.RequestHelperBase.securedInvoke(RequestHelperBase.java:151)
         at com.bea.wli.sb.transports.http.wls.HttpTransportServlet.service(HttpTransportServlet.java:127)
         at weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:25)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3686)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Thanks,
    Chandana

    Make sure that you are using non-xa datasources and in DBAdapter outbound connection pool configuration provide the data source JNDI in "dataSourceName" property instead of "xADataSourceName" property. Update the DBAdapter after changing configuration.
    Regards,
    Anuj

  • Error while invoking web services from Proxy services in OSB

    I have a Proxy Service of message type in Oracel Service Bus 10gR3 and it passes the incoming messages from a JMS Queue to Business Service of Web Services type. This Web Service is hosted in Glass Fish v3 and it's binding style is RPC. The JRE used in both the servers are 1.6.0_20. The JMS message is of Text type. The Web Services at the Glass Fish throws MessageCreationException for any content of the JMS message. However, it works fine if Business Service's test client is invoked from the OSB'S Admin Console. However, the same will not work if Proxy Service's test client is called.
    The detailed exception stack is given below :
    Thanks for the help.
    - Raj
    com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
    at [row,col {unknown-source}]: [1,0]
         at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:359)
         at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:318)
         at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:92)
         at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:501)
         at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:285)
         at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:143)
         at org.glassfish.webservices.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:116)
         at org.glassfish.webservices.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
         at org.glassfish.webservices.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:196)
         at org.glassfish.webservices.EjbWebServiceServlet.service(EjbWebServiceServlet.java:127)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
         at com.sun.grizzly.http.servlet.FilterChainImpl.doFilter(FilterChainImpl.java:195)
         at com.sun.grizzly.http.servlet.FilterChainImpl.invokeFilterChain(FilterChainImpl.java:139)
         at com.sun.grizzly.http.servlet.ServletAdapter.doService(ServletAdapter.java:376)
         at com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.java:329)
         at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166)
         at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
         at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245)
         at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
         at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
         at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
         at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
         at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
         at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
         at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
         at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
         at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
         at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
         at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
         at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
         at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
         at java.lang.Thread.run(Thread.java:619)
    Caused by: com.sun.xml.ws.streaming.XMLStreamReaderException: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
    at [row,col {unknown-source}]: [1,0]
         at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:267)
         at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:95)
         at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:110)
         at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:100)
         at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:175)
         at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:303)
         at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:129)
         at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:354)

    Let me explain what I am trying to achieve. Our application receives data from multiple sources - from mainframe using FTP, JMS Queue and BPM application using Web Services. The data from all these sources are sending to a Web Service running in GlassFish V3. To handle this I have created three Proxy Services and one Business Service on OSB. The Business Service is of type Web Service using the same WSDL from the target Web Service.
    The Proxy Services are configured as follows:
    Proxy 1 (type - Messaging service) listens to the JMS Queue and receives JMS Text Message -> Business Service(B1) (Web Service).
    Proxy 2 (type - Messaging service Polls files from the FTP Server -> Business Service(B1) (Web Service).
    Proxy 3 (type - Web service) is invoked by the BPM application and sends a String -> Business Service(B1) (Web Service).
    All the Proxies route to the same Business Service - B1 which calls the Web Service in GlassFish. The only Proxy that works fine is Proxy 3 which is created using the same WSDL of the Web Service. In the other two proxies it thows the same exception in GlassFish as I mentioned before.
    com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:359)
    Is this configuration correct to achieve my requirements?
    Once again thanks for the help.
    - Raj

  • OSB - how to handle poll file error in FTP Proxy Service

    I configed a proxy service to poll file from a FTP server.
    How can I capture the error when the proxy service cannnot poll? (FTP server is down, folder not found, username invalid, etc )
    I want to make it show in the Operations >Message Reports table.

    It is not possible. Those errors will only be logged to logfile.
    Manoj

  • File Proxy Service Problem on errors

    In continuation of this thread...
    File Proxy Service Problem on errors
    We are now facing two problems.
    1.The proxy service is executed twice
    2.File is getting moved to error directory with prefixed file names which we are not able to retrieve and use in the notification email.
    Not sure how to fix :(

    1.The proxy service is executed twice Check if this is due to transaction timeout issue as discussed here. Re: OSB File polling working twice with the same file
    2.File is getting moved to error directory with prefixed file names which we are not able to retrieve and use in the notification email.I am not sure wehther you have any option here. You can check with support. Alternatively can raise notification mail with the timestamp and some file/business identifier from the file. The support person can then open the file from error directory to verify the file/business id in the file or educate the support user that the files will have a prefix

  • Error Destination in JMS Transport Configuration page (Proxy Services)

    Hi, Can anybody provides me the sample of Error Destination in JMS Transport Configuration page (Proxy Services) .I need to know the format. I am using "jms://<host:port[,host:port]*/factoryJndiName/destJndiName>", but it does not work.
    From Oracle webstie, http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html, the detail description of Error Destination is " In this field you can configure the name of the target destination for the messages, which have reached the maximum number of retry count. "

    Can you provide the JNDI name of the error destination alone there ?

  • Error using tuxedo proxy services in a cluster

    We have successfully created proxy services using tuxedo transport in single server ALSB configurations.
    We are now installing ALSB 2.6 in a cluster, and we cannot make the service work. We have configured WTC in all the servers of the cluster.
    When we invoke the service, we get the following error in the log
    ####<Feb 19, 2007 4:32:00 PM CLST> <Error> <TuxedoTransport> <quintay> <ALSB1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1171913520640> <BEA-381600> <Exception in TuxedoTask, java.lang.NullPointerException
    java.lang.NullPointerException
         at com.bea.wli.sb.transports.tuxedo.TuxedoTask.service(TuxedoTask.java:107)
         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:585)
         at weblogic.wtc.gwt.InboundEJBRequest.run(InboundEJBRequest.java:467)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Any help or workaround? Is it possible to use tuxedo transport in a cluster configuration? Other problem we have seen is that the ALSB console only allows us to deploy the service in one local domain. How can I deploy the service in all the wtc servers?
    Thanks in advance
    Mauricio Palma

    Yes, BEA released a patch which solves partially the problem, now we can invoke the proxy service from tuxedo. There are some features missing (for example, we have to configure a separate proxy service in each node of the cluster, with different names, and then import every service from tuxedo, so we cannot do fault tolerance).
    I don't know if the patch is available, we had to create a support case with BEA.

  • Error in a Proxy service

    Hi,
    I'm new to ALSB and created a weblogic webservice and imported it as a WSDL resource. This is then used for creating a business service. Now, I have a proxy service which take string as input (configured 2 proxy services, one takes from jms request queue and other from http request ) and depending on the string value, it will call the different method in the business service.
    When I tested it in the ALSB console, it is able to call the correct method in business service depending on input parameter. but always throw a error with http response code of 500. And it changed the $body with a Fault string of "Failed to get operation name for incoming request".
    If am able to test the business service in the alsb console successfully, why am not able to test the proxy service from the console?
    Thanks in advance for your help.

    I might need a bit more info here but it seems you are not setting the 'header' and 'body' variables correctly when calling the business service.
    Assuming your service is SOAP1.1, you need to assign valid soap body and header(optional) to those variables inside your route action.
    If you open the test console for the business service you should get the payload xml needed for the service. In the proxy, you will need to wrap that with <soap-env:Body> (soap-env is a pre-saved namesapce) and assign it to 'body'.
    If you have already done that then I defiantly need more info.
    Ryan

  • Errors "Load tModels into the registry" option & publishing proxy services

    Hi,
    I'm making a study with BEA Aqualogic Service Bus and BEA Aqualogic Service Registry.
    Reading official documentation (Console Help), I added with the BEA ALSB Console two registries. But during the configuration it doesn't allow me to set the *"Load tModels into the registry"* option, in fact when I click "Save" I get this error:
    *"Permission to generate key uddi:bea.com:servicebus:servicetype denied".*
    However I added two registries without setting this option.
    Now, when I want to publish a proxy service (in any registry), following the official procedure, I get this error:
    *"The publish completed with error. One or more services can't be published correctly, please see the detailed error messages in the summary table".*
    *"CannotCreate The key uddi:bea.com:servicebus:properties does not represent a valid taxonomy!"*
    I don't think it's all right! :)
    Someone can help me?

    Thank you for your help (even though you didn't know you were helping). I am also studying ALSB and ALSR, and I had the same problem when I tried to publish a proxy service ("... does not represent a valid taxonomy"). Based on your experience, I updated my registry in ALSB and checked "Load tModels". This was successful. I then published my proxy service and this too was successful.
    So the help you've given me was to suggest that publishing proxy services cannot be done unless the BEA tModels are first loaded into the registry.
    This means that your real problem is that you can't load the tModels. To do this, I suggest that the user ID you give when you're setting up the registry in ALSB must be an administrative user. When you installed the ALSR, an administrative account was created. Try giving this account information to the ALSB.
    If you don't want to give the administrative ID and password, you must set up an account in ALSR that has the ability to create tModels. In the ALSR's console page (probably at http://localhost:7001/registry/uddi/web), look at the administrative account's permissions (you'll find it on the "Manage" tab, under "Permissions"--you won't see the "Manage" tab unless you log in as an administrator). In my system, the administrator account has four permissions; I would guess that the one you need is "org.systinet.uddi.security.permission.ConfigurationManagerPermission".

Maybe you are looking for

  • Report painter add characteristis to a librairy

    Hello Like you know we can add some characteristics in report painter into a librairy. With transaction GCRT, and OSS note 395894 - Numeric variables in reports, it seems that we can add characteristic into a librairy. Until now I never saw an exampl

  • Load balancing on the local host only (6.40 Java)

    Hello! When configuring load balancing for Web AS 6.20 (Java), the property "LocalLoadBalancing" was available in the ServiceManager of the dispatcher. See Note 772561. This property is not available in Web AS 6.40 (SP14). How can I now ensure that a

  • Function module to input dates

    Hi All, Require function module where i can input From Date and To Dates as input parameters. This should appear as a dialog box.

  • All Songs "Hidden" on iPod

    Hi, After comming back from a vacation and turning on my iPod, I noticed that all of my songs were gone. I plugged it into my computer, and all of the songs did show up in iTunes. The "songs" playilst isn't showing up on my iPod even though the songs

  • Compiler error importing TestStand ActiveX Engine with Borland C++ Builder 6

    I'm having problems importing TestStand Engine Activex in Borland C++ Builder 6. In the file "TS_TLB.h" automatically generated, the compiler stops with the error message "E2034: Cannot convert 'Variant' to 'tagSAFEARRAY'" and the point in source cod