[JBoss JIRA] Created: (JGRP-977) Handle IPv6 link-local addresses correctly when used as bind addresses or multicast addresses
by Richard Achmatowicz (JIRA)
Handle IPv6 link-local addresses correctly when used as bind addresses or multicast addresses
---------------------------------------------------------------------------------------------
Key: JGRP-977
URL: https://jira.jboss.org/jira/browse/JGRP-977
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.6.10, 2.4.6, 2.8
Environment: IPv6 addresses being used
Reporter: Richard Achmatowicz
Assignee: Bela Ban
IPv6 has two types of IP addresses: global addresses and non-global addresses.
Global addresses are unique across the internet (via judicious allocation of network prefixes by authorities). They make up the range 2000::/3 (2000:: to 3fff:ffff:ffff:ffff:ffff:ffff:ffff:ffff). Global addresses generally require no special treatment.
Non-global addresses, like link-local (fe80::/10) and site-local addresses (fec0::/10) are not guaranteed to be unique - in the extreme case, two interfaces on the same host can have the same link-local address. This means that they cannot be used on their own when binding to a socket, but must have extra information (a zone id or sometimes called scope) added to them to disambiguate them. The zone id is basically the interface you want the message to go out on.
A scoped link-local address is one which has a scope appended to it. The way to notate this is to append the scope to the link-local address after a % sign:
<link-local IP address>%<zone id>
where the zone Id can be numerical or simply the next name of the interface. For example, fe80::215:58ff:fec8:81a8%eth0.
A JGroups user may make use of link-local addresses when binding. In that case, we need to make sure that the scope is present, and if not, take some action. Otherwise, when binding to a socket with an unscoped link-local address, a SocketException will be raised.
--
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
16 years, 4 months
[JBoss JIRA] Created: (JBAS-7785) JBossManager cannot register mbean for root context
by Brian Stansberry (JIRA)
JBossManager cannot register mbean for root context
---------------------------------------------------
Key: JBAS-7785
URL: https://jira.jboss.org/jira/browse/JBAS-7785
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-6.0.0.M2, JBossAS-6.0.0.M1, JBossAS-5.1.0.GA
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M3
When JBossManager attempts to register an mbean for itself when it's the manager for a root context (i.e. one who's path is "") it fails with
javax.management.MalformedObjectNameException: Unterminated key property part.
Problem is the ObjectName construction logic is failing to deal with the empty path:
ObjectName clusterName = new ObjectName(domain
+ ":type=Manager,host=" + hostName + ",path="
+ ((Context) container_).getPath());
Fix is:
String path = ((Context) container_).getPath();
path = "".equals(path) ? "/" : path;
ObjectName clusterName = new ObjectName(domain
+ ":type=Manager,host=" + hostName + ",path="
+ path);
Using / as the path is consistent with how StandardContext creates an ObjectName for itself.
This bug ObjectName results in an ERROR in the server log and the mbean for the session manager not being registered, but it doesn't prevent normal operation of the session manager.
--
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
16 years, 4 months
[JBoss JIRA] Created: (JBEE-32) javax.annotations
by Anil Saldhana (JIRA)
javax.annotations
------------------
Key: JBEE-32
URL: https://jira.jboss.org/jira/browse/JBEE-32
Project: JBoss JavaEE APIs
Issue Type: Feature Request
Reporter: Anil Saldhana
Assignee: Shelly McGowan
the tomcat annotations-api.jar has the following annotations:
=================
anil@localhost:~/apache-tomcat-6.0.18/lib$ jar tvf annotations-api.jar
0 Tue Jul 22 02:00:40 CDT 2008 META-INF/
106 Tue Jul 22 02:00:38 CDT 2008 META-INF/MANIFEST.MF
0 Tue Jul 22 02:00:32 CDT 2008 javax/
0 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/
0 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/security/
637 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/Generated.class
396 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/PostConstruct.class
390 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/PreDestroy.class
1179 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/Resource$AuthenticationType.class
903 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/Resource.class
427 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/Resources.class
433 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/security/DeclareRoles.class
393 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/security/DenyAll.class
409 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/security/PermitAll.class
447 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/security/RolesAllowed.class
418 Tue Jul 22 02:00:30 CDT 2008 javax/annotation/security/RunAs.class
0 Tue Jul 22 02:00:30 CDT 2008 javax/ejb/
629 Tue Jul 22 02:00:30 CDT 2008 javax/ejb/EJB.class
398 Tue Jul 22 02:00:30 CDT 2008 javax/ejb/EJBs.class
0 Tue Jul 22 02:00:30 CDT 2008 javax/persistence/
737 Tue Jul 22 02:00:30 CDT 2008 javax/persistence/PersistenceContext.class
1085 Tue Jul 22 02:00:30 CDT 2008 javax/persistence/PersistenceContextType.class
459 Tue Jul 22 02:00:30 CDT 2008 javax/persistence/PersistenceContexts.class
404 Tue Jul 22 02:00:30 CDT 2008 javax/persistence/PersistenceProperty.class
524 Tue Jul 22 02:00:30 CDT 2008 javax/persistence/PersistenceUnit.class
450 Tue Jul 22 02:00:30 CDT 2008 javax/persistence/PersistenceUnits.class
0 Tue Jul 22 02:00:32 CDT 2008 javax/xml/
0 Tue Jul 22 02:00:32 CDT 2008 javax/xml/ws/
633 Tue Jul 22 02:00:32 CDT 2008 javax/xml/ws/WebServiceRef.class
434 Tue Jul 22 02:00:32 CDT 2008 javax/xml/ws/WebServiceRefs.class
=============================================
Some of these are generic cross cutting annotations that should not reside in for example, the jboss ejb3 jars.
Carlo had mentioned sometime back that he intends to pull out the annotations from ejb3 into a separate module
under javaee project.
--
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
16 years, 4 months
[JBoss JIRA] Created: (JBRULES-2433) Facts with event roles in process constraints cause exception
by Paul Borlin (JIRA)
Facts with event roles in process constraints cause exception
-------------------------------------------------------------
Key: JBRULES-2433
URL: https://jira.jboss.org/jira/browse/JBRULES-2433
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Paul Borlin
Assignee: Mark Proctor
When the following conditions are met, a runtime exception is thrown when the following said type is inserted into working memory:
1. A ruleflow and rule definition are asserted into the knowledgebase
2. The rule definition declares a type as being an "event". (declare myType @role( event ) @timestamp( value ) end )
3. The ruleflow references that type in a constraint.
4. A rule in the rule definition has a LHS constraint that references that type as an event (i.e., code such as "over window:time( 12M )" is used)
Attached is a JUnit test that reproduces issue. The following stack trace is the result:
java.lang.ClassCastException: org.drools.common.DefaultFactHandle cannot be cast to org.drools.common.EventFactHandle
at org.drools.rule.SlidingTimeWindow.updateNextExpiration(SlidingTimeWindow.java:198)
at org.drools.rule.SlidingTimeWindow.assertRightTuple(SlidingTimeWindow.java:120)
at org.drools.rule.BehaviorManager.assertRightTuple(BehaviorManager.java:88)
at org.drools.reteoo.JoinNode.assertObject(JoinNode.java:186)
at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:42)
at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:147)
at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:360)
at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:337)
at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:184)
at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:146)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1093)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1044)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:829)
at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:233)
at com.company.RuleFlowTest.pepPostEvent(RuleFlowTest.java:83)
--
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
16 years, 4 months
[JBoss JIRA] Created: (JBVFS-144) vfs30 does not play well with 3rd party registering URLHandlers
by Thomas Diesler (JIRA)
vfs30 does not play well with 3rd party registering URLHandlers
---------------------------------------------------------------
Key: JBVFS-144
URL: https://jira.jboss.org/jira/browse/JBVFS-144
Project: JBoss VFS
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0.CR3
Reporter: Thomas Diesler
Assignee: John Bailey
The Felix OSGi Framework registers URLHandlers
http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.framework...
If it does so all access to file resources breaks and you should see
14:00:38,361 INFO [FelixIntegration] JBossOSGi Felix - 2.0.2.SP1-SNAPSHOT
14:01:52,483 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://java.sun.com/dtd/web-app_2_3.dtd
14:02:00,703 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd
14:02:01,190 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://www.jboss.org/j2ee/dtd/service-ref_5_0.dtd
14:02:03,064 WARN [JBossEntityResolver] Cannot load systemId from resource: connector_1_5.xsd
14:02:03,065 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd
14:02:04,243 WARN [JBossEntityResolver] Cannot load systemId from resource: j2ee_1_4.xsd
14:02:04,245 WARN [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd
14:02:05,411 WARN [JBossEntityResolver] Cannot load systemId from resource: xml.xsd
Later there are also various classloading issues.
The URLHandlers can be disabled like this
<entry><key>felix.service.urlhandlers</key><value>false</value></entry>
However then, you'll see a variation of [JBVFS-142]
Caused by: java.lang.NullPointerException
at org.jboss.vfs.VirtualJarInputStream.read(VirtualJarInputStream.java:149)
at org.jboss.vfs.VirtualJarInputStream.read(VirtualJarInputStream.java:142)
at org.apache.felix.framework.cache.BundleCache.copyStreamToFile(BundleCache.java:254)
at org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:167)
at org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:80)
at org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:58)
at org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:1020)
at org.apache.felix.framework.cache.BundleArchive.revise(BundleArchive.java:631)
at org.apache.felix.framework.cache.BundleArchive.<init>(BundleArchive.java:147)
at org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:176)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2317)
--
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
16 years, 4 months