[JBoss JIRA] (AS7-3830) Remote JNDI call does not bind stateful beans
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created AS7-3830:
-------------------------------------
Summary: Remote JNDI call does not bind stateful beans
Key: AS7-3830
URL: https://issues.jboss.org/browse/AS7-3830
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.Final
Reporter: Ondřej Chaloupka
Assignee: jaikiran pai
It seems that current ejb remote client is not able to find stateful bean. Exception is thrown instead:
{code}
javax.naming.NamingException: java.lang.IllegalStateException: No EJB client context is available [Root exception is java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:135)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:124)
at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:70)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: No EJB client context is available
at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:91)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:133)
... 7 more
Caused by: java.lang.IllegalStateException: No EJB client context is available
at org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:233)
at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:160)
at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:89)
... 8 more
{code}
Please, check my test whether definition of remote context does not contain a mistake. But finding singleton and stateless beans works fine.
https://github.com/ochaloup/jboss-as/blob/ejb-remote-call/testsuite/integ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-3916) Concurrent access leads to empty domain.xml
by Heiko Braun (JIRA)
Heiko Braun created AS7-3916:
--------------------------------
Summary: Concurrent access leads to empty domain.xml
Key: AS7-3916
URL: https://issues.jboss.org/browse/AS7-3916
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.1.1.Final
Hi Red Hat team. We're still trying to narrow down the trigger but there is a very serious bug when using the admin console in AS 7.1 Final that causes the domain.xml file to be wiped of everything other than the extensions section that is at the top. Have not checked yet if this is a known bug or not but wanted to alert you immediately.
The potential trigger for this is more than one person using the admin
console at the same time. Even if just for monitoring while the other
person is making configuration changes. (Fortunately we had backed up
the config using the CLI.)
We are trying right now to get our QA1 drop out the door but we'll be
giving this a closer look tomorrow. Has anyone else reported this though?
Thanks,
Bill
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-3790) TS: Unable to pass tests in integration smoke test part of testsuite in IPv6 environment
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/AS7-3790?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar closed AS7-3790.
-------------------------------
Done, closing.
> TS: Unable to pass tests in integration smoke test part of testsuite in IPv6 environment
> ----------------------------------------------------------------------------------------
>
> Key: AS7-3790
> URL: https://issues.jboss.org/browse/AS7-3790
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
> Assignee: Shelly McGowan
>
> I've tried to build AS7 and run default part of testsuite (including integration smoke tests) in IPv6 environment like:{code}./build.sh clean install -Dnode0=::1 -Dipv6{code}
> My lookpack network interface was configured as:{code}[root@fedora15-vrt1 Documents]# ifconfig lo
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:60156 errors:0 dropped:0 overruns:0 frame:0
> TX packets:60156 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:37911245 (36.1 MiB) TX bytes:37911245 (36.1 MiB)
> [root@fedora15-vrt1 Documents]#
> {code}
> The result is failure because timeout:
> {code}
> <snip>
> main:
> build-smoke:
> [INFO] Executed tasks
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-ts-integ-smoke ---
> [INFO] Compiling 110 source files to /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/target/test-classes
> [WARNING] /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/surefire/servermodule/AbstractServerInModuleTestCase.java:[54,62] [deprecation] getModulesDir() in org.jboss.as.server.ServerEnvironment has been deprecated
> [INFO]
> [INFO] --- maven-surefire-plugin:2.10:test (smoke-full.surefire) @ jboss-as-ts-integ-smoke ---
> [INFO] Surefire report directory: /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.952s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [1.435s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.276s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [1.525s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [11.337s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [5.599s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [21.175s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [3.940s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [2.620s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [2.615s]
> [INFO] JBoss Application Server: Embedded ................ SUCCESS [4.239s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [5.673s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [6.888s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [3.532s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [8.944s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [4.899s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [11.049s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [5.775s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [9.914s]
> [INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [8.926s]
> [INFO] JBoss Application Server: EE ...................... SUCCESS [13.024s]
> [INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [7.015s]
> [INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [0.184s]
> [INFO] JBoss Application Server: Common code for clustering subsystems SUCCESS [5.332s]
> [INFO] JBoss Application Server: JGroups Subsystem ....... SUCCESS [8.036s]
> [INFO] JBoss Application Server: Infinispan Subsystem .... SUCCESS [23.168s]
> [INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [11.052s]
> [INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [19.138s]
> [INFO] JBoss Application Server: Clustering Server API ... SUCCESS [13.274s]
> [INFO] JBoss Application Server: Clustered registry service SUCCESS [2.203s]
> [INFO] JBoss Application Server: JacORB Subsystem ........ SUCCESS [16.268s]
> [INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [35.557s]
> [INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [5.422s]
> [INFO] JBoss Application Server: Clustering Server API implementation SUCCESS [5.224s]
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SUCCESS [7.409s]
> [INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [19.789s]
> [INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.183s]
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SUCCESS [9.624s]
> [INFO] JBoss Application Server: Application Client Bootstrap SUCCESS [7.014s]
> [INFO] JBoss Application Server: Command line interface .. SUCCESS [12.399s]
> [INFO] JBoss Application Server: EJB Client BOM .......... SUCCESS [0.226s]
> [INFO] JBoss Application Server: JMS Client BOM .......... SUCCESS [0.213s]
> [INFO] JBoss Application Server: EJB and JMS client combined jar SUCCESS [4.948s]
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SUCCESS [3.795s]
> [INFO] JBoss Application Server: Clustered service provider registry services SUCCESS [4.434s]
> [INFO] JBoss Application Server: Clustered singleton services SUCCESS [5.016s]
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SUCCESS [24.135s]
> [INFO] JBoss Application Server: Config Admin ............ SUCCESS [5.690s]
> [INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [7.514s]
> [INFO] JBoss Application Server: EE Deployment ........... SUCCESS [4.195s]
> [INFO] JBoss Application Server: JAXR Client ............. SUCCESS [4.562s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [0.231s]
> [INFO] JBoss Application Server: JPA SPI ................. SUCCESS [4.460s]
> [INFO] JBoss Application Server: JPA UTIL ................ SUCCESS [1.698s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [7.273s]
> [INFO] JBoss Application Server: Weld Integration ........ SUCCESS [8.499s]
> [INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [8.492s]
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SUCCESS [0.158s]
> [INFO] JBoss Application Server: JDR ..................... SUCCESS [6.291s]
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SUCCESS [5.485s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [3.706s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [18.260s]
> [INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [13.138s]
> [INFO] JBoss Application Server: Mail subsystem .......... SUCCESS [7.227s]
> [INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [18.398s]
> [INFO] JBoss Application Server: ModCluster Subsystem .... SUCCESS [7.415s]
> [INFO] JBoss Application Server: OSGi .................... SUCCESS [0.148s]
> [INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [9.388s]
> [INFO] JBoss Application Server: OSGi ConfigurationAdmin . SUCCESS [4.866s]
> [INFO] JBoss Application Server: POJO Subsystem .......... SUCCESS [7.217s]
> [INFO] JBoss Application Server: sosreport scripts ....... SUCCESS [2.259s]
> [INFO] JBoss Application Server: Service Archive Subsystem SUCCESS [6.041s]
> [INFO] JBoss Application Server: XTS Subsystem ........... SUCCESS [7.902s]
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SUCCESS [3.552s]
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SUCCESS [4.524s]
> [INFO] JBoss Application Server: Infinispan Hibernate 2nd level cache provider SUCCESS [1.783s]
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SUCCESS [3.333s]
> [INFO] JBoss Application Server: Build ................... SUCCESS [21.975s]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.190s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [1.574s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [3.888s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [2.520s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [18.181s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [3.492s]
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SUCCESS [0.261s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration SUCCESS [15.898s]
> [INFO] JBoss Application Server: Demos: Aggregator ....... SUCCESS [2.748s]
> [INFO] JBoss Application Server: Demos: Spec ............. SUCCESS [4.056s]
> [INFO] JBoss Application Server: Demos: Legacy TO BE MOVED SUCCESS [10.657s]
> [INFO] JBoss Application Server: Distribution ............ SUCCESS [1.035s]
> [INFO] JBoss Application Server: Remoting Subsystem Test . SUCCESS [2.981s]
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SUCCESS [2.360s]
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SUCCESS [1.969s]
> [INFO] JBoss Application Server Test Suite: Shared ....... SUCCESS [7.605s]
> [INFO] JBoss Application Server Test Suite: Aggregator ... SUCCESS [6.152s]
> [INFO] JBoss Application Server Test Suite: Integration .. SUCCESS [2.203s]
> [INFO] JBoss Application Server Test Suite: Integration - Smoke FAILURE [15:07.181s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 26:31.461s
> [INFO] Finished at: Thu Feb 16 11:51:51 CET 2012
> [INFO] Final Memory: 341M/494M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (smoke-full.surefire) on project jboss-as-ts-integ-smoke: Failure or timeout -> [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/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jboss-as-ts-integ-smoke
> [pjanouse@fedora15-vrt1 jboss-as]$
> {code}
> Unfortunately org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase.txt and org.jboss.as.test.smoke.embedded.demo~essaging.MessagingTestCase-output.txt files in jboss-as/testsuite/integration/smoke/target/surefire-reports are created, but leaved empty only. Nor work-around mentioned in [ARQ-696|https://issues.jboss.org/browse/ARQ-696?focusedCommentId=12667010...] comment doesn't help.
> BTW I've checked standalone-full.xml and basic things are correctly assigned to ::1 (especially _management_ and _public_ interface)
--
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, 1 month
[JBoss JIRA] (AS7-3828) EJB client tries to invoke EJBs after application was undeployed
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3828:
-----------------------------------
Summary: EJB client tries to invoke EJBs after application was undeployed
Key: AS7-3828
URL: https://issues.jboss.org/browse/AS7-3828
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Priority: Critical
Fix For: 7.1.1.Final
And this results in NoSuchEJBException.
One more feature that was fully supported in previous version (AS 5.1).
{noformat}
2012/02/20 10:59:11:336 EST [WARN ][Runner - 43] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 43.>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 43.
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:79)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.ejb.NoSuchEJBException: No such EJB[appname=clusterbench-ee6,modulename=clusterbench-ee6-ejb,distinctname=,beanname=RemoteStatefulSBImpl]
at org.jboss.ejb.client.remoting.GeneralInvocationFailureResponseHandler.processMessage(GeneralInvocationFailureResponseHandler.java:75)
at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleMessage(ChannelAssociation.java:385)
at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:371)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
... 1 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-3902) NPE in JGroups on shutting down the server
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3902:
-----------------------------------
Summary: NPE in JGroups on shutting down the server
Key: AS7-3902
URL: https://issues.jboss.org/browse/AS7-3902
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Priority: Critical
Fix For: 7.1.1.Final
Ran into while manually playing around.
1/ 2 server
2/ client requesting session on #1
3/ #2 is shut down >
Preceeding this log is AS7-3180.
{noformat}
17:23:39,763 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000082: Stopping the RpcDispatcher
17:23:40,086 SEVERE [org.jgroups.JChannel] failed destroying the protocol stack: java.lang.NullPointerException
at org.jboss.as.clustering.jgroups.ManagedSocketFactory.close(ManagedSocketFactory.java:174) [jboss-as-clustering-jgroups-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at org.jgroups.stack.DiagnosticsHandler.stop(DiagnosticsHandler.java:76) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.protocols.TP.stop(TP.java:1010) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.protocols.UDP.stop(UDP.java:248) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:996) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.stopStack(JChannel.java:923) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.disconnect(JChannel.java:380) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel._close(JChannel.java:909) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.close(JChannel.java:389) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jboss.as.clustering.jgroups.subsystem.ChannelService.stop(ChannelService.java:61) [jboss-as-clustering-jgroups-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at org.jboss.as.clustering.msc.AsynchronousService$2.run(AsynchronousService.java:84) [jboss-as-clustering-common-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
17:23:40,090 SEVERE [org.jgroups.JChannel] failed destroying the protocol stack: java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:922) [rt.jar:1.6.0_29]
at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:980) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.stopStack(JChannel.java:923) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel._close(JChannel.java:910) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jgroups.JChannel.close(JChannel.java:389) [jgroups-3.0.4.Final-redhat-0-todo.jar:3.0.4.Final]
at org.jboss.as.clustering.jgroups.subsystem.ChannelService.stop(ChannelService.java:61) [jboss-as-clustering-jgroups-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at org.jboss.as.clustering.msc.AsynchronousService$2.run(AsynchronousService.java:84) [jboss-as-clustering-common-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-3796) Remote EJB client seems to be leaking messages MAX_OUTBOUND_MESSAGES (ChannelBusyException: Too many open outbound writes)
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3796:
-----------------------------------
Summary: Remote EJB client seems to be leaking messages MAX_OUTBOUND_MESSAGES (ChannelBusyException: Too many open outbound writes)
Key: AS7-3796
URL: https://issues.jboss.org/browse/AS7-3796
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB, Remoting
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: David Lloyd
Priority: Critical
Fix For: 7.1.1.Final
David and Jaikiran,
lets revisit this topic. I still think were are leaking messages in remoting3. Badly. Even though I set MAX_O_Ms to 100K it still results in:
{noformat}
2012/02/16 08:34:48:728 EST [WARN ][Runner - 227] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 227.>
org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 227.
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:79)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy0.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
... 3 more
Caused by: org.jboss.remoting3.ChannelBusyException: Too many open outbound writes
at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:111)
at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:235)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:193)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:173)
at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:43)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:92)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
... 5 more
{noformat}
Here is a snip from the client properties:
{noformat}
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=perf18,perf19,perf20,perf21
remote.connection.perf18.host=perf18
remote.connection.perf18.port=4447
remote.connection.perf18.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connection.perf18.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=100000
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (AS7-5958) Incorrect Candidate permutation failed due to a conflict between imports exception when using host and fragment bundles
by Paul Illingworth (JIRA)
Paul Illingworth created AS7-5958:
-------------------------------------
Summary: Incorrect Candidate permutation failed due to a conflict between imports exception when using host and fragment bundles
Key: AS7-5958
URL: https://issues.jboss.org/browse/AS7-5958
Project: Application Server 7
Issue Type: Feature Request
Components: OSGi
Affects Versions: 7.2.0.Alpha1
Environment: Windows XP SP3
Reporter: Paul Illingworth
Assignee: Thomas Diesler
I am getting the following exception when my bundle is being resolved. I don't believe this is correct.
{noformat}
2012-11-15 15:10:41,403 DEBUG [org.jboss.osgi.resolver](qtp4105020-187) Candidate permutation failed due to a conflict between imports; will try another if possible.: org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource resource-console-web [HostBundleRevision[resource-console-web:1.0.0.SNAPSHOT]] because it is exposed to package 'com.google.inject' from resources com.google.inject [HostBundleRevision[com.google.inject:3.0.0]] and com.google.inject [HostBundleRevision[com.google.inject:3.0.0]] via two dependency chains.
Chain 1:
resource-console-web [HostBundleRevision[resource-console-web:1.0.0.SNAPSHOT]]
import: null
|
export: osgi.wiring.package=com.google.inject
com.google.inject [HostBundleRevision[com.google.inject:3.0.0]]
Chain 2:
resource-console-web [HostBundleRevision[resource-console-web:1.0.0.SNAPSHOT]]
import: null
|
export: osgi.wiring.package=com.saaconsultants.gwt.rpc.server.servlets; uses:=com.google.inject
reims-gwt-rpc [HostBundleRevision[reims-gwt-rpc:1.0.0.SNAPSHOT]]
import: null
|
export: osgi.wiring.package=com.google.inject
com.google.inject [HostBundleRevision[com.google.inject:3.0.0]]
at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1142)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:197)
at org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:56)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:152)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:167)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:598)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:214)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:520)
at org.apache.felix.webconsole.internal.core.BundlesServlet.doPost(BundlesServlet.java:331)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:437)
at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:384)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.ops4j.pax.web.service.internal.HttpServiceStarted$2.invoke(HttpServiceStarted.java:209)
at org.ops4j.pax.web.service.internal.$Proxy39.service(Unknown Source)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:117)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:74)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
at org.eclipse.jetty.server.Server.handle(Server.java:349)
at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:936)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:801)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:224)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:51)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
at java.lang.Thread.run(Thread.java:662)
2012-11-15 15:10:41,403 TRACE [org.jboss.osgi.framework](qtp4105020-187) Release framework lock
{noformat}
It seems to be happening because the ResolverImpl.isCompatible() method is comparing two capabilities; one is an AbstractBundleCapability and the other is a WrappedCapability that contains the same instance of AbstractBundleCapability. The result of the comparison is false.
As a quick hack I changed the equals method of WrappedCapability to
{noformat}
@Override
public boolean equals(Object obj)
{
return m_cap.equals(obj);
}
{noformat}
and that seemed to make it work and resolution was successful.
--
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, 1 month