Tomcat cannot be launched

yamileliassoto · 5 April 2016 23:08

I just installed Bonita BPM 7.2.2 in a Windows 10 (x64) computer and it went without issues. Then I tried to run the expense report example and I got the following error:

'Starting Tomcat v7.0 Server at localhost has encountered a problem.'
Server Tomcat v7.0 Server al localhost failed to start.

And then the next window appeared with another message:

Tomcat cannot be launched:
the port might be aready used by another application. Possible causes are that another Studio or another Tomcat is already running.

That makes sense to me, maybe I forgot to stop Tomcat v8.0 server, but when I go to cmd and I type netstat -a I have the following connections:

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:80             pubads:0               LISTENING
  TCP    0.0.0.0:135            pubads:0               LISTENING
  TCP    0.0.0.0:445            pubads:0               LISTENING
  TCP    0.0.0.0:5357           pubads:0               LISTENING
  TCP    0.0.0.0:49664          pubads:0               LISTENING
  TCP    0.0.0.0:49665          pubads:0               LISTENING
  TCP    0.0.0.0:49666          pubads:0               LISTENING
  TCP    0.0.0.0:49667          pubads:0               LISTENING
  TCP    0.0.0.0:49668          pubads:0               LISTENING
  TCP    0.0.0.0:49670          pubads:0               LISTENING
  TCP    0.0.0.0:50311          pubads:0               LISTENING
  TCP    0.0.0.0:56928          pubads:0               LISTENING
  TCP    0.0.0.0:57621          pubads:0               LISTENING
  TCP    10.151.254.247:139     pubads:0               LISTENING
  TCP    10.151.254.247:55990   dfw06s41-in-f4:http    CLOSE_WAIT
  TCP    10.151.254.247:55998   msnbot-65-52-108-216:https  ESTABLISHED
  TCP    10.151.254.247:56368   ec2-23-23-102-127:https  CLOSE_WAIT
  TCP    10.151.254.247:56369   ec2-23-23-102-127:https  CLOSE_WAIT
  TCP    10.151.254.247:56370   a23-64-171-27:http     CLOSE_WAIT
  TCP    10.151.254.247:56372   ec2-23-23-102-127:https  CLOSE_WAIT
  TCP    10.151.254.247:56373   a184-24-98-96:http     CLOSE_WAIT
  TCP    10.151.254.247:56374   ec2-54-243-93-168:https  CLOSE_WAIT
  TCP    10.151.254.247:58863   2d:https               ESTABLISHED
  TCP    10.151.254.247:58864   dfw06s46-in-f164:http  CLOSE_WAIT
  TCP    10.151.254.247:58881   dfw06s46-in-f10:https  ESTABLISHED
  TCP    10.151.254.247:59129   dfw06s47-in-f205:https  CLOSE_WAIT
  TCP    10.151.254.247:59260   sjc1-accesspoint-a110:4070  ESTABLISHED
  TCP    10.151.254.247:59305   ec2-54-229-15-211:https  ESTABLISHED
  TCP    10.151.254.247:59306   ok-in-f188:5228        ESTABLISHED
  TCP    10.151.254.247:59308   bam-5:https            ESTABLISHED
  TCP    10.151.254.247:59365   a184-24-106-90:https   ESTABLISHED
  TCP    10.151.254.247:59377   pubads:0               LISTENING
  TCP    10.151.254.247:59403   a23-212-53-125:http    TIME_WAIT
  TCP    10.151.254.247:59436   live:https             ESTABLISHED
  TCP    10.151.254.247:59455   dfw06s48-in-f14:https  ESTABLISHED
  TCP    10.151.254.247:59484   ec2-52-11-82-49:https  TIME_WAIT
  TCP    10.151.254.247:59485   dfw06s46-in-f174:https  ESTABLISHED
  TCP    10.151.254.247:59489   server-54-230-6-144:https  ESTABLISHED
  TCP    10.151.254.247:59492   ec2-176-34-117-204:https  TIME_WAIT
  TCP    10.151.254.247:59494   ec2-54-86-223-162:https  ESTABLISHED
  TCP    10.151.254.247:59495   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59496   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59497   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59498   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59499   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59500   a23-33-20-216:https    TIME_WAIT
  TCP    10.151.254.247:59501   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59502   ec2-54-86-223-162:https  ESTABLISHED
  TCP    10.151.254.247:59504   23.227.10.138:https    ESTABLISHED
  TCP    10.151.254.247:59505   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59506   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59507   a23-33-20-216:https    ESTABLISHED
  TCP    10.151.254.247:59509   dfw25s12-in-f14:https  ESTABLISHED
  TCP    10.151.254.247:59510   dfw25s08-in-f136:https  ESTABLISHED
  TCP    10.151.254.247:59511   199.27.76.175:https    ESTABLISHED
  TCP    10.151.254.247:59512   23.235.46.175:https    ESTABLISHED
  TCP    10.151.254.247:59513   dfw25s08-in-f136:https  CLOSE_WAIT
  TCP    10.151.254.247:59514   199.27.76.175:https    ESTABLISHED
  TCP    10.151.254.247:59515   23.235.46.175:https    ESTABLISHED
  TCP    10.151.254.247:59516   ou-in-f157:https       ESTABLISHED
  TCP    10.151.254.247:59517   23.227.10.139:https    ESTABLISHED
  TCP    10.151.254.247:59518   23.227.10.139:https    ESTABLISHED
  TCP    10.151.254.247:59519   23.227.10.139:https    ESTABLISHED
  TCP    10.151.254.247:59520   dfw06s40-in-f14:https  ESTABLISHED
  TCP    10.151.254.247:59521   23.227.10.139:https    ESTABLISHED
  TCP    10.151.254.247:59522   dfw06s40-in-f14:https  CLOSE_WAIT
  TCP    10.151.254.247:59523   dfw06s40-in-f14:https  ESTABLISHED
  TCP    10.151.254.247:59524   ec2-54-243-103-188:https  TIME_WAIT
  TCP    10.151.254.247:59525   ec2-54-243-103-188:https  TIME_WAIT
  TCP    127.0.0.1:4370         pubads:0               LISTENING
  TCP    127.0.0.1:4371         pubads:0               LISTENING
  TCP    127.0.0.1:4380         pubads:0               LISTENING
  TCP    127.0.0.1:4381         pubads:0               LISTENING
  TCP    127.0.0.1:6543         pubads:0               LISTENING
  TCP    127.0.0.1:6969         pubads:0               LISTENING
  TCP    127.0.0.1:56929        G50-30:56930           ESTABLISHED
  TCP    127.0.0.1:56930        G50-30:56929           ESTABLISHED
  TCP    127.0.0.1:57193        G50-30:57194           TIME_WAIT
  TCP    127.0.0.1:57195        G50-30:57196           TIME_WAIT
  TCP    [::]:80                G50-30:0               LISTENING
  TCP    [::]:135               G50-30:0               LISTENING
  TCP    [::]:445               G50-30:0               LISTENING
  TCP    [::]:5357              G50-30:0               LISTENING
  TCP    [::]:49664             G50-30:0               LISTENING
  TCP    [::]:49665             G50-30:0               LISTENING
  TCP    [::]:49666             G50-30:0               LISTENING
  TCP    [::]:49667             G50-30:0               LISTENING
  TCP    [::]:49668             G50-30:0               LISTENING
  TCP    [::]:49670             G50-30:0               LISTENING
  TCP    [::]:50311             G50-30:0               LISTENING
  TCP    [::]:56928             G50-30:0               LISTENING
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:3544           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:5353           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:51787          *:*
  UDP    0.0.0.0:57152          *:*
  UDP    0.0.0.0:57621          *:*
  UDP    0.0.0.0:58125          *:*
  UDP    10.151.254.247:137     *:*
  UDP    10.151.254.247:138     *:*
  UDP    10.151.254.247:1900    *:*
  UDP    10.151.254.247:53247   *:*
  UDP    10.151.254.247:55749   *:*
  UDP    10.151.254.247:59377   *:*
  UDP    10.151.254.247:59813   *:*
  UDP    10.151.254.247:61552   *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:55750        *:*
  UDP    [::]:500               *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:4500              *:*
  UDP    [::]:5353              *:*
  UDP    [::]:5355              *:*
  UDP    [::]:58126             *:*
  UDP    [::1]:1900             *:*
  UDP    [::1]:55748            *:*
  UDP    [fe80::207c:532b:4440:efd9%3]:546  *:*
  UDP    [fe80::bdb4:3dd0:80a7:3e81%4]:1900  *:*
  UDP    [fe80::bdb4:3dd0:80a7:3e81%4]:55747  *:*

I don’t see tomcat running anywhere, and when I check it on my local services it isn’t running. Anyone have an idea?

system · 7 April 2016 09:02

Are you running Bonita BPM Studio or a Bonita BPM Tomcat bundle?

Can you try to close the Studio / stop Tomcat server and run netstat -a -n -p tcp and share the output in a file (forum seems to mess up formating)?
If you can do the same after restarting Studio / Tomcat bundle.
Also if you can share the Studio / Engine logs files that would be nice.

Thanks

yamileliassoto · 9 April 2016 00:41

I tried what you said antoine and it only shows this:

Proto Local Address Foreign Address State

is this what you asked for? I didn’t put it in a file because it won’t have any sense, but here is the other output.

Where can I find the Engine logs? I’m new in Bonita BPM and I’ don’t know where to find them.

system · 11 April 2016 07:58

You can find log files in Bonita Studio directory under workspace\.metadata folder.
You should find two files: tomcat.log and .log.

Note that .metadata and .logfile are hidden by default you might need to change file explorer settings to view them.

You can also get logs files from Studio “Help” menu.

yamileliassoto · 11 April 2016 17:48

Here is the tomcat.log and here is the .log file.

system · 12 April 2016 13:43

Can you try to:

Close Bonita BPM Studio
Delete tomcat.log file
Start Bonita BPM Studio
Share the full content of tomcat.log file

Thanks

yamileliassoto · 12 April 2016 14:12

Here is the tomcat.log output.

system · 12 April 2016 16:45

From the log file it seems that you have a mix of versions.

Tomcat log file reports version 6.4.0 (C:\BonitaBPMCommunity-6.4.0) whereas Studio log file report 7.2.2.

Can you get rid of version 6.4.0?

Topic		Replies	Views
Starting TomCat v7 server at localhost has encountered a problem Q&A	7	6	19 September 2015
BonitaBPMCommunity 6.4.2, Ubuntu 64bit: Tomcat not starting Q&A	2	1	24 February 2015
Problem starting tomcat after installing bonita BonitaBPMCommunity-6.1.2-Tomcat-6.0.37 on server Q&A	3	0	14 May 2014
On Mac，Bonita BPM Community failed to launch the tomcat server. Q&A	3	0	28 April 2015
Tomcat fails to start in a freshly installed OpenSuse Leap 42.1 Q&A	2	1	18 October 2016

Tomcat cannot be launched

Related topics