[jBPM] - Errors instaling JBPM 4.3 in JBoss 4.2.3
by Ivan Pazmino
Ivan Pazmino [http://community.jboss.org/people/iapazmino] created the discussion
"Errors instaling JBPM 4.3 in JBoss 4.2.3"
To view the discussion, visit: http://community.jboss.org/message/546140#546140
--------------------------------------------------------------
Hi everyone,
I need some help with jbpm 4.3 installation over a JBoss 4.2.3
I downloaded jbpm-4.3.zip and unzipped it. Then installed the database without trouble.
Problems arouse with the app server installation. I changed build.xml properties regarding JBoss version and location
<property name="jboss.version" value="4.2.3.GA" />
<property name="jboss.parent.dir" value="/usr/local/java" />
Then run ant -Ddatabase=mysql install.jbpm.into.jboss
The execution went without problems, but when starting the app server i got the following exception:
20:14:24,231 ERROR [MainDeployer] Could not create deployment: file:/usr/local/java/jboss-4.2.3.GA/server/jbpm4/deploy/jbpm/jbpm-destinations-service.xml
org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.jms.server.destination.QueueService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.server.destination.QueueService)
I've read some post that report having issues with installations over 4.2.x, but none says anything about adding extra jars to the server's lib.
Any idea what would be wrong?
Thanks in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546140#546140]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[Beginner's Corner] - problems with an EAR file with MDBs
by null null
null null [http://community.jboss.org/people/ranjix] created the discussion
"problems with an EAR file with MDBs"
To view the discussion, visit: http://community.jboss.org/message/546131#546131
--------------------------------------------------------------
Hey guys, maybe you know what's going on...
I'm trying to port some J2EE apps (EARs) from weblogic to jboss. These apps are depending on each other, in the sense that all need a specific one to start first. In short, EAC.ear needs to start first, then the rest - JMS, EDESK and PUBLISH. For this I use the "deploy.last" as a parent for the EARs which depend on EAC. From the above EAR apps, only PUBLISH contains ejbs (an MDB), the rest contain just wars.
Also, I want all these to start from folders in a certain directory, instead of the "deployed" folder from JBoss home folder. For this I modified the profile.xml from JBoss, to include the respective folders.
With these settings, I ran into a strange (for me) issue. In short, if I leave in profile.xml only the EAC, JMS and EDESK apps, they start fine. If I add PUBLISH, no error happens, but none of the JMS, EDESK and PUBLISH start.
so.
*Case 1 - If I have in profile.xml just eac, jms and edesk*
**
<value>${jboss.server.home.url}deploy</value>
<value>file:///C:/10.DEV.NEW.3/modules/eac/appserver/jboss</value>
<value>file:///C:/10.DEV.NEW.3/modules/jms/appserver/jboss</value>
<value>file:///C:/10.DEV.NEW.3/modules/edesk/appserver/jboss</value>
+<!--value>file:///C:/10.DEV.NEW.3/modules/publish/appserver/jboss</value-->+
*Then the output of JBoss is fine*
**
17:36:09,476 INFO [TomcatDeployment] deploy, ctxPath=/eac
17:36:11,136 INFO [STDOUT] Initializing application. (C:\10.DEV.NEW.3\modules\eac\config\eac.appconfig.dna)
17:36:14,757 INFO [STDOUT] Checking initialization state for database 'eac' (jdbc:sqlserver://DB-SPOP:1433;SelectMethod=cursor;DatabaseName=jboss_EAC)...
17:36:15,669 INFO [STDOUT] URL optimisation mode set to: none
17:36:15,678 INFO [STDOUT]
**************************************************************************
Escalate Environment and Access Control successfully started
**************************************************************************
17:36:15,756 INFO [TomcatDeployment] deploy, ctxPath=/jms
17:36:16,344 INFO [STDOUT] Initializing application. (C:\10.DEV.NEW.3\modules\jms\config\jms.appconfig.dna)
17:36:19,541 INFO [STDOUT]
**************************************************************************
Escalate JMS Server successfully started
**************************************************************************
17:36:19,628 INFO [TomcatDeployment] deploy, ctxPath=/edesk
17:36:20,497 INFO [STDOUT] Initializing application. (C:\10.DEV.NEW.3\modules\core\config\pdc.server.appconfig.dna)
17:36:20,695 ERROR [STDERR] Environment variable 'BMS_JMS_SERVER_NAME' missing for DNAList name 'server'
17:36:26,335 INFO [STDOUT] Could not find the 'startup' callback class 'com.bluemartini.dev.net.DevServer'. Ignoring.
17:36:26,427 INFO [STDOUT] Checking initialization state for database 'main' (jdbc:sqlserver://DB-SPOP:1433;SelectMethod=cursor;DatabaseName=jboss_MAIN)...
17:36:26,929 INFO [STDOUT] Checking initialization state for database 'store' (jdbc:sqlserver://DB-SPOP:1433;SelectMethod=cursor;DatabaseName=jboss_STORE)...
17:36:27,865 INFO [STDOUT] URL optimisation mode set to: none
17:36:27,893 INFO [STDOUT] Initializing rules engine...
17:36:27,935 INFO [STDOUT] Rules engine successfully initialized...
17:36:28,055 INFO [STDOUT] SearchIndexLoader.init()
17:36:28,113 INFO [STDOUT] BM JMS: Creating Topic Connection to JMS Server jnp://DB-SPOP:1099
17:36:28,769 INFO [STDOUT] BM JMS: Creating Queue Connection to JMS Server jnp://DB-SPOP:1099
17:36:28,858 INFO [STDOUT] BM JMS: Successfully connected to JMS Server jnp://DB-SPOP:1099
17:36:29,372 INFO [STDOUT]
**************************************************************************
Escalate Enterprise Desktop Server successfully started
**************************************************************************
17:36:29,597 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
17:36:29,633 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
17:36:29,651 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8443
**
*Case 2 - if I add in profile.xml +publish+ (which has an MDB)*
**
<value>${jboss.server.home.url}deploy</value>
<value>file:///C:/10.DEV.NEW.3/modules/eac/appserver/jboss</value>
<value>file:///C:/10.DEV.NEW.3/modules/jms/appserver/jboss</value>
<value>file:///C:/10.DEV.NEW.3/modules/edesk/appserver/jboss</value>
*<value>file:///C:/10.DEV.NEW.3/modules/publish/appserver/jboss</value>*
+
+
*Then the things get screwey*
17:28:04,483 INFO [TomcatDeployment] deploy, ctxPath=/eac
17:28:06,006 INFO [STDOUT] Initializing application. (C:\10.DEV.NEW.3\modules\eac\config\eac.appconfig.dna)
17:28:09,574 INFO [STDOUT] Checking initialization state for database 'eac' (jdbc:sqlserver://DB-SPOP:1433;SelectMethod=cursor;DatabaseName=jboss_EAC)...
17:28:10,441 INFO [STDOUT] URL optimisation mode set to: none
17:28:10,472 INFO [STDOUT]
**************************************************************************
Escalate Environment and Access Control successfully started
**************************************************************************
17:28:10,540 INFO [TomcatDeployment] deploy, ctxPath=/jms
17:28:10,751 INFO [EjbDeployer] installing bean: ejb/publish_ejb_default.jar#PubServerDBUtilTopicMDB,uid680989819
17:28:10,753 INFO [EjbDeployer] with dependencies:
17:28:10,754 INFO [EjbDeployer] and supplies:
17:28:10,755 INFO [EjbDeployer] jndi:null
17:28:10,838 INFO [TomcatDeployment] deploy, ctxPath=/publish
17:28:11,016 INFO [EjbModule] Deploying PubServerDBUtilTopicMDB
17:28:11,069 WARN [EjbModule] EJB configured to bypass security. Please verifyif this is intended. Bean=PubServerDBUtilTopicMDB Deployment=vfsfile:/C:/10.DEV.NEW.3/modules/publish/appserver/jboss/deploy.last/publish.ear/publish_ejb_default.jar/
17:28:11,324 INFO [TomcatDeployment] deploy, ctxPath=/edesk
17:28:12,080 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
17:28:12,119 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
17:28:12,140 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8443
17:28:12,159 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 1m:41s:117ms
I have no idea what's going on, JBoss pretends nothing is wrong, but why I don't see any of the other apps starting fine (jms, edesk and publish), no errors in any log file...
thanks for any idea,
ranjix
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546131#546131]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
[EJB 3.0 Development] - javax.ejb.EJBAccessException: Caller unauthorized when calling //EJB3 @Service from client code
by Dave Bredesen
Dave Bredesen [http://community.jboss.org/people/dbredesen] created the discussion
"javax.ejb.EJBAccessException: Caller unauthorized when calling //EJB3 @Service from client code"
To view the discussion, visit: http://community.jboss.org/message/546116#546116
--------------------------------------------------------------
Hello,
I'm building an application on JBoss AS 5.1 and ICEFaces. The application runs in a single JBoss instance currently. I'm doing authentication via JAAS, using the DatabaseServerLoginModule, and I'm able to login successfully via ICEFaces as follows:
* CallbackHandler cb = new Handler("someuser", password);
*
* LoginContext lc = new LoginContext("foo", cb);
*
* lc.login();*
Once logged in, I can see clearly that "someuser" has the "admin" role. Now, I have an EJB set up as follows:
* @Service
*
* @Local
*
* @SecurityDomain("foo") // corresponds to the security domain above
*
* public class MyService implements MyServiceLocal {
*
* @RolesAllowed("admin")
*
* public void doSomething() {
*
* // do something
*
* }
*
* }*
I am trying to call MyBean.doSomething() from my ICEFaces client code as follows:
* InitialContext ctx = new InitialContext();
*
* final String name = "MyService/local";
*
* service = (MyServiceLocal) ctx.lookup(name);
*
* service.doSomething(); //* *causes EJBAccessException: Caller unauthorized*
Somehow, the callee doesn't recognize that I am authenticated. I did a bit of debugging, and the caller thinks my principal is "anonymous".
How do I get EJB to recognize my credentials which were established outside of EJB? Do I need to pass some extra information to the InitialContext? (I tried setting Context.SECURITY_PRINCIPAL, with no luck...). Any help would be appreciated!
Thanks,
Dave Bredesen
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546116#546116]
Start a new discussion in EJB 3.0 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [JBoss Microcontainer Development POJO Server] - Implementing a non-flat deployment for Weld Integration
by Flavia Rainone
Flavia Rainone [http://community.jboss.org/people/flavia.rainone%40jboss.com] replied to the discussion
"Implementing a non-flat deployment for Weld Integration"
To view the discussion, visit: http://community.jboss.org/message/546115#546115
--------------------------------------------------------------
> Pete Muir wrote:
>
> > I've been thinking about correctness all this time. If somebody places a jar in lib and expects that the beans are created upfront when AS starts, then this would not work using your approach.
>
>
> Ok, I think we've got crossed wires. You can't deploy a library jar in some "context" outside a deployment. The beans don't get created or anything outside the context of a deployment.
>
>
>
> Another way to think of it is that a library in default/lib with a beans.xml in it works just like a library in WEB-INF/lib.
In that case, why the lazy approach wouldn't work?
>From what I can see, if it works just like a library in WEB-INF/lib, it means that we will need to provide a BDA for a lib jar only when Weld requests for one through loadBeanDeploymentArchive, right?
Or, if I'm wrong, do you mean that a BDA for every lib jar with a META-INF/beans.xml should be provided as direct or indirect result of BeanDeploymentArchive.getBeanDeploymentArchives() for every BDA in a Deployment?
Explaining better, given commos/lib/mylib.jar with the following structure:
mylib.jar
|_
META-INF/beans.xml
|_
whatever classes in here
Say we create a BDA upfront, let's call it MY_LIB_BDA, and add this BDA to DefalutDomain Classpath. No deployment is created upfront.
Now, say my-ejb.jar with a META-INF/beans.xml file is deployed to deploy dir. We create a Deployment for it, of course, and we create a BDA for it as well. This BDA, called MY_EJB_BDA, belongs to Default Domain Classpath. So, when Weld invokes MY_EJB_BDA.getBDAs(), it should , directly on indirectly (i.e., by walking on the BDA graph structure), reach MY_LIB_BDA?
This is different from the lazy approach in which you are not required to call loadBeanDeploymentArchive in order to obtain MY_LIB_BDA.
Is that what Weld requires us to do?
> Pete Muir wrote:
>
> > Flavia Rainone wrote:
> >
> > > Ales Justin wrote:
> > >
> > > Why the rush? :-)
> > > If you ask me, I would do it lazily aka on_demand.
> > >
> > > Scanning the whole common/lib is gonna be slow,
> > > and imo, people should not be using libs to deploy Weld components -- simply put them in deploy/.
> > >
> > > Or why would you do it upfront?
> Because the Java EE/CDI specs require it.
BTW, I've read the spec sometime ago. Of course I don't remember all the details so, if you think rereading some specific part of it might be useful, let me know.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/546115#546115]
Start a new discussion in JBoss Microcontainer Development POJO Server at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years