May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBASMP-79) Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase

by James Perkins (JIRA)

James Perkins created JBASMP-79: ----------------------------------- Summary: Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase Key: JBASMP-79 URL: https://issues.jboss.org/browse/JBASMP-79 Project: JBoss AS Maven Plugins Issue Type: Bug Components: deploy Reporter: Martin Basovnik If I try to deploy a deployment just after the server reloading it sometimes fails: {code} 10:20:32,921 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("add") failed - address: ([("deployment" => "jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar\")]" {code} https://github.com/jbossas/jboss-as-maven-plugin/blob/7.6.Final/src/main/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-78) Requirement to ser JBOSS_HOME as soon as commands are executed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-78?page=com.atlassian.jira.plugin.... ] James Perkins closed JBASMP-78. ------------------------------- Resolution: Duplicate Issue > Requirement to ser JBOSS_HOME as soon as commands are executed > -------------------------------------------------------------- > > Key: JBASMP-78 > URL: https://issues.jboss.org/browse/JBASMP-78 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Components: common > Affects Versions: 7.7.Final > Environment: This at least happens on Windows Machines, Haven't tried on Linux/Unix based machines. > Reporter: Christofer Dutz > > If I run jboss-as:run without any configuration and no JBoss installed, the plugin correctly downloads JBoss and unpacks it in my ear projects target directory. It also correctly starts the server and tries to deploy the application. Unfortunately I need to do some configuration first, so I added some "before-deployment" commands. Now the build fails with a message, that the JBOSS_HOME variable isn't set. As soon as I set it to the "target/jboss-as-run/jboss-as-7.1.1.Final" it is able to continue. Would be good however if the plugin could already ensure the variable from being set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-76) Start goal occasionally end prematurely on standalone server

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-76?page=com.atlassian.jira.plugin.... ] James Perkins reassigned JBASMP-76: ----------------------------------- Assignee: James Perkins > Start goal occasionally end prematurely on standalone server > ------------------------------------------------------------ > > Key: JBASMP-76 > URL: https://issues.jboss.org/browse/JBASMP-76 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Affects Versions: 7.7.Final > Environment: JBoss AS 7.2.0 > Reporter: Daniele Gaffuri > Assignee: James Perkins > Attachments: patch.diff > > > When server startup time is over 10 seconds start goal ends prematurely, because test on server-state property checks "starting" and "stopping" states in wrong case (constants are defined in uppercase but are retured in lowercase by client call) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6663) NPE o.j.a.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238)

by Darryl Miles (JIRA)

Darryl Miles created WFLY-6663: ---------------------------------- Summary: NPE o.j.a.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238) Key: WFLY-6663 URL: https://issues.jboss.org/browse/WFLY-6663 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 10.0.0.Final Environment: Win7 64bit + JDK8 64bit Reporter: Darryl Miles 1 in 8 deployments fail to deploy, usually a redeploy fixes it. If there is anyway to get a module state logging out of it, I can send over two logs to compare, one that deploy ok and one that fails. I guess there is a race bug there somewhere. 09:42:01,687 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 529) MSC000001: Failed to start service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124) at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138) at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) ... 6 more Caused by: javax.ejb.EJBException: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterceptor.java:83) at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:91) at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:106) at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:58) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) ... 11 more Caused by: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:319) at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:97) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:103) ... 26 more Caused by: javax.naming.NamingException: WFLYNAM0062: Failed to lookup env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb [Root exception is java.lang.RuntimeException: WFLYEJB0423: Could not create session for stateful bean MainEjbImpl] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:157) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:316) ... 43 more Caused by: java.lang.RuntimeException: WFLYEJB0423: Could not create session for stateful bean MainEjbImpl at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:99) at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:143) ... 48 more Caused by: java.lang.NullPointerException at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238) at org.jboss.as.ejb3.remote.LocalEjbReceiver.openSession(LocalEjbReceiver.java:296) at org.jboss.ejb.client.EJBClient.createSessionWithPossibleRetries(EJBClient.java:225) at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:202) at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:176) at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:97) ... 49 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6383) Entities using Extended PersistentContext are not managed

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-6383?page=com.atlassian.jira.plugin.... ] Yeray Santana Borges updated WFLY-6383: --------------------------------------- Attachment: WFLY-6383.zip Added a maven project with the example files > Entities using Extended PersistentContext are not managed > --------------------------------------------------------- > > Key: WFLY-6383 > URL: https://issues.jboss.org/browse/WFLY-6383 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Environment: WildFLy 10.0.0.Final > Mac > Reporter: Rakesh K. Cherukuri > Labels: Extended, JPA, Persistence, PersistenceContext > Attachments: AtInjectedStatefulEjbClient.java, CdiStatefulEmployeeBean.java, StatefulEjb.java, StatefulEjbClient.java, WFLY-6383.zip > > > Entities using Extended PersistentContext are not managed in a Stateful bean. > Attached are the bean class and the client servlet class -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6383) Entities using Extended PersistentContext are not managed

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-6383?page=com.atlassian.jira.plugin.... ] Yeray Santana Borges commented on WFLY-6383: -------------------------------------------- Hi [~rakcheru] Can you see any error trace in the server log? I have been playing a little with your files and both options works fine in WildFLy 10.0.0.Final (Mac Os, Oracle JDK 1.8), at least using H2 in memory data base, but I think that the database type is not relevant in this issue. > Entities using Extended PersistentContext are not managed > --------------------------------------------------------- > > Key: WFLY-6383 > URL: https://issues.jboss.org/browse/WFLY-6383 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Environment: WildFLy 10.0.0.Final > Mac > Reporter: Rakesh K. Cherukuri > Labels: Extended, JPA, Persistence, PersistenceContext > Attachments: AtInjectedStatefulEjbClient.java, CdiStatefulEmployeeBean.java, StatefulEjb.java, StatefulEjbClient.java > > > Entities using Extended PersistentContext are not managed in a Stateful bean. > Attached are the bean class and the client servlet class -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-69) Enable the patch command

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-69?page=com.atlassian.jira.plugin.... ] James Perkins closed JBASMP-69. ------------------------------- Resolution: Won't Do New features are only going into the [WildFly Maven Plugin|https://issues.jboss.org/browse/WFMP]. > Enable the patch command > ------------------------ > > Key: JBASMP-69 > URL: https://issues.jboss.org/browse/JBASMP-69 > Project: JBoss AS Maven Plugins > Issue Type: Feature Request > Affects Versions: 7.5.Final > Reporter: Shaun Appleton > > A new patching mechanism was introduced for EAP. This involves the new cli command: patch > This is a request to extend the maven plugin to be able to run the patch command as some customers would like to use this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-32) Overriding the deployment name overrides the web-context

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-32?page=com.atlassian.jira.plugin.... ] James Perkins closed JBASMP-32. ------------------------------- Resolution: Won't Do > Overriding the deployment name overrides the web-context > -------------------------------------------------------- > > Key: JBASMP-32 > URL: https://issues.jboss.org/browse/JBASMP-32 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Reporter: James Perkins > > http://stackoverflow.com/questions/14241493/jboss-7-deployment-issues-wit... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-107) jboss-logging-tools don't include the license file

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-107?page=com.atlassian.jira.plugi... ] James Perkins commented on LOGTOOL-107: --------------------------------------- The attached PR adds a {{LICENSE.txt}} file to the {{META-INF}} directory in both the source and binary JAR's. {code} jperkins@localhost ~/projects/jboss/logging/jboss-logging-tools (LOGTOOL-107) $ jar tf annotations/target/jboss-logging-annotations-2.1.0.Alpha1-SNAPSHOT-sources.jar META-INF/MANIFEST.MF META-INF/ org/ org/jboss/ org/jboss/logging/ org/jboss/logging/annotations/ org/jboss/logging/annotations/ConstructType.java org/jboss/logging/annotations/Cause.java org/jboss/logging/annotations/Once.java org/jboss/logging/annotations/Transform.java org/jboss/logging/annotations/Suppressed.java org/jboss/logging/annotations/Fields.java org/jboss/logging/annotations/Property.java META-INF/INDEX.LIST org/jboss/logging/annotations/FormatWith.java org/jboss/logging/annotations/LogMessage.java org/jboss/logging/annotations/LoggingClass.java org/jboss/logging/annotations/MessageBundle.java org/jboss/logging/annotations/Param.java org/jboss/logging/annotations/ValidIdRanges.java org/jboss/logging/annotations/Field.java org/jboss/logging/annotations/Properties.java org/jboss/logging/annotations/Signature.java org/jboss/logging/annotations/Message.java org/jboss/logging/annotations/Pos.java org/jboss/logging/annotations/ValidIdRange.java org/jboss/logging/annotations/MessageLogger.java META-INF/LICENSE.txt {code} If this doesn't look correct just let me know. > jboss-logging-tools don't include the license file > -------------------------------------------------- > > Key: LOGTOOL-107 > URL: https://issues.jboss.org/browse/LOGTOOL-107 > Project: Log Tool > Issue Type: Bug > Reporter: gil cattaneo > Assignee: James Perkins > > Not available LICENSE file in source directory structure > Please. Added license and copyright notice. > the fedora pakaging guideline is very strictly precise about this problem > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging... > thanks > regards -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6620) Remove typo from BAControler interface and its implementations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6620?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-6620: ------------------------------------- Can you add a note as to when this is required for, e.g. a link to a SHA from Narayana > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: WFLY-6620 > URL: https://issues.jboss.org/browse/WFLY-6620 > Project: WildFly > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016