[JBoss jBPM] - jbpm-console user login error with Jbpm-3.26.SP1 and JBoss-4
by arpan25
Hi,
I am using Jbpm-3.26.SP1 along with Jboss-4.2.2.GA. I created teh database, tables and added data to the tables as well..
But I am getting invalid username or password error after logging in.
Can anyone help ? I have pasted the error log of the server below...
12:21:58,773 ERROR [STDERR] Jun 18, 2009 12:21:58 PM com.sun.facelets.compiler.T
agLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/C:/Users/sparkle/Documents/Downloads/jboss-4
.2.2.GA/server/default/deploy/jbpm/jsf-console.war/WEB-INF/lib/jsf-facelets-1.1.
15.B1.jar!/META-INF/jstl-fn.taglib.xml
12:22:06,624 WARN [JBossManagedConnectionPool] Throwable while attempting to ge
t a new connection: null
java.lang.NoSuchMethodError: com.mysql.jdbc.jdbc2.optional.MysqlXADataSource.get
PinGlobalTxToPhysicalConnection()Z
at com.mysql.jdbc.jdbc2.optional.MysqlXADataSource.wrapConnection(MysqlX
ADataSource.java:68)
at com.mysql.jdbc.jdbc2.optional.MysqlXADataSource.getXAConnection(Mysql
XADataSource.java:60)
at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.createM
anagedConnection(XAManagedConnectionFactory.java:136)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.cr
eateConnectionEventListener(InternalManagedConnectionPool.java:577)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.ge
tConnection(InternalManagedConnectionPool.java:262)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BaseP
ool.getConnection(JBossManagedConnectionPool.java:500)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManage
dConnection(BaseConnectionManager2.java:341)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedCo
nnection(TxConnectionManager.java:315)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateC
onnection(BaseConnectionManager2.java:396)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$Connectio
nManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wrapp
erDataSource.java:88)
at org.jboss.security.auth.spi.DatabaseServerLoginModule.getUsersPasswor
d(DatabaseServerLoginModule.java:141)
at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(Usernam
ePasswordLoginModule.java:206)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:1
86)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:6
80)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecur
ityManager.java:603)
at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecur
ityManager.java:537)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityMa
nager.java:344)
at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBos
sSecurityMgrRealm.java:491)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(Form
Authenticator.java:257)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
torBase.java:416)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
onnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ss(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
6)
at java.lang.Thread.run(Thread.java:619)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238626#4238626
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238626
16 years, 10 months
[JBoss Portal] - Re: coordination features in jboss portal
by mposolda@redhat.com
The important assumption is, that you are familiar with inter-portlet communication concepts like Public render parameters and Events, which is described in JSR-286 (http://jcp.org/en/jsr/detail?id=286).
Scenario described in chapter 8 extends the implicit behaviour, which should be implemented by every portal. For example you can use parameter bindings if you have portletA" with public render parameter "paramA" and "portletB" with public render parameter "portletB" and you need to wire these parameters with each other. So you can set "paramA" in processAction method in "portletA" and you can read this parameter as "paramB" in render method of "portletB". With default implicit behaviour, the both parameters need to have same name.
The possibility of different names "paramA" and "paramB" is enabled by parameter bindings. Event wirings and alias bindings concept are similar to this concept as well.
Use portal-coordination-samples if you need more inspiration. We will provide more useful sample portlets soon.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238625#4238625
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238625
16 years, 10 months