Today's commit for "AS7-6593 Deprecated AbstractRuntimeOnlyHandler.waitFor()" breaks build
by Frank Langelage
[INFO]
------------------------------------------------------------------------
[INFO] Building JBoss Application Server: Security Subsystem
8.0.0.Alpha1-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
jboss-as-security ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @
jboss-as-security ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-java-version) @
jboss-as-security ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-maven-version) @
jboss-as-security ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.2:create-timestamp
(get-build-timestamp) @ jboss-as-security ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.2:create (get-scm-revision) @
jboss-as-security ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
jboss-as-security ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @
jboss-as-security ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 70 source files to
/home/jboss/JBoss-8.0/jboss-as/security/target/classes
[WARNING]
/home/jboss/JBoss-8.0/jboss-as/security/src/main/java/org/jboss/as/security/context/SecurityDomainJndiInjectable.java:[36,15]
org.infinispan.config.Configuration in org.infinispan.config has been
deprecated
[WARNING]
/home/jboss/JBoss-8.0/jboss-as/security/src/main/java/org/jboss/as/security/plugins/JNDIBasedSecurityManagement.java:[289,84]
org.infinispan.config.Configuration in org.infinispan.config has been
deprecated
[WARNING]
/home/jboss/JBoss-8.0/jboss-as/security/src/main/java/org/jboss/as/security/plugins/JNDIBasedSecurityManagement.java:[289,29]
defineConfiguration(java.lang.String,java.lang.String,org.infinispan.config.Configuration)
in org.infinispan.manager.EmbeddedCacheManager has been deprecated
[WARNING]
/home/jboss/JBoss-8.0/jboss-as/security/src/main/java/org/jboss/as/security/SecurityExtension.java:[142,20]
isRegisterTransformers() in org.jboss.as.controller.ExtensionContext has
been deprecated
[INFO]
[INFO] --- maven-checkstyle-plugin:2.10:checkstyle (check-style) @
jboss-as-security ---
[INFO] Starting audit...
/home/jboss/JBoss-8.0/jboss-as/security/src/main/java/org/jboss/as/security/SecurityMessages.java:41:8:
Unused import - org.jboss.msc.service.ServiceName.
Audit done.
Removing the unused import at line 41 fixes this problem.
11 years, 8 months
Running single tests
by Gunnar Morling
Hi all,
I'm having a problem with running single tests on jboss-as/master.
If I run all the "basic" integration tests (via ./integration-tests.sh test
-Dts.basic), everything works fine. But if when I run a certain test only
(/integration-tests.sh test -Dts.basic -Dtest=NegativeValidationTestCase),
that one will fail.
The log says:
org.jboss.msc.service.DuplicateServiceException: Service
jboss.connector.connection-factory.java:jboss/exported/bv/VCF is already
registered
(See http://pastebin.com/DkrwVgU5 for the complete stack trace). IIUC this
factory is registered by this test itself, but somehow it fails to be
properly removed/cleaned up when only this single test is run.
Does anyone have an idea what's the cause for this and how it can be
avoided?
Thanks a lot,
--Gunnar
11 years, 8 months
Feature deployment
by Thomas Diesler
Hi Brian,
this is related to Provisioner service and Feature deployment
If I remember correctly we cannot have nested management operations. A deployment being a management op can therefore not trigger another deployment op, right?
The general use case is that during deployment of A I want to deploy B which is required by A. Even more general - a user invoked mgmnt op should be able to trigger a deployment op.
Is there any way to work around that?
If not, the only alternative I can see is to have some service that executes the ops in sequence. That service needs to be invoked from client code (i.e. not from a DUP nor from a mgmnt op)
cheers
--thomas
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
11 years, 8 months
Re: [jboss-as7-dev] How to verify a patches for non-public AS
by Jason Greene
Can we please take this internal Red Hat process discussion off the community list? I am sure that 99% of our external subscribers would rather not get spam about this kind of thing, and much rather see technical topics :)
On Apr 17, 2013, at 9:25 AM, Thomas Diesler <thomas.diesler(a)gmail.com> wrote:
> Again, how can a reporter verify a patch that I cannot apply to the jboss-as code base?
> It's a patch for the OSGi 4.2 Framework that nowadays only exists in jboss-eap, AFAIK.
>
> On Apr 17, 2013, at 4:22 PM, Brian Stansberry <brian.stansberry(a)redhat.com> wrote:
>
>> Any fix in EAP has a bugzilla behind it, and QE verifies all bugzillas before they are closed.
>>
>> The fix should be fixed in the upstream AS7 project at the same time or earlier, so the reporter can verify there. Granted, there can be relevant differences between upstream and EAP. For the reporter to verify against EAP itself they'll need to wait for the EAP beta or whatever that contains the fix.
>>
>> On 4/17/13 3:07 AM, Thomas Diesler wrote:
>>> Folks,
>>>
>>> when I resolve a bug for non-public AS, how can the reporter verify that the patch is working so that the issue can be closed?
>>>
>>> cheers
>>> --thomas
>>>
>>
>>
>> --
>> Brian Stansberry
>> Principal Software Engineer
>> JBoss by Red Hat
>
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
11 years, 8 months
Re: [jboss-as7-dev] How to verify a patches for non-public AS
by Brian Stansberry
Any fix in EAP has a bugzilla behind it, and QE verifies all bugzillas
before they are closed.
The fix should be fixed in the upstream AS7 project at the same time or
earlier, so the reporter can verify there. Granted, there can be
relevant differences between upstream and EAP. For the reporter to
verify against EAP itself they'll need to wait for the EAP beta or
whatever that contains the fix.
On 4/17/13 3:07 AM, Thomas Diesler wrote:
> Folks,
>
> when I resolve a bug for non-public AS, how can the reporter verify that the patch is working so that the issue can be closed?
>
> cheers
> --thomas
>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
11 years, 8 months
How to verify a patches for non-public AS
by Thomas Diesler
Folks,
when I resolve a bug for EAP, how can the reporter verify that the patch is working so that the issue can be closed?
cheers
--thomas
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
11 years, 8 months
Re: [jboss-as7-dev] [Resteasy-users] OAuth2 example - different roles per REST Method
by Bill Burke
Yeah, I don't have time to work on this now. You'd have to post both
user id, client id, and credentials of both. It would work similarly to
the oauth example. You'd use the role mapping for the client-id to
filter the ones from the user role mappings. To do this you'd do a
double internal login for the user/client to get their perspective role
mappings. If I'm making any sense....
You'd add a new method modified on the tokenGrant() method contained in
this file:
https://github.com/resteasy/Resteasy/blob/3.0-beta-4/jaxrs/security/skele...
BTW, this is ugly-ass code. Its very hacky. At the time, it seemed
like the only way I could do this and leverage JBoss's existing security
infrastructure.
On 4/16/2013 2:20 PM, Doug Schnelzer wrote:
> That's exactly what we want to do. Could we take what is available in
> the current implementation and put something together? I'm happy to
> work on it. A pointer in the right direction would be great.
>
> Thanks, Doug
>
> On Tue, Apr 16, 2013 at 2:15 PM, Bill Burke <bburke(a)redhat.com
> <mailto:bburke@redhat.com>> wrote:
>
> So you want to specify user, client-id, and their credentials and get
> back a token that is limited to what the client-id is allowed to get?
> All in one request? I don't have an API for this at the moment.
>
> On 4/16/2013 11:50 AM, Doug Schnelzer wrote:
> > So continuing to peel back the onion... and getting somewhere...
> >
> > Thanks for the pointers. I re-read the docs especially around
> >
> >
> http://docs.jboss.org/resteasy/docs/3.0-beta-4/userguide/html/oauth2.html...
> >
> > I noticed that the commerce-roles.properties for the current OAuth2
> > examples has the following:
> >
> > bburke(a)redhat.com <mailto:bburke@redhat.com>
> <mailto:bburke@redhat.com <mailto:bburke@redhat.com>>=user,products
> > admin=admin
> > customer-portal=login
> > product-portal=login
> > third-party=oauth,*
> >
> > I see that the oauth-client-example project is using the client-id
> > "third-party" which is specified in
> > the org.jboss.resteasy.example.oauth.Bootstrap.contextInitialized().
> > What I want to do is to get a bearer tokan programmatically as
> is done
> > in as is done in the client-grant example
> > (i.e.
> org.jboss.resteasy.example.oauth.ProductDatabaseClient.getProducts()
> > ) but I want to specify the client-id so that I can limit the
> roles that
> > are encoded in the bearer token. My assumption is that
> > since
> org.jboss.resteasy.example.oauth.ProductDatabaseClient.getProducts()
> > is using basic authentication to the auth server that the bearer
> token
> > returned will have all roles for bburke(a)redhat.com
> <mailto:bburke@redhat.com>
> > <mailto:bburke@redhat.com <mailto:bburke@redhat.com>>.
> >
> > So my question is can I easily modify the
> > ProductDatabaseClient.getProducts() so that I am specifying a
> client-id
> > for the resulting bearer token and if so can you point at the
> right part
> > of the API that I should be looking at?
> >
> > Thanks much,
> > Doug
> >
> > On Tue, Apr 16, 2013 at 9:33 AM, Bill Burke <bburke(a)redhat.com
> <mailto:bburke@redhat.com>
> > <mailto:bburke@redhat.com <mailto:bburke@redhat.com>>> wrote:
> >
> > OAuth2 does not define the token format. We have defined our
> own token
> > format that transmits signed role-mapping metadata.
> >
> > Check this out:
> >
> >
> http://docs.jboss.org/resteasy/docs/3.0-beta-4/userguide/html/oauth2.html...
> >
> > An "Oauth client" in skeleton key can be assigned a set of
> roles that it
> > is allowed to assume. So, even though a specific user might have
> > "admin" and "user" permissions, you can specify in the "oauth
> client"
> > role mapping that the "oauth client" is only allowed to
> assume "user"
> > permissions. Please read the linked documentation and get
> back to this
> > list if you have more questions.
> >
> > FYI, because our OAuth2 code reuses and is built on top of
> JBoss's
> > existing Security Domain APIs there's only so much
> flexibility that can
> > be provided. In the future, I have plans to leverage the new
> IDM API in
> > AS8 so that you can do more complex role mappings and OAuth2
> scopes .
> > Right now you're limited to what the documentation specifies.
> Please
> > get back to me. I want to know if what we have is good
> enough for now,
> > or if it is unusable.
> >
> > On 4/16/2013 9:17 AM, Doug Schnelzer wrote:
> > > Thanks. As a follow up, I'd like to request a bearer
> token but limit
> > > the Roles identified in the bearer token. I'm looking
> > > at org.jboss.resteasy.example.oauth.ProductDatabaseClient.
> Would
> > it be
> > > right to look that the Access Token Scope to try and
> accomplish this.
> > > What I'm trying to do is have a set of REST services
> protected
> > using
> > > the @RolesAllowed and a less sensitive role. Even though the
> > Resource
> > > Owner may have access to more sensitive roles, I don't wan
> the bearer
> > > token being given to the client to have all of these
> roles. I'm
> > working
> > > my way through
> > > org.jboss.resteasy.skeleton.key.servlet.ServletOAuthClient and
> > mapping
> > > to the OAuth2 spec, but would welcome any guidance
> pointing me in the
> > > right direction.
> > >
> > >
> > >
> > >
> >
> > --
> > Bill Burke
> > JBoss, a division of Red Hat
> > http://bill.burkecentral.com
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 8 months
trying to get log4j on AS 7.1.3 working
by Warner Onstine
I have tried multiple different ways to get my log4j working, but to no
avail. When we were on 7.1.1 the below worked beautifully. We migrated to
7.1.3 (EAP 6.0.1GA) and it is no longer working and I've gone through
several of the forum solutions as well as the migration guide but nothing
seems to be working.
Here's my current jboss-deployment-structure file:
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
<deployment>
<exclusions>
<module name="org.apache.log4j"/>
</exclusions>
</deployment>
<sub-deployment name="rf-service-ejb-0.1-SNAPSHOT.jar">
<exclusions>
<module name="org.apache.log4j"/>
</exclusions>
<dependencies>
<module name="deployment.rf-service-ear.ear.Log4j"/>
</dependencies>
</sub-deployment>
<module name="deployment.rf-service-ear.ear.Log4j">
<resources>
<resource-root path="lib/log4j-1.2.17.jar">
</resource-root>
</resources>
</module>
</jboss-deployment-structure>
I've tried just the basic exclusion (and nothing else). I have also added
this to the server startup (as recommended by the migration guide):
-Dorg.jboss.as.logging.per-deployment=false
My current error is below
11:47:47,252 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool
-- 95) MSC000001: Failed to start service
jboss.deployment.subunit."rf-service-ear.ear"."rf-service-ejb-0.1-SNAPSHOT.jar".component.RfServiceControl.START:
org.jboss.msc.service.StartException in service
jboss.deployment.subunit."rf-service-ear.ear"."rf-service-ejb-0.1-SNAPSHOT.jar".component.RfServiceControl.START:
java.lang.IllegalStateException: JBAS011048: Failed to construct component
instance
at
org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[rt.jar:1.7.0_15]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
[rt.jar:1.7.0_15]
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
[rt.jar:1.7.0_15]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_15]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_15]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct
component instance
at
org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at
org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at
org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:118)
at
org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:133)
at
org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
... 7 more
Caused by: javax.ejb.EJBException: JBAS014580: Unexpected Error
at
org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:161)
at
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228)
at
org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:331)
at
org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:57)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
... 11 more
Caused by: java.lang.LinkageError: loader constraint violation: when
resolving field "LOG" the class loader (instance of
org/jboss/modules/ModuleClassLoader) of the referring class,
com/fourtwosix/razorfish/common/j2eeservices/ServiceControlBase, and the
class loader (instance of org/jboss/modules/ModuleClassLoader) for the
field's resolved type, viceControlBase, have different Class objects for
that type
at
com.fourtwosix.razorfish.j2eeservices.RfServiceControl.startup(RfServiceControl.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[rt.jar:1.7.0_15]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[rt.jar:1.7.0_15]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[rt.jar:1.7.0_15]
at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_15]
at
org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
[jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
[jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
at
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:226)
... 20 more
Anyone have any clue what I'm doing wrong? (Oh, and I've verified that my
log4j.xml file is in my lib directory as is the log4j-1.2.17.jar file.
Thanks in advance, been beating my head against this particular rock for
the past 2 days.
-warner
11 years, 8 months
bundles as modules?
by Bill Burke
Is there any way we could get the OSGi bundles configured and deployed
as modules? I know David talked something about this earlier. We all
talked earlier about the maven artifact stuff I'm doing with JBoss
Modules, and the OSGI bundles are the only thing that I have excluded
from my JBoss AS build script that sets this up.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11 years, 8 months
Community AS8 Roadmap Proposal
by Jason Greene
Hello Everyone,
I am happy to announce a proposed roadmap for AS8. After some discussions with various AS developers and community members, the goals we think are important are:
1. Java EE7
2. Integration of Undertow (EE7 Web Sockets + performant non-blocking i/o)
3. Patching
4. Migration from JacORB to the JDK Orb
5. Transition to the new yet to be announced name
I am proposing an agressive 6 month timeline for this release, with the following key milestones:
May 7 - Release Alpha1
+ Includes undertow, some ee7
June 11 - Release Beta
+ more progress on EE7
July 11 - Release CR1
+ EE7 feature complete
July 25 - Release CR2 if needed
(Hopefully TCK 100% by this date)
August 8 - Release Final
As usual the August 8th date is conditional on the Java EE certification process.
I look forward to any and all feedback. Thanks!
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
11 years, 8 months
