[EJB3] - EAP 6.1: CMP EntityBeans locked in new Transaction
by Daniel Straub
Daniel Straub [https://community.jboss.org/people/dastraub] created the discussion
"EAP 6.1: CMP EntityBeans locked in new Transaction"
To view the discussion, visit: https://community.jboss.org/message/829611#829611
--------------------------------------------------------------
A costumer of me tries to run a EJB2.1 application on EAP 6.1 (so I don't know all the issuse or reasons, why they don't migrate the application).
They have the following scenario:
- call a statefull sessionbeans method, accessing some cmp-entitybeans (tx-attribute requires-new))
- in this method call they access a new instance of this sfb (via InitialContex.lookup/create) and call a other method, for some reasons a new transaction is requiered (tx-attribute requires-new)
- in this second method call they access the same cmp-entitybeans as in method 1, but the access is locked from the transaction of the previous method
Tthis scenario worked with JBoss 4.3, but not in EAP 6.1.
Here is the log + thread dump :
23:26:35,696 INFO org.jboss.as org.jboss.as (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started in 1900ms - Started 197 of 253 services (55 services are passive or on-demand)
...
23:27:30,337 INFO batchlayer.BatchLayerBean batchlayer.BatchLayerBean (EJB default - 2)
================ doAll in TX 0:ffffc0a8010a:5a755c78:51f04697:e
23:27:30,376 DEBUG org.jboss.as.cmp.jdbc.JDBCJBossQLQuery.StElt#findAll org.jboss.as.cmp.jdbc.JDBCJBossQLQuery.StElt#findAll (EJB default - 2) Executing SQL: SELECT t0_p.elementtype, t0_p.element, t0_p.subelementtype, t0_p.subelement, t0_p.datetype, t0_p.validfrom, t0_p.validuntil, t0_p.range, t0_p.status, t0_p.rulekey, t0_p.info FROM ST_ELT t0_p
23:27:30,392 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#elementtype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#elementtype (EJB default - 2) result: i=1, type=java.lang.String, value=M
23:27:30,392 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#element org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#element (EJB default - 2) result: i=2, type=java.lang.String, value=Merkmal1
23:27:30,392 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelementtype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelementtype (EJB default - 2) result: i=3, type=java.lang.String, value=null
23:27:30,393 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelement org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelement (EJB default - 2) result: i=4, type=java.lang.String, value=null
23:27:30,393 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#datetype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#datetype (EJB default - 2) result: i=5, type=java.lang.String, value=WIRKDAT
23:27:30,393 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validfrom org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validfrom (EJB default - 2) result: i=6, type=java.sql.Timestamp, value=1970-01-01 01:00:00.0
23:27:30,394 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validuntil org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validuntil (EJB default - 2) result: i=7, type=java.sql.Timestamp, value=1970-01-01 01:00:00.0
23:27:30,396 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#range org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#range (EJB default - 2) result: i=8, type=java.lang.Integer, value=0
23:27:30,397 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=range
23:27:30,398 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#status org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#status (EJB default - 2) result: i=9, type=java.lang.String, value=AKTIV
23:27:30,398 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=status
23:27:30,398 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#rulekey org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#rulekey (EJB default - 2) result: i=10, type=java.lang.Integer, value=100
23:27:30,398 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=rulekey
23:27:30,398 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#info org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#info (EJB default - 2) result: i=11, type=java.lang.String, value=null
23:27:30,398 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=info
23:27:30,399 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#elementtype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#elementtype (EJB default - 2) result: i=1, type=java.lang.String, value=M
23:27:30,399 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#element org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#element (EJB default - 2) result: i=2, type=java.lang.String, value=Merkmal2
23:27:30,399 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelementtype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelementtype (EJB default - 2) result: i=3, type=java.lang.String, value=null
23:27:30,399 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelement org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelement (EJB default - 2) result: i=4, type=java.lang.String, value=null
23:27:30,399 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#datetype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#datetype (EJB default - 2) result: i=5, type=java.lang.String, value=WIRKDAT
23:27:30,399 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validfrom org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validfrom (EJB default - 2) result: i=6, type=java.sql.Timestamp, value=1970-01-01 01:00:00.0
23:27:30,399 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validuntil org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validuntil (EJB default - 2) result: i=7, type=java.sql.Timestamp, value=1970-01-01 01:00:00.0
23:27:30,400 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#range org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#range (EJB default - 2) result: i=8, type=java.lang.Integer, value=0
23:27:30,400 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=range
23:27:30,400 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Overriding cached value 0 with 0. pk=daten.StEltPK@6cc4a8f0, field=range
23:27:30,400 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#status org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#status (EJB default - 2) result: i=9, type=java.lang.String, value=AKTIV
23:27:30,400 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=status
23:27:30,400 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Overriding cached value AKTIV with AKTIV . pk=daten.StEltPK@6cc4a8f0, field=status
23:27:30,400 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#rulekey org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#rulekey (EJB default - 2) result: i=10, type=java.lang.Integer, value=101
23:27:30,401 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=rulekey
23:27:30,401 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Overriding cached value 100 with 101. pk=daten.StEltPK@6cc4a8f0, field=rulekey
23:27:30,401 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#info org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#info (EJB default - 2) result: i=11, type=java.lang.String, value=null
23:27:30,401 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=info
23:27:30,401 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Overriding cached value java.lang.Object@ace10d9 with null. pk=daten.StEltPK@6cc4a8f0, field=info
23:27:30,401 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add finder results: entity=StElt results=[daten.StEltPK@6cc4a8f0, daten.StEltPK@6cc4a8f0] readahead=[JDBCReadAheadMetaData : strategy=on-find, pageSize=10, eagerLoadGroup=*, left-join[]]
23:27:30,404 TRACE org.jboss.as.cmp.jdbc.JDBCStoreManager org.jboss.as.cmp.jdbc.JDBCStoreManager (EJB default - 2) RESET PERSISTENCE CONTEXT: id=daten.StEltPK@6cc4a8f0
23:27:30,405 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) load data: entity=StElt pk=daten.StEltPK@6cc4a8f0
23:27:30,405 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Preloading data: entity=StElt pk=daten.StEltPK@6cc4a8f0 cmpField=rulekey
23:27:30,405 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Preloading data: entity=StElt pk=daten.StEltPK@6cc4a8f0 cmpField=info
23:27:30,405 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Preloading data: entity=StElt pk=daten.StEltPK@6cc4a8f0 cmpField=status
23:27:30,406 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Preloading data: entity=StElt pk=daten.StEltPK@6cc4a8f0 cmpField=range
23:27:30,407 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Trying to acquire lock: org.jboss.as.ejb3.tx.OwnableReentrantLock@43401ab6[State = 0, empty queue][Unlocked] for entity bean org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@2599c538 during invocation: org.jboss.invocation.InterceptorContext@1262f2d1
23:27:30,407 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Acquired lock: org.jboss.as.ejb3.tx.OwnableReentrantLock@43401ab6[State = 1, empty queue][Locked by 0:ffffc0a8010a:5a755c78:51f04697:e] for entity bean instance: org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@2599c538 during invocation: org.jboss.invocation.InterceptorContext@1262f2d1
23:27:30,408 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Registered tx synchronization: org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor$EntityBeanSynchronization@3026a5f8 for tx: 0:ffffc0a8010a:5a755c78:51f04697:e associated with stateful component instance: org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@2599c538
23:27:30,408 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Trying to acquire lock: org.jboss.as.ejb3.tx.OwnableReentrantLock@43401ab6[State = 1, empty queue][Locked by 0:ffffc0a8010a:5a755c78:51f04697:e] for entity bean org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@2599c538 during invocation: org.jboss.invocation.InterceptorContext@395a557a
23:27:30,408 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Acquired lock: org.jboss.as.ejb3.tx.OwnableReentrantLock@43401ab6[State = 2, empty queue][Locked by 0:ffffc0a8010a:5a755c78:51f04697:e] for entity bean instance: org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@2599c538 during invocation: org.jboss.invocation.InterceptorContext@395a557a
23:27:30,408 DEBUG org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Looking for stateful component instance with session id: {[-35, 123, -20, -115, -21, -64, 75, -109, -104, -98, 102, 94, -108, -31, 96, -72]}
23:27:30,409 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Trying to acquire lock: org.jboss.as.ejb3.tx.OwnableReentrantLock@10ef63f9[State = 0, empty queue][Unlocked] for stateful component instance: Instance of BatchLayer {{[-35, 123, -20, -115, -21, -64, 75, -109, -104, -98, 102, 94, -108, -31, 96, -72]}} during invocation: org.jboss.invocation.InterceptorContext@548c791e
23:27:30,409 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Acquired lock: org.jboss.as.ejb3.tx.OwnableReentrantLock@10ef63f9[State = 1, empty queue][Locked by 0:ffffc0a8010a:5a755c78:51f04697:17] for stateful component instance: Instance of BatchLayer {{[-35, 123, -20, -115, -21, -64, 75, -109, -104, -98, 102, 94, -108, -31, 96, -72]}} during invocation: org.jboss.invocation.InterceptorContext@548c791e
23:27:30,409 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Registered tx synchronization: org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$StatefulSessionSynchronization@5263cbef for tx: 0:ffffc0a8010a:5a755c78:51f04697:17 associated with stateful component instance: Instance of BatchLayer {{[-35, 123, -20, -115, -21, -64, 75, -109, -104, -98, 102, 94, -108, -31, 96, -72]}}
23:27:30,409 INFO batchlayer.BatchLayerBean batchlayer.BatchLayerBean (EJB default - 2)
================ next in new TX 0:ffffc0a8010a:5a755c78:51f04697:17
23:27:30,410 DEBUG org.jboss.as.cmp.jdbc.JDBCJBossQLQuery.StElt#findAll org.jboss.as.cmp.jdbc.JDBCJBossQLQuery.StElt#findAll (EJB default - 2) Executing SQL: SELECT t0_p.elementtype, t0_p.element, t0_p.subelementtype, t0_p.subelement, t0_p.datetype, t0_p.validfrom, t0_p.validuntil, t0_p.range, t0_p.status, t0_p.rulekey, t0_p.info FROM ST_ELT t0_p
23:27:30,412 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#elementtype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#elementtype (EJB default - 2) result: i=1, type=java.lang.String, value=M
23:27:30,412 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#element org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#element (EJB default - 2) result: i=2, type=java.lang.String, value=Merkmal1
23:27:30,412 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelementtype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelementtype (EJB default - 2) result: i=3, type=java.lang.String, value=null
23:27:30,412 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelement org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelement (EJB default - 2) result: i=4, type=java.lang.String, value=null
23:27:30,412 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#datetype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#datetype (EJB default - 2) result: i=5, type=java.lang.String, value=WIRKDAT
23:27:30,412 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validfrom org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validfrom (EJB default - 2) result: i=6, type=java.sql.Timestamp, value=1970-01-01 01:00:00.0
23:27:30,412 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validuntil org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validuntil (EJB default - 2) result: i=7, type=java.sql.Timestamp, value=1970-01-01 01:00:00.0
23:27:30,412 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#range org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#range (EJB default - 2) result: i=8, type=java.lang.Integer, value=0
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=range
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#status org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#status (EJB default - 2) result: i=9, type=java.lang.String, value=AKTIV
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=status
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#rulekey org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#rulekey (EJB default - 2) result: i=10, type=java.lang.Integer, value=100
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=rulekey
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#info org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#info (EJB default - 2) result: i=11, type=java.lang.String, value=null
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=info
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#elementtype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#elementtype (EJB default - 2) result: i=1, type=java.lang.String, value=M
23:27:30,413 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#element org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#element (EJB default - 2) result: i=2, type=java.lang.String, value=Merkmal2
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelementtype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelementtype (EJB default - 2) result: i=3, type=java.lang.String, value=null
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelement org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#subelement (EJB default - 2) result: i=4, type=java.lang.String, value=null
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#datetype org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#datetype (EJB default - 2) result: i=5, type=java.lang.String, value=WIRKDAT
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validfrom org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validfrom (EJB default - 2) result: i=6, type=java.sql.Timestamp, value=1970-01-01 01:00:00.0
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validuntil org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#validuntil (EJB default - 2) result: i=7, type=java.sql.Timestamp, value=1970-01-01 01:00:00.0
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#range org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#range (EJB default - 2) result: i=8, type=java.lang.Integer, value=0
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=range
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Overriding cached value 0 with 0. pk=daten.StEltPK@6cc4a8f0, field=range
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#status org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#status (EJB default - 2) result: i=9, type=java.lang.String, value=AKTIV
23:27:30,414 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=status
23:27:30,415 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Overriding cached value AKTIV with AKTIV . pk=daten.StEltPK@6cc4a8f0, field=status
23:27:30,415 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#rulekey org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#rulekey (EJB default - 2) result: i=10, type=java.lang.Integer, value=101
23:27:30,415 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=rulekey
23:27:30,415 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Overriding cached value 100 with 101. pk=daten.StEltPK@6cc4a8f0, field=rulekey
23:27:30,415 TRACE org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#info org.jboss.as.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.StElt#info (EJB default - 2) result: i=11, type=java.lang.String, value=null
23:27:30,415 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add preload data: entity=StElt pk=daten.StEltPK@6cc4a8f0 field=info
23:27:30,415 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Overriding cached value java.lang.Object@ace10d9 with null. pk=daten.StEltPK@6cc4a8f0, field=info
23:27:30,415 TRACE org.jboss.as.cmp.jdbc.ReadAheadCache.StElt org.jboss.as.cmp.jdbc.ReadAheadCache.StElt (EJB default - 2) Add finder results: entity=StElt results=[daten.StEltPK@6cc4a8f0, daten.StEltPK@6cc4a8f0] readahead=[JDBCReadAheadMetaData : strategy=on-find, pageSize=10, eagerLoadGroup=*, left-join[]]
23:27:30,416 TRACE org.jboss.as.ejb3 org.jboss.as.ejb3 (EJB default - 2) Trying to acquire lock: org.jboss.as.ejb3.tx.OwnableReentrantLock@43401ab6[State = 1, empty queue][Locked by 0:ffffc0a8010a:5a755c78:51f04697:e] for entity bean org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@2599c538 during invocation: org.jboss.invocation.InterceptorContext@5e196d07
2013-07-24 23:27:34
Full thread dump Java HotSpot(TM) 64-Bit Server VM (20.45-b01-451 mixed mode):
"EJB default - 2" prio=5 tid=7f8e12896000 nid=0x11611a000 waiting on condition https://community.jboss.org/message/829611#829611#829611/116113000 EAP 6.1: CMP EntityBeans locked in new Transaction
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <7face9498> (a org.jboss.as.ejb3.tx.OwnableReentrantLock)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:842)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1178)
at org.jboss.as.ejb3.tx.OwnableReentrantLock.lock(OwnableReentrantLock.java:86)
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanSynchronizationInterceptor.processInvocation(EntityBeanSynchronizationInterceptor.java:80)
at org.jboss.as.cmp.component.interceptors.CmpEntityBeanSynchronizationInterceptor.processInvocation(CmpEntityBeanSynchronizationInterceptor.java:67)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanAssociatingInterceptor.processInvocation(EntityBeanAssociatingInterceptor.java:79)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:226)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:317)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:214)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$2.processInvocation(EjbExceptionTransformingInterceptorFactories.java:89)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.entity.interceptors.EntityBeanPrimaryKeyInterceptor.processInvocation(EntityBeanPrimaryKeyInterceptor.java:52)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72)
at daten.StElt$$$view4.getSubelement(Unknown Source)
at batchlayer.BatchLayerBean.next(BatchLayerBean.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.jpa.interceptor.SFSBInvocationInterceptor.processInvocation(SFSBInvocationInterceptor.java:58)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:156)
- locked <7faab4428> (a java.lang.Object)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:67)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:339)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:216)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:65)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
at org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:222)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144)
at com.sun.proxy.$Proxy10.next(Unknown Source)
at batchlayer.BatchLayerBean.doAll(BatchLayerBean.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:58)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.jpa.interceptor.SFSBInvocationInterceptor.processInvocation(SFSBInvocationInterceptor.java:58)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:156)
- locked <7fa9a35f8> (a java.lang.Object)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:67)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:216)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:65)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:329)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/829611#829611]
Start a new discussion in EJB3 at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 8 months
[Snowdrop] - Accessing spring beans that are deployed in a war.
by Bas Ven
Bas Ven [https://community.jboss.org/people/batter] created the discussion
"Accessing spring beans that are deployed in a war."
To view the discussion, visit: https://community.jboss.org/message/829560#829560
--------------------------------------------------------------
We are converting a huge Spring 3 based application to eventually be a JEE application using jBoss 7.1.1.Final.
As a first step we wrapped our application inside a war file which deploys inside jboss and works well.
I am trying to see if I can inject some of the spring beans inside this jar into a simple EJB. Both the war and EJB are packaged in an ear and I moved all jars from the war to the ear lib.
My war file has the META-INF/jboss-spring.xml file:
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" " http://www.springframework.org/dtd/spring-beans.dtd http://www.springframework.org/dtd/spring-beans.dtd">
>
> <beans>
>
> <description>BeanFactory=(*Commander*)</description>
> <bean id="*dataSourceManager*" class="database.DataSourceManagerImpl" />
> </beans>
and I see in the jboss log file at startup what looks like it is being read:
> 09:01:46,210 INFO [org.jboss.spring.factory.NamedXmlApplicationContext] (MSC service thread 1-2) Refreshing org.jboss.spring.factory.NamedXmlApplicationContext@1daef240: startup date [Wed Jul 24 09:01:46 MDT 2013]; root of context hierarchy
> 09:01:46,211 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (MSC service thread 1-2) Loading XML bean definitions from "/content/assembly.ear/commander.war/META-INF/jboss-spring.xml"
> 09:01:46,217 INFO [org.springframework.beans.factory.support.DefaultListableBeanFactory] (MSC service thread 1-2) Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@330ec996: defining beans [*dataSourceManager*]; root of factory hierarchy
I try to inject this bean in my EJB as follows:
> | | @Spring(bean = "*dataSourceManager*", jndiName = "*Commander*") |
>
However when I try to call into my EJB I am getting a huge stacktrace that in the end tells me snowdrop couldn't find the 'Commander' factory:
> Caused by: java.lang.IllegalStateException: javax.naming.NameNotFoundException: *Commander* -- service jboss.naming.context.java.jboss.Commander
> at org.jboss.spring.support.SpringInjectionSupport.lookup(SpringInjectionSupport.java:180) [snowdrop-deployers.jar:2.1.0.Final]
> at org.jboss.spring.support.SpringInjectionSupport.getObjectFromBeanFactory(SpringInjectionSupport.java:136) [snowdrop-deployers.jar:2.1.0.Final]
Any ideas? Is this setup even supported or instead of wrapping our spring application inside a servlet should we 'just' make its jars avaliable and have some dummy EJB or sar start the application?
As a side note, I tried to build the sportsclub example but it can't find the jpl-util 1.0 (which is not avaliable on maven central); it also looks very outdated and I am wondering if there is a newer example distribution for snowdrop 2.x?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/829560#829560]
Start a new discussion in Snowdrop at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 8 months
[jBPM] - Accessing simple process variable for Drools rule?
by Patrick Steiner
Patrick Steiner [https://community.jboss.org/people/patste] created the discussion
"Accessing simple process variable for Drools rule?"
To view the discussion, visit: https://community.jboss.org/message/824469#824469
--------------------------------------------------------------
Hi,
I'm currently trying to learn jBPM & Drools, to be more precise, JBoss BRMS ...
Currently I'm stuck at a point where I could really need some help!
All the samples, e.g. the Car-Insurance sample from Eric Schabells Github repository do work with complex datatypes.
What I'm trying to achieve is much, much simpler - using the webbased process designer/Guvnor ...
Actually all I want is to extend Eric's brms-rewards-demo to the following:
1) add an 'amount' field to the process
2) dependent on value of the 'amount' a second approval
I have managed to extend the sample to do both, but now I would like to do the decission for 2) via a Drools rule.
Beeing a noop in this matter, I don't know how to proceed.
It would be great if someone here could point me to another sample or give me some hint on how to proceed.
I have added my "extended" version of Erics sample as an repository, just in case ...
Thanks a lot in advanced
Patrick
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/824469#824469]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 8 months
[JNDI and Naming] - javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
by jashan07
jashan07 [https://community.jboss.org/people/jashan07] created the discussion
"javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]"
To view the discussion, visit: https://community.jboss.org/message/829512#829512
--------------------------------------------------------------
Hi,
I am trying to run my application on 6.0.1 EAP and m getting the following error:
javax.naming.NoInitialContextException
Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException
I found from some forums that i have to add jbossall-client.jar file but jboss 6.0.1 doesnt contain any jar like this.
Can any one help me to get out of this problem?
my BookClient code:
*public* *class* BookClient {
*public static void* *main(String z[]) {*
*try* *{*
*int* *choice = 1;**Properties p =*
*new* *Properties();**p.put(Context.*
++*INITIAL_CONTEXT_FACTORY*++*,*
*"org.jnp.interfaces.NamingContextFactory"**);**p.put(Context.*
++*URL_PKG_PREFIXES*++*,*
*"org.jboss.naming:org.jnp.interfaces"**);**p.put(Context.*
++*PROVIDER_URL*++*, "localhost:4447"**);**InitialContext ctx =*
*new* *InitialContext(p);*
*BookHome home = (BookHome) ctx.lookup(*
*"BK"**);*
*Book bean = home.create();*
*Scanner sc =*
*new Scanner(System.+*+in+*+**);*
*while* *(choice != 2) {**String bname;*
*System.*
++*out*++*.println("Enter choice 1. Add 2. Over"**);**choice = sc.nextInt();*
*if* *(choice == 1) {**System.*
++*out*++*.println("Enter book name"**);**bname = sc.next();*
*bean.addBook(bname);*
*}*
*else if* *(choice == 2) {*
*break**;**}*
*}*
*Vector v = bean.getBooks();*
*System.*
++*out*++*.println("Size of vector \t"* *+ v.size());*
*for (int* *i = 0; i < v.size(); ++i) {**System.*
++*out*++*.println((String) v.elementAt(i));**}*
*}*
*catch* *(Exception e) {**System.*
++*out*++*.println(e);**}*
*}*
*where is the error or which jar file i need to add or modification i need to do?*
*Thanks,*
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/829512#829512]
Start a new discussion in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 8 months
[jBPM] - Any alternative for Guvnor to store process definition, process image, and task form file for JBPM 5.4. Final?
by Thomas Setiabudi
Thomas Setiabudi [https://community.jboss.org/people/thomas.setiabudi] created the discussion
"Any alternative for Guvnor to store process definition,process image, and task form file for JBPM 5.4. Final?"
To view the discussion, visit: https://community.jboss.org/message/829462#829462
--------------------------------------------------------------
Hi,
I use JBPM5.4 final
Currently I regularly run into an issue in Guvnor (Guvnor 5.5.0) as posted here https://community.jboss.org/thread/230743 https://community.jboss.org/thread/230743
I still cannot find the cause or even the solution for that. (done IRC chat with psiroky, Rikkola, and salaboy but still no clue)
So I am thinking about abandoning Guvnor at least for JBPM 5.4.
One solution that I find is to put all my process definition files, images, and task form files in a folder. Then create a component to load all these files and feed it to KnowledgeBase.
My question is, is there any other alternative solution for this?
>From an IRC chat with salaboy, It seems Guvnor has changed much in version 6 that I cannot use Guvnor 6 with JBPM 5.4 is it true?
Any help will be appreciated. Thank you
Regards,
Thomas Setiabudi
Note: I know the other alternative is to upgrade to JBPM 6 and Guvnor 6, But I still need to wait for the final version of those two.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/829462#829462]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 8 months
[JBoss Tools] - JBoss Tools 4.1 and Red Hat JBoss Developer Studio 7 go GA
by Nick Boldt
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the blog post:
"JBoss Tools 4.1 and Red Hat JBoss Developer Studio 7 go GA"
To view the blog post, visit: https://community.jboss.org/community/tools/blog/2013/07/23/jboss-tools-4...
--------------------------------------------------------------
On behalf of the JBoss Tools and Developer Studio team, I'm extremely proud to announce the general availability of the JBoss Tools 4.1.0.Final and JBoss Developer Studio 7.0.0.GA releases. https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21201/j... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-212...
Developer Studio: [ https://marketplace.eclipse.org/node/503834 Marketplace] [ http://devstudio.jboss.com/earlyaccess Download] | Tools: [ https://marketplace.eclipse.org/node/420896 Marketplace] [ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/stable/juno/ Update Site] | [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
+To Infinity and Beyond, but Mobile first!+
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exists for JBoss and related technologies in the default Eclipse distribution.
Red Hat JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes the majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuss installation.
If you are into doing your own bleeding edge Eclipse plugin assembly, JBoss Tools is for you; if you are more into having something that "Just Works" then JBoss Developer Studio is the way to go.
Installation
JBoss Developer Studio is available with a http://devstudio.jboss.com/earlyaccess one-download-installer with everything bundled and configured out of the box.
You can also install JBoss Developer Studio or JBoss Tools from Eclipse Marketplace via "Help > Eclipse Marketplace..."
When installing from Eclipse Marketplace we recommend using a fresh http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/... Eclipse 4.3 JEE Bundle since then you'll have most of the dependencies preinstalled.
Note: SOA tooling for BPEL, Drools, Guvnor, jBPM, ESB, Modeshape, pi4soa, Savara, SwitchYard & Teiid, in future referred collectively as the JBoss Tools or JBoss Developer Studio *Integration Stack (JBT-IS or JBDS-IS)*, are not yet available for this release. They will become available separately later. If you wish to use these today we recommend you continue to use JBoss Tools 3.3 or JBoss Developer Studio 5.0, or try one installing the latest +unsupported nightly build+ from this update site:
http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
h1. Performance and stability improvements
JBoss Tools 4.1.0 and JBDS 7.0 are built on top of Eclipse Kepler (e4.3), which brought noticeable performance and stability improvements over the previous Juno version (e4.2). But we also improved the performance in some of our own features (Central, JAX-RS tooling, Web Service testing).
We worked really hard to fix more than https://issues.jboss.org/issues/?jql=(project%20%3D%20JBIDE%20AND%20fixVe... 1600 bugs and feature enhancements into this release.
We have so much good stuff this time around, it's hard to cram everything into a (readable) blog post, so I'll just present the major features we have here, introduced since JBoss Tools 4.0 and JBDS 6.0. But make sure to read the complete http://docs.jboss.org/tools/whatsnew/ New and Noteworthy for a more detailed and complete overview.
TL;DR : The recurring theme of this release is "HTML5 and mobile development". https://twitter.com/burrsutter Burr Sutter made a screencast highlighting several of the new features available in this release :
h2. LiveReload
Probably the coolest new features we have, the new LiveReload server allows you to have your browser automatically refresh when you save your html, javascript and css files.You can just focus on content and functionallity and instantly see and use the changes in your browser. If it is hard to imagine how it works, Xavier Coulon (https://twitter.com/xcoulon) made a video showing how to activate and use it (on the right).
you should install a LiveReload plugin/extension into your browser as documented in our What’s New and Noteworthy (http://docs.jboss.org/tools/whatsnew/livereload/livereload-news-1.0.0.Alp...). If you can't, don't worry, keep reading.
LiveReload supports local (i.e. file:// based urls) or content served out from an application server. In the latter case, the browser will reload once the files are published on the application server, especially useful when editing JSF content like xhtml.
You can right-click on files in the Project Explorer view or on modules deployed to a server, to load your Browser with a LiveReload enabled page. This action will setup the LiveReload server for you if it does not already exist :
https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21171/o... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-211...
Our server implements the existing defacto protocol (http://feedback.livereload.com/knowledgebase/articles/86174-livereload-pr...) used by the original LiveReload (http://livereload.com/) and related plugins, meaning any browser, script and tool that works with live reload today should work with our Eclipse implementation of it.
It's really nice to have instant feedback for HTML5/JS based applications. But wait, it's getting even better :
*Proxying and Open in external Device*
http://docs.jboss.org/tools/whatsnew/images/LiveReload_open_in_web_browse... (http://docs.jboss.org/tools/whatsnew/images/LiveReload_open_in_web_browse...)
If your browser does not have the LiveReload plugin, like Safari or you're using a mobile device, you would normally manually add a livereload.js loading snippet in every web page. That can be tedious and requires changes to files you might not want to commit to your source repository. It's alright. Please meet our "LiveReload Proxying" :
It is enabled by checking "Inject the livereload.js script in HTML pages" in the LiveReload Server configuration. This allows you to proxy your file:// urls and have them served out on localhost:35729/<projectname>/<filepath> (or any other port if you choose so in the LiveReload Server configuration) .
For security reasons, remote connections are disabled by default, so if you want mobile devices to be able to load the page, just enable "Allow Remote Connections".
Now, typing a complex, long url on a mobile device can be tedious, so in order to make your life even easier, we've added a "Show In > Web Browser on External device..." menu. This will display a QR code for the LiveReload enabled url. Simply use a QR reader application and have the webpage load on your device. Watch your pages reload as you make the modifications in your IDE, it's close to black magic!
h2. HTML5/JQuery Mobile Palette
To further improve your HTML5 / mobile development experience, we’ve added a new HTML5 palette with initial support for JQuery Mobile widgets. This palette will show up when you edit HTML5 files (files with <!DOCTYPE HTML> doc type). If it does not show up, it is probably using HTML4 or XHTML content types.
The JQuery Mobile palette features a dialog preview when you click or drag one of the buttons for a component, it lets you see and customize what will be inserted :
http://docs.jboss.org/tools/whatsnew/jst/images/4.1.0.Alpha2/lf.png http://docs.jboss.org/tools/whatsnew/jst/images/4.1.0.Alpha2/lf.png http://docs.jboss.org/tools/whatsnew/jst/images/4.1.0.Beta1/set.png http://docs.jboss.org/tools/whatsnew/jst/images/4.1.0.Beta1/set.png
Alexey Kazakov r http://www.screenr.com/embed/7M57 ecorded a video to show it in action.
h2.
h2. BrowserSim goodies
BrowserSim is a mobile web browser simulator, used to test your web pages on mobile devices with a realistic mobile device skin.
Now guess what? your mobile application development experience just scored 11. In this release, we've added a bunch of really exciting features, available with a right-click on the device bezel :
* synched browsing : open the same web page in 2 different but synchronized browsers. You can test horizontal and landscape modes at the same time or view how layout behaves on different devices simultaneously.
* screenshot : easily take screenshots to share your awesome design or nasty bug you want someone to hunt down.
* debugging facilities : use Firebug Lite for easy local debugging, or debug remotely using any Weinre compatible server to debug/inspect the application running in BrowserSim.
* new skins galore
https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21173/b... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-211...
Please note BrowserSim must be launched with a 32bits JRE (you can now select it in JBossTools > BrowserSim / Cordova preferences) and Safari must be installed on your machine.
h3. Windows 64-bit Visual Page Editor
A long standing issue for our Visual Page Editor was the lack of proper Windows 64-bit XULRunner integration.
https://community.jboss.org/people/carsten.pfeiffer Carsten Pfeiffer did an awesome contribution and made this happen. If you're using Windows 64 bit, and if you follow the https://community.jboss.org/docs/DOC-10862 JBoss Tools Visual Editor FAQ link, you will be told to try to install XULRunner from http://download.jboss.org/jbosstools/builds/staging/xulrunner-1.9.2_win64... http://download.jboss.org/jbosstools/builds/staging/xulrunner-1.9.2_win64...
Hopefully you should see the following, before and after installing the proper XulRunner version :
http://docs.jboss.org/tools/whatsnew/vpe/images/4.1.0.Beta1/missing-xulru... http://docs.jboss.org/tools/whatsnew/vpe/images/4.1.0.Beta1/missing-xulru... http://docs.jboss.org/tools/whatsnew/vpe/images/4.1.0.Beta1/vpe-win64.png http://docs.jboss.org/tools/whatsnew/vpe/images/4.1.0.Beta1/vpe-win64.png
We would love to hear if this works for you on Windows 64-bit or if you still see problems.
You can give your feedback on https://issues.jboss.org/browse/JBIDE-2720 this bug
h3. Hybrid Mobile via Apache Cordova (Experimental)
If real, cross-platform Mobile application development is your thing, we now have experimental support for developing Hybrid mobile applications with Apache Cordova.
You can create an "Hybrid Mobile" project and test and develop it using the Android SDK and XCode for iOS testing.
http://docs.jboss.org/tools/whatsnew/aerogear/images/runConfigs.png http://docs.jboss.org/tools/whatsnew/aerogear/images/runConfigs.png
Note: this is only available as Experimental in JBoss Tools, not part of Developer Studio (yet)
h3. CordovaSim (Experimental)
To help testing hybrid mobile development we've extended our BrowerSim to use Ripple to provide a way to do portable testing (meaning you do not necessarily need Android or XCode installed to do development)
http://docs.jboss.org/tools/whatsnew/browsersim/images/4.1.0.Beta1/Cordov... http://docs.jboss.org/tools/whatsnew/browsersim/images/4.1.0.Beta1/Cordov...
Note: this is only available as Experimental in JBoss Tools, not part of Developer Studio (yet)
h3. Forge integration
The majority of the feedback we got for the awesome integration of Forge into Eclipse was that many preferred to use a wizard over only having access to a "command line style" UI.
We listened to you and added new wizards, to give an Eclipse front-end to the following Forge features:
* Generate Entities from existing tables
* Generate REST Endpoint from Entities
* Scaffold UI (JSF or AngularJS based) from Entities
You will find these wizards - +which are Technology Preview as of this release+ - under "File > New > JBoss Tools":
https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21190/n... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-211...
Make sure you read a detailed description of these wizard in http://docs.jboss.org/tools/whatsnew/forge/forge-news-4.1.0.Beta2.html Forge What's New. Oh and to make it all work, we now embed the Forge 1.3.3.Final runtime.
Please note these wizards are considered *Technology Preview*, thus, even though they're included, are not supported in JBoss Developer Studio.
The long term goal is to get a closer integration between Forge and Eclipse. This is a current work in progress with Forge 2, which is now available as an +experimental+ download for JBoss Tools
h3. Arquillian (Experimental)
Arquillian Eclipse is a new JBoss Tools component that makes Java EE integration testing using http://arquillian.org/ Arquillian easier. The Arquillian support can be added/removed by right-clicking the project and selecting Configure>Add/Remove Arquillian support.
The project has to be a Maven (m2e) project. The "Add Arquillian Support" action adds the Arquillian nature to the project as well as arquillian artifacts (bom, dependencies, required plugins, profiles ...) to the project's pom.xml. The Remove Arquillian Support removes the Arquillian nature, but doesn't change the project's pom.xml.
A new "Arquillian JUnit Test Case" wizard, based on the JUnit Test Case wizard, adds the following to a created class:
* @RunWith(Arquillian.class) annotation
* the deployment method
https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21181/a... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-211... https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21183/a... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-211...
Enabling Arquillian support also brings you validation, navigation across arquillian resources, launch configuration... You'll most certainly want to read a more complete overview of the Arquillian support http://docs.jboss.org/tools/whatsnew/arquillian/arquillian-news-4.1.0.Bet... here.
Note: this is only available as Experimental in JBoss Tools, not part of Developer Studio (yet)
h2.
h2. OpenShift
OpenShift Tools received a good deal of improvements, usability wise. Improved UI, more explicit labels where needed, but more importantly :
*Git output streaming*
http://docs.jboss.org/tools/whatsnew/openshift/images/publishing-to-opens... http://docs.jboss.org/tools/whatsnew/openshift/images/publishing-to-opens... Ever since we added OpenShift support to Eclipse we've had the problem that EGit did not allow streaming of console output when performing a push.
This mean that when doing a long running push Eclipse would just have a blank console and show "Push in progress".
In Kepler, EGit now includes our contribution of allowing this meaning Git users and OpenShift users can and will get streaming of the console output. You can now see what is going on.
h3. Restart OpenShift Application
http://docs.jboss.org/tools/whatsnew/openshift/images/restart-application... http://docs.jboss.org/tools/whatsnew/openshift/images/restart-application... We've added "Restart" to the UI, allowing you to trigger a node restart for your application in case something bad has happened or you changed a configuration that requires a full node restart.
*Create application from a remote repository*
Opening the advanced section of the New OpenShift Appliction wizard, you can now create an application directly seeded from a remote git repository (github for instance) instead of forcing you to use git recursive merges locally.
http://docs.jboss.org/tools/whatsnew/openshift/images/advanced-source-cod... http://docs.jboss.org/tools/whatsnew/openshift/images/advanced-source-cod...
*Configure OpenShift markers*
OpenShift is using markers to enable or disable features. These markers are hidden files added to the <project>/.openshift/markers directory. You can now add/remove/edit these markers by invoking a wizard from the OpenShift > Configure Markers... menu in th Project- or Package-Explorer.
http://docs.jboss.org/tools/whatsnew/openshift/images/configre-markers-wi... http://docs.jboss.org/tools/whatsnew/openshift/images/configre-markers-wi...
*Application creation logs*
When creating applications you want to know about the credentials that OpenShift initially set for you. This is especially helpful and required when you create a jenkins where you get its url and username/password presented. We now display what OpenShift did for you if there's anything to be noticed for any type of application and/or cartridge.
h2. JBoss Central
JBoss Central, the welcome screen of JBDS / JBoss Tools has a new design. We've tried to make it easier for you to get started building new applications, providing more samples, displaying descriptions of what each wizard gives you.
http://content.screencast.com/users/fbricon/folders/Jing/media/679e2a00-1... http://content.screencast.com/users/fbricon/folders/Jing/media/679e2a00-1...
You can also access wizards for features you haven't installed yet, such as the OpenShift Application. You'll be prompted to install the required OpenShift Tools feature if you haven't installed it already.
In the software/update tab, you'll find we have added VJet, a promising new JavaScript editor, which should help you build, you know, HTML5 and mobile applications.
h2. Servers and runtimes
*New server adapters*
* JBoss EAP 6.1, freely available to developers (you can get it from the http://www.jboss.org/jbossas/downloads http://www.jboss.org/jbossas/downloads JBoss AS download page), now has its own server adapter.
* WildFly now also has its own dedicated server adapter. Please note it's still considered experimental as WildFly itself is not stabilized to this day. We recommend using the latest Alpha-3 release, which fixes some file locking issue on windows and now support JSP development mode.
https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21191/n... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-211...
*Better server identification*
Servers derived from JBoss AS 7.x (JPP, SOA-P, GateIn), are now properly identified, making searching runtimes easier to setup. We now reuse the stacks.yml descriptor provided by the JBoss Developer Framework to provide downloads of different runtimes and thus providing a consistent experience, as part of the JBoss Way initiative.
*Better server management*
Server tools now uses the AS 7.x/EAP/WildFly management api, allowing for faster and more reliable (re)starts of servers, as well as better module management (individual module restart, status information).
*Tomcat runtime detection (JBoss Tools only)*
A new Tomcat runtime feature detection allows you to automatically detect and create tomcat-based servers, after scanning a specified server directory.
h3. Maven Integration++
*m2e 1.4.0 and m2e-wtp 1.0.0*
* JBDS comes with m2e 1.4.0 which brings some performance enhancements, as well as a very convenient Alt-F5 shortcut, to update project configuration, when it's gone out-of-synch.
* we contributed the JBoss JPA/JSF/JAX-RS configurators to the http://www.eclipse.org/m2e-wtp/ m2e-wtp project at eclipse.org, which just graduated from the Eclipse Incubator into version 1.0.0, adding support to Java EE 7.
In this Kepler release the configuration of these configurators moved under the Preferences > Maven > Java EE Integration.
*Automatic Source Lookup for the masses*
Ever tasted m2e's awesome automatic source download but were frustrated when going back to work on legacy, non-maven projects? Then rejoice, we now enable automatic source lookup for *all*, *non-maven* java projects.
The automatic Source Lookup feature is based on Maven/m2e. As such, downloaded sources will be stored under your local Maven repository.
Since JDT doesn't support variables in source attachments (such as M2_REPO), source attachments use absolute (non-portable) paths. It's ok when the jar is part of a Classpath Library, since the path is stored in your own workspace. But it can become a problem if your jar dependency is listed in your project's .classpath descriptor, potentially shared with other developers. For this reason, by default, you'll be warned when a compatible source has been found :
https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21192/a... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-211...
The good news is the source lookup mechanism is capable of fixing bad source attachements, even for Maven enabled projects. If the attached source doesn't exist (ex. you wiped out your maven local repository or shared hard-coded source attachments in your scm) or doesn't contain the right source files, it will try to download the proper source.
h3. *Maven repository edition*
Maven Repositories defined in profiles in your settings.xml (Window > Preferences > JBoss Tools > Maven Integration > Configure Maven Repositories...) can now be edited with the "Edit Repository..." button :
https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21193/e... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-5273-211...
And much more...
there's not enough room here to list all the great things the team managed to pull. Better JAX-RS tooling performance, JSF 2.2 and updated Deltaspike support, improved web service tester (now using JBoss Wise). So, again, make sure you take a look at the news and screenshots in our http://docs.jboss.org/tools/whatsnew What's New page.
h2. Giving Feedback
Please don't hesitate to use our forum to ask questions, or, if you have ideas to better improve JBoss Tools / JBDS, or found a bug, then open an issue in our https://jira.jboss.org/jira/browse/JBIDE issue tracker.
h2. What's Next ?
First, some of us are gonna take a tiny bit of rest in the coming weeks. Then we'll work on a service release, mainly focused on bug fixes, to accompany the Eclipse Kepler SR1 release in september. Hopefully, new features should see the light of day by the end of the year.
Have fun!
Fred Bricon
http://twitter.com/fbricon http://twitter.com/fbricon
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/community/tools/blog/2013/07/23/jboss-tools-4...]
12 years, 8 months