Home.... | log in.... | Pub my question! | Sign-up....
Java-index >> Archived Forums >> Socket Programming

about LoanProcessing

hai,

I implemented LoanProcessing (it is the Example of netbeans ide) .All are sucessful but In composite application it gives the error like

An activated endpoint already has the same SOAP Address location : http://localhost:18181/LoanRequestor1Service/LoanRequestor1Port

Failed to deploy: java.lang.Exception: An activated endpoint already has the same SOAP Address location : http://localhost:18181/LoanRequestor1Service/LoanRequestor1Port

javax.jbi.JBIException: java.lang.Exception: An activated endpoint already has the same SOAP Address location : http://localhost:18181/LoanRequestor1Service/LoanRequestor1Port

at com.sun.jbi.httpsoapbc.ServiceUnitImpl.createEndpoints(ServiceUnitImpl.java:409)

at com.sun.jbi.httpsoapbc.ServiceUnitImpl.deploy(ServiceUnitImpl.java:162)

at com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer.deploy(HttpSoapBindingDeployer.java:144)

at com.sun.jbi.framework.ServiceUnitOperation.process(ServiceUnitOperation.java:145)

at com.sun.jbi.framework.Operation.run(Operation.java:86)

at java.lang.Thread.run(Thread.java:595)

Caused by: java.lang.Exception: An activated endpoint already has the same SOAP Address location : http://localhost:18181/LoanRequestor1Service/LoanRequestor1Port

at com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle.endpointDeployed(HttpSoapBindingLifeCycle.java:285)

at com.sun.jbi.httpsoapbc.ServiceUnitImpl.createEndpoints(ServiceUnitImpl.java:386)

... 5 more

javax.jbi.messaging.MessagingException: Service connection already exists for endpoint {http://j2ee.netbeans.org/wsdl/LoanRequestor1}LoanRequestor1Service LoanRequestor1Port

at com.sun.jbi.messaging.EndpointRegistry.addEndpointConnection(EndpointRegistry.java:380)

at com.sun.jbi.management.system.DeploymentService.activateConnections(DeploymentService.java:2477)

at com.sun.jbi.management.system.DeploymentService.start(DeploymentService.java:1719)

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)

whenever i deployed the composite application

if you the answer send the reply as early as possible

Thanks

radhi.

[2427 byte] By [bondada.radhikaa] at [2007-11-26 12:22:18]
«« Is there a way to delete a directory with files in it?
»» Migrate NMS 4.15 to JMS 6
# 1

Radhi,

In this version of the HTTP BC, we had very explicit checking of endpoints. An endpoint is represented by a service/port combination. If you had already deployed an endpoint that has the same URL, then the HTTP BC will throw an error.

Having said that, it turns out that there were cases where this checking was too strict. There was also a bug where if the Service Assembly didn't get deployed completely, the state within the HTTP BC wasn't cleaned up. Both these issues have actually already been fixed.

To get around this problem, try the following:

1. Remove any Service Assembly you might have deployed or half-deployed and restart the app server. This will ensure that the HTTP BC is in a clean state. Try to deploy your Service Assembly at that point.

2. If you still can't deploy your Service Assembly, then somewhere in your project, you've defined two ednpoints with the exact same SOAP Address. Review your project and make sure that you don't have duplicate WSDLs that might have duplicate endpoints.

Let me know if that works!

Alex

amfunga at 2007-7-7 15:15:17 > top of Java-index,Archived Forums,Socket Programming...
# 2
Did you get this issue resolved?
itsvamsia at 2007-7-7 15:15:17 > top of Java-index,Archived Forums,Socket Programming...
Archived Forums
Socket Programming

Archived Forums New Topic

Archived Forums Hot Topic

Archived Forums

All Classified