[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on WFLY-3189:
-----------------------------------
I'll try to get to verify the patch asap. Please remember to update the schema on the jboss website as well: http://www.jboss.org/schema/jbossas/
We generally pull in all schema updates from the website to make sure we have the most up-to-date schema available. Merging changes makes this problematic. If this change would be inappropriate to be made on the publicly available schema, we should discuss this further.
> Error validating jboss-ejb3.xml.
> --------------------------------
>
> Key: WFLY-3189
> URL: https://issues.jboss.org/browse/WFLY-3189
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Final
> Environment: WildFly 8.0.0.Final
> Reporter: shinzey shinzey
> Assignee: David Lloyd
> Attachments: p.patch
>
>
> I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error:
> {noformat}
> src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33]
> src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35]
> src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37]
> src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35]
> src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39]
> {noformat}
> The jboss-ejb3.xml is quite simple:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss:ejb-jar version="3.1" impl-version="2.0"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
> xmlns:s="urn:security:1.1"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd
> http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd">
> <assembly-descriptor>
> <s:security>
> <ejb-name>*</ejb-name>
> <s:security-domain>testsd</s:security-domain>
> </s:security>
> </assembly-descriptor>
> </jboss:ejb-jar>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-838) Can't get implementing classname for JSR77 MBean
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-838?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated WFLY-838:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1138595
> Can't get implementing classname for JSR77 MBean
> ------------------------------------------------
>
> Key: WFLY-838
> URL: https://issues.jboss.org/browse/WFLY-838
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Reporter: Anders Welen
> Priority: Minor
> Fix For: Awaiting Volunteers
>
>
> The following exception are thrown when asking the MBean server for the classname implementing "jboss.jsr77:j2eeType=WebModule,name=MyWar.war,J2EEServer=default".
> It should be a legal call. Why are the code clearly states it's illegal?
>
> java.lang.IllegalStateException: JBAS019905: Should not get called
> at org.jboss.as.jsr77.managedobject.J2EEDeployedObjectHandlers$J2EEModuleHandler.queryObjectNames(J2EEDeployedObjectHandlers.java:245)
> at org.jboss.as.jsr77.managedobject.BaseHandler.getMBeanInfo(BaseHandler.java:64)
> at org.jboss.as.jsr77.managedobject.J2EEDeployedObjectHandlers.getMBeanInfo(J2EEDeployedObjectHandlers.java:147)
> at org.jboss.as.jsr77.managedobject.ManagedObjectHandlerRegistry.getMBeanInfo(ManagedObjectHandlerRegistry.java:112)
> at org.jboss.as.jsr77.subsystem.JSR77ManagementMBeanServer.getMBeanInfo(JSR77ManagementMBeanServer.java:179)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanInfo(PluggableMBeanServerImpl.java:212)
>
> The error can easily be triggered by using JConsole to browse the same MBean.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-3816) ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
by Yannick Lorenzati (JIRA)
[ https://issues.jboss.org/browse/WFLY-3816?page=com.atlassian.jira.plugin.... ]
Yannick Lorenzati commented on WFLY-3816:
-----------------------------------------
With IBM JDK 7 and Jboss as 7.2 : still the same bug, and the workaround of adding
<path name="com/ibm/crypto"/>
<path name="com/ibm/crypto/provider"/>
in the module.xml of ibm.jdk is still working
> ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
> ----------------------------------------------------------------------
>
> Key: WFLY-3816
> URL: https://issues.jboss.org/browse/WFLY-3816
> Project: WildFly
> Issue Type: Bug
> Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final
> Environment: Linux / Aix ; IBM JDK 1.6
> Reporter: Yannick Lorenzati
> Assignee: Jason Greene
> Priority: Minor
>
> I use Jboss AS 7.2.0 with IBM JDK 1.6
> One of my applications try to load the security provider com.ibm.crypto.provider.IBMJCE but I got an ClassNotFoundException.
> I think it’s because in the ibm.jdk module.xml we need to add the package of the security provider like this
> <module xmlns="urn:jboss:module:1.1" name="ibm.jdk">
> <resources>
> </resources>
> <dependencies>
> <system export="true">
> <paths>
> <path name="com/ibm"/>
> <path name="com/ibm/jvm"/>
> <path name="com/ibm/jvm/io"/>
> <path name="com/ibm/jvm/util"/>
> <path name="com/ibm/match"/>
> <path name="com/ibm/misc"/>
> <path name="com/ibm/net"/>
> <path name="com/ibm/nio"/>
> <path name="com/ibm/nio/ch"/>
> <path name="com/ibm/security/auth"/>
> <path name="com/ibm/security/bootstrap"/>
> <path name="com/ibm/security/auth/module"/>
> <path name="com/ibm/security/util"/>
> </paths>
> </system>
> </dependencies>
> </module>
> We need to add this
> <path name="com/ibm/crypto"/>
> <path name="com/ibm/crypto/provider"/>
> Can't do a pull request at work, but i hope this help
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-3816) ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3816?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3816:
-----------------------------------
You can also try AS 7.2 with JDK7, I would even recommend you to do that. AS jdk6 is really really old.
> ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
> ----------------------------------------------------------------------
>
> Key: WFLY-3816
> URL: https://issues.jboss.org/browse/WFLY-3816
> Project: WildFly
> Issue Type: Bug
> Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final
> Environment: Linux / Aix ; IBM JDK 1.6
> Reporter: Yannick Lorenzati
> Assignee: Jason Greene
> Priority: Minor
>
> I use Jboss AS 7.2.0 with IBM JDK 1.6
> One of my applications try to load the security provider com.ibm.crypto.provider.IBMJCE but I got an ClassNotFoundException.
> I think it’s because in the ibm.jdk module.xml we need to add the package of the security provider like this
> <module xmlns="urn:jboss:module:1.1" name="ibm.jdk">
> <resources>
> </resources>
> <dependencies>
> <system export="true">
> <paths>
> <path name="com/ibm"/>
> <path name="com/ibm/jvm"/>
> <path name="com/ibm/jvm/io"/>
> <path name="com/ibm/jvm/util"/>
> <path name="com/ibm/match"/>
> <path name="com/ibm/misc"/>
> <path name="com/ibm/net"/>
> <path name="com/ibm/nio"/>
> <path name="com/ibm/nio/ch"/>
> <path name="com/ibm/security/auth"/>
> <path name="com/ibm/security/bootstrap"/>
> <path name="com/ibm/security/auth/module"/>
> <path name="com/ibm/security/util"/>
> </paths>
> </system>
> </dependencies>
> </module>
> We need to add this
> <path name="com/ibm/crypto"/>
> <path name="com/ibm/crypto/provider"/>
> Can't do a pull request at work, but i hope this help
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-3816) ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
by Yannick Lorenzati (JIRA)
[ https://issues.jboss.org/browse/WFLY-3816?page=com.atlassian.jira.plugin.... ]
Yannick Lorenzati commented on WFLY-3816:
-----------------------------------------
Woah. This is really fast.
I use Jboss as 7.2 so I just check :
the package name is still the same in IBM JDK 7
The line bellow are still missing in wildfly 8.1
So, if i 'm right on how the ibm.jdk module work, the problem also happens
If you want i can do a real test this afternoon, but i'm not sur my application are wildfly 8.1 compliant
> ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
> ----------------------------------------------------------------------
>
> Key: WFLY-3816
> URL: https://issues.jboss.org/browse/WFLY-3816
> Project: WildFly
> Issue Type: Bug
> Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final
> Environment: Linux / Aix ; IBM JDK 1.6
> Reporter: Yannick Lorenzati
> Assignee: Jason Greene
> Priority: Minor
>
> I use Jboss AS 7.2.0 with IBM JDK 1.6
> One of my applications try to load the security provider com.ibm.crypto.provider.IBMJCE but I got an ClassNotFoundException.
> I think it’s because in the ibm.jdk module.xml we need to add the package of the security provider like this
> <module xmlns="urn:jboss:module:1.1" name="ibm.jdk">
> <resources>
> </resources>
> <dependencies>
> <system export="true">
> <paths>
> <path name="com/ibm"/>
> <path name="com/ibm/jvm"/>
> <path name="com/ibm/jvm/io"/>
> <path name="com/ibm/jvm/util"/>
> <path name="com/ibm/match"/>
> <path name="com/ibm/misc"/>
> <path name="com/ibm/net"/>
> <path name="com/ibm/nio"/>
> <path name="com/ibm/nio/ch"/>
> <path name="com/ibm/security/auth"/>
> <path name="com/ibm/security/bootstrap"/>
> <path name="com/ibm/security/auth/module"/>
> <path name="com/ibm/security/util"/>
> </paths>
> </system>
> </dependencies>
> </module>
> We need to add this
> <path name="com/ibm/crypto"/>
> <path name="com/ibm/crypto/provider"/>
> Can't do a pull request at work, but i hope this help
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1877) System.nanoTime() can be negative
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1877?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1877:
---------------------------
Summary: System.nanoTime() can be negative (was: System.nanoTime() may be negative)
> System.nanoTime() can be negative
> ---------------------------------
>
> Key: JGRP-1877
> URL: https://issues.jboss.org/browse/JGRP-1877
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6
>
>
> According to the javadoc, {{System.nanoTime()}} should only be used to measure _elapsed time_, but not compute a _target time in the future_, as {{nanoTime()}} might return a a time in the future.
> Code like the one below might fail:
> {code:title=Responses.waitFor()|borderStyle=solid}
> public boolean waitFor(long timeout) {
> long wait_time;
> final long target_time=System.nanoTime() + TimeUnit.NANOSECONDS.convert(timeout, TimeUnit.MILLISECONDS); // ns
> lock.lock();
> try {
> while(!done && (wait_time=target_time - System.nanoTime()) > 0) {
> try {
> cond.await(wait_time,TimeUnit.NANOSECONDS);
> }
> catch(InterruptedException e) {
> }
> }
> return done;
> }
> finally {
> lock.unlock();
> }
> }
> {code}
> When computing {{target_time}}, {{System.nanoTime()}} could return a negative value (numeric overflow) or a value in the future. In the first case, {{target_time}} could be negative, so the method would not block at all. In the latter case, {{target_time}} could be huge, so the method would block for a long time.
> Investigate all occurrences where we use {{nanoTime()}} to compute a time in the future, and see what impact a future value value could have. Possibly replace with {{System.currentTimeMillis()}} or the _time service_.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1877) System.nanoTime() may be negative
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1877?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1877:
---------------------------
Description:
According to the javadoc, {{System.nanoTime()}} should only be used to measure _elapsed time_, but not compute a _target time in the future_, as {{nanoTime()}} might return a a time in the future.
Code like the one below might fail:
{code:title=Responses.waitFor()|borderStyle=solid}
public boolean waitFor(long timeout) {
long wait_time;
final long target_time=System.nanoTime() + TimeUnit.NANOSECONDS.convert(timeout, TimeUnit.MILLISECONDS); // ns
lock.lock();
try {
while(!done && (wait_time=target_time - System.nanoTime()) > 0) {
try {
cond.await(wait_time,TimeUnit.NANOSECONDS);
}
catch(InterruptedException e) {
}
}
return done;
}
finally {
lock.unlock();
}
}
{code}
When computing {{target_time}}, {{System.nanoTime()}} could return a negative value (numeric overflow) or a value in the future. In the first case, {{target_time}} could be negative, so the method would not block at all. In the latter case, {{target_time}} could be huge, so the method would block for a long time.
Investigate all occurrences where we use {{nanoTime()}} to compute a time in the future, and see what impact a future value value could have. Possibly replace with {{System.currentTimeMillis()}} or the _time service_.
was:
According to the javadoc, {{System.nanoTime()}} should only be used to measure _elapsed time_, but not compute a _target time in the future_, as {{nanoTime()}} might return a a time in the future.
Code like the one below might fail:
{code:title=Responses.waitFor()|borderStyle=solid}
public boolean waitFor(long timeout) {
long wait_time;
final long target_time=System.nanoTime() + TimeUnit.NANOSECONDS.convert(timeout, TimeUnit.MILLISECONDS); // ns
lock.lock();
try {
while(!done && (wait_time=target_time - System.nanoTime()) > 0) {
try {
cond.await(wait_time,TimeUnit.NANOSECONDS);
}
catch(InterruptedException e) {
}
}
return done;
}
finally {
lock.unlock();
}
}
{code}
Investigate all occurrences where we use {{nanoTime()}} to compute a time in the future, and see what impact a future value value could have. Possibly replace with {{System.currentTimeMillis()}} or the _time service_.
> System.nanoTime() may be negative
> ---------------------------------
>
> Key: JGRP-1877
> URL: https://issues.jboss.org/browse/JGRP-1877
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6
>
>
> According to the javadoc, {{System.nanoTime()}} should only be used to measure _elapsed time_, but not compute a _target time in the future_, as {{nanoTime()}} might return a a time in the future.
> Code like the one below might fail:
> {code:title=Responses.waitFor()|borderStyle=solid}
> public boolean waitFor(long timeout) {
> long wait_time;
> final long target_time=System.nanoTime() + TimeUnit.NANOSECONDS.convert(timeout, TimeUnit.MILLISECONDS); // ns
> lock.lock();
> try {
> while(!done && (wait_time=target_time - System.nanoTime()) > 0) {
> try {
> cond.await(wait_time,TimeUnit.NANOSECONDS);
> }
> catch(InterruptedException e) {
> }
> }
> return done;
> }
> finally {
> lock.unlock();
> }
> }
> {code}
> When computing {{target_time}}, {{System.nanoTime()}} could return a negative value (numeric overflow) or a value in the future. In the first case, {{target_time}} could be negative, so the method would not block at all. In the latter case, {{target_time}} could be huge, so the method would block for a long time.
> Investigate all occurrences where we use {{nanoTime()}} to compute a time in the future, and see what impact a future value value could have. Possibly replace with {{System.currentTimeMillis()}} or the _time service_.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1877) System.nanoTime() may be negative
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1877?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1877:
---------------------------
Summary: System.nanoTime() may be negative (was: System.nanoTime() may be in the future)
> System.nanoTime() may be negative
> ---------------------------------
>
> Key: JGRP-1877
> URL: https://issues.jboss.org/browse/JGRP-1877
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6
>
>
> According to the javadoc, {{System.nanoTime()}} should only be used to measure _elapsed time_, but not compute a _target time in the future_, as {{nanoTime()}} might return a a time in the future.
> Code like the one below might fail:
> {code:title=Responses.waitFor()|borderStyle=solid}
> public boolean waitFor(long timeout) {
> long wait_time;
> final long target_time=System.nanoTime() + TimeUnit.NANOSECONDS.convert(timeout, TimeUnit.MILLISECONDS); // ns
> lock.lock();
> try {
> while(!done && (wait_time=target_time - System.nanoTime()) > 0) {
> try {
> cond.await(wait_time,TimeUnit.NANOSECONDS);
> }
> catch(InterruptedException e) {
> }
> }
> return done;
> }
> finally {
> lock.unlock();
> }
> }
> {code}
> Investigate all occurrences where we use {{nanoTime()}} to compute a time in the future, and see what impact a future value value could have. Possibly replace with {{System.currentTimeMillis()}} or the _time service_.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-3816) ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3816?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3816:
-----------------------------------
Given that WildFly requires JDK7 can you confirm this problem also happens on IBM JDK7?
> ClassNotFoundException com.ibm.crypto.provider.IBMJCE with IBM JDK 1.6
> ----------------------------------------------------------------------
>
> Key: WFLY-3816
> URL: https://issues.jboss.org/browse/WFLY-3816
> Project: WildFly
> Issue Type: Bug
> Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final
> Environment: Linux / Aix ; IBM JDK 1.6
> Reporter: Yannick Lorenzati
> Assignee: Jason Greene
> Priority: Minor
>
> I use Jboss AS 7.2.0 with IBM JDK 1.6
> One of my applications try to load the security provider com.ibm.crypto.provider.IBMJCE but I got an ClassNotFoundException.
> I think it’s because in the ibm.jdk module.xml we need to add the package of the security provider like this
> <module xmlns="urn:jboss:module:1.1" name="ibm.jdk">
> <resources>
> </resources>
> <dependencies>
> <system export="true">
> <paths>
> <path name="com/ibm"/>
> <path name="com/ibm/jvm"/>
> <path name="com/ibm/jvm/io"/>
> <path name="com/ibm/jvm/util"/>
> <path name="com/ibm/match"/>
> <path name="com/ibm/misc"/>
> <path name="com/ibm/net"/>
> <path name="com/ibm/nio"/>
> <path name="com/ibm/nio/ch"/>
> <path name="com/ibm/security/auth"/>
> <path name="com/ibm/security/bootstrap"/>
> <path name="com/ibm/security/auth/module"/>
> <path name="com/ibm/security/util"/>
> </paths>
> </system>
> </dependencies>
> </module>
> We need to add this
> <path name="com/ibm/crypto"/>
> <path name="com/ibm/crypto/provider"/>
> Can't do a pull request at work, but i hope this help
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month