March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-945) Ship XSD protocol config schema with JGroups and reference it from XML config files

by Bela Ban (JIRA)

Ship XSD protocol config schema with JGroups and reference it from XML config files ----------------------------------------------------------------------------------- Key: JGRP-945 URL: https://jira.jboss.org/jira/browse/JGRP-945 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Vladimir Blagojevic Priority: Minor Fix For: 2.8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-403) XACML: Resource can have multiple attributes with resource-id

by Anil Saldhana (JIRA)

XACML: Resource can have multiple attributes with resource-id ------------------------------------------------------------- Key: SECURITY-403 URL: https://jira.jboss.org/jira/browse/SECURITY-403 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-sunxacml Affects Versions: JBossXACML_2.0.3.CR4 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossXACML_2.0.3.CR5 Associated forum thread has the issue. Page 70 of the spec at http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-core-spec-o... ========== The <Resource> element MAY contain one or more <Attribute> elements with an AttributeId of "urn:oasis:names:tc:xacml:2.0:resource:resource-id". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1799) endpoint-deployer "installs" successfully even on test failures

by jaikiran pai (JIRA)

endpoint-deployer "installs" successfully even on test failures --------------------------------------------------------------- Key: EJBTHREE-1799 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1799 Project: EJB 3.0 Issue Type: Bug Components: endpoint-deployers Affects Versions: 1.1.3 Reporter: jaikiran pai Assignee: jaikiran pai endpoint-deployer (and probably other components which use JBBOOT in tests) successfully "install"s, "deploy"s etc... even when there are test case failures. The testcase needs to set the exitOnShutdown bootstrap config property to false and additionally (as a workaround till JBBOOT-20 is fixed) set the "jboss.shutdown.forceHalt" system property to false. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBAS-6705) AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template"

by Emanuel Muckenhuber (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6705?page=com.atlassian.jira.plug... ] Emanuel Muckenhuber resolved JBAS-6705. --------------------------------------- Resolution: Done This should be fixed in rev 86519. Thanks! > AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template" > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6705 > URL: https://jira.jboss.org/jira/browse/JBAS-6705 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS (JBoss Messaging) > Environment: JBoss AS Branch_5_x r86417, embjopr r259 > Reporter: Farah Juma > Assignee: Emanuel Muckenhuber > Fix For: JBossAS-5.1.0.CR1 > > > Steps to reproduce: > Attempt to create a new Topic or Queue. The following error occurs: > Failed to add Resource (see app server log for additional details): java.lang.RuntimeException:Failed to process template. > Deployment "vfsfile:/home/fjuma/jbossas5/Branch_5_x_extra/build/output/jboss-5.1.0.CR1/server/default/deploy/testTopic-service.xml" is in error due to the following reason(s): java.lang.RuntimeException: No Attribute found with name: downCacheSize for jboss.messaging.destination:service=Topic,name=testTopic, attributes: [DurableMessageCount, Instance, ExpiryQueue, ServerPeer, RedeliveryDelay, NonDurableMessageCount, NonDurableSubscriptionsCount, DurableSubscriptionsCount, Clustered, JNDIName, MaxDeliveryAttempts, MessageCounters, FullSize, AllMessageCount, MaxSize, DownCacheSize, SecurityConfig, CreatedProgrammatically, PageSize, Name, DLQ, AllSubscriptionsCount, MessageCounterHistoryDayLimit] > It looks like attribute names now start with an upper case letter instead of a lower case one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1798) JNDIKernelRegistryPlugin should not create proxies or sessions during MC context state change

by jaikiran pai (JIRA)

JNDIKernelRegistryPlugin should not create proxies or sessions during MC context state change --------------------------------------------------------------------------------------------- Key: EJBTHREE-1798 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1798 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: 1.1.3 Reporter: jaikiran pai Assignee: jaikiran pai The JNDIKernelRegistryPlugin is to used for the jndi: dependencies (which is a MC context) that are added to the EJB containers which are installed as MC beans. When MC internally, changes the state of the contexts, there are multiple calls to the : public KernelRegistryEntry getEntry(Object name) API. The jndi: dependencies point to proxy factories bound to JNDI and when this API is called it results in a JNDI lookup and a subsequent proxy/session creation. This needs to be avoided -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-941) Merge: log merge results and make them available via JMX

by Bela Ban (JIRA)

Merge: log merge results and make them available via JMX -------------------------------------------------------- Key: JGRP-941 URL: https://jira.jboss.org/jira/browse/JGRP-941 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.6.9, 2.8 We should log information about (1) a digest received, (2) my own digest and (3) the result of the digest merging. This should be logged (TRACE level) *and* we should also keep this information available in a (bounded) list in JMX -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-393) Caused by: KrbException: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC

by Nagendra krishnawat (JIRA)

Caused by: KrbException: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC ----------------------------------------------------------------------------------------------------------------------- Key: SECURITY-393 URL: https://jira.jboss.org/jira/browse/SECURITY-393 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Environment: Server Machine: Microsoft windows server 2003 R2 (Name: PASKTABSVR1, Domain: wamtest.wa.local, FullName:PASKTABSVR1.wamtest.wa.local) KDC : windows server 2003 R2, In my case server and KDC are same machine. (Name: PASKTABSVR1, Domain: wamtest.wa.local FullName:PASKTABSVR1.wamtest.wa.local) Client Machine: Microsoft windows XP professional (Name: PASKTABCL1, Domain: wamtest.wa.local FullName:PASKTABCL1.wamtest.wa.local) Reporter: Nagendra krishnawat Assignee: Anil Saldhana Fix For: Negotiation_2.0.3.GA I am using SPNEGO for silent authentication. Referring https://www.jboss.org/community/docs/DOC-10680 Environment specification: Server Machine: Microsoft windows server 2003 R2 (Name: PASKTABSVR1, Domain: wamtest.wa.local, FullName:PASKTABSVR1.wamtest.wa.local) KDC : windows server 2003 R2, In my case server and KDC are same machine. (Name: PASKTABSVR1, Domain: wamtest.wa.local FullName:PASKTABSVR1.wamtest.wa.local) Client Machine: Microsoft windows XP professional (Name: PASKTABCL1, Domain: wamtest.wa.local FullName:PASKTABCL1.wamtest.wa.local) I basically followed the pdf document userguide downloaded from above link (https://www.jboss.org/community/docs/DOC-10680) I have checked "Use DES type encryption types for this account" SPN setting: C:\Program Files\Support Tools>setspn -l PASKTABSVR1 Registered ServicePrincipalNames for CN=PASKTABSVR1,OU=Domain Controllers,DC=wamtest,DC=wa,DC=local: HTTP/PASKTABSVR1.wamtest.wa.local NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/PASKTABSVR1.wamtest.wa.local ldap/PASKTABSVR1.wamtest.wa.local/ForestDnsZones.wamtest.wa.local GC/PASKTABSVR1.wamtest.wa.local/wamtest.wa.local HOST/PASKTABSVR1.wamtest.wa.local/WAMTEST HOST/PASKTABSVR1 HOST/PASKTABSVR1.wamtest.wa.local HOST/PASKTABSVR1.wamtest.wa.local/wamtest.wa.local E3514235-4B06-11D1-AB04-00C04FC2DCD2/c97c1681-4636-4d4a-b7fe-94f6bf0567cf/wamtest.wa.local ldap/c97c1681-4636-4d4a-b7fe-94f6bf0567cf._msdcs.wamtest.wa.local ldap/PASKTABSVR1.wamtest.wa.local/WAMTEST ldap/PASKTABSVR1 ldap/PASKTABSVR1.wamtest.wa.local ldap/PASKTABSVR1.wamtest.wa.local/DomainDnsZones.wamtest.wa.local ldap/PASKTABSVR1.wamtest.wa.local/wamtest.wa.local DNS/PASKTABSVR1.wamtest.wa.local Command used to create keytab file: C:\Program Files\Support Tools>ktpass -crypto DES-CBC-CRC -princ host/PASKTABS...(a)WAMTEST.WA.LOCAL -pass Autumn08 -mapus er WAMTEST\PASKTABSVR1 -out C:\pasktabsvr1.host.keytab Login moduoles from Jboss(login-config.xml): . .. ...... <application-policy name="host"> <authentication> <login-module code="com.sun.security.auth.module.Krb5LoginModule" flag="required"> <module-option name="storeKey">true</module-option> <module-option name="useKeyTab">true</module-option> <module-option name="principal">host/PASKTABS...(a)WAMTEST.WA.LOCAL</module-option> <module-option name="keyTab">C:/pasktabsvr1.host.keytab</module-option> <module-option name="doNotPrompt">true</module-option> <module-option name="debug">true</module-option> </login-module> </authentication> </application-policy> <application-policy name="SPNEGO"> <authentication> <login-module code="org.jboss.security.negotiation.spnego.SPNEGOLoginModule" flag="requisite"> <module-option name="password-stacking">useFirstPass</module-option> <module-option name="serverSecurityDomain">host</module-option> </login-module> <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"> <module-option name="password-stacking">useFirstPass</module-option> <module-option name="usersProperties">props/spnego-users.properties</module-option> <module-option name="rolesProperties">props/spnego-roles.properties</module-option> </login-module> </authentication> </application-policy> ..... .. . As per document there are three tests, First and second test passes, ie the client browser gets the token, in second test host login module gets authenticated ie the second test passes. The final test, i.e. "secured" which is the integrated test of both client and server fails with following exception: Caused by: KrbException: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC at sun.security.krb5.KrbApReq.authenticate(KrbApReq.java:262) at sun.security.krb5.KrbApReq.<init>(KrbApReq.java:134) at sun.security.jgss.krb5.InitSecContextToken.<init>(InitSecContextToken.java:79) I tried mapping different SPN: C:\Program Files\Support Tools>setspn.exe -a HTTP/PASKTABSVR1.wamtest.wa.local PASKTABSVR1 C:\Program Files\Support Tools>setspn.exe -a HTTP/pasktabsvr1.wamtest.wa.local PASKTABSVR1 (Small case pasktansvr1) But it didn't help, I got same exception "Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC" Am I doing anything fundamentally wrong or this is a bug, or user doc is prepared on different environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-6707) So, you can "hot deploy" application(s) on the fly while JBoss AS is still running.

by Brian Milnes (JIRA)

So, you can "hot deploy" application(s) on the fly while JBoss AS is still running. ----------------------------------------------------------------------------------------- Key: JBAS-6707 URL: https://jira.jboss.org/jira/browse/JBAS-6707 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Administration and Configuration Guide Affects Versions: JBossAS-5.0.1.GA Reporter: Brian Milnes Priority: Trivial So, you can "hot deploy" application on the fly while JBoss AS is still running. Typo: should be applications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-6705) AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template"

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6705?page=com.atlassian.jira.plug... ] Charles Crouch commented on JBAS-6705: -------------------------------------- Emanuel, can you take a look at this? The problem appears to be at the deployment layer, when trying to deploy a new Topic/Queue. I've checked the management view and its definitely declaring the property as 'downCacheSize' with a lower case dee, but the deployer seems to be expecting upper case: [...DownCacheSize,...] > AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template" > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6705 > URL: https://jira.jboss.org/jira/browse/JBAS-6705 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS (JBoss Messaging) > Environment: JBoss AS Branch_5_x r86417, embjopr r259 > Reporter: Farah Juma > Assignee: Emanuel Muckenhuber > Fix For: JBossAS-5.1.0.CR1 > > > Steps to reproduce: > Attempt to create a new Topic or Queue. The following error occurs: > Failed to add Resource (see app server log for additional details): java.lang.RuntimeException:Failed to process template. > Deployment "vfsfile:/home/fjuma/jbossas5/Branch_5_x_extra/build/output/jboss-5.1.0.CR1/server/default/deploy/testTopic-service.xml" is in error due to the following reason(s): java.lang.RuntimeException: No Attribute found with name: downCacheSize for jboss.messaging.destination:service=Topic,name=testTopic, attributes: [DurableMessageCount, Instance, ExpiryQueue, ServerPeer, RedeliveryDelay, NonDurableMessageCount, NonDurableSubscriptionsCount, DurableSubscriptionsCount, Clustered, JNDIName, MaxDeliveryAttempts, MessageCounters, FullSize, AllMessageCount, MaxSize, DownCacheSize, SecurityConfig, CreatedProgrammatically, PageSize, Name, DLQ, AllSubscriptionsCount, MessageCounterHistoryDayLimit] > It looks like attribute names now start with an upper case letter instead of a lower case one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-6705) AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template"

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6705?page=com.atlassian.jira.plug... ] Charles Crouch reassigned JBAS-6705: ------------------------------------ Assignee: Emanuel Muckenhuber (was: Charles Crouch) > AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template" > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBAS-6705 > URL: https://jira.jboss.org/jira/browse/JBAS-6705 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS (JBoss Messaging) > Environment: JBoss AS Branch_5_x r86417, embjopr r259 > Reporter: Farah Juma > Assignee: Emanuel Muckenhuber > Fix For: JBossAS-5.1.0.CR1 > > > Steps to reproduce: > Attempt to create a new Topic or Queue. The following error occurs: > Failed to add Resource (see app server log for additional details): java.lang.RuntimeException:Failed to process template. > Deployment "vfsfile:/home/fjuma/jbossas5/Branch_5_x_extra/build/output/jboss-5.1.0.CR1/server/default/deploy/testTopic-service.xml" is in error due to the following reason(s): java.lang.RuntimeException: No Attribute found with name: downCacheSize for jboss.messaging.destination:service=Topic,name=testTopic, attributes: [DurableMessageCount, Instance, ExpiryQueue, ServerPeer, RedeliveryDelay, NonDurableMessageCount, NonDurableSubscriptionsCount, DurableSubscriptionsCount, Clustered, JNDIName, MaxDeliveryAttempts, MessageCounters, FullSize, AllMessageCount, MaxSize, DownCacheSize, SecurityConfig, CreatedProgrammatically, PageSize, Name, DLQ, AllSubscriptionsCount, MessageCounterHistoryDayLimit] > It looks like attribute names now start with an upper case letter instead of a lower case one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2009