JBossDeveloper

using win xp---mysql 4.1.8 + mysql-connector-java-3.1.12-bin.jar + portal 2.2.1rc1 + jboss AS 4.0.3sp1

y used to have jdk1.5.....i uninstalled like yiou said, instaled 1.4_10 version and make all the things about the database format...and reinstaled jboss AS but it the same.........when i deploy the portal 2.2 works fine.....

here i add more information.....y have cleared the jboss as and mysql but its still the problem....look at this:


--- MBeans waiting for other MBeans ---
ObjectName: portal:policy=PortalPolicyConfigStore,type=Component
State: FAILED
Reason: java.lang.IllegalArgumentException: No transaction manager provided
I Depend On:
portal:policy=JaccPortalPolicyConfigurator
portal:service=TreeCacheProvider,type=transient
portal:policy=PortalPolicyConfigService
Depends On Me:
portal:deploymentFactory=PortletApp

ObjectName: portal:deploymentFactory=PortletApp
State: CONFIGURED
I Depend On:
portal:deployer=PortalWebApp
portal:service=WebAppRegistry
portal:service=ServerConfig
portal:policy=PortalPolicyConfigStore,type=Component
Depends On Me:
portal:deployer=Adapter

ObjectName: portal:deployer=Adapter
State: CONFIGURED
I Depend On:
portal:deploymentFactory=Object
portal:deploymentFactory=PortletApp
portal:deploymentFactory=Layout
portal:deploymentFactory=LayoutFeatures
portal:deploymentFactory=Theme
portal:service=Module,type=User
portal:service=Module,type=Role
portal:service=Module,type=Mail
portal:deployer=PortalWebApp
jboss.web:service=WebServer

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: portal:policy=PortalPolicyConfigStore,type=Component
State: FAILED
Reason: java.lang.IllegalArgumentException: No transaction manager provided
I Depend On:
portal:policy=JaccPortalPolicyConfigurator
portal:service=TreeCacheProvider,type=transient
portal:policy=PortalPolicyConfigService
Depends On Me:
portal:deploymentFactory=PortletApp


i'am doing all steps said in the user guide :(

can i change the html editor bundled in the cms admin??
i can't manage the content the way i want, the color , the size of the letters etc doen't work...maybe a javascript problem.

2) when i upload a file the cms admin disapears..how can i make a new blank intalation? there is something in my winxp configuration that changed?


thnx.
noicangi

I am joining this only because I can confirm the problem. I am using mysql 4.1.16 + mysql-connector-java-3.1.12-bin.jar + portal 2.2.1rc1 + jboss AS 4.0.3sp1 default install + Fedora 4 + java 1.5
All the messages reported appear under linux in the same way as in xp. If I can be of any help let me know.

I had the same problem with mysql 5.0.17, jboss 4.0.3SP1, mysql-connector-java-3.1.12-bin.jar, portal 2.2.1rc1, java 1.5. I downloaded the JBoss + Portal 2.2.1RC1 bundle and used the same portal-mysql-ds.xml. Now portal works perfectly. I'm not sure of the actual cause of the problem, but this was an easy workaround.

this error is caused installing jboss AS with the instaler.jar, if you just unzip jboss bundled and configure portal DB its work perfectly

Me2. I'm running on Windows XP. Using PosgresQL 8.

I see a couple of errors:

13:26:27,336 DEBUG [ServiceController] Creating service jboss.system:service=Thr State: FAILED
Reason: javax.jcr.RepositoryException: failed to load persisted repository sta
te: java.sql.SQLException: ERROR: invalid large-object descriptor: 0: java.sql.S
QLException: ERROR: invalid large-object descriptor: 0
I Depend On:
jboss.jca:service=DataSourceBinding,name=PortalDS
portal:service=JAASLoginModule
Depends On Me:
portal:mapper=CMSObject

ObjectName: portal:policy=PortalPolicyConfigStore,type=Component
State: FAILED
Reason: java.lang.IllegalArgumentException: No transaction manager provided
I Depend On:
portal:policy=JaccPortalPolicyConfigurator
portal:service=TreeCacheProvider,type=transient
portal:policy=PortalPolicyConfigService
Depends On Me:
portal:deploymentFactory=PortletApp

==Leonard

Also, I installed JBoss AS with the installer, and selected "all" so that I would get EJB3.

What does using the installer cause trouble? If so, when can we expect this to work?

thanks,
==Leonard

I just tried the zip'd JBoss AS download, instead of the installer one, and the portal does work, as someone previously said in this thread, but I do get a similar error:

2006-01-26 14:14:42,439 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner
] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: portal:service=CMS
State: FAILED
Reason: javax.jcr.RepositoryException: failed to load persisted repository sta
te: java.sql.SQLException: ERROR: invalid large-object descriptor: 0: java.sql.S
QLException: ERROR: invalid large-object descriptor: 0
I Depend On:
jboss.jca:service=DataSourceBinding,name=PortalDS
portal:service=JAASLoginModule
Depends On Me:
portal:mapper=CMSObject

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: portal:service=CMS
State: FAILED
Reason: javax.jcr.RepositoryException: failed to load persisted repository sta
te: java.sql.SQLException: ERROR: invalid large-object descriptor: 0: java.sql.S
QLException: ERROR: invalid large-object descriptor: 0
I Depend On:
jboss.jca:service=DataSourceBinding,name=PortalDS
portal:service=JAASLoginModule
Depends On Me:
portal:mapper=CMSObject

Maybe this isn't related to the reason why the installer one fails to run the portal.

BTW, when I say the installer one, I mean that I installed AS via the "Run Installer" link, not that I actually downloaded the jboss-4.0.3SP1-installer.jar and ran that.

I tested on PostGres 8.1 and it was working.

Make sure you are getting the 2.2.1RC1 binary. http://prdownloads.sourceforge.net/jboss/jboss-portal-2.2.1RC1.zip?download

Deploy it under AS 4.0.3SP1.

I'm using PostgresQL 8.0, Portal 2.2.1RC1, and I'm using AS 4.0.3SP1 both from the zip download and the installer link.

Should using Portal under the AS acquired via the installer link work, that is, it has been tested?

Do you think the different in PostgresQL 8.0 and 8.1 would make a difference?

thanks.

No. The postgres minor version should not matter.

The CMS code was changed and fixed the PostGres problem, as PG did not like closing the stream before the tx.commit. I test it and it worked, but I'm beginning to think the fix did not make it in to the distro.

Julien refactored the CMS persistence manager, so I will now test for the upcoming RC2 and make certain it works on popular DBs.

sitongia, the same happened to me, i tried unstalling jboss as 401sp1 with the instaler.jar without result, then i tried upzip the jboss and unzip the portal 2.2.1rc1 to the deploy and didn`t work....finaly i just unzip the portal bundled with jboss (2.2.1rc1+ jboss as 403sp1) and worked.

to make portal function with mySQL in case of using the hibernate y add the connector to the lib dir and delete the portal-hb***-DB.xml and add the portal-mysql-db.xml and that's it.

i think its this and not a posgress error.

hope its usefull
nx

to make portal function with mySQL in case of using the hibernate y add the connector to the lib dir and delete the portal-hb***-DB.xml and add the portal-mysql-db.xml and that's it.

JBoss 4.0.3.sp1
jdk 1.5
ejb3 rc4
portal 2.2.1.rc2
sqlserver 2000

I was getting the no transaction manager problem that others described earlier on this thread. I changed the configuration of the transient tree cache mbean in the portal's jboss-service.xml to the following...

<mbean

 code="org.jboss.cache.TreeCache"

 name="portal:service=TreeCache,type=transient">

 <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>

 <attribute name="IsolationLevel">REPEATABLE_READ</attribute>

 <attribute name="CacheMode">LOCAL</attribute>
 <depends>jboss.jca:service=DataSourceBinding,name=PortalDS</depends>

 </mbean>