February 2009 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Maven release - How is the parent version updated?

by jaikiran

While working on an (unrelated) issue, i noticed that the pom.xml of jboss-ejb3-embedded still has version 1.0.0-Beta9 for the parent jboss-ejb3-build https://svn.jboss.org/repos/jbossas/projects/ejb3/trunk/embedded/pom.xml. I was under the impression that, after our last 1.0.0 release all the components were now having a 1.0.0 jboss-ejb3-build parent. Infact, i see that most of them do have this parent (ex: jboss-ejb3-common https://svn.jboss.org/repos/jbossas/projects/ejb3/trunk/common/pom.xml) except embedded. Just curious - is this version increment done by Maven or is it done manually during release? I went through this Maven release process wiki http://jboss.org/community/docs/DOC-11372 which says that the version increment is done by the release plugin, but it isn't clear enough about which version is incremented (the pom itself or its parent reference). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206997#4206997 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206997

15 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Strange classloading behavior -- thread stuck

by adrian＠jboss.org

"bstansberry(a)jboss.com" wrote : I was able to induce the classloading loop quite easily using JDK 6 (u12) a stock 5.0.0.GA. But with the 2.0.3-SNAPSHOT libraries I've been trying for over half an hour without success. | | So, something you did helped. :-) | | More mysterious is exactly what caused the problem. I have logs from a server that failed and grepped for "Circular" or "LinkageError" and saw nothing. The logs are quite complex so it would probably take hours of detail analysis to get anything out of them. I attached them to JBCL-81 just so they are archived somewhere in case they prove useful. | I've been examing your log and I think I understand another way this can happen. My fix is also correct in that case as well, which is why it helped. Its failry complicated so bare with me (I'll try and simplify it to the bare minimum :-). Step 1 Thread1: gets a lock on ClassLoader A to do a normal classloading request on ClassA Step 2 Thread1: to load ClassA it also needs to load ClassB from ClassLoader B Thread1: aquires the lock - but hasn't scheduled the task yet Step 3 Thread2: wants to load ClassC from ClassLoaderA and schedules against Thread1 to do that since it owns the lock Step 4 Thread1: schedules the load ClassB, but it is behind ClassC Step 5 Thread1: does the load on ClassC but this requires to load ClassD from ClassLoaderA (note Thread1 is now the requestingThread even the requestingThread for the inital load of ClassC - this is the importan part) Step 6 Thread1: Schedules the load of ClassD Step 7 Thread1: does the load of ClassB and then tries to reassign the tasks. But there is still the load of ClassD for the same thread in the list from step (5) So it loops trying to reassign to itself. As I noted in step (5) the case I'd missed when trying to determine how it could happen is when you get a recursive classloading request. Although the load of ClassC belongs to Thread2, its knock on effect to load ClassD actually belongs to Thread1 So the ClassCircularity bug is not required to reproduce the problem, just this "jumping the queue" or more correctly, interleaving of recursive requests that get executed on the same thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206995#4206995 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206995

15 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - JPA deployers in jboss-ejb3-embedded

by jaikiran

jboss-ejb3-embedded uses its own copy of jpa-deployers-beans.xml: | <?xml version="1.0" encoding="UTF-8"?> | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | <bean name="DataSourceDependencyResolver" class="org.jboss.ejb3.embedded.resolvers.EmbeddedDataSourceDependencyResolver"/> | | <bean name="JavaEEModuleInformer" class="org.jboss.ejb3.embedded.javaee.SimpleJavaEEModuleInformer"/> | | <bean name="PersistenceUnitDependencyResolver" class="org.jboss.jpa.resolvers.DefaultPersistenceUnitDependencyResolver"/> | | <bean name="PersistenceParsingDeployer" class="org.jboss.jpa.deployers.PersistenceParsingDeployer"/> | | <bean name="PersistenceDeployer" class="org.jboss.jpa.deployers.PersistenceDeployer"/> | <bean name="PersistenceUnitDeployer" class="org.jboss.jpa.deployers.PersistenceUnitDeployer"> | <property name="defaultPersistenceProperties"> | <map keyClass="java.lang.String" valueClass="java.lang.String"> | <entry> | <key>hibernate.transaction.manager_lookup_class</key> | <value>org.hibernate.transaction.JBossTransactionManagerLookup</value> | </entry> | </map> | </property> | </bean> | </deployment> While working on https://jira.jboss.org/jira/browse/EJBTHREE-1716 i had to upgrade the version of jboss-ejb3-core to 1.0.0 in the pom.xml dependency of embedded. This version of ejb3-core expects the PersistenceUnitDependencyResolver to have a search strategy and has various different impls. The ejb3-core by default uses: | <bean name="PersistenceUnitDependencyResolver" class="org.jboss.jpa.resolvers.DynamicPersistenceUnitDependencyResolver"/> Which one do we want to use in the ejb3-embedded? Right now i have let it remain at DefaultPersistenceUnitDependencyResolver with a SpecCompliantSearchStrategy: <bean name="SpecCompliantSearchStrategy" class="org.jboss.jpa.resolvers.strategy.SpecCompliantSearchStrategy"/> | |  | <bean name="PersistenceUnitDependencyResolver" class="org.jboss.jpa.resolvers.DefaultPersistenceUnitDependencyResolver"/> | Is this OK? Or should ejb3-embedded too use the dynamic resolver? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206994#4206994 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206994

15 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Strange classloading behavior -- thread stuck

by bstansberry＠jboss.com

No problem. :-) The ClassLoadingTask log category had I typo: protected static Logger log = Logger.getLogger("org.jboss.detailed.classloader.ClassLoadinTask"); Missing "g" in "Loading". I just fixed that, r83853. To which I just a just realized I didn't add a commit message. :( Better get some coffee. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206989#4206989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206989

15 years, 4 months

1
0
0 / 0

[Design of JBoss Identity] - Re: comments on IDM 1.0-alpha1.

by jeff.yuchang

OK, here goes those two jiras: https://jira.jboss.org/jira/browse/JBID-45, https://jira.jboss.org/jira/browse/JBID-46 Thanks Jeff View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206986#4206986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206986

15 years, 4 months

1
0
0 / 0

[Design of JBoss Identity] - Re: comments on IDM 1.0-alpha1.

by anil.saldhana＠jboss.com

We should have a general discussion on dependencies and also inform whenever we are getting new dependencies. I think many of the dependencies exist in the JDK (JAXB etc) or provided by the EE environment. Anything else, should be discussed. Dependencies are interesting as well as critical topic. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206985#4206985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206985

15 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: caching xa resource on the client side.

by ataylor

actually on further investigation start(..) needs to be blocking as we have to check for XAException.XAER_DUPID. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206980#4206980 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206980

15 years, 4 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Remoting 2: Timeout waiting on socket for InvokerLocator

by sentcs

Hi, I am also getting same problem for jboss-4.2.3.GA-jdk6 with jboss-messaging-1.4.0.SP3 envirnment. As per your suggestion, I have added one more attribute as 'connectionwait' into remoting-bisocket-service.xml. Here i have a query as 'how to increase the number of connections' since you said that connection default is 50. And i want know, any impact if i am going to change the number of connection. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206967#4206967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206967

15 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBoss 5.0.0.GA: jboss.entity.manager.factory.jndi.name w

by matt10

All matters discussed on this post are addressed by the following JIRAs: https://jira.jboss.org/jira/browse/JBJPA-6 https://jira.jboss.org/jira/browse/JBJPA-7 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206957#4206957 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206957

15 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Chasing illegal URL

by alesj

"ctomc" wrote : Which version of seam and facelets are you using? Dunno. :-) The one that comes with 5_0 branch. Anyway ... - http://lists.jboss.org/pipermail/jboss-development/2009-February/013456.html But thanks for the help. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206956#4206956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206956

15 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2009