WebSphere Portal Server - Could not create SOAP Connector to connect...

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Portal Server > October 2004 > Could not create SOAP Connector to connect...





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Could not create SOAP Connector to connect...
meian

2004-04-02, 10:36 am

I tried to install a portlet . wpsadmin is the user who install the portlet
and was added in the console user in WAS console. I got error messages said
"could not create SOAP connector to connect host localhost at port 8881".

Any clue would be appreciated.

Thanks


Rob

2004-04-02, 1:33 pm

meian wrote:
> I tried to install a portlet . wpsadmin is the user who install the portlet
> and was added in the console user in WAS console. I got error messages said
> "could not create SOAP connector to connect host localhost at port 8881".
>
> Any clue would be appreciated.
>
> Thanks
>
>


Make sure server1 us up and has the adminconsole application installed
and running. Also check the end points for your server, the SOAP
connector usually defaults to 8880 - if the port is different either
change it or change the value in wsadmin.properties.

if all else fails do a netstat -an and see if there are any ports
listening in the 888x range.
meian

2004-04-05, 3:33 pm

My server1 is up, but when I logged into the admin console, the left panel
is blank except a node name displayed. I didn't see any error message in
SystemOut.log. It all said server 1 open for e-business. in my
serverindex.xml file, the end points of SOAP connector for server1 is 8880
and portal is 8881. what's wrong with my admin console.

thanks.


"Rob" <robertb.nospam@axium.com> wrote in message
news:c4ka1b$5ilu$1@news.boulder.ibm.com...
> meian wrote:
portlet[color=darkred]
said[color=darkred]
8881".[color=darkred]
>
> Make sure server1 us up and has the adminconsole application installed
> and running. Also check the end points for your server, the SOAP
> connector usually defaults to 8880 - if the port is different either
> change it or change the value in wsadmin.properties.
>
> if all else fails do a netstat -an and see if there are any ports
> listening in the 888x range.



ibmdude

2004-10-11, 3:56 am

Hi,

the obvious part is: the soap connector can't connect to that port on that machine.

the possible problems:
1. port not currently listening
2. the hostname (machine) cannot be resolved.

i had the same problem and i put the fully qualified hostname on the host file so that it resolves to the ip address of the machine (without having to go to network dispatcher or dns server)

hope it helps

===================



quote:
Originally posted by meian
My server1 is up, but when I logged into the admin console, the left panel
is blank except a node name displayed. I didn't see any error message in
SystemOut.log. It all said server 1 open for e-business. in my
serverindex.xml file, the end points of SOAP connector for server1 is 8880
and portal is 8881. what's wrong with my admin console.

thanks.


"Rob" <robertb.nospam@axium.com> wrote in message
news:c4ka1b$5ilu$1@news.boulder.ibm.com...
> meian wrote:
portlet[color=darkred]
said[color=darkred]
8881".[color=darkred]
>
> Make sure server1 us up and has the adminconsole application installed
> and running. Also check the end points for your server, the SOAP
> connector usually defaults to 8880 - if the port is different either
> change it or change the value in wsadmin.properties.
>
> if all else fails do a netstat -an and see if there are any ports
> listening in the 888x range.

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com