Port out of range:65536 exepction by adding a stream node
This is my setup:
App Server: Tomcat 8.5
OS: CentOS 7 running in a docker container.
Pega version: Pega Infitniy 8.1
Unfortunately no backgroud agents ("Queue processors) are running. According to the arning message in the queue processor lading page "Stream service is down. The values displayed on this page may be inaccurate." the stream node is missing.
So I wanted to add a stream node, but I'm getting always the following error.
java.lang.IllegalArgumentException: port out of range:65536
at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143)
at java.net.InetSocketAddress. (InetSocketAddress.java:224)
at com.pega.dsm.dnode.impl.server.web.StreamDataSetWebService.run(StreamDataSetWebService.java:94)
***Edited by Moderator Marissa to update platform capability tags****
Accepted Solution
USU GmbH
DE
The problme got solved.
As my pega instance is running on a docker container I assumed, that the "identification/cluster/public/address" should be set in the prconfic to the host which I thought is the host IP on wich docker is running. But this was a wrong assumtion.
If you are running pega in a docker container, this setting "identification/cluster/public/address" needs to be set to the IP of the docker container on wich the pega instance is running.
Changes on /ect/hosts file and other settings were not needed anymore after this correction.
Pegasystems Inc.
IN
Hi,
Can you check below SA article, might be same issue else would need more detail on error stack
https://community.pega.com/support/support-articles/gridgain-error-during-vbd-startup
Thank You
USU GmbH
DE
Thanks for the fast response, but in fact I already tried it. I found two SAs about this issue:
https://community.pega.com/support/support-articles/vbd-service-cannot-be-accessed
and
https://community.pega.com/support/support-articles/gridgain-error-during-vbd-startup
But it didn't work for me.
I might have wrongly setup the ipaddress in /etc/hosts
here some insights about my Env setup:
Host on which Docker is running (CentOS): Proprietary information hidden
Docker Container (CentOS) IP: Proprietary information hidden
For this steup my /etc/hosts file looks like:
Proprietary information hidden localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Proprietary information hidden pegadev
what do I wrong?
USU GmbH
DE
Here the whole stack trace:
Here the whole stack trace:
java.lang.IllegalArgumentException: port out of range:65536
at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143)
at java.net.InetSocketAddress. (InetSocketAddress.java:224)
at com.pega.dsm.dnode.impl.server.web.StreamDataSetWebService.run(StreamDataSetWebService.java:94)
at com.pega.dsm.dnode.api.server.StreamServerService.startWebService(StreamServerService.java:451)
at com.pega.dsm.dnode.api.server.StreamServerService.access$600(StreamServerService.java:66)
at com.pega.dsm.dnode.api.server.StreamServerService$StreamServiceStartOperation$3.emit(StreamServerService.java:421)
at com.pega.dsm.dnode.impl.stream.DataObservableImpl$SafeDataSubscriber.subscribe(DataObservableImpl.java:338)
at com.pega.dsm.dnode.impl.stream.DataObservableImpl.subscribe(DataObservableImpl.java:40)
at com.pega.dsm.dnode.impl.stream.DataObservableImpl.await(DataObservableImpl.java:102)
at com.pega.dsm.dnode.impl.stream.DataObservableImpl.await(DataObservableImpl.java:91)
at com.pega.dsm.dnode.api.prpc.service.operation.StartOperation.doActualServerStart(StartOperation.java:175)
at com.pega.dsm.dnode.api.prpc.service.operation.StartOperation.access$400(StartOperation.java:22)
at com.pega.dsm.dnode.api.prpc.service.operation.StartOperation$3.execute(StartOperation.java:156)
at com.pega.dsm.dnode.util.OperationWithLock$LockingOperation.couldAcquireLock(OperationWithLock.java:133)
at com.pega.dsm.dnode.util.OperationWithLock$LockingOperation.performLockOperation(OperationWithLock.java:123)
at com.pega.dsm.dnode.util.OperationWithLock$LockingOperation.access$100(OperationWithLock.java:70)
at com.pega.dsm.dnode.util.OperationWithLock.doWithLock(OperationWithLock.java:67)
at com.pega.dsm.dnode.util.OperationWithLock.doWithLock(OperationWithLock.java:63)
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeWithLockInternal(ServiceHelper.java:212)
at com.pega.dsm.dnode.impl.prpc.service.ServiceHelper.executeWithLock(ServiceHelper.java:168)
at com.pega.dsm.dnode.api.prpc.service.operation.StartOperation.initializeServerMode(StartOperation.java:153)
at com.pega.dsm.dnode.api.prpc.service.operation.StartOperation.access$200(StartOperation.java:22)
at com.pega.dsm.dnode.api.prpc.service.operation.StartOperation$1.emit(StartOperation.java:83)
at com.pega.dsm.dnode.impl.stream.DataObservableImpl$SafeDataSubscriber.subscribe(DataObservableImpl.java:338)
at com.pega.dsm.dnode.impl.stream.DataObservableImpl.subscribe(DataObservableImpl.java:40)
at com.pega.dsm.dnode.impl.stream.DataObservableImpl.await(DataObservableImpl.java:102)
at com.pega.dsm.dnode.impl.stream.DataObservableImpl.await(DataObservableImpl.java:91)
at com.pega.dsm.dnode.api.prpc.service.ServiceManager.initialize(ServiceManager.java:463)
at com.pega.dsm.dnode.api.prpc.service.ServiceManager.initializeServiceAndRegisterPulse(ServiceManager.java:418)
at com.pega.dsm.dnode.api.prpc.service.ServiceManager.access$500(ServiceManager.java:77)
at com.pega.dsm.dnode.api.prpc.service.ServiceManager$7.run(ServiceManager.java:341)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at com.pega.dsm.dnode.util.PrpcRunnable$1.run(PrpcRunnable.java:44)
at com.pega.dsm.dnode.util.PrpcRunnable$1.run(PrpcRunnable.java:41)
at com.pega.dsm.dnode.util.PrpcRunnable.execute(PrpcRunnable.java:52)
at com.pega.dsm.dnode.impl.prpc.PrpcThreadFactory$PrpcThread.run(PrpcThreadFactory.java:109)
Pegasystems Inc.
IN
I don't see any specific issue here. You might consider opening a SR if you don't get any more help here as it might need more investigation and debugging.
Accepted Solution
USU GmbH
DE
The problme got solved.
As my pega instance is running on a docker container I assumed, that the "identification/cluster/public/address" should be set in the prconfic to the host which I thought is the host IP on wich docker is running. But this was a wrong assumtion.
If you are running pega in a docker container, this setting "identification/cluster/public/address" needs to be set to the IP of the docker container on wich the pega instance is running.
Changes on /ect/hosts file and other settings were not needed anymore after this correction.