Current Position:Home > Portal Jserv : fetcher dying...The portlet could not be contacted.

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

Update:12-10Source: network consolidation
Advertisement
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).

The Best Answer

Advertisement
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).
  • Portal Jserv : fetcher dying...The portlet could not be contacted. Update:12-10

    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 contact

  • Pls/portal shows: Error: The portlet could not be contacted  after SSL enab Update:11-30

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

  • Passing parameter spage id and portal language to a report portlet Update:11-30

    Hi, how can I pass the page id and portal language to a report portlet so I can filter my query according to that page id and language. See the report query below: select <information required> from ana_statistics where portal_page = :page_parameter

  • Cannot access page groups via Navigator "portlet could not be contacted" Update:11-30

    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 bro

  • Portlet counld not be contacted Update:11-30

    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. "Port

  • Portlet could not be contacted error in content area Update:10-11

    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

  • Error: Portlet could nog be contacted when adding URL portlet Update:11-30

    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

  • Patch 2744619 causes portlet could not be contacted Update:11-30

    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 C

  • Portlet could not be contacted Update:11-30

    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 SS

  • Error : Portlet could not be contacted ? Update:11-30

    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 CONTACTE