[JBoss JIRA] (JBAS-9554) for the jboss4.0.5 ，how to download the jar-version.xml？？
by daisishu daisishu (JIRA)
daisishu daisishu created JBAS-9554:
---------------------------------------
Summary: for the jboss4.0.5 ，how to download the jar-version.xml？？
Key: JBAS-9554
URL: https://issues.jboss.org/browse/JBAS-9554
Project: Application Server 3 4 5 and 6
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Spring integration
Affects Versions: JBossAS-4.0.5.GA
Environment: linux
Reporter: daisishu daisishu
Assignee: Ales Justin
Fix For: JBossAS-4.0.5.GA
for the jboss4.0.5 ，how to download the jar-version.xml？？
--
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
10 years, 3 months
[JBoss JIRA] (WFLY-260) Error
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-260?page=com.atlassian.jira.plugin.s... ]
David Lloyd resolved WFLY-260.
------------------------------
Fix Version/s: (was: 8.0.0.CR1)
(was: 8.0.0.Final)
Resolution: Incomplete Description
Closing due to lack of updates
> Error
> -----
>
> Key: WFLY-260
> URL: https://issues.jboss.org/browse/WFLY-260
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Class Loading
> Reporter: Pablo Ochoa
> Assignee: David Lloyd
>
> Buenos Días,
> Tengo problema con la version 7.1.1 de Jboss por defecto viene creado un Selector y yo intento crea uno nuevo para el manejo de mi classes me arroja el siguiente error
> Preferred repository selector not installed because one has already exists. No problem, using existing selector...
> Estado investigando de verdad no conseguido algo para poder solventar este problema el la ultima version de Jboss 6 no ocurre este mismo problema agradezco toda la colaboración que me puedan brindar
> Te anexo el codigo que utilizo
> import java.util.*;
> import javax.naming.*;
> import org.apache.log4j.Hierarchy;
> import org.apache.log4j.Level;
> import org.apache.log4j.spi.*;
> public class Log4jContextJNDISelector
> implements RepositorySelector
> {
> public Log4jContextJNDISelector(){
> defaultHierarchy = new Hierarchy(new RootLogger(Level.DEBUG));
> }
> public LoggerRepository getLoggerRepository()
> {
> String loggingContextName = null;
> try
> {
> Context ctx = new InitialContext();
> loggingContextName = (String)ctx.lookup("java:comp/env/log4j/logging-context");
> }
> catch(NamingException ne) { }
> if(loggingContextName == null)
> return defaultHierarchy;
> Hierarchy hierarchy = (Hierarchy)hierMap.get(loggingContextName);
> if(hierarchy == null)
> {
> hierarchy = new Hierarchy(new RootLogger(Level.DEBUG));
> hierMap.put(loggingContextName, hierarchy);
> }
> return hierarchy;
> }
> Archivo web.xml esta configuración
> <context-param>
> <param-name>log4j-selector</param-name>
> <param-value>ve.com.prueba.gdis.cia.config.logging.Log4jContextJNDISelector</param-value>
> <description> Selector de repositorios basado en JNDI desde donde se
> configurar el repositorio de logs para esta aplicación
> </description>
> </context-param>
--
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
10 years, 3 months
[JBoss JIRA] (WFLY-1537) getHardwareAddress() return different result on the AS 7.1.1
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-1537?page=com.atlassian.jira.plugin.... ]
David Lloyd resolved WFLY-1537.
-------------------------------
Resolution: Incomplete Description
Closing due to lack of updates.
> getHardwareAddress() return different result on the AS 7.1.1
> ------------------------------------------------------------
>
> Key: WFLY-1537
> URL: https://issues.jboss.org/browse/WFLY-1537
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EE
> Environment: Windows 7 64bit JBOSS AS 7.1.1 Final JDK1.6.0_45
> Reporter: eob free
> Assignee: David Lloyd
>
> {code:java}
> Enumeration e1 = NetworkInterface.getNetworkInterfaces();
> for (e1.hasMoreElements();) {
> NetworkInterface NIC = (NetworkInterface) e1.nextElement();
> byte buf[] = NIC.getHardwareAddress();
> ...
> }
> {code}
> On JBOSS AS 4.2.3,buf[] is not null in some loops,but is all null on JBOSS AS 7.1.1,so can not obtain the MAC address.
--
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
10 years, 3 months
[JBoss JIRA] (WFLY-2689) @Producer method never called when producing a bean from a static module
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/WFLY-2689?page=com.atlassian.jira.plugin.... ]
Pedro Igor commented on WFLY-2689:
----------------------------------
Thanks Jozef. I'm happy that this issue is already being addressed.
> @Producer method never called when producing a bean from a static module
> ------------------------------------------------------------------------
>
> Key: WFLY-2689
> URL: https://issues.jboss.org/browse/WFLY-2689
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CDI / Weld
> Affects Versions: 8.0.0.CR1
> Environment: WildFly 8.0.0.CR1
> Reporter: Pedro Igor
> Assignee: Stuart Douglas
>
> I've configured a static module for PicketLink CDI library. This library provides some extensions which are loaded fine, as described by WFLY-1370.
> However, I'm trying to deploy my application which the following producer method:
> {code}
> @Produces
> @PicketLink
> public PartitionManager getPartitionManager() {
> // produce an instance
> }
> {code}
> Where the @PicketLink annotation is a qualifier that allows my deployment to provide its own instance instead.
> In the PicketLink side, we have a injection point as follows:
> @Inject
> @PicketLink
> private Instance<PartitionManager> partitionManagerInstance;
> Where a call to partitionManagerInstance.isUnsatisfied() always returns true, even if my deployment provides a proper producer method.
> The issue here is that the producer method is never called, despite the use of qualifiers or not.
> FYI, I'm able to listen for events fired by PicketLink during the application startup as follows:
> public void observeIdentityConfigurationEvent(@Observes IdentityConfigurationEvent event) {
> // observer
> }
> Where IdentityConfigurationEvent is one of the lifecycle events fired by PicketLink during the startup.
--
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
10 years, 3 months
[JBoss JIRA] (WFLY-2697) Domain Mode does not start with the IBM JDK
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-2697?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-2697:
----------------------------------------
There is some problem here sending the auth key over stdin. The auth key is a byte[16]. For any byte in the array whose most significant bit is 1 (i.e. a negative number if converted to a signed byte) the value sent and the value received differ.
The sending side code is simply:
final Process process = builder.start();
final OutputStream stdin = process.getOutputStream();
stdin.write(authKey);
stdin.flush();
The reading code is simply:
final byte[] authKey = new byte[16];
StreamUtils.readFully(System.in, authKey);
with the util method a simple loop
{code}
int n = 0;
while (n < len) {
int count = in.read(b, off + n, len - n);
if (count < 0)
throw MESSAGES.readBytes(n);
n += count;
}
{code}
I suspect this is a JVM bug of some sort as the AS code is not doing anything except making basic JDK calls.
> Domain Mode does not start with the IBM JDK
> -------------------------------------------
>
> Key: WFLY-2697
> URL: https://issues.jboss.org/browse/WFLY-2697
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.CR1
> Environment: Windows (OS), IBM JDK 7
> Reporter: Eric Rich
> Assignee: Brian Stansberry
> Fix For: 8.0.0.Final
>
>
> When starting domain mode with the IBM JDK the following is produced 3 out of 4 times.
> [Host Controller] 16:44:06,419 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("start") failed - address: ([
> [Host Controller] ("host" => "master"),
> [Host Controller] ("server-config" => "server-one")
> [Host Controller] ]): java.lang.IllegalStateException: JBAS010986: Host-Controller is already shutdown.
> [Host Controller] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:175)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.startServer(DomainModelControllerService.java:781)
> [Host Controller] at org.jboss.as.host.controller.operations.ServerStartHandler$1.execute(ServerStartHandler.java:107)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:607) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:485) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282)
> [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277) [jbo
> ss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:231) [jboss-as-contr
> oller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:137) [jboss-as-controller-7.
> 3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(Mode
> lControllerClientOperationHandler.java:173) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(Mod
> elControllerClientOperationHandler.java:105) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelC
> ontrollerClientOperationHandler.java:125) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelC
> ontrollerClientOperationHandler.java:121) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at java.security.AccessController.doPrivileged(AccessController.java:366) [vm.jar:1.7.0]
> [Host Controller] at javax.security.auth.Subject.doAs(Subject.java:572) [rt.jar:1.7.0]
> [Host Controller] at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.3.0.Fi
> nal-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(Mode
> lControllerClientOperationHandler.java:121) [jboss-as-controller-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:283) [jboss-a
> s-protocol-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:504) [j
> boss-as-protocol-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) [rt.jar:1.7.0]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626) [rt.jar:1.7.0]
> [Host Controller] at java.lang.Thread.run(Thread.java:804) [vm.jar:1.7.0]
> [Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Fin
> al-redhat-1]
> [Host Controller]
--
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
10 years, 3 months
[JBoss JIRA] (WFLY-2704) FORM authentication credentials lost on failover
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-2704:
----------------------------------
Summary: FORM authentication credentials lost on failover
Key: WFLY-2704
URL: https://issues.jboss.org/browse/WFLY-2704
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: 8.0.0.CR1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 8.0.0.Final
Unlike BASIC, DIGEST, and CERT authentication, FORM authentication requires an additional server side mechanism to store the credentials from the login form so that a user does not need to reauthenticate on failover.
Traditionally, clustered SSO was the mechanism of choice (see https://issues.jboss.org/browse/JBAS-1900 )
An analogous strategy is needed for Undertow.
--
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
10 years, 3 months
[JBoss JIRA] (DROOLS-387) NoSuchElementException on addKnowledgePackages when a "not" follows an "eval"
by Davide Sottara (JIRA)
[ https://issues.jboss.org/browse/DROOLS-387?page=com.atlassian.jira.plugin... ]
Davide Sottara closed DROOLS-387.
---------------------------------
Resolution: Done
> NoSuchElementException on addKnowledgePackages when a "not" follows an "eval"
> -----------------------------------------------------------------------------
>
> Key: DROOLS-387
> URL: https://issues.jboss.org/browse/DROOLS-387
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final
> Environment: java version "1.7.0_21"
> Reporter: Jason Saint
> Assignee: Mark Proctor
>
> I apologize if this has already been reported, but I did not see anything in search results for which this looked like a duplicate.
> With the following 2 rules, compiling the first and adding it to a knowledge base causes subsequent package additions to fail with a NoSuchElementException.
> rule "Problem"
> when
> eval(true == true)
> not String() from "Problem"
> then
> end
> rule "Test1"
> when
> $test : String() from "Test"
> then
> end
> The following java code will produce the exception on the second call to addKnowledgePackages (tried with Drools 5.4 and 5.5)
> {code}
> package com.chiprewards.droolsbug;
> import org.drools.KnowledgeBase;
> import org.drools.KnowledgeBaseFactory;
> import org.drools.builder.KnowledgeBuilder;
> import org.drools.builder.KnowledgeBuilderErrors;
> import org.drools.builder.KnowledgeBuilderFactory;
> import org.drools.io.Resource;
> import org.drools.builder.ResourceType;
> import org.drools.io.ResourceFactory;
> /**
> * Hello world!
> *
> */
> public class App
> {
> public static void main( String[] args )
> {
> KnowledgeBase kBase = KnowledgeBaseFactory.newKnowledgeBase();
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
>
> String problem_rule = "rule \"Problem\"\n when\n eval(true == true)\n not String() from \"Problem\"\n then\nend";
>
> Resource resource = ResourceFactory.newByteArrayResource(problem_rule.getBytes());
> kbuilder.add(resource, ResourceType.DRL);
> if(kbuilder.hasErrors()) {
> System.out.println("First rule had error parsing");
> System.exit(1);
> }
>
> kBase.addKnowledgePackages(kbuilder.getKnowledgePackages());
>
> //Add second rule
>
> String next_rule = "rule \"Test\"\n when\n String() from \"Test\"\n then\nend";
>
> resource = ResourceFactory.newByteArrayResource(next_rule.getBytes());
> kbuilder.add(resource, ResourceType.DRL);
> if(kbuilder.hasErrors()) {
> System.out.println("Second rule had error parsing");
> System.exit(1);
> }
>
> kBase.addKnowledgePackages(kbuilder.getKnowledgePackages());
> }
> }
> {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
10 years, 3 months