Portal Jserv : fetcher dying...The portlet could not be contacted.

I have a TAR open, but with no luck till now. So here it goes:
Configuration: IAS 1.0.2.2 on HPUX11 32bit, oracle 8.1.7.2.5 on NT4 sp6
When trying to login to main portal myhost.mydomain:7777/pls/portal30 I get Error: The portlet could not be contacted.
The Jserv log has these entries:
[26/02/2002 10:33:02:785 GMT-05:00] page/UncaughtException in thread name=conten
t-fetcher10, starting a new fetcher after exception
java.lang.NoClassDefFoundError
at oracle.webdb.cache.CacheHTTPConnection.<init>(CacheHTTPConnection.jav
a:54)
at oracle.webdb.cache.CacheFactory.getHTTPConnection(CacheFactory.java:5
7)
at oracle.webdb.page.ContentFetcher.run(ContentFetcher.java:170)
The Apache log looks OK.
Anybody has any idea how to get it straight ???
If logging through SSO to "Mod_plsql Configuration Menu" as portal30, I get the mod_plsql configuration page working
Please help, as we are in the dark here (our local oracle support including).

Similar Messages

Pls/portal shows: Error: The portlet could not be contacted after SSL enab

The OCS /pls/portal page shows: Error: The portlet could not be contacted, I believe this happened after SSL enabling the system. Anyone out there seen this errof before?

FYI
This happens if you remove port 80 as a listening port webcache/em, etc. Oracle claims it needs port 80 for internal communication. For whatever reason the /pls/portal providers are registered in non-SSL. Not sure if Oracle will provide a fix or ?

Error: The portlet could not be contacted.

OS: Solaris
Database: 8.1.7
POrtal: 3.07
When a page is bookmarked and/or set as the default page the portlets do not load without hitting refresh.
I need the pages to load without this error since the pages are public. Does anyone know the work around?
Thanks,
Michael

Michael,
I posted a possible solution in this thread.
Rich

The portlet could not be contacted and other time-out errors: the cause!

Did you encounter these kind of errors? Even after upgrading to
version 3.0.9.8.1?
We have searched for many months for the cause of these problems
and finally found it. It's the user SYS ! When you analyze SYS's
objects (tables and indexes), Portal gets totally confused.
Especially after rebooting a server, retrieving the first page
can take five minutes or even more.
We have removed all statistics from SYS and the responstimes
have been increased dramatically. From minutes to just a few
seconds!
So, if you want to experience these problems, just analyze user
SYS. And if you want to get rid of these problems, drop SYS's
statistics.

hi,
Have a look at this discussion. It is the same problem what you face, provided your portal version is also 3.0.9.
Re: ocopy.exe utility in Oracle 9i
Thanks,
Sriram

Cannot access page groups via Navigator "portlet could not be contacted"

On the Portal Navigator's Page Groups tab, the error "The portlet could not be contacted." appears where the list of Page Groups should be.
This is happening for 2 users. I see it the error in 1 browser, but not in another (logged on in both browser as same user).
There are no errors in the Apache error log. There are errors in the OC4J_Portal application log:
07/01/26 14:32:05 portal: id=673911615591,2 ContentFetcher Unexpected Exception Request Failed:oracle.webdb.dispatcher.DispatcherException: I/O Error dispatching request name=content-fetcher0 label=dbPortlet url=http://portal.domain.com:7823/pls/portal/!PORTAL.wwpro_app_provider.execute_portlet/771029724/15 time=949ms timeout=15000ms process=Redirecting
07/01/26 14:32:05 portal: [perf] 199.64.107.21 http://portal.domain.com:7823/pls/portal/!PORTAL.wwpro_app_provider.execute_portlet/771029724/15 id=673911615591,2 type=dbPortlet name=ORACLE+PORTAL,6_500169_6_3_23 status=(null) user=E032034 subscriberID=1 reqTime=949ms waitTime=0ms cache=(null) timeout=No redirects=0 bytes=0 authLevel=10 webCacheStatus=(null) webCacheExpires=(null) webCacheAge=(null) csConv=No readTime=No,0ms pageTimeout=No procTime=0ms
07/01/26 14:32:05 portal: [perf] 199.64.107.21 http://portal.domain.com:7823/pls/portal/!PORTAL.wwpob_page.show?_pageid=6,3,6_23 id=673911615591,2 type=pageMeta name=6,3,6_23 status=200 user=E032034 subscriberID=1 reqTime=90ms waitTime=0ms cache=MISS,NEW timeout=No redirects=0 bytes=19652 authLevel=10 webCacheStatus=MISS,STALE [G] webCacheExpires=86400 webCacheAge=0 csConv=No readTime=No,0ms pageTimeout=No procTime=90ms
07/01/26 14:32:05 portal: [perf] 199.64.107.21 http://portal.domain.com/portal/page?_pageid=6,3,6_23&_dad=portal&_schema=PORTAL id=673911615591,2 type=page name=6,3,6_23 status=200 user=E032034 subscriberID=1 reqTime=1039ms waitTime=0ms cache=(null) timeout=No redirects=0 bytes=16878 authLevel=10 webCacheStatus=(null) webCacheExpires=(null) webCacheAge=(null) csConv=No readTime=No,0ms pageTimeout=No procTime=0ms
I placed the log in debug mode and got the error below:
07/01/26 18:54:20 portal: DEBUG: active=26 id=8817185720131,2 Content Fetcher Caught Dispatcher Exception :
oracle.webdb.utils.PortalExceptionImpl: I/O Error dispatching request
     at oracle.portal.PortalException.<init>(Unknown Source)
     at oracle.webdb.dispatcher.DispatcherException.<init>(Unknown Source)
     at oracle.webdb.dispatcher.HTTPDispatcher.dispatch(Unknown Source)
     at oracle.webdb.dispatcher.CacheDispatcher.dispatch(Unknown Source)
     at oracle.webdb.page.ContentFetcher.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:452)
     at java.net.Socket.connect(Socket.java:402)
     at java.net.Socket.<init>(Socket.java:309)
     at java.net.Socket.<init>(Socket.java:153)
     at HTTPClient.HTTPConnection$EstablishConnection.run(HTTPConnection.java:3938)
caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:452)
     at java.net.Socket.connect(Socket.java:402)
     at java.net.Socket.<init>(Socket.java:309)
     at java.net.Socket.<init>(Socket.java:153)
     at HTTPClient.HTTPConnection$EstablishConnection.run(HTTPConnection.java:3938)
What is confusing is how 1 browser gets the error but another does not.
Any suggestions?
TIA

This issue seems to be related to the specific URL used to access the Navigator. I was using a specific URL to display a particular page region for editing, namely
/portal/page?_pageid=6,3,6_23&_dad=portal&_schema=PORTAL&p_otype=FOLDER&p_octx=FOLDER.334478_1453&p_domain=wwc&p_sub_domain=SITEEXP
Once the Navigator is accessed via this URL, all subsequent attempts to access Page Groups Navigator portlet fail.
I changed my process to not use the URL above.

Error : The porlet could not be contacted

Anybody knows why the browser (Netscape) sometime shows "Error : The portlet could not be contacted" when I am accessing the web using portal.
Thanks so much.

There is a timeout duration set in your apache config file. If that portal takes more that that time to come then it
gets timed out

Patch 2744619 causes portlet could not be contacted

Hello,
Any anyone installed the Portlet patch 2744619 in an HTTPS configuration?
The patch successfully installs, no errors in the install log or portal.log. But when I log into Portal, ALL
Portlets have this error message:
The Portlet Could Not Be Contacted.
I don't receive this error message when applying the patch to a non-SSL installation.
Thanks,
- Carl

Found out to apply the patch to an SSL enabled environment you first must disable SSL, apply the patch and then enable SSL.
If you are running UNIX be sure to set PTLASST.CSH to execute privs. During the upgrade, this file is missing execute priv so when configuring SSL, it will fail.
- Carl

Portlet could not be contacted error in content area

hi everybody,
i've developed an application using Portal Content Area.And i am
accessing the content Area
like "http://<servername>/pls/portal30/url/folder/<Content area
name>".
But when i access it shows "Error : Portlet could not be
Contacted".then when i press refresh it opens the content Area.
Now i badly in need of avoiding that portlet error and directly
go to content area.
Pl. help me.
thanks in advance
regards,
Kathir

I strongly recommend upgrading to the 3.0.9 release (iAS
1.0.2.2) with the 3.0.9.8.2 patch (this patch should be
available for NT/2000 this week). Also, the database should be
running 8.1.7.1 (or later), as explained in the iAS release
notes.
Regards,
Jerry

Portlet could not be contacted

Hello!
Has anybody experinced this problem:
we have the following:
Server A, Windows 2000,2GB RAM, 9ias(9.0.2.0.0) [ infrastrcture, Portal, J2ee container, webcashe ]
Server B, Database Oracle 9i
when accessing a portal page through Webcashe over SSL, the user receives the error message, "Portlet could not be contacted".
when accessing a portal page directly (not over SSL and not through WEBChache), results no error message.
The problem appeared when the tried to deploy an j2ee applications to OC4j,deployment failed and they rebooted the server.
http event_log contains the following error:
03/Apr/2003:11:04:05 +0000 -- Error: SSL Handshake Failed NZERROR=28858
03/Apr/2003:11:04:23 +0000 -- Warning: In recv, recv fails with Net_Recv_x: Socket Timed out = 948
03/Apr/2003:11:04:25 +0000 -- Information: <Invalidation>0 URLs with prefix /pls/portal/ have been successfully invalidated.
03/Apr/2003:11:04:25 +0000 -- Information: <Invalidation>Invalidation with info 'INVALIDATION INFO.: URL=/pls/portal/PORTAL.wwpro_app_provider.do_object_signon;Event=invalidate_session_data' has returned with status 'SUCCESS'; number of documents invalidated: '0'.
03/Apr/2003:11:04:25 +0000 -- Error: In send, send fails with Net_Send_x.WriteFile: Socket Network Error = 64
03/Apr/2003:11:04:25 +0000 -- Error: SSL Handshake Failed NZERROR=28858
and the log.xml under 9ias_home\dcm\logs\dcmctl_logs shows
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2003-04-03T12:57:09.078+02:00</TSTZ_ORIGINATING>
<COMPONENT_ID>iAS_dcm</COMPONENT_ID>
<MSG_TYPE TYPE="ERROR"></MSG_TYPE>
<MSG_GROUP>n/a</MSG_GROUP>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>NT16</HOST_ID>
<HOST_NWADDR>139.106.0.2</HOST_NWADDR>
<MODULE_ID>oracle/defaultLogger/ExceptionLogger</MODULE_ID>
<PROCESS_ID>null-Thread[main,5,main]</PROCESS_ID>
<USER_ID>administrator</USER_ID>
</HEADER>
<PAYLOAD>
<MSG_TEXT>[TM] !!! Warning !!!
We have detected multiple DCM management processes managing the iAS instance, "D:\oracle\9ias". If configuration changes or application deployment operations are executed while multiple management processes are running, inconsistencies in configuration can occur. It is highly recommended that just one DCM management process be running at a time. The management process may be in the form of either the dcmctl command line process or the EMD management process.
If you have verified that only one management process is running and this message is still being logged, it is possible a management process was not shutdown down properly. Run "dcmctl shutdown -force" to properly shutdown the iAS instance and clean up any left over process state.</MSG_TEXT>
</PAYLOAD>
</MESSAGE>

Hi,
<MSG_TEXT>[TM] !!! Warning !!!
We have detected multiple DCM management processes managing the iAS instance, "D:\oracle\9ias". If configuration changes or application deployment operations are executed while multiple management processes are running, inconsistencies in configuration can occur. It is highly recommended that just one DCM management process be running at a time. The management process may be in the form of either the dcmctl command line process or the EMD management process.
If you have verified that only one management process is running and this message is still being logged, it is possible a management process was not shutdown down properly. Run "dcmctl shutdown -force" to properly shutdown the iAS instance and clean up any left over process state.</MSG_TEXT>
This is a synchronous problem between dcm proccesses.
You can solve it by installing 2591631 patch.
Also You should install 9.0.2.1 CorePatch before 2591631 patch.
And i want to tell that I think it isnt relevant about your problem "Portlet could not be contacted".
Good luck.

Error : Portlet could not be contacted ?

Hi ,
Working on Portal 9.0.2.3 , integrated an java application as Portlet to the tab by registering as new portlet provider .
It went on fine till now , recently when i click that particular tab i get this error
ERROR : PORTLET COULD NOT BE CONTACTED .
I tried to refresh the page manualy but still the error exisits.
kindly let me know how to debug this.

Mats,
I found this seems to happen if you are using the fully resolved url to access a page rather than unresolved url.
Unresolved URL:
http://socsbo1.scs.uiuc.edu/pls/portal30/url/page/socsbo_main
Resolved URL:
http://socsbo1.scs.uiuc.edu/servlet/page?_pageid=53&_dad=portal30&_schema=PORTAL30&_mode=3
Why it does this I don't know, but once I made sure the users where using the unresolved URL to access the page the portlet errors went away.
Portal Version: 3.0.7.6.2
Maybe this is happening to you?

HT4623 i have updated my i.phone 4 g but after updating when i turned on my phone it was showing the sign to connect to i.tunes and when when i connected i.tunes showed error that the server could not be contacted.... so what i can do now to resolve the

i have updated my ios 5 to 6 but when the updating aur dowloading has comleted and i turned on the phone it showed a sign to connect to the itunes and then i connecte to itunes but i.tunes showed error that the server could not be contacted....now what i can do to resolve the problem????

has your phone been jailbroken?

The data could not be saved because the server could not be contacted - Error

Hello, I'm a beginner in ligthswitch, so, I made a couple of screens and I made the database and attach to the application but when i want to save the new records shows me this error:
The data could not be saved because the server could not be contacted. Please check your network connection and try saving again.
The operation has timed out.
I verify the database, the record is saved but the application show me the error.
Please help me I have to deliver this screens today.
Thanks!
Boanerges. Mr 3: 17

Hi Elmer,
I researched this error message, I think you can try the methods below:
Increase the timeout of the connection between the client and the server
Increase Client timeout, and it is set in the Application class in the Client Project
For further information: Error message: Unable to save data

HT201210 trying to update my iphone but it ends up giving me an error saying , the server could not be contacted or is unavailabe ????

trying to update my iphone but it ends up giving me an error saying , the server could not be contacted or is unavailabe ????

Restore the iPhone when connected to iTunes by cable.
Still the same TS1275?
Is your iPhone jailbroken?
Or
Has your computer ever been used to jailbrake or downgrade (Tinyumbrella) any iPhone?

LS Getting the error "The data could not be saved because the server could not be contacted" when deploying on my local desktop

Hi:
I have a very simple test LS App:
1 Table "Person" with 1 property "Name"
One totally standard Editable Grid
So no complicated calculations that could timed out...
When I hit F5 the screen launches and shows the data, but when I try to create a new Person it waits for about 2 minutes and then the following error appears:
The data could not be saved because the server could not be contacted. Please check your network connection and try saving again. The Operation timed out.
Despite the error the data gets persisted on the database.
I am on VS 2013 Pro Update 4 and SQL Server LocalDB 2012 (v11.0).

If you decide to try again I would:
1) Uninstall Visual Studio
2) Uninstall SQL Server (all versions)
3) Re-install SQL Server
4) Re-Install Visual Studio
Unleash the Power - Get the LightSwitch 2013 HTML Client / SharePoint 2013 book
http://LightSwitchHelpWebsite.com

"Error Dialog: The server could not be contacted " when deploying web srvc

I have the J2EE 1.4 and Application Server 8 Q1 installed under windows. I have used all of the defaults on the install. The admin port is 4848. I want to install a web service on the http listener at 3345 (8080 was used and 3345 was substituted at installation time). I am getting the error from the deploytool when deploying the example web service "Hello". I am sure that the server is running and that the userid and password are the correct (I can log into the admin console with them). I've seen this error in other posts, but no solution. Does anyone have a solution to this???
Thanks in advance : )

yep, i get d same error on that, in fact, port 8000 is d default web service port, if i deploy the application via invalid port (eg. 4848 or 1234), i will get an error, say "cannot obtain a connected depolyment manager". but if i deploy that via 8000 (or 9191, it is also avaliable, casue i can connect to http://localhost:9191/ as default j2ee home page as well), i will get the error " the server could not be contected", and i m definitely sure that i can connect to console via 8000 and j2ee server is running by typing "j2ee -verbose" in command line.

Portal Jserv : fetcher dying...The portlet could not be contacted.

Similar Messages

Maybe you are looking for