September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3216) Enable marshalling of Entry Points

by Mark Proctor (JIRA)

Enable marshalling of Entry Points ---------------------------------- Key: JBRULES-3216 URL: https://issues.jboss.org/browse/JBRULES-3216 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1504) management console not loaded via Apache proxy

by u j (JIRA)

management console not loaded via Apache proxy ---------------------------------------------- Key: AS7-1504 URL: https://issues.jboss.org/browse/AS7-1504 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.Alpha1 Reporter: u j Assignee: Heiko Braun Priority: Blocker Accessing the management console via an Apache proxy fails using a 7.1.0 nightly build of 28th July. Apache configuration: NameVirtualHost *:82 <VirtualHost *:82> ProxyPass /console http://127.0.0.1:9990/console ProxyPassReverse /console http://127.0.0.1:9990/console ProxyPass /management http://127.0.0.1:9990/management ProxyPassReverse /management http://127.0.0.1:9990/management </VirtualHost> JBoss standalone.xml: For <interfaces> <interface name="management"> <any-address /> </interface> <interface name="public"> <inet-address value="127.0.0.1"/> </interface> </interfaces> and using http://[server_ip]:82/console, the page is redirected to http://[server_ip]:82/console/App.html, which loads two GWT scripts and then gives an error "NetworkError: 405 Method Not Allowed - http://[server_ip]:9990/management". For <interface name="management"> <inet-address value="[my_remote_address]"/> </interface> I get 01:34:02,264 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC00001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: failed to resolve interface management at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2297) Enable marshalling of events in drools fusion

by Maciej Prochniak (JIRA)

Enable marshalling of events in drools fusion --------------------------------------------- Key: JBRULES-2297 URL: https://jira.jboss.org/jira/browse/JBRULES-2297 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core, drools-core (fusion) Affects Versions: 5.1.0.M1 Reporter: Maciej Prochniak Assignee: Mark Proctor Currently, when one tries to (un)marshall EventFactHandle an exception is thrown, as default marshaller recognizes only DefaultFactHandle. -- 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

14 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JGRP-1363) UNICAST2: NPE with LockService

by Bela Ban (JIRA)

UNICAST2: NPE with LockService ------------------------------ Key: JGRP-1363 URL: https://issues.jboss.org/browse/JGRP-1363 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Attachments: fast.xml "one" unlocked by D::1 2 [ERROR] UNICAST2: couldn't deliver message [dst: B, src: A (3 headers), size=84 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.FRAG2.up(FRAG2.java:181) 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:870) at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:245) at org.jgroups.protocols.UNICAST2.handleDataReceived(UNICAST2.java:746) at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:338) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:583) at org.jgroups.protocols.BARRIER.up(BARRIER.java:102) at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:134) at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:273) at org.jgroups.protocols.MERGE2.up(MERGE2.java:208) at org.jgroups.protocols.Discovery.up(Discovery.java:334) at org.jgroups.protocols.TP.passMessageUp(TP.java:1091) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1646) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1628) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3214) Timers do not work properly with timezones west of GMT

by Edson Tirelli (JIRA)

Timers do not work properly with timezones west of GMT ------------------------------------------------------ Key: JBRULES-3214 URL: https://issues.jboss.org/browse/JBRULES-3214 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Beta1, 5.2.0.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.2.1.Final, 5.3.0.CR1 Timers are not working properly with timezones west of GMT, as the cron algorithm is desined to work from the epoch date (Jan 1st, 1970 00:00:00) but the western timezones cause the clock to start in Dec 31st, 1969. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1364) JGRP-2.10.0.GA deos not disable ipv6

by rsolanki rsolanki (JIRA)

JGRP-2.10.0.GA deos not disable ipv6 ------------------------------------ Key: JGRP-1364 URL: https://issues.jboss.org/browse/JGRP-1364 Project: JGroups Issue Type: Bug Environment: windows 7 Reporter: rsolanki rsolanki Assignee: Bela Ban JGRP-2.10.0.GA deos not disable ipv6, Even After -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Stack=false. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1571) System package list is ignored for resources

by William Louth (JIRA)

System package list is ignored for resources -------------------------------------------- Key: AS7-1571 URL: https://issues.jboss.org/browse/AS7-1571 Project: Application Server 7 Issue Type: Bug Components: Modules Affects Versions: 7.0.1.Final Reporter: William Louth Assignee: David Lloyd https://issues.jboss.org/browse/MODULES-93 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1572) jboss.modules.system.pkgs set in standalone.conf[.bat] and domain.conf[.bat]

by William Louth (JIRA)

jboss.modules.system.pkgs set in standalone.conf[.bat] and domain.conf[.bat] ---------------------------------------------------------------------------- Key: AS7-1572 URL: https://issues.jboss.org/browse/AS7-1572 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.1.Final, 7.0.0.CR1, 7.0.0.Beta3 Reporter: William Louth Assignee: Jason Greene Priority: Blocker Fix For: 7.0.2.Final In both the domain.conf and standalone.conf the following is being set. -Djboss.modules.system.pkgs=org.jboss.byteman This complicates matters for integration with other javaagents which alter the script because this property must also be set and it is not defined in the JVM what precedence is given to multiple same property settings on the command line. Please remove or uncomment in both conf files including window versions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWEB-213) JBoss Web Native Connectors bundles contain wrong paths

by Dan Mazzell (JIRA)

JBoss Web Native Connectors bundles contain wrong paths ------------------------------------------------------- Key: JBWEB-213 URL: https://issues.jboss.org/browse/JBWEB-213 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Environment: Non-Winows, Linux x86, X64, IA64, Solaris, Reporter: Dan Mazzell Assignee: Remy Maucherat Priority: Minor When extracting the jboss-native 2.x tar bundles, the location of the libs should match what the startup script, (run.sh) is expecting. For example, for a Linux x64 system, the run.sh expects the native libraries to be placed into the jboss/bin/META-INF/lib/linux2/x64/ directory, however when tar-gunzipping the jboss-native-2.0.10-linux2-x64-ssl.tar.gz, the binaries are placed in the bin/naitive dir. The tar file path should match what JBoss's run.sh sets up the path as. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1832) Fix the descriptors for the Deployment part of the model

by Kabir Khan (JIRA)

Fix the descriptors for the Deployment part of the model -------------------------------------------------------- Key: AS7-1832 URL: https://issues.jboss.org/browse/AS7-1832 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan This part of the model is currently removed in org.jboss.as.test.surefire.servermodule.ValidateModelTestCase (The test may be moved somewhere else, ping me if you need to find it). The missing parts are: {code} "deployment" => { "description" => "A list of deployments available for use on the server.", "min-occurs" => 0, "model-description" => {"*" => { "description" => "A deployment represents anything that can be deployed (e.g. an application such as EJB-JAR, WAR, EAR, any kind of standard archive such as RAR or JBoss-specific deployment) into a server.", "head-comment-allowed" => true, "tail-comment-allowed" => false, "attributes" => {SNIP}, "operations" => {SNIP}, "children" => { "subsystem" => {"model-description" => {"web" 1) NEEDS A DESCRIPTION => {"children" => {"servlet" 2) NEEDS A DESCRIPTION => {"model-description" => {"*" => undefined 4) WHAT GOES HERE?} }}}}}, "subdeployment" => {"model-description" => {"*" => 5) NEEDS A DESCRIPTION { "description" => "A deployment represents anything that can be deployed (e.g. an application such as EJB-JAR, WAR, E AR, any kind of standard archive such as RAR or JBoss-specific deployment) into a server.", "head-comment-allowed" => true, "tail-comment-allowed" => false, "attributes" => {SNIP}, "operations" => {SNIP}, "children" => {"subsystem" 6) NEEDS A DESCRIPTION => {"model-description" => {"web" 7) NEEDS A DESCRIPTION=> {"children" => {"servlet" 8) NEEDS A DESCRIPTION=> {"model-description" => {"*" => undefined 9) WHAT GOES HERE????}}}}}}} }}} } }} }, {code} This currently lives in https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2011