[JBoss JIRA] (AS7-6779) AS7.1 jars run against as7.2/eap6.1 cause test case (eclipse) to hang
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6779?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6779:
----------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 927318|https://bugzilla.redhat.com/show_bug.cgi?id=927318] from POST to MODIFIED
> AS7.1 jars run against as7.2/eap6.1 cause test case (eclipse) to hang
> ---------------------------------------------------------------------
>
> Key: AS7-6779
> URL: https://issues.jboss.org/browse/AS7-6779
> Project: Application Server 7
> Issue Type: Bug
> Components: Remoting
> Reporter: Rob Stryker
> Assignee: Emanuel Muckenhuber
> Priority: Blocker
> Attachments: AS7-6779.out2.txt, AS7-6779.stack.txt, out.zip
>
>
> Somewhere along the line recently, EAP6.1 / AS 7.2 has a regression in remoting or xnio somehow, and this is causing blocking problems for tools.
> Recall:
> 1) JBossTools bundles a set of jars capable of communicating with a running application server
> 2) This single set of jars must be capable of communicating with all servers in the 7.x stream
> 3) Bundling a second set of jars is not easily accomplished, but could be possible
> And:
> 4) Using the as7.1.0 jars against eap6.1 in a specific unit test causes eclipse to hang
> The basic code of our test case (once we get rid of the jbt stuff wrapped around it) is basically as follows:
> {code}
> this.client = ModelControllerClient.Factory.create(details.getHost(), details.getManagementPort(),
> getCallbackHandler());
> this.manager = ServerDeploymentManager.Factory.create(client);
> DeploymentPlanBuilder builder = manager.newDeploymentPlan().replace(name, file);
> try {
> DeploymentAction action = builder.getLastAction();
> Future<ServerDeploymentPlanResult> planResult = manager.execute(builder.build());
> // FREEZE HERE
> // This is "DeploymentOperationResult.getStatus() in the stack trace
> ServerDeploymentActionResult actionResult = planResult.get().getDeploymentActionResult(action.getId());
> IStatus status = createStatus(action.getDeploymentUnitUniqueName(), action.getType().name(), actionResult);
> } catch (Exception e) {
> throw new JBoss7ManangerException(e);
> }
> {code}
> The actual stack trace is:
> {code}
> Thread [main] (Suspended)
> owns: RunnableLock (id=461)
> waiting for: ActiveOperationSupport$ActiveOperationImpl<T,A> (id=462)
> Object.wait(long) line: not available [native method]
> ActiveOperationSupport$ActiveOperationImpl<T,A>(Object).wait() line: 503
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).await() line: 192
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).get() line: 266
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get() line: 363
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get() line: 317
> ServerDeploymentPlanResultFuture.get() line: 76
> ServerDeploymentPlanResultFuture.get() line: 42
> DeploymentOperationResult.getStatus() line: 52
> AS7ManagerTestUtils.waitUntilFinished(IJBoss7DeploymentResult) line: 93
> AS7ManagerIntegrationTest.canReplaceWar() line: 129
> {code}
> The list of jars we are using to communicate with the server are:
> {code}
> jboss-as-controller-client-7.1.0.Final.jar
> jboss-as-protocol-7.1.0.Final.jar
> jboss-dmr-1.1.1.Final.jar
> jboss-logging-3.1.0.GA.jar
> jboss-marshalling-1.3.9.GA.jar
> jboss-remoting-3.2.7.GA.jar
> jboss-sasl-1.0.0.Final.jar
> jboss-threads-2.0.0.GA.jar
> xnio-api-3.0.3.GA.jar
> xnio-nio-3.0.3.GA.jar
> {code}
> It was suggested in irc by ctomc that we simply replace the following jars with new jars from jboss-as 7.2 / eap6.1:
> {code}
> jboss-remoting-3.2.7.GA.jar -> 3.2.15.GA
> xnio-api-3.0.3.GA.jar -> 3.0.7
> xnio-nio-3.0.3.GA.jar -> 3.0.7
> {code}
> This approach also failed, with the following stack trace:
> {code}
> java.lang.NoClassDefFoundError: org/xnio/Cancellable
> (sic)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:59)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:211)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:173)
> {code}
> So it is obvious that jboss-as-controller jar from as-7.1 requires classes that are no longer present in xnio. If this is the case, it would indicate that xnio has REMOVED classes from its jar during an incremental version from 3.0.3 to 3.0.7, which would constitute an API breakage.
> So clearly for us, updating only remoting and xnio does not work. The next possible solution would be to update ALL jars, however, this led to a similar situation when using AS7.2 / Eap 6.1 jars to communicate with an AS 7.0.0 server. Again, similar to what was mentioned above, all tests passed EXCEPT the test above. The test above failed with an almost identical stack trace:
> {code}
> Thread [main] (Suspended)
> owns: RunnableLock (id=160)
> waiting for: ActiveOperationSupport$ActiveOperationImpl<T,A> (id=161)
> Object.wait(long) line: not available [native method]
> ActiveOperationSupport$ActiveOperationImpl<T,A>(Object).wait() line: 503
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).await() line: 192
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).get() line: 266
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture(AbstractDelegatingAsyncFuture<T>).get() line: 100
> ServerDeploymentPlanResultFuture.get() line: 76
> ServerDeploymentPlanResultFuture.get() line: 42
> DeploymentOperationResult.getStatus() line: 52
> AS7ManagerTestUtils.waitUntilFinished(IJBoss7DeploymentResult) line: 93
> AS7ManagerTestUtils.quietlyUndeploy(String, AS71Manager) line: 76
> AS7ManagerIntegrationTest.canReplaceWar() line: 135
> {code}
> No matter how you look at it, the contract has been broken. JBossTools now is looking for a specific set of jars which care capable of communicating with AS7.0, 7.1, 7.2, eap6.0, 6.1, jpp6.0, etc. Without a set of jars that can communicate with all of these servers, our tools will need to implement drastic workarounds or bundle several versions of the app server's jars within it.
> It's interesting to me that the as7.1 jars work against everything except eap6.1, and yet, the eap6.1 jars work against everything except as7.0.0.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6727) Modular build not in sync with modules directory structure
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6727?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6727:
----------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 947145|https://bugzilla.redhat.com/show_bug.cgi?id=947145] from POST to MODIFIED
> Modular build not in sync with modules directory structure
> ----------------------------------------------------------
>
> Key: AS7-6727
> URL: https://issues.jboss.org/browse/AS7-6727
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Labels: Karaf
>
> {code}
> [echo] Static modules: [org.jboss.as.standalone,org.jboss.as.domain-http-error-context,,, org.jboss.logging, org.jboss.vfs, org.slf4j, org.jboss.logging.jul-to-slf4j-stub]
> [java] Exception in thread "main" java.io.FileNotFoundException: /Users/tdiesler/git/jboss-as/build-modular/../build/src/main/resources/modules/org/jboss/as/logging/main/module.xml (No such file or directory)
> [java] at java.io.FileInputStream.open(Native Method)
> [java] at java.io.FileInputStream.<init>(FileInputStream.java:138)
> [java] at org.jboss.as.config.assembly.ModuleParser.parse(ModuleParser.java:61)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.processModuleDependency(GenerateModulesDefinition.java:193)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.process(GenerateModulesDefinition.java:130)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.main(GenerateModulesDefinition.java:104)
> [java] Java Result: 1
> {code}
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6826) Add Support for Equinox ForkJoinPool
by Philippe Marschall (JIRA)
Philippe Marschall created AS7-6826:
---------------------------------------
Summary: Add Support for Equinox ForkJoinPool
Key: AS7-6826
URL: https://issues.jboss.org/browse/AS7-6826
Project: Application Server 7
Issue Type: Enhancement
Components: EE
Reporter: Philippe Marschall
Assignee: David Lloyd
Unfortunately JSR-236 does not address Java 7 fork/join pools. This puts people how want to use fork/join pools in an awkward position, either don't use them and wait for EE 8 (four or five years) or violate the "contract" and just create them anyway.
This presents a great opportunity for AS8 to go further than the spec and provide a {{java.util.concurrent.ForkJoinPool}} and a {{java.util.concurrent.ForkJoinPool.ForkJoinWorkerThreadFactory}}. This allows us to innovate and standardize at a later time in EE 8 once we gained experience.
This should include the following features:
* Allow the configuration of {{java.util.concurrent.ForkJoinPool}} in the server configuration. You should be able to configure the parallelism and asyncMode (see constructor arguments). Similar to {{javax.enterprise.concurrent.ManagedExecutorService}}.
* Allow the injection of {{java.util.concurrent.ForkJoinPool}} configured in the server. Similar to {{javax.enterprise.concurrent.ManagedExecutorService}}.
* Allow the configuration of {{java.util.concurrent.ForkJoinPool.ForkJoinWorkerThreadFactory}} in the server configuration, merely to match the same feature in JSR-268.
* Allow the injection of {{java.util.concurrent.ForkJoinPool.ForkJoinWorkerThreadFactory}} configured in the server (similar to Infinispan), merely to match the same feature in JSR-268.
* {{java.util.concurrent.ForkJoinPool}} should per default not preserve the context http://java.net/projects/concurrency-ee-spec/lists/jsr236-experts/archive... (naming, security, transactions, class loading). Optionally you should be able to configure which contexts are preserved, this might be tough as {{ForkJoinPool}} is not designed for extensibility.
I'm well aware that this is unspecified behaviour but so is Infinispan in AS7 and AS8 since JSR-107 again didn't make it.
This issue is intended for AS8, not AS7.
--
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
13 years, 3 months
[JBoss JIRA] (DROOLS-80) Create a project that will allow Drools to be tested against many OSGi frameworks
by Cristiano Gavião (JIRA)
[ https://issues.jboss.org/browse/DROOLS-80?page=com.atlassian.jira.plugin.... ]
Cristiano Gavião commented on DROOLS-80:
----------------------------------------
Initially was added only tests for bundle installation. Next step is to create tests to ensure that Drools OSGi services are being published properly.
> Create a project that will allow Drools to be tested against many OSGi frameworks
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-80
> URL: https://issues.jboss.org/browse/DROOLS-80
> Project: Drools
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Cristiano Gavião
> Assignee: Mark Proctor
> Labels: OSGi
>
> The actual project that tests Drools in a OSGi platform was not defined for a reliable and consistent tests on more than one framework.
> So the propose is to create a new project that will use Pax-Exam tool which will able to test Drools bundles in the most important existent frameworks: Equinox, Felix and Knopflerfish.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6727) Modular build not in sync with modules directory structure
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6727?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6727:
----------------------------------------------
Mike Harvey <mharvey(a)redhat.com> made a comment on [bug 947145|https://bugzilla.redhat.com/show_bug.cgi?id=947145]
Acking on behalf of Pavel Slavicek.
> Modular build not in sync with modules directory structure
> ----------------------------------------------------------
>
> Key: AS7-6727
> URL: https://issues.jboss.org/browse/AS7-6727
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Labels: Karaf
>
> {code}
> [echo] Static modules: [org.jboss.as.standalone,org.jboss.as.domain-http-error-context,,, org.jboss.logging, org.jboss.vfs, org.slf4j, org.jboss.logging.jul-to-slf4j-stub]
> [java] Exception in thread "main" java.io.FileNotFoundException: /Users/tdiesler/git/jboss-as/build-modular/../build/src/main/resources/modules/org/jboss/as/logging/main/module.xml (No such file or directory)
> [java] at java.io.FileInputStream.open(Native Method)
> [java] at java.io.FileInputStream.<init>(FileInputStream.java:138)
> [java] at org.jboss.as.config.assembly.ModuleParser.parse(ModuleParser.java:61)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.processModuleDependency(GenerateModulesDefinition.java:193)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.process(GenerateModulesDefinition.java:130)
> [java] at org.jboss.as.config.assembly.GenerateModulesDefinition.main(GenerateModulesDefinition.java:104)
> [java] Java Result: 1
> {code}
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6779) AS7.1 jars run against as7.2/eap6.1 cause test case (eclipse) to hang
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-6779?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-6779:
----------------------------------------------
Mike Harvey <mharvey(a)redhat.com> made a comment on [bug 927318|https://bugzilla.redhat.com/show_bug.cgi?id=927318]
Acking on behalf of Pavel Slavicek.
> AS7.1 jars run against as7.2/eap6.1 cause test case (eclipse) to hang
> ---------------------------------------------------------------------
>
> Key: AS7-6779
> URL: https://issues.jboss.org/browse/AS7-6779
> Project: Application Server 7
> Issue Type: Bug
> Components: Remoting
> Reporter: Rob Stryker
> Assignee: Emanuel Muckenhuber
> Priority: Blocker
> Attachments: AS7-6779.out2.txt, AS7-6779.stack.txt, out.zip
>
>
> Somewhere along the line recently, EAP6.1 / AS 7.2 has a regression in remoting or xnio somehow, and this is causing blocking problems for tools.
> Recall:
> 1) JBossTools bundles a set of jars capable of communicating with a running application server
> 2) This single set of jars must be capable of communicating with all servers in the 7.x stream
> 3) Bundling a second set of jars is not easily accomplished, but could be possible
> And:
> 4) Using the as7.1.0 jars against eap6.1 in a specific unit test causes eclipse to hang
> The basic code of our test case (once we get rid of the jbt stuff wrapped around it) is basically as follows:
> {code}
> this.client = ModelControllerClient.Factory.create(details.getHost(), details.getManagementPort(),
> getCallbackHandler());
> this.manager = ServerDeploymentManager.Factory.create(client);
> DeploymentPlanBuilder builder = manager.newDeploymentPlan().replace(name, file);
> try {
> DeploymentAction action = builder.getLastAction();
> Future<ServerDeploymentPlanResult> planResult = manager.execute(builder.build());
> // FREEZE HERE
> // This is "DeploymentOperationResult.getStatus() in the stack trace
> ServerDeploymentActionResult actionResult = planResult.get().getDeploymentActionResult(action.getId());
> IStatus status = createStatus(action.getDeploymentUnitUniqueName(), action.getType().name(), actionResult);
> } catch (Exception e) {
> throw new JBoss7ManangerException(e);
> }
> {code}
> The actual stack trace is:
> {code}
> Thread [main] (Suspended)
> owns: RunnableLock (id=461)
> waiting for: ActiveOperationSupport$ActiveOperationImpl<T,A> (id=462)
> Object.wait(long) line: not available [native method]
> ActiveOperationSupport$ActiveOperationImpl<T,A>(Object).wait() line: 503
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).await() line: 192
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).get() line: 266
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get() line: 363
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get() line: 317
> ServerDeploymentPlanResultFuture.get() line: 76
> ServerDeploymentPlanResultFuture.get() line: 42
> DeploymentOperationResult.getStatus() line: 52
> AS7ManagerTestUtils.waitUntilFinished(IJBoss7DeploymentResult) line: 93
> AS7ManagerIntegrationTest.canReplaceWar() line: 129
> {code}
> The list of jars we are using to communicate with the server are:
> {code}
> jboss-as-controller-client-7.1.0.Final.jar
> jboss-as-protocol-7.1.0.Final.jar
> jboss-dmr-1.1.1.Final.jar
> jboss-logging-3.1.0.GA.jar
> jboss-marshalling-1.3.9.GA.jar
> jboss-remoting-3.2.7.GA.jar
> jboss-sasl-1.0.0.Final.jar
> jboss-threads-2.0.0.GA.jar
> xnio-api-3.0.3.GA.jar
> xnio-nio-3.0.3.GA.jar
> {code}
> It was suggested in irc by ctomc that we simply replace the following jars with new jars from jboss-as 7.2 / eap6.1:
> {code}
> jboss-remoting-3.2.7.GA.jar -> 3.2.15.GA
> xnio-api-3.0.3.GA.jar -> 3.0.7
> xnio-nio-3.0.3.GA.jar -> 3.0.7
> {code}
> This approach also failed, with the following stack trace:
> {code}
> java.lang.NoClassDefFoundError: org/xnio/Cancellable
> (sic)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:59)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:211)
> at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:173)
> {code}
> So it is obvious that jboss-as-controller jar from as-7.1 requires classes that are no longer present in xnio. If this is the case, it would indicate that xnio has REMOVED classes from its jar during an incremental version from 3.0.3 to 3.0.7, which would constitute an API breakage.
> So clearly for us, updating only remoting and xnio does not work. The next possible solution would be to update ALL jars, however, this led to a similar situation when using AS7.2 / Eap 6.1 jars to communicate with an AS 7.0.0 server. Again, similar to what was mentioned above, all tests passed EXCEPT the test above. The test above failed with an almost identical stack trace:
> {code}
> Thread [main] (Suspended)
> owns: RunnableLock (id=160)
> waiting for: ActiveOperationSupport$ActiveOperationImpl<T,A> (id=161)
> Object.wait(long) line: not available [native method]
> ActiveOperationSupport$ActiveOperationImpl<T,A>(Object).wait() line: 503
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).await() line: 192
> ActiveOperationSupport$ActiveOperationImpl<T,A>(AsyncFutureTask<T>).get() line: 266
> AbstractModelControllerClient$DelegatingCancellableAsyncFuture(AbstractDelegatingAsyncFuture<T>).get() line: 100
> ServerDeploymentPlanResultFuture.get() line: 76
> ServerDeploymentPlanResultFuture.get() line: 42
> DeploymentOperationResult.getStatus() line: 52
> AS7ManagerTestUtils.waitUntilFinished(IJBoss7DeploymentResult) line: 93
> AS7ManagerTestUtils.quietlyUndeploy(String, AS71Manager) line: 76
> AS7ManagerIntegrationTest.canReplaceWar() line: 135
> {code}
> No matter how you look at it, the contract has been broken. JBossTools now is looking for a specific set of jars which care capable of communicating with AS7.0, 7.1, 7.2, eap6.0, 6.1, jpp6.0, etc. Without a set of jars that can communicate with all of these servers, our tools will need to implement drastic workarounds or bundle several versions of the app server's jars within it.
> It's interesting to me that the as7.1 jars work against everything except eap6.1, and yet, the eap6.1 jars work against everything except as7.0.0.
--
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
13 years, 3 months
[JBoss JIRA] (DROOLS-94) Hashed field on Integer.this causes a RuntimeException
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-94?page=com.atlassian.jira.plugin.... ]
Mario Fusco resolved DROOLS-94.
-------------------------------
Fix Version/s: 5.6
6.0.0.Beta1
Resolution: Done
> Hashed field on Integer.this causes a RuntimeException
> ------------------------------------------------------
>
> Key: DROOLS-94
> URL: https://issues.jboss.org/browse/DROOLS-94
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 5.6, 6.0.0.Beta1
>
>
> Having the following drl
> {code}
> global java.util.List list;
> rule R when
> $i : Integer( this == 1 )
> then
> list.add( $i );
> end
> rule S when
> $i : Integer( this == 2 )
> then
> list.add( $i );
> end
> rule T when
> $i : Integer( this == 3 )
> then
> list.add( $i );
> end
> {code}
> and inserting an Integer(1) in the ksession causes the following Exception:
> org.drools.core.RuntimeDroolsException: Conversion to long not supported from java.lang.Integer
> at org.drools.core.base.extractors.BaseObjectClassFieldReader.getLongValue(BaseObjectClassFieldReader.java:126)
> Note that it is necessary to have the constraint on Integer.this in 3 different rule in order to enable the field hashing.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-5970) RichFaces Showcase portlet is unable to switch skins
by Stan Silvert (JIRA)
[ https://issues.jboss.org/browse/AS7-5970?page=com.atlassian.jira.plugin.s... ]
Stan Silvert resolved AS7-5970.
-------------------------------
Fix Version/s: EAP 6.1.0.Alpha (7.2.0.Final)
Resolution: Done
> RichFaces Showcase portlet is unable to switch skins
> ----------------------------------------------------
>
> Key: AS7-5970
> URL: https://issues.jboss.org/browse/AS7-5970
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Ken Finnigan
> Assignee: Stan Silvert
> Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
>
>
> The following exception is thrown when the user changes skins for the second time immediately after changing the skin for the first time:
> {noformat}
> Caused by: javax.faces.FacesException: Cannot remove the same component twice: pbG9dea276d_2dee9e_2d4150_2dad91_2d22255b5a57d2_j_id1:j_idt444
> at com.sun.faces.context.StateContext$AddRemoveListener.handleAddRemoveWithAutoPrune(StateContext.java:489) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1]
> at com.sun.faces.context.StateContext$AddRemoveListener.handleRemove(StateContext.java:371) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1]
> at com.sun.faces.context.StateContext$AddRemoveListener.processEvent(StateContext.java:334) [jsf-impl-2.1.13-redhat-1.jar:2.1.13-redhat-1]
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) [jboss-jsf-api_2.1_spec-2.0.7.Final-redhat-1.jar:2.0.7.Final-redhat-1]
> {noformat}
> This error manifests due to the Portlet Bridge needing to retain the UIViewRoot from JSF between Portlet Requests, which causes the list of component tree actions, ie. adding and removing, to be retained making JSF think that it's trying to remove a component that was actually removed in a previous request.
> This has been raised as http://java.net/jira/browse/JAVASERVERFACES-2609, but wanted to raise this as a tracker so that when that fix is available it can be incorporated.
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener
by Sudip Bhowmik (JIRA)
[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ]
Sudip Bhowmik commented on AS7-6819:
------------------------------------
Thank you Jesper. I have created a following thread on the same:
https://community.jboss.org/thread/223211
Hope to get some help.
> MBD @ResourceAdapter deployment issue with JCA inbound listener
> ---------------------------------------------------------------
>
> Key: AS7-6819
> URL: https://issues.jboss.org/browse/AS7-6819
> Project: Application Server 7
> Issue Type: Release
> Components: EJB, JCA
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows with Jboss 7.1.3 EAP version.
> Reporter: Sudip Bhowmik
> Labels: jboss
> Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml
>
>
> The source set is attached here with.
> =================================================
> 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
> ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
> terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
--
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
13 years, 3 months
[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ]
Jesper Pedersen closed AS7-6819.
--------------------------------
Resolution: Rejected
Post your questions here - https://community.jboss.org/en/jbossas7
JIRA is for tracking issues with the application server
> MBD @ResourceAdapter deployment issue with JCA inbound listener
> ---------------------------------------------------------------
>
> Key: AS7-6819
> URL: https://issues.jboss.org/browse/AS7-6819
> Project: Application Server 7
> Issue Type: Release
> Components: EJB, JCA
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows with Jboss 7.1.3 EAP version.
> Reporter: Sudip Bhowmik
> Labels: jboss
> Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml
>
>
> The source set is attached here with.
> =================================================
> 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
> ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
> terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
--
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
13 years, 3 months