[JBoss AS 7 Development] - Issue while deploying EJB 3 with JBoss AS 7
by Manoj Agarwal
Manoj Agarwal [https://community.jboss.org/people/manoj.m.agarwal] created the discussion
"Issue while deploying EJB 3 with JBoss AS 7"
To view the discussion, visit: https://community.jboss.org/message/742586#742586
--------------------------------------------------------------
Hi,
I am trying to deploy a SLSB with annotations @Singleton and @Startup. I packaged it as a jar and put it under standalone/deployments.
I get this error while starting server. Any help will be very helpful.
11:35:22,844 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."xyz-startup-bean-3.0.0-SNAPSHOT.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xyz-startup-bean-3.0.0-SNAPSHOT.jar".POST_MODULE: Failed to process phase POST_MODULE of deployment "xyz-startup-bean-3.0.0-SNAPSHOT.jar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
Caused by: java.lang.NullPointerException
at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:53) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:63)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
...............................
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742586#742586]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[JBoss Tools Development] - How we create our update-sites? What are they? Which one you should use?
by Nick Boldt
Nick Boldt [https://community.jboss.org/people/nickboldt] modified the document:
"How we create our update-sites? What are they? Which one you should use?"
To view the document, visit: https://community.jboss.org/docs/DOC-18462
--------------------------------------------------------------
JBoss Tools is made of a lot of plugins coming from different component, and that are aggregated for ease their installation. There are a lot of repositories. This page is intended to explain what are our repositories, what are they aimed to, and where they are coming from:
h1. General process
Here is the general process of the lifecycle of sites in the build.
*For each stream (branch or trunk) in progress*:
1. Mirror requirements and composite specific versions into a single Requirements site
2. Build all common stuff (parent, target-platforms). Publish to maven artifacts to JBoss Nexus and update sites to download.jboss.org
3. Build each component and publish to download.jboss.org
4. A *staging composite* repository is used to provide a single URL for all components' update sites
5. A *nightly snapshot* is continuously created from the composite site. It contains the latest good build of each component, including categorization & source features/plugins. A test site is also created, containing only test features/plugins.
6. After a code-freeze, the nightly snapshot is first staged as a *development milestone* and passed to QE for validation. Upon approval, it is published to www.jboss.org.
7. After several milestone and validation cycles, we publish our best *development milestone* as a *stable release*.
The same applies to SOA components. Some additional steps exist to also build JBDS site and products continuously, following the same lifecycle.
Here's a diagram which shows how all the jobs, update sites, and other artifacts co-exist:
https://community.jboss.org/servlet/JiveServlet/showImage/102-18462-2-187... https://community.jboss.org/servlet/JiveServlet/downloadImage/102-18462-2...
The diagram below (while out of date) provides some additional information about the process:
h2. http://anonsvn.jboss.org/repos/jbosstools/trunk/build/diagrams/JBDS_Aggre... http://anonsvn.jboss.org/repos/jbosstools/trunk/build/diagrams/JBDS_Aggre... Repositories / Update-Sites
h3. Requirements / Target-platfoms sites / Mirrors
These site are mirrors of dependencies of JBoss Tools. They are here to provide more performance and to ensure we have a backup of everything we depend on.
|| *URL* || *Name* || *Profile to activate in build* || *Performance*
|| *When to use it?
* ||
| http://download.jboss.org/jbosstools/updates/requirements/+<NAME>+/+<VERSION>/+ | Individual mirror | Not possible | Good | When you want to install a 3rd-party deps, and you prefer this server |
| http://download.jboss.org/jbosstools/updates/+<ECLIPSE_RELEASE_TRAIN>+/ | Composute requirements | Not possible, should be part of Target Platform | Bad | To build extras and target-platform site |
| http://download.jboss.org/jbosstools/updates/target-platform_+<NAME>+/ | Target Platform site | By default, as part of the target-platform | Good | Is a mirror of the target platform. It is used whenever you use a .target file. |
h3. JBT (non-SOA)
|| *URL
* || *Name* || *Profile to activate in build* || *Quality/Stability* || Performances || When to use it? ||
| http://download.jboss.org/jbosstools/builds/staging/+<COMPONENT_JOB_NAME>+/all/repo/ | Component rep | Not possible, use composite instead | Poor | Good | When you really want the latest stuff on a single component without loosing performances |
| http://download.jboss.org/jbosstools/builds/staging/_composite_/core/+<BRANCH_NAME>+ | Composite repo | -P jbosstools-nightly-composite | Poor | Poor | If you want very latest changes |
| http://download.jboss.org/jbosstools/builds/staging/jbosstools-+<BRANCH_NAME>+.aggregate/all/repo/ | Aggregated snapshot repo | Not possible, use jbosstools-nightly instead | Poor | Average | NEVER. This is the temporary location of the aggregated site. It gets published to a better location afer |
| http://download.jboss.org/jbosstools/updates/nightly/core/+<BRANCH_NAME>+ | Aggregated snapshot repo | Currently, use -P jbosstools-staging-aggregate | Poor | Good | When you want to develop with recent version of dependencies (1 or 2 days ago). Suitable for local testing
NOTE: this is the "work in progress" final site |
| http://download.jboss.org/jbosstools/updates/nightly/coretests/+<BRANCH_NAME>+ | Aggegated tests | Currently, use -P jbosstools-staging-aggregate | Poor | Good | Contains tests |
| http://download.jboss.org/jbosstools/updates/JBossTools-+<x.y.z.q>+.core/ | Milestones | Not possible | Average | Good | Good for testing, evaluating features. Good for community contributors. |
| http://download.jboss.org/jbosstools/updates/development/+<TARGET_ECLIPSE_RELEASE_TRAIN>+/ | Latest Milestone | Not possible | Average | Good | Good for testing, and for building stuff on top of JBT that will be released a bit later |
| http://download.jboss.org/jbosstools/updates/stable/<TARGET_ECLIPSE_RELEASE_TRAIN>/ | Release | Not possible | Good | Good | Good for end-users |
h3. JBT SOA
|| *URL
* || *Name* || *Profile to activate in build* || *Quality/Stability* || *Performance* || *When to use it?* ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-18462]
Create a new document in JBoss Tools Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 7 months
[JBoss Profiler Development] - Segmentation Fault
by Johannes Schmidt
Johannes Schmidt [https://community.jboss.org/people/johnsky] created the discussion
"Segmentation Fault"
To view the discussion, visit: https://community.jboss.org/message/742066#742066
--------------------------------------------------------------
Hallo comunity,
I am having trouble starting Jboss 5 on a Linux with JDSK 6_2. The Jdk is kind of old, but I am sure I will not have the posibility to update it so easily (pre-production-system).
To activate the profiling of JBoss Profiler 2.0 Beta5 I put this line into my run.conf
JAVA_OPTS="$JAVA_OPTS -javaagent:/usr/local/jboss-5.1.0.GA/bin/jboss-profiler.jar -Djboss-profiler.properties=/usr/local/jboss-5.1.0.GA/bin/jboss-profiler.properties"
Starting from shell gives me this:
/usr/local/jboss/bin/run.sh: line xx: 512 Segmentation fault "$JAVA" $JAVA_OPTS -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" -classpath "$JBOSS_CLASSPATH" org.jboss.Main "$@"
Is there any solution for this? It looks like the jdk is too old or jboss is missing some classes. Although I tried it on another linux/jboss 5 but newer jdk and that works.
Hopefully someone can help me. As always, any help is apreciated.
Thanks a lot
Best
Johannes
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742066#742066]
Start a new discussion in JBoss Profiler Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[JBoss AS 7 Development] - Remote Ejb Calls - SimpleSecurityManager and JBossCachedAuthenticationManager do not work correctly
by Michael Gronau
Michael Gronau [https://community.jboss.org/people/Michael_Gronau] created the discussion
"Remote Ejb Calls - SimpleSecurityManager and JBossCachedAuthenticationManager do not work correctly"
To view the discussion, visit: https://community.jboss.org/message/732713#732713
--------------------------------------------------------------
Hello,
As far as I still have the problem, that my custom login module is called with every remote ejb invocation i investigated a little bit more the jboss code. I see that the method SimpleSecurityManager.push(...) is called for every ejb call and here for every call a new instance of SimplePrincipal is created for the SubjectInfo. Then the method authenticate() is called. Here it delegates to the JBossCachedAuthenticationManager which tries to find an already cached principal, but this cannot work, because the get function of the cache returns null. It returns null, because of the newly created SimplePrincipal for the current invocation. The JBossCachedAuthenticationManager pushes back my principal (created in my custom login module), but cannot find it again.
It's like this for every remote ejb call:
1. call to the ejb
2. SimpleSecurityManager creates a SubjectInfo with a new(!) instance of SimplePrincipal
3. SimpleSecurityManager tries to authenticate -> delegates to JBossCachedAuthenticationManager
4. JBossCachedAuthenticationManager tries to find cached principal with a call to method get() with the principal instance from SimpleSecurityManager
5. JBossCachedAuthenticationManager finds no cached instance and starts a new authentication with my custom login module
6. My custom login module creates a new instance of Principal and commits it(), creates a Group called CallerPrincipal, adds the new Principal and adds this group to current subject
7. JBossCachedAuthenticationManager pushes back my Principal correctly
8. Ejb is called.
9. when you call the ejb again (in a simple for-loop or somehting like that) all starts again at point 1. The problem is the creation of the new Principal instance for every remote ejb call.
I think https://issues.jboss.org/browse/AS7-3525 https://issues.jboss.org/browse/AS7-3525 should be reopened. What do you think?
With best regards,
Michael Gronau
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/732713#732713]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[JBoss AS 7 Development] - AS 7 Custom Hibernate Persistence Provider in EAR
by Thomas Woelfle
Thomas Woelfle [https://community.jboss.org/people/woelfle] created the discussion
"AS 7 Custom Hibernate Persistence Provider in EAR"
To view the discussion, visit: https://community.jboss.org/message/742369#742369
--------------------------------------------------------------
We have have a custom implementation of HibernatePersistence. We've packaged it in the 'ear' file since it uses other classes from our application. When deploying the application a 'NoClassDefFoundError' for 'org.hibernate.ejb.HibernatePersistence' occurs.
08:50:14,766 WARN [org.jboss.modules] (MSC service thread 1-2) Failed to define class my.custom.HibernatePersistence in Module "deployment.ear.ear:main" from Service Module Loader: java.lang.LinkageError: Failed to link my/custom/HibernatePersistence (Module "deployment.ear.ear:main" from Service Module Loader)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:396) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.Module.loadModuleClass(Module.java:517) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
at org.jboss.as.jpa.processor.PersistenceProviderProcessor.deploy(PersistenceProviderProcessor.java:76)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
Caused by: java.lang.NoClassDefFoundError: org/hibernate/ejb/HibernatePersistence
at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0]
at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [rt.jar:1.7.0]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [rt.jar:1.7.0]
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391) [jboss-modules.jar:1.1.1.GA]
... 15 more
Caused by: java.lang.ClassNotFoundException: org.hibernate.ejb.HibernatePersistence from [Module "deployment.ear.ear:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
... 20 more
08:50:14,789 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."ear.ear".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."ear.ear".INSTALL: Failed to process phase INSTALL of deployment "ear.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011426: Could not deploy application packaged persistence provider 'my.custom.HibernatePersistence'
at org.jboss.as.jpa.processor.PersistenceProviderProcessor.deploy(PersistenceProviderProcessor.java:91)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: java.lang.ClassNotFoundException: my.custom.HibernatePersistence from [Module "deployment.ear.ear:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at org.jboss.as.jpa.processor.PersistenceProviderProcessor.deploy(PersistenceProviderProcessor.java:76)
... 6 more
'jar tf' on our ear file lists following contents:
META-INF/
META-INF/MANIFEST.MF
lib/
services-0.0.22-SNAPSHOT.jar
META-INF/application.xml
lib/guava-r07.jar
lib/asm-analysis-3.2.jar
lib/persistence_api-0.0.22-SNAPSHOT.jar
lib/asm-3.2.jar
lib/services_api-0.0.22-SNAPSHOT.jar
lib/asm-tree-3.2.jar
lib/utils-0.0.22-SNAPSHOT.jar
lib/asm-util-3.2.jar
lib/joda-time-2.0.jar
lib/domain-0.0.22-SNAPSHOT.jar
lib/antlr-2.7.7.jar
lib/commons-codec-1.3.jar
lib/asm-commons-3.2.jar
lib/backport-util-concurrent-3.1.jar
lib/commons-lang-2.4.jar
lib/commons-io-1.4.jar
lib/commons-logging-1.1.1.jar
lib/persistence_impl-0.0.22-SNAPSHOT.jar
META-INF/maven/
META-INF/maven/de.patronas.opus.server/
META-INF/maven/de.patronas.opus.server/ear/
META-INF/maven/de.patronas.opus.server/ear/pom.xml
META-INF/maven/de.patronas.opus.server/ear/pom.properties
Any idea what we've done wrong?
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742369#742369]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[JBoss Profiler Development] - Hibernate/Seam plugin not loaded
by Johannes Schmidt
Johannes Schmidt [https://community.jboss.org/people/johnsky] created the discussion
"Hibernate/Seam plugin not loaded"
To view the discussion, visit: https://community.jboss.org/message/742065#742065
--------------------------------------------------------------
Hallo all together in this comunity,
I am very thankful for the Profiler Project, I am using it successfully on Win 7 and Linux in big Project (Salud Hds in Mexico, JBoss 5, Seam 2, Jdk 6).
Here are my questions:
After using/testing the profiler and its client succesfully on Win 7 I installed the profiler on our linux servers.
Server 1 with Java 6_31 64bit: when starting the client I get this message:
Plugin org.jboss.profiler.plugins.Seam could not be loaded
To make it work on Linux I had to change the run.conf in this way
JAVA_OPTS="$JAVA_OPTS -javaagent:/usr/local/jboss-5.1.0.GA/bin/jboss-profiler.jar -Djboss-profiler.properties=/usr/local/jboss-5.1.0.GA/bin/jboss-profiler.properties"
On windows I did not had to put paths...
It looks like I have to anounce the jboss-profiler-plugin.jar in some place, but I don't know where.
Can anybody share her/his experience with me, please?
Any hint is apreciated
Thank you
Best
Johannes
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742065#742065]
Start a new discussion in JBoss Profiler Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[JBoss ESB Development] - Parallel execution of jBOSS ESB project when it called by jBPM process instances
by Arunava Basu
Arunava Basu [https://community.jboss.org/people/arunava.basu] created the discussion
"Parallel execution of jBOSS ESB project when it called by jBPM process instances"
To view the discussion, visit: https://community.jboss.org/message/742247#742247
--------------------------------------------------------------
*Dear All,*
*Problem:* The process of calling an ESB from jBPM process instances of a jBPM process is synchronous. If many requests call that particular jBPM process then the rest process requests will be in *RUNNING* state. That means they will be in queue until the older request has been executed.
*What I did:*
1. Make the ESB node *asynchronous.*
*Outcome*: Execute as a *Synchronous* process as before.
1. Call a webservice from an ESB action. It calls a function which doesn’t return anything (i.e. return type is *void*). The method calls an ESB.
*Outcome*: Execute as a *Synchronous* process as before.
1. Instead of ESB node, I used simple *NODE*. In that node I define an *action handler* which calls an ESB.
*Outcome*: Execute as a *Synchronous* process as before.
I want the ESB project should execute in parallel. I call an ESB project from a JBPM process. when I call that jBPM many times, the process instances is waiting in the queue till the older request has been executed. i want that all the process instances should execute in parallel. For that,the ESB project should be executed in parallel.
Thanx in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/742247#742247]
Start a new discussion in JBoss ESB Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
