[Datasource Configuration] - Need help accessing a jdbc datasource inside ejb on jboss 7.1.1
by tareq zaman
tareq zaman [https://community.jboss.org/people/tareq_zaman] created the discussion
"Need help accessing a jdbc datasource inside ejb on jboss 7.1.1"
To view the discussion, visit: https://community.jboss.org/message/826053#826053
--------------------------------------------------------------
Hi,
I would appreciate any help on this. I have tried so many ways but no success yet. I am trying to test a datasource inside an session ejb in JBoss AS 7.1.1.Final. Using MS SQL server.
Getting name not found exception, here is the stack trace. Please note in the code I am using the full JNDI name as java:jboss/datasources/ezsystemDS.
19:20:57,293 ERROR [stderr] (EJB default - 1) javax.naming.NameNotFoundException: jboss/datasources/ezsystemDS -- service jboss.naming.context.java.jboss.exported.jboss.datasources.ezsystemDS
19:20:57,306 ERROR [stderr] (EJB default - 1) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
19:20:57,317 ERROR [stderr] (EJB default - 1) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
19:20:57,325 ERROR [stderr] (EJB default - 1) at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127)
19:20:57,332 ERROR [stderr] (EJB default - 1) at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73)
19:20:57,337 ERROR [stderr] (EJB default - 1) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
19:20:57,341 ERROR [stderr] (EJB default - 1) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
19:20:57,344 ERROR [stderr] (EJB default - 1) at java.lang.Thread.run(Thread.java:724)
19:20:57,646 INFO [org.jboss.as.naming] (Remoting "sc1-mis99" task-3) JBAS011806: Channel end notification received, closing channel Channel ID 5643bfb0 (inbound) of Remoting connection 0148380c to null
When Jboss starts I can see datasources are bound correctly. Also verified that from JBOSS console naming tree view.
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-14) JBAS010400: Bound data source [java:jboss/datasources/ezsystemSeqDS]
19:15:45,643 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
19:15:45,643 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-11) JBAS010400: Bound data source [java:jboss/datasources/ezsystemDS]
19:15:45,947 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 http://127.0.0.1:9990
19:15:45,948 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final
Here is my ejb code
public String echo(String input){
try {
InitialContext ctx = new InitialContext();
DataSource datasrc = (DataSource)ctx.lookup("java:jboss/datasources/ezsystemDS");
if(datasrc != null) {
Connection con = datasrc.getConnection();
con.close();
}
} catch (Exception e) {
// TODO Auto-generated catch block
String x = e.getMessage();
e.printStackTrace();
}
return "Echoing back " + input ;
}
Data sources are configured in module.xml and created using admin console. Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/826053#826053]
Start a new discussion in Datasource Configuration at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 9 months
[Datasource Configuration] - Regarding "Communications link failure" in Jboss 5.1.2
by JBoss Is My Boss
JBoss Is My Boss [https://community.jboss.org/people/imranbaseer] created the discussion
"Regarding "Communications link failure" in Jboss 5.1.2"
To view the discussion, visit: https://community.jboss.org/message/826215#826215
--------------------------------------------------------------
Hello Folks,
Could you please help me on the below issue?
Event: While doing AP → DB process, there is a process which run SQL for long time, when passing 3600 seconds（60 minutes） then the session was disconnected and an error occurred in Jboss side then after that it became the status which the process was not running normally unless rebooting the instance of Jboss. No issues if it is processing within 3600 seconds.
In the jboss-4.0.5 environment, Normal result is the output to the screen after a lapse of more than 3600 seconds. But In the jboss-5.1 environment, an error will occur when 3600 seconds have elapsed.
Error in Jboss Log:
Attached with this discussion. Please find it.
We are using the below ,
MySQL 5.5.21
Jboss 5.1.2
OpenJDK 1.6.0_22
Redhat Linux 5.7
I am thinking that the root cause is the connection error that is occurring at the mysql driver level and there is an external change that is causing the communication link failure and this is not originating from the application server. It is manifesting at the driver level. Please confirm?
Could you please let me know the following,
1) Countermeasure to avoid the session disconnection at 3600 seconds in jboss-5.1 environment?
2) Cause for not performing normally if it takes 3600 seconds in jboss-5.1 environment?
3) Long SQL query(3600 seconds) is processing normally in jboss-4.0.5 environment but not in the jboss-5.1 environment. What could be reason for this issue?
4) How to solve this issue in jboss-5.1 environment? Please let me know if you need more information
Please let me know if you need more information.
Thanks in advance for you suggestions and solutions.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/826215#826215]
Start a new discussion in Datasource Configuration at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 9 months
[jBPM] - jBPM over cluster environment
by Moisés Fernández
Moisés Fernández [https://community.jboss.org/people/moifer] created the discussion
"jBPM over cluster environment"
To view the discussion, visit: https://community.jboss.org/message/826125#826125
--------------------------------------------------------------
Hello,
We are planning to use jBPM 5.4 over a clustered environment: Weblogic 11g clustered with 2 instance nodes over Red Hat Linux using Oracle 11g in the DB tier. We want to know if it's possible to use jBPM over this clustered enviroment and how, we haven't found any documentation about this subject (jBPM clustering).
The configuration that we've in mind is to use jBPM with Spring and Hibernate to persist the jBPM information needed to run it into the Oracle DB, but we've some questions: what about StatefulKnowledgeSession?: we should replicate it manually across the several App. Server nodes? We should have diferent sessions at the several nodes? If yes, if a session is running a process, the other session in the other node could access to that process?
By the way, we are planning to use Mina Task Server for the human task, can it run over a clustered environment?
Thanks in advance,
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/826125#826125]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 9 months
[jBPM] - jBPM 5.4, Persistence, and Safe-Points
by Franco Gasperino
Franco Gasperino [https://community.jboss.org/people/franco.gasperino] created the discussion
"jBPM 5.4, Persistence, and Safe-Points"
To view the discussion, visit: https://community.jboss.org/message/825366#825366
--------------------------------------------------------------
Community,
Excuse the long-winded post. I'm trying to debug an issue with an integration project with the following components:
* jBPM 5.4 final, Drools 5.5 final
* Spring 3.2.x
* Bitronix 2.1.x
The core jBPM engine is heavily integrated with a custom stack allowing process instances to be created and run via all sorts of connectivity. The custom layer will take the process id & input parameters, delegate to a thread in an executor, which will:
1. Instantiate the drools environment (with JTA support).
2. Create the knowledge session.
3. Create a custom WorkItemHandler, associate each custom service task with this handler.
4. Create and associate the event handlers.
5. Create and start the process instance.
Everything executes as-expected, the JTA is performing commits and I can see the Hibernate activity inserting, updating, and deleting records from the Derby XA database.
However, when testing a process instance which *should* trigger a safe-point, i see unexpected behavior. In this case:
* Script "Hello" is a java/groovy/whatever script task.
* ServiceTask "MockAsyncTask" is a java class, which is associated / registered with the custom WorkItemHandler. * executeWorkItem() does NOT call completeWorkItem()
* Returns control to the jBPM engine, which should trigger a safe-point.
* Causes return of startProcessInstance(), which will exit the worker thread in the executor.
* Script "Bye" is a java/groovy/whatever script task.
The workflow: Start -> Hello -> MockAsyncTask -> Bye -> End
As expected, I see the behavior. I see that the ProcessInstance object associated has a state field of "2", which is active. Howevever, the hibernate update statements on the ProcessInstanceInfo table always have a state value of '0'. This is the breaking behavior.
When I attempt to call the adapter layer with the session id, process instance id, work item id, and a payload:
1. Instantiate the drools environment (JTA support).
2. Load the existing knowledge session.
3. Create a custom WorkItemHandler, associate each custom service task with this handler.
4. Create and associate event handlers.
5. Call completeWorkItem().
The workItem does complete, and i see it deleted from the WorkItemInfo table. However, since the process instance state has been reloaded with a value of '0', the "Bye" script task is never fired.
Any ideas? A full code dump would be huge, but I'm happy to inject some loggers if it would assist troubleshooting.
Thanks!
Franco
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/825366#825366]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 9 months
[EJB3] - Failed to create Resource DEPLOYMENTS MISSING DEPENDENCIES
by Carlos Farias
Carlos Farias [https://community.jboss.org/people/cafaray] created the discussion
"Failed to create Resource DEPLOYMENTS MISSING DEPENDENCIES"
To view the discussion, visit: https://community.jboss.org/message/825860#825860
--------------------------------------------------------------
Hi, I'm new in Jboss, I'm using Jboss6.0.0-final and running the standard server. I'm trying to deploy an EJB with a Session Bean Stateless and MDB, but i get the next error (I've worked in eclipse and the same version of JBoss in my local, here works fine)
Can any body give an idea:
Regards
Failed to create Resource FITANotificaciones.jar - cause: java.lang.Exception:Failed to start deployment [vfs:///usr/local/jboss-6.0.0/server/standard/deploy/FITANotificaciones.jar] during deployment of 'FITANotificaciones.jar' - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=EnviaCorreo,service=EJB3" is missing the following dependencies: Dependency "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=EnviaCorreo,service=EJB3>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **") Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3" is missing the following dependencies: Dependency "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **") Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3" (should be in state "Installed", but is actually in state "PreInstall") Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3" is missing the following dependencies: Dependency "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **") Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3" (should be in state "Installed", but is actually in state "PreInstall") DEPLOYMENTS IN ERROR: Deployment "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' ** Deployment "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' ** Deployment "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=EnviaCorreo,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' ** -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=EnviaCorreo,service=EJB3" is missing the following dependencies: Dependency "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=EnviaCorreo,service=EJB3>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **") Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3" is missing the following dependencies: Dependency "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **") Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3" (should be in state "Installed", but is actually in state "PreInstall") Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3" is missing the following dependencies: Dependency "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **") Deployment "jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3_endpoint" is missing the following dependencies: Dependency "jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3" (should be in state "Installed", but is actually in state "PreInstall") DEPLOYMENTS IN ERROR: Deployment "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=Sample,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' ** Deployment "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=NotificaRegistro,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' ** Deployment "<UNKNOWN jboss.j2ee:jar=FITANotificaciones.jar,name=EnviaCorreo,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/825860#825860]
Start a new discussion in EJB3 at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 9 months