Hi ,

I have created the MWS server under the server in the deployer. I have given the public IP and port . But I am not able to connect to the server using the deployer . ButI am able to access the server through the browser . What could be the reason ?

Hi Sreejith,

are there any error messages shown in Deployer UI, in the server.log of the IS hosting deployer and/or MWS full.log related to this?

Are IS/Deployer and MWS running on the same box?
Are there firewall and/or network issues which might hinder the IS connecting to the MWS?

Regards,
Holger

Hi ,

This is the exception in the IS Server .

com.wm.app.b2b.server.ServiceException: [DEP.0006.0010] An error has occurred while invoking the service wm.deployer.NewPlugin.RPCEncoded.DeployerPluginRPCEncoded_.connectors:DeployerPlugin_Ping remotely on the system MWSLivetest.
The service has failed with the following exception : Connection timed out: connect
.
Refer the Integration Server logs for more details.
at com.wm.deployer.mgmt.connection.Connection.invokeISService(Connection.java:422)
at com.wm.deployer.mgmt.connection.Connection.invokeService(Connection.java:265)
at wm.deployer.gui.UIPlugin.pingPluginServer(UIPlugin.java:1365)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:443)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:640)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:49)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:289)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:368)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:544)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:383)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:244)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:108)
at com.wm.app.b2b.server.ns.Namespace.invoke(Namespace.java:612)
at com.wm.util.template.Reporter.invoke(Reporter.java:919)
at com.wm.util.template.InvokeToken.eval(InvokeToken.java:70) …

jvm 1 | at java.lang.Thread.run(Thread.java:724)
jvm 1 | com.wm.app.b2b.server.ServiceException: [DEP.0006.0010] An error has occurred while invoking the service wm.
deployer.NewPlugin.RPCEncoded.DeployerPluginRPCEncoded_.connectors:DeployerPlugin_GetDependencies remotely on the system
MWSLivetest.
jvm 1 | The service has failed with the following exception : Connection timed out: connect
jvm 1 | .
jvm 1 | Refer the Integration Server logs for more details.
jvm 1 | at com.wm.deployer.mgmt.connection.Connection.invokeISService(Connection.java:422)
jvm 1 | at com.wm.deployer.mgmt.connection.Connection.invokeService(Connection.java:265)
jvm 1 | at wm.deployer.gui.PluginUtils.getPluginReferences(PluginUtils.java:773)
jvm 1 | at wm.deployer.gui.UIDependency.getAndProcessSourceSystemDependencies(UIDependency.java:1190)
jvm 1 | at wm.deployer.gui.UIDependency.getAndProcessBundleDependencies(UIDependency.java:468)
jvm 1 | at wm.deployer.gui.UIDependency.getUnresolvedBundleDependencies(UIDependency.java:170)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
jvm 1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
jvm 1 | at java.lang.reflect.Method.invoke(Method.java:606)
jvm 1 | at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:443)
jvm 1 | at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:640)
jvm 1 | at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
jvm 1 | at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:49)
jvm 1 | at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
jvm 1 | at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
jvm 1 | at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
jvm 1 | at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:289)
jvm 1 | at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
jvm 1 | at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:368)
jvm 1 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:544)
jvm 1 | at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:383)
jvm 1 | at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:244)
jvm 1 | at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:93)
jvm 1 | at com.wm.app.b2b.server.Service.doInvoke(Service.java:676)
jvm 1 | at com.wm.app.b2b.server.Service.doInvoke(Service.java:564)
jvm 1 | at com.wm.deployer.project.Bundle.hasUnresolvedDependencies(Bundle.java:443)
jvm 1 | at wm.deployer.gui.UIProject.getProjectBundles(UIProject.java:863)
jvm 1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) …

Both the IS and MWS is running in the same box .

There are no network issues .

Hi Sreejith,

are you using localhost as the destionation address?

This is not really recommended.

Please use the real name of the box for the destination address.

Regards,
Holger

Hi ,

We are using the IP (public ip of the box) as the hostname .

We are able to connect to the IP : port through the browser , but the IS is not able to connect to it , because of which we are not able to make proper deployer build from the same .

Thanks .

Hi Sreejith,

what is the result when testing the server in the deployer?

If there is an error message, post it here.
Most likely you will have a network issue here.

If not, the error is somewhere else.

Regards,
Holger

Hi ,

This is the error that is coming on trying to connect to the MWS server through the deployer

Error connecting to server: [DEP.0006.0024] Plugin System Name: MWSLivetest, Plugin Type: MWS, Deployer tried to connect to the plugin-server with specified connection details but could not connect. Make sure that you are trying to connect to the correct plug-in server and that the plug-in server is up and running.

This is when we give the public ip of the box and its port . The public ip is used for our clients to access this MWS , and is accessible .

Well when we try to connect using the localhost or the local ip of the box , it connects through the deployer . The issue happens when we create a build using the public ip , and sent to the client , they will not be able to continue if the deployer cannot connect to the MWS .

Thanks .
server.log (11 KB)

Sreejith,

Perhaps you can explain your environment a little better to us because it’s a little confusing. You say you have IS and MWS running on the same box, and I’m assuming this IS is the same one that has Deployer installed, right?

That being the case, why do you want to use the public IP of the box? The public IP is typically reserved for external clients. The IS on that same box is clearly not an external client. Either use the local IP, or better yet, don’t use an IP at all. Use the host name and it should get resolved to the appropriate IP.

When it comes to testing the connection from a browser, are you launching the browser from the server itself? If not, it doesn’t necessarily mean a whole lot.

The last thing that is a bit confusing is your statement “The issue happens when we create a build using the public ip , and sent to the client , they will not be able to continue if the deployer cannot connect to the MWS.”

Are you creating a build and sending it to your client so they can import it into their Deployer? If so, their Deployer will NOT have to connect to the source again. That’s the point of creating and exporting a build.

Hope this helps,
Percio

Hi ,

We have the MWS and IS installed in the same box which is a test machine upgraded to MWS 9.5 for our clients to access it from external network . Because of which we have the public IP and port . They are creating the same MWS instance at their side corresponding to this box.
I created the MWS source server in the deployer with the public IP for the same reason to take build and sent to them .

Now the issue is that while taking the build , it gives this exception . [DEP.0006.0024] Plugin System Name: MWSLivetest, Plugin Type: MWS, Deployer tried to connect to the plugin-server with specified connection details but could not connect. Make sure that you are trying to connect to the correct plug-in server and that the plug-in server is up and running.)

But the server is up and running

Thanks,

Let me simplify: use the host name or local IP to create the build.

Percio

Hi ,

Thanks for your comment .

But I have one more doubt at this point. After creating the build in our environment , we export the build and sent that to the client , for them to import the same build to their environment and continue . In that case , they will be selecting the source server , for which they have to give our server’s IP(which is public as the client is in external network). In that case , will this create the same error as I described previously ?.

Thanks,

Sreejith,

Like I mentioned above, “their Deployer will NOT have to connect to the source again.” That is one of main reasons behind the build export/import feature of Deployer. Once you have a build, you no longer need to connect to the source.

Percio

Hi Sreejith,

your external partner does not require to access your source servers.
All the neccessary artifiactes are inside the build.

They will only have to import the build, create maps for the sets contained in the build, create deployment candidates for the build-map combinations, simulate them, take checkpoints and deploy them.

Regards,
Holger

Thanks Holger and Percio for your valuable comments .