[JBoss Microcontainer Development POJO Server] New message: "Re: Classloader VFS3 Integration"
by Ales Justin
User development,
A new message was posted in the thread "Classloader VFS3 Integration":
http://community.jboss.org/message/521706#521706
Author : Ales Justin
Profile : http://community.jboss.org/people/alesj
Message:
--------------------------------------------------------------
> I guess I don't see any reason it has to be just jboss-cl. The problem is there are a lot of VFS dependent projects and it is becoming a difficult to manage all the branches, so I was trying to see if there was a way we could chip away at getting them on the trunk as the projects we more and more stable with the VFS3 integration and an based on dependency order, jboss-cl was the next likely candidate.
I think we should just set a reasonable date when we're gonna change them all at once.
We give devs time till then - properly warn/promote this date.
Then branch previous stuff to right branch versions, and move VFS3 stuff to respected trunks.
Wrt jboss-cl, I know Adrian is currently working on some OSGi support, so might not be the best time to "sweep the rug under his feet". :-)
> Below is a list of all the dependent projects that are used by AS. There may even be a few more that I haven't come across. Feel free to add any additional you can think of.
>
> http://community.jboss.org/docs/DOC-14634
I don't see Seam-int there:
* http://anonsvn.jboss.org/repos/jbossas/projects/jboss-seam-int/trunk/
Although we need to check how much of VFS usage should be there once you move to VFS3.
It might be that we won't need it anymore -- due to more standard URL, paths, ...
I'll think about it if there are some others we missed.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521706#521706
16 years, 3 months
[jBPM] New message: "jBPM 4.3 - Will cause memory leaks due to unclosed InitialContext()"
by Martin Porter
User development,
A new message was posted in the thread "jBPM 4.3 - Will cause memory leaks due to unclosed InitialContext()":
http://community.jboss.org/message/521698#521698
Author : Martin Porter
Profile : http://community.jboss.org/people/jedizippy
Message:
--------------------------------------------------------------
Hi,
Further to my previous post regarding JTA transactions and upon my concern at finding an unclosed InitialContext I did a search through the jBPM source code and to my amazement I found that this is in fact commonplace. And this same issue can be found throughout the entire code base !!!!!!! Am I really looking at the right code here ?????. Its the 4.3 source code !.
The following classes have this issue:-
org.jboss.bpm.console.server.util.InvocationProxy
org.jbpm.jpdl.internal.activity.JavaActivity
org.jbpm.jpdl.internal.activity.JmsActivity
org.jbpm.pvm.internal.cfg.ConfigurationImpl
org.jbpm.pvm.internal.processengine.ProcessEngineImpl
org.jbpm.pvm.internal.tx.JtaTransaction
org.jbpm.pvm.internal.wire.descriptor.JbossIdmIdentitySessionFactoryDescriptor
org.jbpm.pvm.internal.wire.descriptor.JndiDescriptor
This means that the current distribution of 4.3 could simply not be used in a real production scenario due to memory leaks. I have will raise a JIRA for this issue !
If someone gives me access to the source code I can make the appropriate changes but I am very concerned at this. I have not worked with JBoss but as far as I know it wont close connections for you !!.
Regards
Martin
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521698#521698
16 years, 3 months
[jBPM] New message: "jBPM 4.3 - Which JTA config to use for non-JBoss platform."
by Martin Porter
User development,
A new message was posted in the thread "jBPM 4.3 - Which JTA config to use for non-JBoss platform.":
http://community.jboss.org/message/521690#521690
Author : Martin Porter
Profile : http://community.jboss.org/people/jedizippy
Message:
--------------------------------------------------------------
Hi,
Whilst investigating an issue (and during an upgrade process) to 4.3 running on WLS I have attempted to include the jbpm JTA configuration in our jbpm.cfg.xml as follows (as per a recent update to the docs):-
<import resource="jbpm.tx.jta.cfg.xml"/>
This immediately failed during the engine initialization as the TransactionManager and the UserTransaction are not found in JNDI. Upon inspection of the code it is immediately apparent given the first two lines of code in:-
org.jbpm.pvm.internal.tx.JtaTransaction
The offending lines of code:-
public static final String JNDINAME_USERTRANSACTION_JBOSS_GLOBAL = "UserTransaction";
public static final String JNDINAME_TRANSACTIONMANAGER_JBOSS_GLOBAL = "java:/TransactionManager";
Hence this will of course not work on another other server than JBoss. These settings should come from my jbpm.hibernate.cfg.xml where the following properties should be used:-
<property name=+"hibernate.transaction.factory_class"+>org.hibernate.transaction.JTATransactionFactory</property>
<property name=+"hibernate.transaction.manager_lookup_class"+>org.hibernate.transaction.WeblogicTransactionManagerLookup</property>
<property name=+"jta.UserTransaction"+>java:comp/UserTransaction</property>
<property name=+"jndi.class"+>weblogic.jndi.WLInitialContextFactory</property>
So is it my confusion. Should this <import resource="*jbpm.tx.jta.cfg.xml"*/> be used only in JBoss platform and on other platforms the default hibernate configuration used <import resource="*jbpm.tx.hibernate.cfg.xml*"/>. .Or is it a bug in the code ?.
In addition I am more concerned by the following line of code in the actual method that gets the context from JNDI:-
public static Object lookupFromJndi(String jndiName) {
try {
InitialContext initialContext = new InitialContext();
return initialContext.lookup(jndiName);
} catch (Exception e) {
throw new JbpmException("couldn't lookup '"+jndiName+"' from jndi: "+e.getMessage()+": "+e.getMessage(), e);
}
}
This will of course result in memory leaks and eventual file descriptor issues as the InitialContext is not closed.
Regards
Martin
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521690#521690
16 years, 3 months
[JNDI and Naming] New message: "Re: Name lookup fails, reason unknown"
by Timothy Mowlem
User development,
A new message was posted in the thread "Name lookup fails, reason unknown":
http://community.jboss.org/message/521689#521689
Author : Timothy Mowlem
Profile : http://community.jboss.org/people/jvm
Message:
--------------------------------------------------------------
Just to note that the stack trace was: [I have hidden real app name for client confidentiality]
Connecting to server jnp://localhost:1099
2010-01-22 11:04:26,573 DEBUG ContextFactory:41 - Connecting to jnp://localhost:1099
2010-01-22 11:04:26,577 DEBUG BeanFinder:49 - Starting bean lookup
2010-01-22 11:04:26,800 ERROR BeanFinder:65 - Context factory - looking for myapp/MyAppFacade/remote
javax.naming.NameNotFoundException: myapp not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
The EAR file was named myapp.ear
The bean was deployed in beans.jar inside the EAR
No ejb-jar.xml
No JBoss specific xml files were present
application.xml contains:
<display-name>MyApp</display-name>
<module>
<ejb>beans.jar</ejb>
</module>
<module>
<web>
<web-uri>web.war</web-uri>
<context-root>myapp</context-root>
</web>
</module>
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521689#521689
16 years, 3 months