October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5672) Fix the configs verification job

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-5672: --------------------------------- Summary: Fix the configs verification job Key: AS7-5672 URL: https://issues.jboss.org/browse/AS7-5672 Project: Application Server 7 Issue Type: Task Components: Build System Reporter: Ondrej Zizka Assignee: Ondrej Zizka I see that your Jenkins job validating configs [1] (starting up EAP with all distributed configs) doesn't use a proper EAP zip from upstream Jenkins job [2]. It's always run on jboss-eap-6.0.0.CR.zip from Shelly's home [3]. It's very critical bug in our Smoke Tests that we run before hand-off EAP to QE or other teams! [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/EAP6-validate-configs/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBoss-EAP-6.0.x-smok... [3] /home/smcgowan/public_html/jboss-eap-6.0.0.CR.zip -- 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

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] (AS7-5669) Cant connect to jboss using CLI under Cygwin

by Michal Matloka (JIRA)

Michal Matloka created AS7-5669: ----------------------------------- Summary: Cant connect to jboss using CLI under Cygwin Key: AS7-5669 URL: https://issues.jboss.org/browse/AS7-5669 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.1.Final Environment: Win7 x64, java 1.6.0_32 x64 Reporter: Michal Matloka Assignee: Alexey Loubyansky Cant connect to jboss via cli under cygwin. -- 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

11 years, 7 months

4
5
0 / 0

[JBoss JIRA] (JBRULES-3648) Adding a comment containing a comma in the RHS causes a compilation failure

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3648: ------------------------------------ Summary: Adding a comment containing a comma in the RHS causes a compilation failure Key: JBRULES-3648 URL: https://issues.jboss.org/browse/JBRULES-3648 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Adding a comment containing a comma in the RHS, as in the following example, causes a compilation failure. rule R1 when $p : Person( age < name.length ) then insertLogical(new Person("Mario", // this is the age, 38)); end -- 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

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] (AS7-5471) inbound RAR inside EAR: cannot redeploy

by Marcel Šebek (JIRA)

Marcel Šebek created AS7-5471: --------------------------------- Summary: inbound RAR inside EAR: cannot redeploy Key: AS7-5471 URL: https://issues.jboss.org/browse/AS7-5471 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1 Reporter: Marcel Šebek Assignee: Jesper Pedersen There is a regression somewhere after 7.1.1.Final release regarding inbound resource adapters inside EAR. Previously, it was possible to redeploy EAR containing inbound RAR. Now, only the first attempt succeeds, and the subsequent deployments fail. It is reproducible in both latest git master snapshot, and in some older (about a month) snapshot of 7.1.3 branch. I have tested the issue using a very simple EAR containing a trivial inbound RAR, EJB-JAR with a MDB consuming messages from RAR, and a library JAR with listener interface (sources and binaries attached). Here is the relevant part of server log: {{ 14:52:49,934 INFO [org.jboss.as.repository] (HttpManagementService-threads - 2) JBAS014900: Content added at location /home/marcel/compile/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/72/40a822f9ee326844575078a21f942890414c2b/content 14:53:01,460 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "test-ear.ear" 14:53:01,557 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "test-ejb-2.0.0-SNAPSHOT.jar" 14:53:01,557 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "test-rar-2.0.0-SNAPSHOT.rar" 14:53:02,015 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-2) IJ020002: Deployed: file:/home/marcel/compile/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/tmp/vfs/deploymentcae5cd1d0b6a9fb7/test-rar-2.0.0-SNAPSHOT.rar-ca312609764d3645/contents/ 14:53:02,137 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'InboundMDB' with 'test-ear.ear#test-rar-2.0.0-SNAPSHOT' resource adapter 14:53:02,188 INFO [org.hibernate.validator.util.Version] (ServerService Thread Pool -- 64) Hibernate Validator 4.2.0.Final 14:53:02,381 INFO [org.jboss.as.server] (HttpManagementService-threads - 2) JBAS018559: Deployed "test-ear.ear" 14:53:06,898 INFO [stdout] (MSC service thread 1-4) TestRA stopped 14:53:06,923 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment test-ejb-2.0.0-SNAPSHOT.jar in 39ms 14:53:06,925 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test-rar-2.0.0-SNAPSHOT.rar in 40ms 14:53:06,926 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment test-ear.ear in 42ms 14:53:06,997 INFO [org.jboss.as.server] (HttpManagementService-threads - 2) JBAS018558: Undeployed "test-ear.ear" 14:53:11,789 INFO [org.jboss.as.repository] (HttpManagementService-threads - 2) JBAS014901: Content removed from location /home/marcel/compile/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/72/40a822f9ee326844575078a21f942890414c2b/content 14:53:19,937 INFO [org.jboss.as.repository] (HttpManagementService-threads - 2) JBAS014900: Content added at location /home/marcel/compile/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/72/40a822f9ee326844575078a21f942890414c2b/content 14:53:25,438 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "test-ear.ear" 14:53:25,447 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test-ejb-2.0.0-SNAPSHOT.jar" 14:53:25,447 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test-rar-2.0.0-SNAPSHOT.rar" 14:53:25,604 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-2) IJ020002: Deployed: file:/home/marcel/compile/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/tmp/vfs/deploymentcae5cd1d0b6a9fb7/test-rar-2.0.0-SNAPSHOT.rar-26147c352a452c34/contents/ 14:53:25,815 INFO [org.jboss.as.server] (HttpManagementService-threads - 2) JBAS015870: Deploy of deployment "test-ear.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.VIEW.\"test.TestEventListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"test-ear.ear\".deploymentCompleteService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".deploymentCompleteService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"test-ear.ear\".\"test-ejb-2.0.0-SNAPSHOT.jar\".component.InboundMDB.CREATE Missing[jboss.ra.\"test-ear.ear#test-rar-2.0.0-SNAPSHOT\"]"]} 14:53:25,823 INFO [stdout] (MSC service thread 1-3) TestRA stopped 14:53:25,861 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment test-ejb-2.0.0-SNAPSHOT.jar in 45ms 14:53:25,862 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test-rar-2.0.0-SNAPSHOT.rar in 45ms 14:53:25,864 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment test-ear.ear in 48ms }} -- 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

11 years, 7 months

5
9
0 / 0

[JBoss JIRA] (SECURITY-699) Remove

by Paul Gier (JIRA)

Paul Gier created SECURITY-699: ---------------------------------- Summary: Remove Key: SECURITY-699 URL: https://issues.jboss.org/browse/SECURITY-699 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_4_0_12.Final Reporter: Paul Gier Assignee: Peter Skopek Priority: Minor jbosssx includes a dependency on oswego-concurrent library. This library is not necessary since jdk1.5, and the build doesn't seem to require it, so it should be removed from the pom. -- 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

11 years, 7 months

1
2
0 / 0

[JBoss JIRA] (AS7-5477) Allow processing of the module phase to be deferred

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5477: ----------------------------------- Summary: Allow processing of the module phase to be deferred Key: AS7-5477 URL: https://issues.jboss.org/browse/AS7-5477 Project: Application Server 7 Issue Type: Feature Request Components: OSGi, Server Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.CR1 Currently, there are a lot of DUPs in the INSTALL phase that do nothing when there is no Module attached to the DU. This would be the case when an unresolved OSGi bundle runs through the INSTALL phase. Alternatively, it [was suggested|http://lists.jboss.org/pipermail/jboss-as7-dev/2012-August/0065...] to only process INSTALL DUPs when there actually is a Module available. This essentially would boil down to adding a dependency on a resolve service to the MODULE phase. -- 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

11 years, 7 months

1
5
0 / 0

[JBoss JIRA] (AS7-5581) Do not ignore security annotations and deployment descriptor configurations on EJBs in the absence of explicit security domain configuration

by jaikiran pai (JIRA)

jaikiran pai created AS7-5581: --------------------------------- Summary: Do not ignore security annotations and deployment descriptor configurations on EJBs in the absence of explicit security domain configuration Key: AS7-5581 URL: https://issues.jboss.org/browse/AS7-5581 Project: Application Server 7 Issue Type: Feature Request Components: EJB Affects Versions: 7.1.2.Final (EAP) Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.2.0.Alpha1 Consider the following example: {code} @Stateless public class SecureBean { @RolesAllowed("role1") public void restrictedRoles() { ... } @DenyAll public void denyEveryone() { ... } } {code} Notice that the bean methods use EJB security annotations to restrict access *however* the bean doesn't have any explicit @SecurityDomain configured (not even in jboss-ejb3.xml). Right now, AS7 ignores the security restriction on that bean allows everyone to invoke on it, as if security wasn't configured for that bean. This has confused users who expect the invocations to fail since they have used the javax.ejb.* security annotations to restrict access. Many users have asked for a feature where the security domain is defaulted (if not explicitly specified) in cases like this. This JIRA is expected to introduce this feature in AS 7.2.x -- 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

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3645) Add a null-safe dereferencing operator to LHS pattern matching

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3645: ------------------------------------ Summary: Add a null-safe dereferencing operator to LHS pattern matching Key: JBRULES-3645 URL: https://issues.jboss.org/browse/JBRULES-3645 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Provide a null-safe dereferencing operator working as described in this post https://plus.google.com/u/0/b/101003552532172845268/101003552532172845268... -- 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

11 years, 7 months

1
1
0 / 0

[JBoss JIRA] (AS7-5172) cannot define service activator in WAR META-INF, must be in WAR WEB-INF/classes/META-INF

by John Mazzitelli (JIRA)

John Mazzitelli created AS7-5172: ------------------------------------ Summary: cannot define service activator in WAR META-INF, must be in WAR WEB-INF/classes/META-INF Key: AS7-5172 URL: https://issues.jboss.org/browse/AS7-5172 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: John Mazzitelli Priority: Minor (note: I talked to dmlloyed on this in #jboss-as7 - he thinks its a bug, hence why I am filing this JIRA) I have a WAR. I want it to have a service activator in it (I want it to install an MSC service). So, in the WAR's META-INF directory, I create a "services/org.jboss.msc.service.ServiceActivator" file with the appropriate content. The service fails to activate. However, if I put that same META-INF content in my WAR's WEB-INF/classes directory (that is, my WAR has a WEB-INF/classes/META-INF/services/org.jboss.msc.service.ServiceActivator), my service activates fine. I will attach a .war file that you can use to test this. To see what I'm taking about, take the attached war and explode it inside the standalone/deployments directory in AS 7.1.1.Final. Run the app server - you will see in the output this: INFO [stdout] (MSC service thread 1-5) $$$$$$$$$$$$$$$$ SERVICE ACTIVATING! (this output comes from my ServiceActivator's activate() method - it does a System.out.println as soon as activate() is entered). This shows the WEB-INF/classes/META-INF/services being honored. Now shutdown the app server, cd to the deployments directory and cd down into the exploded war directory. Now move that services/ content directly up to the WAR's own META-INF directory: mv WEB-INF/classes/META-INF/services META-INF/ Now run the app server again. Notice you do NOT see the "SERVICE ACTIVATING" message. So it appears the WAR's META-INF/services is ignored when looking for service activators, but when the same services marker file is in WEB-INF/classes/META-INF/services, it works fine. -- 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

11 years, 7 months

4
11
0 / 0

[JBoss JIRA] (JBWEB-243) HTTPS / TLS Client certificate authentication does not give client certificate to server side

by Tomas Gustavsson (JIRA)

[ https://issues.jboss.org/browse/JBWEB-243?page=com.atlassian.jira.plugin.... ] Tomas Gustavsson edited comment on JBWEB-243 at 10/2/12 10:48 AM: ------------------------------------------------------------------ Ok, after much struggling I found out it is because of WSDL location rewrite. The wsdl specifies that my webservice in on http://localhost:8080, which is not the SSL port. In JBoss 5 you would simply comment out: <property name="webServiceHost">${jboss.bind.address}</property> In order for the wsdl rewrite to replace the host and port of: <soap:address location="http://localhost:8443/ejbca/ejbcaws/ejbcaws"/> with what was actually used to call the service. In JBoss previous to JBoss 5 this was default (which seems natural to me), in JBoss 5 we had to configure this to workaround. I found in standalone.xml the part with <wsdl-host>. I found the docs at: https://docs.jboss.org/author/display/JBWS/Advanced+User+Guide There I found the <wsdl-host>jbossws.undefined.host</wsdl-host> setting. With that it does work as expected, This issue can be closed. was (Author: tomasg1): Ok, after much struggling I found out it is because of WSDL location rewrite. The wsdl specifies that my webservice in on http://localhost:8080, which is not the SSL port. In JBoss 5 you would simply comment out: <property name="webServiceHost">${jboss.bind.address}</property> In order for the wsdl rewrite to replace the host and port of: <soap:address location="http://localhost:8443/ejbca/ejbcaws/ejbcaws"/> with what was actually used to call the service. In JBoss previous to JBoss 5 this was default (which seems natural to me), in JBoss 5 we had to configure this to workaround. How can we workaround it in JBoss 7? I found in standalone.xml the part with <wsdl-host>. I found the docs at: https://docs.jboss.org/author/display/JBWS/Advanced+User+Guide There I found the <wsdl-host>jbossws.undefined.host</wsdl-host> setting. With that it does work as expected, This issue can be closed. > HTTPS / TLS Client certificate authentication does not give client certificate to server side > --------------------------------------------------------------------------------------------- > > Key: JBWEB-243 > URL: https://issues.jboss.org/browse/JBWEB-243 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBoss AS 7.1.0.GA > Reporter: Tomas Gustavsson > > We use client certificate authentication (TLS) for our webservice (JAX-WS annotated EJB). > In JBoss 5 and 6 the following code worked to fetch the client certificate in the session bean. > MessageContext msgContext = wsContext.getMessageContext(); > HttpServletRequest request = (HttpServletRequest) msgContext.get(MessageContext.SERVLET_REQUEST); > X509Certificate[] certificates = (X509Certificate[]) request.getAttribute("javax.servlet.request.X509Certificate"); > In JBoss AS 7.1.0.GA no certificate is retrieved. -- 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

11 years, 7 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 October 2012