security in domain testsuite
by Thomas Diesler
Folks,
I currently see
Caused by: java.io.FileNotFoundException:
/home/tdiesler/git/jboss-as/testsuite/domain/target/domains/DeploymentManagementTestCase/master/configuration/application-users.properties
(No such file or directory)
when I run the domain test cases. AFAICS, it is true that security is
not defined for the main server group, but deployments still go through
and the tests pass. Is this intentional?
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
12 years, 9 months
Why should a remote jndi client have to depend on jboss-marshalling-river?
by Scott Stark
I'm working on getting the helloworld-jms quickstart from https://github.com/jbossas/quickstart.git running against an as7.1.0.Final instance, and one change I had to make was to add the jboss-marshalling-river dependency shown below. Without this I'm getting a "Could not find a marshaller factory for river marshalling strategy" failure. This seems like quite a low level dependency for a user to have to figure out. Shouldn't this be coming from either the jboss-as-naming or the jboss-as-messaging, which ever one is needing this for the protocol?
<dependencies>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-naming</artifactId>
<version>7.1.0.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.jms</groupId>
<artifactId>jboss-jms-api_1.1_spec</artifactId>
<version>1.0.0.Final</version>
<!--scope>provided</scope-->
</dependency>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-messaging</artifactId>
<version>7.1.0.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.marshalling</groupId>
<artifactId>jboss-marshalling-river</artifactId>
<version>1.3.9.GA</version>
</dependency>
</dependencies>
12 years, 9 months
org.jboss.naming.remote.client.InitialContextFactory and Context.SECURITY_PRINCIPAL/Context.SECURITY_CREDENTIALS
by Scott Stark
The org.jboss.naming.remote.client.InitialContextFactory.createCallbackHandler(Properties) method does not look for the Context.SECURITY_PRINCIPAL/Context.SECURITY_CREDENTIALS among the system properties. This means that these values either need to be passed in via a jboss-naming-client.properties or through the env passed to InitialContextFactory. Wouldn't be better if we looked for all of the following as system properties to allow system properties to be a complete specification of what is needed for a secure jndi connection?
java.naming.security.principal
java.naming.security.credentials
jboss.naming.client.security.callback.handler.class
jboss.naming.client.security.password.base64
jboss.naming.client.security.realm
12 years, 9 months
Infinispan AS7 domain quickstart deployment "fun"
by Galder Zamarreño
Hi,
I've been having a bit of "fun" deploying Infinispan AS7 quickstarts in domain mode.
1. Trying to deploy Infinispan AS7 domain quickstart (https://github.com/galderz/infinispan-quickstart/tree/t_710final/jboss-as7) into AS 7.1.0.Final fails with:
https://issues.jboss.org/browse/AS7-4048
2. This appears to be fixed in AS 7.1.1.Final but in this version, there's another error when you deploy the quickstart via the CLI:
[Server:server-four] 08:53:47,370 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "infinispan-jboss-as7.war" was rolled back with failure message JBAS014750: Operation handler failed to complete
I asked Emanuel about this and he's told me that this is fixed in master (??).
3. Right, so let's have a go at deploying the quickstart in master domain mode. Doesn't work:
[Server:server-three] 09:26:02,823 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."infinispan-jboss-as7.war".WeldService: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
[Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:83)
[Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
[Server:server-three] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
[Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
[Server:server-three] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
[Server:server-three] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
[Server:server-three] Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-001450 Interceptor method public java.lang.Object org.jboss.solder.exception.control.ExceptionHandledInterceptor.passExceptionsToSolderCatch(javax.interceptor.InvocationContext) throws java.lang.Throwable does not declare that it throws Exception.
[Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isValidBusinessMethodInterceptorMethod(InterceptorMetadataUtils.java:98)
[Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.isInterceptorMethod(InterceptorMetadataUtils.java:53)
[Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.buildMethodMap(InterceptorMetadataUtils.java:130)
[Server:server-three] at org.jboss.weld.interceptor.reader.InterceptorMetadataUtils.readMetadataForInterceptorClass(InterceptorMetadataUtils.java:38)
[Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:30)
[Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader$1.apply(DefaultMetadataCachingReader.java:28)
[Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355)
[Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184)
[Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153)
[Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69)
[Server:server-three] at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393)
[Server:server-three] at org.jboss.weld.interceptor.reader.cache.DefaultMetadataCachingReader.getInterceptorMetadata(DefaultMetadataCachingReader.java:54)
[Server:server-three] at org.jboss.weld.bean.InterceptorImpl.<init>(InterceptorImpl.java:64)
[Server:server-three] at org.jboss.weld.bean.InterceptorImpl.of(InterceptorImpl.java:59)
[Server:server-three] at org.jboss.weld.bootstrap.AbstractBeanDeployer.createInterceptor(AbstractBeanDeployer.java:228)
[Server:server-three] at org.jboss.weld.bootstrap.BeanDeployer.createBeans(BeanDeployer.java:137)
[Server:server-three] at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:204)
[Server:server-three] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)
[Server:server-three] at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
[Server:server-three] at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
[Server:server-three] ... 5 more
Kevin/Pete, any idea what's up this time?
Please, let's try to get this fixed before 7.1.2.Final is out so that we can finally have the Infinispan quickstarts working again.
Cheers,
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
12 years, 9 months
Help on service controller lifecycles
by Jeff Mesnil
Hi guys,
there are intermittent failures when updating a connection factory
attributes in messaging subsystem[1] and I tracked it down to a problem
of service states
To make a story short, when we update a connection factory, we recreate
its JNDI binding by doing a unbind() followed by a bind() on the
AS7BindingRegistry[2].
To bind a CF, we install a BindingService into the controller and set
its mode to ACTIVE.
To unbind a CF, we set its ServiceController's mode to REMOVE.
However, it occurs that when doing a unbind() followed by a bind(),
we may try to install a BindingService when it is not uninstalled yet
(it's in the DOWN/REMOVING) state (removing the Thread.sleep() in [3] to
highlight the issue)
I fix the issue locally by checking in bind() whether the service
controller exists and if it is DOWN/REMOVING wait until it is REMOVED.
But I don't like sleeping until a service controller state changes. I am
sure there is a more idiomatic/elegant way to do this.
Does someone have pointers to show me the best way to do this?
thanks,
jeff
[1] https://issues.jboss.org/browse/JBPAPP-8184
[2]
https://github.com/jmesnil/jboss-as/blob/JBPAPP-8184_connection_factory_f...
[3]
https://github.com/jmesnil/jboss-as/blob/JBPAPP-8184_connection_factory_f...
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/
12 years, 9 months
Autocompletion of most used/opened files in AS7
by Galder Zamarreño
Guys,
Let me make one suggestion. Which are the two files you're most likely to open with an editor in AS7? IMO:
standalone/configuration/standalone.xml
domain/configuration/domain.xml
So, we should strive to make autocompletion of these as clean/quick/painless as possible. The following does not help:
-rw-r--r--@ 1 g admin 77716 Mar 22 08:50 domain.xml
drwxr-xr-x 7 g admin 238 Mar 22 08:52 domain_xml_history
Why? Because once you start typing the actual file name, you have to skip the history file.
So, can we please rename the history xml file to something else that does no start with domain?
Same thing for standalone.
Cheers,
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
12 years, 9 months
What is this dependency issue in quickstarts/kitchensink-ear
by Scott Stark
I can package up the quickstarts/kitchensink-ear contents, but when I run the jboss-as:deploy step, it rechecks the build and now finds that the org.jboss.as.quickstarts:jboss-as-kitchensink-ear-ejb:jar:7.1.1-SNAPSHOT is missing. What is going on there?
I'm using using the current git://github.com/jbossas/quickstart.git head.
[starksm@libra kitchensink-ear]$ mvn package
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] JBoss AS Quickstarts: Kitchensink EAR
[INFO] JBoss AS Quickstarts: Kitchensink EAR: EJB Module
[INFO] JBoss AS Quickstarts: Kitchensink EAR: WAR Module
[INFO] JBoss AS Quickstarts: Kitchensink EAR: EAR Module
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Kitchensink EAR 7.1.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Kitchensink EAR: EJB Module 7.1.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ jboss-as-kitchensink-ear-ejb ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ jboss-as-kitchensink-ear-ejb ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ jboss-as-kitchensink-ear-ejb ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-kitchensink-ear-ejb ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.4.3:test (default-test) @ jboss-as-kitchensink-ear-ejb ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-ejb-plugin:2.3:ejb (default-ejb) @ jboss-as-kitchensink-ear-ejb ---
[INFO] Building EJB jboss-as-kitchensink-ear-ejb-7.1.1-SNAPSHOT with EJB version 3.1
[INFO] Building jar: /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-ejb/target/jboss-as-kitchensink-ear-ejb-7.1.1-SNAPSHOT.jar
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Kitchensink EAR: WAR Module 7.1.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ jboss-as-kitchensink-ear-web ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-web/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ jboss-as-kitchensink-ear-web ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ jboss-as-kitchensink-ear-web ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-web/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-kitchensink-ear-web ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.7.2:test (default-test) @ jboss-as-kitchensink-ear-web ---
[INFO] No tests to run.
[INFO] Surefire report directory: /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-web/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-war-plugin:2.1.1:war (default-war) @ jboss-as-kitchensink-ear-web ---
[INFO] Packaging webapp
[INFO] Assembling webapp [jboss-as-kitchensink-ear-web] in [/home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-web/target/jboss-as-kitchensink-ear-web-7.1.1-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-web/src/main/webapp]
[INFO] Webapp assembled in [37 msecs]
[INFO] Building war: /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-web/target/jboss-as-kitchensink-ear-web-7.1.1-SNAPSHOT.war
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Kitchensink EAR: EAR Module 7.1.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-ear-plugin:2.6:generate-application-xml (default-generate-application-xml) @ jboss-as-kitchensink-ear-ear ---
[INFO] Generating application.xml
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ jboss-as-kitchensink-ear-ear ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-ear/src/main/resources
[INFO]
[INFO] --- maven-ear-plugin:2.6:ear (default-ear) @ jboss-as-kitchensink-ear-ear ---
[INFO] Copying artifact[war:org.jboss.as.quickstarts:jboss-as-kitchensink-ear-web:7.1.1-SNAPSHOT] to[jboss-as-kitchensink-ear-web-7.1.1-SNAPSHOT.war]
[INFO] Copying artifact[ejb:org.jboss.as.quickstarts:jboss-as-kitchensink-ear-ejb:7.1.1-SNAPSHOT] to[jboss-as-kitchensink-ear-ejb-7.1.1-SNAPSHOT.jar]
[INFO] Copy ear sources to /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-ear/target/jboss-as-kitchensink-ear
[INFO] Could not find manifest file: /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-ear/target/jboss-as-kitchensink-ear/META-INF/MANIFEST.MF - Generating one
[INFO] Building jar: /home/starksm/quickstarts/kitchensink-ear/jboss-as-kitchensink-ear-ear/target/jboss-as-kitchensink-ear.ear
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss AS Quickstarts: Kitchensink EAR ............. SUCCESS [0.003s]
[INFO] JBoss AS Quickstarts: Kitchensink EAR: EJB Module . SUCCESS [0.921s]
[INFO] JBoss AS Quickstarts: Kitchensink EAR: WAR Module . SUCCESS [0.793s]
[INFO] JBoss AS Quickstarts: Kitchensink EAR: EAR Module . SUCCESS [0.241s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.212s
[INFO] Finished at: Tue Mar 20 00:02:54 PDT 2012
[INFO] Final Memory: 6M/15M
[INFO] ------------------------------------------------------------------------
[starksm@libra kitchensink-ear]$ mvn jboss-as:deploy
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] JBoss AS Quickstarts: Kitchensink EAR
[INFO] JBoss AS Quickstarts: Kitchensink EAR: EJB Module
[INFO] JBoss AS Quickstarts: Kitchensink EAR: WAR Module
[INFO] JBoss AS Quickstarts: Kitchensink EAR: EAR Module
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Kitchensink EAR 7.1.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- jboss-as-maven-plugin:7.1.0.Final:deploy (default-cli) @ jboss-as-kitchensink-ear ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Kitchensink EAR: EJB Module 7.1.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- jboss-as-maven-plugin:7.1.0.Final:deploy (default-cli) @ jboss-as-kitchensink-ear-ejb ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Kitchensink EAR: WAR Module 7.1.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss AS Quickstarts: Kitchensink EAR ............. SUCCESS [0.385s]
[INFO] JBoss AS Quickstarts: Kitchensink EAR: EJB Module . SUCCESS [0.174s]
[INFO] JBoss AS Quickstarts: Kitchensink EAR: WAR Module . FAILURE [0.072s]
[INFO] JBoss AS Quickstarts: Kitchensink EAR: EAR Module . SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.078s
[INFO] Finished at: Tue Mar 20 00:03:01 PDT 2012
[INFO] Final Memory: 6M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project jboss-as-kitchensink-ear-web: Could not resolve dependencies for project org.jboss.as.quickstarts:jboss-as-kitchensink-ear-web:war:7.1.1-SNAPSHOT: Could not find artifact org.jboss.as.quickstarts:jboss-as-kitchensink-ear-ejb:jar:7.1.1-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce...
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :jboss-as-kitchensink-ear-web
12 years, 9 months
How to report exception cause in AS7 consoles?
by Jeff Mesnil
Hi,
I am working on a messaging issue[1] to add more contextual info when
reporting messaging failure on CLI operations.
In this case, a JMS queue can not been added because the user specified
an invalid filter.
We throw a StartException with a cause Throwable (corresponding to the
invalid filter parsing) but the CLI console displays only the
StartException's message 'failed to create queue' and not its cause.
I have several ways to fix the issue and I am not sure which one is the
more appropriate for AS7:
1) I can fix the code in the messaging subsystem to append the cause's
localized message to the StartException message every time I throw one
2) In the controller code, when I report the StartException to the user,
I append the cause's l10ned message (if there is a cause) to
StartException.toString() message (this impacts all thrown
StartException, not only those from messaging subsystem)
3) I update StartException.toString() to append the cause message
I prefer (3) since as it is the only place where I would have to deal
with this but I don't realize the whole implication.
More generally, are there guidelines for reporting errors in AS7 CLI &
Web consoles? Are stacktraces acceptable? Is it up to every subsystems
to "prettify" their exceptions to provide all info in the message?
thanks,
jeff
[1] https://issues.jboss.org/browse/AS7-1735
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/
12 years, 9 months
NPEs when EE subsystem is disabled
by Carlo de Wolf
This is mostly just mierenneuken.
If the EE subsystem is disabled you get interesting NPEs from other subsystems (for obvious reasons).
09:27:12,934 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."node-info.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."node-info.war".PARSE: Failed to process phase PARSE of deployment "node-info.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_b147-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_b147-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_b147-icedtea]
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.processors.EjbContextJndiBindingProcessor.deploy(EjbContextJndiBindingProcessor.java:68)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]
... 5 more
Do we want to have a more friendly message when dependent subsystems are not available?
Carlo
12 years, 9 months
