Re: [jboss-dev-forums] [Management Development] - Domain model work in AS 6.0.0
by Brian Stansberry
Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion
"Domain model work in AS 6.0.0"
To view the discussion, visit: http://community.jboss.org/message/535837#535837
--------------------------------------------------------------
Jason's http://community.jboss.org/docs/DOC-15098 requirements doc is more focused on the long term goal. But what's required for an AS 6.0 to achieve the "pros" listed above?
1. At a minimum I think we need a domain.xml schema that fully covers the single server case. This should be quite close to what we would expect to use in AS 7 and EAP 6. For later releases add elements related to multi-server use cases, perhaps some wrapper elements around the 6.0 stuff, but the guts of an AS 6 domain.xml should be recognizable in an AS 7 document.
That's really the core thing that allows most of the "pros" I listed. If we can't do that, I don't see much point.
Beyond that:
2. Persistence of changes made via admin interfaces back to the domain.xml (as opposed to just persisting them AS 5-style to the data dir and then overlaying them on top of what comes out domain.xml).
Not including 2. means an AS 6.0 domain.xml isn't really the authoritative document, it's just a centralized configuration file, helping users avoid digging through our myriad of xml. Which is a worthy goal. But not including 2. means we're not getting much of the community bake time benefit. OTOH not including 2. may somewhat reduce the "con" risk of a suboptimal design, as a lot of the design difficulties center on the persistence aspects.
3. Embedded console management interface stuff. This is really part and parcel of 2. If 2. is out-of-scope for AS 6.0 then the existing user interfaces in the embedded console are sufficient. If 2. is included, we'd need to solve the problem of how to distinguish actions that affect the domain model from those that do not.
4. Other user interfaces (CLI, REST). I don't see why this would need to be in an AS 6.0.
Bottom line: is my 1. above a sufficient goal to make this worth doing in AS 6.0? If yes then we can discuss whether it is doable.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535837#535837]
Start a new discussion in Management Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-dev-forums] [Management Development] - domain.xml work
by Brian Stansberry
Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] replied to the discussion
"domain.xml work"
To view the discussion, visit: http://community.jboss.org/message/535793#535793
--------------------------------------------------------------
In a true multi-server domain (i.e. not just a collection of servers each with the proposed first-stage standalone server domain) a new node joining should get its configuration from a "central point"; whatever it has locally on disk when it first starts should be replaced. In Westford we discussed that any of the running servers in the domain whose profile has the required capability could act as that "central point", with an HASingleton-like mechanism used to determine which node is currently taking on that role.
The node joining the domain would need to know enough to contact the domain to get its config; such info would presumably be provided via the command line (or perhaps a simple properties file). I envision that working somewhat like HA-JNDI does now; the client is (optionally) provided a set of well-known URLs to contact, (optionally) falling back to multicast discovery.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535793#535793]
Start a new discussion in Management Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[JBoss Transactions Development] - EJB3.0 transaction not active Realy strange!!!
by dimitar dimitar
dimitar dimitar [http://community.jboss.org/people/dimitarn] created the discussion
"EJB3.0 transaction not active Realy strange!!!"
To view the discussion, visit: http://community.jboss.org/message/535788#535788
--------------------------------------------------------------
http://community.jboss.org/message/535788#535788/JDBCExceptionReporter http://community.jboss.org/message/535788#535788/JDBCExceptionReporter SQL Error: 0, SQLState: null15:44:29,962 ERROR http://community.jboss.org/message/535788#535788/JDBCExceptionReporter http://community.jboss.org/message/535788#535788/JDBCExceptionReporter Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000001:c779:4bbb2b0e:505b status: ActionStatus.ABORT_ONLY >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000001:c779:4bbb2b0e:505b status: ActionStatus.ABORT_ONLY >)15:44:29,967 ERROR http://community.jboss.org/message/535788#535788/TxPolicy http://community.jboss.org/message/535788#535788/TxPolicy javax.ejb.EJBTransactionRolledbackException: org.hibernate.exception.GenericJDBCException: Cannot open connection15:44:29,970 ERROR http://community.jboss.org/message/535788#535788/PositionsManagementBean http://community.jboss.org/message/535788#535788/PositionsManagementBean PositionsManagementIntr::onMessage()::The exception type is: javax.ejb.EJBTransactionRolledbackException15:44:29,970 ERROR http://community.jboss.org/message/535788#535788/PositionsManagementBean http://community.jboss.org/message/535788#535788/PositionsManagementBean PositionsManagementIntr::onMessage()::The exception is:::org.hibernate.exception.GenericJDBCException: Cannot open connection15:44:29,970 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR javax.ejb.EJBTransactionRolledbackException: org.hibernate.exception.GenericJDBCException: Cannot open connection15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:115)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)15:44:29,971 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at $Proxy731.method5(Unknown Source)
15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at MyBean.method4(MyBean.java:337)15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at MyBean.method3(MyBean.java:324)
15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at MyBean.method2(MyBean.java:132)
15:44:29,972 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...............
at $Proxy851.onMessage(Unknown Source)15:44:29,978 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at ManagementBean.onMessage(PositionsQueueManager.java:59)
15:44:29,978 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:229)15:44:29,978 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:1043)15:44:29,978 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at org.jboss.messaging.util.OrderedExecutorFactory$ChildExecutor.run(OrderedExecutorFactory.java:120)15:44:29,979 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)15:44:29,979 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)15:44:29,979 ERROR http://community.jboss.org/message/535788#535788/STDERR http://community.jboss.org/message/535788#535788/STDERR at java.lang.Thread.run(Thread.java:619)
@Stateful
@CacheConfig(idleTimeoutSeconds = 3600)
public class ManagementBean implements IManagementLocal {
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public void onMessage(final javax.jms.Message msg) {
method1(msg);
}
private void method1(msg) {
for(...) {
processBean.method2(...); //statless bean call
}
}
}
@Statless
public class ProcessBean {
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public void method2(...) {
if(...) {
method3(..);
} else {
try {
method4(...);
} catch(Exception e) {
method3(...);
}
}
}
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
private void method3(...) {
otherStatlesBean.method5(); //This is with the default trans atributte required
}
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
private void method4(...) {
}
}
I cannot understand WHY it is complaining with transaction not active
In method2 if method4 fails(it is executed in new separate tarnsaction) i catch the excepton and call method3 which calls statless bean method and there it complains that the transaction is not active, How can a just created new transaction in the caller bean be not active???
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535788#535788]
Start a new discussion in JBoss Transactions Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years