Active Redeploy - do we do it in AS7.1.0
by Vimal Kansal
Hi,
Glassfish has a feature called "Active Redeploy" for preserving session
state across re-deployments and this it does for HTTP sessions, stateful
EJB's and persistently created EJB timers. I wonder if AS 7.1.0 does
this or something planned?
Thx
Vimal
14 years, 2 months
CLI public API
by Alexey Loubyansky
I've received requests lately to re-use some of the functionality
implemented in the CLI. So, I am cleaning up the API for external (to
the CLI code) users, which I'd like to complete for the upcoming release.
If anybody is interested, here is the first simple article
https://community.jboss.org/wiki/JBossAS7Command-linePublicAPI
There is one commit waiting to get merged though until it's all in master.
Suggestions and ideas are welcome.
Thanks,
Alexey
14 years, 2 months
modcluster config
by Heiko Braun
can some review the modcluster config? it seems to me that the load provider configuration is missing.
/ike
14 years, 2 months
Migration - Remote access / naming of EJB beans
by Wolf-Dieter Fink
Hi all,
I'm looking for possibilities how to migrate an application from AS4/5
to AS7.1/EAP6 and try to document the todo's
Is there a possibility to avoid jboss-ejb-client.properties?
I miss the @RemoteBinding @LocalBinding annotation to set the JNDI name,
is is gone and no other one?
regards
Wolf
14 years, 2 months
Application Client ENC
by Wolfgang Knauf
Hi,
I asked this already in the forums, but did not receive an answer up to
now. So I try it here:
Full question: https://community.jboss.org/thread/195232
Short summary: how does the Environment Naming Context for application
clients work?
Would be great if someone could point me to a doc or give me a quickstart.
Many thanks
Wolfgang Knauf
14 years, 2 months
NPE in jacorb
by Ales Justin
Hey,
got this NPE at shutdown.
Running custom AS7 branch with standalone-full-ha.xml.
No changes made to IIOP, etc.
---
15:57:37,387 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
15:57:37,393 INFO [jacorb.poa] POA IRPOA destroyed
15:57:37,394 INFO [jacorb.poa] POA Naming destroyed
15:57:37,394 WARN [org.jboss.msc.service.fail] MSC00004: Failure during stop of service jboss.jacorb.poa-service.rootpoa: java.lang.NullPointerException
at org.jacorb.poa.POA.destroy(POA.java:1019)
at org.jboss.as.jacorb.service.CorbaPOAService.stop(CorbaPOAService.java:187)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
15:57:37,419 INFO [jacorb.orb] prepare ORB for shutdown...
15:57:37,420 INFO [jacorb.orb] ORB going down...
15:57:37,424 INFO [jacorb.poa] POA RootPOA destroyed
15:57:37,426 INFO [jacorb.orb] ORB shutdown complete
15:57:37,427 INFO [jacorb.orb.iiop] Listener exited
15:57:37,428 INFO [jacorb.orb] ORB run, exit
-Ales
14 years, 2 months
Problems EJB invocations from a remote server instance
by Julio Cesar Silveira
Hi Guys,
I'm trying to implement the EJB remote connection between two servers
JBoss7, using the documentation described in this document:
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+...
I did everything as described in this document but got the following error
in the application deployment process:
...
14:50:54,507 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10)
MSC00001: Failed to start service
jboss.ejb3.dd-based-ejb-client-context."Sicop.war":
org.jboss.msc.service.StartException in service
jboss.ejb3.dd-based-ejb-client-context."Sicop.war": Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_26]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93)
at
org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.createRemotingConnections(DescriptorBasedEJBClientContextService.java:124)
at
org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.start(DescriptorBasedEJBClientContextService.java:86)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
14:50:54,520 ERROR [org.jboss.remoting.remote.connection] (Remoting "zeus"
read-1) JBREM000200: Remote connection failed:
javax.security.sasl.SaslException: Authentication failed: all available
authentication mechanisms failed
14:50:54,720 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2)
JBAS015870: Deploy of deployment "Sicop.war" was rolled back with failure
message {"JBAS014671: Failed services" =>
{"jboss.ejb3.dd-based-ejb-client-context.\"Sicop.war\"" =>
"org.jboss.msc.service.StartException in service
jboss.ejb3.dd-based-ejb-client-context.\"Sicop.war\": Failed to start
service"}}
14:50:54,739 INFO [org.jboss.as.server.deployment] (MSC service thread
1-2) JBAS015877: Stopped deployment Sicop.war in 19ms
14:50:54,741 INFO [org.jboss.as.controller] (DeploymentScanner-threads -
2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service
jboss.ejb3.dd-based-ejb-client-context."Sicop.war":
org.jboss.msc.service.StartException in service
jboss.ejb3.dd-based-ejb-client-context."Sicop.war": Failed to start service
14:50:54,743 ERROR [org.jboss.as.server.deployment.scanner]
(DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed
and was rolled back. Steps that failed:" => {"Operation step-2" =>
{"JBAS014671: Failed services" =>
{"jboss.ejb3.dd-based-ejb-client-context.\"Sicop.war\"" =>
"org.jboss.msc.service.StartException in service
jboss.ejb3.dd-based-ejb-client-context.\"Sicop.war\": Failed to start
service"}}}}
I ask this is a bug? Do you have any workaround to solve this problem? What
other way to do remote connection between servers JBoss EJB 7?
thank you
_______________________________________
Julio Cesar Silveira - julio(a)3layer.com.br
Arquiteto de Soluções
Skype: juliocsmac
Blog: http://juliocsmac.blogspot.com/
3layer - Porto Alegre - RS - Brasil
14 years, 2 months
Hard Coded URL's in Tests
by Stuart Douglas
I have noticed that at the moment we don't have a solution for how to deal with server changes that need to happen before the deployment (e.g. adding a security domain).
At the moment this is hacked up by having the @Deployment method connect with a hard coded URL, and performing any setup it needs to do.
I have come up with a solution to this: https://github.com/jbossas/jboss-as/commit/5bbdbb1f7428300982aeafc8e73864...
If you need to do any setup in your test class you simply annotate it @ServerSetup(MySetupClass.class) (where MySetupClass implements ServerSetupTask).
You can then do any server setup/cleanup necessary in your MySetupClass using the ManagementClient that is passed to the method.
At the moment the implementation is quite simple (only one action per test, superclasses are not examined etc) but if more functionality is required it should be fairly easy to implement.
Stuart
14 years, 2 months
Demos
by Stuart Douglas
What do people think about getting rid of the demo's in the AS7 source tree?
IMHO the quickstarts contain much better examples of how to get started with AS7.
Some of the examples are used in tests, I think we should move these classes to the test suite and just remove the rest.
Stuart
14 years, 2 months
