Portlet counld not be contacted

Hi all!
i have done so far successfully with portal deploying jpdk but
when i recompiled one java file downloaded with Scheduler Portlet(it was registered before that) mentioning classpath and path,my portal main page is no more accessible i.e. "Portlet could not be contacted" ,Jserv log says "no classDeffound error'.
what is the problem??
thanks

In regards to your first problem: it is a bug - no 1552088.
As for the second problem - make sure that the page has Public property checked on.
Hope this helps.
Inga
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by bertrand hamonou ([email protected]):
I have a problem to view my Portal pages as a public viewer.When I type the address in my browser, the page is found but I see this message (
Error : portlet could not be contacted
for each portlet on my page.
One click on the refresh button shows the portlets.
What can I do to avoid that?
I've also created a URL-Item in a content area-folder, that allows you to go to the specified URL (open in a new browser) by clicking on the URL-associated image; but as it works perfectly when I'm logged on, once again, I can't view the portlet as a public user, even when I refresh the page.
Do you have advice for me?
thank you for your help
bertrand<HR></BLOCKQUOTE>
null

Similar Messages

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

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).

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).

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.

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

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 ?

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?

Portlet can not be contact

Hello,
System spec:
Portal 904
db 9.0.1.5
notbook memory: 1G
The problem:
We have a problem with one of our Portal 904 portlet.
After registering 2 Web providers, one to create a graph and one an outlook portlet on a notebook. we test them in our office, and all was well.
When we went to one of our customers, we tried to demonstrates the site with these 2 portlets, but instead we got: Portlet can not be contact.
We thought it was a memory problem or different java jvm but we are not sure, and can not test it now.
What can be the problem ?
Thanks

o Have you successfully accessed the provider test page (running on the laptop)?
o Did the provider registration go well?
o Can you ping the laptop from the Portal middle tier host?
o Have you tried replacing the laptop host name with its IP address?
o Have you checked the application.log file for additional information?
Peter

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

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

Error: Portlet could nog be contacted when adding URL portlet

Perhaps I'll get an answer this time... I refuse to write URGENT all over the title too...
I've done the following:
1. Create a Content Area.
2. Edit the page that corresponds to this Content Area
3. Add an item (URL)
4. Set the Display options (tab 3 in the wizard) to 'Item Displayed Directly In Folder Area'
5. Press Finish
6. Voila - some 1-2 minutes pass, and then a page saying 'Error: The portlet could not be contacted'
If I set the display options to the first or the second choice in step 4, everything works as it should. Is there a known bug or am I having Murphy for lunch?
The database is an 8.1.7.0.0EE on Solaris 8, the portal is a 3.0.9 on a 9iAS 1.0.2.2. I've tried the patch for Timeout for Content, and I've tried increasing the servlet.page.initArgs=requesttime to 45 or 60, but to no avail.
null

Hey!!! what happened????. I sent a message and it disappeared!!!!!. OTN isn't working!!!
well!!!
I realized that my Oracle DB spends a lot of time in sqls like this(8000 records each time):
SELECT *
FROM portalWWNLS_STRINGS$
STR1,WWNLS_STRINGS$ STR2
WHERE STR1.ID = :b1
AND STR2.DOMAIN (+) = STR1.DOMAIN
AND STR2.SUB_DOMAIN (+) = STR1.SUB_DOMAIN
AND STR2.NAME (+) = STR1.NAME
AND STR2.LANGUAGE (+) = LOWER(:b2)
Just create Indexes(PORTAL30 and PORTAL30_SSO schemas) to optimize this query and your Oracle Portal will fly!!!!!
CREATE INDEX wwnls_stri_idx_adr_id
ON wwnls_strings$
( id )
PCTFREE 10
INITRANS 2
MAXTRANS 255
TABLESPACE system
STORAGE (
INITIAL 12288
NEXT 49152
PCTINCREASE 50
MINEXTENTS 1
MAXEXTENTS 249
CREATE INDEX wwnls_stri_idx_adr_super
ON wwnls_strings$
( domain,
sub_domain,
name,
language )
PCTFREE 10
INITRANS 2
MAXTRANS 255
TABLESPACE system
STORAGE (
INITIAL 12288
NEXT 73728
PCTINCREASE 50
MINEXTENTS 1
MAXEXTENTS 249
I hope this help you!!!!
Adrian

Site Index Portlet is not refreshed correctly

I have deployed the Site Index Portlet in Portal 10.1.4, and it seems to work nicely. However, sometimes the portlet does not refresh correctly, even though other elements on the page (e.g. banner, page path) are updated. Refreshing the page with F5 in Internet Explorer 6.0 (or clicking the same link once more) refreshes the content of the portlet, but this is unacceptable for end users.
The same problem is not possible to reproduce in Firefox 1.5. If only all end users were using Firefox . . .
Any ideas for how to fix this for all browsers?
-- [email protected] [Senior Principal Consultant]
-- http://home.c2i.net/toreingolf/contact/

My browser caching is already set to "Every visit to the page", I'm afraid.
I was suspecting the PPE in Portal, but if that was the reason, then the problem would occur in all browsers, right? Or do you think this could be caused by how IE handles ESI?
Interestingly, the portlet works perfectly in Firefox (the menu is even updated immediately, before the new page loads!). And in Opera, the menu doesn't show up at all! What's going on here?

HELP! iPhone 3GS stuck in recovery loop and iTunes gives error message" iPod update server can not be contacted"

As I said, it's an iPhone 3GS (never jailbroken), iOS 4.1, PowerPC G4 OS X 10.4.11, iTunes 9.2. I have had the phone since new, never had any issues with it and am at my wits end trying to figure it out. I have seen many different solutions to this exact problem, but none have worked for me. Anyone have any ideas?

This is what I posted to someone else having an update issue... Just for your information:
I having the same issue about the and iTunes says "The iPhone cannot be restored at this time because the iPhone software update server could not be contacted or is temporarily unavailable.". I've had the iPhone 3GS since it came out. It was working fine until I just tried to update it. It has NEVER been hacked or jailbroken. WE AND A FEW OTHERS are having the same issue then it is more than likely that this is an update issue. I took mine to the Apple store and the tech tried to update it and he came to the same problem and told me he couldn't update it. My assumption is that we are not the only one's with this issue and that if there was a way to update it to the update before this last one it might be a solution. I don't know how to get the previous update. Apple probably is aware of the problem, and hasn't come up with a solution yet. Or, enough people haven't complained yet. The tech suggested that there might be something wrong with the phone itself, but that couldn't be since it was working perfectly before I updated it and others are having the same issue. It is highly unlikely that a lot of people are having the same hardware issue all of a sudden at the same time. Apple/iTunes needs to fix this... and hopefully soon
Also: I can update or restore my iPhone 5 and other iPhones so it is not an issue with my firewall or other software on my computer. No one touches my iPhone or my computer they are secure, locked all the time, and I have no jailbreak software on my computer (Apple tried it and they are clueless at the moment from what I can tell).

Portlet counld not be contacted

Similar Messages

Maybe you are looking for