October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-473) Add documentation for IBM JRE

by Darran Lofthouse (JIRA)

Add documentation for IBM JRE ----------------------------- Key: SECURITY-473 URL: https://jira.jboss.org/jira/browse/SECURITY-473 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Negotiation Affects Versions: Negotiation_2.0.3.SP2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP3, Negotiation_2.0.4.GA Add documentation for IBM JRE http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rz... http://www.ibm.com/developerworks/java/jdk/security/50/secguides/jgssDocs... Example: - <application-policy name="host-ibm"> <authentication> <login-module code="com.ibm.security.auth.module.Krb5LoginModule" flag="required"> <module-option name="useKeytab">file:///home/darranl/src/negotiation-as/jboss-5.1.0.GA-vm137/bin/service.keytab</module-option> <module-option name="principal">host/testserver(a)VM137DOMAIN.GSSLAB</module-option> <module-option name="credsType">both</module-option> <module-option name="debug">false</module-option> </login-module> </authentication> </application-policy> Also see JBAS-4969 the property jboss.security.disable.secdomain.option=true needs to be set. -- 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

12 years

1
6
0 / 0

[JBoss JIRA] Created: (SECURITY-457) User guide builds incorrectly using Java 6

by Darran Lofthouse (JIRA)

User guide builds incorrectly using Java 6 ------------------------------------------ Key: SECURITY-457 URL: https://jira.jboss.org/jira/browse/SECURITY-457 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA The user guide builds incorrectly running Java 6, however Java 5 still works as expected. Suspect XML parsing differences, documentation should be updated to work with Java 6. -- 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

12 years

1
4
0 / 0

[JBoss JIRA] (SECURITY-704) Login modules should log invalid options.

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-704: ----------------------------------------- Summary: Login modules should log invalid options. Key: SECURITY-704 URL: https://issues.jboss.org/browse/SECURITY-704 Project: PicketBox Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_1_2, Negotiation_2_2_2 Login modules should log a warning for all invalid options. -- 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
1
0 / 0

[JBoss JIRA] (AS7-5850) Core queues created with HornetQ API does not create resources

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5850: -------------------------------- Summary: Core queues created with HornetQ API does not create resources Key: AS7-5850 URL: https://issues.jboss.org/browse/AS7-5850 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.3.Final (EAP) Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 7.2.0.Alpha1 HornetQ core queues can be created through HornetQ API (ClientSession.createQueue()). These queues are not exposed as resources through AS7 management API. When such a queue is created/destroyed, the AS7 HornetQServerResource should check on the Hornet'Q managementService to query for its queues. -- 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
1
0 / 0

[JBoss JIRA] (JGRP-1530) TCPConnectionMap$TCPConnection$ConnectionPeerReceiver allocate and hold a 1.6G byte[]

by Ken Chiu (JIRA)

Ken Chiu created JGRP-1530: ------------------------------ Summary: TCPConnectionMap$TCPConnection$ConnectionPeerReceiver allocate and hold a 1.6G byte[] Key: JGRP-1530 URL: https://issues.jboss.org/browse/JGRP-1530 Project: JGroups Issue Type: Bug Affects Versions: 2.10 Environment: Linux (2.6.18-308.13.1.el5) Java HotSpot(TM) 64-Bit Server VM (20.10-b01, mixed mode) Reporter: Ken Chiu Assignee: Bela Ban In our application, after running a few hours of load test we will encounter OutOfMemoryError. It is caused by we use TCPPING with port_range and hit a JVM defect: http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=a8f3e6a330c2871287... When we use TCPPING with port_range in some linux environments, the application can occasionally connect to a not listened local port. This socket will have the same local/destination port. If this connection is established, bytes written via this socket's OutputStream will be read from this socket's InputStream. In jGtoups, a client socket will send cookie({ 'b', 'e', 'l', 'a' }) as its first data and it will be read from the same socket's InputStream at TCPConnectionMap$TCPConnection$ConnectionPeerReceiver. This will allocation a 1.6G byte[] and hold it forever because the client socket won't read enough data in its whole life. I think a simple solution is to check the connected client socket is a self-connected(local/destination ip and port are the same) and retry next port when this happen. -- 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

2
7
0 / 0

[JBoss JIRA] (JBJCA-913) eclipse UI update - icons and toolbar

by Jeff Zhang (JIRA)

Jeff Zhang created JBJCA-913: -------------------------------- Summary: eclipse UI update - icons and toolbar Key: JBJCA-913 URL: https://issues.jboss.org/browse/JBJCA-913 Project: IronJacamar Issue Type: Task Components: Eclipse Affects Versions: 1.1.0.Beta2 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.1.0.Beta3 -- 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
1
0 / 0

[JBoss JIRA] (JBAS-9519) JPA Entity(Hibernate) update is not replicated with REPL_SYNC cache mode

by Miklos Molnar (JIRA)

Miklos Molnar created JBAS-9519: ----------------------------------- Summary: JPA Entity(Hibernate) update is not replicated with REPL_SYNC cache mode Key: JBAS-9519 URL: https://issues.jboss.org/browse/JBAS-9519 Project: Application Server 3 4 5 and 6 Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, JBC, JPA / Hibernate Affects Versions: JBossAS-5.0.0.GA Environment: windows xp, clustering on same machine with 2 nodes Reporter: Miklos Molnar Assignee: Paul Ferraro Dear JBoss users, I am using jboss AS 5.0 and I have the following issue : I am working on POF with having stateless session bean in cluster (round robin) in front of the hibernate-jpa. The second level cache is turned on. I have tried all cache configuration (optimistic-shared, pessimistic-shared, optimistic-entity, etc...), but I do experience in all cases that the Entity update does not get synced/invalidated on the other node. When a new item is added to the cache it is always replicated well, but the entity update does not. So this means that on only one node the second level cache is updated on the other node the old data remains. So when after the entity update I make the call to the session beans on the different nodes they return different data for the same entity. On the node which received the entity update call everything is fine, however the other node does not receive any notification about the update. I turned the org.hibernate.cache log to INFO and I see "externalPutRead" command notification when a new item is added to the cache on the other node, however I see nothing when the entity is updated by the other node. My JPA Entity's cache configuration is TRANSACTIONAL and the JPA EntityManager access is done in REQUIRED transaction in the session bean. Do I miss anything?You can see my persistence.xml here : -------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="AppStore" transaction-type="JTA"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>java:/appstore</jta-data-source> <class>com.miklos.Customer</class> <class>com.miklos.Item</class> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/> <property name="hibernate.generate_statistics" value="true"/> <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup" /> <property name="hibernate.cache.use_second_level_cache" value="true"/> <property name="hibernate.cache.use_query_cache" value="true"/> <property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.jbc2.MultiplexedJBossCacheRegionFactory"/> <property name="hibernate.cache.region.jbc2.cfg.query" value="replicated-query"/> <property name="hibernate.cache.region.jbc2.cachefactory" value="java:CacheManager"/> <property name="hibernate.cache.region.jbc2.cfg.entity" value="replicated-query"/> <property name="hibernate.cache.region.jbc2.cfg.collection" value="replicated-query"/> </properties> </persistence-unit> </persistence> ------------------------------------------------------------------- Thanks for any comment. regards, Miklos -- 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
0
0 / 0

[JBoss JIRA] (JBRULES-3630) Nested ClassPathResources within ChangeSet use wrong ClassLoader

by Chris Rankin (JIRA)

Chris Rankin created JBRULES-3630: ------------------------------------- Summary: Nested ClassPathResources within ChangeSet use wrong ClassLoader Key: JBRULES-3630 URL: https://issues.jboss.org/browse/JBRULES-3630 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.4.0.Final, 5.1.1.FINAL Environment: Win7 / Java6 / JBoss6 Reporter: Chris Rankin Assignee: Mark Proctor I am trying to load a "rules" JAR dynamically. This JAR contains a {{change-set.xml}} and all of its DRL files: {code:XML} <?xml version="1.0" encoding="UTF-8"?> <change-set xmlns='http://drools.org/drools-5.0/change-set' xmlns:xs='http://www.w3.org/2001/XMLSchema-instance' xs:schemaLocation='http://drools.org/drools-5.0/change-set http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-api/src/...'> <add> <resource source='classpath:com/my/stuff/rules/Stuff.drl' type='DRL' /> </add> </change-set> {code} I am loading the JAR dynamically via {{URLClassLoader}} and _successfully_ creating the ChangeSet resource: {code} Resource changeSet = ResourceFactory.newClassPathResource("change-set.xml", classLoader);{code} However, it then always explodes when I try to add the resource to the {{KnowledgeBuilder}}, complaining that "'com/my/stuff/rules/Stuff.drl' cannot be opened because it does not exist". I am suspecting that the {{KnowledgeBuilder}} is not using my class loader to load {{Stuff.drl}}, despite me passing the correct class loader in via {{KnowledgeBuilderConfiguration}}. (And the "changeset:" handling in {{org.drools.xml.changeset.ResourceHandler}} would seem to support my theory.) -- 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

2
11
0 / 0

[JBoss JIRA] (JBRULES-3640) Rete tree error in Drools 5.4 (related to use of single quotes)

by B Dolbeare (JIRA)

B Dolbeare created JBRULES-3640: ----------------------------------- Summary: Rete tree error in Drools 5.4 (related to use of single quotes) Key: JBRULES-3640 URL: https://issues.jboss.org/browse/JBRULES-3640 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.4.0.Final Environment: All Reporter: B Dolbeare Assignee: Mark Proctor Drools is not producing consistent Rete trees when a rules does an equality check with single quotes when other rules include the similar equality checks using double quotes as demonstrated in the example drl attached. This appears to be a problem with Drools 5.4 as the same drl works correctly in earlier Drools 5.X releases. -- 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

2
2
0 / 0

[JBoss JIRA] (AS7-5843) To make JBOSS AS 7 node communication secure

by hitesh yadav (JIRA)

hitesh yadav created AS7-5843: --------------------------------- Summary: To make JBOSS AS 7 node communication secure Key: AS7-5843 URL: https://issues.jboss.org/browse/AS7-5843 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, Server, Web Affects Versions: 7.1.0.Final Environment: JBOSS AS 7.1.0 final , Windows 7 Reporter: hitesh yadav Assignee: Paul Ferraro I am using JBOSS AS 7.1.0 final in domain mode . There are 4 node in cluster. My requirement is to make node communication secure like HTTPS. As per my understanding JBOSS AS 7 uses JGroups for communication between domain node and JGroups use TCP or UDP protocol for communicate. For example ......when we are using HTTPS protocol, all communication between Browser and Server are done in Encrypted formate........... I need same thing in JBOSS AS 7 node communication ........means all communication between domain nodes must be done in some Encryption/Decryption form or any other way to make communication secure ...... -- 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

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2012