Error during proxy processing Message E SG 105 cannot be processed in plugi

When I move a new custom proxy from Dev to Qa I am getting the above error when running the test from XI. However, the test runs fine in SPROXY test tool. Has anyone else run into this problem in the past? The error catagory is Dynamic_Call_Failure
Thanks,
Chris

Hi,
I'm facing the same problem.
I wrote an very easy report. It works as intended, but when i set fillable='X' i get the error FPRUNX 001.
FP_GET_LAST_ADS_TRACE return following:
Begin operation:
Render, elapsed time = 16 ms.
#   End operation: Render, elapsed time = 89 ms.
#   Begin operation: UsageRights, elapsed time = 89 ms.
#   End operation: UsageRights, elapsed time = 97 ms.#
...and the error string of FP_GET_LAST_ADS_ERRSTR is:
ADS: Request start time: Wed Jul 01 14:44:26 CEST 2009(200.101).
Any idea what the problem might be?

Similar Messages

Error during proxy processing

Hi Experts,
We have a web service hosted on PI and getting the Tax Jurisdiction values from Taxware via ECC(ECC has a TCP/IP connection to connect to Taxware system, From there ECC gets Taxjurisdiction Codes and gives back to PI).
When we make a call to this Web service following Error response has been given. Please let us know what could be the reason.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1 />
<SAP:P2>ZCL_GET_TAX_IN</SAP:P2>
<SAP:P3>GET_TAX_JURISDICTION_SYNC</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing Message E TAX_TXJCD 110 cannot be processed in plugin mode HTTP</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Thanks,
Sekhar.J

Hi,
We are using XI adapter. The same Web Service is working good in Development and Quality Enviroments, I am wondering why it is failing in Production Environement intermittently. And also in ECC we are using TCP/IP connection to fetch Tax Jurisdiction codes from TaxWare System. This TCP/IP connection was configured in SM59 of ECC. PI will make call to ECC and ECC will make call to TaxWare and returns the result back PI.
Thanks,
Sekhar.J

DYNAMIC_CALL_FAILURE Error during proxy processing An exception with the ty

Hi,
SRM 7.0 contains 2 clients:
Sender: 100 for EBP, logical system is CLNT100
Receiver: 200 for SUS, logical system is CLNT200
both the clients are connected through PI 7.0, logical system of PI is CLNT001.
From SPROXY of 100EBP, i'm executing the outbound proxy, in moni sent msg success.
In PI also msg is processed.
But in SUS200, it is showing below error msg:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX_TRADING_PARTNER_SUS_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Pls help in resolving the same....
tnx n rgds,
balu

Hi,
How did you solve the issue? Can you please provide the solution.
Thanks,
-Devi Swain

Error during proxy processing An exception with the type CX_BBPX1_STD_MESSA

Hello,everyone!
My PI version is 7.11,SRM SUS version is 7.0,ECC version is 6.0 ,When I import XI SRM CONTEN,sending IDOC in ECC,there is a error some of the mesages:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX1_SUSPO_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Detialed error from SXMB_MONI,
Error in XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 0015111411 with type 'Vendor' I:R5:553 -'Different country' field contents deleted because identical to 'Country' E:BS:002 -"Create" is not allowed (SUS Purchase Order 7100076527 ) Program: CX_BBP_BD_ERROR===============CP; include: CX_BBP_BD_ERROR===============CM002; Line:
This issue only ocuured for partner 0015111411, but we tried with other partner ID and those messages are processed sucessfully and PO is created.
I have a doubt that, is there functionality in proxy to compare the country with partner in SRM system. Could please anyone help me one the same.
Regards,
Baskaran K

HI,
This is a standard proxy. I'm not sure how to debug the proxy with payload. Could you please tell me the steps.
We have one more error message
<FAULT_TEXT>Error in XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner XY91 with type 'Sold-to Party' E:BS:002 -"Create" is not allowed (SUS Purchase Order 7100076526 ) Program: CX_BBP_BD_ERROR===============CP; include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
Is there any table to check these details like Sold-to Part, Vendor etc in SRM system?
Regards,
Baskaran K

Error during Proxy Processing from ECC system

Hi All,
I had created Webservice using ABAP in ECC system with Message interface designed in XI system. This Webservice will simply displays employee address when you enter employee id and address type.During my testing of Web service in ECC system via Tcode WSADMIN, I am getting below error
"An error has occurred. Maybe the request is not accepted by the server: "
"Error during proxy processing"
Request
POST /sap/bc/srt/xip/sap/Z_ADDRESS_01?sap-client=100 HTTP/1.1
Host: rpmsap3.rapidigm.com:8080
Content-Type: text/xml
Connection: close
authorization: <value is hidden>
Content-Length: 389
SOAPAction: ""
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><ns1:Request_Message xmlns:ns1='http://sap2webservice'><Employee_Id>MM01</Employee_Id><Address_Type>AM</Address_Type><Date>11/11/2006</Date></ns1:Request_Message></SOAP-ENV:Body></SOAP-ENV:Envelope>
Response
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><ns1:Request_Message xmlns:ns1='http://sap2webservice'><Employee_Id>MM01</Employee_Id><Address_Type>AM</Address_Type><Date>11/11/2006</Date></ns1:Request_Message></SOAP-ENV:Body></SOAP-ENV:Envelope> HTTP/1.1 500 Internal Server Error
set-cookie: sap-usercontext=sap-client=100; path=/
content-type: text/xml; charset=utf-8
content-length: 270
sap-srt_id: 20061111/154215/v1.00_final_6.40/A901A40749EEA74BB8D8AB72B56C02A7
server: SAP Web Application Server (1.0;640)
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><soap-env:Fault><faultcode>soap-env:Server</faultcode><faultstring xml:lang="en">Error during proxy processing</faultstring></soap-env:Fault></soap-env:Body></soap-env:Envelope>
Appreciate any help on above issue
Regards
Manish Mundra

Hi All,
Please help on below issue.
Thanks in Advance
Regards
Manish

Error during proxy processing An exception with the type CX_SY_OPEN_SQL_DB

Hi All,
I am facing the following problem in production server when even the file got processed successfully .
Error during proxy processing An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause The system tried to insert a data record, even though a data record with the same primary key already exists
Can you please suggest how it can be handled?
Regards,
Saras

You need to debug your proxy program and check all the insert statemrnts. Looks like there is an exception being thrown in the proxy (may be after the completion logic to push the data in to db) which is not being caught.
Proxies are object oriented and it is a good practice to implement Exception Handling mechanism.
VJ

BPM Error during delivery of message

Hi All,
I am working on BPM Scenario, to collect the files based on Correlation Id.
Its working file in PROD, Last 2 days back we processed 20 message, 4 was not processed. Data looks good, and i am trying to process those 4 records.
I am getting the below error in SMQ2.
SysFAIL - >Permanent error in BPE inbound processing -> Display Trace: 193 385 20091008225338.6300000 DATA SWF_INB EXCEPTIONS WF-BATCH X Error during delivery of message BDAAD94EA8454FA005F1A2C9416843DC to receive processes WS90100038 XBQO$PE_WS90100038 BDAAD94EA8454FA005F1A2C9416843DC
I cleared the SMQ2 and SWWL, and reprocessed the file, still i am getting same error...
SXMB_MONI_BPE - > Continoue Process flow after error nothing is displayed...
Any cause, i am getting the error???
Thanks,
SR

Hi Siva,
Normally this error occurs when your data not sufficient,check your data its correct or not,i think its not satisying your condition / corealtion what you defined in BPM.
Regards,
Raj

An "error during rendering/encoding" message

Hello, can someone help me? I'm trying to burn a dvd using idvd through imovie. I start to end the rendering of my menus and the message pops up:
Error during rendering/encoding
There was an error during rendering/encoding of the menus/slideshows. Burning process abored.
Can any one help with this issue? thanks
bryan

Bryan,
I just went through this problem, and this is the advice I got and that worked for me...
Joan Philgreen, "Error during rendering/encoding", 01:31am Aug 11, 2005 CDT
I hope your situation is as easy to fix as mine was.
-Joan

Error during activation a message mapping

Hi,
I get this error during activation a message mapping:
source code has an syntax error:
D:/usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapf1f9db20a78a11dac004000f1ff80130/source/com/sap/xi/tf/_Source2Target_.java:2: package com.sap.aii.mappingtool.tfapi does not exist import com.sap.aii.mapping.api.; import com.sap.aii.mappingtool.tfapi.; ^ 1 error
Can anybody help me please??
Thanks.
Regards
Stefan

Hi Michal,
I do not have deleted some libraries in the XI-Installation.
I have some customer functions in other mappings but no message mapping without or with customer function can I activate, now.
The mappings are in serveral software components but it is no chance to activate a message mapping.
Regards,
Stefan

HT4061 I can't download an application from Apple store. A message comes' your request cannot be processed'. Error code 1009

Hello,
I cannot download an application from Apple store. A message appeares "your request cannot be processed. Error code 1009 "

hi
i have a messege ( your request cannot be processed error code 1009) my iphone is 4s with ios 7.0.4 .
so cannot download in itunes
if i creat a new apple id problem is solved
thanks

BSP Error:Message E BL 203 cannot be processed in plugin mode HTTPs

Hi Experts ,
I am trying to navigate from one application to another by clicking on the opportunity that i have created.
While navigating i am getting the following error but this error does not occur for all the users.
The following error text was processed in the system:
Message E BL 203 cannot be processed in plugin mode HTTPs
Exception Class CX_SY_MESSAGE_IN_PLUGIN_MODE
Error Name
Program CL_CRM_BSP_FRAME_MAIN=========CP
Include CL_CRM_BSP_FRAME_MAIN=========CM001
ABAP Class CL_CRM_BSP_FRAME_MAIN
Method DO_REQUEST
Line 1003
Could you please help me in this regard.
Regards
D.Vadivukkarasi

You can use T_code SICF to active bc-->bsp and some components if you feel it is relevant.

Error: Message E RSDODSO 201 cannot be processed in plugin mode HTTP

Hi all,
We have developed a BSP page in which, on button click, the onInputProcessing has a code written where 'Performs' in ABAP programs are being called.
When i execute the page, the layout gets executed fine. But on clicking the button after entering text, the following error is thrown:
Message E RSDODSO 201 cannot be processed in plugin mode HTTP
Exception Class CX_SY_MESSAGE_IN_PLUGIN_MODE
Error Name
Program CL_RSD_DTA====================CP
Include CL_RSD_DTA====================CM01P
ABAP Class CL_RSD_DTA
Method FACTORY
Line 45
Long text -
Please provide your suggestions to resolve the error.
Thanks,
Abhishek.

Hi Karthik,
This error occurs if you are calling external ABAP Perform or program, and the program is trying to raise any message.
Please debug your BSP application to find out exactly where this message is being raised.
Hope this helps.
Thanks,
Abhishek.

Message E R7 005 cannot be processed in plugin mode HTTP

Hi All,
I test my BSP page with transaction : BPS_WB u2013 Customizing Web Interface Builder.
I press u2018display previewu2019 to check layout and it displays well.
If i have not change any data, it can save.
But i has error when i change or input date and save it.
The error message is "Message E R7 005 cannot be processed in plugin mode HTTP ".
Does anyone have any idea about tracing/debug bsp page?
BR.
Wu

Hi Tanguy,
I have actived the InfoProvider of my InfoArea,but it still has an error messge like before.
After i trace the function, i find it is a sap program error(Note 1244874 - Inherited Error in RSDRI_CUBE_WRITE_PACKAGE).
I will import SAP_BW SP20 and test the function again.
Thanks for your advices.
BR.
Wu

Con. Req. 'Receiving Transaction Manager' Inactive/No Manager : This request is an unconstrained request. (queue_method_code = I) , No concurrent manager is defined to process this request, so it cannot be processed.

Hi Gurus,
I need your help on a concurrent request ( Receiving Transaction Manager ) showing as Inactive/No Manager.
EBS: R12.1.2 on Linux
Database: 11.2.0.3 on HP UX Itanium
A user is submitting the concurrent request - "Receiving Transaction Manager" (It is a concurrent program not a concurrent manager). The request ends up as Inactive/No Manager. When I click on the diagnostics button this is what it shows -
"No concurrent manager is defined to process this request, so it cannot be processed.
Contact your system administrator to define a concurrent manager to process this request or to verify that existing concurrent managers have the correct specialization rules."
I ran analyzereq.sql and the analysis is
Analysis:
Request 1427025 is in phase "Pending" with status " Normal".
                           (phase_code = P)   (status_code = I)
This request is an unconstrained request. (queue_method_code = I)
It is in a "Pending/Normal" status, ready
to be run by the next available manager.
Checking managers available to run this request...
There is no manager defined that can run this request
This should show on the form as Inactive/No Manager
Check the specialization rules for each
manager to make sure they are defined correctly.
Additional information (from apps.FND_CONC.DIAGNOSE):
No concurrent manager is defined to process this request, so it cannot be processed.
Contact your system administrator to define a concurrent manager to process this request or to verify that existing concurrent managers have the correct specialization rules.
I ran another SQL to find out which manager runs the program :
select CONTROLLING_MANAGER,request_id
from fnd_concurrent_requests
where request_id=1427025;
It returned blank (or) NULL for controlling Manager.
select b.USER_CONCURRENT_QUEUE_NAME from fnd_concurrent_processes a,
fnd_concurrent_queues_vl b, fnd_concurrent_requests c
where a.CONCURRENT_QUEUE_ID = b.CONCURRENT_QUEUE_ID
and    a.CONCURRENT_PROCESS_ID = c.controlling_manager
and    c.request_id = 1427025;
Returned Nothing.
I thought that for a concurrent program when no specific manager is defined, Standard Manager is the default. Is my understanding wrong ?? Have anyone of you faced this issue? How did you fix it ?
I did check the profile - Concurrent: Conflict Domain for the responsibility and it is blank.
Appreciate any help.
Thanks
Cherrish Vaidiyan

Was this working before? If yes, any changes been done recently?
Your understanding is correct, unless this concurrent program is excluded from being processed by standard manager.
If the request was not processed then the no rows output is an expected behavior -- (Doc ID 344011.1)
Have you tried the solution in (Doc ID 1303315.1)?
Thanks,
Hussein

Error during deployment of Message Driven Bean

Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          I am getting some error (or perhaps warning) during deployment of Message
          Driven Bean. Any one seen this before?
          This error only comes on a machine with Dual Network card.
          Thanks.
          ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
          <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
          enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
          Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
          is of a non-final version of the appropriate specification. It is subject to
          change in future releases once the specification becomes finalized. This may
          cause application code developed for BEA WebLogic Server 6.1 that uses the
          new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          supported in future releases of BEA WebLogic Server.>
          ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          container will automatically attempt to re-establish the connection with the
          JMS server. This warning may occur during WebLogic Cluster start-up if the
          JMS destination is located on another server. When the JMS server connection
          is re-established, the Message-Driven EJB will again receive JMS messages.
          The Error was:
          Unable to create a JNDI InitialContext to lookup the JMS destination. The
          error was:
          javax.naming.CommunicationException. Root exception is
          java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          nested exception is:
          java.net.ConnectException: Connection refused: connect; No available router
          to destination
          at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:307)
          at
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          textFactoryDelegate.java:211)
          at
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          ory.java:149)
          at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          at javax.naming.InitialContext.init(InitialContext.java:217)
          at javax.naming.InitialContext.<init>(InitialContext.java:193)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          rivenBeanInfoImpl.java:641)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          nPoller.java:474)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          .java:418)
          at
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          nectionPoller.java:286)
          at
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          foImpl.java:511)
          at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          at weblogic.j2ee.Application.addComponent(Application.java:170)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          arget.java:360)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          Target.java:285)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          eploymentTarget.java:239)
          at
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          entTarget.java:199)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy34.updateDeployments(Unknown Source)
          at
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          ServerMBean_CachingStub.java:2977)
          at
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          icationManager.java:372)
          at
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          r.java:160)
          at java.lang.reflect.Method.invoke(Native Method)
          at
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          .java:636)
          at
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          21)
          at
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          nImpl.java:360)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          at $Proxy49.start(Unknown Source)
          at
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          ApplicationManagerMBean_CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          at weblogic.management.Admin.finish(Admin.java:644)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          at weblogic.Server.main(Server.java:35)
          >
          ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          <system> <> <010009> <EJB Deployed EJB with JNDI name
          ASYNCMessageDrivenBean.>


Hi Tom
          Yes we do have an URL provided in the descriptor. It's
          t3://jms.server.net:7001.
          and the jms.server.net is resolved via a hosts file in Win2K
          eg,
          192.168.100.200 jms.server.net
          You are right in saying that the loopback in a dual-net card is a problem.
          But our solution
          above solves the issue as long as your host file does not use 127.0.0.1 as
          the IP.
          We need the URL b/c depending on our client's deployment , the JMS Server
          may be remote or may be local.
          "Tom Barnes" <[email protected]> wrote in message
          news:[email protected]...
          > Hi x,
          >
          > Something to do with the loopback and dual-network cards is
          > messin' with WLS' mind. I do not know what the problem is,
          > but I can guess:
          >
          > You have specified an URL in the MDB descriptor when there
          > is no need for one. If t3://127.0.0.1:7001 is in the same
          > cluster the MDB is running in (I suspect this URL is
          > actually the same WL server), then don't specify the URL.
          > This URL is only useful for connecting an MDB to a JMS
          > server that is outside local server and outside the cluster.
          > The URL may be working on single-network card systems
          > as perhaps then WL has enough info to guess that you
          > actually mean the local WL server, and simply converts
          > the context to a local context.
          >
          > Note that the URL option in the MDB descriptor is actually
          > a WebLogic extension of J2EE.
          >
          > Tom
          >
          >
          >
          > x wrote:
          > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
          > >
          > > I am getting some error (or perhaps warning) during deployment of
          Message
          > > Driven Bean. Any one seen this before?
          > > This error only comes on a machine with Dual Network card.
          > >
          > > Thanks.
          > >
          > >
          > >
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
          > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
          features
          > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
          1.2,
          > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
          6.1
          > > is of a non-final version of the appropriate specification. It is
          subject to
          > > change in future releases once the specification becomes finalized. This
          may
          > > cause application code developed for BEA WebLogic Server 6.1 that uses
          the
          > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
          > > supported in future releases of BEA WebLogic Server.>
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
          <main>
          > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
          > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
          > > container will automatically attempt to re-establish the connection with
          the
          > > JMS server. This warning may occur during WebLogic Cluster start-up if
          the
          > > JMS destination is located on another server. When the JMS server
          connection
          > > is re-established, the Message-Driven EJB will again receive JMS
          messages.
          > > The Error was:
          > > Unable to create a JNDI InitialContext to lookup the JMS destination.
          The
          > > error was:
          > > javax.naming.CommunicationException. Root exception is
          > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
          > > nested exception is:
          > > java.net.ConnectException: Connection refused: connect; No available
          router
          > > to destination
          > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:307)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:211)
          > > at
          > >
          weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          > > ory.java:149)
          > > at
          javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
          > > at
          javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
          > > at javax.naming.InitialContext.init(InitialContext.java:217)
          > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
          > > rivenBeanInfoImpl.java:641)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
          > > nPoller.java:474)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
          > > .java:418)
          > > at
          > >
          weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
          > > nectionPoller.java:286)
          > > at
          > >
          weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
          > > foImpl.java:511)
          > > at
          weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
          > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
          > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
          > > at weblogic.j2ee.Application.addComponent(Application.java:170)
          > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
          > > arget.java:360)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
          > > Target.java:285)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
          > > eploymentTarget.java:239)
          > > at
          > >
          weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
          > > entTarget.java:199)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy34.updateDeployments(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
          > > ServerMBean_CachingStub.java:2977)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
          > > icationManager.java:372)
          > > at
          > >
          weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
          > > r.java:160)
          > > at java.lang.reflect.Method.invoke(Native Method)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
          > > .java:636)
          > > at
          > >
          weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
          > > 21)
          > > at
          > >
          weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
          > > nImpl.java:360)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          > > at
          com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > > at $Proxy49.start(Unknown Source)
          > > at
          > >
          weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
          > > ApplicationManagerMBean_CachingStub.java:480)
          > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
          > > at weblogic.management.Admin.finish(Admin.java:644)
          > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
          > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
          > > at weblogic.Server.main(Server.java:35)
          > >
          > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
          > > <system> <> <010009> <EJB Deployed EJB with JNDI name
          > > ASYNCMessageDrivenBean.>
          > >
          > >
          >

Error during proxy processing Message E SG 105 cannot be processed in plugi

Similar Messages

Maybe you are looking for