September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBWEB-303) PHP for the php servlet - Downloads - dead link

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBWEB-303?page=com.atlassian.jira.plugin.... ] David Hladky updated JBWEB-303: ------------------------------- Labels: download (was: ) > PHP for the php servlet - Downloads - dead link > ----------------------------------------------- > > Key: JBWEB-303 > URL: https://issues.jboss.org/browse/JBWEB-303 > Project: JBoss Web > Issue Type: Bug > Reporter: David Hladky > Assignee: Remy Maucherat > Priority: Critical > Labels: download > > There is a missing download link on http://jbossweb.jboss.org/downloads/php.html . It appears all links were moved to http://download.jboss.org/jbossweb/modules/php/ except for the Windows link. > I tried to find the missing module in download.jboss.org, but I was not able to find it. Please, fix the page or at least if you know the proper link, I can update the page myself with the proper link. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-303) PHP for the php servlet - Downloads - dead link

by David Hladky (JIRA)

David Hladky created JBWEB-303: ---------------------------------- Summary: PHP for the php servlet - Downloads - dead link Key: JBWEB-303 URL: https://issues.jboss.org/browse/JBWEB-303 Project: JBoss Web Issue Type: Bug Reporter: David Hladky Assignee: Remy Maucherat Priority: Critical There is a missing download link on http://jbossweb.jboss.org/downloads/php.html . It appears all links were moved to http://download.jboss.org/jbossweb/modules/php/ except for the Windows link. I tried to find the missing module in download.jboss.org, but I was not able to find it. Please, fix the page or at least if you know the proper link, I can update the page myself with the proper link. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1179) Guard against Subject modification

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1179?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1179: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1091419|https://bugzilla.redhat.com/show_bug.cgi?id=1091419] from NEW to POST > Guard against Subject modification > ---------------------------------- > > Key: JBJCA-1179 > URL: https://issues.jboss.org/browse/JBJCA-1179 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.26.Final, 1.1.6.Final, 1.2.0.Beta2 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final, 1.1.8.Final, 1.2.0.CR1 > > Attachments: ironjacamar-jdbc.jar > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1212) Pool could keep connections open after shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1212?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1212: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1147412|https://bugzilla.redhat.com/show_bug.cgi?id=1147412] from NEW to POST > Pool could keep connections open after shutdown > ----------------------------------------------- > > Key: JBJCA-1212 > URL: https://issues.jboss.org/browse/JBJCA-1212 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.28.Final, 1.1.8.Final, 1.2.0.CR1 > > > Let MCP check pool status before scheduling prefill -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-66) Provide an operation to request service status report after server has been started

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-66?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-66: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 980219|https://bugzilla.redhat.com/show_bug.cgi?id=980219] from ON_QA to VERIFIED > Provide an operation to request service status report after server has been started > ------------------------------------------------------------------------------------- > > Key: WFCORE-66 > URL: https://issues.jboss.org/browse/WFCORE-66 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emmanuel Hugonnet > Labels: console_prio > Fix For: 1.0.0.Alpha6 > > > For proper healthcare it would beneficial if I could verify the server status after it has been started. I.e. to catch these, which currently only appear in the server log: > [Server:server-three] 17:48:26,636 INFO [org.jboss.as.server] (MSC service thread 1-2) Service status report > [Server:server-three] New missing/unsatisfied dependencies: > [Server:server-three] service jboss.binding.http2 (missing) > [Server:server-three] > [Server:server-three] 17:48:26,636 ERROR [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 3893ms - Started 101 of 149 services (1 services failed or missing dependencies, 47 services are passive or on-demand) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3905) POJO JAX-WS endpoints should not be processed if packaged in EJB-jar

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-3905?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-3905: ---------------------------------- Fix Version/s: 9.0.0.Beta1 > POJO JAX-WS endpoints should not be processed if packaged in EJB-jar > -------------------------------------------------------------------- > > Key: WFLY-3905 > URL: https://issues.jboss.org/browse/WFLY-3905 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Alpha1 > Reporter: Kyle Lape > Assignee: Kyle Lape > Fix For: 9.0.0.Beta1 > > > If a POJO is defined like this in an EJB-jar: > {code:java} > package com.redhat.gss.ws; > @javax.jws.WebService > public class HelloService { > public String sayHello() { > return "Hello World!"; > } > } > {code} > Deployment structure: > {noformat} > klape@localhost ws-java.jar$ tree > . > ├── com > │ └── redhat > │ └── gss > │ └── ws > │ └── HelloService.java > └── META-INF > └── MANIFEST.MF > 5 directories, 2 files > klape@localhost ws-java.jar$ > {noformat} > Upon deployment, you get this in the log: > {noformat} > 16:52:51,372 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-7) JBWS024061: Adding service endpoint metadata: id=com.redhat.gss.ws.HelloService > address=http://localhost:8080/ws-java/HelloService > implementor=com.redhat.gss.ws.HelloService > serviceName={http://ws.gss.redhat.com/}HelloServiceService > portName={http://ws.gss.redhat.com/}HelloServicePort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:52:51,571 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-7) Creating Service {http://ws.gss.redhat.com/}HelloServiceService from class com.redhat.gss.ws.HelloService > 16:52:51,879 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-7) Setting the server's publish address to be http://localhost:8080/ws-java/HelloService > 16:52:51,925 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/remote/klape/work/archives/wildfly-8.1.0.Final/standalone/data/wsdl/ws-java.jar/HelloServiceService.wsdl > {noformat} > Yet when you try to get the WSDL at {{http://localhost:8080/ws-java/HelloService?wsdl}} (pulled from the metadata in the log), you get a 404 error. > JBossWS should not be trying to deploy the POJO endpoint from within an EJB-jar. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3623) Spurious ":" in @Resource annotation 'name' value results in invalid binding but no deployment error

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3623?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3623: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1139188|https://bugzilla.redhat.com/show_bug.cgi?id=1139188] from NEW to ASSIGNED > Spurious ":" in @Resource annotation 'name' value results in invalid binding but no deployment error > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3623 > URL: https://issues.jboss.org/browse/WFLY-3623 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final > Reporter: Brian Stansberry > Assignee: Bartosz Baranowski > Attachments: 01134324.jar, dumpServices.txt > > > See attached jar for a reproducer. Just deploy it. The jar includes it's own source. > An @Resource annotation with a spurious ":" in the name attribute value results in an incorrect binding but no deployment failure: > {code} > @Resources({ > @Resource( > // name="java:jboss/ResourceTestEJB", // ==> this works fine > name="java:jboss:/ResourceTestEJB", // ==> this will not bind the JNDI correctly, and there is no error on deploying EJB > > type=com.test.ResourceEJB.class, > lookup="java:global/01134324/ResourceEJBImpl") > }) > {code} > There is no error reported in the log. > Using jndi-view op in the CLI, I see: > {code} > [standalone@localhost:9990 subsystem=naming] :jndi-view > { > "outcome" => "success", > "result" => { > "java: contexts" => { > ..... > "java:jboss" => { > .... > "java:jboss:" => {"class-name" => "javax.naming.Context"}, > } > } > .... > } > {code} > Any time the jndi-view op is run, the following is logged in the server.log: > {code} > 10:52:02,985 ERROR [org.jboss.as.naming] (management-handler-thread - 5) WFLYNAM0013: Failed to obtain jndi view value for entry java:jboss:.: javax.naming.NameNotFoundException: jboss: -- service jboss.naming.context.java.jboss.jboss: > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) [wildfly-naming-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:132) [wildfly-naming-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.naming.management.JndiViewOperation.access$000(JndiViewOperation.java:47) [wildfly-naming-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.naming.management.JndiViewOperation$1.execute(JndiViewOperation.java:72) [wildfly-naming-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:603) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:481) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:282) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:277) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1060) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:296) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:165) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:204) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:133) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:154) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_45] > at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_45] > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:150) [wildfly-controller-1.0.0.Alpha2.jar:1.0.0.Alpha2] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:297) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:536) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > {code} > If a proper binding can't be done per the annotation value, there should be an exception thrown triggering deployment rollback. > I'll attach an MSC service dump in case it's useful. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3909) Upgrade PicketBox

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3909?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-3909: ---------------------------------------- Peter, probably one for you? > Upgrade PicketBox > ----------------- > > Key: WFLY-3909 > URL: https://issues.jboss.org/browse/WFLY-3909 > Project: WildFly > Issue Type: Component Upgrade > Components: Security > Reporter: David Lloyd > Assignee: Peter Skopek > Fix For: 9.0.0.CR1 > > > Upgrade PicketBox to a version which resolves SECURITY-861. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2456) Using add-user.bat for initial admin user results in "JBAS015234: No mgmt-groups.properties files found"

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2456?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2456: ---------------------------------------- Please take your question to the forums, this issue only remains open so we can review if we can detect permissions issues on the files. > Using add-user.bat for initial admin user results in "JBAS015234: No mgmt-groups.properties files found" > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-2456 > URL: https://issues.jboss.org/browse/WFLY-2456 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.0.0.Beta1 > Environment: Windows 7, 32-bit, jdk1.7.0_45 > Reporter: John Lusk > Assignee: Darran Lofthouse > Fix For: 9.0.0.Beta1 > > > Just getting started w/Wildfly after a long absence from Java. Fresh download, trying to hit admin console, got instructed to use add-user to add an admin user. > c:\usr\local\wildfly-8.0.0.Beta1\bin>.\add-user.bat > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): a > * Error * > JBAS015234: No mgmt-groups.properties files found. > Press any key to continue . . . > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JBOSS_HOME% > C:\usr\local\wildfly-8.0.0.Beta1 > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JAVA_HOME% > C:\java\jdk1.7.0_45 > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %M2_HOME% > C:\usr\local\Maven\3.1.1 > c:\usr\local\wildfly-8.0.0.Beta1\bin>mvn -version > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:2 > 2-0400) > Maven home: C:\usr\local\Maven\3.1.1 > Java version: 1.7.0_45, vendor: Oracle Corporation > Java home: C:\java\jdk1.7.0_45\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" > c:\usr\local\wildfly-8.0.0.Beta1\bin> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3909) Upgrade PicketBox

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3909?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-3909: ----------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > Upgrade PicketBox > ----------------- > > Key: WFLY-3909 > URL: https://issues.jboss.org/browse/WFLY-3909 > Project: WildFly > Issue Type: Component Upgrade > Components: Security > Reporter: David Lloyd > Assignee: Peter Skopek > Fix For: 9.0.0.CR1 > > > Upgrade PicketBox to a version which resolves SECURITY-861. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014