[Beginners Corner] - Re: Jboos Wiki install - help
by PeterJ
I'm running the wiki on Portal 2.6.2. All I did was drop the wiki.war into the deploy folder. As far as I know, the wiki does not use the database (it stores the wiki contents on disk), so I do not think that the errors are necessarily wiki related.
A few thoughts:
1) I'm not sure if the wiki has been updated to run on 2.6.3 (I haven't tried it, and judging from earlier posts the wiki tends to be picky about which Portal version it runs with). Try running it on 2.6.2, if that works, you need to use that version.
2) Did you start over from scratch with an empty database? Perhaps the wiki contents being in CMS is causing the issue. I would first bring up just the Portal (with a clean install and clean database), and after verifying that that is running, I would bring down the app server, copy the wiki.war to the deploy folder, and then start it again.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125205#4125205
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125205
16 years, 4 months
[JBoss Seam] - Seam + Informix - java.lang.IllegalStateException
by dmg
I have written an application using Seam & MySQL which is working. I am now trying to connect the application to Informix and I am getting the following exceptions:
| 10:42:15,676 INFO [AuthenticatorAction] authenticating admin
| 10:42:16,841 INFO [STDOUT] Hibernate:
| select
| user0_.id as id6_,
| user0_.username as username6_,
| user0_.password as password6_,
| user0_.salt as salt6_,
| user0_.email as email6_,
| user0_.role as role6_
| from
| uv_user user0_
| where
| user0_.username=?
| 10:42:16,912 INFO [AuthenticatorAction] authenticating admin succeeded
| 10:42:17,268 ERROR [SeamPhaseListener] uncaught exception
| java.lang.IllegalStateException: Could not commit transaction
| at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:602)
| at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:330)
| at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:231)
| at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:182)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280)
| at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
| .....
| Caused by: 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
| at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1401)
| at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
| at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
| at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140)
| at org.jboss.seam.transaction.UTTransaction.commit(UTTransaction.java:52)
| at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:592)
|
These exceptions are raised after a user successfully authenticates using:
| @Stateless
| @Name("authenticator")
| public class AuthenticatorAction implements Authenticator
| {
| @PersistenceContext
| private EntityManager em;
|
| @In
| Identity identity;
|
| @Out(required = false, scope = SESSION)
| private User user;
|
| @Logger
| Log log;
|
| public boolean authenticate()
| {
| log.info("authenticating #0", identity.getUsername());
|
| try
| {
| user = (User) em.createQuery("from User where username = :username")
| .setParameter("username", identity.getUsername())
| .getSingleResult();
|
| if (!user.getPassword().equals(Passwords.passwordDigest(identity.getPassword(), user.getSalt())))
| return false;
|
| if (user.getRole() != null)
| {
| identity.addRole(user.getRole());
| }
|
| log.info("authenticating #0 succeeded", identity.getUsername());
| return true;
| }
| catch (NoResultException e)
| {
| log.info("exception while authenticating #0", e, identity.getUsername());
| return false;
| }
| }
| }
|
My Informix datasource file is:
| <datasources>
| <local-tx-datasource>
| <jndi-name>informixDatasource</jndi-name>
|
| <connection-url>jdbc:informix-sqli://hostname:1526/database:INFORMIXSERVER=iserver</connection-url>
| <driver-class>com.informix.jdbc.IfxDriver</driver-class>
| <user-name>username</user-name>
| <password>password</password>
|
| <exception-sorter-class-name>
| org.jboss.resource.adapter.jdbc.vendor.InformixExceptionSorter
| </exception-sorter-class-name>
| <metadata>
| <type-mapping>InformixDB</type-mapping>
| </metadata>
| </local-tx-datasource>
| </datasources>
|
and my persistence file is:
| <persistence-unit name="uvoltds">
| <provider>org.hibernate.ejb.HibernatePersistence</provider>
| <jta-data-source>java:/informixDatasource</jta-data-source>
| <properties>
| <property name="hibernate.dialect" value="org.hibernate.dialect.InformixDialect"/>
|
| <property name="hibernate.hbm2ddl.auto" value="validate" />
| <property name="hibernate.show_sql" value="true" />
| <property name="hibernate.format_sql" value="true" />
| <property name="jboss.entity.manager.factory.jndi.name"
| value="java:/uvoltdsEntityManagerFactory" />
| </properties>
| </persistence-unit>
|
I've tried unsuccessfully to find a clue via google. Can anyone point out the obvious or push me in the right direction?
Thanks,
Dan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125200#4125200
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125200
16 years, 4 months
[JBoss Seam] - Clone Seam application for Virtual Domains
by vanyatka
Hi,
I have to admit I'm in a bit of a quandary. I need to clone a seam application and place it under new virtual domain name. The business logic should remain the same, while the presentation layer and the DB will change.
The easiest option would be to build an EAR for each of the hosts, where only WAR and persistence.xml would be different. One of the drawbacks of this solution is that there is a copy of the JAR in all EARs, and if I need to make a change in actions, I would have to rebuild all EARs.
Before writing this message I thought I'd much like to see a single instance of JAR, but that would require a single of EAR as well, and that in turn would require reloading the whole set of webapps to make a single change in any of the webapps. Please, correct me if I'm wrong here.
Right now I'm thinking that creating multiple EARs for each of the virtual hosts isn't a bad solution, given that the process bulding those EARs is automated with ant.
Has anyone had to solve this kind of task of cloning and putting clones under the different domain names?
Thanks,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125194#4125194
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125194
16 years, 4 months