[JBoss AOP] - aop and eclipse rcp
by favez
Hi,
I'need to use jboss aop with eclipse rcp. I need to have an jboss-aop.xml file per plug-in and I need dynamic load-time.
Each plugin having is own classloader, I need to be able to load aspect(s) during application execution (for exemple, create a plug-in with an jboss aop extension point and each plug-in that need to use jboss-aop extends this extension point. That will allow the "jboss aop" plugin to control get the class loader of each plug-in extending jboss-aop.)
So I need to load dynamicly the class loader, to be able to modifiy byte code during application.
I see that calling AspectManager.instance() ; load the aspect definition found in file "Meta-Inf/jboss-aop.xml.
Now I need to load in bytecode de modification.
How can I do that in my java code ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969655#3969655
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969655
19 years, 7 months
[JBoss jBPM] - Re: jbpm.war with jboss-4.0.4.GA - How to... Pleae help ???
by bertrand.njiipwo
Sorry hier the error trace from JBoss.
anonymous wrote : 09:40:53,307 INFO [NamingHelper] JNDI InitialContext properties:{}
| 09:40:53,337 INFO [DatasourceConnectionProvider] Using datasource: java:/jbpmBpelDS
| 09:40:53,457 INFO [SettingsFactory] RDBMS: MySQL, version: 4.1.9-nt
| 09:40:53,467 INFO [SettingsFactory] JDBC driver: MySQL-AB JDBC Driver, version: mysql-connector-java-3.1.12 ( $Date: 2005-11-17 15:53:48 +0100 (Thu, 17 Nov 2005) $, $Revision$ )
| 09:40:53,577 INFO [Dialect] Using dialect: org.hibernate.dialect.MySQLInnoDBDialect
| 09:40:53,637 INFO [TransactionFactoryFactory] Using default transaction strategy (direct JDBC transactions)
| 09:40:53,677 INFO [TransactionManagerLookupFactory] No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)
| 09:40:53,698 INFO [SettingsFactory] Automatic flush during beforeCompletion():disabled
| 09:40:53,718 INFO [SettingsFactory] Automatic session close at end of transaction: disabled
| 09:40:53,738 INFO [SettingsFactory] JDBC batch size: 15
| 09:40:53,748 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled
| 09:40:53,798 INFO [SettingsFactory] Scrollable result sets: enabled
| 09:40:53,808 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): enabled
| 09:40:53,818 INFO [SettingsFactory] Connection release mode: auto
| 09:40:53,828 INFO [SettingsFactory] Maximum outer join fetch depth: 2
| 09:40:53,838 INFO [SettingsFactory] Default batch fetch size: 1
| 09:40:53,848 INFO [SettingsFactory] Generate SQL with comments: disabled
| 09:40:53,858 INFO [SettingsFactory] Order SQL updates by primary key: disabled
| 09:40:53,868 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
| 09:40:53,908 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
| 09:40:53,908 INFO [SettingsFactory] Query language substitutions: {}
| 09:40:53,968 INFO [SettingsFactory] Second-level cache: enabled
| 09:40:53,978 INFO [SettingsFactory] Query cache: disabled
| 09:40:53,988 INFO [SettingsFactory] Cache provider: org.hibernate.cache.EhCacheProvider
| 09:40:54,028 INFO [SettingsFactory] Optimize cache for minimal puts: disabled
| 09:40:54,038 INFO [SettingsFactory] Structured second-level cache entries: disabled
| 09:40:54,118 INFO [SettingsFactory] Statistics: disabled
| 09:40:54,128 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled
| 09:40:54,148 INFO [SettingsFactory] Default entity-mode: pojo
| 09:40:54,449 INFO [SessionFactoryImpl] building session factory
| 09:40:54,479 ERROR [[DeployServlet]] Servlet.service() for servlet DeployServlet threw exception
| java.lang.IllegalAccessError: tried to access method net.sf.ehcache.CacheManager.()V from class org.hibernate.cache.EhCacheProvider
| at org.hibernate.cache.EhCacheProvider.start(EhCacheProvider.java:124)
| at org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:180)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1213)
| at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:90)
| at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:74)
| at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:79)
| at org.jbpm.persistence.db.DbPersistenceService.getGraphSession(DbPersistenceService.java:216)
| at org.jbpm.JbpmContext.getGraphSession(JbpmContext.java:433)
| at org.jbpm.JbpmContext.deployProcessDefinition(JbpmContext.java:172)
| at org.jbpm.bpel.web.deploy.DeployServlet.doGet(DeployServlet.java:55)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969652#3969652
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969652
19 years, 7 months
[JBoss Messaging] - Re: Queue configuration
by thebreeze
Good to see this is getting attention :)
I appreciate that clustering is important - in fact I have couple of customers who are waiting for it. However, for them the DLQ is an absolute "must have". Without the DLQ we cannot have MDBs processing a queue, even in a single node environment.
The situtation for the customer I'm working with that started this thread is that we would accept two standalone messaging servers rather than a clustered pair for our availability requirements - so long as we had a DLQ ...
I guess this is a round about way of saying that for us a DLQ is higher priority than clustering.
Unfortunately I am currently working flat out on a couple of projects so my ability to contribute towards making it happen is severly limited (quite happy to run our tests again if anyone does make progress on the DQL ;)
Cheers,
Andy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969649#3969649
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969649
19 years, 7 months
[EJB 3.0] - Re: Problem calling SLSBs from isolated EARs
by ferenc.hechler
The behaviour for CallByValue is described in
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
as:
Call By Value
1. caller does ejb.someMethod()
2. invocation is marshalled - the parameters are turned into ObjectStream? (a byte[])
3. container with a different classloader unmarshalls - byte[] -> java Objects - including classloading
4. invocation is passed through ejb container
5. container does bean.someMethod()
6. result is marshalled - the return value is turned into ObjectStream?
7. result is unmarshalled using the caller's classloader - byte[] -> java Object
8. result is return to the caller
If a call "proxy.f(myType)" is done via Call By Value in step 2. the parameter myType should be serialized.
I modified MyType to debug de-/serialization:
public class MyType implements Serializable {
| public String str;
| private void writeObject(ObjectOutputStream out) throws IOException
| {
| // debug
| out.defaultWriteObject();
| }
|
| private void readObject(ObjectInputStream in) throws IOException, ClassNotFoundException
| {
| in.defaultReadObject();
| // debug
| }
| }
If a call via remote interface is made from a client-java-app the writeObject() and readObject() methods get called.
If a call is made from inside a SLSB (local interface) neither method gets called.
So the step 2. (marshall parameters) is missing.
Did I miss something in the configurations?
conf/jboss-service.xml:
...
| <mbean code="org.jboss.naming.NamingService" name="jboss:service=Naming" xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
| <attribute name="CallByValue">true</attribute>
| <attribute name="Port">1099</attribute>
| <attribute name="BindAddress">${jboss.bind.address}</attribute>
| <attribute name="RmiPort">1098</attribute>
| <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
| <depends optional-attribute-name="LookupPool" proxy-type="attribute">jboss.system:service=ThreadPool</depends>
| </mbean>
| ...
deploy/ear-deployer.xml:
<server>
| <mbean code="org.jboss.deployment.EARDeployer" name="jboss.j2ee:service=EARDeployer">
| <attribute name="Isolated">true</attribute>
| <attribute name="CallByValue">true</attribute>
| </mbean>
| </server>
EAR1: META-INF/jboss-app.xml:
<jboss-app>
| <loader-repository>mydomain:loader=mycomponent1</loader-repository>
| </jboss-app>
EAR2: META-INF/jboss-app.xml:
<jboss-app>
| <loader-repository>mydomain:loader=mycomponent2</loader-repository>
| </jboss-app>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3969648#3969648
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3969648
19 years, 7 months