[JBoss Portal] - Re: increasing the height of the hearder - jboss portal
by nhearne
"m.paranjape" wrote : You need to play around with the stylesheet. Follow the follwing steps.
|
| 1) check the theme that your are using in your portal page and go to the appropriate theme folder under your jboss-portal.sar\portal-core.war\themes folder.
|
| 2) open the portal_style.css file
|
| 3) Trying changing the #header-container, #header and #logoName as per your needs.
|
| Everything about the look and feel of the portal is in this style sheet.
|
Hello Thanks very much for your reply.
I am using 'renaissance' theme and have been playing with portal_style.css file in the 'renaissance' folder (I am using jboss protal bundle 2.6.6) working on exaclty same styles as you said (#header-container, #header and #logoName ) but nothing seem to have any affect on the height of the header, I thought changing the height on the #header should do it but it didn't! I have tried every single property in these styles and nothing has worked. I have manged to chagne the size of the image and other things but not the height of the header, am I missing something?
All the best!
N
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178792#4178792
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178792
17 years, 7 months
[Installation, Configuration & DEPLOYMENT] - classloader problem with a ear + sar inside
by DeMarco2
Hi jboss specialists.
I try to deploy an ear containg 1 sar 1 ejb and multible shared jars.
I try the follwing structure of the ear:
app.ear
|
|--- META-INF
| |
| |--- application.xml
| |--- jboss-app.xml
|
|--- lib
| |
| |--- lib1.jar
| |--- lib2.jar
| |--- .....
|
|--- service.sar
|--- ejb.jar
The service.sar also contains some jar-files which only should by loaded by the sar-classes. So the sar-file and it's packages should be loaded in seperate classloader.
For that reason, the sar file also contains a jboss-app.xml with the following entry:
<loader-repository>com.test.app:loader=service.sar</loader-repository>
If I deploy the sar-file standalone to jboss, this works fantastic. I see in the jmx-console that a new loader-repository is created.
But if I try to pack the sar in ear, no loader-repository is created for the sar-file!!!
So why is this entry in this way ignored?
The loader-repository entry in the jboss-app.xml of the ear does not help, because both ejb and sar should run in a different repositorys. the ejb-.jar must run in
the ucl because it uses some libraries of the common jboss lib-path.
You are asking why everything is packed together in the same ear-file? Both (sar and ear) share libraries (in a special version) in a in the lib path, and they should only deployed once...
Thanks for help
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178769#4178769
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178769
17 years, 7 months
[JBoss Portal] - Deadlock when clustering
by michaelchan
I get the following exception when clustering jboss portal on two nodes: I only extract first few lines of each exception here. Could someone please help me solve this? I suspected that it is a JBoss Cache configuration issue.
09:55:53,804 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2] TwoPhaseCoordinator.beforeCompletion - failed for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@503e4b
java.lang.RuntimeException:
Caused by: org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/, caller=GlobalTransaction:<10.0.0.98:34750>:47748, lock=write owner=GlobalTransaction:<10.0.0.98:34750>:47746 (activeReaders=0, activeWriter=Thread[ajp-10.0.0.98-8009-19,5,jboss], waitingReaders=0, waitingWriters=0, waitingUpgrader=0)
at org.jboss.cache.Node.acquire(Node.java:500)
Caused by: org.jboss.cache.lock.TimeoutException: write lock for / could not be acquired after 15000 ms. Locks: Read lock owners: []
Write lock owner: GlobalTransaction:<10.0.0.98:34750>:47746
(caller=GlobalTransaction:<10.0.0.98:34750>:47748, lock info: write owner=GlobalTransaction:<10.0.0.98:34750>:47746 (activeReaders=0, activeWriter=Thread[ajp-10.0.0.98-8009-19,5,jboss], waitingReaders=0, waitingWriters=0, waitingUpgrader=0))
at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:206)
at org.jboss.cache.Node.acquireWriteLock(Node.java:529)
at org.jboss.cache.Node.acquire(Node.java:476)
09:55:53,807 WARN [TreeCache] replication failure with method_call optimisticPrepare; id:18(GlobalTransaction:<10.0.0.103:34547>:15349, [_put; id:38(GlobalTransaction:<10.0.0.103:34547>:15349, /org/jboss/portal/core/impl/model/portal/ObjectNodeSecurityConstraint/actions/org.jboss.portal.core.impl.model.portal.ObjectNodeSecurityConstraint.actions#1059, item, CollectionCacheEntry[viewrecursive], true, org.hibernate.cache.OptimisticTreeCache$NonLockingDataVersion@1fe76c6)], null, 10.0.0.103:34547, false) exception
Caused by: org.jboss.cache.lock.TimeoutException: write lock for /org/jboss/portal/core/impl/model/portal/ObjectNodeSecurityConstraint/actions could not be acquired after 15000 ms. Locks: Read lock owners: []
09:55:53,807 WARN [TxInterceptor] Rolling back, exception encountered
javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178765#4178765
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178765
17 years, 7 months