[JBoss JIRA] Created: (EJBTHREE-2265) JndiSessionRegistrarBase registers EJBs with @RemoteBinding twice
by Dennis Reed (JIRA)
JndiSessionRegistrarBase registers EJBs with @RemoteBinding twice
-----------------------------------------------------------------
Key: EJBTHREE-2265
URL: https://issues.jboss.org/browse/EJBTHREE-2265
Project: EJB 3.0
Issue Type: Bug
Components: proxy-impl
Affects Versions: EJB3_1 1.0.6
Reporter: Dennis Reed
Assignee: Dennis Reed
JndiSessionRegistrarBase registers the EJB's ProxyFactory, then immediately unbinds and registers it again.
This causes problems in ProxyClusteringRegistry because the register call sets up a map of cluster members, which is referenced
from the EJB's ReplicantsManagerInterceptor. The unbind then deletes this map in ProxyClusteringRegistry, and the 2nd
register creates a new map that will get updates when the cluster membership changes.
Since the interceptor now has a reference to a different map, it never sees the cluster membership changes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBBUILD-690) The JBoss parent pom should be dual licenced under LGPL and ASL (not just LGPL)
by Geoffrey De Smet (JIRA)
The JBoss parent pom should be dual licenced under LGPL and ASL (not just LGPL)
-------------------------------------------------------------------------------
Key: JBBUILD-690
URL: https://issues.jboss.org/browse/JBBUILD-690
Project: JBoss Build System
Issue Type: Bug
Components: JBoss Parent POM
Affects Versions: JBoss Parent POM - 6
Reporter: Geoffrey De Smet
Assignee: Paul Gier
Fix For: JBoss Parent POM - 6
Drools and jBPM are ASL licensed and therefor can't really depend on LGPL licensed software :(
That includes the parent poms, so the jboss-parent can't be only LGPL licensed.
Option 1: Add the ASL license to make it dual licensed under LGPL and ASL:
{code}
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
{code}
Note: a pom that inherits from the jboss-parent pom and specifies a license, only has it's own license (try yourself with "mvn help:effective-pom".
Option 2: Only use an ASL license, because LGPL can use ASL (and not the other way around).
Option 3: Only use a BSD license, because LGPL and ASL can use that.
Note: you need to specify a license so <distribution>repo</distribution> can be set.
Seperate issue: add <distribution>repo</distribution> to whichever licence it uses.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (LOGTOOL-23) Seems to be an XNIO bug with the processor and JDK7
by James Perkins (JIRA)
Seems to be an XNIO bug with the processor and JDK7
---------------------------------------------------
Key: LOGTOOL-23
URL: https://issues.jboss.org/browse/LOGTOOL-23
Project: Log Tool
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: James Perkins
Assignee: James Perkins
The error appears to be in com.sun.tools.javac.files.JavacFilerManager.
error: Cannot read org.jboss.logging.test package files, cause : java.io.FileNotFoundException: org.jboss.logging.test/ExtendedBasicLogger
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:613)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
error: Cannot read org.jboss.logging.test package files, cause : java.io.FileNotFoundException: org.jboss.logging.test/ExtendedBasicLogger
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1456) How to configure keystore-type and ciphers in jboss 7.0 standalone
by Gabriel Rabbaa (JIRA)
How to configure keystore-type and ciphers in jboss 7.0 standalone
------------------------------------------------------------------
Key: AS7-1456
URL: https://issues.jboss.org/browse/AS7-1456
Project: Application Server 7
Issue Type: Feature Request
Reporter: Gabriel Rabbaa
Fix For: 7.0.0.Final
Hi,
I'm trying to configure standalone.xml file in order to use my keystore certificate but I need to add some more attributes like keystoreType and ciphers.
is it possible to do it?
At the moment could just configure the file store location and its password
{code}
<connector name="https" scheme="https" protocol="HTTP/1.1" socket-binding="https" secure="true">
<ssl name="https" password="my_password" certificate-key-file="../standalone/configuration/server.keystore"/>
</connector>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (AS7-1445) Pax-Logging deployment hangs server
by Thomas Diesler (JIRA)
Pax-Logging deployment hangs server
-----------------------------------
Key: AS7-1445
URL: https://issues.jboss.org/browse/AS7-1445
Project: Application Server 7
Issue Type: Bug
Reporter: Thomas Diesler
Arnaud says,
Trying to deploy an application using pax-logging (1.6.3), it seems to
hang JBoss AS (7)
By waiting some time I had the stackoverflow stack trace above, os I
suspected something wrong with pax-logging service.
If I remove pax-logging service from my application, it works fine.
As JBoss 7 allow to deploy bundles direcly, I tried to deploy
pax-logging-api and pax-logging-service directly and it seems to hand
Jboss as well, the server stop to answer, but anything is log
A simple way t reproduce, start a JBoss AS 7 server, go to the JBoss
console (http://127.0.0.1:9990/console/App.html), the console page
should be displayed
Copy pax-logging-api and pax-logging-service in
$JBOSS_HOME/standalone/deployments, wait for pax logging bundles to be
deployed
Then try to go to the jboss console again, it does not respond anymore.
Is it a known issue ? is there any special configuration to have pax
logging service to work with JBoss 7 ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBRULES-2949) Drools eclipse plugins build should not output stacktraces when trying to check the p2 repository (since upgrade to tycho 0.11.0)
by Geoffrey De Smet (JIRA)
Drools eclipse plugins build should not output stacktraces when trying to check the p2 repository (since upgrade to tycho 0.11.0)
---------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-2949
URL: https://issues.jboss.org/browse/JBRULES-2949
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Priority: Optional
[INFO] Resolving target platform for project MavenProject: org.drools:org.drools.eclipse:5.2.0-SNAPSHOT @ /home/gdesmet/projects/jboss/droolsjbpm/droolsjbpm-tools/drools-eclipse/org.drools.eclipse/pom.xml
java.io.FileNotFoundException: /home/gdesmet/.m2/repository/org/drools/org.drools.eclipse/5.2.0.M1/org.drools.eclipse-5.2.0.M1-p2artifacts.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at org.sonatype.tycho.p2.repository.LocalRepositoryReader.getContents(LocalRepositoryReader.java:28)
at org.sonatype.tycho.p2.repository.LocalRepositoryReader.getContents(LocalRepositoryReader.java:22)
at org.sonatype.tycho.p2.maven.repository.AbstractMavenArtifactRepository.loadMaven(AbstractMavenArtifactRepository.java:73)
at org.sonatype.tycho.p2.maven.repository.AbstractMavenArtifactRepository.<init>(AbstractMavenArtifactRepository.java:61)
at org.sonatype.tycho.p2.maven.repository.LocalArtifactRepository.<init>(LocalArtifactRepository.java:51)
at org.sonatype.tycho.p2.impl.resolver.P2ResolverImpl.setLocalRepositoryLocation(P2ResolverImpl.java:661)
at org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:196)
at org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.resolvePlatform(P2TargetPlatformResolver.java:151)
at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:86)
at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
java.io.FileNotFoundException: /home/gdesmet/.m2/repository/org/drools/org.drools.eclipse.feature/5.2.0.M1/org.drools.eclipse.feature-5.2.0.M1-p2artifacts.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at org.sonatype.tycho.p2.repository.LocalRepositoryReader.getContents(LocalRepositoryReader.java:28)
at org.sonatype.tycho.p2.repository.LocalRepositoryReader.getContents(LocalRepositoryReader.java:22)
at org.sonatype.tycho.p2.maven.repository.AbstractMavenArtifactRepository.loadMaven(AbstractMavenArtifactRepository.java:73)
at org.sonatype.tycho.p2.maven.repository.AbstractMavenArtifactRepository.<init>(AbstractMavenArtifactRepository.java:61)
at org.sonatype.tycho.p2.maven.repository.LocalArtifactRepository.<init>(LocalArtifactRepository.java:51)
at org.sonatype.tycho.p2.impl.resolver.P2ResolverImpl.setLocalRepositoryLocation(P2ResolverImpl.java:661)
at org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:196)
at org.sonatype.tycho.p2.facade.P2TargetPlatformResolver.resolvePlatform(P2TargetPlatformResolver.java:151)
at org.codehaus.tycho.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:86)
at org.codehaus.tycho.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:94)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months