April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9033) InvocationContext.getContextData() returns null when used in a interceptor

by jaikiran pai (JIRA)

InvocationContext.getContextData() returns null when used in a interceptor -------------------------------------------------------------------------- Key: JBAS-9033 URL: https://issues.jboss.org/browse/JBAS-9033 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 Assignee: jaikiran pai The javax.interceptor.InvocationContext#getContextData() http://download.oracle.com/javaee/6/api/javax/interceptor/InvocationConte... states: {quote} Returns the context data associated with this invocation or lifecycle callback. If there is no context data, an empty Map<String,Object> object will be returned. {quote} However when the InvocationContext.getContextData() is used in an interceptor, it returns null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-9354) Failing Deployment on startup receives a very meager error message

by Carlo de Wolf (JIRA)

Failing Deployment on startup receives a very meager error message ------------------------------------------------------------------ Key: JBAS-9354 URL: https://issues.jboss.org/browse/JBAS-9354 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Fix For: 7.0.0.Beta4 The following shows a server which has an invalid deployment in standalone.xml: {noformat} $ ./standalone.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/carlo/work/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT JAVA: /usr/lib/jvm/java-6-sun/bin/java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 ========================================================================= 14:41:10,570 INFO [org.jboss.modules] JBoss Modules version 1.0.0.Beta17 14:41:10,715 INFO [org.jboss.msc] JBoss MSC version 1.0.0.Beta8 14:41:10,747 INFO [org.jboss.as] JBoss AS 7.0.0.Beta3-SNAPSHOT "TBD" starting 14:41:11,091 INFO [org.jboss.as.server] Activating core services 14:41:11,175 INFO [org.jboss.as] creating native management service using network interface (default) port (9999) 14:41:11,181 INFO [org.jboss.as] creating http management service using network interface (default) port (9990) 14:41:11,196 INFO [org.jboss.as.arquillian] Activating Arquillian Subsystem 14:41:11,201 INFO [org.jboss.as.ee] Activating EE subsystem 14:41:11,234 INFO [org.jboss.as.naming] Activating Naming Subsystem 14:41:11,340 INFO [org.jboss.as.connector.subsystems.datasources] Deploying JDBC-compliant driver class org.h2.Driver (version 1.2) 14:41:11,348 INFO [org.jboss.as.osgi] Activating OSGi Subsystem 14:41:11,584 INFO [org.jboss.as.webservices] Activating WebServices Extension 14:41:11,663 ERROR [org.jboss.as.server] Boot update failed: "None of the following parameters were defined [input-stream-index, bytes, hash, url]." 14:41:11,676 INFO [org.jboss.as.naming] Starting Naming Service 14:41:11,679 INFO [org.jboss.as.logging] Removing bootstrap log handlers 14:41:11,689 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-16) Starting remote JMX connector 14:41:11,701 INFO [org.jboss.as.deployment] (MSC service thread 1-10) Started FileSystemDeploymentService for directory /home/carlo/work/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/standalone/deployments 14:41:11,708 INFO [org.jboss.wsf.common.management.AbstractServerConfig] (MSC service thread 1-11) JBoss Web Services - Stack CXF Server 4.0.0.Alpha4 14:41:11,722 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 3.1.0.Beta2 14:41:11,799 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) live server is starting.. 14:41:11,802 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-9) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-6-sun-1.6.0.24/jre/lib/amd64/server:/usr/lib/jvm/java-6-sun-1.6.0.24/jre/lib/amd64:/usr/lib/jvm/java-6-sun-1.6.0.24/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib 14:41:11,831 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-14) Starting Coyote HTTP/1.1 on http-dwarf-127.0.0.1-8080 14:41:11,850 INFO [org.jboss.as.connector] (MSC service thread 1-9) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.Beta5) 14:41:11,874 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) Bound JDBC Data-source [java:/H2DS] 14:41:11,918 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.1.Final-r2319 dwarf:5455 for CORE protocol 14:41:11,919 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-4) Started Netty Acceptor version 3.2.1.Final-r2319 dwarf:5445 for CORE protocol 14:41:11,920 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-4) HornetQ Server version 2.1.2.Final (Colmeia, 120) started 14:41:11,986 INFO [org.jboss.as] (MSC service thread 1-12) JBoss AS 7.0.0.Beta3-SNAPSHOT "TBD" started in 1545ms - Started 99 of 123 services (24 services are passive or on-demand) {noformat} In a normal (80x24) terminal everything before 11,813 has scrolled away. So it appears to be a normal startup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9094) Determine the standard configurations community AS 7 will ship

by Brian Stansberry (JIRA)

Determine the standard configurations community AS 7 will ship -------------------------------------------------------------- Key: JBAS-9094 URL: https://issues.jboss.org/browse/JBAS-9094 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: 7.0.0.Beta4 See also JBAS-9093, which provides support for choosing the config file(s) to use from the command line. This task is to determine what config files we will ship in community AS (if anything more than the standard domain.xml, host.xml, standalone.xml) and to develop processes to ensure they are valid. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7950) HornetQ keeps re-delivering the message infinitely on a failure to deliver to MDB

by jaikiran pai (JIRA)

HornetQ keeps re-delivering the message infinitely on a failure to deliver to MDB ---------------------------------------------------------------------------------- Key: JBAS-7950 URL: https://jira.jboss.org/jira/browse/JBAS-7950 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (HornetQ) Environment: AS trunk (hornetq 2.1.0 Beta2) Reporter: jaikiran pai Assignee: Clebert Suconic As discussed in the referenced forum thread, when HornetQ first fails to deliver a message to a MDB, it continues to redeliver the message infinitely. Also note that the JMS Message.getJMSRedelivered() is also broken - it keeps returning false even on a redelivered message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

8
36
0 / 0

[JBoss JIRA] Created: (JBAS-8817) Service POJO deployment throws NullPointerException

by Devinder Singh (JIRA)

Service POJO deployment throws NullPointerException --------------------------------------------------- Key: JBAS-8817 URL: https://issues.jboss.org/browse/JBAS-8817 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers, Weld/CDI Affects Versions: 6.0.0.CR1 Environment: RedHat Linux 5.5 Reporter: Devinder Singh Assignee: Ales Justin I have a very simple test service POJO that I'm trying to deploy to JBoss AS 6 on Linux. But it's failing with below exception: Java code for the test can be obtained from the forum link: http://community.jboss.org/message/581413 14:42:21,599 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:ear=foliage.ear,jar=foliageEJB.jar,name=CoolSystemInitService,service=EJB3 state=Configured: java.lang.NullPointerException at org.jboss.weld.integration.instantiator.Jsr299BeanInstantiator.locateWeldManager(Jsr299BeanInstantiator.java:102) [:6.0.0.20101110-CR1] at org.jboss.weld.integration.instantiator.Jsr299BeanInstantiator.getWeldManager(Jsr299BeanInstantiator.java:93) [:6.0.0.20101110-CR1] at org.jboss.weld.integration.instantiator.Jsr299BeanInstantiator.create(Jsr299BeanInstantiator.java:72) [:6.0.0.20101110-CR1] at org.jboss.ejb3.EJBContainer.construct(EJBContainer.java:997) [:1.6.3] at org.jboss.ejb3.service.ServiceContainer.create(ServiceContainer.java:205) [:1.6.3] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_21] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_21] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_21] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_21] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.Alpha9] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-9202) Server creation on slave fails to return result, but creation succeeds

by Heiko Rupp (JIRA)

Server creation on slave fails to return result, but creation succeeds ---------------------------------------------------------------------- Key: JBAS-9202 URL: https://issues.jboss.org/browse/JBAS-9202 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp Have 2 hosts, a DC one (snert) and a Slave, SL (pintsize). On the DC: [localhost:9999 /] /host=snert/server-config=newServer4:add(group=main-server-group,auto-start=1) { "outcome" => "success", "result" => undefined, "compensating-operation" => { "operation" => "remove", "address" => [ ("host" => "snert"), ("server-config" => "newServer4") ] } } On the slave: [localhost:9999 /] /host=pintsize/server-config=newServer5:add(group=main-server-group,auto-start=1) Communication error: java.util.concurrent.ExecutionException: java.io.EOFException But the server has been created: [localhost:9999 /] ls /host=pintsize/server-config=newServer5 path jvm interface -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-9021) IIOP subsystem

by David Lloyd (JIRA)

IIOP subsystem -------------- Key: JBAS-9021 URL: https://issues.jboss.org/browse/JBAS-9021 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 Implement an IIOP subsystem which creates an ORB service at "jboss.orb", with configurable network and threading properties. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-9309) Host Controller shutdown / restart operations

by Brian Stansberry (JIRA)

Host Controller shutdown / restart operations --------------------------------------------- Key: JBAS-9309 URL: https://issues.jboss.org/browse/JBAS-9309 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 Analogous to the shutdown operation on the standalone server, but shuts down the HC. We need to think through the reasonable variants. A full shutdown of the ProcessController and all child processes is one. Another is a restart of the HC, leaving all servers running. A third is a shutdown of all servers, followed by a restart of the HC which would bring up auto-start servers. A shutdown of the HC but not the PC is not allowed; the PC will always ensure there is an HC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-9288) ServerDeploymentManager: Cannot get the result of a deployment action

by Andre Dietisheim (JIRA)

ServerDeploymentManager: Cannot get the result of a deployment action --------------------------------------------------------------------- Key: JBAS-9288 URL: https://issues.jboss.org/browse/JBAS-9288 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Andre Dietisheim I actually try to get the result of a deployment and unfortunately fail so far. I proceed in the following manner: I add an deployment, get the action that was created for it, and then try to retrieve the result of this action: ... ServerDeploymentManager manager = ServerDeploymentManager.Factory.create(client); InitialDeploymentPlanBuilder builder = manager.newDeploymentPlan(); builder = builder.add(file.getName(), file).addDeploy(); DeploymentAction action = builder.getLastAction(); DeploymentPlan plan = builder.build(); Future<ServerDeploymentPlanResult> planResult = manager.execute(plan); ServerDeploymentPlanResult result = resultFuture.get(timeout,TimeUnit.MILLISECONDS); ServerDeploymentActionResult actionResult = result.getDeploymentActionResult(action.getId()); .... Unfortunately actionResult is always null. Stepping through the code did not help a lot so far: The result of the server deployment plan seems always to hold an empty map of actionResults (DeploymentPlanResultImpl#actionResults). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-9190) CLI hangs on bad input

by Heiko Rupp (JIRA)

CLI hangs on bad input ---------------------- Key: JBAS-9190 URL: https://issues.jboss.org/browse/JBAS-9190 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CLI Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp connect with the CLI to a domain and then issue [localhost:9999 /] ls /host=pintsize/server/ after the last / press either <TAB> or <RETURN> Cli just hangs there and needs to be hard-killed vial Ctrl-C -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011