[Beginners Corner] - Migrating from 4.0.5 to 4.2.1 problems
by xpern
Hi! Optimistically I tried deploying my current application that?s running nicely in JBoss 4.0.5 on the later version 4.2.1
First off, I?d like to mention that JBoss starts nicely if I don?t add any application. ;)
I have two problems, who might be the same;
Fist one, how do I get rid of
url=file:/C:/jboss-4.2.1.GA/server/default/conf/login-config.xml
2007-09-11 17:01:46,937 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Failed to load config as XML
org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser
at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100)
at org.jboss.security.auth.login.XMLLoginConfigImpl.loadXMLConfig(XMLLoginConfigImpl.java:320)
at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:288)
at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:268)
I?ve seen the suggestion here in the faq that I should add the endorsed directory in the startup parameters but there was no difference at all for me.
(Something similar to ?Djava.endoresed.lib=c:\jboss421\lib\endorsed couldn?t find the exact command now)
Please help, how do I get rid of this problem!
-----
Second problem is perhaps related to the first one: JBoss cant find my datasource anymore: (Name of my datasource is ProfilerDS)
file:/C:/jboss-4.2.1.GA/server/default/conf/standardjbosscmp-jdbc.xml
2007-09-11 17:02:00,328 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.Absence] jar:file:/C:/jboss-4.2.1.GA/server/default/tmp/deploy/tmp5829profiler.ear-contents/profiler.jar!/META-INF/jbosscmp-jdbc.xml found. Overriding defaults
2007-09-11 17:02:00,500 DEBUG [org.jboss.ejb.EjbModule] Starting failed jboss.j2ee:service=EjbModule,module=profiler.jar
org.jboss.deployment.DeploymentException: Error: can't find data source: java:/ProfilerDS; - nested throwable: (javax.naming.NameNotFoundException: ProfilerDS not bound)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.init(JDBCEntityBridge.java:153)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:435)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:368)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172)
Thank you for your time!
/Per
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083076#4083076
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083076
18 years, 7 months
[JBoss Seam] - Re: EntityQuery bug
by rmemoria
Hi all,
I've been debugging the SEAM source code and I found a solution I would like to share with you. It requires modification in the SEAM source code, but it fix the bug in EntityQuery.
in org.jboss.seam.framework.Query:
include this new method:
protected String getCountEjbqlWithRestrictions() {
| String hql = getCountEjbql();
|
| StringBuilder builder = new StringBuilder().append(hql);
|
| for (int i = 0; i < getRestrictions().size(); i++) {
| Object parameterValue = getRestrictionParameters().get(i)
| .getValue();
| if (isRestrictionParameterSet(parameterValue)) {
| if (WHERE_PATTERN.matcher(builder).find()) {
| builder.append(" and ");
| } else {
| builder.append(" where ");
| }
| builder.append(parsedRestrictions.get(i));
| }
| }
| return builder.toString();
| }
in org.jboss.seam.framework.EntityQuery:
in method createCountQuery() (around line 167), change the line
javax.persistence.Query query = getEntityManager().createQuery( getCountEjbql() );
to this
javax.persistence.Query query = getEntityManager().createQuery( getCountEjbqlWithRestrictions() );
It would be nice if it were permanently implemented in the SEAM source code (or something similar to fix the present problem).
Regards,
Ricardo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083075#4083075
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083075
18 years, 7 months
[JBossCache] - What is the relation between in-memory nodes and nodes in db
by sg283
I have configured one of my cache region ( called fare) as below:-
maxNodes = 4500
timeToLiveSeconds = 2073600
I have defined maxNodes in this region to be 4500.I am persisting cache in db using cache loader.
In my application I am keeping data only on the leaf nodes.
When I query my db for nodes with data, that number is very big than 4500. Currently, number of leaf nodes (with data) is 5672. This is the count only for leaf nodes. Actual number of nodes would be even more.
As per my understanding, number of nodes in any region should not exceed the maxNodes. But I see different thing here.
What is the relation between in-memory nodes and nodes in db? Does JBoss Cache maintains maxNodes in memory and if the number exceeds beyond this, it keeps all other nodes in db? So at a given point of time if there are 4500 nodes are there in memory, and the application tries to put 1000 more nodes in the same region, would these nodes be put in db. SO there would be 4500+1000 = 5500 nodes in db and only 4500 nodes in memory?
Also I have a default cache region with 5000 maxNodes configured.
May this happen, if in number of nodes in any of my cache region exceeds the maxNodes, any new node would be put in the _default_ region?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083061#4083061
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083061
18 years, 7 months