Hi Frank,

I could not reproduce the problem here.
I created a user, TEST, and set the profiling rule to j2 (the default) or 
user-role-fallback, but couldn't reproduce it.
Could you provide a reproducing steps with a clean Jetspeed-2.2.0 installation?

Woonsan


----- Original Message ----
> From: Frank Otto <[email protected]>
> To: Jetspeed Users List <[email protected]>
> Sent: Fri, April 16, 2010 4:58:43 PM
> Subject: Re: users default-page was not loaded
> 
> I have enabled ojb logging, and the log shows this:

2010-04-16 
> 16:55:47,435 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.core.PersistenceBrokerImpl - Creating RsIterator for 
> class 
> [org.apache.jetspeed.profiler.rules.impl.PrincipalRuleImpl]
2010-04-16 
> 16:55:47,435 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl - executeQuery: 
> QueryByCriteria 
> from class org.apache.jetspeed.profiler.rules.impl.PrincipalRuleImpl  where 
> [principalName = OTF, locatorName = page]
2010-04-16 16:55:47,435 
> [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.sql.SqlQueryStatement$TableAlias - 
> TableAlias(): using hints ? false
2010-04-16 16:55:47,435 
> [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.sql.SqlGeneratorDefaultImpl - SQL:SELECT 
> A0.PRINCIPAL_NAME,A0.LOCATOR_NAME,A0.RULE_ID FROM PRINCIPAL_RULE_ASSOC A0 
> WHERE 
> (A0.PRINCIPAL_NAME = ?) AND A0.LOCATOR_NAME = ?
2010-04-16 16:55:47,437 
> [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl - 
> executeQuery: com.informix.jdbc.ifxpreparedstatem...@4976d6
2010-04-16 
> 16:55:47,439 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.RsIterator - 
> RsIterator[org.apache.ojb.broker.accesslayer.RsQueryObject[query: 
> QueryByCriteria from class 
> org.apache.jetspeed.profiler.rules.impl.PrincipalRuleImpl  where 
> [principalName = OTF, locatorName = page], class descriptor: 
> org.apache.jetspeed.profiler.rules.impl.PrincipalRuleImpl]] 
> initialized
2010-04-16 16:55:47,439 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.RsIterator - hasNext() -> 
> true
2010-04-16 16:55:47,439 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.core.PersistenceBrokerImpl - getObjectByIdentity 
> org.apache.jetspeed.profiler.rules.impl.AbstractProfilingRule{user-role-fallback}
2010-04-16 
> 16:55:47,443 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.StatementManager - closeResources was 
> called
2010-04-16 16:55:47,445 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.core.QueryReferenceBroker - getCollectionByQuery (class 
> org.apache.ojb.broker.util.collections.RemovalAwareCollection, class 
> org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl, QueryByCriteria 
> from 
> class org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl  where 
> [ruleId = user-role-fallback])
2010-04-16 16:55:47,445 
> [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.core.PersistenceBrokerImpl - 
> Creating RsIterator for class 
> [org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl]
2010-04-16 
> 16:55:47,445 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl - executeQuery: 
> QueryByCriteria 
> from class org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl  where 
> [ruleId = user-role-fallback]
2010-04-16 16:55:47,445 [http-8180-Processor24] 
> DEBUG org.apache.ojb.broker.accesslayer.sql.SqlQueryStatement$TableAlias - 
> TableAlias(): using hints ? false
2010-04-16 16:55:47,445 
> [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.sql.SqlGeneratorDefaultImpl - SQL:SELECT 
> A0.CRITERION_ID,A0.RULE_ID,A0.FALLBACK_ORDER,A0.REQUEST_TYPE,
> href="http://A0.NAME";>A0.NAME,A0.COLUMN_VALUE,A0.FALLBACK_TYPE FROM 
> RULE_CRITERION A0 WHERE A0.RULE_ID = ? ORDER BY 3
2010-04-16 16:55:47,448 
> [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.JdbcAccessImpl - 
> executeQuery: com.informix.jdbc.ifxpreparedstatem...@1a3b17a
2010-04-16 
> 16:55:47,449 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.RsIterator - 
> RsIterator[org.apache.ojb.broker.accesslayer.RsQueryObject[query: 
> QueryByCriteria from class 
> org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl  where [ruleId = 
> user-role-fallback], class descriptor: 
> org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl]] 
> initialized
2010-04-16 16:55:47,449 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.RsIterator - hasNext() -> 
> true
2010-04-16 16:55:47,449 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.RsIterator - hasNext() -> 
> true
2010-04-16 16:55:47,449 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.RsIterator - hasNext() -> 
> true
2010-04-16 16:55:47,449 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.RsIterator - hasNext() -> 
> true
2010-04-16 16:55:47,450 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.accesslayer.RsIterator - hasNext() -> 
> false
2010-04-16 16:55:47,450 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - Materialisation of object 
> is 
> finished, push 6objects to cache
2010-04-16 16:55:47,450 
> [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - 
> Push to cache: 
> org.apache.jetspeed.profiler.rules.impl.PrincipalRuleImpl{OTF,page}
2010-04-16 
> 16:55:47,450 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - Push to cache: 
> org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl{21}
2010-04-16 
> 16:55:47,450 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - Push to cache: 
> org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl{22}
2010-04-16 
> 16:55:47,450 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - Push to cache: 
> org.apache.jetspeed.profiler.rules.impl.AbstractProfilingRule{user-role-fallback}
2010-04-16 
> 16:55:47,450 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - Push to cache: 
> org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl{19}
2010-04-16 
> 16:55:47,450 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - Push to cache: 
> org.apache.jetspeed.profiler.rules.impl.RuleCriterionImpl{20}
2010-04-16 
> 16:55:47,450 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - Clear materialization 
> cache
2010-04-16 16:55:47,452 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.core.PersistenceBrokerImpl - PB.close was called: 
> org.apache.ojb.broker.core.persistencebrokeri...@17cd18d
2010-04-16 
> 16:55:47,452 [http-8180-Processor24] DEBUG 
> org.apache.ojb.broker.cache.MaterializationCache - Clear materialization 
> cache


So I think jetspeed use user-role-fallback

Am 16.04.2010 
> 16:51, schrieb Woonsan Ko:
> Hi Frank,
> 
> I think you can 
> find it with j2-admin's UserManagement portlet. (e.g. 
> http://localhost:8080/jetspeed/portal/Administrative/user-mgt.psml)
> If 
> you choose the user, TEST, then you could find the profile name on the right 
> pane.
> 
> Woonsan
> 
> 
> ----- Original Message 
> ----
>    
>> From: Frank Otto<
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]>
>> To: 
> Jetspeed Users List<
> href="mailto:[email protected]";>[email protected]>
>> 
> Sent: Fri, April 16, 2010 4:29:32 PM
>> Subject: Re: users default-page 
> was not loaded
>> 
>> Hi Woonsan,
>>    
>   
> How can I find this? In a table?
> 
> I test 
> jetspeed on an
>    
>> informix database. The generate 
> script works fine,
>>      
> jetspeed started 
> and
>    
>> j2-admin/jetspeed-layouts/myPortlets was 
> deployed.
>>      
> My portal app works 
> on
>    
>> mssql and unify sqlbase database. So I 
> think it
>>      
> must be an error on 
> database
>    
>> structure (or datas) in 
> informix.
>>      
> 
> Frank
> 
> 
> 
> 
> Am 16.04.2010
>    
>> 
> 16:22, schrieb Woonsan Ko:
>> Hi Frank,
>> 
>> What 
> profiling rule
>> is configured for the TEST user?
>> 
> 
>> 
>> -Woonsan
>> 
>> 
>> ----- 
> Original Message ----
>> 
>> 
>>      
> 
>>> From: Frank Otto<
>>>        
> 
>> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]>
>>  
>     
>>> To:
>>>        
> 
>> ymailto="mailto:
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]"
>> 
> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
>>  
>     
>>>        
>> Sent: 
> Fri, April 16, 2010 3:30:16 PM
>>      
>>> 
> Subject: users default-page was
>>>        
> 
>> not loaded
>>      
>>> 
> Hi,
>>> 
>>>        
>> I 
> have registered a new user (for example: TEST) in my jetspeed
>> 
> 
>> 
>>      
>>> portal (2.2.0). 
> The folder /_user/TEST was created, but If I
>>>      
>   
>> logged in, the
>>      
> 
>>> default-page.psml from this folder will not 
> be
>>>        
>> loaded. The 
> default-page.psml
>>      
>>> from 
> min-pages folder was
>>>        
>> 
> shown.
>>      
>>> 
>>>  
>       
>> Has someone an idea? How can I
>> 
> check
>> 
>>      
>>> this? I 
> found no error in my log
>>>        
>> 
> files.
>>      
>>> 
>>>  
>       
>> kind
>> 
>> 
> 
>>      
>>> regards,
>>> 
> 
>>>        
>> Frank
>> 
> 
>> 
>> 
>> 
> ---------------------------------------------------------------------
>> 
> 
>> To
>> 
>>      
>>> 
> unsubscribe, e-mail:
>>> 
>>>        
> 
>> ymailto="mailto:
>> href="mailto:
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]"
>>  
>     
>>>        
>> 
> href="mailto:
>> href="mailto:
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]">
>> 
> ymailto="mailto:
> href="mailto:[email protected]";>[email protected]"
>> 
> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
>>  
>     
>>> 
>>>        
> 
>> 
>> For
>> 
>>      
> 
>>> additional
>>>        
> 
>> commands, e-mail:
>>      
>>> 
> ymailto="mailto:
>>>        
>> 
> ymailto="mailto:
> href="mailto:[email protected]";>[email protected]"
>> 
> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]"
>>  
>     
>>>        
>> 
> href="mailto:
>> href="mailto:
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]">
>> 
> ymailto="mailto:
> href="mailto:[email protected]";>[email protected]"
>> 
> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
>>  
>     
>>> 
>>>        
> 
>> 
>> 
>> 
>> 
>> 
>> 
> ---------------------------------------------------------------------
>> 
> To
>> unsubscribe, e-mail:
>> ymailto="mailto:
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]"
>> 
> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
>> 
> 
>> For additional commands, e-mail:
>> ymailto="mailto:
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]"
>> 
> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
>> 
> 
>> 
>> 
>> 
>>      
> 
> 
> 
> ---------------------------------------------------------------------
> 
> To
>    
>> unsubscribe, e-mail:
>> 
> ymailto="mailto:
> href="mailto:[email protected]";>[email protected]"
>> 
> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
>>  
>     
> For
>    
>> additional 
> commands, e-mail:
>> ymailto="mailto:
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]"
>> 
> href="mailto:
> href="mailto:[email protected]";>[email protected]">
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
>>  
>     
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To 
> unsubscribe, e-mail: 
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
> 
> For additional commands, e-mail: 
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
> 
> 
>    
> 


---------------------------------------------------------------------
To 
> unsubscribe, e-mail: 
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]
For 
> additional commands, e-mail: 
> ymailto="mailto:[email protected]"; 
> href="mailto:[email protected]";>[email protected]


      

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to