[JBoss JIRA] Commented: (JBAS-1924) Pressing button Graph Dataset in Snapshot breaks JBoss AS
by Niels Bischof (JIRA)
[ https://issues.jboss.org/browse/JBAS-1924?page=com.atlassian.jira.plugin.... ]
Niels Bischof commented on JBAS-1924:
-------------------------------------
It seems, the system property java.awt.headless=true has to be set to work around this problem.
The line:
JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true"
in /etc/sysconfig/jboss fixed the problem for me (on JBoss-6.0.0.Final).
BTW, the problem is not a new one: https://issues.jboss.org/browse/SOA-227
> Pressing button Graph Dataset in Snapshot breaks JBoss AS
> ---------------------------------------------------------
>
> Key: JBAS-1924
> URL: https://issues.jboss.org/browse/JBAS-1924
> Project: Legacy JBoss Application Server 6
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-4.0.2 Final
> Environment: #CPU: 1
> OS: Linux 2.4.21-215-default (i386)
> JVM Version: 1.4.2-b28 (Sun Microsystems Inc.)
> JVM Name: Java HotSpot(TM) Server VM
> Version: 4.0.2(build: CVSTag=JBoss_4_0_2 date=200505022023)
> Reporter: Werner Frerichs
>
> I created A Snapshot for FreeMemory with the web-console with Time Period 1000, start the snapshot in the web-console wih Start Snapshot and wait for a few minutes. Pressing the button Show Dataset show me the values.
> When Pressing the button Show Dataset in the web-console Jboss breaks immediatly and killed every running JBoss tasks. In the console where I started Jboss stand the following:
> X11 connection rejected because of wrong authentication.
> In the Logfile from Jboss for STDOUT stand the following:
> X connection to localhost:12.0 broken (explicit kill or server shutdown).
> In server/all/log/server.log I cannot find anything belong to this error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBNAME-55) jnp-client.jar doesn't have proper information in MANIFEST.MF
by Peter Skopek (JIRA)
jnp-client.jar doesn't have proper information in MANIFEST.MF
-------------------------------------------------------------
Key: JBNAME-55
URL: https://issues.jboss.org/browse/JBNAME-55
Project: JBoss Naming
Issue Type: Bug
Components: jnp-client
Reporter: Peter Skopek
While checking if build contains proper version of jboss security jars, I have found that some of the jars don't have proper information in MANIFEST.MF and jar-versions.xml.
jnp-client.jar
MANIFEST.MF contains for example this:
Manifest-Version: 1.0
Specification-Title: @specification.title@
Archiver-Version: Plexus Archiver
Built-By: mockbuild
Created-By: @java.vm.version@ (@java.vm.vendor@)
Specification-Version: @specification.version@
Implementation-Vendor-Id: @implementation.vendor.id@
Implementation-URL: @implementation.url@
Build-Jdk: 1.5.0_20
Ant-Version: Apache Ant 1.7.1
Implementation-Title: @implementation.title@
Specification-Vendor: @specification.vendor@
Implementation-Version: @implementation.version@
Implementation-Vendor: @implementation.vendor@
Can this be fixed, please?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (AS7-875) Rename connector subsystem
by Jesper Pedersen (JIRA)
Rename connector subsystem
--------------------------
Key: AS7-875
URL: https://issues.jboss.org/browse/AS7-875
Project: Application Server 7
Issue Type: Task
Components: JCA
Affects Versions: 7.0.0.Beta3
Reporter: Jesper Pedersen
Assignee: Stefano Maestri
Priority: Critical
Fix For: 7.0.0.CR1
Rename the "connector" subsystem to "ironjacamar" such that it is clear what the subsystem is.
The internal names can stay the same - that can be changed later.
Sources stay under connector/.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBAS-9032) @EJB injection with same "name" on two different fields leads to DuplicateServiceException
by jaikiran pai (JIRA)
@EJB injection with same "name" on two different fields leads to DuplicateServiceException
------------------------------------------------------------------------------------------
Key: JBAS-9032
URL: https://issues.jboss.org/browse/JBAS-9032
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 7.0.0.Beta1
Environment: JBoss AS7 master, JBoss AS 7.0 Beta1
Reporter: jaikiran pai
Consider this servlet (or any other component):
{code}
public class MyServlet extends HttpServlet {
@EJB (name="simpleName", beanName="SomeEJB")
private SomeEJB bean;
@EJB (name="simpleName", beanName="SomeEJB")
private SomeEJB beanAgain;
...
}
{code}
Notice that both the @EJB injection points expect the bean to be injected from bean in ENC at java:comp/env/simpleName. This however, leads to exception during deployment with the following message:
{code}
16:06:43,846 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."myejbapp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."myejbapp.war".INSTALL: Failed to process phase INSTALL of deployment "myejbapp.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.module.myejbapp.myejbapp.env/simpleName is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:143)
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months