Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

JBoss ConfigurationManager problem

Avatar

20-05-2008

Hello,



I've install Adobe LiveCycle ES trial version with JBoss and everything seems to be good during installation.



But when I launch the ConfigurationManager and try to deploy EAR files, the process is stopped at 64% and i've got the error message witch say that the ports that JBoss need are already busy (8080)...

What can I do ?



Thank you for your help and sorry for my bad english 🙂



Marion.

Replies

Avatar

20-05-2008

For more details : it failed on Verifying ports required by service JBoss for Adobe LiveCycle ES V8.0 are available...

But even if I kill instance that using 8080 port, it doesn't change anything...

😞

Avatar

20-05-2008

Strange. You should contact Adobe support. I don't know what the cause may be. It is easy to change the jboss port number, but I am not sure how you can make LC use another port.

Avatar

Avatar
Boost 5
Level 3
JohnFait
Level 3

Likes

6 likes

Total Posts

67 posts

Correct Reply

12 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Level 3
JohnFait
Level 3

Likes

6 likes

Total Posts

67 posts

Correct Reply

12 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
JohnFait
Level 3

14-07-2008

The list port usage to determine what is using the port you can try

>netstat -ao



Does the issue persist after a reboot?

Avatar

Avatar
Boost 5
Level 3
JohnFait
Level 3

Likes

6 likes

Total Posts

67 posts

Correct Reply

12 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Level 3
JohnFait
Level 3

Likes

6 likes

Total Posts

67 posts

Correct Reply

12 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
JohnFait
Level 3

14-07-2008

To list port usage to determine what is using the port you can try

>netstat -ao



Does the issue persist after a reboot?