[JBoss JIRA] (AS7-6924) Cannot resolve against javax.xml.stream.events package capability
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-6924:
--------------------------------
Summary: Cannot resolve against javax.xml.stream.events package capability (was: javax.xml.stream.events package not exported to OSGi bundles)
> Cannot resolve against javax.xml.stream.events package capability
> -----------------------------------------------------------------
>
> Key: AS7-6924
> URL: https://issues.jboss.org/browse/AS7-6924
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, XML Frameworks
> Affects Versions: 8.0.0.Alpha1
> Reporter: Aaron Whiteside
> Assignee: Thomas Diesler
>
> {code}
> 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]]
> 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER
> {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, 3 months
[JBoss JIRA] (AS7-6924) javax.xml.stream.events package not exported to OSGi bundles
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler edited comment on AS7-6924 at 4/17/13 3:31 AM:
--------------------------------------------------------------
Package capabilities that are considered user configuration are unlikely to get added to the default configuration.
You have three options:
# Find a 3rd party bundle that provides them
# Find a module in the AS distribution that contains these packages
# Add them to the configuration as FRAMEWORK_SYSTEMPACKAGES_EXTRA
With the second option you can rely on auto-generated package capabilities or you could define osgi metadata explicitly in jbosgi-xservice.properties like we do for the javax.persistence.api module.
However, I see these packages being exported by the system module
{code}
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset.serial, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset.spi, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
...
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.keyinfo, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.spec, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.datatype, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.namespace, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.parsers, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream.events, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream.util, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.sax, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.stax, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.stream, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.validation, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.xpath, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
{code}
The javax.xml.stream API should however work out of the box. We have test coverage in the jbosgi project for that but not in the AS testsuite AFAICS. Let me add that - it could help to get at the bottom of this.
was (Author: thomas.diesler):
Package capabilities that are considered user configuration are unlikely to get added to the default configuration.
You have three options:
# Find a 3rd party bundle that provides them
# Find a module in the AS distribution that contains these packages
# Add them to the configuration as FRAMEWORK_SYSTEMPACKAGES_EXTRA
With the second option you can rely on auto-generated package capabilities or you could define osgi metadata explicitly in jbosgi-xservice.properties like we do for the javax.persistence.api module.
However, I see these packages being exported by the system module
{code}
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset.serial, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset.spi, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
...
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.keyinfo, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.spec, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.datatype, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.namespace, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.parsers, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream.events, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream.util, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.sax, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.stax, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.stream, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.validation, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.xpath, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
{code}
> javax.xml.stream.events package not exported to OSGi bundles
> ------------------------------------------------------------
>
> Key: AS7-6924
> URL: https://issues.jboss.org/browse/AS7-6924
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, XML Frameworks
> Affects Versions: 8.0.0.Alpha1
> Reporter: Aaron Whiteside
> Assignee: Thomas Diesler
>
> {code}
> 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]]
> 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER
> {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, 3 months
[JBoss JIRA] (AS7-6924) javax.xml.stream.events package not exported to OSGi bundles
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler edited comment on AS7-6924 at 4/17/13 3:24 AM:
--------------------------------------------------------------
Package capabilities that are considered user configuration are unlikely to get added to the default configuration.
You have three options:
# Find a 3rd party bundle that provides them
# Find a module in the AS distribution that contains these packages
# Add them to the configuration as FRAMEWORK_SYSTEMPACKAGES_EXTRA
With the second option you can rely on auto-generated package capabilities or you could define osgi metadata explicitly in jbosgi-xservice.properties like we do for the javax.persistence.api module.
However, I see these packages being exported by the system module
{code}
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset.serial, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,971 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.sql.rowset.spi, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
...
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,973 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.keyinfo, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.crypto.dsig.spec, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.datatype, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.namespace, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.parsers, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream.events, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.stream.util, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.dom, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.sax, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,974 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.stax, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.transform.stream, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.validation, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
09:20:12,975 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-8) XPackageCapability[atts={osgi.wiring.package=javax.xml.xpath, bundle-symbolic-name=system.bundle, bundle-version=0.0.0},[system.bundle:0.0.0]]
{code}
was (Author: thomas.diesler):
The package capabilities that you require are considered user configuration and unlikely to get added to the default configuration.
You have three options:
# Find a 3rd party bundle that provides them
# Find a module in the AS distribution that contains these packages
# Add them to the configuration as FRAMEWORK_SYSTEMPACKAGES_EXTRA
With the second option you can rely on auto-generated package capabilities or you could define osgi metadata explicitly in jbosgi-xservice.properties like we do for the javax.persistence.api module.
> javax.xml.stream.events package not exported to OSGi bundles
> ------------------------------------------------------------
>
> Key: AS7-6924
> URL: https://issues.jboss.org/browse/AS7-6924
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, XML Frameworks
> Affects Versions: 8.0.0.Alpha1
> Reporter: Aaron Whiteside
> Assignee: Thomas Diesler
>
> {code}
> 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]]
> 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER
> {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, 3 months
[JBoss JIRA] (JBDEPLOY-278) DefaultStructureCache uses unescaped path as regex
by Carlo de Wolf (JIRA)
[ https://issues.jboss.org/browse/JBDEPLOY-278?page=com.atlassian.jira.plug... ]
Carlo de Wolf updated JBDEPLOY-278:
-----------------------------------
Attachment: JBDEPLOY-278.patch
> DefaultStructureCache uses unescaped path as regex
> --------------------------------------------------
>
> Key: JBDEPLOY-278
> URL: https://issues.jboss.org/browse/JBDEPLOY-278
> Project: JBoss Deployers
> Issue Type: Bug
> Components: vfs
> Affects Versions: JBDEPLOY-2.0.10.GA
> Reporter: James Livingston
> Attachments: JBDEPLOY-278.diff, JBDEPLOY-278.patch
>
>
> DefaultStructureCache.getLeaves() takes an unescaped pathName and then uses it as part of a regular expression. This could cause problems if pathName contained any characters that have special meaning in regexps.
> The method also creates a new Pattern object on each call which is relatively expensive.
> It could be fixed and the regex creation dropped by using the following:
> bool matches = key.startsWith(pathName) && (key.charAt(pathName.length) == '/') && (key.substring(pathName.length + 1).indexOf('/') == -1)
--
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, 3 months
[JBoss JIRA] (AS7-5586) @PreDestroy not called on view scoped managed bean
by Anders Jespersen (JIRA)
[ https://issues.jboss.org/browse/AS7-5586?page=com.atlassian.jira.plugin.s... ]
Anders Jespersen edited comment on AS7-5586 at 4/17/13 3:13 AM:
----------------------------------------------------------------
testet with our own application. We don't use @PreDestroy, only some @ViewScoped managedbeans that are never released by the webcontainer, ie we run out of memory.
I think this issue is a resolved the way AS7-6709 is (by new JSF-impl), thats why I commented it, so someone might close it or some such thing :)
was (Author: andersbohn):
testet with our own application. We don't use @PreDestroy, only some @ViewScoped managedbeans that are never released by the webcontainer, ie we run out of memory.
I think this issue is a resolved the way AS7-6709 is (by new JSF-impl), thats why I commented it, someone might close it or some such thing :)
> @PreDestroy not called on view scoped managed bean
> --------------------------------------------------
>
> Key: AS7-5586
> URL: https://issues.jboss.org/browse/AS7-5586
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP)
> Environment: Initializing Mojarra 2.1.7-jbossorg-2 (20120412-0335) and all native Jboss JSF impl
> Reporter: Mauricio Fenoglio
> Assignee: Stan Silvert
> Labels: jsf2, jsf21, memoryleak
> Attachments: InjectionTest.jar, InjectionTest.war, InjectionTest.war, InjectionTestV2.jar, TestingJSFMemoryLeak-1.0-SNAPSHOT.war
>
>
> All JSF ManagedBean are not destroyed and generate a great memory problem.
> This happen for View Scopes
> Nor are running @PreDestroy
> It is not possible to have production environments with jsf, so it is a blocker issue.
--
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, 3 months
[JBoss JIRA] (AS7-5586) @PreDestroy not called on view scoped managed bean
by Anders Jespersen (JIRA)
[ https://issues.jboss.org/browse/AS7-5586?page=com.atlassian.jira.plugin.s... ]
Anders Jespersen commented on AS7-5586:
---------------------------------------
testet with our own application. We don't use @PreDestroy, only some @ViewScoped managedbeans that are never released by the webcontainer, ie we run out of memory.
I think this issue is a resolved the way AS7-6709 is (by new JSF-impl), thats why I commented it, someone might close it or some such thing :)
> @PreDestroy not called on view scoped managed bean
> --------------------------------------------------
>
> Key: AS7-5586
> URL: https://issues.jboss.org/browse/AS7-5586
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP)
> Environment: Initializing Mojarra 2.1.7-jbossorg-2 (20120412-0335) and all native Jboss JSF impl
> Reporter: Mauricio Fenoglio
> Assignee: Stan Silvert
> Labels: jsf2, jsf21, memoryleak
> Attachments: InjectionTest.jar, InjectionTest.war, InjectionTest.war, InjectionTestV2.jar, TestingJSFMemoryLeak-1.0-SNAPSHOT.war
>
>
> All JSF ManagedBean are not destroyed and generate a great memory problem.
> This happen for View Scopes
> Nor are running @PreDestroy
> It is not possible to have production environments with jsf, so it is a blocker issue.
--
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, 3 months
[JBoss JIRA] (AS7-6924) javax.xml.stream.events package not exported to OSGi bundles
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6924?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler commented on AS7-6924:
-------------------------------------
The package capabilities that you require are considered user configuration and unlikely to get added to the default configuration.
You have three options:
# Find a 3rd party bundle that provides them
# Find a module in the AS distribution that contains these packages
# Add them to the configuration as FRAMEWORK_SYSTEMPACKAGES_EXTRA
With the second option you can rely on auto-generated package capabilities or you could define osgi metadata explicitly in jbosgi-xservice.properties like we do for the javax.persistence.api module.
> javax.xml.stream.events package not exported to OSGi bundles
> ------------------------------------------------------------
>
> Key: AS7-6924
> URL: https://issues.jboss.org/browse/AS7-6924
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, XML Frameworks
> Affects Versions: 8.0.0.Alpha1
> Reporter: Aaron Whiteside
> Assignee: Thomas Diesler
>
> {code}
> 12:53:16,935 WARN [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011910: Cannot resolve requirements: [XPackageRequirement[dirs={filter=(&(osgi.wiring.package=javax.xml.stream.events)(version>=0.0.0))},[org.springframework.core:3.2.2.RELEASE]]]
> 12:53:16,940 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015970: Defer FIRST_MODULE_USE for org.springframework.core-3.2.2.RELEASE.jar making it NEVER
> {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, 3 months
[JBoss JIRA] (JGRP-1621) NPE on Locking.handleDeleteLockRequest
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1621?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1621:
---------------------------
Fix Version/s: 3.3
Do you have more info on how to reproduce this ?
> NPE on Locking.handleDeleteLockRequest
> --------------------------------------
>
> Key: JGRP-1621
> URL: https://issues.jboss.org/browse/JGRP-1621
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.12.1
> Reporter: freeliuade freeliuade
> Assignee: Bela Ban
> Fix For: 3.3
>
>
> meet NPE on Locking.handleDeleteLockRequest, this NPE seems happens on the network full bandwidth.
> and it seems this exception will result in a lock can't be unlock.
> I'm pretty sure a locker has called unlock, but using LockService.printLocks() still can find the locker is be holding by a thread.
> below is the log:
> 03:00:00,881 WARN [GMS] hyliuds2-8321: not member of view [hyliuds1-33648|2] [hyliuds1-33648]; discarding it
> 03:00:00,890 WARN [GMS] hyliuds2-30414: not member of view [hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852]; discarding it
> 03:00:00,886 WARN [GMS] hyliuds2-13134: not member of view [hyliuds1-13050|4] [hyliuds1-13050, node2-62142, node2-26805]; discarding it
> 03:00:00,924 WARN [GMS] hyliuds2-10154: not member of view [hyliuds1-51819|4] [hyliuds1-51819, node2-14763, node2-26168]; discarding it
> 03:00:01,264 WARN [GMS] jnp://10.101.7.172:1100: not member of view [jnp://10.101.7.24:1100|2] [jnp://10.101.7.24:1100]; discarding it
> 03:00:02,368 WARN [VIEW_SYNC] discarding view as I (hyliuds2-30414) am not member of view ([hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852])
> 03:00:03,659 WARN [GMS] hyliuds2-13134: failed to collect all ACKs (expected=4) for view MergeView::[node2-62142|5] [node2-62142, hyliuds2-13134, node2-26805, hyliuds1-13050], subgroups=[[hyliuds1-13050|4] [hyliuds1-13050, node2-62142, node2-26805], [hyliuds2-13134|3] [hyliuds2-13134]] after 2000ms, missing ACKs from [node2-62142, node2-26805]
> 03:00:06,019 INFO [DomainManager] Installing App sla in domain DefaultDomain.
> 03:00:06,021 INFO [DomainManager] App sla is installed in domain DefaultDomain.
> 03:00:19,321 INFO [StateCache] Accept a new Node list "[jnp://10.101.7.24:1100, jnp://10.101.7.172:1100]"
> 03:00:33,586 WARN [VIEW_SYNC] discarding view as I (hyliuds2-30414) am not member of view ([hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852])
> 03:00:50,634 INFO [StateCache] Accept a new Node list "[jnp://10.101.7.24:1100, jnp://10.101.7.172:1100]"
> 03:01:03,585 WARN [VIEW_SYNC] discarding view as I (hyliuds2-30414) am not member of view ([hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852])
> 03:01:30,951 INFO [DomainManager] Installing App dojoclient in domain DefaultDomain.
> 03:01:30,971 INFO [DomainManager] App dojoclient is installed in domain DefaultDomain.
> 03:01:41,450 WARN [VIEW_SYNC] discarding view as I (hyliuds2-10154) am not member of view ([hyliuds1-51819|4] [hyliuds1-51819, node2-14763, node2-26168])
> 03:01:49,799 WARN [VIEW_SYNC] discarding view as I (hyliuds2-30414) am not member of view ([hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852])
> 03:02:02,298 WARN [VIEW_SYNC] discarding view as I (hyliuds2-10154) am not member of view ([hyliuds1-51819|4] [hyliuds1-51819, node2-14763, node2-26168])
> 03:03:33,370 WARN [VIEW_SYNC] discarding view as I (hyliuds2-10154) am not member of view ([hyliuds1-51819|4] [hyliuds1-51819, node2-14763, node2-26168])
> 03:04:26,623 WARN [GMS] hyliuds2-8321: not member of view [hyliuds1-33648|4] [hyliuds1-33648]; discarding it
> 03:04:35,922 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:35,922 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:37,106 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:53,227 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:53,227 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:53,227 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:53,228 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:53,228 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:53,527 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:54,460 INFO [DomainManager] Deploying project "/apps/sla/projects/SLAAppletProject$Deployment" with release tag "TipOfTrunk" and deployment configuration "Deployment". The overwrite flag is true. The required Runtime Server is "DefaultPool/". The required Feed Server is "auto". The required Data Source for Runtime Server is "auto". The required Data Source for Feed Server is "auto".
> 03:04:54,837 INFO [DomainManager] Project "/apps/sla/projects/SLAAppletProject$Deployment" has been dispatched with Runtime Server "DefaultPool/rs2", Feed Server "fs", Runtime Server Data Source "/vitria/m3o/datasource/DefaultDomain/datasource", Feed Server Data Source "/vitria/m3o/datasource/DefaultDomain/datasource".
> 03:04:54,986 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:54,987 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:04:56,972 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:05:03,650 INFO [DomainManager] Data Source "/vitria/m3o/datasource/DefaultDomain/datasource" was deployed to RuntimeServer "DefaultPool/rs2".
> 03:05:03,692 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:05:03,692 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:05:04,387 INFO [DomainManager] Data Source "/vitria/m3o/datasource/DefaultDomain/datasource" was deployed to FeedServer "fs".
> 03:05:04,956 INFO [DomainManager] Feed "/apps/sla/projects/SLAAppletProject$Deployment/Vitria/Feed/EventSourceExceptionFeed" was deployed to FeedServer "fs".
> 03:05:05,000 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:05:05,001 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:05:05,994 INFO [DomainManager] Feed "/apps/sla/projects/SLAAppletProject$Deployment/Feeds/KPINotifications" was deployed to FeedServer "fs".
> 03:05:06,991 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:05:11,047 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
> 03:05:13,003 INFO [DomainManager] Project "/apps/sla/projects/SLAAppletProject$Deployment" successfully deployed on server "DefaultPool/rs2".
> 03:05:13,007 INFO [DomainManager] Notify an event with type "Deploy".
> 04:57:15,746 WARN [NAKACK] hyliuds2-10154: dropped message from hyliuds1-51819 (not in table [node2-14763, node2-26168, hyliuds2-10154]), view=[node2-14763|6] [node2-14763, hyliuds2-10154, node2-26168]
> 04:57:15,785 WARN [NAKACK] hyliuds2-10154: dropped message from hyliuds1-51819 (not in table [node2-14763, node2-26168, hyliuds2-10154]), view=[node2-14763|6] [node2-14763, hyliuds2-10154, node2-26168]
> 04:57:19,956 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|7] [hyliuds2-8321]
> 04:57:35,009 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|7] [hyliuds2-8321]
> 04:57:43,024 ERROR [UNICAST] couldn't deliver message [dst: hyliuds2-8321, src: hyliuds1-33648 (3 headers), size=95 bytes, flags=DONT_BUNDLE]
> java.lang.NullPointerException
> at org.jgroups.protocols.Locking.handleDeleteLockRequest(Locking.java:505)
> at org.jgroups.protocols.Locking.up(Locking.java:243)
> at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:150)
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:189)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:418)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:400)
> at org.jgroups.protocols.pbcast.GMS.up(GMS.java:891)
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:246)
> at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:170)
> at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:613)
> at org.jgroups.protocols.UNICAST.up(UNICAST.java:294)
> at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:703)
> at org.jgroups.protocols.BARRIER.up(BARRIER.java:119)
> at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:133)
> at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:177)
> at org.jgroups.protocols.FD.up(FD.java:275)
> at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:275)
> at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
> at org.jgroups.protocols.Discovery.up(Discovery.java:293)
> at org.jgroups.protocols.PING.up(PING.java:69)
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1109)
> at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1665)
> at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1647)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
--
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, 3 months
[JBoss JIRA] (JGRP-1621) NPE on Locking.handleDeleteLockRequest
by freeliuade freeliuade (JIRA)
freeliuade freeliuade created JGRP-1621:
-------------------------------------------
Summary: NPE on Locking.handleDeleteLockRequest
Key: JGRP-1621
URL: https://issues.jboss.org/browse/JGRP-1621
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Reporter: freeliuade freeliuade
Assignee: Bela Ban
meet NPE on Locking.handleDeleteLockRequest, this NPE seems happens on the network full bandwidth.
and it seems this exception will result in a lock can't be unlock.
I'm pretty sure a locker has called unlock, but using LockService.printLocks() still can find the locker is be holding by a thread.
below is the log:
03:00:00,881 WARN [GMS] hyliuds2-8321: not member of view [hyliuds1-33648|2] [hyliuds1-33648]; discarding it
03:00:00,890 WARN [GMS] hyliuds2-30414: not member of view [hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852]; discarding it
03:00:00,886 WARN [GMS] hyliuds2-13134: not member of view [hyliuds1-13050|4] [hyliuds1-13050, node2-62142, node2-26805]; discarding it
03:00:00,924 WARN [GMS] hyliuds2-10154: not member of view [hyliuds1-51819|4] [hyliuds1-51819, node2-14763, node2-26168]; discarding it
03:00:01,264 WARN [GMS] jnp://10.101.7.172:1100: not member of view [jnp://10.101.7.24:1100|2] [jnp://10.101.7.24:1100]; discarding it
03:00:02,368 WARN [VIEW_SYNC] discarding view as I (hyliuds2-30414) am not member of view ([hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852])
03:00:03,659 WARN [GMS] hyliuds2-13134: failed to collect all ACKs (expected=4) for view MergeView::[node2-62142|5] [node2-62142, hyliuds2-13134, node2-26805, hyliuds1-13050], subgroups=[[hyliuds1-13050|4] [hyliuds1-13050, node2-62142, node2-26805], [hyliuds2-13134|3] [hyliuds2-13134]] after 2000ms, missing ACKs from [node2-62142, node2-26805]
03:00:06,019 INFO [DomainManager] Installing App sla in domain DefaultDomain.
03:00:06,021 INFO [DomainManager] App sla is installed in domain DefaultDomain.
03:00:19,321 INFO [StateCache] Accept a new Node list "[jnp://10.101.7.24:1100, jnp://10.101.7.172:1100]"
03:00:33,586 WARN [VIEW_SYNC] discarding view as I (hyliuds2-30414) am not member of view ([hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852])
03:00:50,634 INFO [StateCache] Accept a new Node list "[jnp://10.101.7.24:1100, jnp://10.101.7.172:1100]"
03:01:03,585 WARN [VIEW_SYNC] discarding view as I (hyliuds2-30414) am not member of view ([hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852])
03:01:30,951 INFO [DomainManager] Installing App dojoclient in domain DefaultDomain.
03:01:30,971 INFO [DomainManager] App dojoclient is installed in domain DefaultDomain.
03:01:41,450 WARN [VIEW_SYNC] discarding view as I (hyliuds2-10154) am not member of view ([hyliuds1-51819|4] [hyliuds1-51819, node2-14763, node2-26168])
03:01:49,799 WARN [VIEW_SYNC] discarding view as I (hyliuds2-30414) am not member of view ([hyliuds1-3567|4] [hyliuds1-3567, node2-9324, node2-33852])
03:02:02,298 WARN [VIEW_SYNC] discarding view as I (hyliuds2-10154) am not member of view ([hyliuds1-51819|4] [hyliuds1-51819, node2-14763, node2-26168])
03:03:33,370 WARN [VIEW_SYNC] discarding view as I (hyliuds2-10154) am not member of view ([hyliuds1-51819|4] [hyliuds1-51819, node2-14763, node2-26168])
03:04:26,623 WARN [GMS] hyliuds2-8321: not member of view [hyliuds1-33648|4] [hyliuds1-33648]; discarding it
03:04:35,922 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:35,922 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:37,106 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:53,227 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:53,227 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:53,227 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:53,228 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:53,228 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:53,527 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:54,460 INFO [DomainManager] Deploying project "/apps/sla/projects/SLAAppletProject$Deployment" with release tag "TipOfTrunk" and deployment configuration "Deployment". The overwrite flag is true. The required Runtime Server is "DefaultPool/". The required Feed Server is "auto". The required Data Source for Runtime Server is "auto". The required Data Source for Feed Server is "auto".
03:04:54,837 INFO [DomainManager] Project "/apps/sla/projects/SLAAppletProject$Deployment" has been dispatched with Runtime Server "DefaultPool/rs2", Feed Server "fs", Runtime Server Data Source "/vitria/m3o/datasource/DefaultDomain/datasource", Feed Server Data Source "/vitria/m3o/datasource/DefaultDomain/datasource".
03:04:54,986 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:54,987 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:04:56,972 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:05:03,650 INFO [DomainManager] Data Source "/vitria/m3o/datasource/DefaultDomain/datasource" was deployed to RuntimeServer "DefaultPool/rs2".
03:05:03,692 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:05:03,692 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:05:04,387 INFO [DomainManager] Data Source "/vitria/m3o/datasource/DefaultDomain/datasource" was deployed to FeedServer "fs".
03:05:04,956 INFO [DomainManager] Feed "/apps/sla/projects/SLAAppletProject$Deployment/Vitria/Feed/EventSourceExceptionFeed" was deployed to FeedServer "fs".
03:05:05,000 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:05:05,001 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:05:05,994 INFO [DomainManager] Feed "/apps/sla/projects/SLAAppletProject$Deployment/Feeds/KPINotifications" was deployed to FeedServer "fs".
03:05:06,991 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:05:11,047 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|5] [hyliuds2-8321]
03:05:13,003 INFO [DomainManager] Project "/apps/sla/projects/SLAAppletProject$Deployment" successfully deployed on server "DefaultPool/rs2".
03:05:13,007 INFO [DomainManager] Notify an event with type "Deploy".
04:57:15,746 WARN [NAKACK] hyliuds2-10154: dropped message from hyliuds1-51819 (not in table [node2-14763, node2-26168, hyliuds2-10154]), view=[node2-14763|6] [node2-14763, hyliuds2-10154, node2-26168]
04:57:15,785 WARN [NAKACK] hyliuds2-10154: dropped message from hyliuds1-51819 (not in table [node2-14763, node2-26168, hyliuds2-10154]), view=[node2-14763|6] [node2-14763, hyliuds2-10154, node2-26168]
04:57:19,956 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|7] [hyliuds2-8321]
04:57:35,009 WARN [NAKACK] hyliuds2-8321: dropped message from hyliuds1-33648 (not in table [hyliuds2-8321]), view=[hyliuds2-8321|7] [hyliuds2-8321]
04:57:43,024 ERROR [UNICAST] couldn't deliver message [dst: hyliuds2-8321, src: hyliuds1-33648 (3 headers), size=95 bytes, flags=DONT_BUNDLE]
java.lang.NullPointerException
at org.jgroups.protocols.Locking.handleDeleteLockRequest(Locking.java:505)
at org.jgroups.protocols.Locking.up(Locking.java:243)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:150)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:189)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:418)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:400)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:891)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:246)
at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:170)
at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:613)
at org.jgroups.protocols.UNICAST.up(UNICAST.java:294)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:703)
at org.jgroups.protocols.BARRIER.up(BARRIER.java:119)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:133)
at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:177)
at org.jgroups.protocols.FD.up(FD.java:275)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:275)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
at org.jgroups.protocols.Discovery.up(Discovery.java:293)
at org.jgroups.protocols.PING.up(PING.java:69)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1109)
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1665)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1647)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
--
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, 3 months