Fusion Weaver 1.1 | Products | Forum

Please consider registering
guest

Log In Register

Register | Lost password?
Advanced Search:

— Forum Scope —



— Match —



— Forum Options —




Wildcard usage:
*  matches any number of characters    %  matches exactly one character

Minimum search word length is 4 characters - maximum search word length is 84 characters

Topic RSS
Fusion Weaver 1.1
December 20, 2011
9:48 am
blh
Luxembourg
New Member
Forum Posts: 1
Member Since:
September 12, 2011
Offline

Hello, 

 

I am having the following error any time I try to upload any structure to the application.

 

NetConnection.Call.Failed:HTTP:Failed: url: “http://localhost:8082/FusionWeaver/messagebroker/amf”

 

Thanks for any clue.

 

The version of the app is the 1.1.

 

Regards,

 

Borja.

December 20, 2011
3:28 pm
Phil
Admin
Forum Posts: 5
Member Since:
March 23, 2011
Offline

Hi,

I'm sorry you're having trouble with Fusion Weaver but we'll try and solve this for you.

The error message you are seeing is a bit cryptic but it is stating that the Weaver cannot communicate to its own internal server. It uses port 8082, which hopefully is a port that isn't being used by your system. In some cases it is, so what we need to do is determine if that port is being used or not.

First, please can you stop the Weaver. Then open a Command Prompt and run the command:
    netstat -aon | findstr 8082

If anything is returned, it shows the port is in use. An example from my machine when the Fusion Weaver is running returns:
  TCP    ** you don’t have permission to see this link **              LISTENING       4912

This indicates that port 8082 is in use and is being used by process # 4912.

To find out what process 4912 actually is we can run the following command from the Command Prompt:
tasklist | findstr 4912

And on my machine (which is running Fusion Weaver) I see the following:
javaw.exe                     4912 Console                    1     64,292 K

The key item in this returned response is the first column. This shows a Java process is running. Unfortunately this doesn't explain which one, but these steps could be useful in determining what is stopping the Weaver from running. You can stop the application that is using the port and then try restarting the Weaver. Use the Windows Task Manager to identify the application with the same process number (in my case 4912) and terminate it.

Regards,

Phil

Powered by WishList Member - Membership Site Software