[EJB3] - Exception while deploing an ear with @MessageDriven bean
by Stanislav Kogut
stasikos [http://community.jboss.org/people/stasikos] created the discussion
"Exception while deploing an ear with @MessageDriven bean"
To view the discussion, visit: http://community.jboss.org/message/575308#575308
--------------------------------------------------------------
There is an example of bean code:
@MessageDriven (activationConfig={
@ActivationConfigProperty(propertyName="destination", propertyValue="jms/Queue")})
public class JBossMDB implements MessageListener{
@Override
public void onMessage(Message message) {
Logger.getLogger("JbossMDB").log(Level.INFO, message.toString());
}
}
But when deploying (firest deploy) an ear with this bean to JBosss AS 6CR1 I have this exception:
Failed to create Resource J6EELearning.ear - cause: java.lang.Exception:Failed to start deployment [vfs:///home/stasikos/Soft/jboss-6.0.0.20101110-CR1/server/default/deploy/J6EELearning.ear] during deployment of 'J6EELearning.ear' - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS IN ERROR: Deployment "jboss.j2ee:ear=J6EELearning.ear,jar=J6EELearning-ejb.jar,name=JBossMDB,service=EJB3" is in error due to the following reason(s): java.lang.IllegalStateException: Timer service with timedObjectId: jboss.j2ee:ear=J6EELearning.ear,jar=J6EELearning-ejb.jar,name=JBossMDB,service=EJB3 is already registered -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS IN ERROR: Deployment "jboss.j2ee:ear=J6EELearning.ear,jar=J6EELearning-ejb.jar,name=JBossMDB,service=EJB3" is in error due to the following reason(s): java.lang.IllegalStateException: Timer service with timedObjectId: jboss.j2ee:ear=J6EELearning.ear,jar=J6EELearning-ejb.jar,name=JBossMDB,service=EJB3 is already registered
It is little strange to have Timer service errors when deploying Message-Driven Beans. Also, if I remove this bean from ear, deploy is successfull.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/575308#575308]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 4 months
[JBoss Web Services] - Need little help with isolation configuration and class loading
by Nikolay Karasev
Nikolay Karasev [http://community.jboss.org/people/nkarasev] created the discussion
"Need little help with isolation configuration and class loading"
To view the discussion, visit: http://community.jboss.org/message/575291#575291
--------------------------------------------------------------
Hi,
I am new here. If this is not correct forum (location) please suggest the better one.
Our company has jboss installed on some QA and Prod servers and accessing and modifying any files on server is less than desirable for stability reasons.
However the installed version (4.2.3.GA) is using older hibernate libraries (/server/default/lib/hibernate3.jar,...). I have to use newer libraries to be able to use hibernate annotations. I have set up maven project(s) so that I am downloading correct versions of hibernate, hibernate-annotations and hibernate-commons-annotations. These are getting bundled into the WAR and then into EAR files and are extracted properly into application's /lib directory. However jboss is picking up the default libraries (I can see that in logs) and AnnotationConfiguration is probably not the correct class (configure() method is not found).
If I remove the default jar files from jboss installation on my dev box, all works fine, all newer versions of hibernate libraries are loaded and my app works as expected. But like I said - modifying anything on the server side is not desired at all, I would like to force jboss to pick those hibernate libraries from supplied WAR/EAR files.
While trying to investigate and find the remedy, the only way I see is to do something with class loader in jboss-web.xml file. Maybe I am wrong here, but I cannot find anything close enough. However I am not able to understand how this file is organized. I have assumption that <loader-repository>com.example.loaderrepository:loader=my.war needs to be properly assigned, but I am not sure to what? "com.example" - is this a placeholder for the class that I need to load, or is this for something else? Currently my domain is just "localhost" but in QA or Prod environment it will be xxxxx.com
Also do I need to use java2ParentDelegation=false?
Thanks,
Nikolay
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/575291#575291]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 4 months
[JNDI and Naming] - Lookup bean from AS 4.0.5 to 5.1.0
by Gabriel Valencia
Gabriel Valencia [http://community.jboss.org/people/gvalenc] created the discussion
"Lookup bean from AS 4.0.5 to 5.1.0"
To view the discussion, visit: http://community.jboss.org/message/575250#575250
--------------------------------------------------------------
I have an EJB3 stateless session bean deployed in AS 5.1.0 that I am trying to look up from some client code deployed in a remote AS 4.0.5 installation. The client isn't a true EJB client, just something that happens to be running within the context of a 3rd party EJB in that server. Should this be possible? The client has the same class files inside its jar as those in the 5.1.0 bean's jar. I specifically set the JNDI provider URL to be the remote 5.1.0 server in the InitialContext properties before lookup.
I get this exception during the narrow() call:
Caused by: java.lang.ClassCastException
at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:229)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
at com.venetica.vbr.res.ejb.EJBLocator.locateDirector(EJBLocator.java:115)
... 23 more
Caused by: java.lang.ClassCastException: javax.naming.Reference
at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:212)
... 25 more
Caused by: java.lang.ClassCastException
at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:229)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
at ****(****.java:115)
... 23 more
Caused by: java.lang.ClassCastException: javax.naming.Reference
at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:212)
... 25 more
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/575250#575250]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 4 months
[jBPM] - Re: Create a flexible workflow and deploy it in JBPM on the fly
by Justin Lee
Justin Lee [http://community.jboss.org/people/justin.l] created the discussion
"Re: Create a flexible workflow and deploy it in JBPM on the fly"
To view the discussion, visit: http://community.jboss.org/message/575197#575197
--------------------------------------------------------------
We had the same kind of requirement that an admin in system can update the workflow at any time.
The solution we provided was as we know jBPM supports the version number for process definitions and whenever an admin makes updates to the workflow, the updated workflow will be saved with new version number. Admin has to choose whether the system should go with the executions of older version which is already created for the users or should go with the new version. If it is with new version, admin user has to force close all the executions for the old version and then allow the system to create the new instances for workflow with latest version, for all the users.
This is the workaround we provided in our system for client requirement.
Applying workflow updates on the fly to the running executions(process instances) is not supported by jBPM.
Thanks!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/575197#575197]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 4 months