June 2009 - jboss-user - Jboss List Archives

[Installation, Configuration & DEPLOYMENT] - Re: access jboss web console remotely?

by hand-solo

I'm such a dope, I had opened up port 80, but not 8080 Thanks for the help I'm so used to using port 80 guess I had it stuck in my head. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238627#4238627 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238627

16 years, 10 months

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[Security & JAAS/JBoss] - Re: JBoss SSO not able to build the src folder..

by anil.saldhana＠jboss.com

http://www.jboss.org/auth/jbossidentity/ Take a look at this project. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238624#4238624 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238624

16 years, 10 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - xxx-jboss-beans.xml realm

by michel.strogoff

Hi, I have created a realm configuration to authenticate users against a JNDI registered database. I have followed the instructions of this blog : http://anil-identity.blogspot.com/2009/05/as5-specifying-security-domain..... The configuration of the realm seems to be correct since it works correctly when I put it in the login-config.xml file. But when I use it as a embedded in my web app (along with jboss-web.xml file), I get the following error : javax.security.auth.login.LoginException: Error looking up DataSource from: java:/jdbc/ShareDataSource at org.jboss.security.auth.spi.DatabaseServerLoginModule.getUsersPassword(DatabaseServerLoginModule.java:194) at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... Caused by: javax.naming.NameNotFoundException: ShareDataSource When I connect to JBoss admin-console, I can see the data source is available. And the application starts up and connects to it. But the realm login module is not. Can you see why ? Best regards, Eric View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238623#4238623 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238623

16 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: 4.2.3.GA messaging service?

by clebert.suconic＠jboss.com

http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238621#4238621 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238621

16 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: 4.2.3.GA messaging service?

by newmanw10

Thanks Peter! Is there any easy way to configure 4.2.3 to use JBoss Messaging? What are some high level advantages if so. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238620#4238620 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238620

16 years, 10 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Migration from Geronimo

by michel.strogoff

It may help anyone who face the same ces error stack, I solved this by analyzing the dependencies of the project and discovering that several Xerces jar where included in the web app (lib folder). These Xerces jar where conflicting with JBoss own shared libraries. After removing these libraries, the web app runs fine. Best regards, Eric View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238619#4238619 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238619

16 years, 10 months

1
0
0 / 0

[JBoss Messaging] - Re: 4.2.3.GA messaging service?

by PeterJ

JBossMQ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238617#4238617 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238617

16 years, 10 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: access jboss web console remotely?

by PeterJ

If port 8080 open in your firewall? Also, check the console log and verify which IP address JBoss AS is binding to - it is a few lines before the "started in xxx seconds" message: 14:26:27,755 INFO [Http11Protocol] (main) Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238616#4238616 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238616

16 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2009