October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5682) Allow configure SSL connection in stanalone.xml for email servers

by Alexey Volkov (JIRA)

Alexey Volkov created AS7-5682: ---------------------------------- Summary: Allow configure SSL connection in stanalone.xml for email servers Key: AS7-5682 URL: https://issues.jboss.org/browse/AS7-5682 Project: Application Server 7 Issue Type: Feature Request Components: Mail Affects Versions: 7.1.1.Final Reporter: Alexey Volkov Assignee: Tomaz Cerar Priority: Optional Allow to SSL configure connection to email servers into stanalone.xml Here is the discussion into community https://community.jboss.org/thread/205364 -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] (AS7-2660) wsconsume command line tool: Option --target is ignored

by Andreas Reimer (Created) (JIRA)

wsconsume command line tool: Option --target is ignored ------------------------------------------------------- Key: AS7-2660 URL: https://issues.jboss.org/browse/AS7-2660 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.0.2.Final Reporter: Andreas Reimer Assignee: Alessio Soldano Priority: Minor wsconsume always generates the same code regardless of the -t or --target switch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
5
0 / 0

[JBoss JIRA] (AS7-4899) Datasource names starting with number are invalid and gets deleted

by Luca Molteni (JIRA)

Luca Molteni created AS7-4899: --------------------------------- Summary: Datasource names starting with number are invalid and gets deleted Key: AS7-4899 URL: https://issues.jboss.org/browse/AS7-4899 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Luca Molteni Copy the example datasource into something like <datasource jndi-name="java:jboss/datasources/18DS" pool-name="18DS" enabled="true" use-java-context="true"> <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url> <driver>h2</driver> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> The datasource is not parsed correctly and gets deleted when refreshing using the console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
2
0 / 0

[JBoss JIRA] (JBRULES-3649) Planner: IndexOutOfBoundsException in Benchmarker's BestScoreProblemStatistic.writeGraphStatistic

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3649: ----------------------------------------- Summary: Planner: IndexOutOfBoundsException in Benchmarker's BestScoreProblemStatistic.writeGraphStatistic Key: JBRULES-3649 URL: https://issues.jboss.org/browse/JBRULES-3649 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.5.0.Beta1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 5.5.0.CR1 {code} Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(Unknown Source) at java.util.ArrayList.get(Unknown Source) at org.drools.planner.benchmark.core.statistic.bestscore.BestScoreProblemStatistic.writeGraphStatistic(BestScoreProblemStatistic.java:120) at org.drools.planner.benchmark.core.statistic.AbstractProblemStatistic.writeStatistic(AbstractProblemStatistic.java:82) at org.drools.planner.benchmark.core.statistic.BenchmarkReport.writeReport(BenchmarkReport.java:138) at org.drools.planner.benchmark.core.DefaultPlannerBenchmark.benchmarkingEnded(DefaultPlannerBenchmark.java:295) at org.drools.planner.benchmark.core.DefaultPlannerBenchmark.benchmark(DefaultPlannerBenchmark.java:174) {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, 7 months

1
2
0 / 0

[JBoss JIRA] (AS7-5679) JacORB giop-minor-version doesn't accept 0

by Takayoshi Kimura (JIRA)

Takayoshi Kimura created AS7-5679: ------------------------------------- Summary: JacORB giop-minor-version doesn't accept 0 Key: AS7-5679 URL: https://issues.jboss.org/browse/AS7-5679 Project: Application Server 7 Issue Type: Bug Components: IIOP Affects Versions: 7.1.2.Final (EAP), 7.2.0.Alpha1 Reporter: Takayoshi Kimura Assignee: Takayoshi Kimura Priority: Minor Setting giop-minor-version="0" failed with a validation error and this is not really a designed behavior. {noformat} Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[183,13] Message: "JBAS014708: 0 is an invalid value for parameter giop-minor-version. A minimum value of 1 is required" at org.jboss.as.controller.SimpleAttributeDefinition.parse(SimpleAttributeDefinition.java:154) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.controller.SimpleAttributeDefinition.parseAndSetParameter(SimpleAttributeDefinition.java:207) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.jacorb.JacORBSubsystemParser.parseAttributes(JacORBSubsystemParser.java:691) {noformat} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5675) Restart fail with bundles previously deployed

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-5675?page=com.atlassian.jira.plugin.s... ] Thomas Diesler deleted AS7-5675: -------------------------------- > Restart fail with bundles previously deployed > --------------------------------------------- > > Key: AS7-5675 > URL: https://issues.jboss.org/browse/AS7-5675 > Project: Application Server 7 > Issue Type: Feature Request > Environment: AS7 master (Oct 3 codebase) > Reporter: David Bosschaert > Assignee: Thomas Diesler > > I install a fairly large number of OSGi bundles into AS7 using a script (40+ bundles). The script installs the bundles as follows: > {{jboss-cli.sh -c --command="deploy bundle_x.jar"}} > The installation itself completes without error. > Then I stop AS7 (git ctrl-c) and restart it again. At that point I get an exception: > {code}POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."cxf-bundle-minimal-2.5.4.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "cxf-bundle-minimal-2.5.4.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_35] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_35] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_35] > Caused by: java.lang.NullPointerException > at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.deploy(JaxrsScanningProcessor.java:106) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more{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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4240) NameNotFoundException thrown when trying to read java:*/env context in Servlet container.

by Robert Edgecombe (JIRA)

Robert Edgecombe created AS7-4240: ------------------------------------- Summary: NameNotFoundException thrown when trying to read java:*/env context in Servlet container. Key: AS7-4240 URL: https://issues.jboss.org/browse/AS7-4240 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.1.Final Environment: Windows7 Enterprise x64 Intel Core 2 Duo Oracle Java jdk1.6.0_29 Reporter: Robert Edgecombe Assignee: John Bailey We have many J2EE 1.4 apps that need to be migrated from Oracle Application Server These applications rely on configuration using Environment Entries Most of the answers to issues I have read indicate that this is done using jboss-web.xml but this is not an acceptable solutin as it requires repackaging of the deployment artifact for different servers and different environments and is therefor contrary to the spirit (and I believe the letter) of the JavaEE spec. The documentation on this capability is either hidden or missing. I was tasked with working out how to use the JBOSS tools to configure these values and have been unable to do so. I modified the quickstart helloworld example to accept a value using the @Resource annotation and attempted to set this value using jboss-cli. After several attempts to guess how to do this I modified the servlet to walk down the context tree. This servlet throws a NameNotFoundException when trying to list the bindings at: * java:comp/env * java:app/env * java:module/env I have written the servlet to perform this walk in the following contexts: * Ithe initial context * java: * java:jboss * java:comp * java:module * java:app * java:global java:global seems to be able to accept values added using jboss-cli (not surprising) java:comp, java:module and java:app seem to return some of the expected values (eg ModuleName and AppName) but throw the exception when trying to list entries under */env The initial context and java: seem to display the entries added through jboss-cli Adding a Deployment descriptor (web.xml), that provides values for these entries, results in no entries that are visible through jboss-cli or any of the contexts listed in the servlet. I then ran the following command through jboss-cli and restarted the app /profile=full/subsystem=naming/binding=\/java\:app\/jboss-as-helloworld-ear\/env\/GREETING_TEXT:add(binding-type="simple",value="RE") This resulted in the same NameNotFoundException being thrown at java:app/env when walking the initial context as has been thrown all along when listing env in java:app It also resulted in java:app appearing in the java: context but being empty. Prior to running the add command, java:app did not appear in the initial context or java: context at all. I then ran the following command through jboss-cli and restarted the app /profile=full/subsystem=naming/binding=\/java\:module\/jboss-as-helloworld-ear\/jboss-as-helloworld\/env\/GREETING_TEXT:add(binding-type="simple",value="SJM") This resulted in the same NameNotFoundException being thrown at java:module/env when walking the initial context as has been thrown all along when listing env in java:module It also resulted in java:module appearing in the java: context but being empty. Prior to running the add command, java:module did not appear in the initial context or java: context at all. My conclusion is that my commands in jboss-cli may be the appropriate ones to add the correct entries but that the servlet cannot reach the java:module/env or java:app/env contexts that should be available to it according to the javaEE6 spec. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

6
22
0 / 0

[JBoss JIRA] (AS7-5678) Honor the directory grouping by-type for domain server directories

by James Perkins (JIRA)

James Perkins created AS7-5678: ---------------------------------- Summary: Honor the directory grouping by-type for domain server directories Key: AS7-5678 URL: https://issues.jboss.org/browse/AS7-5678 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management Reporter: James Perkins Assignee: James Perkins Fix For: 7.2.0.CR1 Currently if one of the directories (jboss.server.log.dir, jboss.server.tmp.dir or jboss.server.data.dir) are overridden the directory grouping is ignored. It would be nicer if the directory grouping was set to {{by-type}} the base directory would be used, but the {{by-type}} configuration would be honored. {code} ${JBOSS_HOME}/bin/domain.sh -Djboss.server.log.dir=/var/log/ {code} host.xml {code} <host name="master" xmlns="urn:jboss:domain:1.3"> ... <servers directory-grouping="by-type"> <server name="server-one" group="main-server-group"> </server> <server name="server-two" group="main-server-group" auto-start="true">  <socket-bindings port-offset="150"/> </server> <server name="server-three" group="other-server-group" auto-start="false">  <socket-bindings port-offset="250"/> </server> </servers> </host> {code} Should result in a log directory for {{server-one}} of {{/var/log/server-one/logs/}}. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] (AS7-5677) Split up GlobalOperationHandlers

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5677: ------------------------------------- Summary: Split up GlobalOperationHandlers Key: AS7-5677 URL: https://issues.jboss.org/browse/AS7-5677 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Break into multiple classes; get rid of inner classes so it's easier to see what handler is involved when debugging complex ops. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5374) Windows PowerShell scripts in bin

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5374: ------------------------------------- Summary: Windows PowerShell scripts in bin Key: AS7-5374 URL: https://issues.jboss.org/browse/AS7-5374 Project: Application Server 7 Issue Type: Bug Components: Scripts Reporter: Brian Stansberry Fix For: Open To Community Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
1
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 October 2012