[JBoss JIRA] (WFLY-2221) NPE in BinderService
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-2221?page=com.atlassian.jira.plugin.... ]
Eduardo Martins commented on WFLY-2221:
---------------------------------------
Jesper, this error should be masking another issue, probably as result of the resource binding logic changes, wrt default EE bindings, but no harm in BinderService being prepared for such case. Thanks.
> NPE in BinderService
> --------------------
>
> Key: WFLY-2221
> URL: https://issues.jboss.org/browse/WFLY-2221
> Project: WildFly
> Issue Type: Bug
> Components: Naming
> Affects Versions: 8.0.0.Beta1
> Reporter: Jesper Pedersen
> Assignee: Eduardo Martins
>
> {noformat}
> 11:03:33,766 ERROR [org.jboss.msc.service] (MSC service thread 1-4) MSC000002: Invocation of listener "org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor$BinderReleaseListener@2d6f9ce1" failed: java.lang.NullPointerException
> at org.jboss.as.naming.service.BinderService.release(BinderService.java:100) [wildfly-naming-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor$BinderReleaseListener.transition(ModuleJndiBindingProcessor.java:302) [wildfly-ee-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1533) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:51) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:2095) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {noformat}
> Master from 3 days ago
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBASMP-52) jboss-as:deploy deploys ear but doesn't deploy contained ejb module
by Matías Blasi (JIRA)
[ https://issues.jboss.org/browse/JBASMP-52?page=com.atlassian.jira.plugin.... ]
Matías Blasi commented on JBASMP-52:
------------------------------------
Perfect! I'll try with that.
I'm deploying on JBoss AS 7.1.1-Final.
Let you know any news.
Regards,
Matías.
> jboss-as:deploy deploys ear but doesn't deploy contained ejb module
> -------------------------------------------------------------------
>
> Key: JBASMP-52
> URL: https://issues.jboss.org/browse/JBASMP-52
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Components: deploy
> Affects Versions: 7.4.Final
> Environment: Linux hostname 3.7.10-gentoo #1 SMP Fri Aug 30 17:01:59 ART 2013 x86_64 Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz GenuineIntel GNU/Linux
> Reporter: Matías Blasi
> Assignee: James Perkins
>
> I have a simple ear application (build with maven-ear-plugin).
> This application contains just a persistence-unit definition (persistence.xml) and a ejb-module.
> The ejb module is another maven build, containing some ejb3, handled with maven-ejb-plugin.
> The ear file is correctly built:
> myapp.ear
> |
> + META-INF/application.xml
> + lib/allmylibs.jar
> + myejb.jar
> When trying to deploy the ear with the jboss-as:deploy, the application is deployed (the persistence unit deployment logs in server.log), but no ejb is registered, anyway, no errors in log, and BUILD SUCCESFUL after mvn command.
> Finally, an ear file is present under $JBOSS_HOME/standalone/data/content
> The strange thing is that if I get that generated ear file, I can succesfully deploy it through the management console, or by copying it to a folder scanned by a deployment-scanner (in both cases the ejbs are correctly deployed)
> Nothing found in google! :(
> I tried with all the plugin version from 7.1.1 to 7.4.
> Also a lot of tries with different maven-ear-plugin and maven-jboss-as-plugin configuration options.... no lucky after two days of work.
> Regards,
> Matías.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBASMP-52) jboss-as:deploy deploys ear but doesn't deploy contained ejb module
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-52?page=com.atlassian.jira.plugin.... ]
James Perkins commented on JBASMP-52:
-------------------------------------
What is the target runtime, JBoss AS 7.x, WildFly or EAP? Also which version of the runtime? The quick start example seems to work okay, maybe you could try deploying it just to see if it works https://github.com/jboss-developer/jboss-eap-quickstarts/tree/master/ejb-...
> jboss-as:deploy deploys ear but doesn't deploy contained ejb module
> -------------------------------------------------------------------
>
> Key: JBASMP-52
> URL: https://issues.jboss.org/browse/JBASMP-52
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Components: deploy
> Affects Versions: 7.4.Final
> Environment: Linux hostname 3.7.10-gentoo #1 SMP Fri Aug 30 17:01:59 ART 2013 x86_64 Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz GenuineIntel GNU/Linux
> Reporter: Matías Blasi
> Assignee: James Perkins
>
> I have a simple ear application (build with maven-ear-plugin).
> This application contains just a persistence-unit definition (persistence.xml) and a ejb-module.
> The ejb module is another maven build, containing some ejb3, handled with maven-ejb-plugin.
> The ear file is correctly built:
> myapp.ear
> |
> + META-INF/application.xml
> + lib/allmylibs.jar
> + myejb.jar
> When trying to deploy the ear with the jboss-as:deploy, the application is deployed (the persistence unit deployment logs in server.log), but no ejb is registered, anyway, no errors in log, and BUILD SUCCESFUL after mvn command.
> Finally, an ear file is present under $JBOSS_HOME/standalone/data/content
> The strange thing is that if I get that generated ear file, I can succesfully deploy it through the management console, or by copying it to a folder scanned by a deployment-scanner (in both cases the ejbs are correctly deployed)
> Nothing found in google! :(
> I tried with all the plugin version from 7.1.1 to 7.4.
> Also a lot of tries with different maven-ear-plugin and maven-jboss-as-plugin configuration options.... no lucky after two days of work.
> Regards,
> Matías.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBASMP-52) jboss-as:deploy deploys ear but doesn't deploy contained ejb module
by Matías Blasi (JIRA)
[ https://issues.jboss.org/browse/JBASMP-52?page=com.atlassian.jira.plugin.... ]
Matías Blasi commented on JBASMP-52:
------------------------------------
Hi James.
First of all thank you for your support.
The answer is YES.
My ear pom has the jbss-as-maven-plugin defined as follows:
<plugin>
<groupId>org.jboss.as.plugins</groupId>
<artifactId>jboss-as-maven-plugin</artifactId>
<version>7.4.Final</version>
<configuration>
<name>mercury-ear</name>
<force>true</force>
</configuration>
</plugin>
And finally, I run:
# mvn jboss-as:deploy in that ear project.
The ear deploy process succeses:
Maven console:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
...
[INFO] task-segment: [jboss-as:deploy]
[INFO] ------------------------------------------------------------------------
...
[INFO] [jboss-as:deploy {execution: default-cli}]
oct 02, 2013 10:57:30 AM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.3.GA
oct 02, 2013 10:57:30 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.3.GA
oct 02, 2013 10:57:30 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.3.GA
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15 seconds
[INFO] Finished at: Wed Oct 02 10:57:35 ART 2013
[INFO] Final Memory: 23M/246M
[INFO] ------------------------------------------------------------------------
Jboss server log:
INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "mercury.ear"
and later executions:
INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "mercury.ear" with deployment "mercury.ear"
But no EJB deployment is triggered in JBoss.
Regards,
Matías.
> jboss-as:deploy deploys ear but doesn't deploy contained ejb module
> -------------------------------------------------------------------
>
> Key: JBASMP-52
> URL: https://issues.jboss.org/browse/JBASMP-52
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Components: deploy
> Affects Versions: 7.4.Final
> Environment: Linux hostname 3.7.10-gentoo #1 SMP Fri Aug 30 17:01:59 ART 2013 x86_64 Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz GenuineIntel GNU/Linux
> Reporter: Matías Blasi
> Assignee: James Perkins
>
> I have a simple ear application (build with maven-ear-plugin).
> This application contains just a persistence-unit definition (persistence.xml) and a ejb-module.
> The ejb module is another maven build, containing some ejb3, handled with maven-ejb-plugin.
> The ear file is correctly built:
> myapp.ear
> |
> + META-INF/application.xml
> + lib/allmylibs.jar
> + myejb.jar
> When trying to deploy the ear with the jboss-as:deploy, the application is deployed (the persistence unit deployment logs in server.log), but no ejb is registered, anyway, no errors in log, and BUILD SUCCESFUL after mvn command.
> Finally, an ear file is present under $JBOSS_HOME/standalone/data/content
> The strange thing is that if I get that generated ear file, I can succesfully deploy it through the management console, or by copying it to a folder scanned by a deployment-scanner (in both cases the ejbs are correctly deployed)
> Nothing found in google! :(
> I tried with all the plugin version from 7.1.1 to 7.4.
> Also a lot of tries with different maven-ear-plugin and maven-jboss-as-plugin configuration options.... no lucky after two days of work.
> Regards,
> Matías.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (WFLY-2222) SecurityExceptions when starting server with signed jars in an exploded app deployment
by Matt Fluet (JIRA)
[ https://issues.jboss.org/browse/WFLY-2222?page=com.atlassian.jira.plugin.... ]
Matt Fluet commented on WFLY-2222:
----------------------------------
Sure...we will setup our patched server with this alternative fix and let the automated restarts continue over the weekend. Will report status back here on Monday.
> SecurityExceptions when starting server with signed jars in an exploded app deployment
> --------------------------------------------------------------------------------------
>
> Key: WFLY-2222
> URL: https://issues.jboss.org/browse/WFLY-2222
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Reporter: Matt Fluet
> Assignee: David Lloyd
> Priority: Critical
> Attachments: 0001-Fix-ClassLoader-SecurityException-with-jar-certifica.patch
>
>
> This issue is directly related to https://issues.jboss.org/browse/AS7-2724, where signed jars are sometimes throwing a security exception when the server starts up and then classes cannot be loaded out of certain packages (appears to be some sort of a concurrency issue).
> The fix for that issue was applied to JarFileResourceLoader here: https://github.com/jboss-modules/jboss-modules/commit/8cf33f5c02c0c4bf6f9...
> However, our application is exploded, so the VFSResourceLoader needs a similar fix. I will attach a git patch file with the change we're proposing.
> To test the theory, we applied the patch to one server and left another as is as a control...we then left a process running that continually restarted the server for 3 days. The control server hit the SecurityException problem 5 times, and the patched server didn't show it at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (WFLY-2223) EE ConcurrentContextService name conflict
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-2223?page=com.atlassian.jira.plugin.... ]
Eduardo Martins updated WFLY-2223:
----------------------------------
Summary: EE ConcurrentContextService name conflict (was: Duplicated EE ConcurrentContextService)
> EE ConcurrentContextService name conflict
> -----------------------------------------
>
> Key: WFLY-2223
> URL: https://issues.jboss.org/browse/WFLY-2223
> Project: WildFly
> Issue Type: Feature Request
> Components: EE
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
>
> When there is a conflict between modules wrt their names, there is a DUP that solves the conflict and sets new name(s) in the EE Module Description, but the problem is that such change is not propagated into ConcurrentContexts, which use such name to compute their MSC service name, meaning the modules in conflict will try to install services with same name, failing the deploy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (WFLY-2223) Duplicated EE ConcurrentContextService
by Eduardo Martins (JIRA)
Eduardo Martins created WFLY-2223:
-------------------------------------
Summary: Duplicated EE ConcurrentContextService
Key: WFLY-2223
URL: https://issues.jboss.org/browse/WFLY-2223
Project: WildFly
Issue Type: Feature Request
Components: EE
Reporter: Eduardo Martins
Assignee: Eduardo Martins
When there is a conflict between modules wrt their names, there is a DUP that solves the conflict and sets new name(s) in the EE Module Description, but the problem is that such change is not propagated into ConcurrentContexts, which use such name to compute their MSC service name, meaning the modules in conflict will try to install services with same name, failing the deploy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBASMP-52) jboss-as:deploy deploys ear but doesn't deploy contained ejb module
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-52?page=com.atlassian.jira.plugin.... ]
James Perkins commented on JBASMP-52:
-------------------------------------
Where do you have the jboss-as-maven-plugin defined? In the EAR POM?
> jboss-as:deploy deploys ear but doesn't deploy contained ejb module
> -------------------------------------------------------------------
>
> Key: JBASMP-52
> URL: https://issues.jboss.org/browse/JBASMP-52
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Components: deploy
> Affects Versions: 7.4.Final
> Environment: Linux hostname 3.7.10-gentoo #1 SMP Fri Aug 30 17:01:59 ART 2013 x86_64 Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz GenuineIntel GNU/Linux
> Reporter: Matías Blasi
> Assignee: James Perkins
>
> I have a simple ear application (build with maven-ear-plugin).
> This application contains just a persistence-unit definition (persistence.xml) and a ejb-module.
> The ejb module is another maven build, containing some ejb3, handled with maven-ejb-plugin.
> The ear file is correctly built:
> myapp.ear
> |
> + META-INF/application.xml
> + lib/allmylibs.jar
> + myejb.jar
> When trying to deploy the ear with the jboss-as:deploy, the application is deployed (the persistence unit deployment logs in server.log), but no ejb is registered, anyway, no errors in log, and BUILD SUCCESFUL after mvn command.
> Finally, an ear file is present under $JBOSS_HOME/standalone/data/content
> The strange thing is that if I get that generated ear file, I can succesfully deploy it through the management console, or by copying it to a folder scanned by a deployment-scanner (in both cases the ejbs are correctly deployed)
> Nothing found in google! :(
> I tried with all the plugin version from 7.1.1 to 7.4.
> Also a lot of tries with different maven-ear-plugin and maven-jboss-as-plugin configuration options.... no lucky after two days of work.
> Regards,
> Matías.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (WFLY-2222) SecurityExceptions when starting server with signed jars in an exploded app deployment
by Matt Fluet (JIRA)
[ https://issues.jboss.org/browse/WFLY-2222?page=com.atlassian.jira.plugin.... ]
Matt Fluet updated WFLY-2222:
-----------------------------
Attachment: 0001-Fix-ClassLoader-SecurityException-with-jar-certifica.patch
Attaching a patch file with the fix for the VFSResourceLoader problem
> SecurityExceptions when starting server with signed jars in an exploded app deployment
> --------------------------------------------------------------------------------------
>
> Key: WFLY-2222
> URL: https://issues.jboss.org/browse/WFLY-2222
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Reporter: Matt Fluet
> Assignee: David Lloyd
> Priority: Critical
> Attachments: 0001-Fix-ClassLoader-SecurityException-with-jar-certifica.patch
>
>
> This issue is directly related to https://issues.jboss.org/browse/AS7-2724, where signed jars are sometimes throwing a security exception when the server starts up and then classes cannot be loaded out of certain packages (appears to be some sort of a concurrency issue).
> The fix for that issue was applied to JarFileResourceLoader here: https://github.com/jboss-modules/jboss-modules/commit/8cf33f5c02c0c4bf6f9...
> However, our application is exploded, so the VFSResourceLoader needs a similar fix. I will attach a git patch file with the change we're proposing.
> To test the theory, we applied the patch to one server and left another as is as a control...we then left a process running that continually restarted the server for 3 days. The control server hit the SecurityException problem 5 times, and the patched server didn't show it at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months