May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9034) Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference

by Scott Marlow (JIRA)

Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9034 URL: https://issues.jboss.org/browse/JBAS-9034 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
8
0 / 0

[JBoss JIRA] (JBJCA-818) Parameter type of connection interface method can be anything

by Jeff Zhang (JIRA)

Jeff Zhang created JBJCA-818: -------------------------------- Summary: Parameter type of connection interface method can be anything Key: JBJCA-818 URL: https://issues.jboss.org/browse/JBJCA-818 Project: IronJacamar Issue Type: Task Components: Code Generator Affects Versions: 1.1.0.Alpha7 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.1.0.Alpha8 1 Parameter type: int or Integer (ok) 2 Parameter type: javax.resource.spi.work.Work (ok) 3 Parameter type: Work (error) -- 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

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-4664) Upgrade PicketLink Libraries to 2.1.0.Final

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-4664: ---------------------------------- Summary: Upgrade PicketLink Libraries to 2.1.0.Final Key: AS7-4664 URL: https://issues.jboss.org/browse/AS7-4664 Project: Application Server 7 Issue Type: Component Upgrade Components: Security Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 7.1.2.Final-redhat1 -- 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

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] (AS7-4721) CLONE - Jms client can't authenticate to messaging subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-4721?page=com.atlassian.jira.plugin.s... ] Jason Greene resolved AS7-4721. ------------------------------- Resolution: Done > CLONE - Jms client can't authenticate to messaging subsystem > ------------------------------------------------------------ > > Key: AS7-4721 > URL: https://issues.jboss.org/browse/AS7-4721 > Project: Application Server 7 > Issue Type: Bug > Components: JMS, Security > Affects Versions: 7.1.1.Final > Reporter: Miroslav Novak > Assignee: Jason Greene > Priority: Blocker > Fix For: 7.1.2.Final (EAP) > > > Jms client can't authenticate to messaging subsystem. I've prepared reproducer for EAP 6 ER6 but this issue is also in AS7 master. > Exception: > {code} > Exception in thread "main" javax.jms.JMSSecurityException: Unable to validate user: admin > at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:312) > at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:781) > at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:280) > at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:601) > at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:684) > at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:119) > at testjndi.SecurityClient.getConnection(SecurityClient.java:308) > at testjndi.SecurityClient.initializeClient(SecurityClient.java:83) > at testjndi.SecurityClient.main(SecurityClient.java:363) > Caused by: HornetQException[errorCode=105 message=Unable to validate user: admin] > ... 9 more > {code} > Steps to reproduce: > 1. Download and unzip EAP 6 ER6 - http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.0.0-ER6/j... > 2. Using add-user.sh create user to application realm - for example with username: admin, password:adminadmin, role:guest > 3. Unzip attached reproducer.zip and copy standalone-full-ha.xml to $JBOSS_HOME/stanalone/configuration > 4. Start server > 5. Start jms client in reproducer - sh start-client.sh 127.0.0.1 jms/queue/testQueue0 admin adminadmin (parameters are hostname queueJndiName username password) -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4741) Add a mode to the jboss-as maven plugin where undeploying an application that isn't deployed doesn't fail

by Pete Muir (JIRA)

Pete Muir created AS7-4741: ------------------------------ Summary: Add a mode to the jboss-as maven plugin where undeploying an application that isn't deployed doesn't fail Key: AS7-4741 URL: https://issues.jboss.org/browse/AS7-4741 Project: Application Server 7 Issue Type: Feature Request Reporter: Pete Muir Assignee: James Perkins Fix For: 7.1.1.Final Currently if I try to run {code} mvn jboss-as:undeploy {code} on a maven project which I haven't actually deployed to the application server (or have previously undeployed), the jboss-as maven plugin will give an error and cause maven to exit. Consider a project like the quickstarts, where we have many deployable artifacts, of which the user may deploy a few. They then wish to undeploy any quickstarts, but currently have no easy way to do it, other than going to each quickstart they deployed and typing mvn jboss-as:undeploy (as doing a mvn jboss-as:undeploy at the root of the quickstart project will try to undeploy all of them, including those not yet deployed, and hence fail). I think this is going to apply to development of any moderately complex project, where there is more than one deployable. artifact. I would propose that undeploying a non-existent project shouldn't be an error at all, but a warning, and that we should simply log this. We already have the force (true by default) flag, which could be extended to cover undeployment. If the user set force=false, then the error could occur. -- 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

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3495) Error 404 when run maven install http://repository.jboss.org/nexus/content/groups/public/org/drools/droolsjbpm-parent/5.5.0-SNAPSHOT/droolsjbpm-parent-5.5.0-SNAPSHOT.pom

by Ramon Rosa da Silva (JIRA)

Ramon Rosa da Silva created JBRULES-3495: -------------------------------------------- Summary: Error 404 when run maven install http://repository.jboss.org/nexus/content/groups/public/org/drools/drools... Key: JBRULES-3495 URL: https://issues.jboss.org/browse/JBRULES-3495 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.5.0.Beta1 Environment: Windows 7, Eclipse Indigo Service Release 2 or CMD, Apache Maven 3.4 Reporter: Ramon Rosa da Silva Assignee: Mark Proctor When I run mvn install on drools-multiproject occur: [INFO] Scanning for projects... Downloading: http://repository.jboss.org/nexus/content/groups/public/org/drools/drools... [WARNING] Could not transfer metadata org.drools:droolsjbpm-parent:5.5.0-SNAPSHOT/maven-metadata.xml from/to jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/): Connection to http://repository.jboss.org refused Downloading: http://repository.jboss.org/nexus/content/groups/public/org/drools/drools... [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.drools:drools-multiproject:5.5.0-SNAPSHOT (C:\Users\IBM_ADMIN\git\drools\pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not transfer artifact org.drools:droolsjbpm-parent:pom:5.5.0-SNAPSHOT from/to jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/): Connection to http://repository.jboss.org refused and 'parent.relativePath' points at wrong local POM @ line 6, column 11: Connection timed out: connect -> [Help 2] [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/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2785) Documentation fixes w.r.t. events

by Wolfgang Laun (JIRA)

Documentation fixes w.r.t. events ---------------------------------- Key: JBRULES-2785 URL: https://jira.jboss.org/browse/JBRULES-2785 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical Fix For: 5.2.0.M1 Correct the documentation: (1) Explicit expiry time by @expires() in declare has precedence over implicit, dervide from rules. (Critical, because right now is documented the other way round.) (2) Document that declare without any fields must refer to an existing, imported type. (3) Document the semantics of timer, and that timer() can only be used in a STREAM session. Also, document that "int:" (as in "timer(int: 0 1m)") is optional. (4) Make it clear that window:length( N ) is also satisfied if there are less than N events. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
15
0 / 0

[JBoss JIRA] Created: (JBRULES-2681) Drools: Unable to load session snapshot

by Gustavo Tenrreiro (JIRA)

Drools: Unable to load session snapshot --------------------------------------- Key: JBRULES-2681 URL: https://jira.jboss.org/browse/JBRULES-2681 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.0.FINAL Environment: Windows Server, SQL Server 2005, Tomcat 5.5, Hibernate, Bitronix Reporter: Gustavo Tenrreiro Assignee: Mark Proctor After an event is processed the session fails to load using JPA persistence. I ve attached a test case. It uses a Drools flow file, and a drl file. Both very simple.. The flow file has a "Start" then an action that prints a message to the console, then "End" The Drl has one rule that processes an event: import com.kgcontrols.services.company.standardsRequests.workflow.events.VoteCreatedEvent declare VoteCreatedEvent @role(event) end rule "testEvents" when VoteCreatedEvent() from entry-point "VoteCreatedStream" then System.out.println("--------------------------- YEAH the event got here"); end I can see the "YEAH the event go here" on the console so I know the rule fired. But after that, if I try to load the session from the database I get: 1. INFO 2010-09-02 08:28:56 [ERROR] com.kgcontrols.services.company.standardsRequ 2. ests.workflow.TimerRunner java.lang.reflect.InvocationTargetException 3. java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException 4. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.buildComman 5. Service(KnowledgeStoreServiceImpl.java:106) 6. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.loadStatefu 7. lKnowledgeSession(KnowledgeStoreServiceImpl.java:74) 8. at org.drools.persistence.jpa.JPAKnowledgeService.loadStatefulKnowledgeS 9. ession(JPAKnowledgeService.java:118) 10. at com.kgcontrols.services.company.standardsRequests.workflow.JPAKnowle 11. dgeSessionLookup.loadSession(JPAKnowledgeSessionLookup.java:103) 12. at com.kgcontrols.services.company.standardsRequests.workflow.TimerRunn 13. er.run(TimerRunner.java:39) 14. at java.lang.Thread.run(Thread.java:619) 15. Caused by: java.lang.reflect.InvocationTargetException 16. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 17. 18. at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct 19. orAccessorImpl.java:39) 20. at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC 21. onstructorAccessorImpl.java:27) 22. at java.lang.reflect.Constructor.newInstance(Constructor.java:513) 23. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.buildComman 24. Service(KnowledgeStoreServiceImpl.java:91) 25. ... 5 more 26. Caused by: java.lang.RuntimeException: Unable to load session snapshot 27. at org.drools.persistence.session.JPASessionMarshallingHelper.loadSnapsh 28. ot(JPASessionMarshallingHelper.java:96) 29. at org.drools.persistence.session.SingleSessionCommandService.initKsessi 30. on(SingleSessionCommandService.java:196) 31. at org.drools.persistence.session.SingleSessionCommandService.<init>(Sin 32. gleSessionCommandService.java:159) 33. ... 10 more 34. Caused by: java.lang.NullPointerException 35. at org.drools.reteoo.LeftTuple.<init>(LeftTuple.java:135) 36. at org.drools.reteoo.LeftTuple.<init>(LeftTuple.java:121) 37. at org.drools.marshalling.impl.InputMarshaller.readLeftTuple(InputMarsha 38. ller.java:461) 39. at org.drools.marshalling.impl.InputMarshaller.readFactHandles(InputMars 40. haller.java:351) 41. at org.drools.marshalling.impl.InputMarshaller.readSession(InputMarshall 42. er.java:205) 43. at org.drools.marshalling.impl.DefaultMarshaller.unmarshall(DefaultMarsh 44. aller.java:91) 45. at org.drools.persistence.session.JPASessionMarshallingHelper.loadSnapsh 46. ot(JPASessionMarshallingHelper.java:91) 47. ... 12 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
18
0 / 0

[JBoss JIRA] (AS7-4745) Localized DMR descriptions not picked up

by Jason Greene (JIRA)

Jason Greene created AS7-4745: --------------------------------- Summary: Localized DMR descriptions not picked up Key: AS7-4745 URL: https://issues.jboss.org/browse/AS7-4745 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Priority: Blocker Fix For: 7.1.2.Final (EAP) It seems the translations are not picked up. I've pulled the most recent set and verified that a portuguese translation [1] exists for the transaction subsystem, that acts as example in this case. However when I query the DMR description with providing a locale it does return the english contents [2]. [1] transactions/src/main/resources/org/jboss/as/txn/subsystem/LocalDescriptions_pt_BR.properties [2] example query: {noformat} /subsystem=transactions:read-resource-description(locale=pt_BR) [...] "enable-tsm-status" => { "type" => BOOLEAN, "description" => "Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not..", "expressions-allowed" => false, "nillable" => true, "default" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "all-services" }, [...] {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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4744) CLONE - Granular / attribute-based session replication replicates uncecessary data

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4744: ----------------------------------- Summary: CLONE - Granular / attribute-based session replication replicates uncecessary data Key: AS7-4744 URL: https://issues.jboss.org/browse/AS7-4744 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Radoslav Husar Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.2.Final (EAP) Results show that the size of replicated data is high with attribute-based granularity. The average replicated (and response) sized are ((1.7681421793709815E7 + 1.755308562069113E7) / 5 743.8) * bytes = 5.99058091 kilobytes whereas this cost should be minimal as only an int is being replicated. https://hudson.qa.jboss.com/hudson/job/eap-6x-stress-http-repl-sync-granu... -- 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

14 years, 2 months

1
0
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 May 2012