Cancel
Showing results for 
Search instead for 
Did you mean: 

Error while loging the thin client

Solution Partner Valued Contributor Solution Partner Valued Contributor
Solution Partner Valued Contributor

Hello all,

 

I installed and configurated Jboss then when I wanted to login I get this error:

 

logtc.PNG

 

This is what I find in server.log file:

 

 

11:00:10,242 INFO  [stdout] (http--127.0.0.1-8080-1) INFO  - 127.0.0.1.66648.Anonymous.00001 - 2018/11/27-10:00:10,242 UTC - USER-PC - Global pool config published.

11:00:10,880 INFO  [stdout] (http--127.0.0.1-8080-1) WARN  - 127.0.0.1.66648.Anonymous.00001 - 2018/11/27-10:00:10,880 UTC - USER-PC - Global pool configuration INVOCATION_MAX_CONNECTIONS not found.  Using 1000

11:00:10,924 INFO  [stdout] (http--127.0.0.1-8080-1) ERROR - 127.0.0.1.66648.Anonymous.00001 - 2018/11/27-10:00:10,924 UTC - USER-PC - Cannot find any server pools.  Please check TreeCache configuration.
11:00:10,925 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Cluster Name=Cluster
11:00:10,926 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Mode=TCP
11:00:10,926 INFO  [stdout] (http--127.0.0.1-8080-1) 	Local Service Port=17810
11:00:10,927 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Socket Connect Timeout=2000
11:00:10,927 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Peers=localhost[17800]
11:00:10,927 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Port Range=1
11:00:10,928 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Connection Timeout=30000
11:00:10,928 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Merge Min=5000
11:00:10,929 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Merge Max=10000
11:00:10,929 INFO  [stdout] (http--127.0.0.1-8080-1) 	TreeCache Join Timeout=60000
11:00:10,930 INFO  [stdout] (http--127.0.0.1-8080-1) :com.teamcenter.jeti.serverassigner.ServerAssigner.assignNewServer(Unknown Source) com.teamcenter.jeti.serverassigner.ServerAssigner 

11:00:10,937 INFO  [stdout] (http--127.0.0.1-8080-1) WARN  - 127.0.0.1.66648.Anonymous.00001 - 2018/11/27-10:00:10,937 UTC - USER-PC - Aucun pool de serveur n'est enregistré dans le cluster TreeCache. Vérifiez qu'un Gestionnaire de serveur est en cours d'exécution  et que sa configuration TreeCache correspond à la configuration pour le serveur d'application.

I hope you could help me,

Warm regards.

7 REPLIES 7

Re: Error while loging the thin client

Legend
Legend

Error message says, there is no server manager reachable.

Do you have a server manager running?

Is it running on the same host?

 

Re: Error while loging the thin client

Solution Partner Valued Contributor Solution Partner Valued Contributor
Solution Partner Valued Contributor

Thank you @Roman65

Yes I have, but last week it was infected and we changed its Motherboard.

can this impact  license recognition???

Re: Error while loging the thin client

Legend
Legend

License is served by the license manager, running?

 

what are the parameters for the Treecache in your pool_manager?

 

Re: Error while loging the thin client

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
The original problem is that the JBoss configuration for TreeCache Peers is wrong. @Roman65 correctly asked you if Pool Manager is installed on the same machine as JBoss. The reason he asked is because you have specified localhost[17800]. If they are not on the same machine then you need to change the value for the actual server name that is running Pool Manager. Both Pool Manager (cut down version of JBoss) and JBoss share a TreeCache which keeps track of sessions so that the web server knows where to route the session calls and info.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Error while loging the thin client

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
Your response about changing the motherboard...
If this same server is running the license service and has an integrated NIC then it will certainly affect licensing. You can review the FlexLM log to validate if the license service started correctly or has issues. If startup failed then you'll likely need to find your CID again and submit a server change form to your CSR and wait for them to generate a new license from the new CID. You can work with your vendor or GTAC to get this escalated.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Error while loging the thin client

Legend
Legend

@RandyEllsworth

Your detailed explanations are always much better than mine

Re: Error while loging the thin client

Solution Partner Valued Contributor Solution Partner Valued Contributor
Solution Partner Valued Contributor

Thank you both

@Roman65 by the way the license manager is runing on the server not on the same host where I'm going to deploy the web tier application