Re: [jboss-dev-forums] [JBoss AS7 Development] - Data Source Configuration in AS 7
by Armen Arzumanyan
Armen Arzumanyan [http://community.jboss.org/people/armdev] commented on the document
"Data Source Configuration in AS 7"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-16657#comment-8203
--------------------------------------------------
Hi Alli, how can we call datasource from percictance-unit??
If my DS name is newsportal under glassfish I just write newsportl in the p.unit.
<persistence-unit name="jmagazinePU" transaction-type="JTA">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>newsportal</jta-data-source>
<exclude-unlisted-classes>false</exclude-unlisted-classes>
<properties>
<property name="hibernate.connection.useUnicode" value="true"/>
<property name="hibernate.connection.characterEncoding" value="UTF-8"/>
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
<property name="hibernate.hbm2ddl.auto" value="none"/>
</properties>
</persistence-unit>
Also Where we can copy-paste mysql jdbc driver? Stiil I can not configure DS under JBoss7 and use it with p.unit.
Thanks
--------------------------------------------------
12 years, 5 months
[JBoss AS7 Development] - Logging Id's
by Brian Stansberry
Brian Stansberry [http://community.jboss.org/people/brian.stansberry] modified the document:
"Logging Id's"
To view the document, visit: http://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | C |
| *10700 - 10799* | *CMP* |
|
| *10900 - 10999* | *Domain Controller* |
|
| *11000 - 11099* | *EE* | C |
| *11100 - 11199* | *Embedded* | C |
| *11200 - 11299* | *JAXRS* | C |
| *11300 - 11399* | *JMX* | C |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi (as plugin 00-10; service 11-99)* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *13100 - 13199* | *Security* |
|
| *14100 - 14399* | *Ejb3* | I |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
|
| *EE Deployment* |
|
|
| *Host Controller* |
|
|
| *Jacorb* |
|
|
| *JAXR* |
|
|
| *JDR* |
|
| *15400-15499* | *Mail* |
|
|
| *Platform MBean* |
|
|
| *POJO* |
|
|
| *Remoting* |
|
|
| *SAR* |
|
|
| *Security* |
|
|
| *Server* |
|
|
| *Threads* |
|
|
| *Web* |
|
|
| *Web Services* |
|
|
| *Weld* |
|
|
| *Xts* |
|
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
12 years, 5 months
Re: [jboss-dev-forums] [JBoss AS7 Development] - Infinispan Subsystem Management API
by Brian Stansberry
Brian Stansberry [http://community.jboss.org/people/brian.stansberry] commented on the document
"Infinispan Subsystem Management API"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-17351#comment-8198
--------------------------------------------------
Re: "To handle these situations, the management API provides an attribute "restart-required" for operations which can affect the runtime state and will initiate the appropriate restart actions"
To clarify a bit, if an operation is has "all-services" or "jvm" as it's restart-required value, the handler for the operation *should not* trigger a restart. The OperationContext exposes reloadRequired() and restartRequired() methods -- those should be invoked. They mark the server as needing restart. It is up to the user to take action, when they deem appropriate, to effect that restart.
Re: using "resource-services" as the restart-required value and then having the operation handler restart the services: be cautious about doing that. Restarting a service has the effect of restarting any services that depend on that service. That can quickly broaden out to include a restart of a large number of things that the user may not anticipate. Understand that by supporting this you may be giving your users a gun they can shoot themselves with.
--------------------------------------------------
12 years, 5 months
[JBoss AS7 Development] - Logging Id's
by James Perkins
James Perkins [http://community.jboss.org/people/jamezp] modified the document:
"Logging Id's"
To view the document, visit: http://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | C |
| *10700 - 10799* | *CMP* |
|
| *10900 - 10999* | *Domain Controller* |
|
| *11000 - 11099* | *EE* | C |
| *11100 - 11199* | *Embedded* | C |
| *11200 - 11299* | *JAXRS* | C |
| *11300 - 11399* | *JMX* | C |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi (as plugin 00-10; service 11-99)* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *13100 - 13199* | *Security* |
|
| *14100 - 14399* | *Ejb3* | I |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
|
| *EE Deployment* |
|
|
| *Host Controller* |
|
|
| *Jacorb* |
|
|
| *JAXR* |
|
|
| *JDR* |
|
|
| *Mail* |
|
|
| *Platform MBean* |
|
|
| *POJO* |
|
|
| *Remoting* |
|
|
| *SAR* |
|
|
| *Security* |
|
|
| *Server* |
|
|
| *Threads* |
|
|
| *Web* |
|
|
| *Web Services* |
|
|
| *Weld* |
|
|
| *Xts* |
|
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
12 years, 5 months
[JBoss AS7 Development] - Logging Id's
by James Perkins
James Perkins [http://community.jboss.org/people/jamezp] modified the document:
"Logging Id's"
To view the document, visit: http://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | W |
| *10700 - 10799* | *CMP* |
|
| *10900 - 10999* | *Domain Controller* |
|
| *11000 - 11099* | *EE* | W |
| *11100 - 11199* | *Embedded* | W |
| *11200 - 11299* | *JAXRS* | W |
| *11300 - 11399* | *JMX* | W |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi (as plugin 00-10; service 11-99)* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *13100 - 13199* | *Security* |
|
| *14100 - 14399* | *Ejb3* | I |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
|
| *EE Deployment* |
|
|
| *Host Controller* |
|
|
| *Jacorb* |
|
|
| *JAXR* |
|
|
| *JDR* |
|
|
| *Mail* |
|
|
| *Platform MBean* |
|
|
| *POJO* |
|
|
| *Remoting* |
|
|
| *SAR* |
|
|
| *Security* |
|
|
| *Server* |
|
|
| *Threads* |
|
|
| *Web* |
|
|
| *Web Services* |
|
|
| *Weld* |
|
|
| *Xts* |
|
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
12 years, 5 months
[JBoss AS7 Development] - EJB Local reference
by Sunil Pandit
Sunil Pandit [http://community.jboss.org/people/spandit2] created the discussion
"EJB Local reference"
To view the discussion, visit: http://community.jboss.org/message/636498#636498
--------------------------------------------------------------
Folks ,
I am trying to deploy an ear containing two ejb's . Both the ejb's are stateless session . Both the ejb's are in the same Jar file .
Definition of First EJB is like this
<ejb-name>SystemAccess</ejb-name>
<local-home>com.csc.fs.sa.ejb.SystemAccessLocalHome</local-home>
<local>com.csc.fs.sa.ejb.SystemAccessLocal</local>
<ejb-class>com.csc.fs.sa.ejb.SystemAccessSession</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
When I start the server , the log message indicates that the JNDI binding is done .
16:08:35,001 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named SystemAccess in deployment unit subdeployment "accelEJB.jar" of deployment "formsMgmtAdminJB7EARa.ear" are as follows:
java:global/formsMgmtAdminJB7EARa/accelEJB/SystemAccess!com.csc.fs.SystemAccess
java:app/accelEJB/SystemAccess!com.csc.fs.SystemAccess
java:module/SystemAccess!com.csc.fs.SystemAccess
java:global/formsMgmtAdminJB7EARa/accelEJB/SystemAccess
java:app/accelEJB/SystemAccess
java:module/SystemAccess
16:08:35,001 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named ServiceController in deployment unit subdeployment "accelEJB.jar" of deployment "formsMgmtAdminJB7EARa.ear" are as follows:
java:global/formsMgmtAdminJB7EARa/accelEJB/ServiceController!com.csc.fs.ejb.ServiceControllerSession
java:app/accelEJB/ServiceController!com.csc.fs.ejb.ServiceControllerSession
java:module/ServiceController!com.csc.fs.ejb.ServiceControllerSession
java:global/formsMgmtAdminJB7EARa/accelEJB/ServiceController
java:app/accelEJB/ServiceController
java:module/ServiceController
However the second EJB has ejb-local-ref to first ejb
<ejb-local-ref id="EJBLocalRef_1">
<ejb-ref-name>ejb/accelerator/comp/SystemAccess</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.csc.fs.sa.ejb.SystemAccessLocalHome</local-home>
<local>com.csc.fs.sa.ejb.SystemAccessLocal</local>
<ejb-link>java:module/SystemAccess</ejb-link>
</ejb-local-ref>
Jboss throws an error saying
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: No component found for type 'com.csc.fs.sa.ejb.SystemAccessLocal' with name java:module/SystemAccess
What am I missing here . Is the local reference not supported ?
Can some one shed some light please ? Is there any sample out there ?
Thanks
Sunil
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/636498#636498]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 5 months
[JBoss AS7 Development] - How to use dmr management api at application startup? Dead-lock issue.
by frankie007
frankie007 [http://community.jboss.org/people/frankie007] created the discussion
"How to use dmr management api at application startup? Dead-lock issue."
To view the discussion, visit: http://community.jboss.org/message/636492#636492
--------------------------------------------------------------
Dear,
In short:
How can you make an application master of management objects like jdbc-connections?
How to use the management api at startup of an application while still using synchronous ModelControllerClient.execute calls?
Somewhat longer:
I'm having two major issues when using the management api at startup of my application.
Please considermy current situation.
I'm creating an application that contains it's own configuration of jdbc-connections, messaging objects, schedulers etc (lets call this application the Repo).
To work with these objects the Repo needs to configure these objects at its own startup in the JBoss runtime. To do this we decided to use the management api (DMR), because it looks very promissing.
I'm currently facing two major issues with this aproach.
*1.* The changes made to the JBoss runtime are all persisted in the config file of JBoss. I've asked in another post and there is no way to disable this. This raises issues on how to synchronise the Repo config and the JBoss config. One workaround would be to first delete all JBoss management objects at start up of the Repo and then create them again (huge overhead), a second workaroung would exist of keeping a list of all created/updated management objects and remove the ones that still exist in JBoss but no longer in the Repo config (less overhead, but complex). Maybe I'm doing things totally wrong? Are there better approaches? Anyway, when implementing these workarounds I came a accross a second even bigger problem.
*2.* To deploy an application (like our Repo) JBoss uses the management api itself, which results in a dead-lock. Apparantly it is not possible to run ModelControllerClient.execute synchronously while being in another instance of this execute method. So for example when I want to run the add operation to create a jdbc-connection in the startup of the Repo the application hangs because the deployment of the Repo is running inside an execute of the deploy operation by JBoss. A workaround for this issue would exist in calling the ModelControllerClient.executeAsync method. This works fine but complicates the workarounds for my first issue gravely. For example the remove all approach (see issue 1) requires me to first get a list of all connections, but this would require me to write custom callback handlers for the async call. This all seems very complicated and fare sought I believe.
I have the feeling that my approach is not the right one here? Do you have any suggestion on this? The fact the Repo is the master of the management objects is however really required for our setup.
Thanks for your help
Laurenz
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/636492#636492]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 5 months
[JBoss AS7 Development] - Logging Id's
by James Perkins
James Perkins [http://community.jboss.org/people/jamezp] modified the document:
"Logging Id's"
To view the document, visit: http://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI
* |
|
| *10600 - 10699* | *Controller Client* | W |
| *10700 - 10799* | *CMP* |
|
| *10900 - 10999* | *Domain Controller* |
|
| *11000 - 11099* | *EE* | I |
| *11100 - 11199* | *Embedded* | W |
| *11200 - 11299* | *JAXRS* | W |
| *11300 - 11399* | *JMX* | W |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi (as plugin 00-10; service 11-99)* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *13100 - 13199* | *Security* |
|
| *14100 - 14399* | *Ejb3* | I |
| *14400 - 14499* | *AppClient* | C |
| *14500 - 14599* | *JDR* | C |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Deployment HTTP API* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
|
| *EE Deployment* |
|
|
| *Host Controller* |
|
|
| *Jacorb* |
|
|
| *JAXR* |
|
|
| *JDR* |
|
|
| *Mail* |
|
|
| *Platform MBean* |
|
|
| *POJO* |
|
|
| *Remoting* |
|
|
| *SAR* |
|
|
| *Security* |
|
|
| *Server* |
|
|
| *Threads* |
|
|
| *Web* |
|
|
| *Web Services* |
|
|
| *Weld* |
|
|
| *Xts* |
|
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
12 years, 5 months