September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5513) JNDI Lookup is not working in thread run method

by sandip jorwekar (JIRA)

sandip jorwekar created AS7-5513: ------------------------------------ Summary: JNDI Lookup is not working in thread run method Key: AS7-5513 URL: https://issues.jboss.org/browse/AS7-5513 Project: Application Server 7 Issue Type: Bug Components: Application Client Affects Versions: 7.1.1.Final Environment: Windows XP and JDK1.6 Reporter: sandip jorwekar Assignee: Stuart Douglas Priority: Critical Fix For: Open To Community When i do the JNDI lookup in thread's run method then i am getting below error java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:auroraclientcommon,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@64883c at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584) at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119) at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181) 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) at $Proxy0.create(Unknown Source) at BookClient1.test(BookClient1.java:117) at BookClient1.run(BookClient1.java:104) -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] (AS7-5505) Cannot overlay in a single composite operation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5505: ----------------------------------- Summary: Cannot overlay in a single composite operation Key: AS7-5505 URL: https://issues.jboss.org/browse/AS7-5505 Project: Application Server 7 Issue Type: Bug Components: Server Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.2.0.Alpha1 In order to support AS7-3694 I need to associate a META-INF/jboss-all.xml descriptor with bundle deployments. This I currently do in six discrete steps {code} { "address" => ("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"), "operation" => "add" } { "address" => undefined, "operation" => "upload-deployment-stream", "input-stream-index" => 0 } { "address" => [ ("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"), ("content" => "META-INF/jboss-all.xml") ], "operation" => "add", "content" => {"hash" => bytes { 0xdb, 0x79, 0x11, 0xff, 0xdf, 0x8f, 0xfc, 0x65, 0xc2, 0xe3, 0x6b, 0x20, 0xa5, 0x89, 0xa7, 0xdb, 0x10, 0xed, 0xcc, 0xc0 }} } { "address" => [ ("deployment-overlay" => "bundle-b.jar/META-INF/jboss-all.xml"), ("deployment" => "bundle-b.jar") ], "operation" => "add" } { "operation" => "add", "address" => [("deployment" => "bundle-b.jar")], "runtime-name" => "bundle-b.jar", "content" => [{"input-stream-index" => 0}] } { "operation" => "deploy", "address" => [("deployment" => "bundle-b.jar")] } {code} As far as I know these cannot be combined in a composite operation because step #3 uses the result of #2. The management API should allow this to happen in a single composite operation. -- 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, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (AS7-1263) Publish deployment descriptor schemas and dtd in the dist

by Brian Stansberry (JIRA)

Publish deployment descriptor schemas and dtd in the dist --------------------------------------------------------- Key: AS7-1263 URL: https://issues.jboss.org/browse/AS7-1263 Project: Application Server 7 Issue Type: Task Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.0.1.Final AS 7.0 has the domain/host/standalone config schemas in docs/schema, but not the deployment descriptor schemas and DTDs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

7
14
0 / 0

[JBoss JIRA] (AS7-5510) EJB deploys with dual definition

by Dan Wilkin (JIRA)

Dan Wilkin created AS7-5510: ------------------------------- Summary: EJB deploys with dual definition Key: AS7-5510 URL: https://issues.jboss.org/browse/AS7-5510 Project: Application Server 7 Issue Type: Feature Request Components: EJB Affects Versions: 7.1.0.Final Environment: Windows 7 Reporter: Dan Wilkin Assignee: jaikiran pai When two uniquely defined Session Beans reference the same interface in the {{@Remote}} annotation, the following exception occurs: {noformat} Caused by: org.jboss.invocation.CannotProceedException: INV-00002:Invocation cannot proceed (end of interceptor chain has been hit) at org.jboss.invocation.InvocationMessages_$bundle.cannotProceed(InvocationMessages_$bundle.java:131) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:293) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:202) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final] ... 100 more {noformat} This can occur from a copy-paste error: {code:title=RedSLSB.java} @Stateless @Remote(Red.class) public class RedSLSB implements Red { ... } {code} {code:title=BlueSLSB.java} @Stateless @Remote(Red.class) public class BlueSLSB implements Blue { ... } {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, 8 months

4
6
0 / 0

[JBoss JIRA] (AS7-4057) Create logging profiles for deployments

by James Perkins (JIRA)

James Perkins created AS7-4057: ---------------------------------- Summary: Create logging profiles for deployments Key: AS7-4057 URL: https://issues.jboss.org/browse/AS7-4057 Project: Application Server 7 Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.2.0.Alpha1 Create logging profiles to be assignable to deployments. The precedence would be deployment configuration -> profile configuration -> default configuration. This would allow profiles to be configured with the management interface. Each profile would have it's own LogContext and the context could be secured. -- 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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (JBRULES-3619) Knowledge Agent: add the possibility to apply ByteArrayResources

by Esteban Aliverti (JIRA)

Esteban Aliverti created JBRULES-3619: ----------------------------------------- Summary: Knowledge Agent: add the possibility to apply ByteArrayResources Key: JBRULES-3619 URL: https://issues.jboss.org/browse/JBRULES-3619 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Reporter: Esteban Aliverti Assignee: Mark Proctor Priority: Minor -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] (AS7-5514) Local access to admin console hangs with spinning "Loading..." icon. Remote access works.

by Dean Schulze (JIRA)

Dean Schulze created AS7-5514: --------------------------------- Summary: Local access to admin console hangs with spinning "Loading..." icon. Remote access works. Key: AS7-5514 URL: https://issues.jboss.org/browse/AS7-5514 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Environment: Windows 7 Pro 64-bit, JDK 1.7 64-bit Reporter: Dean Schulze Assignee: Heiko Braun Installed JBoss 7.1.1 Final from .zip archive. Added a management user. Started standalone.bat. localhost:8080 shows the splash page. Clicking on the Admin Console link hangs with the "Loading..." icon spinning. Modified standalone.xml to allow remote access (management and public) and opened up Windows firewall to the java.exe program that is running JBoss. I can access the splash page and admin console remotely. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2385) Management - readding file handler logger fails

by Dominik Pospisil (Created) (JIRA)

Management - readding file handler logger fails ----------------------------------------------- Key: AS7-2385 URL: https://issues.jboss.org/browse/AS7-2385 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Logging Affects Versions: 7.1.0.Beta1 Reporter: Dominik Pospisil Assignee: Brian Stansberry Removing and adding file handler fails. Perhaps remove operation does not clean up all resources properlly. Steps to reproduce: [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"}) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:remove {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"}) { "outcome" => "failed", "failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.logging.handler-file.test-fh is already registered", "rolled-back" => true } [standalone@localhost:9999 /] -- 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

13 years, 8 months

6
5
0 / 0

[JBoss JIRA] (JBRULES-3613) Support "Defeasible" rules in Drools

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3613: --------------------------------------- Summary: Support "Defeasible" rules in Drools Key: JBRULES-3613 URL: https://issues.jboss.org/browse/JBRULES-3613 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical Very roughly speaking, "defeasiblity" is about rules being able to prevent other rules from firing, or canceling the conclusions other rules. It is used to manage "exceptions" or "(counter)arguments", where different rules lead to conflicting conclusions and a resolution strategy has to be applied, depending on some relative ordering (strength, salience, temporal, weight, etc..). While an ad-hoc implementation is possible combining salience, appropriate insertions/retractions and the rule-based agenda, a more declarative approach should be provided to the user. This lack of a feature is currently a blocker for the adoption of Drools in several medical and legal communities, just to cite some. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] (AS7-5398) Upgrade JGroups to 3.0.12.Final

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-5398: ----------------------------------- Summary: Upgrade JGroups to 3.0.12.Final Key: AS7-5398 URL: https://issues.jboss.org/browse/AS7-5398 Project: Application Server 7 Issue Type: Component Upgrade Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.3.Final (EAP) Just released! On 20/08/12 11:16, Bela Ban wrote:> FYI, > contains 2 fixes, one of them [1] seems to fix the issue with AS > clustering which led to incorrect CacheView installation. > > > [1] https://issues.jboss.org/browse/JGRP-1502 -- 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

13 years, 8 months

2
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012