[GLASSFISH-21126] Sync and cleanup GF download URL Created: 10/Jul/14  Updated: 19/Sep/14

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 4.0, 4.1
Fix Version/s: not determined

Type: Task Priority: Trivial
Reporter: David Delabassee Assignee: sbcaruso
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

NA



 Description   

The GF Install Guide mentions (#1) as the place to download GF but it is really (#2)

(#1) http://glassfish.java.net/public/downloadsindex.html
(#2) https://glassfish.java.net/download.html

I have put a redirect from (#1) to (#2) to temporally fix this. We should sync and agree on a single common URL for the next Doc rev.






[GLASSFISH-20869] Provide a way to change SSO cookie name Created: 23/Oct/13  Updated: 24/Apr/14

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: future release
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: haducloc13 Assignee: JeffTancill
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All environments



 Description   

No way to change the name of SSO cookie name now. It was fixed "JSESSIONSSO".






[GLASSFISH-19283] CLONE -Managing custom error pages for different http errors Created: 03/Nov/12  Updated: 03/Nov/12

Status: Open
Project: glassfish
Component/s: web_container
Affects Version/s: 3.1
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: Wasomumba Assignee: Shing Wai Chan
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Issuezilla Id: 13,297

 Description   

Hi,

recently I was trying to to find a way to changes the default glassfish error
pages, such as

  • 404
  • 500
  • ...

I prefered to do this somehow globally instead of only webapp based (web.xml).
The only way to do this is in the domain.xml file. An example could be:

<virtual-server hosts="$

{com.sun.aas.hostName}

"
http-listeners="http-listener-1,http-listener-2" id="server"
log-file="$

{com.sun.aas.instanceRoot}/logs/server.log" state="on">
<property name="docroot" value="${com.sun.aas.instanceRoot}

/docroot"/>
<property name="accesslog" value="$

{com.sun.aas.instanceRoot}

/logs/access"/>
<property name="sso-enabled" value="false"/>
<property name="send-error_1" value="path=../errors/404.html
reason=Resource_not_found code=404"/>
</virtual-server>

I am ok with this part, but unfortunately one has to maintain each of the http
errors 1 by 1. Imagine you want to catch all of the 400 and 500 error codes -
that would cause you a lot of work...

My idea would be to offer something like this:

<property name="send-error_1" value="path=../errors/4x.html
reason=Resource_not_found code=4*"/>

or

<property name="send-error_1" value="path=../errors/5x.html
reason=Resource_not_found code=5*"/>

or even

<property name="send-error_1" value="path=../errors/x.html
reason=Resource_not_found code=*"/>

And in the file you have specified you could either add some "static" contetn
like "An Error has occured". Of course you could even offer some kind of feature
that allows you to place plcaholders in that files to be filled with the error
code itself. The advantage would be that one only would need to specify one
error file and the content of that file would be dynamic.



 Comments   
Comment by Wasomumba [ 03/Nov/12 ]

I'm really looking for such a feature too.





[osgi-cdi] support @Inject @OSGiService Instance<T> (GLASSFISH-16805)

[GLASSFISH-18978] select OSGi services used in CDI beans based on OSGi filters Created: 06/Aug/12  Updated: 06/Aug/12

Status: Open
Project: glassfish
Component/s: OSGi-JavaEE
Affects Version/s: future release
Fix Version/s: not determined

Type: Sub-task Priority: Major
Reporter: TangYong Assignee: Sanjeeb Sahoo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Requirements:

CDI004 - The specification MUST make it possible to select OSGi services used in CDI beans based on OSGi
filters.

liking the following:

@Inject @ServiceFilter("(country=CN)") Service service;



 Comments   
Comment by TangYong [ 06/Aug/12 ]

Now, the feature has been supported. Please see.

https://github.com/tangyong/gf-cdi-osgi-integration

DEMO: https://github.com/tangyong/gf-cdi-osgi-integration/tree/master/samples/[RFP146]CDI004

Using Way:

@Inject @ServiceFilter("(country=CN)") Service<StockQuoteService> sqses;
....





[GLASSFISH-18407] Remote EJBs fail with ClassCastException in embeddable Glassfish Created: 24/Feb/12  Updated: 01/May/13

Status: Open
Project: glassfish
Component/s: embedded
Affects Version/s: 3.1_b39
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: vins4java Assignee: Bhavanishankar
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive glassfish-test-arquillian.zip    
Tags: 3_1-exclude, 3_1-fishcat, 3_1-release-note-added, 3_1-release-notes, 3_1_1-approved, 3_1_1-next

 Description   

I think I've found a specification violation in the embeddable Glassfish project. My apologies if it turns out that this is not the case, but I've taken the liberty of setting the priority to Major because I don't see any wiggling out of this one.

Here's what the specification has to say about business interfaces of stateless session beans in section 4.9.7:

"If the business interface is a remote business interface, the argument and return values must be of valid types for RMI/IIOP. The remote business interface is not required or expected to be a java.rmi.Remote interface."

My business interface is declared thusly:

public interface AppealTypeManager extends DAO<Long, AppealType>

{ public Collection <? extends AppealType> findAllAppealTypes(final PagingControl pagingControl); }

(Note the lack of @Remote, and the lack of "extends Remote".)

My bean class is declared thusly:

@Stateless//(name = "AppealTypeManager")
@TransactionAttribute(TransactionAttributeType.REQUIRED)
@Remote(AppealTypeManager.class)
public class AppealTypeManagerBean extends AbstractDAO<Long, AppealType, AppealTypeEntity> implements AppealTypeManager

{ // ...etc. }

I look up a reference to the remote business interface like this:

final Context c = new InitialContext();
final AppealTypeManager a = (AppealTypeManager)c.lookup("java:global/test-classes/AppealTypeManagerBean");

When I deploy my EJB module to embeddable Glassfish, I get the following error upon lookup:

javax.naming.NamingException: Lookup failed for 'java:global/test-classes/AppealTypeManagerBean' in SerialContext[myEnv=

{java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming}

[Root exception is javax.naming.NamingException: ejb ref resolution error for remote business interfacecom.jenzabar.ngp.ia.designation.api.AppealTypeManager [Root exception is java.lang.ClassCastException]]
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:525)
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.jenzabar.junit.ejb.dbunit.mem.GlassfishEmbeddedStrategy.getBean(GlassfishEmbeddedStrategy.java:126)
at com.jenzabar.junit.ejb.dbunit.mem.AbstractEJBTestCase.setUp(AbstractEJBTestCase.java:98)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:145)
at org.apache.maven.surefire.Surefire.run(Surefire.java:104)
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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017)
Caused by: javax.naming.NamingException: ejb ref resolution error for remote business interfacecom.jenzabar.ngp.ia.designation.api.AppealTypeManager [Root exception is java.lang.ClassCastException]
at com.sun.ejb.EJBUtils.lookupRemote30BusinessObject(EJBUtils.java:434)
at com.sun.ejb.containers.RemoteBusinessObjectFactory.getObjectInstance(RemoteBusinessObjectFactory.java:75)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
at com.sun.enterprise.naming.impl.SerialContext.getObjectInstance(SerialContext.java:559)
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:521)
... 34 more
Caused by: java.lang.ClassCastException
at com.sun.corba.ee.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:262)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
at com.sun.corba.ee.impl.presentation.rmi.DynamicMethodMarshallerImpl$12.read(DynamicMethodMarshallerImpl.java:353)
at com.sun.corba.ee.impl.presentation.rmi.DynamicMethodMarshallerImpl.readResult(DynamicMethodMarshallerImpl.java:483)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:203)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)
at com.sun.corba.ee.impl.presentation.rmi.codegen.CodegenStubBase.invoke(CodegenStubBase.java:227)
at com.sun.ejb.codegen._GenericEJBHome_Generated_DynamicStub.create(com/sun/ejb/codegen/_GenericEJBHome_Generated_DynamicStub.java)
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 com.sun.ejb.EJBUtils.lookupRemote30BusinessObject(EJBUtils.java:422)
... 38 more
Caused by: java.lang.ClassCastException: Object is not of remote type java.rmi.Remote
at com.sun.corba.ee.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:254)
... 50 more

Again, the specification does not require a remote business interface to extend java.rmi.Remote, but it would appear that the Glassfish embedded runtime thinks it's necessary.



 Comments   
Comment by vins4java [ 24/Feb/12 ]

this is a clone of http://java.net/jira/browse/GLASSFISH-15775
I've reopened it because I saw another user ("vasilievip") asked to reopen it but he had no answer.
We have the same problem with the latest build of glassfish-embedded-all (version 3.1.1) available for maven users.

Note:
In order reproduce the bug, I ran the original attachment issued by original issuer ("ljnelson") and set the following section into pom.xml.

<repositories>
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Maven Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public-jboss/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
<repository>
<id>jboss-deprecated-public-repository-group</id>
<name>JBoss Deprecated Public Maven Repository Group</name>
<url>https://repository.jboss.org/nexus/content/repositories/deprecated/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
</repository>
</repositories>

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by drivera [ 01/May/13 ]

I'm having a similar problem under 3.1.2.2 final, with the difference that the EJB's are being deployed in OSGi bundles.

The logs show the bundles deploying correctly, and the @OSGiService injection decoration from the OSGI-CDI bridge API helps find the EJB properly, but I too get this exception:

java.lang.ClassCastException: Object is not of remote type java.rmi.Remote
at com.sun.corba.ee.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:254)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:137)
at com.sun.corba.ee.impl.presentation.rmi.DynamicMethodMarshallerImpl$12.read(DynamicMethodMarshallerImpl.java:353)
at com.sun.corba.ee.impl.presentation.rmi.DynamicMethodMarshallerImpl.readResult(DynamicMethodMarshallerImpl.java:483)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:203)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)
at com.sun.corba.ee.impl.presentation.rmi.codegen.CodegenStubBase.invoke(CodegenStubBase.java:227)
at com.sun.ejb.codegen._GenericEJBHome_Generated_DynamicStub.create(com/sun/ejb/codegen/_GenericEJBHome_Generated_DynamicStub.java)
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 com.sun.ejb.EJBUtils.lookupRemote30BusinessObject(EJBUtils.java:421)
at com.sun.ejb.containers.RemoteBusinessObjectFactory.getObjectInstance(RemoteBusinessObjectFactory.java:75)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
at com.sun.enterprise.naming.impl.SerialContext.getObjectInstance(SerialContext.java:556)
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:514)
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.ejb.EjbNamingReferenceManagerImpl.resolveEjbReference(EjbNamingReferenceManagerImpl.java:186)
at com.sun.enterprise.container.common.impl.ComponentEnvManagerImpl$EjbReferenceProxy.create(ComponentEnvManagerImpl.java:1109)
at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:776)
at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:744)
at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:169)
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:498)
at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:599)
at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:470)
at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstance(InjectionManagerImpl.java:171)
at org.glassfish.weld.services.InjectionServicesImpl.aroundInject(InjectionServicesImpl.java:130)
at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:46)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:157)
at org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:131)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:153)
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:293)
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:68)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:637)
at org.jboss.weld.el.AbstractWeldELResolver.lookup(AbstractWeldELResolver.java:127)
at org.jboss.weld.el.AbstractWeldELResolver.getValue(AbstractWeldELResolver.java:96)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:188)
at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)
at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:103)
at com.sun.el.parser.AstValue.getValue(AstValue.java:179)
at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:224)
at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
at javax.faces.component.ComponentStateHelper.eval(ComponentStateHelper.java:194)
at org.primefaces.component.dashboard.Dashboard.getModel(Dashboard.java:101)
at org.primefaces.component.dashboard.DashboardRenderer.encodeMarkup(DashboardRenderer.java:56)
at org.primefaces.component.dashboard.DashboardRenderer.encodeEnd(DashboardRenderer.java:41)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1764)
at javax.faces.render.Renderer.encodeChildren(Renderer.java:168)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:845)
at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:304)
at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:105)
at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:845)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1757)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1760)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1760)
at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:402)
at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:131)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)





[GLASSFISH-18230] [UB]GlassFish "Typical" Install flow change. Domain Info screen has been added to allow a user to add a password Created: 19/Jan/12  Updated: 05/Apr/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_b18
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Alex Pineda Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

System is OEL5 with JDK 1.6.0_30. GF 3.1.2 build18. Installation done through GUI using "typical" option with default settings.


Attachments: PDF File DomainInfo.pdf    
Tags: glassfish, installer

 Description   

The "Typical" Glassfish Installation process has been changed. A screen has been added (Domain Info) which basically allows a user to modify the Domain name, Admin port, Http port, admin user, admin password, and ability to set up DomainServices. This screen appears to be a similar or same screen that is part of the Custom Install process.

The explanation for adding this screen is based on a Security requirement noted in https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=12652057 . So, there's no possibility to revert the Install flow to what it was in GF 3.1.2 build 16 or the previous versions of Glassfish (3.1.1, 3.1, etc...).

So this report is basically to track the change and the affected areas. From a Test standpoint, this change affects our manual test procedure to include test cases that cover the "Domain Info" screen. Perhaps there's an impact to the Install Guide to add the additional screen.

Attached is a screenshot of the Domain Info page that is now added to the "Typical" install.



 Comments   
Comment by Joe Di Pol [ 24/Jan/12 ]

Assigning to docs to make sure this change is documented in the install guide.

Comment by Paul Davies [ 15/Feb/12 ]

[UB]: Affects unbundled documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-18195] [UB]Document the copying of jdbc drivers to appropriate locations for different modes of JMS Created: 13/Jan/12  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_b17
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: saradak Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Please document that
For EMBEDDED mode, the jdbc driver needs to be copied to the directory glassfish3/glassfish/lib/install/applications/jmsra/

For LOCAL/REMOTE modes, the jdbc driver needs to be copied to the directory glassfish3/mq/lib/ext/

-Sarada.



 Comments   
Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-18193] [UB]Misleading prerequisite in To Enable the Load Balancer Auto Apply Feature Created: 13/Jan/12  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: None
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Paul Davies Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

One prerequisite in the procedure To Enable the Load Balancer Auto Apply Feature is that SSH must be configured to enable centralized administration on the host where the DAS is running.

However, this prerequisite must be met only to enable the subcommands create-instance, start-instance or start-cluster to run. This procedure does not use any of these subcommands, so it is not clear why this prerequisite is stated. The documentation should be clarified in one of the following ways:

  • If the prerequisite is valid, the procedure should clarify why SSH is needed only on the DAS host and whether DCOM is an acceptable substitute on Windows systems.
  • Otherwise, the prerequisite should be corrected or removed.


 Comments   
Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-18175] The key-store, trust-store element in ssl protocol element are not working Created: 12/Jan/12  Updated: 25/Apr/14

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: None
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Shing Wai Chan Assignee: JeffTancill
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-18179 When SSL keystore or truststore is sp... Sub-task Closed Amy Roh  
Tags: 3_1_2-exclude

 Description   

Specifying the keystore and truststore in ssl protocol element in domain.xml are not working.
One still pick up the keystore and truststore from jvm options.

A sample xml snapshot is as follows:
<protocol security-enabled="true" name="ssl-listener">
<http default-virtual-server="server">
<file-cache></file-cache>
</http>
<ssl key-store="/opscenter/security/keystore/keystore" ssl3-tls-ciphers="+SSL_RSA_WITH_RC4_128_MD5,+SSL_RSA_WITH_RC4_128_SHA" classname="com.sun.enterprise.security.ssl.GlassfishSSLImpl" trust-store="/opscenter/security/keystore/truststore_gf" cert-nickname="s1as"></ssl>
</protocol>

I notice the following in debugger:
GlassfishSSLImpl#getServerSocketFactory() --> new GlassfishServerSocketFactory()
and we have GlassfishServerSocketFactory#getKeyManagers as follows:

        if (sslUtils == null) {
            initSSLUtils();
        }
        String keystoreFile = (String) attributes.get("keystore");
        if (logger.isLoggable(Level.FINE)) {
            logger.log(Level.FINE, "Keystore file= {0}", keystoreFile);
        }

        String keystoreType = (String) attributes.get("keystoreType");
        if (logger.isLoggable(Level.FINE)) {
            logger.log(Level.FINE, "Keystore type= {0}", keystoreType);
        }
        KeyManager[] kMgrs = sslUtils.getKeyManagers(algorithm);
        if (keyAlias != null && keyAlias.length() > 0 && kMgrs != null) {
            for (int i = 0; i < kMgrs.length; i++) {
                kMgrs[i] = new J2EEKeyManager((X509KeyManager) kMgrs[i], keyAlias);
            }
        }
        return kMgrs;
    }

(a) I notice that the keystoreFile are correctly pick up from protocol ssl element.
(b) the keystoreFile above is computed but "not" used in the computation of key managers
(c) The key managers are dervied from SSLUtils which is looked up from habitat.
However, we have
SSLUtils is scoped by Singleton.class
(ii) inside SSLUtils, the key managers are computed from SecuritySupportImpl.java
(iii) SecuritySupportImpl is also Singleton scoped
also, #initJKS method only get keystores info from jvm options



 Comments   
Comment by Shing Wai Chan [ 12/Jan/12 ]

Per discussion with Kumar, this bug is similar to http://java.net/jira/browse/GLASSFISH-15973.

I have manually classname attribute in ssl protocol element.
Then it works.

Now we have the following questions.
1) Now, by default, we use GlassfishSSLImpl. It seems that we should use "" here.
"" means that we will use the default from Grizzly.
Should we always use "" as a default?

2) If we edit the ssl keystore and truststore from admin console, then the classname will be set to GlassfishSSLImpl. And one cannot set the classname to "" from admin console.

Comment by kumarjayanti [ 12/Jan/12 ]

Shing Wai wrote :
------------
Now we have the following questions.
1) Now, by default, we use GlassfishSSLImpl. It seems that we should use "" here.
"" means that we will use the default from Grizzly.
Should we always use "" as a default?

2) If we edit the ssl keystore and truststore from admin console, then the classname will be set to GlassfishSSLImpl. And one cannot set the classname to "" from admin console.
----------------

Comment on #1 : So we cannot switch to "" as the default because we need to be secure by default.

Comment on #2 : Agreed this is an issue and we need to fix this in the CLI command. when explicit keystore and truststore are specified then the command should remove the classname.

Comment by Shing Wai Chan [ 12/Jan/12 ]

Can you clarify why "" is "not" secure?
If it is really not secure, then I think we should fix our default implementation to support the switching keystores as one don't want to compromise the security by using a two different keystores.

Comment by kumarjayanti [ 13/Jan/12 ]

"" is not secure because in this case the default Grizzly SSLImplementation is used and it expects the keystore and truststore passwords to be supplied

Either as additional attributes in the ssl element,
OR
as System properties javax.net.ssl.keyStorePassword and javax.net.ssl.trustStorePassword.

The default impl as you know reads Keystore and TrustStore from the System properties javax.net.ssl.keyStore and javax.net.ssl.trustStore so there is no issue there.

However you seem to have found an issue that GlassFish cannot be started if trustStore points to a different location other than domain config. This problem is independent of the Default SSL Implementation and i see that you have filed a different bug for that.





[GLASSFISH-18139] [UB]Repository docs issue with upgrading from GlassFish Open Source Edition to Oracle GlassFish Server Created: 06/Jan/12  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_b01, 3.1.2_b02, 3.1.2_b03, 3.1.2_b04, 3.1.2_b05, 3.1.2_b06, 3.1.2_b07, 3.1.2_b09, 3.1.2_b10, 3.1.2_b11, 3.1.2_b12, 3.1.2_b13, 3.1.2_b14, 3.1.2_b15, 3.1.2_b16
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: jclingan Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Irrelevant.



 Description   

The default repositories are:
PUBLISHER TYPE STATUS URI
stable.glassfish.org (preferred) origin online http://pkg.glassfish.org/v3/stable/
contrib.glassfish.oracle.com origin online http://pkg.oracle.com/glassfish/v3/contrib/
contrib.glassfish.org origin online http://pkg.glassfish.org/v3/contrib/

Problem 1:
The documentation states to remove the following repositories:
dev.glassfish.org
stable.glassfish.org
release.javaeesdk.oracle.com

The only repository in common beteen the OSS and commercial versions is stable.glassfish.org. I think we want to state in the docs to remove stable.glassfish.org, and if the others exist [ the contrib and sdk repositories ], delete them as well.

Problem 2, the order of the documented steps is incorrect. You can't delete the preferred repository. First you must added the new repositories (including setting the new default repository as release.glassfish.oracle.com). After that is done, then you can remove the glassfish.org repositories.



 Comments   
Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-18101] Error message reported during upgrade of 2.1.1 Cluster to GF3.1.2 Created: 30/Dec/11  Updated: 27/Mar/13

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: 3.1.2_b16
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Alex Pineda Assignee: JeffTancill
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris 10 Sparc system. GF v2.1.1patch 12. GF3.1.2 build16. Firefox 3.6.2 browser. JDK1.6.0_26


Attachments: Text File server.log     Text File upgrade.log    

 Description   

The test scenario is a "side-by-side" upgrade scenario from GFv2.1.1patch12 to GF3.1.2 build16. The overall steps are:

  • Install GFv2.1.1patch12 (sges-2_1_1-p12-bin-b02-solaris-sparc-09_jun_2011.bin) in $HOME/SUNWappserver
  • Enter admin123 as the admin password. Start the server.
  • Create node agent, cluster and two instances.
  • Deploy hello.war on the cluster. Verify that it works.
  • Deploy clusterjsp.ear on the instance (DAS). Verify that it works
  • Deploy UpgradeTester-ear.ear (upgrade app created by bbissett). Verify that it works
  • Shutdown the server.
  • Install GF3.1.2 (ogs-3.1.2-b16-unix.sh) in $HOME/glassfish3. Use default values (port, no admin password)
  • Verify server is functional (check localhost:8080, localhost:4848)
  • Shutdown the server
  • Invoke asupgrade tool (cd $1AS_HOME/domains; asupgrade -c -s $HOME/SUNWappserver/domains/domain1 -t .)
    It's during the above step that the errors are displayed,

asadmin: INFO: Disabling application UpgradeTester-ear
Possible error encountered during upgrade. See server log after upgrade process
completes.
asadmin: java.lang.NullPointerException^M
asadmin: at com.sun.web.security.RealmAdapter.postConstruct(RealmAdapter.java:1746)
asadmin: at com.sun.hk2.component.AbstractCreatorImpl.inject(AbstractCreatorImpl.java:131)
asadmin: at com.sun.hk2.component.ConstructorCreator.initialize(ConstructorCreator.java:91)
asadmin: at com.sun.hk2.component.AbstractCreatorImpl.get(AbstractCreatorImpl.java:82)
asadmin: at com.sun.hk2.component.EventPublishingInhabitant.get(EventPublishingInhabitant.java:139)
asadmin: at com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:78)
asadmin: at org.jvnet.hk2.component.Habitat.getByContract(Habitat.java:1050)
asadmin: at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1941)
asadmin: at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1661)
asadmin: at com.sun.enterprise.web.WebApplication.start(WebApplication.java:109)
asadmin: at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
asadmin: at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
asadmin: at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301)
asadmin: at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
asadmin: at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:375)
asadmin: at com.sun.enterprise.v3.admin.adapter.InstallerThread.load(InstallerThread.java:210)
asadmin: at com.sun.enterprise.v3.admin.adapter.InstallerThread.run(InstallerThread.java:108)
asadmin: |#]
asadmin: java.lang.Exception: java.lang.NullPointerException^M
asadmin: at com.sun.enterprise.web.WebApplication.start(WebApplication.java:138)
asadmin: at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
asadmin: at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
asadmin: at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301)
asadmin: at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
asadmin: at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:375)
asadmin: at com.sun.enterprise.v3.admin.adapter.InstallerThread.load(InstallerThread.java:210)
asadmin: at com.sun.enterprise.v3.admin.adapter.InstallerThread.run(InstallerThread.java:108)
asadmin: |#]
asadmin: Completed shutdown of Log manager service
asadmin: java.io.InterruptedIOException
asadmin: at java.io.FileOutputStream.writeBytes(Native Method)
asadmin: at java.io.FileOutputStream.write(FileOutputStream.java:282)
asadmin: at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
asadmin: at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
asadmin: at com.sun.enterprise.server.logging.GFFileHandler$MeteredStream.flush(GFFileHandler.java:514)
asadmin: at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:278)
asadmin: at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
asadmin: at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
asadmin: at java.util.logging.StreamHandler.flush(StreamHandler.java:225)
asadmin: at com.sun.enterprise.server.logging.GFFileHandler.log(GFFileHandler.java:679)
asadmin: at com.sun.enterprise.server.logging.GFFileHandler$1.run(GFFileHandler.java:179)
asadmin: Completed shutdown of GlassFish runtime
asadmin: Command start-domain executed successfully.
asadmin: The DAS was stopped.
End asadmin local command output.
Upgrade completed.

In the server.log, one can see the error as a SEVERE message. This error has not been seen in previous upgrade tests from v.2.1.1 to 3.1.1.

Subsequently and after recreating the node, cluster and instances, the deployed apps all appear to work normal. Need further investigation.



 Comments   
Comment by Bobby Bissett [ 30/Dec/11 ]

Am moving to security team for a look.

Comment by Joe Di Pol [ 20/Jan/12 ]

Based on this e-mail update from Nithya I'm lowering the priority and removing 3_1_2-review:

"The issue was happening because when the application was getting deployed in v3, the network-config element was probably unavailable in the v3 instance for the first time. However on subsequent restart, the network configuration would have been made available in v3 and the scenario would work fine.
If the restart is part of the test case, then this is not a serious issue to be fixed urgently in 3.1.2."





[GLASSFISH-18045] [UB]Provide instructions to configure 64-bit usage of Webserver when on Solaris 11 (sparcv9) Created: 19/Dec/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: not determined

Type: Task Priority: Major
Reporter: varunrupela Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 312_qa

 Description   

Once Solaris 11 is added as a supported platform in the HA Admin Guide, instructions will be needed to configure usage of the 64-bit Webserver.
http://docs.oracle.com/cd/E18930_01/html/821-2426/gldbq.html#scrolltoc

On Solaris 11, extra steps are required to configure usage of the Webserver as 64-bit software. This is required since the lb configurator will install a 64-bit LB and would need the webserver to be running as 64-bit.

The extra steps are noted here:
http://docs.oracle.com/cd/E19146-01/821-1832/gdaem/index.html

***
Set the configuration property:
$ wadm set-config-prop --user=admin-user --host=host-name --port=admin-port
--config=config-name platform=64

Deploy the configuration:
$ wadm deploy-config config-name
****



 Comments   
Comment by Paul Davies [ 19/Dec/11 ]

[UB] - Affects unbundled documentation.

In addition to the HA Administration Guide, this issue might also affect the examples in the Quick Start Guide (if only to the extent of updating the assumptions to include an operating system other than Solaris 11).

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-18010] Resources Added using "Add Resource" feature do not show up for clusters and instances. Created: 15/Dec/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: jca
Affects Version/s: 3.1.2_b14
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: shaline Assignee: Jagadish
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Solaris Sparc 10
FF 8.0.1
GF 3.1.2 SCF b14.


Attachments: XML File glassfish-resources.xml    
Tags: 3_1_2-exclude, 3_1_2-qa

 Description   

Enable Secure admin and access console remotely. Create a 2 instance cluster and start the cluster. Create a standalone instance and start the instance.
--Using the Add Resources feature select a glassfish-resources.xml file and first select the "server" as target. Resources will be added successfully. Check the Added Resources under server(Admin Server)/Resources Tab. We can see the JDBC resource added.
--Now go ahead and add the same glassfish-resources.xml and select the "cluster" target. Resources added successfully message is displayed. Check under Clusters/cluster1/Resources Tab. Notice that the resource is not listed.
--Repeat the steps for a standalone instance, message says Resources are added, but we do not find them under the Standalone-Instances/instance-name/Resources Tab.

Using CLI, these resources are listed for clusters and instances. if I do #asadmin list-jdbc-connection-pools cluster1, then I do see the pools for the cluster. But they do not show up in Console.

Attached the glassfish-resource.xml file to reproduce.



 Comments   
Comment by Anissa Lam [ 15/Dec/11 ]

I think Shaline is seeing the wrong thing. When you call add-resources using the same glassfish-resources.xml, but select another target, the command actually failed. There is no way that the resource is created for the other target using the add-resources command.

Here is what i see when using CLI to repeat the steps that Shaline reported above:

%> asadmin add-resources glassfish-resources.xml
Command : JDBC connection pool jdbc/test-pool created successfully.
Command : JDBC resource jdbc/test-ds created successfully.
Command add-resources executed successfully.

%>v3admin add-resources --target clusterABC glassfish-resources.xml
Command : A resource named jdbc/test-pool already exists.
Command : A JdbcResource named jdbc/test-ds already exists. If you are trying to create the existing resource configuration in target clusterABC, please use create-resource-ref command (or create resource-ref using admin console).
Command add-resources executed successfully.

However, when i try to do add-resources using GUI, it gives me an successfully message, but in fact, nothing happened. ie, no resource-ref is added for cluster-ABC. This is expected.

So, GUI should display the error message like CLI. It should not hide it and says successful. Maybe the backend didn't return a failure, or maybe GUI 'hide' the failure and didn't display that to user. This needs to be fixed.

Comment by Anissa Lam [ 15/Dec/11 ]

I know why Shaline is confused.
She said:
>> if I do #asadmin list-jdbc-connection-pools cluster1, then I do see the pools for the cluster. But they do not show up in Console.

She has mixed up connection-pools with jdbc Resources. Connection pool doesn't 'associate' with a target. Its for the entire domain. Resources has targets.

If she does
%asadmin list-jdbc-resources cluster1
she will see that the newly created resource, jdbc/test-ds will not show up.

%asadmin list-jdbc-connection-pools cluster1
will show all the connection pools for the domain, thus, she is seeing jdbc/test-pool.

Actually, list-jdbc-connection-pools should not take a target since it doesn't apply.
In fact, if you do
%asadmin list-jdbc-connection-pools lasjdlfajsdlfjlsakdjflksjdf

it will still show you the connection pools ok. The target is basically ignored. I think that command has a bug.

Comment by sumasri [ 19/Dec/11 ]

Here is what we see when using CLI to repeat the steps that Shaline reported above:

%> asadmin add-resources glassfish-resources.xml
Command : JDBC connection pool jdbc/test-pool created successfully.
Command : JDBC resource jdbc/test-ds created successfully.
Command add-resources executed successfully.

%>v3admin add-resources --target clusterABC glassfish-resources.xml
Command : A resource named jdbc/test-pool already exists.
Command : A JdbcResource named jdbc/test-ds already exists. If you are trying to create the existing resource configuration in target clusterABC, please use create-resource-ref command (or create resource-ref using admin console).
Command add-resources executed successfully.

In the second step, even though all resources are not added successfully, CLI is reporting it as success..
Hence, even GUI is just showing the success message.

It should be fixed it in the back end first. May be it should return a warning status and with the message.

Comment by sumasri [ 19/Dec/11 ]

Assigning it to jca team(Jagadish).

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17953] WSIT pipes may be cached Created: 21/Aug/07  Updated: 09/Dec/11

Status: Open
Project: glassfish
Component/s: jbi
Affects Version/s: None
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: slweng Assignee: Bhavanishankar
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: XML File inputdata.xml     Text File JBI_projects.zip     Text File TestClient.zip    
Issuezilla Id: 661
Tags: as91-na

 Description   

HTTP BC uses the asynchronous transport so HTTP SOAP processing is asynchronous
by default. When WSIT policies are present, we expect to see synchronous
behavior.
However, once a WSIT feature is used in any JBI project (with SOAP request
processed by HTTP BC), all subsequent SOAP processing will fall back to sync
mode, even for projects with no WSIT policies defined.

Attached are two simple JBI projects: TestSyncApp has WSIT policies defined,
TestAsyncApplication does not.
In these projects, we use HTTP BC to receive SOAP requests and route them to
the BPEL engine. The BPEL process is a simple pass through. It logs a record in
a JMS queue everytime a new message arrives. A long "wait" activity is placed
to create a block on the response. Incoming requests will be blocked, i.e. not
put through to the BPEL process when processing is synchronous (all incoming
request processing threads are tied up waiting for the responses)
A test client project (HttpBCAsyncTester) is also attached here. The test
client will keep track of the number of SOAP requests posted to HTTP BC, and
the number of records logged in the JMS queue(which corresponds to the number
of message received in BPEL). If the number of messages sent matches the number
of JMS records, then it is asynchronous. If the number of messages sent is
greater than the JMS records, then that means the request processing is
synchronous.
The SOAP message the test client uses to post requests is also attached here
(inputdata.xml)

Steps to reproduce the issue:

1. Install and start following JBI components:
HTTP BC, JMS BC, BPEL SE
2. Right click on HTTP BC node in NetBeans JBI manager, select "properties",
set the "number of outbound threads" to 3
3. Extract the attached project zip files
4. Make sure the inputdata.xml is saved in the file system.
5. Open the projects in NetBeans
6. Right click on TestAsyncApplication project, select "Deploy Project".
7. Right click on HttpBCAsyncTester project, select "Properties", select "Run",
select "AsyncTest" from the "Configuration" drop down list.
Make sure the last argument points to the file location of the input data.
(Note: the file location needs to be prefixed by "f://")
The other 2 arguments should not be changed.
8. Right click on HttpBCAsyncTester project, select "Run"
9. Observe the output on the HttpBCAsyncTester run window.
The number of messages sent should be 6. The number of messages read from
the JMS queue should also be 6.
10. Right click on TestAsyncApplication project, select "Undeploy Project"
11. Right click on TestSyncApp project, select "Deploy project"
12. Right click on HttpBCAsyncTester project, select "Properties",
select "Run", select "SyncTest" from the "Configuration" drop down list.
Make sure the last argument points to the file location of the input data.
(Note: the file location needs to be prefixed by "f://")
The other 2 arguments should not be changed.
13. Right click on HttpBCAsyncTester project, select "Run"
14. Observe the output on the HttpBCAsyncTester run window.
The number of sent message should be 6, but the number of messages read
from the JMS queue should be 3.
15. Undeploy TestSyncApp, and deploy TestAsyncApplication again.
16. Repeat step 7 & 8
The number of messages sent should be 6, but the number of message read
from the JMS queue should be 0.



 Comments   
Comment by slweng [ 21/Aug/07 ]

Created an attachment (id=420)
JBI projects

Comment by slweng [ 21/Aug/07 ]

Created an attachment (id=421)
Test client project

Comment by slweng [ 21/Aug/07 ]

Created an attachment (id=422)
input data

Comment by haroldcarr [ 21/Aug/07 ]

Assigned to Kohsuke. Added as91-na keyword. This is targeted for AS 9.1.1.

Comment by haroldcarr [ 23/Aug/07 ]

Reassign to Fabian.

Comment by ritzmann [ 24/Aug/07 ]

Trying to reproduce the issue...

Comment by ritzmann [ 24/Aug/07 ]

Before I am wasting more hours on step 1:

How exactly do I install HTTP BC etc.? The NB Ent Pack is only available for NB
5.5 not 5.5.1. I don't get NB 5.5 to recognize GlassFish v2 b58. I believe that
is because of a bug that was fixed in NB 5.5.1. NB 6.0 daily build is not an
option because the debugger is not working properly on my platform.

Comment by slweng [ 24/Aug/07 ]

HTTP JBI binding component (HTTP BC) comes with glassfish installation, so no
extra installation step is required.
However, to run the test cases attached, you will need NB 6.0 and BPEL SE.
You can download them from OpenESB at:
https://open-esb.dev.java.net/Downloads_OpenESB_Addons_NB6.html

The installer will install latest NetBeans 6.0, Glassfish and all the JBI
components.

Hope this helps

Comment by slweng [ 24/Aug/07 ]

You would need NB 6.0 for these projects. The debugger works pretty good for
me, although I don't know what platform specific issue you have...

Comment by ritzmann [ 27/Aug/07 ]

The OpenESB download got me a bit further. Unfortunately, I am now stuck in step
6 with a bug that occurs with NetBeans on Mac OS X and Linux and that I reported
this spring. It is currently being fixed, but we can't wait for that. Given that
the NetBeans 6.0 debugger is not working so well on Mac OS X right now, we'd
better reassign this task. Marek, can you look into it?

Comment by m_potociar [ 29/Aug/07 ]

Taking the issue

Comment by m_potociar [ 29/Aug/07 ]

Hello,
I went through the steps 1-9, however in the step 9 I received following output
during the first run, after which the "Run" process hangs:

Number of messages sent - 6
Number of messages read from Queue (AsyncTestQ) - 5

When I retried the steps, I indeed received th output:

Number of messages sent - 6
Number of messages read from Queue (AsyncTestQ) - 6

but the process still hangs and needs to be manually killed.

Then I proceeded with steps 10-13 and got the output:
Number of messages sent - 6
Number of messages read from Queue (SyncTestQ) - 3

...again, I had to manually kill the "Run" process afterwards.

After steps 14-16 I received:

Number of messages sent - 6
Number of messages read from Queue (AsyncTestQ) - 6

After another retry, I received

Number of messages sent - 6
Number of messages read from Queue (AsyncTestQ) - 0

Then I undeployed async app and deployed the sync app, and received

Number of messages sent - 6
Number of messages read from Queue (SyncTestQ) - 0

as well...

Then I have restarted GF and tried to run several (cca 5-6) times async test,
and I received always the same result:

Number of messages sent - 6
Number of messages read from Queue (AsyncTestQ) - 6

Then I have restarted GF and tried to run several (cca 5-6) times sync test, and
in the first run I received:

Number of messages sent - 6
Number of messages read from Queue (SyncTestQ) - 3

however, in the consecutive runs I always received:

Number of messages sent - 6
Number of messages read from Queue (SyncTestQ) - 0

Of course, I had to manually kill each "Run" process, as it hangs after
providing the output.

Conclusion:
It seems to me that sync call for some reason in the first run "consumes" the 3
JMS queue threads and never releases them back. Killing the "Run" process does
not help either. Due to this, the consecutive runs of any test (sync or async)
result in 0 messages read from the queue. Please verify that you properly
dispose JMS resources when you are finished with them. I am reassigning th issue
back to Sherry for reevaluation a verification of my observations.

Comment by m_potociar [ 29/Aug/07 ]

As it seems not related to WSIT, downgrading to P4 for now. Please, feel free to
raise the priority back if you feel it should be higher.





[GLASSFISH-17911] update-node-com error message refers to SSH Created: 06/Dec/11  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: distributed management
Affects Version/s: None
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Paul Davies Assignee: Byron Nevins
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1_2-exclude

 Description   

An unsuccessful attempt to update a DCOM node displays an error message that refers to SSH:

asadmin> update-node-dcom -w hudson --nodehost  host.example.com xkyd
remote failure: Warning: some parameters appear to be invalid.
SSH node not updated. To force an update of the node with these parameters rerun
the command using the --force option.
com.sun.enterprise.universal.process.WindowsException: org.jinterop.dcom.common.
JIException: Access is denied, please check whether the [domain-username-password]
are correct. Also, if not already done please check the GETTING STARTED and
FAQ sections in readme.htm. They provide information on how to correctly configure
the Windows machine for DCOM access, so as to avoid such exceptions.  [0x00000005]
Command update-node-dcom failed.


 Comments   
Comment by Joe Di Pol [ 30/Jan/12 ]

Not a 3.1.2 stopper.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-17806] [UB]Docs need to be corrected to reflect the supported OS and Webserver matrix for LB Created: 23/Nov/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: varunrupela Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to GLASSFISH-16490 [UB]Additional Instructions for setti... Open
is related to GLASSFISH-16491 [UB]Additional Instructions for setti... In Progress
Tags: 312_qa

 Description   

The "Supported Operating Systems and Webservers" for LB needs correction in the "Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide".

The supported matrix is available at:
http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/GlassFish+3.1.x+Loadbalancer+plugin

For example: The doc indicates support for 32 bit Webservers on Linux, while that is not the case for GF 3.1.1.



 Comments   
Comment by Mike Fitch [ 10/Jan/12 ]

Added [UB] to summary, as this issue applies to unbundled (i.e., not online or inline help) documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17798] get-health always say instance as not started Created: 22/Nov/11  Updated: 17/Oct/12

Status: In Progress
Project: glassfish
Component/s: group_management_service
Affects Version/s: 4.0
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Anissa Lam Assignee: Joe Fialli
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File clustersetup.sh     Text File server.log    
Tags: 3_1_2-exclude, 3_1_x-exclude

 Description   

This is on latest workspace,rev# 51051 on the 3.1.2 branch.
Tried several times, and always reproducible.
I created a cluster (clusterABC) with 4 instances, all using the localhost-domain1 node.
I can start the instances, but get-health always says they are not started.

Here is the copy&paste of my commands. I will attach server.log as well.

~/Awork/V3/3.1.2/3.1.2 1)  cd $AS3/bin
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 2)  asadmin list-clusters
clusterABC not running
Command list-clusters executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 3)  asadmin list-instances --long
NAME   HOST       PORT   PID  CLUSTER     STATE         
ABC-4  localhost  24848  --   clusterABC   not running  
ABC-3  localhost  24849  --   clusterABC   not running  
ABC-2  localhost  24850  --   clusterABC   not running  
ABC-1  localhost  24851  --   clusterABC   not running  
Command list-instances executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 4)  asadmin start-instance ABC-1
Waiting for ABC-1 to start ..........
Successfully started the instance: ABC-1
instance Location: /Users/anilam/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/nodes/localhost-domain1/ABC-1
Log File: /Users/anilam/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/nodes/localhost-domain1/ABC-1/logs/server.log
Admin Port: 24851
Command start-local-instance executed successfully.
The instance, ABC-1, was started on host localhost
Command start-instance executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 5)  asadmin start-instance ABC-2
Waiting for ABC-2 to start ..........
Successfully started the instance: ABC-2
instance Location: /Users/anilam/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/nodes/localhost-domain1/ABC-2
Log File: /Users/anilam/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/nodes/localhost-domain1/ABC-2/logs/server.log
Admin Port: 24850
Command start-local-instance executed successfully.
The instance, ABC-2, was started on host localhost
Command start-instance executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 6)  asadmin list-instances --long
NAME   HOST       PORT   PID    CLUSTER     STATE         
ABC-4  localhost  24848  --     clusterABC   not running  
ABC-3  localhost  24849  --     clusterABC   not running  
ABC-2  localhost  24850  12517  clusterABC   running      
ABC-1  localhost  24851  12507  clusterABC   running      
Command list-instances executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 7)  asadmin get-health clusterABC
ABC-1 not started
ABC-2 not started
ABC-3 not started
ABC-4 not started
Command get-health executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 8)  asadmin start-cluster clusterABC
Command start-cluster executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 9)  asadmin list-instances --long
NAME   HOST       PORT   PID    CLUSTER     STATE     
ABC-4  localhost  24848  12540  clusterABC   running  
ABC-3  localhost  24849  12541  clusterABC   running  
ABC-2  localhost  24850  12517  clusterABC   running  
ABC-1  localhost  24851  12507  clusterABC   running  
Command list-instances executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 10)  asadmin get-health clusterABC
ABC-1 not started
ABC-2 not started
ABC-3 not started
ABC-4 not started
Command get-health executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 11)  



 Comments   
Comment by Joe Fialli [ 22/Nov/11 ]

Unable to recreate reported issue with build 51075.
Attached a shell script called clustersetup.sh to standardize HOW the cluster and instances are created.
(must configure GF_HOME to point to a valid 3.1.2 installation)
My results of running the script are counter to reported issue.

$GF_HOME/bin/asadmin list-instances
instance01 running
instance02 running
instance03 running
Command list-instances executed successfully.
$GF_HOME/bin/asadmin get-health myCluster
instance01 started since Tue Nov 22 11:38:25 EST 2011
instance02 started since Tue Nov 22 11:38:25 EST 2011
instance03 started since Tue Nov 22 11:38:25 EST 2011
Command get-health executed successfully.

***********
Analysis:

there is no evidence that multicast is working from the submitted DAS server.log.
Is it possible that this was attempted while connected with VPN?
VPN will interfer with multicast working.

Please submit output of "ifconfig -a" and also follow HA admin guide instructions for validating
that multicast is working properly for your system.
http://download.oracle.com/docs/cd/E18930_01/html/821-2426/gjfnl.html#gklhd
The instructions assume two different machines but you can check if multicast is working between processes
on same machine by opening two terminal windows on same machine.
Note that multicast does not work when one is connected via VPN.
(it disables multicast as a protection mechanism).

Specifying bindinterfaceaddress of 127.0.0.1 allows one to work with clusters on one machine while
connected via VPN.

Comment by Joe Fialli [ 22/Nov/11 ]

The attached shell script creates a domain, a cluster and 3 instances for the cluster and starts
up the cluster. Validates that cluster started using "asadmin get-health" and "asadmin list-instances".
User must edit script variable GF_HOME to point to a valid GF v3.1.2 installation.

Comment by Anissa Lam [ 22/Nov/11 ]

Yes, I saw the issue when I was working from home and using VPN.
So, is this a known issue that get-health will NOT provide a correct state of the instance when it is on VPN ?

I think that since there is no way to fix the code if one is on VPN, then even though you cannot gives the exact state like 'FAILED', 'STOPPED' and the timestamp, it should at least report the correct status. It shouldn't just say 'not started', instead, it should at least report the instance is running or not. Can the code detect that multicast is not working and code it like list-instances to find out the status of the instance and return that ?

Console is displaying whatever get-health returns, and telling user that the instance is 'not running' when it actually is doesn't sound acceptable. Especially when the Status from list-instance is displayed on the same screen, that says 'RUNNING', and the next line says 'not running' giving conflicting information.

Comment by Joe Fialli [ 22/Nov/11 ]

get-health reports the status of GMS.
GMS in multicast mode (the default) only works when multicast is working.

Please see bobby's blog, you are misinterpreting results.
asadmin get-health only works correctly when GMS is working correctly.
(asadmin get-health is a GMS client and it can only work as well as GMS subsystem is working)

http://blogs.oracle.com/bobby/entry/validating_multicast_transport_where_d

Comment by Anissa Lam [ 22/Nov/11 ]

As a user, when i am seeing the following:

~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 8) asadmin start-cluster clusterABC
Command start-cluster executed successfully.

~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 9) asadmin list-instances --long
NAME HOST PORT PID CLUSTER STATE
ABC-4 localhost 24848 12540 clusterABC running
ABC-3 localhost 24849 12541 clusterABC running
ABC-2 localhost 24850 12517 clusterABC running
ABC-1 localhost 24851 12507 clusterABC running
Command list-instances executed successfully.

~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 10) asadmin get-health clusterABC
ABC-1 not started
ABC-2 not started
ABC-3 not started
ABC-4 not started
Command get-health executed successfully.
~/Awork/V3/3.1.2/3.1.2/dist-gf/glassfish/bin 11)

I can only say that 'get-health' is giving me the wrong information. The server instance is obviously running, why 'get-health' says it is not started ?
If there is any issue that prevents "get-health" to give the correct information, then it should return an error informing the user what the problem is. Giving the wrong info and says executed successfully is not acceptable.

Comment by Joe Fialli [ 22/Nov/11 ]

reduced priority from critical to minor.

My recommendation is to change "not started" to "unknown".
The asadmin get-health command tells the state of the cluster
from the GMS point of view. If multicast is not working properly
and cluster is not forming properly, that is what the command should relay.

Comment by Bobby Bissett [ 23/Nov/11 ]

"I can only say that 'get-health' is giving me the wrong information. The server instance is obviously running, why 'get-health' says it is not started ?
If there is any issue that prevents "get-health" to give the correct information, then it should return an error informing the user what the problem is. Giving the wrong info and says executed successfully is not acceptable."

That's the way it is. The whole POINT of get-health is to tell you the state of the cluster. If the instances are up, but can't communicate, then there's a serious problem and the only way the user will know it is by running get-health and seeing the wrong result. This is all documented.

In the admin console, you can say whatever you want. The enum name is "NOT_RUNNING" but you can say whatever you want.

Comment by Bobby Bissett [ 23/Nov/11 ]

When the admin console gets the output from the get health command, it's getting the enum name from this enumeration:

// NOT_RUNNING means there is no time information associated
public static enum STATE {
NOT_RUNNING (strings.getString("state.not_running")),
RUNNING (strings.getString("state.running")),
REJOINED (strings.getString("state.rejoined")),
FAILURE (strings.getString("state.failure")),
SHUTDOWN (strings.getString("state.shutdown"));

private final String stringVal;

STATE(String stringVal)

{ this.stringVal = stringVal; }

@Override
public String toString()

{ return stringVal; }

}

There is no point in changing the name of the state in the enum, it's separate from the i18n'ed value that is presented to the user. So when the admin console sees that state, it can output anything you want. Are you using the LocalStrings.properties file in the gms-bootstrap module to get the actual text to use? If so, we can change that to say "not joined" instead. Otherwise, this issue doesn't really affect gms since you can use whatever text you want.

Just wanted to check to see if you're using our props file or your own for the text the user sees.

Comment by Anissa Lam [ 23/Nov/11 ]

I get it now.
I feel that it will be very nice if user can perform validate-multicast on the console.
Will it be possible to make validate-multicast a remote command so that console can call that ? Or its too much to ask for 3.1.2 ?
thanks Joe and Bobby for helping me to understand this.

Comment by Bobby Bissett [ 23/Nov/11 ]

Nope, validate-multicast has to be a local command only because it needs to be run on each machine that will host an instance. In fact, it's better if the server is not up when the command is run. If you're bored, you can watch a screen cast with the details

http://www.youtube.com/watch?v=sJTDao9OpWA

There is an RFE for a tool that's more centralized, which I think fits what you're looking for. It won't happen for 3.1.2, but it's possible it could happen later: GLASSFISH-13056

Comment by Joe Fialli [ 23/Nov/11 ]

Too big a change for 3.1.2 release to change the output of asadmin get-health that
is documented in asadmin get-health --help documentation.

Recommend considering fixing this in a major release.

We could release note in 3.1.2 that "asadmin get-health" "not started" status applies
to both the instance not running or the instance is running but the current configuration
is not allowing GMS communications. (could be multicast is not enabled properly or
non-multicast GMS mode is misconfigured.)

Comment by Joe Fialli [ 23/Nov/11 ]

Exclude changing asadmin get-health output in a minor release.





[GLASSFISH-17726] [UB]document IE security settings to load Admin Console remotely Created: 15/Nov/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2_b10
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: lidiam Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows xp, IE 7


Attachments: JPEG File ie-cantload-security-tls.JPG    

 Description   

Admin Console cannot be loaded with IE 7 default settings. A generic page is displayed instead saying that "Internet Explorer cannot display the webpage". Steps to reproduce:

1. Install Glassfish b10 on some remote machine.
2. Start domain: asadmin start-domain.
3. Change admin password, if blank, by running asadmin change-admin-password command.
4. Enable secure administration: asadmin enable-secure-admin.
5. Restart the domain (asadmin stop-domain, asadmin start-domain).
6. On a windows machine bring up IE 7 and enter Admin Console url: http://<host>:4848
7. A page is displayed saying that "Internet Explorer cannot display the webpage" (screenshot attached).

The same page has more details and among them the following:

"If this is an secure (HTTPS) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section."

In my IE 7 TLS is not enabled by default. After enabling TLS Admin Console comes up. It is not intuitive to know that this is the issue for the user, cause the url that one is trying to access is http not https. The problem is because of the redirect, but the user may not know/realize that.

I'm not sure we can do anything about this. If not, we should at least document this issue.



 Comments   
Comment by Anissa Lam [ 15/Nov/11 ]

Thats a good point.
This may not be just for IE7, since IE8 (or other browser) will require the same settings. Regardless what is the default settings, we should document this.
With the security requirement changes in 3.1.2, maybe there is a section/chapter that dedicated for the changes. This should be added to such chapter, besides any other doc that the doc team believes this kind of info should go.

Comment by Paul Davies [ 15/Nov/11 ]

We should restrict the documentation for this issue to the behavior of GlassFish Server: namely explain when the url is re-directed from http://<host>:<port> to https://<host>:<port>.

We should avoid documenting in the GlassFish Server documentation standard browser behavior. Instead we should refer users to the browser help for that information.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17722] [UB]Certificate realm LoginModule docs refer to blog postings Created: 14/Nov/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: None
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Paul Davies Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The following documentation for the certificate realm LoginModule refers to blog postings:

If the content of these blog postings describes supported use cases for GlassFish Server, the content should be part of the GlassFish Server product documentation and cross-referred to there. Otherwise, these cross-references should be removed.



 Comments   
Comment by Mike Fitch [ 10/Jan/12 ]

Removed reference to blog from create-auth-realm, pointing reader instead to "Custom Authentication of Client Certificate in SSL Mutual Authentication".

Committed fix in rev 51972.

Adding [UB] to summary and setting fix version to 3.1.2, as all that remains now is to fix the unbundled documentation portion of this issue.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17458] in non-multicast mode, one failed to connect per cluster instance at startup Created: 22/Oct/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: group_management_service
Affects Version/s: 3.1.2_b05
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: zorro Assignee: Joe Fialli
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 2.6.18-164.0.0.0.1.el5



 Description   

Glassfish version 3.1.2 build 5

Lots of the following exception are being seen the the server logs.

Expected: All exceptions to be handled

http://aras2.us.oracle.com:8080/logs/gf31/gms//set_10_20_11_t_11_56_02/scenario_0012_Thu_Oct_20_12_00_37_PDT_2011.html

11-10-20T18:56:57.888+0000|INFO|glassfish3.1.2|ShoalLogger.nomcast|_ThreadID=84;_ThreadName=Thread-2;|failed to send message to a virtual multicast endpoint[10.133.184.137:9090:230.30.1.1:9090:clusterz1:Unknown_10.133.184.137_9090] message=[MessageImpl[v1:MASTER_NODE_MESSAGE: NAD, Target: 10.133.184.137:9090:230.30.1.1:9090:clusterz1:Unknown_10.133.184.137_9090 , Source: 10.133.184.207:9090:230.30.1.1:9090:clusterz1:server, MQ, ]
java.io.IOException: failed to connect to 10.133.184.137:9090:230.30.1.1:9090:clusterz1:Unknown_10.133.184.137_9090
at com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyTCPConnectorWrapper.send(GrizzlyTCPConnectorWrapper.java:132)
at com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyTCPConnectorWrapper.doSend(GrizzlyTCPConnectorWrapper.java:96)
at com.sun.enterprise.mgmt.transport.AbstractMessageSender.send(AbstractMessageSender.java:74)
at com.sun.enterprise.mgmt.transport.VirtualMulticastSender.doBroadcast(VirtualMulticastSender.java:134)
at com.sun.enterprise.mgmt.transport.AbstractMulticastMessageSender.broadcast(AbstractMulticastMessageSender.java:70)
at com.sun.enterprise.mgmt.transport.grizzly.GrizzlyNetworkManager.broadcast(GrizzlyNetworkManager.java:295)
at com.sun.enterprise.mgmt.MasterNode.send(MasterNode.java:1338)
at com.sun.enterprise.mgmt.MasterNode.discoverMaster(MasterNode.java:382)
at com.sun.enterprise.mgmt.MasterNode.startMasterNodeDiscovery(MasterNode.java:1235)
at com.sun.enterprise.mgmt.MasterNode.run(MasterNode.java:1204)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:701)
at com.sun.grizzly.TCPConnectorHandler.finishConnect(TCPConnectorHandler.java:297)
at com.sun.grizzly.connectioncache.client.CacheableConnectorHandler.finishConnect(CacheableConnectorHandler.java:230)
at com.sun.enterprise.mgmt.transport.grizzly.grizzly1_9.GrizzlyTCPConnectorWrapper$CloseControlCallbackHandler.onConnect(GrizzlyTCPConnectorWrapper.java:185)
at com.sun.grizzly.CallbackHandlerContextTask.doCall(CallbackHandlerContextTask.java:70)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
... 1 more

#]


 Comments   
Comment by Joe Fialli [ 24/Oct/11 ]

This is only occuring in Glassfish Shoal QE test when running with GMS_DISCOVERY_URI_LIST set to
a list on instances that have not been created (or started yet) and the DAS initially joins the cluster.

There is only one exception per cluster member listed in GMS_DISCOVERY_URI_LIST.
For the test case this is reported against, there are 9 instances, so there are nine connection
failed when DAS joins cluster initially and those instances have yet to been created and started.
When DAS first joins cluster and no instance has even been created yet,
the DISCOVERY_URI_LIST contains connection info to yet to be created instances.

We will demote the failed connections during discovery from WARNING to FINE, this
will enable us to debug network configuration issues (such as firewalls) without
the nusance of always seeing one failure per cluster member referenced in GMS_DISCOVERY_URI_LIST.

Note: this issue does not apply to GMS_DISCOVERY_URI_LIST set to "generate" or to group discovery
via UDP multicast.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17252] [UB]Improve GlassFish Administration Guide with mod_proxy_ajp info Created: 29/Aug/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1.2
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Amy Roh Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

From user post http://forums.java.net/node/838467

"The GlassFish 3.1 Administration Guide provides information on fronting
GlassFish with Apache via mod_jk, but does not provide any information about
mod_proxy_ajp.

It appears that you can get Apache connected to GlassFish via mod_proxy_ajp
so it would be nice if the documentation at leasts mentions it (and discusses
any gotchas which I might be overlooking)."

We should improve GlassFish Administration Guide with mod_proxy_ajp info.



 Comments   
Comment by Mike Fitch [ 08/Nov/11 ]

Changing component to docs and assignee to myself.

Comment by Paul Davies [ 21/Jan/12 ]

[UB]: Affects unbundled documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17178] [UB]Glassfish 3.1.1 with JK Listener enabled throws exception of NoSuchThreadPool when EJB is deployed Created: 10/Aug/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs, web_container
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: vin4bacchus Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS X Lion, Windows 7 32bit



 Description   

Glassfish 3.1.1 build12 with a JK Listener enabled and set to thread-pool-1 throws NoSuchThreadPool exception when EJB is deploy individually or as part of an EAR.

Tested on multiple environments standalone and via Eclipse plugin. Same results each time. Reproducible every time.
Deploying applications with no EJBs has no issue.
Removing JK Listener resolves the problem.

Steps to reproduce.
1) New Glassfish 3.1.1 (build 12) install from zip.
2) Configure JK Listener on port 8009 on address 0.0.0.0 with thread-pool-1 as thread pool on server "server".
3) Create test EJB Project in Eclipse with one Hello World type method with both local and remote interfaces.
4) Export test EJB Project to JAR.
5) Deploy from web interface Applications menu.

Exception details below:
WARNING: No default ThreadPool defined
com.sun.corba.ee.spi.orbutil.threadpool.NoSuchThreadPoolException
at org.glassfish.enterprise.iiop.util.S1ASThreadPoolManager.getThreadPool(S1ASThreadPoolManager.java:246)
at org.glassfish.enterprise.iiop.util.S1ASThreadPoolManager.getDefaultThreadPool(S1ASThreadPoolManager.java:276)
at org.glassfish.enterprise.iiop.impl.PEORBConfigurator.configure(PEORBConfigurator.java:138)
at com.sun.corba.ee.impl.orb.ORBConfiguratorImpl.runUserConfigurators(ORBConfiguratorImpl.java:185)
at com.sun.corba.ee.impl.orb.ORBConfiguratorImpl.configure(ORBConfiguratorImpl.java:170)
at com.sun.corba.ee.impl.orb.ORBImpl.postInit(ORBImpl.java:625)
at com.sun.corba.ee.impl.orb.ORBImpl.set_parameters(ORBImpl.java:704)
at com.sun.corba.ee.impl.orb.ORBImpl.setParameters(ORBImpl.java:691)
at com.sun.corba.ee.spi.osgi.ORBFactory.initialize(ORBFactory.java:107)
at org.glassfish.enterprise.iiop.impl.GlassFishORBManager.initORB(GlassFishORBManager.java:581)
at org.glassfish.enterprise.iiop.impl.GlassFishORBManager.getORB(GlassFishORBManager.java:263)
at org.glassfish.enterprise.iiop.impl.GlassFishORBFactoryImpl.createORB(GlassFishORBFactoryImpl.java:93)
at org.glassfish.enterprise.iiop.api.GlassFishORBHelper.getORB(GlassFishORBHelper.java:152)
at org.glassfish.enterprise.iiop.api.GlassFishORBHelper.getProtocolManager(GlassFishORBHelper.java:219)
at com.sun.ejb.containers.BaseContainer.initializeProtocolManager(BaseContainer.java:818)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:566)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:155)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:149)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:105)
at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:230)
at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:290)
at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:101)
at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:186)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:257)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:382)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1064)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1244)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1232)
at org.glassfish.admin.rest.ResourceUtil.runCommand(ResourceUtil.java:202)
at org.glassfish.admin.rest.ResourceUtil.runCommand(ResourceUtil.java:195)
at org.glassfish.admin.rest.resources.TemplateListOfResource.createResource(TemplateListOfResource.java:148)
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 com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
at com.sun.jersey.server.impl.container.grizzly.GrizzlyContainer._service(GrizzlyContainer.java:182)
at com.sun.jersey.server.impl.container.grizzly.GrizzlyContainer.service(GrizzlyContainer.java:147)
at org.glassfish.admin.rest.adapter.RestAdapter.service(RestAdapter.java:184)
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:238)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:828)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:725)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1019)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:680)



 Comments   
Comment by Hong Zhang [ 10/Aug/11 ]

Not sure if it's an ejb issue or orb issue, assign to ejb team for initial evaluation.

Comment by Cheng Fang [ 10/Aug/11 ]

Can you try not specifying threadpool option when creating the listener? Or use "http-thread-pool".

thread-pool-1 is for servicing IIOP requests and for resource adapters to service work management requests.

Comment by vin4bacchus [ 10/Aug/11 ]

"thread-pool-1" was chosen because default "http-thread-pool" only has a max of 5 threads and choosing this pool threw a warning in the logs about not large enough max thread pool for AJP listener.

Upped "http-thread-pool" max threads to 50 and assigned the AJP JK Listener to it and tested on sample EJB project ok.
This appears to have solved the issue by using a different thread pool than "thread-pool-1".

Comment by Cheng Fang [ 10/Aug/11 ]

transfer to doc team to clarify. The following is what I observed. You may want to check with web container team:

do not use the build-in thread-pool-1 for any network-listener;

if users do not specify a threadpool for the jk listener, the default threadpool used is http-thread-pool. And users also need to up the max size for http-thread-pool from 5 to a bigger number.

users can also create a new thread pool with create-threadpool command with decent max size, for jk listener.

Comment by vin4bacchus [ 10/Aug/11 ]

Only one clarification. The default thread pool for a new JK Listener is actually the "admin" thread pool.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17134] after update to 3.1.11 (?) jsf web app causes server shutdown Created: 29/Jul/11  Updated: 09/May/13

Status: In Progress
Project: glassfish
Component/s: security
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: silveredge8181 Assignee: JeffTancill
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows xp


Attachments: Text File Copy of server.txt    

 Description   

Launching GlassFish on Felix platform
Jul 29, 2011 11:48:52 AM com.sun.enterprise.server.logging.LogManagerService postConstruct
WARNING: Record begin marker is not a proper value so using default.
Jul 29, 2011 11:48:52 AM com.sun.enterprise.server.logging.LogManagerService postConstruct
WARNING: Record end marker is not a proper value so using default.
Jul 29, 2011 11:48:52 AM com.sun.enterprise.server.logging.LogManagerService postConstruct
WARNING: Log Format field separator is not a character so using default.
Jul 29, 2011 11:48:52 AM com.sun.enterprise.server.logging.LogManagerService postConstruct
WARNING: Date Format specified is wrong so using default.
INFO: Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry
INFO: The Admin Console is already installed, but not yet loaded.
INFO: Grizzly Framework 1.9.36 started in: 550ms - bound to [0.0.0.0:8181]
INFO: Grizzly Framework 1.9.36 started in: 701ms - bound to [0.0.0.0:8080]
INFO: Grizzly Framework 1.9.36 started in: 540ms - bound to [0.0.0.0:4848]
INFO: Grizzly Framework 1.9.36 started in: 470ms - bound to [0.0.0.0:7676]
INFO: Grizzly Framework 1.9.36 started in: 500ms - bound to [0.0.0.0:3700]
INFO: SEC1002: Security Manager is OFF.
INFO: SEC1010: Entering Security Startup Service
INFO: SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
INFO: SEC1115: Realm [admin-realm] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.
INFO: SEC1115: Realm [file] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.
INFO: SEC1115: Realm [certificate] of classtype [com.sun.enterprise.security.auth.realm.certificate.CertificateRealm] successfully created.
INFO: SEC1011: Security Service(s) Started Successfully
INFO: WEB0169: Created HTTP listener [http-listener-1] on host/port [0.0.0.0:8080]
INFO: WEB0169: Created HTTP listener [http-listener-2] on host/port [0.0.0.0:8181]
INFO: WEB0169: Created HTTP listener [admin-listener] on host/port [0.0.0.0:4848]
INFO: WEB0171: Created virtual server [server]
INFO: WEB0171: Created virtual server [__asadmin]
INFO: WEB0172: Virtual server [server] loaded default web module []
INFO: Hibernate Validator 4.1.0.Final
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
FINEST: Begin predeploying Persistence Unit WebWormSalesPU; session file:/K:/Java code/WebWormSales/build/web/WEB-INF/classes/_WebWormSalesPU; state Initial; factoryCount 0
FINEST: property=eclipselink.orm.throw.exceptions; default value=true
FINEST: property=eclipselink.weaving.changetracking; default value=true
FINEST: property=eclipselink.weaving.lazy; default value=true
FINEST: property=eclipselink.weaving.eager; default value=false
FINEST: property=eclipselink.weaving.fetchgroups; default value=true
FINEST: property=eclipselink.weaving.internal; default value=true
FINEST: property=eclipselink.multitenant.tenants-share-cache; default value=false
FINEST: property=eclipselink.metadata-source; default value=null
FINEST: property=eclipselink.jpa.uppercase-column-names; default value=false
FINER: Searching for default mapping file in file:/K:/Java%20code/WebWormSales/build/web/WEB-INF/classes/
FINER: Searching for default mapping file in file:/K:/Java%20code/WebWormSales/build/web/WEB-INF/classes/
CONFIG: The access type for the persistent class [class entity.Salesrecords] is set to [FIELD].
CONFIG: The access type for the persistent class [class entity.Wormgrowers] is set to [FIELD].
CONFIG: The access type for the persistent class [class entity.Message] is set to [FIELD].
CONFIG: The access type for the persistent class [class entity.Sequence] is set to [FIELD].
CONFIG: The access type for the persistent class [class entity.SalesrecordsPK] is set to [FIELD].
CONFIG: The alias name for the entity class [class entity.Salesrecords] is being defaulted to: Salesrecords.
CONFIG: The alias name for the entity class [class entity.Wormgrowers] is being defaulted to: Wormgrowers.
CONFIG: The alias name for the entity class [class entity.Message] is being defaulted to: Message.
CONFIG: The alias name for the entity class [class entity.Sequence] is being defaulted to: Sequence.
FINER: Class [entity.SalesrecordsPK] registered to be processed by weaver.
FINER: Class [entity.Salesrecords] registered to be processed by weaver.
FINER: Class [entity.Wormgrowers] registered to be processed by weaver.
FINER: Class [entity.Message] registered to be processed by weaver.
FINER: Class [entity.Sequence] registered to be processed by weaver.
FINEST: End predeploying Persistence Unit WebWormSalesPU; session file:/K:/Java code/WebWormSales/build/web/WEB-INF/classes/_WebWormSalesPU; state Predeployed; factoryCount 1
FINEST: Begin weaver class transformer processing class [entity/Salesrecords].
FINEST: Weaved persistence (PersistenceEntity) [entity/Salesrecords].
FINEST: Weaved change tracking (ChangeTracker) [entity/Salesrecords].
FINEST: Weaved fetch groups (FetchGroupTracker) [entity/Salesrecords].
FINEST: End weaver class transformer processing class [entity/Salesrecords].
INFO: Portable JNDI names for EJB SalesrecordsFacade : [java:global/WebWormSales/SalesrecordsFacade!session.SalesrecordsFacade, java:global/WebWormSales/SalesrecordsFacade]
FINEST: Begin weaver class transformer processing class [entity/Wormgrowers].
FINEST: Weaved persistence (PersistenceEntity) [entity/Wormgrowers].
FINEST: Weaved change tracking (ChangeTracker) [entity/Wormgrowers].
FINEST: Weaved fetch groups (FetchGroupTracker) [entity/Wormgrowers].
FINEST: End weaver class transformer processing class [entity/Wormgrowers].
INFO: Portable JNDI names for EJB WormgrowersFacade : [java:global/WebWormSales/WormgrowersFacade!session.WormgrowersFacade, java:global/WebWormSales/WormgrowersFacade]
FINEST: Begin weaver class transformer processing class [entity/Sequence].
FINEST: Weaved persistence (PersistenceEntity) [entity/Sequence].
FINEST: Weaved change tracking (ChangeTracker) [entity/Sequence].
FINEST: Weaved fetch groups (FetchGroupTracker) [entity/Sequence].
FINEST: End weaver class transformer processing class [entity/Sequence].
INFO: Portable JNDI names for EJB SequenceFacade : [java:global/WebWormSales/SequenceFacade, java:global/WebWormSales/SequenceFacade!session.SequenceFacade]
FINEST: Begin weaver class transformer processing class [entity/Message].
FINEST: Weaved persistence (PersistenceEntity) [entity/Message].
FINEST: Weaved change tracking (ChangeTracker) [entity/Message].
FINEST: Weaved fetch groups (FetchGroupTracker) [entity/Message].
FINEST: End weaver class transformer processing class [entity/Message].
INFO: Portable JNDI names for EJB MessageFacade : [java:global/WebWormSales/MessageFacade!session.MessageFacade, java:global/WebWormSales/MessageFacade]
INFO: Initializing Mojarra 2.1.3 (FCS b02) for context '/WebWormSales'
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: Monitoring jndi:/server/WebWormSales/WEB-INF/faces-config.xml for modifications
INFO: WEB0671: Loading application [WebWormSales] at [/WebWormSales]
INFO: CORE10010: Loading application WebWormSales done in 37,754 ms
INFO: Oracle GlassFish Server 3.1.1 (12) startup time : Felix (3,945ms), startup services(40,869ms), total(44,814ms)
INFO: JMXStartupService: Started JMXConnector, JMXService URL = service:jmx:rmi://PSO-ecarter:8686/jndi/rmi://PSO-ecarter:8686/jmxrmi
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: WEB0169: Created HTTP listener [http-listener-1] on host/port [0.0.0.0:8080]
INFO: Grizzly Framework 1.9.36 started in: 10ms - bound to [0.0.0.0:8080]
INFO: WEB0169: Created HTTP listener [http-listener-2] on host/port [0.0.0.0:8181]
INFO: Grizzly Framework 1.9.36 started in: 10ms - bound to [0.0.0.0:8181]
INFO: ____________________________
Welcome to Apache Felix Gogo

INFO: g!
INFO: gosh: stopping framework
INFO: Stopping com.sun.enterprise.v3.server.AppServerStartup@e25f8a
FINEST: Begin undeploying Persistence Unit WebWormSalesPU; session file:/K:/Java code/WebWormSales/build/web/WEB-INF/classes/_WebWormSalesPU; state Predeployed; factoryCount 1
INFO: RAR7094: __ds_jdbc_ra shutdown successful.
FINEST: End undeploying Persistence Unit WebWormSalesPU; session file:/K:/Java code/WebWormSales/build/web/WEB-INF/classes/_WebWormSalesPU; state Undeployed; factoryCount 0
INFO: JMXStartupService: Stopped JMXConnectorServer: null
INFO: JMXStartupService and JMXConnectors have been shut down.
INFO: Shutdown procedure finished
INFO: [Thread[GlassFish Kernel Main Thread,5,main]] exiting
Completed shutdown of Log manager service
Error stopping framework: org.glassfish.embeddable.GlassFishException: org.osgi.framework.BundleException: Bundle org.apache.felix.framework [0] cannot be stopped since it is already stopping.
org.glassfish.embeddable.GlassFishException: org.osgi.framework.BundleException: Bundle org.apache.felix.framework [0] cannot be stopped since it is already stopping.
at com.sun.enterprise.glassfish.bootstrap.osgi.OSGiGlassFishRuntime.shutdown(OSGiGlassFishRuntime.java:81)
at com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher$1.run(GlassFishMain.java:203)
Caused by: org.osgi.framework.BundleException: Bundle org.apache.felix.framework [0] cannot be stopped since it is already stopping.
at org.apache.felix.framework.Felix.stopBundle(Felix.java:2139)
at org.apache.felix.framework.Felix.stop(Felix.java:869)
at com.sun.enterprise.glassfish.bootstrap.osgi.OSGiGlassFishRuntime.shutdown(OSGiGlassFishRuntime.java:76)
... 1 more



 Comments   
Comment by Ed Burns [ 19/Aug/11 ]

It seems your are running stock GlassFish 3.1:

Running GlassFish Version: Oracle GlassFish Server 3.1 (build 43)

with Mojarra 2.1:

Initializing Mojarra 2.1.0 (FCS 2.1.0-b11)

And later in the log file I see:

Oracle GlassFish Server 3.1.1 (build 12)

[...]

Initializing Mojarra 2.1.3 (FCS b02)

With GlassFish 3.1 I see the server shutdown being initiated soon after Mojarra initialized.

With GlassFish 3.1.1 I see several SEVERE errors from the Felix OSGi system soon after Mojarra is initialized.

It appears there are several more attempts to start the server, each of which has a shutdown soon after the Mojarra initialization.

The last such attempt fails with this exception log:

Caused by: java.lang.ClassNotFoundException: com/sun/enterprise/security/jmac/config/GFAuthConfigFactory
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at javax.security.auth.message.config.AuthConfigFactory$1.run(AuthConfigFactory.java:217)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.message.config.AuthConfigFactory.getFactory(AuthConfigFactory.java:206)
... 24 more

#]

I see no evidence that JSF is the cause of these failures, while I do see evidence that looking into the OSGi bundles or the security problem may lead to a resolution of the problem.

Therefore, I am going to edit this issue to give it a specific component and let JIRA assign the issue to the component leader.

Comment by Ed Burns [ 19/Aug/11 ]

Assign to security component.





[GLASSFISH-17106] [UB]Add userdefined library information to load-balancer documentation Created: 26/Jul/11  Updated: 07/Mar/12

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: kshitiz_saxena Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PDF File user-defined-load-balancing.pdf    
Issue Links:
Dependency
blocks GLASSFISH-16616 ReadMe.UserDefinedLB needs an update ... Reopened

 Description   

There is Readme for userdefined library bundled with load-balancer plugin. This information can be captured in load-balancer documentation itself.



 Comments   
Comment by kshitiz_saxena [ 26/Jul/11 ]

Content of user defined README
---------------------------------

With User Defined Loadbalancer the user can have a custom logic for loadbalancing. Examples would be user identity based redirect, mime based load balancing etc. The user of this feature has to develop a shared library which would be loaded by load balancer. The user has to implement the interface as defined in loadbalancer.h which be placed in <glassfish plugin install dir>/lib/install/templates. An example module which implements the basic roundrobin algorithm(roundrobin.c) is included. The following are the steps needed to compile and configure the User Defined module.
1. Copy the roundrobin.c to a work directory (for example: /home/user/workspacelb).
2. Compile roundrobin.c with either the ANSI C/C++ compiler(for eg. sunstudio compiler or gcc). Take care to build a dynamic shared library and not a static executable.

  • Using sun studio cc compiler:
    % cc -m64 -G -I<glassfish plugin install dir>/lib/install/templates roundrobin.c -o roundrobin.so
    Note: In case of relocations error, use option "-xcode=pic32" with cc. cc -m64 -G -xcode=pic32 -I<glassfish plugin install dir>/lib/install/templates roundrobin.c -o roundrobin.so
  • Using gcc
    % gcc -m64 -shared -I<glassfish plugin install dir>/lib/install/templates roundrobin.c -o roundrobin.so
    Note: In case of relocations error, use option "-fPIC" with gcc. The command will look like: gcc -m64 -shared -fPIC -I<glassfish plugin install dir>/lib/install/templates roundrobin.c -o roundrobin.so
  • On windows download MSVC++ 2008 Express Edition from http://www.microsoft.com/express/download/ . Ensure that system environment variables related to MSVC are set. These include INCLUDE=<msvc-install-dir/VC/include>, LIB=<msvc-install-dir>/VC/lib;<microsoft-sdk-lib-dir>. Also note to update the PATH to include <msvc-install-dir>/VC/bin;<msvc-install-dir>/Common7/IDE. The command to build the dll would be:
    % cl /D_WINDOWS /I<glassfish plugin install dir>/lib/install/templates /LD roundrobin.c

3. Change the loadbalancer.xml to point to the newly built module.
<cluster name="cluster1" policy="user-defined" policy-module="home/user/workspacelb/roundrobin.so">

4. Start the webserver if its not running or wait till LB re-configure.

Comment by Mike Fitch [ 01/Feb/12 ]

The attachment user-defined-load-balancing.pdf shows the content added to the HA Admin Guide to resolve this issue. Please review this content and update this issue with comments.

Comment by kshitiz_saxena [ 02/Feb/12 ]

Change
< To Build the Sample User-Defined Load Balancing Algorithm on Solaris
to
>To Build the Sample User-Defined Load Balancing Algorithm on Unix platform

Change
< The cc compiler, version 4.0.4 or later
to
> The sun studio cc compiler, version 4.0.4 or later

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-17004] firefox 5.0 : few icons in the promotion page doesn't display Created: 08/Jul/11  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: other
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: shaline Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: windows 2008 server
Browser : FireFox 5.0


Attachments: JPEG File ff5-winxp-aix.JPG     JPEG File ff5.jpg     JPEG File mac-ff5.jpg    
Tags: 3_1_1-scrubbed, 3_1_2-exclude

 Description   

GF 3.1.1 promoted build 10.

In the common tasks window right bottom frame, the icons for facebook, twitter, youtube etc under "Stay Connected" section are not displayed in firefox 5.0 browser. This is visible in IE, and ff 3.6.
Attached the screen shot for the common tasks window.



 Comments   
Comment by Anissa Lam [ 08/Jul/11 ]

Does this always reproducible ?
It shows up correctly for me on Firefox 5 on my Mac. (see attached mac-ff5.jpg

If you use your browser and go to "http://java.sun.com/glassfish/productmsg.html" directly, does it show up ?

This is not from GUI and there is nothing i can do if it doesn't show up.

Comment by Anissa Lam [ 08/Jul/11 ]

Jason mentioned that he is seeing the problem on FF5. No error in server.log nor firebug console.
I am running 5.0 on my Mac, I cleared cache and restart browser, it works for me though.

Transferring to John since he owns this promotion page.

Comment by lidiam [ 09/Jul/11 ]

I can see the icons fine on FF5 on Windows XP with build ogs-3.1.1-b11-07_07_2011-aix.zip (on AIX).

Comment by lidiam [ 09/Jul/11 ]

Icons displayed in FF5 on Windows XP, Glassfish on AIX.

Comment by shaline [ 12/Jul/11 ]

On the promoted b11, the issue still exists on windows 2008 server. The links like "http://java.sun.com/glassfish/productmsg.html when directly accessed works fine , but the icons in the bottom promotion page are not displayed, in the Common Tasks window.

Comment by scatari [ 02/Nov/11 ]

Look into to see if this is a browser/os specific issue.

Comment by scatari [ 18/Jan/12 ]

Romaine, Could you please look at this issue?

Comment by Joe Di Pol [ 21/Jan/12 ]

Another data point: I tried Firefox 9.0.1 on Windows Server 2008 with a 3.1.2 build and the icons showed up fine.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16978] [UB]Change error message OR Improve documentation Created: 07/Jul/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: alessalessio Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 1 day
Time Spent: Not Specified
Original Estimate: 1 day
Environment:

Windows 7, Eclipse Helios


Tags: documentation, error_handling, masterpassword

 Description   

Documentation about securing domain passwords in Glassfish should be improved, or error log changed.

Suppose to have a Connection Pool and a related resource. This connection pool contains:
<property name="password" value="$

{ALIAS=dbpass}

"/>.

As stated in Glassfish documentation, the encrypted value of the password linked by the alias is contained into a domain-passwords file. The key which encrypts and decrypts this password is contained into a masterpassword file (supposing that the domain is created with --savemasterpassword=true option).

Now, if i develop a we application running on a Glassfish server, and i want to protect it, leaving the DB access only to people that I want to. If i give a copy of those files (masterpassword and domain-passwords) to those people, they should be able to connect to the DB (since they have my masterpassword, and domain-passwords).

This actually does not happen, and Glassfish console states:
"The Master Password is required to start the domain. No console, no prompting possible. You should either create the domain with --savemasterpassword=true or provide a password file with the --passwordfile option."

Which is actually NOT true. The masterpassword is present and it was created with --savemasterpassword=true.

The problem seems to be that actually, i would need to send both masterpassword, domain-passwords, AND keystore.jks and cacerts.jks.

So please provide a better explanation how these two files are related to the masterpassword AND/OR change that error log.



 Comments   
Comment by Tom Mueller [ 22/Dec/11 ]

This is actually a documentation improvement suggestion.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16952] Provide copy realm function Created: 04/Jul/11  Updated: 27/Mar/13

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Minor
Reporter: mkarg Assignee: JeffTancill
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Did a typo when creating a JDBC realm, wanted to fix it... bug cannot after pressing OK!

Would be great if the GUI would allow to rename a realm, so I am not forced to type in all the complete config again. This is not very smart.



 Comments   
Comment by Anissa Lam [ 04/Jul/11 ]

The name of the realm is the id /primary key for this realm, just like any other element, like name of instance, name of cluster, listener, anything. Once it is created, the name cannot be changed.
There is no way to do that.
Maybe you can request the backend to provide a copy-realm function , then you can copy and delete the previous one.
I will change this to request a copy function and transfer to backend.
If this is implemented, then console can add in the UI.

Comment by mkarg [ 06/Jul/11 ]

I do not see how the backend could solve this. The information I want to keep at the renaming is the configuration of a jdbc-realm. Only GlassFish knows that information. The backend is out of scope and has no problem.

Comment by mkarg [ 06/Jul/11 ]

I do not see why it shall be impossible to implement the rename. You can just implement it as a copy-delete action:

  • Create new realm configuration as a copy of the old one, using the target name.
  • Remove the configuration of the old realm, using the source name.
  • Replace the old realm name by the new realm name wherever it is reference in the GlassFish configuration.
Comment by Anissa Lam [ 06/Jul/11 ]

When i say 'backend', i mean the GF admin or security team.
They can provide the copy-realm command so that all clients can benefit from it.

Comment by mkarg [ 07/Jul/11 ]

I see. I assumed that "backend" is the server, as typical in IT discussions.





[GLASSFISH-16825] If It is Impossible to Transform Classes -- Disable Monitoring Created: 08/Jun/11  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: monitoring
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Byron Nevins Assignee: Byron Nevins
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-next, 3_1_1-scrubbed, 3_1_x-exclude

 Description   

Very early in the process of booting up a GF Server we should check and see if it is possible to do bytecode transformation of classes. If NOT then we should :

1) if monitoring is enabled, log a SEVERE message about the problem and then disable monitoring – but just for that run. Don't persist it in domain.xml

2) if monitoring is disabled – then do nothing

In either case if the user runs "enable-monitoring" we should return a strongly worded error.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16805] [osgi-cdi] support @Inject @OSGiService Instance<T> Created: 06/Jun/11  Updated: 22/Nov/12

Status: Open
Project: glassfish
Component/s: OSGi-JavaEE
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Sanjeeb Sahoo Assignee: Sivakumar Thyagarajan
Resolution: Unresolved Votes: 1
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-18978 select OSGi services used in CDI bean... Sub-task Open Sanjeeb Sahoo  
Tags: 3_1-next

 Description   

Currently having something like
@Inject @OSGiService(dynamic=true)
private Instance<AdminService> adminService;

cause following exception:

java.lang.UnsupportedOperationException: Injection target type javax.enterprise.inject.Instance<org.glassfish.fighterfish.test.app18.AdminService>not supported
at org.glassfish.osgicdi.impl.OSGiServiceExtension.afterBeanDiscovery(OSGiServiceExtension.java:185)
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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:88)
at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:52)
at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:43)
at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:372)
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:170)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:270)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
at org.glassfish.osgijavaeebase.OSGiDeploymentRequest.deploy(OSGiDeploymentRequest.java:183)
at org.glassfish.osgijavaeebase.OSGiDeploymentRequest.execute(OSGiDeploymentRequest.java:118)
at org.glassfish.osgijavaeebase.AbstractOSGiDeployer.deploy(AbstractOSGiDeployer.java:121)
at org.glassfish.osgijavaeebase.OSGiContainer.deploy(OSGiContainer.java:154)
at org.glassfish.osgijavaeebase.JavaEEExtender.deploy(JavaEEExtender.java:107)
at org.glassfish.osgijavaeebase.JavaEEExtender.access$200(JavaEEExtender.java:61)
at org.glassfish.osgijavaeebase.JavaEEExtender$HybridBundleTrackerCustomizer$1.call(JavaEEExtender.java:151)
at org.glassfish.osgijavaeebase.JavaEEExtender$HybridBundleTrackerCustomizer$1.call(JavaEEExtender.java:148)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:55)
at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:43)
at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:372)
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:170)
... 17 more

#]


 Comments   
Comment by Sanjeeb Sahoo [ 06/Jun/11 ]

assigning to Siva for evaluation.

Comment by Sivakumar Thyagarajan [ 07/Jun/11 ]

Tagging this as 3_1-next, as this is not critical for the 3.1.1 release.

Comment by Sanjeeb Sahoo [ 07/Jun/11 ]

Do you know why it is not working? Can you at least mention the reason?

Comment by Sivakumar Thyagarajan [ 13/Jun/11 ]

Marked it as an improvement(RFE)

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by TangYong [ 06/Aug/12 ]

Now, the feature has been supported combined with subTask(GLASSFISH-18978). Please see.

https://github.com/tangyong/gf-cdi-osgi-integration

DEMO1: https://github.com/tangyong/gf-cdi-osgi-integration/tree/master/samples/[RFP146]CDI018
DEMO2: https://github.com/tangyong/gf-cdi-osgi-integration/tree/master/samples/[RFP146]CDI004

Using Way:

1 get all osgi services
@Inject Service<StockQuoteService> sqses;
....

2 get osgi services qualified @ServiceFilter
@Inject @ServiceFilter("(country=CN)") Service<StockQuoteService> sqses;
...

Comment by TangYong [ 22/Nov/12 ]

After event integration was finished, the feature will start because compared with other features, it has been turned more important.





[GLASSFISH-16687] [UB]GFv3: add DB2 Type4 Driver to supported driver list Created: 19/May/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Task Priority: Minor
Reporter: Andreas Rieck Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux SLES 10 and SLES 11, GFv3.01 and GFv3.1, IBM DB2 JDBC Type-4 driver


Tags: DB2, JDBC, Type-4

 Description   

Seen within Oracle GlassFish Server 3.1 Administration Guide, Section Configuration Specifics for JDBC Drivers,
it is described that GlassFish Server is designed to support connectivity to any database management system
by using a corresponding JDBC driver.
http://download.oracle.com/docs/cd/E18930_01/html/821-2416/beamw.html

However on the list for configuration information the "IBM DB2 Database Type 4 Driver" is not included.
The documentation looks like that DB2 type-4 driver is not supported, but we do provide
already within GFv2 and GFv3 installations coresponding configuration template as well.

see:

GFv2_INSTALL_DIR/lib/install/templates/resources/jdbc/db2_jcc_datasource.xml
GFv3_INSTALL_DIR/glassfish/lib/install/templates/resources/jdbc/db2_jcc_datasource.xml

Content of db2_jcc_datasource.xml, special the entry "driverType".

...
IBM DB2 JDBC type-4 driver for DB2 Databases
The JAR file for the DB2 driver db2jcc.jar
...
<jdbc-connection-pool
name="db2_jcc_pool"
datasource-classname="com.ibm.db2.jcc.DB2SimpleDataSource"
res-type="javax.sql.DataSource">
<property name="user" value="DB_USER"/>
<property name="password" value="DB_PASSWORD"/>
<property name="serverName" value="DB_HOSTNAME"/>
<property name="portNumber" value="50000"/>
<property name="databaseName" value="DATABASE_NAME"/>
<property name="driverType" value="4"/>
</jdbc-connection-pool>
...

Same IBM DB2 type 4 JDBC driver usage is described vor GFv1/v2 at Jagadish's Blog
http://blogs.oracle.com/JagadishPrasath/entry/jdbc_connection_pool_templates_glassfish

This is a Documentation RFE request, to please add "IBM DB2 Database Type 4 Driver" to this list as well.
http://download.oracle.com/docs/cd/E18930_01/html/821-2416/beamw.html

IBM's article about DB2 JDBC can be found here:
http://www.ibm.com/developerworks/data/library/techarticle/0203zikopoulos/0203zikopoulos.html#type2
http://www.ibm.com/developerworks/data/library/techarticle/0203zikopoulos/0203zikopoulos.html#type4



 Comments   
Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16619] Got com.sun.xml.wss.XWSSecurityException when ran some WSS security tests on AIX Created: 12/May/11  Updated: 09/Apr/12

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: sonialiu Assignee: JeffTancill
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

AIX, IBM jdk1.6.0


Attachments: File all.log.b07     Text File server.log     Text File server.log    
Tags: 3_1-approved

 Description   

build: V3.1.1 build 4
OS: AIX

Please note that this test only failed on AIX and it passed on all other OS/platforms.

Steps to reproduce the bug:
1.Checkout SQE workspace:
cvs co appserver-sqe/bootstrap.xml
(CVSROOT=:pserver:cvsguest@sunsw.us.oracle.com:/m/jws)
cd appserver-sqe
ant -f bootstrap.xml co-security
2. install GF V3.1.1, start domain domain1
3. Set env. variables
S1AS_HOME <GF installation dir> (example: /export/sonia/v3/glassfishv3/glassfish
SPS_HOME <workspace dir> (example: /export/sonia/appserver-sqe)
ANT_HOME <ant dir>
JAVA_HOME <java dir>
4. cd appserver-sqe/pe/security/wss/annotations/servletws, run "ant all", test failed with the following error:
[exec] </S:Envelope>==== Received Message End ====
[exec] [exec] May 11, 2011 2:19:20 AM com.sun.xml.wss.impl.SecurityRecipient processMessagePolicy
[exec] SEVERE: WSS0253: Message does not conform to configured policy: No Security Header found in message
[exec] com.sun.xml.wss.XWSSecurityException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.wss.impl.SecurityRecipient.processMessagePolicy(SecurityRecipient.java:818)
[exec] at com.sun.xml.wss.impl.SecurityRecipient.validateMessage(SecurityRecipient.java:261)
[exec] at com.sun.xml.wss.provider.ClientSecurityAuthModule.validateResponse(ClientSecurityAuthModule.java:156)
[exec] at com.sun.enterprise.security.jmac.config.GFServerConfigProvider$GFClientAuthContext.validateResponse(GFServerConfigProvider.java:1279)
[exec] at com.sun.enterprise.security.webservices.ClientSecurityPipe.processSecureRequest(ClientSecurityPipe.java:211)
[exec] at com.sun.enterprise.security.webservices.ClientSecurityPipe.process(ClientSecurityPipe.java:184)
[exec] at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:119)
[exec] at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641)
[exec] at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600)
[exec] at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585)
[exec] at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482)
[exec] at com.sun.xml.ws.client.Stub.process(Stub.java:323)
[exec] at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:161)
[exec] at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:113)
[exec] at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
[exec] at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:144)
[exec] at $Proxy49.getFedTax(Unknown Source)
[exec] at com.sun.appserv.sqe.security.wss.annotations.client.TaxCalClient.callTaxService(TaxCalClient.java:85)
[exec] at com.sun.appserv.sqe.security.wss.annotations.client.TaxCalClient.main(TaxCalClient.java:64)
[exec] javax.xml.ws.WebServiceException: Cannot validate response for

{http://sun.com/appserv/sqe/security/taxws}

TaxPort
[exec] at com.sun.enterprise.security.webservices.ClientSecurityPipe.processSecureRequest(ClientSecurityPipe.java:215)
[exec] at com.sun.enterprise.security.webservices.ClientSecurityPipe.process(ClientSecurityPipe.java:184)
[exec] at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:119)
[exec] at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641)
[exec] at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600)
[exec] at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585)
[exec] at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482)
[exec] at com.sun.xml.ws.client.Stub.process(Stub.java:323)
[exec] at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:161)
[exec] at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:113)
[exec] at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
[exec] at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:144)
[exec] at $Proxy49.getFedTax(Unknown Source)
[exec] at com.sun.appserv.sqe.security.wss.annotations.client.TaxCalClient.callTaxService(TaxCalClient.java:85)
[exec] at com.sun.appserv.sqe.security.wss.annotations.client.TaxCalClient.main(TaxCalClient.java:64)
[exec] Caused by: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.wss.provider.ClientSecurityAuthModule.validateResponse(ClientSecurityAuthModule.java:161)
[exec] at com.sun.enterprise.security.jmac.config.GFServerConfigProvider$GFClientAuthContext.validateResponse(GFServerConfigProvider.java:1279)
[exec] at com.sun.enterprise.security.webservices.ClientSecurityPipe.processSecureRequest(ClientSecurityPipe.java:211)
[exec] ... 14 more
[exec] TaxCal client failed
[exec] Generating report at /export/hudson/workspace/alex-aix3.1.1gf/appserver-sqe/test_results.xml
[exec] [exec] [exec] -----------------------------------------
[exec] - sec-wss-annotate-servletwsendpoint-getFedTax: FAIL -
[exec] -----------------------------------------
[exec] Total PASS: 0
[exec] Total FAIL: 1
[exec] Total DNR: 0
[exec] ----------------------------------



 Comments   
Comment by kumarjayanti [ 13/May/11 ]

Can you attach the sever.log for the failure.

Comment by sonialiu [ 13/May/11 ]

attached server.log

Comment by kumarjayanti [ 18/May/11 ]

Made a change in Metro which when integrated into 3.1.1 might fix the issue.

Comment by scatari [ 07/Jun/11 ]

Pre-approving for 3.1.1 as this is a test blocker.

Comment by scatari [ 08/Jun/11 ]

Updated Metro integrated into 3.1.1 for B07.

Comment by sonialiu [ 10/Jun/11 ]

I saw some new WSS failures(25+ more) which I did not see in b06, and the exceptions in the client side seems similar as I reported in the bug. To reproduce the new failures:
1. cd appserver-sqe/pe/security/wss/enforcepolicy
2. run "ant all"
The following error displayed:

[exec] Jun 10, 2011 2:17:34 PM com.sun.xml.wss.impl.SecurityRecipient processMessagePolicy
[exec] SEVERE: WSS0253: Message does not conform to configured policy: No Security Header found in message
[exec] com.sun.xml.wss.XWSSecurityException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.wss.impl.SecurityRecipient.processMessagePolicy(SecurityRecipient.java:818)
[exec] at com.sun.xml.wss.impl.SecurityRecipient.validateMessage(SecurityRecipient.java:261)
[exec] at com.sun.xml.wss.provider.ClientSecurityAuthModule.validateResponse(ClientSecurityAuthModule.java:156)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invokePriv(AuthContext.java:143)
[exec] at com.sun.enterprise.security.jauth.AuthContext$1.run(AuthContext.java:93)
[exec] at java.security.AccessController.doPrivileged(AccessController.java:251)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invoke(AuthContext.java:90)
[exec] at com.sun.enterprise.security.jauth.ConfigFile$ConfigClient.validateResponse(ConfigFile.java:619)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:281)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:263)
[exec] at com.sun.enterprise.security.webservices.MessageLayerClientHandler.handleResponse(MessageLayerClientHandler.java:167)
[exec] at com.sun.xml.rpc.client.HandlerChainImpl.handleResponse(HandlerChainImpl.java:131)
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:810)
[exec] at com.sun.xml.rpc.client.StreamingSender._preHandlingHook(StreamingSender.java:732)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxIF_Stub._preHandlingHook(TaxIF_Stub.java:436)
[exec] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:124)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxIF_Stub.getStateTax(TaxIF_Stub.java:277)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.testStateTax(TaxCalClient.java:114)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.main(TaxCalClient.java:52)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at org.glassfish.appclient.client.acc.AppClientContainer.launch(AppClientContainer.java:438)
[exec] at org.glassfish.appclient.client.AppClientFacade.launch(AppClientFacade.java:182)
[exec] at org.glassfish.appclient.client.AppClientGroupFacade.main(AppClientGroupFacade.java:65)
[exec] Jun 10, 2011 2:17:34 PM com.sun.enterprise.security.webservices.WebServiceSecurity validateResponse
[exec] SEVERE: Container-auth: wss: Error validating response
[exec] Throwable occurred: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.wss.provider.ClientSecurityAuthModule.validateResponse(ClientSecurityAuthModule.java:161)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invokePriv(AuthContext.java:143)
[exec] at com.sun.enterprise.security.jauth.AuthContext$1.run(AuthContext.java:93)
[exec] at java.security.AccessController.doPrivileged(AccessController.java:251)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invoke(AuthContext.java:90)
[exec] at com.sun.enterprise.security.jauth.ConfigFile$ConfigClient.validateResponse(ConfigFile.java:619)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:281)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:263)
[exec] at com.sun.enterprise.security.webservices.MessageLayerClientHandler.handleResponse(MessageLayerClientHandler.java:167)
[exec] at com.sun.xml.rpc.client.HandlerChainImpl.handleResponse(HandlerChainImpl.java:131)
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:810)
[exec] at com.sun.xml.rpc.client.StreamingSender._preHandlingHook(StreamingSender.java:732)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxIF_Stub._preHandlingHook(TaxIF_Stub.java:436)
[exec] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:124)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxIF_Stub.getStateTax(TaxIF_Stub.java:277)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.testStateTax(TaxCalClient.java:114)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.main(TaxCalClient.java:52)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at org.glassfish.appclient.client.acc.AppClientContainer.launch(AppClientContainer.java:438)
[exec] at org.glassfish.appclient.client.AppClientFacade.launch(AppClientFacade.java:182)
[exec] at org.glassfish.appclient.client.AppClientGroupFacade.main(AppClientGroupFacade.java:65)
[exec] Jun 10, 2011 2:17:34 PM com.sun.enterprise.security.webservices.MessageLayerClientHandler handleResponse
[exec] WARNING: SEC2005: Container-auth: wss: Error validating response
[exec] Throwable occurred: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.wss.provider.ClientSecurityAuthModule.validateResponse(ClientSecurityAuthModule.java:161)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invokePriv(AuthContext.java:143)
[exec] at com.sun.enterprise.security.jauth.AuthContext$1.run(AuthContext.java:93)
[exec] at java.security.AccessController.doPrivileged(AccessController.java:251)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invoke(AuthContext.java:90)
[exec] at com.sun.enterprise.security.jauth.ConfigFile$ConfigClient.validateResponse(ConfigFile.java:619)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:281)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:263)
[exec] at com.sun.enterprise.security.webservices.MessageLayerClientHandler.handleResponse(MessageLayerClientHandler.java:167)
[exec] at com.sun.xml.rpc.client.HandlerChainImpl.handleResponse(HandlerChainImpl.java:131)
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:810)
[exec] at com.sun.xml.rpc.client.StreamingSender._preHandlingHook(StreamingSender.java:732)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxIF_Stub._preHandlingHook(TaxIF_Stub.java:436)
[exec] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:124)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxIF_Stub.getStateTax(TaxIF_Stub.java:277)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.testStateTax(TaxCalClient.java:114)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.main(TaxCalClient.java:52)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at org.glassfish.appclient.client.acc.AppClientContainer.launch(AppClientContainer.java:438)
[exec] at org.glassfish.appclient.client.AppClientFacade.launch(AppClientFacade.java:182)
[exec] at org.glassfish.appclient.client.AppClientGroupFacade.main(AppClientGroupFacade.java:65)
[exec] java.rmi.RemoteException: response handler error: ; nested exception is:
[exec] javax.xml.rpc.JAXRPCException: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:812)
[exec] at com.sun.xml.rpc.client.StreamingSender._preHandlingHook(StreamingSender.java:732)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxIF_Stub._preHandlingHook(TaxIF_Stub.java:436)
[exec] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:124)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxIF_Stub.getStateTax(TaxIF_Stub.java:277)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.testStateTax(TaxCalClient.java:114)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.main(TaxCalClient.java:52)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at org.glassfish.appclient.client.acc.AppClientContainer.launch(AppClientContainer.java:438)
[exec] at org.glassfish.appclient.client.AppClientFacade.launch(AppClientFacade.java:182)
[exec] at org.glassfish.appclient.client.AppClientGroupFacade.main(AppClientGroupFacade.java:65)
[exec] Caused by: javax.xml.rpc.JAXRPCException: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.enterprise.security.webservices.MessageLayerClientHandler.handleResponse(MessageLayerClientHandler.java:172)
[exec] at com.sun.xml.rpc.client.HandlerChainImpl.handleResponse(HandlerChainImpl.java:131)
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:810)
[exec] ... 13 more
[exec] Unknown exception during getStateTax()
[exec] Jun 10, 2011 2:17:35 PM com.sun.xml.wss.impl.filter.DumpFilter process
[exec] INFO: ==== Sending Message Start ====

************************************
In the server.log I saw the following exceptions:
********

[#|2011-06-10T14:17:34.545-0700|SEVERE|glassfish3.1|javax.enterprise.system.core.security.com.sun.enterprise.security.webservices|_ThreadID=9;_ThreadName=Thread-6;|SEC2003: Container-auth: wss: Error securing response
com.sun.enterprise.security.jauth.AuthException: java.lang.NullPointerException
at com.sun.xml.wss.provider.ServerSecurityAuthModule.secureResponse(ServerSecurityAuthModule.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.sun.enterprise.security.jauth.AuthContext.invokePriv(AuthContext.java:143)
at com.sun.enterprise.security.jauth.AuthContext$1.run(AuthContext.java:93)
at java.security.AccessController.doPrivileged(AccessController.java:251)
at com.sun.enterprise.security.jauth.AuthContext.invoke(AuthContext.java:90)
at com.sun.enterprise.security.jauth.ConfigFile$ConfigServer.secureResponse(ConfigFile.java:660)
at com.sun.enterprise.security.webservices.WebServiceSecurity.secureResponse(WebServiceSecurity.java:198)
at com.sun.enterprise.security.webservices.WebServiceSecurity.secureResponse(WebServiceSecurity.java:175)
at com.sun.enterprise.security.webservices.ServletSystemHandlerDelegate.processResponse(ServletSystemHandlerDelegate.java:247)
at org.glassfish.webservices.monitoring.JAXRPCEndpointImpl.processResponse(JAXRPCEndpointImpl.java:151)
at com.sun.xml.rpc.server.http.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:468)
at org.glassfish.webservices.JAXRPCServlet.doPost(JAXRPCServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1539)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:330)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:232)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:736)

#]
Caused by: com.sun.enterprise.security.jauth.AuthException: java.lang.NullPointerException
at com.sun.xml.wss.provider.ServerSecurityAuthModule.secureResponse(ServerSecurityAuthModule.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.sun.enterprise.security.jauth.AuthContext.invokePriv(AuthContext.java:143)
at com.sun.enterprise.security.jauth.AuthContext$1.run(AuthContext.java:93)
at java.security.AccessController.doPrivileged(AccessController.java:251)
at com.sun.enterprise.security.jauth.AuthContext.invoke(AuthContext.java:90)
at com.sun.enterprise.security.jauth.ConfigFile$ConfigServer.secureResponse(ConfigFile.java:660)
at com.sun.enterprise.security.webservices.WebServiceSecurity.secureResponse(WebServiceSecurity.java:198)
at com.sun.enterprise.security.webservices.WebServiceSecurity.secureResponse(WebServiceSecurity.java:175)
at com.sun.enterprise.security.webservices.ServletSystemHandlerDelegate.processResponse(ServletSystemHandlerDelegate.java:247)

Here is the list of wss test cases failed in b07.
appserver-sqe/pe/security/wss/annotations/ejbws
appserver-sqe/pe/security/wss/annotations/servletws
appserver-sqe/pe/security/wss/enforcepolicy/servletws
appserver-sqe/pe/security/wss/dynencryptkey/servletws
appserver-sqe/pe/security/wss/ejbws
appserver-sqe/pe/security/wss/ejbclient
appserver-sqe/pe/security/wss/annotations/ejbws
appserver-sqe/pe/security/wss/annotations/servletws
appserver-sqe/pe/security/wss/mesgmethod/ejbws
appserver-sqe/pe/security/wss/mesgmethod/servletws
appserver-sqe/pe/security/wss/mesgoperation/servletws
appserver-sqe/pe/security/wss/mesgoperation/ejbws
appserver-sqe/pe/security/wss/encrypt/servletws
appserver-sqe/pe/security/wss/encrypt/ejbws
appserver-sqe/pe/security/wss/clienthandler/ejbws
appserver-sqe/pe/security/wss/clientmesgoperation/ejbws
appserver-sqe/pe/security/wss/clientmesgoperation/servletws
appserver-sqe/pe/security/wss/transpo/ejbws
appserver-sqe/pe/security/wss/transpo/servletws
appserver-sqe/pe/security/wss/runasubject/servletws
appserver-sqe/pe/security/auditmodule/apps/ejbws
appserver-sqe/pe/security/auditmodule/apps/servletws

– The exceptions in client side and server.log are attached.

Comment by sonialiu [ 10/Jun/11 ]

server.log and client log for b07

Comment by kumarjayanti [ 13/Jun/11 ]

Why fix this issue in 3.1.1?
It is a QE failure that occurs only on AIX

Which is the targeted build of 3.1.1 for this fix?
TBD

Do regression tests exist for this issue?
YES

Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
The GF Security WebService QE tests.

Comment by sherryshen [ 06/Jul/11 ]

3 runs on b10 are posted for comparing security failure on RunID 55, 56, 57.
http://agni-1.us.oracle.com/JSPWiki/Wiki.jsp?page=GF311SQETest
For webservices security failures:
--b07 has more failures than b04.
--b10 has less failures than b07
I looked into one failure as a reference to look at the test client output.
html report gives machine name for hudson execution, and test case location.
To look at server.log, please login the machine as a hudson user.

--The core result page gives the link of summary report

--summary report gives the link to module report

--module html report gives test case info
http://agni-1.us.oracle.com/asqe-logs/export1/3.1.1/Results/build10/core/aix_security/html/test_results_security.html
Sec::wss_servletws-runas-principal-mls-signatureID
1 fail, 1 pass
/export/hudson/workspace/sherry-aix-311-security/appserver-sqe/pe/security/wss/runasubject/servletws/.
Sec::wss_servletws-runas-principal-mls-signatureID pass
Sec::wss_servletws-runas-principal-mls-usernametokenID fail

--The client output privide more info
http://agni-1.us.oracle.com/asqe-logs/export1/3.1.1/Results/build10/core/aix_security/output/security.wss.output

runclient-ssl-pe:
[echo] Test is running on Platform Edition!
[exec] Jul 3, 2011 1:37:36 PM org.glassfish.appclient.client.acc.AppclientCommandArguments warnAboutPasswordUsage
[exec] WARNING: ACC013: The -password option is deprecated and will likely be removed in a future release. Please use -passwordfile or let the app client container prompt for the username and/or password if they are needed to access a remote resource.
[exec] Jul 3, 2011 1:37:39 PM com.sun.enterprise.deployment.node.SaxParserHandler error
[exec] SEVERE: DPL8015: Invalid Deployment Descriptors in Deployment descriptor file META-INF/application-client.xml in archive [wss-taxcal-clientClient.jar].
[exec] Line 13 Column 26 – cvc-complex-type.2.4.b: The content of element 'port-component-ref' is not complete. One of '

{"http://java.sun.com/xml/ns/javaee":service-endpoint-interface}

' is expected.
[exec] Jul 3, 2011 1:37:40 PM com.sun.enterprise.deployment.node.SaxParserHandler error
[exec] SEVERE: DPL8015: Invalid Deployment Descriptors in Deployment descriptor file META-INF/application-client.xml in archive [wss-taxcal-clientClient.jar].
[exec] Line 14 Column 26 – cvc-complex-type.2.4.b: The content of element 'port-component-ref' is not complete. One of '

{"http://java.sun.com/xml/ns/javaee":service-endpoint-interface}

' is expected.
[exec] Jul 3, 2011 1:37:40 PM com.sun.enterprise.deployment.ServiceReferenceDescriptor addRuntimePortInfo
[exec] WARNING: Runtime port info SEI null is not declared in standard service-ref deployment descriptors (under port-component-ref), is this intended ?
[exec] WS HOME appserver-sqe
[exec] Jul 3, 2011 1:37:41 PM com.sun.enterprise.deployment.node.SaxParserHandler error
[exec] SEVERE: DPL8015: Invalid Deployment Descriptors in Deployment descriptor file META-INF/application-client.xml in archive [wss-taxcal-clientClient.jar].
[exec] Line 13 Column 26 – cvc-complex-type.2.4.b: The content of element 'port-component-ref' is not complete. One of '

{"http://java.sun.com/xml/ns/javaee":service-endpoint-interface}

' is expected.
[exec] Jul 3, 2011 1:37:41 PM com.sun.enterprise.deployment.node.SaxParserHandler error
[exec] SEVERE: DPL8015: Invalid Deployment Descriptors in Deployment descriptor file META-INF/application-client.xml in archive [wss-taxcal-clientClient.jar].
[exec] Line 14 Column 26 – cvc-complex-type.2.4.b: The content of element 'port-component-ref' is not complete. One of '

{"http://java.sun.com/xml/ns/javaee":service-endpoint-interface}

' is expected.
[exec] Jul 3, 2011 1:37:41 PM com.sun.enterprise.deployment.ServiceReferenceDescriptor addRuntimePortInfo
[exec] WARNING: Runtime port info SEI null is not declared in standard service-ref deployment descriptors (under port-component-ref), is this intended ?
[exec] 0.CN=localhost, OU=GlassFish, O=Oracle Corporation, L=Santa Clara, ST=California, C=US
[exec] Jul 3, 2011 1:37:45 PM com.sun.xml.wss.impl.filter.DumpFilter process
[exec] INFO: ==== Sending Message Start ====
[exec] <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://tax.org/wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
[exec] <env:Header>
[exec] <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" env:mustUnderstand="1">
[exec] <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1309725462824-777498885">
[exec] <wsu:Created>2011-07-03T20:37:43Z</wsu:Created>
[exec] <wsu:Expires>2011-07-03T20:42:43Z</wsu:Expires>
[exec] </wsu:Timestamp>
[exec] <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="XWSSGID-13097254628631565534604">MIICcTCCAdqgAwIBAgIETg6YPzANBgkqhkiG9w0BAQQFADB9MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEUMBIGA1UEBxMLU2FudGEgQ2xhcmExGzAZBgNVBAoTEk9yYWNsZSBDb3Jwb3JhdGlvbjESMBAGA1UECxMJR2xhc3NGaXNoMRIwEAYDVQQDEwlsb
2NhbGhvc3QwHhcNMTEwNzAyMDQwMjA3WhcNMjEwNjI5MDQwMjA3WjB9MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEUMBIGA1UEBxMLU2FudGEgQ2xhcmExGzAZBgNVBAoTEk9yYWNsZSBDb3Jwb3JhdGlvbjESMBAGA1UECxMJR2xhc3NGaXNoMRIwEAYDVQQDEwlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKZyKmS6CkwBMzuLLNsl42EV5Y+B9H6zUdp9pFhG7UquChF4JVsgmDdj0FNUGrfq/BYrBJFiWna2mRtIPzswOFRLRwomtMuELVyHRfFQhismjX2p85yBTCYr2OOpG6t9lQHZocK8b0SqW65Mur2ZL4Op5zYVITc1f41iva/OlcpHAgMBAAEwDQYJKoZIhvcNAQEEBQADgYEAlPP1yvWJhvztwQxKHN4nOABuFz+u2ABQOOhaOkIyAlzfOEQtblaNajKGMIBwSoYVNDqroZ4SFxUNC0PvWVv/A4jnS4CMVSxlnUDEQmIqTrFayYXqv2UzaMso/Axsl14jzyOv6kHEIUebce0L1Lw0lU332JTWAhTZ624/0Ql8Vbc=</wsse:BinarySecurityToken>
[exec] <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="XWSSGID-1309725462863-1763461457">
[exec] <ds:SignedInfo>
[exec] <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
[exec] <InclusiveNamespaces xmlns="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="wsse enc env ns0 xsd xsi"/>
[exec] </ds:CanonicalizationMethod>
[exec] <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
[exec] <ds:Reference URI="#XWSSGID-1309725463553-869309864">
[exec] <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[exec] <ds:DigestValue>aPoqufNjuErl0oonWa9RfrFa0qo=</ds:DigestValue>
[exec] </ds:Reference>
[exec] <ds:Reference URI="#XWSSGID-1309725462824-777498885">
[exec] <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[exec] <ds:DigestValue>3K5jSLAEv0iIX6yhWqWdWU8ZW+U=</ds:DigestValue>
[exec] </ds:Reference>
[exec] </ds:SignedInfo>
[exec] <ds:SignatureValue>kGfwr0TBYbd6uZEYCppdt66iU2N1xNFzQdjt45Aze5OZigX7Itusu4Ad6Ni6DxKIsHr3L0JxS9E/
[exec] r+9JmNvMiMFe8ibzWG8sn7WelzSKKT/M/utxYCgW8fZ768BYgRe18fbY3vmnzD+46eWUqVqY3USY
[exec] 1uiXaOlGsZo0ZXDfw2I=</ds:SignatureValue>
[exec] <ds:KeyInfo>
[exec] <wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1309725463506-332222617">
[exec] <wsse:Reference URI="#XWSSGID-13097254628631565534604" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
[exec] </wsse:SecurityTokenReference>
[exec] </ds:KeyInfo>
[exec] </ds:Signature>
[exec] </wsse:Security>
[exec] </env:Header>
[exec] <env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1309725463553-869309864">
[exec] <ns0:getRunAsPrincipalNameSignature/>
[exec] </env:Body>
[exec] </env:Envelope>==== Sending Message End ====
[exec]
[exec] Jul 3, 2011 1:37:50 PM com.sun.xml.wss.impl.filter.DumpFilter process
[exec] INFO: ==== Received Message Start ====
[exec] <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://tax.org/wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
[exec] <env:Header>
[exec] <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" env:mustUnderstand="1">
[exec] <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1309725465508-1460142292">
[exec] <wsu:Created>2011-07-03T20:37:48Z</wsu:Created>
[exec] <wsu:Expires>2011-07-03T20:42:48Z</wsu:Expires>
[exec] </wsu:Timestamp>
[exec] <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="XWSSGID-1309725465508-1386807055">MIICcTCCAdqgAwIBAgIETg6YPzANBgkqhkiG9w0BAQQFADB9MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEUMBIGA1UEBxMLU2FudGEgQ2xhcmExGzAZBgNVBAoTEk9yYWNsZSBDb3Jwb3JhdGlvbjESMBAGA1UECxMJR2xhc3NGaXNoMRIwEAYDVQQDEwls
b2NhbGhvc3QwHhcNMTEwNzAyMDQwMjA3WhcNMjEwNjI5MDQwMjA3WjB9MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEUMBIGA1UEBxMLU2FudGEgQ2xhcmExGzAZBgNVBAoTEk9yYWNsZSBDb3Jwb3JhdGlvbjESMBAGA1UECxMJR2xhc3NGaXNoMRIwEAYDVQQDEwlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKZyKmS6CkwBMzuLLNsl42EV5Y+B9H6zUdp9pFhG7UquChF4JVsgmDdj0FNUGrfq/BYrBJFiWna2mRtIPzswOFRLRwomtMuELVyHRfFQhismjX2p85yBTCYr2OOpG6t9lQHZocK8b0SqW65Mur2ZL4Op5zYVITc1f41iva/OlcpHAgMBAAEwDQYJKoZIhvcNAQEEBQADgYEAlPP1yvWJhvztwQxKHN4nOABuFz+u2ABQOOhaOkIyAlzfOEQtblaNajKGMIBwSoYVNDqroZ4SFxUNC0PvWVv/A4jnS4CMVSxlnUDEQmIqTrFayYXqv2UzaMso/Axsl14jzyOv6kHEIUebce0L1Lw0lU332JTWAhTZ624/0Ql8Vbc=</wsse:BinarySecurityToken>
[exec] <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="XWSSGID-1309725465508-1894216289">
[exec] <ds:SignedInfo>
[exec] <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
[exec] <InclusiveNamespaces xmlns="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="wsse enc env ns0 xsd xsi"/>
[exec] </ds:CanonicalizationMethod>
[exec] <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
[exec] <ds:Reference URI="#XWSSGID-1309725468822-1878860834">
[exec] <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[exec] <ds:DigestValue>2HQZtBsNSV4PBh8/h6ZqX0w//C0=</ds:DigestValue>
[exec] </ds:Reference>
[exec] <ds:Reference URI="#XWSSGID-1309725465508-1460142292">
[exec] <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
[exec] <ds:DigestValue>kc0z/ZcNhkYX++ys1XZbI/HUFdo=</ds:DigestValue>
[exec] </ds:Reference>
[exec] </ds:SignedInfo>
[exec] <ds:SignatureValue>GTwxOYTnZY/T9sQB3i14O1E1p7PYEP3x0GYDaGFvprIgswv5fjqmjs//OqxMCunzN52gboet8tSR
[exec] 9r6eT3zsX8ZjOmDH2Nl/1VEWPhF3nRY6JngwRu6LM8PYiVWdlYgOlLcABMui9VYbLgwOdzP0n3r2
[exec] ztLodWT2m02NZX0MvA4=</ds:SignatureValue>
[exec] <ds:KeyInfo>
[exec] <wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1309725468814456765725">
[exec] <wsse:Reference URI="#XWSSGID-1309725465508-1386807055" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
[exec] </wsse:SecurityTokenReference>
[exec] </ds:KeyInfo>
[exec] </ds:Signature>
[exec] </wsse:Security>
[exec] </env:Header>
[exec] <env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1309725468822-1878860834">
[exec] <ns0:getRunAsPrincipalNameSignatureResponse>
[exec] <result xsi:type="xsd:string">CN=localhost, OU=GlassFish, O=Oracle Corporation, L=Santa Clara, ST=California, C=US</result>
[exec] </ns0:getRunAsPrincipalNameSignatureResponse>
[exec] </env:Body>
[exec] </env:Envelope>==== Received Message End ====
[exec]
[exec] Got:CN=localhost, OU=GlassFish, O=Oracle Corporation, L=Santa Clara, ST=California, C=US;Expected:CN=localhost, OU=GlassFish, O=Oracle Corporation, L=Santa Clara, ST=California, C=US
[exec] Jul 3, 2011 1:37:52 PM com.sun.xml.wss.impl.filter.DumpFilter process
[exec] INFO: ==== Sending Message Start ====
[exec] <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://tax.org/wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
[exec] <env:Header>
[exec] <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" env:mustUnderstand="1">
[exec] <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="XWSSGID-1309725462933-674196013">MIICcTCCAdqgAwIBAgIETg6YPzANBgkqhkiG9w0BAQQFADB9MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEUMBIGA1UEBxMLU2FudGEgQ2xhcmExGzAZBgNVBAoTEk9yYWNsZSBDb3Jwb3JhdGlvbjESMBAGA1UECxMJR2xhc3NGaXNoMRIwEAYDVQQDEwlsb
2NhbGhvc3QwHhcNMTEwNzAyMDQwMjA3WhcNMjEwNjI5MDQwMjA3WjB9MQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTEUMBIGA1UEBxMLU2FudGEgQ2xhcmExGzAZBgNVBAoTEk9yYWNsZSBDb3Jwb3JhdGlvbjESMBAGA1UECxMJR2xhc3NGaXNoMRIwEAYDVQQDEwlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAKZyKmS6CkwBMzuLLNsl42EV5Y+B9H6zUdp9pFhG7UquChF4JVsgmDdj0FNUGrfq/BYrBJFiWna2mRtIPzswOFRLRwomtMuELVyHRfFQhismjX2p85yBTCYr2OOpG6t9lQHZocK8b0SqW65Mur2ZL4Op5zYVITc1f41iva/OlcpHAgMBAAEwDQYJKoZIhvcNAQEEBQADgYEAlPP1yvWJhvztwQxKHN4nOABuFz+u2ABQOOhaOkIyAlzfOEQtblaNajKGMIBwSoYVNDqroZ4SFxUNC0PvWVv/A4jnS4CMVSxlnUDEQmIqTrFayYXqv2UzaMso/Axsl14jzyOv6kHEIUebce0L1Lw0lU332JTWAhTZ624/0Ql8Vbc=</wsse:BinarySecurityToken>
[exec] <xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="XWSSGID-1309725470236-1698110210">
[exec] <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/>
[exec] <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
[exec] <wsse:SecurityTokenReference>
[exec] <wsse:Reference URI="#XWSSGID-1309725462933-674196013" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
[exec] </wsse:SecurityTokenReference>
[exec] </ds:KeyInfo>
[exec] <xenc:CipherData>
[exec] <xenc:CipherValue>d8Ga6jzVttFEnrZMNCBIUsYauwmdEBBS/RNIlyDMtGCySSvOUxPUCJju8g18D1bHyl7muuTbQJTt
[exec] pugaj0WSRsogA+WM1mATFBDSHuealO0P5ZxEP/1DdhbXHeErVrXtF6gGdrj7TAxo7JHG6h59K+O4
[exec] rVdbs1pSYd/onfpgqKA=</xenc:CipherValue>
[exec] </xenc:CipherData>
[exec] </xenc:EncryptedKey>
[exec] <xenc:ReferenceList xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
[exec] <xenc:DataReference URI="#XWSSGID-1309725472383-1556823487"/>
[exec] </xenc:ReferenceList>
[exec] <wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="XWSSGID-1309725462934-1289127666">
[exec] <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="XWSSGID-1309725472383-1556823487" Type="http://www.w3.org/2001/04/xmlenc#Content">
[exec] <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
[exec] <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
[exec] <wsse:SecurityTokenReference>
[exec] <wsse:Reference URI="#XWSSGID-1309725470236-1698110210"/>
[exec] </wsse:SecurityTokenReference>
[exec] </ds:KeyInfo>
[exec] <xenc:CipherData>
[exec] <xenc:CipherValue>Q1/dXuJh7GdNU1yzng83YPGS7WdJCPwGyzp5z0eIrvFeR5SZA18ddYNdlssc8OiNn2NJw+coOOji
[exec] QFRZ6xe7K8qGI4LHs1G5Afuq8t5S6R7CWzvgcR7u85UYEVK7/FmEadjT6i5y0iJn3YYkvqe0cAsh
[exec] XhyJ0lIqycHvhEqy6TEhfB18pr9rZcCCWMvoHXi1Y2ymnVfp+kSUSLV8nCUiZ+HIomxN/B1MOXnr
[exec] u48+jVwT3nt1eGZ2SMzBbKf+BElw5OMR+YF6gvbXgfgUK2Dy+9/Hb5FsXn41iaLSHCQ5muo1UcdJ
[exec] zZmeXe6ZizcTjJlx9tzrtBbe336ObYW2k9oHvPlsr2D/GPH6+DVGGOOwNd/J3DzduHze6+c4stJS
[exec] QAky7wR8NOWmDQEY2seWB1IPzIxmA3mMWCF6hPVWOSbjW7PAWOCeiTwg6JBAgI1V1h2kM5rMLrrv
[exec] It1NGf3QnzpsjQ4IEQP09j6CObVN96KwmH0aUPl2YSpjNOMCv2UZJCV4ryraUIXrce/k2kqFlP05
[exec] 4jGYDHdN0kpNguN/4bEi4qhfXMHoOuJ1A0pMYDBqx8wiFuQAYr7V/B7EVBYJYTIH668I7Q+5P5ZX
[exec] qYqDN31mGQoE7hLtaw0hzs4DrOP2gKS4HzFSQWhQzdFEl7EJ+GURBgPuClsOVpKkKpOUgR+ojU3D
[exec] GCnNKqy20VTNTLtlmGQ2MmTkAMKezL8JkyIQxikpVD33fuzf3Rroi+NVbUIItSzalK39aDeQqjAB
[exec] srZLBa4ZrTmDucpXDbdUJjaqvfkHj5NNgcS7iGVWr+6lQeBmUfEpY7JtsYuKNKyWkyatGo2w</xenc:CipherValue>
[exec] </xenc:CipherData>
[exec] </xenc:EncryptedData>
[exec] </wsse:UsernameToken>
[exec] </wsse:Security>
[exec] </env:Header>
[exec] <env:Body>
[exec] <ns0:getRunAsPrincipalNameUsername/>
[exec] </env:Body>
[exec] </env:Envelope>==== Sending Message End ====
[exec]
[exec] Jul 3, 2011 1:37:57 PM com.sun.xml.wss.impl.filter.DumpFilter process
[exec] INFO: ==== Received Message Start ====
[exec] <?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
[exec] <env:Body>
[exec] <env:Fault>
[exec] <faultcode>env:Server</faultcode>
[exec] <faultstring>JAXRPCSERVLET28: Missing port information</faultstring>
[exec] </env:Fault>
[exec] </env:Body>
[exec] </env:Envelope>==== Received Message End ====
[exec]
[exec] Jul 3, 2011 1:37:57 PM com.sun.xml.wss.impl.SecurityRecipient processMessagePolicy
[exec] SEVERE: WSS0253: Message does not conform to configured policy: No Security Header found in message
[exec] com.sun.xml.wss.XWSSecurityException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.wss.impl.SecurityRecipient.processMessagePolicy(SecurityRecipient.java:818)
[exec] at com.sun.xml.wss.impl.SecurityRecipient.validateMessage(SecurityRecipient.java:261)
[exec] at com.sun.xml.wss.provider.ClientSecurityAuthModule.validateResponse(ClientSecurityAuthModule.java:156)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invokePriv(AuthContext.java:143)
[exec] at com.sun.enterprise.security.jauth.AuthContext$1.run(AuthContext.java:93)
[exec] at java.security.AccessController.doPrivileged(AccessController.java:251)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invoke(AuthContext.java:90)
[exec] at com.sun.enterprise.security.jauth.ConfigFile$ConfigClient.validateResponse(ConfigFile.java:619)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:281)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:263)
[exec] at com.sun.enterprise.security.webservices.MessageLayerClientHandler.handleResponse(MessageLayerClientHandler.java:167)
[exec] at com.sun.xml.rpc.client.HandlerChainImpl.handleResponse(HandlerChainImpl.java:131)
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:810)
[exec] at com.sun.xml.rpc.client.StreamingSender._preHandlingHook(StreamingSender.java:732)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.StateTaxIF_Stub._preHandlingHook(StateTaxIF_Stub.java:298)
[exec] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:124)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.StateTaxIF_Stub.getRunAsPrincipalNameUsername(StateTaxIF_Stub.java:69)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.testRunAsPrincipalNameUsername(TaxCalClient.java:101)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.main(TaxCalClient.java:63)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at org.glassfish.appclient.client.acc.AppClientContainer.launch(AppClientContainer.java:438)
[exec] at org.glassfish.appclient.client.AppClientFacade.launch(AppClientFacade.java:182)
[exec] at org.glassfish.appclient.client.AppClientGroupFacade.main(AppClientGroupFacade.java:65)
[exec] Jul 3, 2011 1:37:57 PM com.sun.enterprise.security.webservices.WebServiceSecurity validateResponse
[exec] SEVERE: Container-auth: wss: Error validating response
[exec] Throwable occurred: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.wss.provider.ClientSecurityAuthModule.validateResponse(ClientSecurityAuthModule.java:161)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invokePriv(AuthContext.java:143)
[exec] at com.sun.enterprise.security.jauth.AuthContext$1.run(AuthContext.java:93)
[exec] at java.security.AccessController.doPrivileged(AccessController.java:251)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invoke(AuthContext.java:90)
[exec] at com.sun.enterprise.security.jauth.ConfigFile$ConfigClient.validateResponse(ConfigFile.java:619)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:281)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:263)
[exec] at com.sun.enterprise.security.webservices.MessageLayerClientHandler.handleResponse(MessageLayerClientHandler.java:167)
[exec] at com.sun.xml.rpc.client.HandlerChainImpl.handleResponse(HandlerChainImpl.java:131)
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:810)
[exec] at com.sun.xml.rpc.client.StreamingSender._preHandlingHook(StreamingSender.java:732)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.StateTaxIF_Stub._preHandlingHook(StateTaxIF_Stub.java:298)
[exec] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:124)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.StateTaxIF_Stub.getRunAsPrincipalNameUsername(StateTaxIF_Stub.java:69)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.testRunAsPrincipalNameUsername(TaxCalClient.java:101)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.main(TaxCalClient.java:63)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at org.glassfish.appclient.client.acc.AppClientContainer.launch(AppClientContainer.java:438)
[exec] at org.glassfish.appclient.client.AppClientFacade.launch(AppClientFacade.java:182)
[exec] at org.glassfish.appclient.client.AppClientGroupFacade.main(AppClientGroupFacade.java:65)
[exec] Jul 3, 2011 1:37:57 PM com.sun.enterprise.security.webservices.MessageLayerClientHandler handleResponse
[exec] WARNING: SEC2005: Container-auth: wss: Error validating response
[exec] Throwable occurred: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.wss.provider.ClientSecurityAuthModule.validateResponse(ClientSecurityAuthModule.java:161)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invokePriv(AuthContext.java:143)
[exec] at com.sun.enterprise.security.jauth.AuthContext$1.run(AuthContext.java:93)
[exec] at java.security.AccessController.doPrivileged(AccessController.java:251)
[exec] at com.sun.enterprise.security.jauth.AuthContext.invoke(AuthContext.java:90)
[exec] at com.sun.enterprise.security.jauth.ConfigFile$ConfigClient.validateResponse(ConfigFile.java:619)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:281)
[exec] at com.sun.enterprise.security.webservices.WebServiceSecurity.validateResponse(WebServiceSecurity.java:263)
[exec] at com.sun.enterprise.security.webservices.MessageLayerClientHandler.handleResponse(MessageLayerClientHandler.java:167)
[exec] at com.sun.xml.rpc.client.HandlerChainImpl.handleResponse(HandlerChainImpl.java:131)
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:810)
[exec] at com.sun.xml.rpc.client.StreamingSender._preHandlingHook(StreamingSender.java:732)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.StateTaxIF_Stub._preHandlingHook(StateTaxIF_Stub.java:298)
[exec] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:124)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.StateTaxIF_Stub.getRunAsPrincipalNameUsername(StateTaxIF_Stub.java:69)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.testRunAsPrincipalNameUsername(TaxCalClient.java:101)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.main(TaxCalClient.java:63)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at org.glassfish.appclient.client.acc.AppClientContainer.launch(AppClientContainer.java:438)
[exec] at org.glassfish.appclient.client.AppClientFacade.launch(AppClientFacade.java:182)
[exec] at org.glassfish.appclient.client.AppClientGroupFacade.main(AppClientGroupFacade.java:65)
[exec] java.rmi.RemoteException: response handler error: ; nested exception is:
[exec] javax.xml.rpc.JAXRPCException: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:812)
[exec] at com.sun.xml.rpc.client.StreamingSender._preHandlingHook(StreamingSender.java:732)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.StateTaxIF_Stub._preHandlingHook(StateTaxIF_Stub.java:298)
[exec] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:124)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.StateTaxIF_Stub.getRunAsPrincipalNameUsername(StateTaxIF_Stub.java:69)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.testRunAsPrincipalNameUsername(TaxCalClient.java:101)
[exec] at com.sun.appserv.sqe.security.wss.servletws.taxcal.client.TaxCalClient.main(TaxCalClient.java:63)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
[exec] at java.lang.reflect.Method.invoke(Method.java:611)
[exec] at org.glassfish.appclient.client.acc.AppClientContainer.launch(AppClientContainer.java:438)
[exec] Checking runas principal for username failed with unknown exception
[exec] at org.glassfish.appclient.client.AppClientFacade.launch(AppClientFacade.java:182)
[exec] at org.glassfish.appclient.client.AppClientGroupFacade.main(AppClientGroupFacade.java:65)
[exec] Caused by: javax.xml.rpc.JAXRPCException: com.sun.enterprise.security.jauth.AuthException: Message does not conform to configured policy [ TimestampPolicy(S) SignaturePolicy(P) ]: No Security Header found
[exec] at com.sun.enterprise.security.webservices.MessageLayerClientHandler.handleResponse(MessageLayerClientHandler.java:172)
[exec] at com.sun.xml.rpc.client.HandlerChainImpl.handleResponse(HandlerChainImpl.java:131)
[exec] at com.sun.xml.rpc.client.StreamingSender._callResponseHandlers(StreamingSender.java:810)
[exec] ... 13 more
[exec] Generating report at /export/hudson/workspace/sherry-aix-311-security/appserver-sqe/test_results.xml
[exec]
[exec]
[exec] -----------------------------------------
[exec] - Sec::wss_servletws-runas-principal-mls-signature: PASS -
[exec] - Sec::wss_servletws-runas-principal-mls-usernametoken: FAIL -
[exec] -----------------------------------------
[exec] Total PASS: 1
[exec] Total FAIL: 1
[exec] Total DNR: 0
[exec] -----------------------------------------

Comment by kumarjayanti [ 07/Jul/11 ]

With latest AIX b10 the error seems to be only in the DUMPING of the messages enabled by the debug property of the SAM.

An AIX specific error is occuring when doing a JAXP Transform.

So the testcase should pass if debug property in the SAM configuration is removed.

Here is the error on the server.log. I have asked the ClassLoader experts on what the problem could be.

-------------------
[#|2011-07-03T14:30:55.536-0700|WARNING|glassfish3.1.1|javax.enterprise.system.cor
e.classloading.com.sun.enterprise.loader|_ThreadID=12;_ThreadName=Thread-9;|Input
stream has been finalized or forced closed without being explicitly closed; stream
instantiation reported in following stack trace
java.lang.Throwable
at com.sun.enterprise.loader.ASURLClassLoader$SentinelInputStream.<init>(A
SURLClassLoader.java:1230)
at com.sun.enterprise.loader.ASURLClassLoader.getResourceAsStream(ASURLCla
ssLoader.java:878)
at org.glassfish.web.loader.WebappClassLoader.getResourceAsStream(WebappCl
assLoader.java:1252)
at com.ibm.xtq.xslt.drivers.SecuritySupport$6.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:202)
at com.ibm.xtq.xslt.drivers.SecuritySupport.getResourceAsStream(Unknown So
urce)
at com.ibm.xtq.xslt.drivers.XylemRuntimePreCompiler.getResource(Unknown So
urce)
at com.ibm.xtq.xslt.drivers.XylemRuntimePreCompiler.getPrecompiledRuntime(
Unknown Source)
at com.ibm.xtq.xslt.drivers.XSLTCompiler.compileRuntime10(Unknown Source)
at com.ibm.xtq.xslt.drivers.XSLTCompiler.compileRuntime(Unknown Source)
at com.ibm.xtq.xslt.drivers.XSLTCompiler.compile(Unknown Source)
at com.ibm.xtq.xslt.jaxp.compiler.TransformerFactoryImpl.createTemplates(U
nknown Source)
at com.ibm.xtq.xslt.jaxp.AbstractTransformerFactory.newTemplates(Unknown S
ource)
at com.sun.xml.wss.impl.filter.TeeFilter.init(TeeFilter.java:164)

This issue should no longer be a release stopper for AIX.

Comment by kumarjayanti [ 08/Jul/11 ]

Adding comments from ClassLoader experts :

Tim Quinn Wrote :
---------------

Sahoo is correct; a stream has been opened but never closed by the code which opened it.

From a quick look at the stack trace, the stream is opened (as a side effect of classLoader.getResourceAsStream) from com.ibm.xtq.xslt.drivers.XylemRuntimePreCompiler, so presumably any fix would need to be there.

  • Tim

On Jul 7, 2011, at 5:45 AM, Sahoo wrote:

Hi Kumar,

That indicates that some of the streams referring to resources returned by this class loader were still open, but there is no reference to those streams in code so finalizer is getting called. It further means there is some bad code somewhere which is not calling InputStream.close(). If this can be isolated, then one has to instrument the code to detect the bad code and fix it. btrace can be excellent option to debug such issues. Copying Tim for any additional input he may have, as he has dealt with such issues in the past and IIRC has introduced this error detection logic in ASURLClassLoader.

HTH,
Sahoo

On Thursday 07 July 2011 12:58 PM, Kumar Jayanti wrote:
Hi Shaoo, Siva,

There is a problem happening on AIX with Metro Security SQE runs. Just wanted to know if you have any idea/hints on what is wrong.

-------------------
[#|2011-07-03T14:30:55.536-0700|WARNING|glassfish3.1.1|javax.enterprise.system.cor
e.classloading.com.sun.enterprise.loader|_ThreadID=12;_ThreadName=Thread-9;|Input
stream has been finalized or forced closed without being explicitly closed; stream
instantiation reported in following stack trace
java.lang.Throwable
at com.sun.enterprise.loader.ASURLClassLoader$SentinelInputStream.<init>(A
SURLClassLoader.java:1230)
at com.sun.enterprise.loader.ASURLClassLoader.getResourceAsStream(ASURLCla
ssLoader.java:878)
at org.glassfish.web.loader.WebappClassLoader.getResourceAsStream(WebappCl
assLoader.java:1252)
at com.ibm.xtq.xslt.drivers.SecuritySupport$6.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:202)
at com.ibm.xtq.xslt.drivers.SecuritySupport.getResourceAsStream(Unknown So
urce)
at com.ibm.xtq.xslt.drivers.XylemRuntimePreCompiler.getResource(Unknown So
urce)
at com.ibm.xtq.xslt.drivers.XylemRuntimePreCompiler.getPrecompiledRuntime(
Unknown Source)
at com.ibm.xtq.xslt.drivers.XSLTCompiler.compileRuntime10(Unknown Source)
at com.ibm.xtq.xslt.drivers.XSLTCompiler.compileRuntime(Unknown Source)
at com.ibm.xtq.xslt.drivers.XSLTCompiler.compile(Unknown Source)
at com.ibm.xtq.xslt.jaxp.compiler.TransformerFactoryImpl.createTemplates(U
nknown Source)
at com.ibm.xtq.xslt.jaxp.AbstractTransformerFactory.newTemplates(Unknown S
ource)
at com.sun.xml.wss.impl.filter.TeeFilter.init(TeeFilter.java:164)
----------------------

regards,
kumar

Comment by kumarjayanti [ 08/Jul/11 ]

Dowgrading the bug since it is only an exception during debug. I am also trying to remove some dependence on Apache Xerces which might help remove this exception (need to verify still). The change will require a new Metro Integration

Comment by Alex Pineda [ 14/Jul/11 ]

Are there plans to integrate this fix and a new Metro version in Glassfish (final GF 3.1.1) build? Need to know to plan the testing appropriately.

Comment by kumarjayanti [ 14/Jul/11 ]

Martin G had a discussion with Sathyan and it seems we are not going to integrate now.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16491] [UB]Additional Instructions for setting up LB on OEL+ OHS 64-bit to be included Created: 27/Apr/11  Updated: 07/Mar/12

Status: In Progress
Project: glassfish
Component/s: docs, load_balancer
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Jothir Ganesan Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OEL + OHS 64-bit + Glassfish lb plugin


Issue Links:
Related
is related to GLASSFISH-17806 [UB]Docs need to be corrected to refl... Open
Tags: 3_1-next_need-more-info

 Description   

I configured lb plugin on 64-bit OHS according to the instructions given in
http://download.oracle.com/docs/cd/E18930_01/html/821-2426/gktke.html

When I start OHS, the https listeners of the instances are being detected as unhealthy.

Need to add the following to bin/apachectl script:
NSS_STRICT_NOFORK=DISABLED; export NSS_STRICT_NOFORK



 Comments   
Comment by Scott Fordin [ 18/May/11 ]

We clearly state at the beginning of "Configuring Web Servers for HTTP Load Balancing" chapter in the HA Admin Guide that, "The Loadbalancer Plug-In does not support web servers running in 64–bit mode, except for Microsoft IIS with 32–bit application support enabled." We also state in the "Configuring Oracle HTTP Server" instructions in that same chapter that, "These procedures apply to Oracle HTTP Server 11.1.1.4+ (32–bit) only. Other versions of Oracle HTTP Server are not supported." So I guess I'm confused. Do we now want to say that we support 64-bit? If so, this will require changes in several locations, not just this one bit in one particular step.

Comment by Scott Fordin [ 31/May/11 ]

Reassigning to Paul Davies.

Comment by kshitiz_saxena [ 14/Jul/11 ]

This issue is not specific to 64 bit OHS. This change is generic. Please capture is under point 3.

Comment by Mike Fitch [ 19/Jul/11 ]

Information added as per Description

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16490] [UB]Additional Instructions for setting up LB on Solaris 10 Sparc + apache 64-bit to be included Created: 27/Apr/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs, load_balancer
Affects Version/s: 3.1.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Jothir Ganesan Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris 10 Sparc + Apache 64-bit with OpenSSl


Issue Links:
Related
is related to GLASSFISH-17806 [UB]Docs need to be corrected to refl... Open
Tags: 3_1-next_need-more-info

 Description   

Configure openssl as below :
1. ./Configure shared --openssldir=<openssl-install-dir> --prefix=<openssl-install-dir> solaris64-sparcv9-cc
2. make
3. make install

Configure Apache as below:
export CFLAGS="-m64"
export LDFLAGS="-m64"
export LD_LIBRARY_PATH=/usr/lib/64:/usr/sfw/lib/64
use sun studio compiler instead of gcc for 64-bit:
1../configure --with-mpm=worker --with-included-apr --with-ssl=/export/kshitiz/64bit/openssl/install --prefix=/export/kshitiz/64bit/apache2.2/install --enable-ssl --enable-so CC=/usr/dist/share/sunstudio_sparc/SUNWspro/bin/cc

2. make
3. make install



 Comments   
Comment by Scott Fordin [ 18/May/11 ]

Similar comment to http://java.net/jira/browse/GLASSFISH-16491, we clearly state at the beginning of "Configuring Web Servers for HTTP Load Balancing" chapter in the HA Admin Guide that, "The Loadbalancer Plug-In does not support web servers running in 64–bit mode, except for Microsoft IIS with 32–bit application support enabled." We also state in the "Configuring Apache HTTP Server" instructions in that same chapter that, "The Loadbalancer Plug-In supports Apache HTTP Server 2.2.x (32–bit)." So I guess I'm confused. Do we now want to say that we support 64-bit? If so, this will require changes in several locations, not just this one bit in one particular step.

Comment by Scott Fordin [ 31/May/11 ]

Reassigning to Paul Davies.

Comment by kshitiz_saxena [ 14/Jul/11 ]

In 3.1.1, we support 64 bit load-balancer plugin. Please refer to issue GLASSFISH-16905.

Comment by Mike Fitch [ 19/Jul/11 ]

Pushing this issue to "future release". For 3.1.1, description of 64-bit LBP support is limited to the Release Notes.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16413] Administrators shall be able to configure a GMS group discovery mechanism for a site. Created: 21/Apr/11  Updated: 17/Oct/12

Status: Open
Project: glassfish
Component/s: group_management_service
Affects Version/s: 4.0
Fix Version/s: not determined

Type: New Feature Priority: Critical
Reporter: Bobby Bissett Assignee: Joe Fialli
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_2prd

 Description   

Mechanism is used to enable a GMS cluster when UDP multicast is unavailable between clustered instances.
Provide CLI to install a group discovery service as an OS service at a Well Known Address.
Provide CLI to configure VM template to reference a site-wide group discovery mechanism.
Provide CLI to configure S3-based group discovery.
(See GLASSFISH-3636 for issue that GMS requires UDP multicast.)



 Comments   
Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by Bobby Bissett [ 07/Dec/11 ]

Moving to Joe since I'm no longer on project.





[GLASSFISH-16355] startup and footprint of larger size application deployment to 3.x Created: 14/Apr/11  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: performance
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Critical
Reporter: Nazrul Assignee: Scott Oaks
Resolution: Unresolved Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-16543 Performance regression in JavaEE (ejb... Open
depends on GLASSFISH-17044 [PERF] gmbal objects consuming large ... Open
depends on GLASSFISH-16540 it takes a long time to boostrap EJB ... Resolved
depends on GLASSFISH-16460 Performance regression in server startup Resolved
depends on GLASSFISH-16747 Excessive memory requirements in EJB app Resolved
depends on GRIZZLY-1144 SocketChannelOutputBuffer consumes to... Resolved
depends on GLASSFISH-17914 Don't initialize StatsProviderRegistr... Closed
Tags: 3_1-next, 3_1_1-scrubbed, 3_1_2-exclude

 Description   

Refer to this blog for description of the problem: http://ktschmidt.blogspot.com/2011/04/is-glassfish-v3-slower-and-bigger.html

Scott Oaks confirmed that the startup time issue is valid.

Also refer to this forum thread: http://forums.java.net/node/798503



 Comments   
Comment by Hong Zhang [ 15/Apr/11 ]

Assign the umbrella issue to Tom. The deployment could have a sub issue of the umbrella issue.

Comment by Tom Mueller [ 15/Apr/11 ]

Not sure why this is an admin issue. Assigning it to performance.

Comment by Nazrul [ 15/Apr/11 ]

Adding 3_1-next tag. We need a fix for this during 3.1.1.

Comment by Tim Quinn [ 09/Jun/11 ]

Linking the apparent MQ start-up regression to this more-or-less umbrella issue.

Comment by Scott Oaks [ 13/Jul/11 ]

Remaining different in heap usage after startup is attributable to retained gmbal-related references.

Comment by Scott Oaks [ 22/Nov/11 ]

We are tracking a new set of tests for this in 3.1.2.

In this set of tests (which includes one large app with multiple jars and wars, including EJBs, JSPs, MDB, etc., and one smaller web app), the heap after starting with the apps deployed in 2.1.1 consumes 41.2MB; in 3.1.2 it consumes 59.7MB. This is before an ORB is started, and hence does not include the gmbal-related references. [So that earlier comment about everything being related to gmbal is in error.] There is no load generated in this test, so lazily-initialized things will benefit the test, which may or may not be a good thing (but it follows the scenario in the posting that drives this bug).

Where does that 18.5MB come from? Here is the short answer:
Additional classes: 4MB
HK2: 4MB
Felix: 5MB
Grizzly: 3MB
Stats Provider: 2MB

In a scenario like this where a significant part of the EE modules are loaded, one place we lose out is in the infrastructure for modularization. In simple terms of classes loaded, 3.1.2 is loading 11% more classes (10K vs 9K), and the class objects themselves consume 50% more heap (12M vs 8M). That is a reflection of the added features as well as the added modularization, of course.

Then there is the memory consumed by instances of the classes. The single instance of org.jvnet.jk2.component.Habitat consumes 1.6MB of heap. However, there are are other habitats (subclasses) as well, and they are consuming at least another 1.2MB of heap (for their MultiMap) and a significant amount of memory for the LazyInhabitant objects. Total consumed by HK2 is in excess of 3.9MB.

Instances of Felix classes consume at least 4MB of heap (not including the classes held by the Felix ModuleClassLoader). The big amounts of memory there are held by Felix ModuleImpls (again not including the inner classloader objects); memory here is consumed by CapabilityImpl, RequirementImpl, and ResolverState. I realize there is overlap between some of those classes, but the 4MB calculation in the tool will have removed that overlap, and in particular the 1.2MB of heap consumed by ResolverState appears independent of the CapabilityImpl/RequirementImpl. So without understanding the code better, I can just say that it heap usage is between 4 and 5.2MB (or bigger).

Grizzly processorTasks consume 3.1MB more heap.
In 2.1.1, the three processor tasks queues consume 2.25MB of heap
In 3.1.2, the there five processor tasks queues consuming 5.3MB of heap
This is a default-configured domain

Stats Provider Registry consumes 2MB of heap

Comment by Scott Oaks [ 23/Nov/11 ]

The extra classes contribute as well to the regression in the time to restart the server: they cause a few expansions of the perm gen as it fills up with the extra classes.

In 2.1.1, a server restart with the EJB apps deployed goes through one resizing of permgen on my laptop; in 3.1.2, there are three or four. If we increase the initial size of perm gen (keeping the max size at 192m), we can improve the server restart in this scenario by 11%. But that will affect the footprint of other smaller deployments, so some discussion on the trade-offs here needs to occur.

Comment by Joe Di Pol [ 18/Jan/12 ]

We won't be making any more progress on this for 3.1.2 so I'm excluding from the release. We did get a gmbal fix into Metro that helps WS applications, but not EJB. The ORB fix has proven more difficult (see linked gmbal bug).

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16166] [UB]GlassFish Admin Guide should document use of GenericJMSRA with Message Queue Created: 07/Mar/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Nigel Deakin Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The GlassFish 3.1 Administration Guide does not describe how to use the Generic Resource Adapter for JMS (GenericJMSRA) to connect to GlassFish Message Queue, even though this is supported.

The only documentation for GenericJMSRA is a section
"Using the Generic Resource Adapter for JMS to Integrate Supported External JMS Providers"
http://download.oracle.com/docs/cd/E18930_01/html/821-2416/gbtvg.html

This describes GenericJMSRA generically and then gives detailed configuration information for WebLogic JMS and IBM WebSphere MQ. However there is no equivalent section for GlassFish Message Queue.

Such a section should mention that when using GlassFish Message Queue, both jndi and javabean integration modes are supported, and what settings are needed in the two cases.



 Comments   
Comment by Mike Fitch [ 19/Jul/11 ]

Setting Fix Version to "future release", as the scope of 3.1.1 is limited to bug fixes, and this is issue requests additional content, not corrections to existing content.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16095] [UB]Doc: Update Tool section in Admin Guide needs to be improved. Created: 24/Feb/11  Updated: 07/Mar/12

Status: Open
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Chris Kasso Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

In the GF Admin Guide there is a section titled:

Tools for Extending and Updating GlassFish Server

This section needs:

1) An introduction to Update Center and then a breakdown of the tools which are available. That includes updatetool, software update/notifier and the pkg command.
2) A section that discusses the various GF repositories which are available and how to access packages on those repositories. This may include discussing how to change the preferred repository for a GF installation.
3) How to enable/disable the notifier post installation.



 Comments   
Comment by Paul Davies [ 03/Mar/11 ]

A conscious decision was taken not to replicate in the GlassFish Server documentation information that is available elsewhere. For example, the GlassFish Server documentation should not replicate information that is provided in the Update Tool online help. This decision was taken when Update Center was still independent of GlassFish Server.

WRT item 1) The cited section already provides a breakdown of the tools that are of interest to the system administrator (see http://download.oracle.com/docs/cd/E18930_01/html/821-2416/gkcbv.html#gkcba ). Now that the sole reason for Update Center's existence is GlassFish, there might be value in adding some of the content in the cross-referenced wikis to the GlassFish documentation.

WRT item 2) This information is already provided in Preconfigured Repositories for GlassFish Server (http://download.oracle.com/docs/cd/E18930_01/html/821-2416/gjzko.html )

WRT item 3) Now that the sole reason for Update Center's existence is GlassFish, there might be value in adding this information to the GlassFish documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16063] Can't find resource for bundle java.util.PropertyResourceBundle, key xfmgr.errTransTags Created: 21/Feb/11  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: None
Affects Version/s: 3.1_b42
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: jbenoit Assignee: Nazrul
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Seeing SEVERE message in server.log, can't find resource for bundle when looking for key xfmgr.errTransTags:

Feb 21, 2011 2:15:51 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 16 msec.
[#|2011-02-21T02:16:01.710+0000|INFO|glassfish3.1|null|_ThreadID=1;_ThreadName=Thread-1;|Running GlassFish Version: GlassFish Server Open Source Edition 3.1-SNAPSHOT (build 42)|#]
[snip]
[#|2011-02-21T02:19:44.473+0000|SEVERE|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=76;_ThreadName=Thread-1;|Exception in thread "registration" |#]

[#|2011-02-21T02:19:44.476+0000|SEVERE|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=76;_ThreadName=Thread-1;|java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key xfmgr.errTransTags
at java.util.ResourceBundle.getObject(ResourceBundle.java:374)
at java.util.ResourceBundle.getString(ResourceBundle.java:334)
at com.sun.enterprise.registration.impl.StringManager.getString(StringManager.java:64)
at com.sun.enterprise.registration.impl.SysnetTransferManager.transferServiceTags(SysnetTransferManager.java:118)
at com.sun.enterprise.registration.impl.SysnetRegistrationService.transferEligibleServiceTagsToSysNet(SysnetRegistrationService.java:153)
at com.sun.enterprise.registration.glassfish.TransferService$1.run(TransferService.java:85)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

#]


 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-16045] [UB]tx rollback/recover examples with --target Created: 18/Feb/11  Updated: 28/Aug/12

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: sherryshen Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris, Linux



 Description   

Administration Guide
Chapter 18, Administering Transactions
I provided a few examples of rollback/recover with --target as a reference.
Thanks for the consideration.

By the way, I also verified 6 doc bugs filed from my tests and
filed this p4 bug to track my review.



 Comments   
Comment by sherryshen [ 18/Feb/11 ]

Review of GFv3.1 tx docs
Updated on Feb. 17, 2011 by sherry.hill

1) rollback example with --target for a clustered instance
2) recovery example with --target for a clustered instance
3) verified the 6 doc bugs filed from my tests.
1) rollback example with --target for a clustered instance
transactions-ag.pdf
page 25 Managing the Transaction Service for Rollbacks
Examples are given for das so that no --target is used.
Here is another example for a clustered instance with the use of --target from my tests for reference.

% asadmin freeze-transaction-service --target clustered_instance_2
Command freeze-transaction-service executed successfully.
%

% asadmin get --monitor=true clustered_instance_2.transaction-service.activeids-current
clustered_instance_2:
clustered_instance_2.transaction-service.activeids-current =
Transaction Id Status ElapsedTime(ms) ComponentName ResourceNames
030000008A0A552A6A65642D617371652D32322C636C757374657265645F696E7374616E63655F322C503433373030 Active 7835 txn.recovery.cliweb2.MyBean jdbc/cliweb2DB1
%

% asadmin rollback-transaction --target clustered_instance_2 --transaction_id 030000008A0A552A6A65642D617371652D32322C636C757374657265645F696E7374616E63655F322C503433373030
Command rollback-transaction executed successfully.
%

% asadmin unfreeze-transaction-service --target clustered_instance_2
Command unfreeze-transaction-service executed successfully.
%

The details can be found in
http://agni-1.us.oracle.com/net/asqe-logs/export1/v3.1/Results/build43/core/clu_oel/amd64/output/txn_recovery_cliweb.output

2) recovery example with --target
transactions-ag.pdf
Page 29, "To Manually Recover Transaction" with 2.2, but without 2.1.
2.1) Example of admincli recover-transactions for delegated recovery
If an application server instance (e.g. clustered_instance_2) fails transactions,
the transaction of that instance is picked up by the other running instance (e.g. clustered_instance_1).
% asadmin recover-transactions --target clustered_instance_1 --transactionlogdir /txlog/clustered_instance_2/tx clustered_instance_2
Command recover-transactions executed successfully.
%

2.2) Example of admincli recover-transactions for self recovery
If a recourse such as a database server fails transactions, the transaction of that instance is recovered by this instance after the database is restarted.
% asadmin recover-transactions clustered_instance_2
Command recover-transactions executed successfully.
%
The details can be found in
http://agni-1.us.oracle.com/net/asqe-logs/export1/v3.1/Results/build43/core/clu_oel/amd64/output/txn_recovery_cliweb.output

3) verified the 6 doc bugs filed from my tests.
3.1) verified the fix in docs.
Administration Guide
Chapter 18, Administering Transactions
Oracle Setup for Transaction Recovery
http://java.net/jira/browse/GLASSFISH-13837 Oracle Setup
http://java.net/jira/browse/GLASSFISH-15561 Oracle Setup

3.2) verified the fix in docs.
Administration Guide
Chapter 18, Administering Transactions
General Recovery Limitations
http://java.net/jira/browse/GLASSFISH-14750 JMS Embedded
http://java.net/jira/browse/GLASSFISH-13818 Expectation of recovery
http://java.net/jira/browse/GLASSFISH-14086 MYSQL

3.3) verified the fix in docs.
Administration Guide
Chapter 18, Administering Transactions
Transaction Logging
http://java.net/jira/browse/GLASSFISH-13527 UID

(removed e-mail address)

Comment by sherryshen [ 18/Feb/11 ]

I will use this bug to add another point in review.
4) about connection validation for recover transaction.
transactions-ag.pdf
To Manually Recover Transaction

  • "Connection validation should be enabled so that the connecton pool is refreshed when the resource is accessed after the recovery".

Any example how to enable connection validation?

http://java.net/jira/browse/GLASSFISH-13818
It gives an error for incorrect validation setting, i.e.
[#|2010-10-06T09:34:39.358-0700|INFO|glassfish3.1|javax.enterprise.resource.resourceadapter.com.sun.gjc.spi|
_ThreadID=15;_ThreadName=Thread-1;|RAR5074 : Table based validation detected
invalid connection.
Querying the table sys.systables failed. Set resource-adapter log-level to FINE
for exception stack trace. |#]

I made a note in the test spec with the examples of validation setting.
http://agni-1.us.oracle.com/asqe-logs/export1/v3.1/docs/sqe/txn/GF31TXRecoveryTestSpec.html

  • 13818, JDBC resources are configured with validation setting
    o asadmin set resources.jdbc-connection-pool.<jdbc_pool_name>.is-connection-validation-required=true
    o asadmin set resources.jdbc-connection-pool.<jdbc_pool_name>.validation-table-name=<table_name>
    o asadmin set resources.jdbc-connection-pool.<jdbc_pool_name>.connection-validation-method=table
    o The <table_name> can be database system table or user created table, which must be different from the table used for rollback/recover-transactions.
    o The following system tables can be used, sys.systables for Derby, DUAL for oracle, dual for MySQL.

I hope that this examples can be adopted to docs if there are not in yet.

Comment by Rebecca Parks [ 23/Feb/11 ]

Changed Fix Version to 3.2. Bundled docs are frozen for 3.1.

Comment by Rebecca Parks [ 12/May/11 ]

I have addressed most of this issue in the 3.1.1 Administration Guide's transactions chapter. To address the connection validation aspect, however, is in the JDBC area, not the transactions area. There is nothing about setting up connection validation in the JDBC chapter of the Admin Guide, but there should be. After this section is added, I can change the link in the transaction recovery section to point to it.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-16005] cannot configure ssl key-/trust-store per http-listener in admin-gui Created: 16/Feb/11  Updated: 27/Mar/13

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: 3.1_b43
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: schaarsc Assignee: JeffTancill
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-next, 3_1_1-exclude, 3_1_1-scrubbed

 Description   

according to GLASSFISH-15973 the per listener configuration does not work with GlassfishSSLImpl and classname needs to be removed from ssl-element. There is no field to choose classname in admin-gui.

I think that admin-gui is the wrong place to fix this, I my opinion GlassfishSSLImpl should do the job and not the user.

Hint: you might not notice the problem if you use nickname=s1as, because then the cert from -Djavax.net.ssl.keystore is used. If you change the nickname you'll get "No available certificate" exception until you remove classname, but then you'll have to add key-store-password to ssl-element



 Comments   
Comment by Anissa Lam [ 16/Feb/11 ]

After reading the comments from GLASSFISH-15973, I am still not sure how exactly GUI should change to provide better user experience.
Request Kumar to tell me what exactly GUI should do. There seems to be discrepancy of what the user prefers to see and what Kumar believes is working by design.

I am transferring this to 'security' for input. Please tell me clearly what fields should be added/modified. thanks.

Comment by schaarsc [ 16/Feb/11 ]

Preferred solution:

  • do not change admin-gui
  • make GlassfishSSLImpl aware of key-store and trust-store attributes

if GlassfishSSLImpl cannot be changed:

  • add classname to gui
  • add key-store-password to gui
  • add trust-store-password to gui
  • add documentation what these values are good for and why / when they need to be specified
Comment by schaarsc [ 16/Feb/11 ]

I noticed that you downgraded this issue to Improvement.
I thinks it's a bug, because if you enter keystore and truststore in the admin-gui it will not do what user expects and there is no way to fix it using admin-gui. domain.xml has to be edited directly.

Comment by Nazrul [ 10/May/11 ]

Lets take a look at this issue

Comment by scatari [ 25/Jun/11 ]

Marking to be considered for next release.





[GLASSFISH-15713] [UB]Non-sticky Load Balancer not supported in GlassFish HA Created: 27/Jan/11  Updated: 07/Mar/12

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1_b39
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Rajiv Mordani Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-approved, 3_1-need_more_info

 Description   

Need to document that when GlassFish is front ended with a non sticky load balancer HA is not supported. It may result in some data loss. Please see bug
http://java.net/jira/browse/GLASSFISH-15575



 Comments   
Comment by Paul Davies [ 27/Jan/11 ]

Reassigned to sfordin. Corrected typo in tag.

Comment by Scott Fordin [ 11/Feb/11 ]

With all the back-and-forth in the comments on this issue, it is unclear to me what actually needs to be said in the docs here, and even in which doc this issue would be most appropriately discussed. Can someone please advise me here?

Comment by Scott Fordin [ 17/Mar/11 ]

Second request: I still need more information to document this issue. It is not clear to me what needs to be said here and where it needs to be said. Can someone please advise?

Comment by Scott Fordin [ 31/May/11 ]

Reassigning to Paul Davies.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-15698] Need clear Error message while creating JDBC connection pool in Admin Console. Created: 26/Jan/11  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1_b39
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: shaline Assignee: sumasri
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Solaris Sparc 10
browser : firefox 3.6



 Description   

GF build used : nightly dated b39-01-25-11
When we create a JDBC connection Pool, if we do not specify any value in the Additional properties for the particular DB vendor, and click the finish button. The pool gets created, but when we select the created pool, and click the "Advanced" tab an error or an exception is thrown, which is not very clear to User what went wrong. Error message needs to be clear.
Steps:
Create Derby Pool, by selecting javax.sql.Datasource, and Derby DB.
Select default and click finish button. ( DO Not specify anything in the additional properties window).
Select the created pool, and click the "Advanced" tab. See the below Error , which is not very clear.
,

An error has occurred

_get-validation-table-names failed : javax.resource.spi.SecurityException: No PasswordCredential found

For Oracle DB, with the same above steps, the below Exception shows up,, since we did not add any additional properties.

An error has occurred
_get-validation-table-names failed : javax.resource.spi.ResourceAllocationException: Connection could not be allocated because: Invalid Oracle URL specified: OracleDataSource.makeURL



 Comments   
Comment by Jagadish [ 26/Jan/11 ]

GUI need not call this method _get-validation-table-names always. It has to be called only when validation is turned on and validation method is table. In this case, its being called even when validation is turned OFF.

Refer both the exceptions :
1) No password credential found
2) Invalid Oracle URL specified

They state that "username, password" are not specified and URL is incorrect. These exceptions are from the driver vendor.

Probably, GUI need to avoid showing this issue when validation is not turned ON.

Comment by Jagadish [ 26/Jan/11 ]

Instead of showing the message as :
_get-validation-table-names failed : javax.resource.spi.SecurityException: No PasswordCredential found

It can be shown as :
Unable to get the list of table-names for selecting the table for table-based validation, following error occurred :
javax.resource.spi.SecurityException: No PasswordCredential found

Comment by sumasri [ 06/Jul/11 ]

Fixed this as part of the issue #16397. Please verify with the latest workspace and update the issue.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-15444] Dev test failures Created: 05/Jan/11  Updated: 06/Mar/12  Due: 14/Jan/11

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Nazrul Assignee: Jason Lee
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-15547 Dev Test Failure(s) Resolved
depends on GLASSFISH-15549 Dev Test Failure(s) Resolved
depends on GLASSFISH-15548 Dev Test Failure(s) Closed
Tags: 3-1-exclude

 Description   

[Tracking Bug]

We need to get console Dev Tests working. I am filing this bug to track this. Please close it only when all GUI Dev Tests are passing. We plan to leverage these Dev Tests during final system testing to certify different supported OS and browser matrix.

Here is the latest status from today:

[artifact:mvn] -------------------------------------------------------
[artifact:mvn] T E S T S
[artifact:mvn] -------------------------------------------------------
[artifact:mvn] Running org.glassfish.admingui.devtests.TransactionServiceTest

[artifact:mvn] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 146.721 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.ConnectorsTest

[artifact:mvn] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 47.524 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.ConnectorServiceTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.328 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.ConfigTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.1 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.VirtualServerTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 8.764 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.LifecycleModulesTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.567 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.JavaMessageServiceTest

[artifact:mvn] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 21.177 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.ResourceAdapterConfigsTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.448 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.SecurityTest

[artifact:mvn] Tests run: 6, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 851.604 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.JVMReportTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.61 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.JdbcTest

[artifact:mvn] Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 35.354 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.LoggerSettingsTest

[artifact:mvn] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.116 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.JvmSettingsTest

[artifact:mvn] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.002 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.AdminServiceTest

[artifact:mvn] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 13.248 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.JndiTest

[artifact:mvn] Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 36.473 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.JmsResourcesTest

[artifact:mvn] Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 29.295 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.GMSTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.942 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.NodeTest

[artifact:mvn] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 345.99 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.ClusterTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 63.381 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.StandaloneTest

[artifact:mvn] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 13.533 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.WorkSecurityMapTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.526 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.RestResponseTest

[artifact:mvn] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 3.457 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.EnterpriseServerTest

[artifact:mvn] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 21.807 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.HttpServiceTest

[artifact:mvn] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 124.764 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.AvailabilityServiceTest

[artifact:mvn] Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 463.54 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.ApplicationTest

[artifact:mvn] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 83.179 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.JavaMailTest

[artifact:mvn] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 24.111 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.IiopListenerTest

[artifact:mvn] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.501 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.EjbContainerTest

[artifact:mvn] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.841 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.MonitoringTest

[artifact:mvn] Tests run: 3, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 159.509 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.WebContainerTest

[artifact:mvn] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.753 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.AdminObjectTest

[artifact:mvn] Tests run: 2, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 16.684 sec <<< FAILURE!
[artifact:mvn] Running org.glassfish.admingui.devtests.JsonUtilTest
[artifact:mvn] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.ThreadPoolsTest

[artifact:mvn] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.466 sec
[artifact:mvn] Running org.glassfish.admingui.devtests.NetworkConfigTest

[artifact:mvn] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.57 sec
[artifact:mvn]
[artifact:mvn] Results :
[artifact:mvn]
[artifact:mvn] Failed tests:
[artifact:mvn] testTransactionService(org.glassfish.admingui.devtests.TransactionServiceTest)
[artifact:mvn] testAddMessageSecurityConfiguration(org.glassfish.admingui.devtests.SecurityTest)
[artifact:mvn] testCreateAndDeleteNode(org.glassfish.admingui.devtests.NodeTest)
[artifact:mvn] testUpdateNode(org.glassfish.admingui.devtests.NodeTest)
[artifact:mvn] testDeleteWithInstance(org.glassfish.admingui.devtests.NodeTest)
[artifact:mvn] testHttpService(org.glassfish.admingui.devtests.HttpServiceTest)
[artifact:mvn] testAvailabilityService(org.glassfish.admingui.devtests.AvailabilityServiceTest)
[artifact:mvn] testWebContainerAvailability(org.glassfish.admingui.devtests.AvailabilityServiceTest)
[artifact:mvn] testEjbContainerAvailability(org.glassfish.admingui.devtests.AvailabilityServiceTest)
[artifact:mvn] testJMSAvailability(org.glassfish.admingui.devtests.AvailabilityServiceTest)
[artifact:mvn] testDeployWar(org.glassfish.admingui.devtests.ApplicationTest)
[artifact:mvn] testMonitoringApplicationsPage(org.glassfish.admingui.devtests.MonitoringTest)
[artifact:mvn] testAdminObjectResources(org.glassfish.admingui.devtests.AdminObjectTest)
[artifact:mvn]
[artifact:mvn] Tests in error:
[artifact:mvn] testConnectorResourcesWithTargets(org.glassfish.admingui.devtests.ConnectorsTest)
[artifact:mvn] testAddVirtualServer(org.glassfish.admingui.devtests.VirtualServerTest)
[artifact:mvn] testLifecycleModules(org.glassfish.admingui.devtests.LifecycleModulesTest)
[artifact:mvn] testJmsPhysicalDestinations(org.glassfish.admingui.devtests.JavaMessageServiceTest)
[artifact:mvn] testSecurityPage(org.glassfish.admingui.devtests.SecurityTest)
[artifact:mvn] testJdbcResourcesWithTargets(org.glassfish.admingui.devtests.JdbcTest)
[artifact:mvn] testEditJmxConntector(org.glassfish.admingui.devtests.AdminServiceTest)
[artifact:mvn] testCustomResourcesWithTargets(org.glassfish.admingui.devtests.JndiTest)
[artifact:mvn] testExternalResourcesWithTargets(org.glassfish.admingui.devtests.JndiTest)
[artifact:mvn] testAddingConnectionFactoriesWithTargets(org.glassfish.admingui.devtests.JmsResourcesTest)
[artifact:mvn] testAddingDestinationResourcesWithTargets(org.glassfish.admingui.devtests.JmsResourcesTest)
[artifact:mvn] testProperties(org.glassfish.admingui.devtests.StandaloneTest)
[artifact:mvn] testCreateAndDeleteStandaloneInstance(org.glassfish.admingui.devtests.StandaloneTest)
[artifact:mvn] testStandaloneInstanceResourcesPage(org.glassfish.admingui.devtests.StandaloneTest)
[artifact:mvn] testPostCommand(org.glassfish.admingui.devtests.RestResponseTest)
[artifact:mvn] testGetCommand(org.glassfish.admingui.devtests.RestResponseTest)
[artifact:mvn] testEndpointExists(org.glassfish.admingui.devtests.RestResponseTest)
[artifact:mvn] testSystemProperties(org.glassfish.admingui.devtests.EnterpriseServerTest)
[artifact:mvn] createMailResourceWithTargets(org.glassfish.admingui.devtests.JavaMailTest)
[artifact:mvn] testMonitoringServerPage(org.glassfish.admingui.devtests.MonitoringTest)
[artifact:mvn] testAdminObjectResourcesWithTargets(org.glassfish.admingui.devtests.AdminObjectTest)
[artifact:mvn]
[artifact:mvn] Tests run: 88, Failures: 13, Errors: 21, Skipped: 0
[artifact:mvn]
[artifact:mvn] [INFO] ------------------------------------------------------------------------
[artifact:mvn] [ERROR] BUILD FAILURE
[artifact:mvn] [INFO] ------------------------------------------------------------------------
[artifact:mvn] [INFO] There are test failures.
[artifact:mvn]
[artifact:mvn] Please refer to c:\hudson\workspace\v3-admingui-devtests\devtests\target\surefire-reports for the individual test results.
[artifact:mvn] [INFO] ------------------------------------------------------------------------
[artifact:mvn] [INFO] For more information, run Maven with the -e switch
[artifact:mvn] [INFO] ------------------------------------------------------------------------
[artifact:mvn] [INFO] Total time: 46 minutes 1 second
[artifact:mvn] [INFO] Finished at: Wed Jan 05 09:11:40 CST 2011
[artifact:mvn] [INFO] Final Memory: 22M/94M
[artifact:mvn] [INFO] ------------------------------------------------------------------------
[artifact:mvn] Java Result: 1



 Comments   
Comment by Nazrul [ 05/Jan/11 ]

Adding 3_1-review to exclude from un-scrubbed list

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-15111] debug(?) messages printed by verifier Created: 11/Dec/10  Updated: 11/Mar/13

Status: Open
Project: glassfish
Component/s: verifier
Affects Version/s: 3.1_b33
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Dies Koper Assignee: Sanjeeb Sahoo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

WinXP


Attachments: File ExitTestAppClient.ear     File isdebug3.ear    

 Description   

The first two messages (about parsing domain.xml performance, user doesn't care - they're GF internals, and jdbc driver not being available, not relevant when using verifier) should be suppressed.

D:\tests\GFv3.1\glassfish-3.1-b33-12_10_2010\glassfish3\glassfish>bin\verifier d:\shared\JavaEE\ExitTestAppClient.ear
INFO: Total time to parse domain.xml: 101 milliseconds
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
INFO: Verifying: [ d:\shared\JavaEE\ExitTestAppClient.ear ]
WARNING: setRuntimeDDPresent method not implemented
INFO: Verifying: [ ExitTestEjb_jar ]
WARNING: setRuntimeDDPresent method not implemented
INFO: Verifying: [ Client_jar ]
WARNING: setRuntimeDDPresent method not implemented
INFO:

  1. of Failures : 0
  2. of Warnings : 0
  3. of Errors : 0
    INFO: No errors found in the archive.


 Comments   
Comment by Dies Koper [ 11/Dec/10 ]

This test app shows more internal message:

Visiting non-standard Signature object

and an exception with stacktrace about a container class's method being missing.
Note that only "WARNING: DPL8007: Unsupported deployment descriptors element resource-adapter-mid value testra" is expected as the app's sun-ejb-jar.xml has a tag defined on a session bean which only applies to MDBs.

Comment by Sanjeeb Sahoo [ 11/Dec/10 ]

Since those warning and info message does not appear in the final report, I don't think it is a serious issue and indeed the submitter has already classified it as a MINOR issue. So, targeting it for 4.0.





[GLASSFISH-15110] unclear warning "setRuntimeDDPresent method not implemented" from verifier Created: 11/Dec/10  Updated: 11/Mar/13

Status: Open
Project: glassfish
Component/s: verifier
Affects Version/s: 3.1_b33
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Dies Koper Assignee: Sanjeeb Sahoo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows XP


Attachments: File is_classloader-web.war    

 Description   

Check the output from the verifier. Am I supposed to implement a "setRuntimeDDPresent" method somewhere to make my application Java EE compliant?? That's the impression the tool is giving.

D:\tests\GFv3.1\glassfish-3.1-b33-12_10_2010\glassfish3\glassfish>bin\verifier d:\shared\JavaEE\ExitTestAppClient.ear
INFO: Total time to parse domain.xml: 101 milliseconds
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
INFO: Verifying: [ d:\shared\JavaEE\ExitTestAppClient.ear ]
WARNING: setRuntimeDDPresent method not implemented
INFO: Verifying: [ ExitTestEjb_jar ]
WARNING: setRuntimeDDPresent method not implemented
INFO: Verifying: [ Client_jar ]
WARNING: setRuntimeDDPresent method not implemented
INFO:

  1. of Failures : 0
  2. of Warnings : 0
  3. of Errors : 0
    INFO: No errors found in the archive.


 Comments   
Comment by Dies Koper [ 11/Dec/10 ]

Ah, I accidentally attached a different test app. But this app gives the same message.
(Note that the error about the missing class is expected. It's just that that should have been the only error displayed.)

Comment by Sanjeeb Sahoo [ 11/Dec/10 ]

Since those warning and info message do not appear in the final report, I don't think it is a serious issue and indeed the submitter has already classified it as a MINOR issue. So, targeting it for 4.0. 3.1 is pretty close to release date and 3.2 will probably have different release requirement.





[GLASSFISH-14218] Cluster: disable start/stop when no instances present Created: 26/Oct/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Trivial
Reporter: lidiam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: JPEG File startstop-cluster.JPG    
Issuezilla Id: 14,218

 Description   

build: glassfish-3.1-b25-10_21_2010.zip

Create a cluster with no instances. Go to clusters page and select newly
created cluster - start/stop cluster buttons are enabled. They should be
disabled when cluster has no instances.



 Comments   
Comment by lidiam [ 26/Oct/10 ]

Created an attachment (id=5239)
screenshot

Comment by Anissa Lam [ 27/Oct/10 ]

This table allows multi-selection. User may select cluster that have some running instance, some
with all stopped instance, some may have no instance. In that case, which button should be enabled
or disabled ?

They can clearly see that there is no instance for this cluster, and if they still want to select that, and
then say start or stop, and wasting their key stroke, they can do that as often as they want.
As long as there is no ill effect, and the page is refresh, i don't see what is the issue here.

If you really think this should be fixed, reopen as P5.

Comment by lidiam [ 28/Oct/10 ]

The issue is not crucial, since there is no ill effect of clicking the enabled
start button when there is nothing to start. It is just misleading,
specifically to new users to Glassfish, since some buttons are disabled if a
given function cannot be performed. Hence, in this case, having a button
enabled indicates that an action can be taken, which is misleading.

Ideally GUI should not display start button as enabled if there is nothing to
start: e.g. there are no instances in a cluster or they are all already started.
Considering the low impact of the current behaviour, I'm changing this issue to
an enhancement request.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13762] translation issue for wsgen, wsimport and schemagen Created: 01/Oct/10  Updated: 11/Feb/13

Status: Reopened
Project: glassfish
Component/s: l10n
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: leonfan Assignee: clyang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,762

 Description   

run those command will show some messages, but we couldn't find them in
glassfish workspace:

C:\glassfish3\glassfish\bin>wsgen
JDK's tools.jar was not found in C:\Program Files\Java\lib\tools.jar. Usually th
is means you are running JRE, not JDK. Please use the java command in JDK 5.0 or
later (not JRE.)

  • This command executes com.sun.tools.ws.WsGen could not find iWsGen.java in
    source code
    -------------------------------------------------

C:\glassfish3\glassfish\bin>wsimport
JDK's tools.jar was not found in C:\Program Files\Java\lib\tools.jar. Usually th
is means you are running JRE, not JDK. Please use the java command in JDK 5.0 or
later (not JRE.)

-same, could not find com.sun.tools.ws.WsImport.java
-------------------------------------------------

C:\glassfish3\glassfish\bin>schemagen
JDK's tools.jar was not found in C:\Program Files\Java\lib\tools.jar. Usually th
is means you are running JRE, not JDK. Please use the java command in JDK 5.0 or
later (not JRE.)

-same, could not find com.sun.tools.jxc.SchemaGeneratorFacade.java



 Comments   
Comment by gmurr [ 01/Oct/10 ]

we need to find where the .java files come from first.

Comment by Lukas Jungmann [ 09/Feb/13 ]

wsgen and wsimport are in JAX-WS RI workspace - https://svn.java.net/svn/jax-ws~sources/branches/jaxws22

schemagen and xjc are in JAXB RI workspace - https://svn.java.net/svn/jaxb~version2/branches/jaxb-2_2-branch/





[GLASSFISH-13629] list-components --long looks cheap Created: 27/Sep/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: deployment
Affects Version/s: future release
Fix Version/s: not determined

Type: Improvement Priority: Minor
Reporter: Byron Nevins Assignee: Hong Zhang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows (generic)
Platform: All


Issue Links:
Dependency
blocks GLASSFISH-12236 Review CLI Output Consistency Resolved
Duplicate
duplicates GLASSFISH-12382 reformat output from list-components ... Resolved
Issuezilla Id: 13,629

 Description   

No formatting. The long option adds enabled inside parenthesis (!!!)
See list-instances for tips on --long output

Other info can be added. E.g. what URL can I use to access the component?

c:\glassfishv3\glassfish>asadmin list-components --long
Math <web> (enabled)
hello <web> (enabled)
monitoring-scripting-client <web> (enabled)

c:\glassfishv3\glassfish>asadmin list-components
Math <web>
hello <web>
monitoring-scripting-client <web>



 Comments   
Comment by Tom Mueller [ 27/Sep/10 ]

Please see the following for guidelines on command output:

http://wikis.sun.com/display/GlassFish/Asadmin+Command+Output+Guidelines

Comment by Hong Zhang [ 28/Sep/10 ]

move under deployment category

Comment by Hong Zhang [ 04/Oct/10 ]

Assign to romain to see how we could improve the format of the current output
of the --long option to conform to the standard.

For adding any additional information for the --long output, we will look in
the next release as potential enhancement.

Comment by Romain Grécourt [ 29/Nov/10 ]

reassign to Herve

Comment by herve_souchaud [ 30/Nov/10 ]

Formatting was added to list-components, list-sub-components and list-application-refs commands output. Now, these commands generate columnar output. Changes are part of the SVN revision #42966.

As Hong already said, adding any additional information for the --long output should be looked in the next release.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13548] Allocate exception for servlet Simple com.sun.enterprise.container.common.spi.util.InjectionException Created: 20/Sep/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: test
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Critical
Reporter: Sreekanth Assignee: Sreekanth
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Attachments: File SampleService.ear     Text File server.log     Text File server.log    
Issuezilla Id: 13,548
Tags: 3_1-exclude, test_issue

 Description   

Once I deploy this webservice transaction test application and access the
webservice, I get the below exception:

Steps to reproduce:
===================

1)Create connection pool using
asadmin --echo=true create-jdbc-connection-pool --datasourceclassname
org.apache.derby.jdbc.ClientXADataSource --restype javax.sql.XADataSource –
property
portNumber=1527:serverName=localhost:User=APP:Password=APP:databaseName=sample
derby_netPool

2)Create jdbc resource using
asadmin create-jdbc-resource --connectionpoolid derby_netPool --enabled=true
jdbc/JavaProgrammingLibrary

3)Deploy the attached application and access it from browser :
http://localhost:8080/SampleService-war/SimpleService?wsdl

Exception:
==========
[#|2010-09-
20T17:27:33.698+0530|INFO|glassfish3.1|javax.enterprise.system.tools.admin.org.g
lassfish.deployment.admin|_ThreadID=15;_ThreadName=Thread-1;|SampleService was
successfully deployed in 25,969 milliseconds.|#]

[#|2010-09-
20T17:27:36.247+0530|INFO|glassfish3.1|javax.enterprise.system.container.web.com
.sun.enterprise.web|_ThreadID=15;_ThreadName=Thread-1;|PWC1412: WebModule[null]
ServletContext.log():PWC1409: Marking servlet Simple as unavailable|#]

[#|2010-09-
20T17:27:36.247+0530|INFO|glassfish3.1|javax.enterprise.system.container.web.com
.sun.enterprise.web|_ThreadID=126;_ThreadName=http-thread-pool-
10080(1);|PWC1412: WebModule[null] ServletContext.log():PWC1409: Marking servlet
Simple as unavailable|#]

[#|2010-09-
20T17:27:36.247+0530|INFO|glassfish3.1|javax.enterprise.system.container.web.com
.sun.enterprise.web|_ThreadID=126;_ThreadName=http-thread-pool-
10080(1);|PWC1412: WebModule[null] ServletContext.log():PWC1409: Marking servlet
Simple as unavailable|#]

[#|2010-09-
20T17:27:36.250+0530|WARNING|glassfish3.1|javax.enterprise.system.container.web.
com.sun.enterprise.web|_ThreadID=15;_ThreadName=Thread-
1;|StandardWrapperValve[Simple]: PWC1382: Allocate exception for servlet Simple
com.sun.enterprise.container.common.spi.util.InjectionException: Error creating
managed object for class org.glassfish.webservices.JAXWSServlet
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManaged
Object(InjectionManagerImpl.java:317)
at
com.sun.enterprise.web.WebContainer.createServletInstance(WebContainer.java:690)
at
com.sun.enterprise.web.WebModule.createServletInstance(WebModule.java:1945)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1251)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:1058)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:1
89)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1
75)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingS
tandardPipeline.java:91)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java
:228)
at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:824)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:721)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1014)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:22
0)
at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.
java:135)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53
)
at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:53
0)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:511)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.enterprise.container.common.spi.util.InjectionException: No
descriptor registered for current invocation :
com.sun.enterprise.web.WebComponentInvocation@14b746c8
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstanc
e(InjectionManagerImpl.java:148)
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstanc
e(InjectionManagerImpl.java:132)
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManaged
Object(InjectionManagerImpl.java:311)
... 28 more

#]

[#|2010-09-
20T17:27:36.250+0530|WARNING|glassfish3.1|javax.enterprise.system.container.web.
com.sun.enterprise.web|_ThreadID=126;_ThreadName=http-thread-pool-
10080(1);|StandardWrapperValve[Simple]: PWC1382: Allocate exception for servlet
Simple
com.sun.enterprise.container.common.spi.util.InjectionException: Error creating
managed object for class org.glassfish.webservices.JAXWSServlet
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManaged
Object(InjectionManagerImpl.java:317)
at
com.sun.enterprise.web.WebContainer.createServletInstance(WebContainer.java:690)
at
com.sun.enterprise.web.WebModule.createServletInstance(WebModule.java:1945)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1251)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:1058)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:1
89)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1
75)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingS
tandardPipeline.java:91)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java
:228)
at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:824)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:721)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1014)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:22
0)
at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.
java:135)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53
)
at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:53
0)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:511)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.enterprise.container.common.spi.util.InjectionException: No
descriptor registered for current invocation :
com.sun.enterprise.web.WebComponentInvocation@14b746c8
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstanc
e(InjectionManagerImpl.java:148)
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstanc
e(InjectionManagerImpl.java:132)
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManaged
Object(InjectionManagerImpl.java:311)
... 28 more

#]

[#|2010-09-
20T17:27:36.250+0530|WARNING|glassfish3.1|javax.enterprise.system.container.web.
com.sun.enterprise.web|_ThreadID=126;_ThreadName=http-thread-pool-
10080(1);|StandardWrapperValve[Simple]: PWC1382: Allocate exception for servlet
Simple
com.sun.enterprise.container.common.spi.util.InjectionException: Error creating
managed object for class org.glassfish.webservices.JAXWSServlet
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManaged
Object(InjectionManagerImpl.java:317)
at
com.sun.enterprise.web.WebContainer.createServletInstance(WebContainer.java:690)
at
com.sun.enterprise.web.WebModule.createServletInstance(WebModule.java:1945)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1251)
at
org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:1058)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:1
89)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1
75)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingS
tandardPipeline.java:91)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java
:228)
at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:824)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:721)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1014)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:22
0)
at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.
java:135)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53
)
at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:53
0)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:511)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.enterprise.container.common.spi.util.InjectionException: No
descriptor registered for current invocation :
com.sun.enterprise.web.WebComponentInvocation@14b746c8
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstanc
e(InjectionManagerImpl.java:148)
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectInstanc
e(InjectionManagerImpl.java:132)
at
com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManaged
Object(InjectionManagerImpl.java:311)
... 28 more

#]


 Comments   
Comment by Sreekanth [ 20/Sep/10 ]

Created an attachment (id=4923)
Ear file

Comment by Bhakti Mehta [ 11/Oct/10 ]
      • Issue 13549 has been marked as a duplicate of this issue. ***
Comment by Bhakti Mehta [ 30/Nov/10 ]

Rama, please can you look into this issue with WSServletContextListener This is the stacktrace I am seeing with yesterday's build
asadmin deploy ~/gfbugs/13458/SampleService.ear
org.glassfish.api.admin.CommandException: remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: java.lang.IllegalArgumentException: javax.servlet.ServletException: com.sun.enterprise.container.common.spi.util.InjectionException: Error creating managed object for class org.glassfish.webservices.WSServletContextListener. Please see server.log for more details.
Command deploy failed.

Btw I tried these steps
asadmin --echo=true create-jdbc-connection-pool --datasourceclassname org.apache.derby.jdbc.ClientXADataSource --restype javax.sql.XADataSource --property portNumber=1527:serverName=localhost:User=APP:Password=APP:databaseName=sample derby_netPool

asadmin create-jdbc-resource --connectionpoolid derby_netPool --enabled=true jdbc/JavaProgrammingLibrary

asadmin deploy ~/gfbugs/13458/SampleService.ear

Comment by ramapulavarthi [ 15/Dec/10 ]

I tried with latest V3.1 standalone built from my local workspace and I could not reproduce the problem. The ear file deployed fine for me. Are you seeing problem when deploying to a cluster? Please confirm the issue with latest Galssfish V3.1 nightly/promoted build.

Comment by ramapulavarthi [ 15/Dec/10 ]

Please confirm the issue with latest build of v3.1.

Comment by Sreekanth [ 20/Dec/10 ]

I am still seeing this issue with the latest build of metro and glassfish 3.1 .I am not using clustered environment.But I have 2 domains running on that server.

Please find the attached server log.

Comment by Sreekanth [ 20/Dec/10 ]

Server file.

Comment by Sreekanth [ 20/Dec/10 ]

Assigning back to Rama.

Comment by ramapulavarthi [ 20/Dec/10 ]

Sreekanth, Can you reproduce it on a default glassfish installation that has single (default) domain?

Comment by Sreekanth [ 21/Dec/10 ]

Yes.It is reproducible on default setup as well.

Comment by Sreekanth [ 21/Dec/10 ]

log file when run with default glassfish installation

Comment by ramapulavarthi [ 22/Dec/10 ]

Finally I have managed to deploy the ear with some modifications.
(1) There are additional resources required by the application. They can be created by doing
asadmin create-jms-resource --restype javax.jms.Queue --enabled=true --property Name=PhysicalQueue jms/Queue
asadmin create-jms-resource --restype javax.jms.ConnectionFactory jms/ConnectionFactory

These steps are gathered from wstx sample in https://wsit-docs.dev.java.net/releases/1.2/wsittutorial.zip

(2) The contents of the ear file are
META-INF/
META-INF/MANIFEST.MF
jar/
lib/
META-INF/application.xml
META-INF/sun-application.xml
SampleService-ejb.jar
SampleService-war.war
lib/SampleService-ejb.jar ---> is not needed and should be removed.

(3) In this application, the META-INF/MANIFEST.MF in SampleService-war.war has Class-Path: SampleService-ejb.jar which is discovered by the EJB Deployer twice as it exists in root ear as well as the classpath of the war.

There seems to be a bug in Gllassfish deployment, when an ejb is shared by the web application like this, the EJB annotations (in this case ws) are processed twice. Some observations about the problem can also be found at a Users's blog http://www.shareyourwork.org/roller/ralphsjavablog/entry/jee6_and_packaging_an_ear.

To workaround this, remove the Class-Path entry in SampleService-war.war META-INF/MANIFEST.MF. Also, this ejb is not used by the Servlet at all and seems to have been introduced for no useful reason. I could deploy fine with the above modifications.

With this evaluation, I think this is a non-blocker for Metro in v3.1. Deployment issue in v3.1 has to be pursued as a separate issue in GF.

Comment by ramapulavarthi [ 23/Dec/10 ]

Assigning back to sqe and adding 3_1-exclude so that sqe can continue to track it for fixing the test case.

The EAR should be fixed to not share the EJB components. May be the Deployer could be intelligent to detect this and warn the users on deployment, but it is tricky to implement with the possibility of different components packaged in the same module in JavaEE 6. The discussion on topic can be followed at http://java.net/projects/glassfish/lists/dev/archive/2010-12/message/200

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13335] Bring focus to top of page after save for long pages Created: 08/Sep/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: lidiam Assignee: lidiam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,335

 Description   

build: glassfish-3.1-b19-09_08_2010.zip

When making changes on pages that are long and need scrolling, there is a Save
button on the bottom. After hitting save, user has to know to scroll to the top
of the page to see the success/failure message. GUI should automatically bring
the focus to the top of page after each save or display message at the bottom as
well. Otherwise, inexperienced user may be hitting Save many times, since it is
not clear if the action took place or not, other than by checking top of the page.



 Comments   
Comment by Anissa Lam [ 05/Oct/10 ]

We will need to do this in case by case basis. There isn't a 'general' way to
do that.
Please specify the page you have the problem. (Better yet, file separate issue
for each page). thanks

Comment by Anissa Lam [ 06/Oct/10 ]

reassign to Lidia for which page this occurs.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13244] GlassFish 3.1 Release (root issue) Created: 02/Sep/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: other
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Blocker
Reporter: Chris Kasso Assignee: Chris Kasso
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-14044 various files point to docs.sun.com Resolved
depends on GLASSFISH-12739 ensure that secure DAS/instance commu... Resolved
depends on GLASSFISH-11921 3.1 is not supported by NetBeans Resolved
Issuezilla Id: 13,244

 Description   

This is the 'root' issue for issues (work) related to the GlassFish Server 3.1.

For details of GlassFish 3.1 see:

http://wikis.sun.com/display/GlassFish/PlanForGlassFish3.1



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13200] [UB]certain number of join notifications are not seen after cluster startup. Created: 30/Aug/10  Updated: 07/Mar/12

Status: In Progress
Project: glassfish
Component/s: docs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: zorro Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: Linux


Issuezilla Id: 13,200

 Description   

build: ogs-3.1-web-b18-08_30_2010

  • start DAS
  • wait for DAS to start
  • start cluster (9 CORE instances on 9 machines)
  • wait for all cluster instances to start
  • stop cluster
  • wait all cluster CORE nodes to stop
  • stop DAS
  • wait to DAS to stop
  • collect logs

bug:
nodes 5 and 10 do not have 9 join notification.

Expected:
Like other nodes at some point we should see 9 join notifications of the 9-node
clusters startup.

Results and logs:
http://aras2



 Comments   
Comment by Joe Fialli [ 31/Aug/10 ]

I am unable to resolve the link that is attached to this report to investigate
this issue. The link is a relative link to target machine(assumes auto
completion to a domain that I may not have configured to auto complete to.)

************

Additonal information required to evaluate this issue.
How is the cluster being started? With the "asadmin start-cluster" command or
are the instances being started up independently via "asadmin start-instance"
for each clustered instance (due to outstanding issue with "asadmin
start-cluster").

******

Note that only the DAS is required to see all JOIN notifications from all
instances during start-cluster sequence.

All GMS notifications are broadcasted to all active members of the cluster.
Since not all instances start in lock step at same moment of time, it is quite
possible that not every instance sees every other instance's JOIN notification.

When an instance registers for an JOIN notification, there are methods on the
notification that allow the instance to learn of all the other ALIVE and READY
members that are currently running.

After "start-cluster" completes and all instances are running, all future
individual GMS notifcations for clustered instances stopping, starting or
failing should be received by all active clustered members. Additionally, there
is a race condition at "asadmin stop-cluster" that not all instances will see
the PLANNED_SHUTDOWN of all other instances. This is basic attribute of GMS
notifications being a broadcast to all registered members. One can not guarantee
the reception of a broadcast during startup or shutdown of entire cluster.

Comment by zorro [ 31/Aug/10 ]
  • The reason this could be a bug is that in nodes 5, and 10 we see 10 join
    notification but no 9 join notification prior to that.
  • Instances were started using start-local-instance
Comment by Joe Fialli [ 15/Sep/10 ]

After applying the system configuration recommendations below,
this problem is no longer occurring on Oracle Enterprise Linux 5.

This system configuration issue must be documented for glassfish v3.1.
While we do not have final tuning values, I will keep this issue open as a
documentation issue for glassfish v3.1 so we remember to document this
important issue that requires OS level configuration.

The default Linux UDP buffer size is too small for a 10 instance cluster.

These values can be configured via sysctl -w (to configure in OS immediately)
and to fix across reboot of the OS, the values should be placed in /etc/sysctl.conf.

We are still working on final recommended UDP buffer size. But for now,
these values have test passsing.

net.core.rmem_max=524288
net.core.wmem_max=524288
net.core.rmem_default=524288
net.core.wmem_default=524288

We have determined that the default values are too small, but we have not come
up with a formula to compute what the values need to be based on the number of
instances in the cluster AND the number of instances per machine.

Comment by Joe Fialli [ 15/Sep/10 ]
      • Issue 13209 has been marked as a duplicate of this issue. ***
Comment by Joe Fialli [ 15/Sep/10 ]
      • Issue 13209 has been marked as a duplicate of this issue. ***
Comment by Paul Davies [ 04/Oct/10 ]

Added [UB] to Summary to denote unbundled documentation.

Comment by Tom Mueller [ 07/Mar/12 ]

Bulk update to set Fix Version to "not determined" for issues that had it set to a version that has already been released.





[GLASSFISH-13115] Provide ability to restore backed up domain during installation. Created: 25/Aug/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: installation
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Chris Kasso Assignee: Snjezana Sevo-Zenzerovic
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 13,115
Tags: 3_1_1-scrubbed, 3_1_next

 Description   

Provide ability to restore backed up domain during installation.

There are existing commands that allow a user to backup a domain (config +
deployed apps) as well as restore the domain. What about offering
an option in the installer to restore a domain from a backup zip?

The scenario would be something like this:

1) The user manually (backup-domain CLI) backed up the domain.

2) The system the DAS is on crashes so the user runs the installer on
another system to reinstall GF.

3) As part of that install process they are given the option to restore
the domain(s) from backups they may be maintaining.

4) We can also give them the option to ping existing instances to
update the DAS coordinates (if they happened to change based on
the move to new HW).



 Comments   
Comment by scatari [ 11/May/11 ]

We should consider this for 3.1.1.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13048] Add option to test ssh connectivity to node Created: 19/Aug/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Minor
Reporter: jclingan Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Issuezilla Id: 13,048

 Description   

When creating a cluster in GlassFish 3, a node must be created. Received an error when creating an
instance on a remote node. However, I can ssh to remote host from command line without providing
credentials, so I do know ssh is set up properly. It would be useful to have a "Test" button on the
administration GUI to "test" ssh connectivity without having to go to the CLI. There are similar "Test"
buttons to test resources in GlassFish, for example.

The results should be "Connection successful" if successful, and listing an error code with error description
if there is a connection error. It would be useful to list help options if connection is unsuccessful (such as
"try to ssh from command line or similar).



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-13030] DDL Generation Ignoring Output Mode Created: 18/Aug/10  Updated: 20/Jun/14

Status: Open
Project: glassfish
Component/s: entity-persistence
Affects Version/s: v3.0.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: lineman78 Assignee: tware
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows XP
Platform: All


Issuezilla Id: 13,030

 Description   

I have the output mode set to database and it is still trying to generate the
files, which is in turn causing other errors because I do not have the file
names set. I have decompiled the source of JPAJava2DBProcessor and it seems to
be calling constructJdbcFileNames no matter what the output mode is set to. If
I add the dll file name properties it seems to work. This issue seems to have
been introduced in a recent update as when I tried with these same lines in Feb.
it worked as intended.

persistence.xml properties:
<property name="eclipselink.target-server" value="SunAS9" />
<property name="eclipselink.target-database" value="Derby" />
<property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
<property name="eclipselink.ddl-generation.output-mode" value="database"/>

Stack Trace:
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1937)
at
org.glassfish.persistence.common.Java2DBProcessorHelper.getDDLNamePrefix(Java2DBProcessorHelper.java:547)
at
org.glassfish.persistence.jpa.JPAJava2DBProcessor.constructJdbcFileNames(JPAJava2DBProcessor.java:249)
at
org.glassfish.persistence.jpa.JPAJava2DBProcessor.isJava2DbPU(JPAJava2DBProcessor.java:216)
at
org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:167)
at
org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:96)
at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:121)
at
com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:644)
at
org.glassfish.javaee.full.deployment.EarDeployer.prepareBundle(EarDeployer.java:269)



 Comments   
Comment by helweg [ 30/Jan/12 ]

I (maybe) stumbled upon something that might be related to this bug.

I could not get glassfish (Version 3.1.1) to drop and create my tables (right in the derby db) with the following properties in persistence.xml:

        <properties>           
            <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
            <property name="eclipselink.application-location" value="C:\projects\myProject\ddl"/>
            <property name="eclipselink.create-ddl-jdbc-file-name" value="createMyProjectDB.ddl"/>
            <property name="eclipselink.drop-ddl-jdbc-file-name" value="dropMyProjectDB.ddl"/>
            <property name="eclipselink.ddl-generation.output-mode" value="both"/>
        </properties>

It would always just create the ddl file but not drop&create the tables in the derby db.
However, when I deleted the last 4 lines and reduced the persistence.xml to the following:

        <properties>           
            <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
        </properties>

it works.

It seems like glassfish is ignoring the eclipselink.ddl-generation.output-mode property.
(I have not further investigated this problem, though.)

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk change to set fix version to "not determined" where the issue is open but the value is for a released version.

Comment by rivasdiaz [ 20/Jun/14 ]

This issue can be reproduced on Glassfish 3.1.2.2





[GLASSFISH-12984] Embedded GlassFish Maven Plugin Documentation Created: 14/Aug/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: other
Affects Version/s: v3.0.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: mkarg Assignee: Bhavanishankar
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 12,984

 Description   

It would be great if there would be a public documentation for the 3.0.1
release of the maven-embedded-glassfish-plugin.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12862] cannot determine anonymous login after session timout Created: 01/Aug/10  Updated: 11/Feb/13

Status: Open
Project: glassfish
Component/s: amx
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Anissa Lam Assignee: Peter Bower
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 12,862
Tags: 3_1-exclude

 Description   

Very often, when the session timeout, I cannot just get back to the GUI
automatically. The login screen is displayed and require me to enter the login
info. I have to enter "admin" as username and leave the password field empty.
Not sure is its GUI's, security or AMX issue.

Here is the info from server.log

[#|2010-08-01T14:30:30.300-0700|INFO|glassfish3.1|org.glassfish.admingui|_ThreadID=62;_ThreadName=http-thread-pool-4848(5);|admin
console: initSessionAttributes()|#]

[#|2010-08-01T14:30:31.621-0700|WARNING|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=62;_ThreadName=http-thread-pool-4848(5);|getRealmNames():
Can't get realm names
java.lang.NullPointerException
at org.glassfish.admin.amx.impl.ext.RealmsImpl.getAuthRealms(RealmsImpl.java:107)
at
org.glassfish.admin.amx.impl.ext.RealmsImpl.getConfiguredRealmNames(RealmsImpl.java:113)
at org.glassfish.admin.amx.impl.ext.RealmsImpl.loadRealms(RealmsImpl.java:122)
at org.glassfish.admin.amx.impl.ext.RealmsImpl.getRealmNames(RealmsImpl.java:194)
at sun.reflect.GeneratedMethodAccessor368.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.glassfish.admin.amx.impl.mbean.AMXImplBase.getAttributeByMethod(AMXImplBase.java:548)
at
org.glassfish.admin.amx.impl.mbean.AMXImplBase.getAttributeInternal(AMXImplBase.java:465)
at
org.glassfish.admin.amx.impl.mbean.AMXImplBase.getAttribute(AMXImplBase.java:420)
at
org.glassfish.admin.amx.impl.mbean.AMXImplBase.getAttributes(AMXImplBase.java:504)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:726)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:665)
at
org.glassfish.admin.amx.util.jmx.MBeanProxyHandler.getAttributes(MBeanProxyHandler.java:274)
at
org.glassfish.admin.amx.core.proxy.AMXProxyHandler.attributesMap(AMXProxyHandler.java:1194)
at
org.glassfish.admin.amx.core.proxy.AMXProxyHandler.attributesMap(AMXProxyHandler.java:1204)
at
org.glassfish.admin.amx.core.proxy.AMXProxyHandler.handleSpecialMethod(AMXProxyHandler.java:415)
at
org.glassfish.admin.amx.core.proxy.AMXProxyHandler._invoke(AMXProxyHandler.java:793)
at
org.glassfish.admin.amx.core.proxy.AMXProxyHandler.invoke(AMXProxyHandler.java:527)
at $Proxy111.attributesMap(Unknown Source)
at
org.glassfish.admingui.common.handlers.ProxyHandlers.getProxyAttribute(ProxyHandlers.java:316)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:442)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:420)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:394)
at
com.sun.jsftemplating.layout.descriptors.LayoutDefinition.dispatchInitPageHandlers(LayoutDefinition.java:332)
at
com.sun.jsftemplating.layout.template.TemplateLayoutDefinitionManager.getLayoutDefinition(TemplateLayoutDefinitionManager.java:201)
at
com.sun.jsftemplating.layout.LayoutDefinitionManager.getLayoutDefinition(LayoutDefinitionManager.java:152)
at
com.sun.jsftemplating.layout.LayoutViewHandler.buildUIComponentTree(LayoutViewHandler.java:507)
at
com.sun.jsftemplating.layout.LayoutViewHandler.buildUIComponentTree(LayoutViewHandler.java:507)
at
com.sun.jsftemplating.layout.LayoutViewHandler.buildUIComponentTree(LayoutViewHandler.java:507)
at
com.sun.jsftemplating.layout.LayoutViewHandler.createView(LayoutViewHandler.java:255)
at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:238)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97)
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:107)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:114)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:334)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1518)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:339)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:211)
at com.sun.webui.jsf.util.UploadFilter.doFilter(UploadFilter.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:211)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:171)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:651)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:591)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:87)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:158)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:651)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:591)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:318)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:222)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:240)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:823)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:720)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:220)
at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:530)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:511)
at java.lang.Thread.run(Thread.java:637)

#]

[#|2010-08-01T14:30:34.181-0700|INFO|glassfish3.1|org.glassfish.admingui|_ThreadID=62;_ThreadName=http-thread-pool-4848(5);|UpdateCheckFrequency
is set to NEVER by user. Component update count not performed. |#]

[#|2010-08-01T14:30:45.695-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|java.lang.reflect.UndeclaredThrowableException|#]

[#|2010-08-01T14:30:46.111-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at $Proxy133.getAnonymousUser(Unknown Source)|#]

[#|2010-08-01T14:30:46.111-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admingui.common.handlers.CommonHandlers.testLoginBypass(CommonHandlers.java:470)|#]

[#|2010-08-01T14:30:46.112-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at sun.reflect.GeneratedMethodAccessor407.invoke(Unknown Source)|#]

[#|2010-08-01T14:30:46.112-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)|#]

[#|2010-08-01T14:30:46.112-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at java.lang.reflect.Method.invoke(Method.java:597)|#]

[#|2010-08-01T14:30:46.112-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:442)|#]

[#|2010-08-01T14:30:46.112-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:420)|#]

[#|2010-08-01T14:30:46.112-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:394)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.descriptors.LayoutDefinition.dispatchInitPageHandlers(LayoutDefinition.java:332)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.template.TemplateLayoutDefinitionManager.getLayoutDefinition(TemplateLayoutDefinitionManager.java:201)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.LayoutDefinitionManager.getLayoutDefinition(LayoutDefinitionManager.java:152)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.ViewRootUtil.getLayoutDefinition(ViewRootUtil.java:257)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.ViewRootUtil.getLayoutDefinition(ViewRootUtil.java:228)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jsftemplating.layout.LayoutViewHandler.createView(LayoutViewHandler.java:201)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:238)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:107)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:114)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:334)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1518)|#]

[#|2010-08-01T14:30:46.113-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatcher.java:831)|#]

[#|2010-08-01T14:30:46.114-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:693)|#]

[#|2010-08-01T14:30:46.114-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:495)|#]

[#|2010-08-01T14:30:46.114-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.core.ApplicationDispatcher.doDispatch(ApplicationDispatcher.java:466)|#]

[#|2010-08-01T14:30:46.114-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.core.ApplicationDispatcher.dispatch(ApplicationDispatcher.java:356)|#]

[#|2010-08-01T14:30:46.114-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:296)|#]

[#|2010-08-01T14:30:46.114-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.java:463)|#]

[#|2010-08-01T14:30:46.114-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:251)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.web.security.RealmAdapter.invokeAuthenticateDelegate(RealmAdapter.java:1183)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:580)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:619)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:591)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:87)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:158)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:651)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:591)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:318)|#]

[#|2010-08-01T14:30:46.115-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:222)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:240)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:823)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:720)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:220)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)|#]

[#|2010-08-01T14:30:46.116-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)|#]

[#|2010-08-01T14:30:46.117-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)|#]

[#|2010-08-01T14:30:46.117-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:530)|#]

[#|2010-08-01T14:30:46.117-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:511)|#]

[#|2010-08-01T14:30:46.117-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at java.lang.Thread.run(Thread.java:637)|#]

[#|2010-08-01T14:30:46.117-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|Caused
by: javax.management.AttributeNotFoundException: Attribute not found:
"AnonymousUser" of MBean amx:pp=/ext,type=realms[null]|#]

[#|2010-08-01T14:30:46.117-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admin.amx.impl.mbean.AMXImplBase.rethrowAttributeNotFound(AMXImplBase.java:532)|#]

[#|2010-08-01T14:30:46.117-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admin.amx.impl.mbean.AMXImplBase.getAttributeByMethod(AMXImplBase.java:553)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admin.amx.impl.mbean.AMXImplBase.getAttributeInternal(AMXImplBase.java:465)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admin.amx.impl.mbean.AMXImplBase.getAttribute(AMXImplBase.java:420)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admin.amx.util.jmx.MBeanProxyHandler.getAttribute(MBeanProxyHandler.java:248)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admin.amx.util.jmx.MBeanProxyHandler.invoke(MBeanProxyHandler.java:386)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admin.amx.core.proxy.AMXProxyHandler._invoke(AMXProxyHandler.java:823)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
at
org.glassfish.admin.amx.core.proxy.AMXProxyHandler.invoke(AMXProxyHandler.java:527)|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|null|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|
... 54 more|#]

[#|2010-08-01T14:30:46.118-0700|SEVERE|glassfish3.1|org.glassfish.admingui|_ThreadID=60;_ThreadName=http-thread-pool-4848(3);|Cannot
determine anonymous login. Login enforced.|#]



 Comments   
Comment by Anissa Lam [ 01/Aug/10 ]

Since the NPE is from amx, I am transferring this to AMX for investigation.

Comment by prasads [ 07/Oct/10 ]

Is this issue even relevant now , since Admin GUI does not use AMX ? Assigning
to Anissa for a response.

Comment by Anissa Lam [ 13/Oct/10 ]

Its true that GUI doesn't depend on AMX for 3.1.
However, the stack trace shows clearly that there is an NPE in getting the realm
names. It means there is an issue within AMX.
It is up to the amx team to determine if they want to fix this or not.

[#|2010-08-01T14:30:31.621-0700|WARNING|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=62;_ThreadName=http-thread-pool-4848(5);|getRealmNames():
Can't get realm names
java.lang.NullPointerException
at org.glassfish.admin.amx.impl.ext.RealmsImpl.getAuthRealms(RealmsImpl.java:107)
at
org.glassfish.admin.amx.impl.ext.RealmsImpl.getConfiguredRealmNames(RealmsImpl.java:113)
at org.glassfish.admin.amx.impl.ext.RealmsImpl.loadRealms(RealmsImpl.java:122)
at org.glassfish.admin.amx.impl.ext.RealmsImpl.getRealmNames(RealmsImpl.java:194)
at sun.reflect.GeneratedMethodAccessor368.invoke(Unknown Source)
at

Comment by prasads [ 08/Dec/10 ]

Excluding this issue from this release , since its not reproducible for now.

Comment by prasads [ 20/Feb/11 ]

Assigning issues to Naman

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12844] Session Persistence Feature for WAB Created: 30/Jul/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: OSGi-JavaEE
Affects Version/s: 3.1
Fix Version/s: not determined

Type: New Feature Priority: Major
Reporter: casmeiron Assignee: Sanjeeb Sahoo
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows 7
Platform: All


Attachments: File simple-cdi-osgi-test-1.0.war    
Issuezilla Id: 12,844

 Description   

In the latest version of glassfish v3.1 I notice that the session for WAB isn't
persisted, whether I redeploy my WAB the session is destroyed and that's bad for
the development process and even to the production environment. If I have a multi-
module apps, I don't want to session be recreated whether I redeploy one of the
modules.

I don't know if thats better as a configuration or default behavior but it's
important to have it somehow.

I'm goin' to attach the test case.



 Comments   
Comment by casmeiron [ 30/Jul/10 ]

Created an attachment (id=4616)
Every time you redeploy you gonna get a different object (as it has SessionScoped ann that proves the session persistence feature doesn't exist)

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12842] Admin-GUI startup resets runtime Default Realm to FileRealm incorrectly Created: 30/Jul/10  Updated: 06/Nov/13

Status: Open
Project: glassfish
Component/s: amx
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: kumarjayanti Assignee: Peter Bower
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Macintosh


Attachments: JPEG File grab-1.jpg     JPEG File grab-2.jpg     JPEG File grab-2.jpg    
Issuezilla Id: 12,842
Tags: 3_1-exclude

 Description   

I have a server config where i have set the default-realm attribute on security-service to "ldaprealm".
Everytime i start Admin-GUI then the default realm gets reset to "filerealm" which happens to be the
default when nothing was explicitly given.

If i try to see the value of default-realm in GUI after loading however it does show the correct
value"ldaprealm". But the internal RuntimeValue in Security Realm.java has been changed to "filerealm"

I debugged this and found that the issue is in AMX code. Attached are call stacks when admin gui is
loading to show the issue.

Steps to reproduce :

1. Open Admin GUI and under Configuration->Security set the default realm to something otherthan
filerealm.

2. You can for example create another realm in GUI first (which can be another filerealm with different
name) and set that as the default.

3. Now restart the server and access admin gui in the browser.

After the browser has loaded Admin-GUI, the default realm in the security runtime would be changed
back to original filerealm and not the one created in step 2.

I also notice that the call to Realm.setDefaultRealm() happens many many times during loading of
Admin GUI which seems somehow unnecessary.

Marking as P2 since without this being fixed we are blocked on the Oracle Access Manager integration
where we require the default glassfish realm to be an ldaprealm. And things only work as long as the
Admin GUI is not loaded.



 Comments   
Comment by kumarjayanti [ 30/Jul/10 ]

Created an attachment (id=4613)
call stack 1

Comment by kumarjayanti [ 30/Jul/10 ]

Created an attachment (id=4614)
call stack 2

Comment by kumarjayanti [ 30/Jul/10 ]

Created an attachment (id=4615)
call stack 2

Comment by prasads [ 07/Oct/10 ]

...

Comment by prasads [ 07/Oct/10 ]

Kumar
, does this issue happen now since Admin GUI does not use AMX.

Comment by prasads [ 07/Oct/10 ]

Downgrading to a P3 now.

Comment by sanandal [ 08/Oct/10 ]

...

Comment by prasads [ 15/Dec/10 ]

Excluding this for v3.1 since GUI does not use AMX

Comment by prasads [ 20/Feb/11 ]

Assigning issues to Naman

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by Peter Butkovic [ 06/Nov/13 ]

The same problem is reproducible when connecting with JConsole (via Remote Process only).

Tested with:

  • Glassfish 3.1.2.2.
  • Windows and Linux




[GLASSFISH-12812] GlassFish 2.1.1 causing some issues with Hibernate Created: 27/Jul/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: deployment
Affects Version/s: v2.1.1
Fix Version/s: not determined

Type: Bug Priority: Trivial
Reporter: rjdkolb Assignee: Hong Zhang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Issuezilla Id: 12,812

 Description   

Hello

We have existing current Hibernate applications that were written for GlassFish 2.1
But now they don't work in GlassFish 2.1.1

The core reason is 2.1.1 has a new library that clashes with Hibernate.
There is nothing to fix, I would just like this documented please.
This will also effect our Spring brothers.

I am adding a section in FishCATGold :
http://wikis.sun.com/display/GlassFish/FishCATGold
FishCAT Gold attempts to have the community identify these problems before
release by the community supplying samples.

From this blog :
http://tai-dev.blog.co.uk/2010/01/21/nosuchmethoderror-org-objectweb-asm-classwriter-when-deploying-your-app-to-a-new-instance-of-glassfish-v2-1-1-it-looks-like-the-upgraded-fins-are-7849068/

"It turns out that the latest version of GlassFish available for download
(v2.1.1 at the time of writing) has slightly different libraries than previous
versions (we were previously using v2.1.0). The asm jar “asm-3.1.jar� in the
library folder of the latest GF release appears to be incompatible with the
version of Spring (v2.5.3) and Hibernate (Core v3.2.6 GA with Hibernate
Annotations v3.3.1 GA) with are using."

Known workarounds :
1) in your sun-web.xml set <class-loader delegate="false"/>
2) manually delete the “asm-3.1.jar� file in the <glassfish-install-dir>/lib/
directory and copy an old version of “asm-<v_num>.jar� in its place.

Here is the stack trace I got :
[#|2010-07-23T15:21:20.263+0200|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=17;_ThreadName=httpSSLWorkerThread-8080-0;|15:21:20,260
ERROR ExceptionFilter:115 - An error has occurred - UID: 1279891280258
javax.servlet.ServletException: PWC1243: Filter execution threw an exception
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:270)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
at
za.co.enerweb.energyprofiling.filter.ExceptionFilter.doFilter(ExceptionFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:313)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1093)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:291)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:666)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:597)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:872)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
at
com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:382)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:264)
at
com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
Caused by: java.lang.NoSuchMethodError: org.objectweb.asm.ClassWriter.<init>(Z)V
at net.sf.cglib.core.DebuggingClassWriter.<init>(DebuggingClassWriter.java:47)
at
net.sf.cglib.core.DefaultGeneratorStrategy.getClassWriter(DefaultGeneratorStrategy.java:30)
at
net.sf.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorStrategy.java:24)
at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:216)
at net.sf.cglib.core.KeyFactory$Generator.create(KeyFactory.java:145)
at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:117)
at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:108)
at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:104)
at net.sf.cglib.proxy.Enhancer.<clinit>(Enhancer.java:69)
at
org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:117)
at
org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.postInstantiate(CGLIBProxyFactory.java:43)
at
org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:162)
at
org.hibernate.tuple.entity.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:135)
at org.hibernate.tuple.entity.PojoEntityTuplizer.<init>(PojoEntityTuplizer.java:55)
at
org.hibernate.tuple.entity.EntityEntityModeToTuplizerMapping.<init>(EntityEntityModeToTuplizerMapping.java:56)
at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:295)
at
org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434)
at
org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109)
at
org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55)
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294)
at
za.co.enerweb.eprofiling.tables.HibernateSessionFactory.<clinit>(HibernateSessionFactory.java:35)
at
za.co.enerweb.energyprofiling.dao.DAOServletFilter.doFilter(DAOServletFilter.java:33)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246)
... 31 more

#]


 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12796] Problem reading AMX beans after Glassfish restart Created: 26/Jul/10  Updated: 17/Jun/13

Status: Open
Project: glassfish
Component/s: amx
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: snobbles1 Assignee: Peter Bower
Resolution: Unresolved Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive Issue12796.zip    
Issuezilla Id: 12,796

 Description   

I'm accessing the jdbc resources in Glassfish via the AMX JMX beans, but I've
having problems on a Glassfish restart
If my war is deployed, and Glassfish is restarted, the war fails to deploy on
the Glassfish restart - this is due to the bean amx:pp=/domain,type=resources
not being present.
The AMX service is only started if its required (eg if the admin console is
loaded)
I've tried manually starting the AMX service from my war:
I've tried calling the method new
AMXGlassfish(AMXGlassfish.DEFAULT_JMX_DOMAIN).bootAMX() from my war, but on
restarting glassfish, the call to bootAMX() hangs indefinitely
I've also tried connecting to the AMX JMX bean with the URL
service:jmx:rmi://<local host>:8686/jndi/rmi://<local host>:8686/jmxrmi
This works if I'm deploying after Glassfish has been started, and the admin
console hasn't been loaded.
If the war is deployed, and Glassfish is restarted, this fails as Glassfish
cannot connect to the RMI JMX service.
From looking at glassfish logs, the start up sequence seems to be that Glassfish
does not launch JMX until after all existing war files have been deployed.
Version of glassfish: v3



 Comments   
Comment by prasads [ 07/Oct/10 ]

Can you please let me know the following details :

1. How does one reproduce this issue ?
2. Can you attach a sample war ?

The reason I am a bit confused is because if a application refers to a JDBC
resource, it should not need AMX to load these MBeans on a restart. The
resources should be loaded on a restart and create the required MBeans which
then would be available via AMX.

Comment by sanandal [ 08/Oct/10 ]

...

Comment by prasads [ 02/Dec/10 ]

I am downgrading this issue as I have not heard more about this issue.

Comment by prasads [ 20/Feb/11 ]

Assigning issues to Naman

Comment by sennen [ 31/Mar/11 ]

We have the same problem - and it's a bit of a show-stopper for us in trying to support both GlassFish 2.1 and 3.1.

In our case, we want to query the "amx:" tree to determine GlassFish version and then use appropriate JMX object path names and code to manipulate file-realm users, in support of a Web Service. We do this in a servlet context listener (i.e. prior to the first use of the Web Service after deployment or appserver restart).

I attach the file issue12796.zip which contains a Maven web application project created under Netbeans 6.9.1. It is a do-nothing servlet, with all the interesting stuff in the servlet context listener (MyContextListener.java). Source is included, and you will find a .war file in the "target" directory.

To repeat the problem, load the .war file into a running GlassFish 3.1 server, the log should show:

INFO: MyContextListener: constructor
INFO: MyContextListener: contextInitialized
INFO: MyContextListener: start AMX
INFO: Initialized AMXStartupServiceNew in 14 ms, registered as amx-support:type=amx-loader,name=startup
INFO: In the registerChildren of MonitoringRootImpl instance Name = server
INFO: AMX ComplianceMonitor: ValidationLevel = full, UnregisterNonCompliant = false, LogInaccessibleAttributes = true
INFO: In AMXConfigLoader : loader == null
INFO: AMX config read, domain config registered as amx:pp=/,type=domain
INFO: J2EEDomain registered at amx:pp=/,type=J2EEDomain,j2eeType=J2EEDomain,name=amx
INFO: AMXStartupServiceNew: AMX ready for use, DomainRoot = amx:pp=,type=domain-root
INFO: MyContextListener: AMX started
INFO: MyContextListener: version=Glassfish V3.1
INFO: MyContextListener: users=[user1,user2,user3]
INFO: WEB0671: Loading application [Issue12796] at [/Issue12796]
INFO: Issue12796 was successfully deployed in 1,395 milliseconds.

However, if you then restart the GlassFish application server:

INFO: MyContextListener: constructor
INFO: MyContextListener: contextInitialized
INFO: MyContextListener: start AMX
SEVERE: MyContextListener: context initialization failed
javax.management.InstanceNotFoundException: amx-support:type=boot-amx
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at com.sun.enterprise.v3.admin.DynamicInterceptor.invoke(DynamicInterceptor.java:387)
at webapp.issue12796.MyContextListener.contextInitialized(MyContextListener.java:25)
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:4690)
at com.sun.enterprise.web.WebModule.contextListenerStart(WebModule.java:534)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5305)
at com.sun.enterprise.web.WebModule.start(WebModule.java:500)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:917)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:901)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:755)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1980)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1630)
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:100)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:286)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
at com.sun.enterprise.v3.server.ApplicationLoaderService.processApplication(ApplicationLoaderService.java:364)
at com.sun.enterprise.v3.server.ApplicationLoaderService.postConstruct(ApplicationLoaderService.java:208)
at com.sun.hk2.component.AbstractCreatorImpl.inject(AbstractCreatorImpl.java:131)
at com.sun.hk2.component.ConstructorCreator.initialize(ConstructorCreator.java:91)
at com.sun.hk2.component.AbstractCreatorImpl.get(AbstractCreatorImpl.java:82)
at com.sun.hk2.component.SingletonInhabitant.get(SingletonInhabitant.java:67)
at com.sun.hk2.component.EventPublishingInhabitant.get(EventPublishingInhabitant.java:139)
at com.sun.hk2.component.AbstractInhabitantImpl.get(AbstractInhabitantImpl.java:76)
at com.sun.enterprise.v3.server.AppServerStartup.run(AppServerStartup.java:243)
at com.sun.enterprise.v3.server.AppServerStartup.start(AppServerStartup.java:135)
at com.sun.enterprise.glassfish.bootstrap.GlassFishImpl.start(GlassFishImpl.java:79)
at com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher.launch(GlassFishMain.java:117)
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 com.sun.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:97)
at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:55)

INFO: WEB0671: Loading application [Issue12796] at [/Issue12796]
INFO: CORE10010: Loading application Issue12796 done in 2,790 ms
INFO: GlassFish Server Open Source Edition 3.1 (43) startup time : Felix (1,866ms), startup services(3,530ms), total(5,396ms)
INFO: JMXStartupService: Started JMXConnector, JMXService URL = service:jmx:rmi://mypc.mydomain.org:8686/jndi/rmi://mypc.mydomain.org:8686/jmxrmi

Ideally, we'd want the "amx:" business ready and waiting for us at servlet context initialisation time.
Even better: we'd also prefer not to have to boot AMX ourselves - can it be set to start in configuration, in an end-user-friendly manner?

Comment by sennen [ 31/Mar/11 ]

Attachment as per my previous comment.

Comment by zlj [ 14/Dec/11 ]

I face nearly the same issue on GF 3.1.1.

When I do not "boot" AMX manually, I can't request any AMX/MBean attributes for my web-applications. "boot" means executing bootAMX() in MBean "amx-support:type=boot-amx".

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by Wasomumba [ 15/Jun/13 ]

The comments in this ticket address different issues. I'm talking about the problem, that the AMX Service is not available at startup, as described by sennen above.

This is caused by the fact, that the amx service is started AFTER startup of the server.

To fix this issue, i think the runlevel from "org.glassfish.admin.mbeanserver.JMXStartupService" and "org.glassfish.admin.mbeanserver.MBeanServerFactory" should be changed from "PostStartupRunLevel" to "InitRunLevel".

What do you think?

Comment by naman_mehta [ 17/Jun/13 ]

hi peter,

Assigning this issue to you. Let me know if you need any details from my side.

Naman





[GLASSFISH-12732] Replace System.getProperty by StartupContext Created: 20/Jul/10  Updated: 04/Jan/13

Status: Open
Project: glassfish
Component/s: embedded
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Sanjeeb Sahoo Assignee: Bhavanishankar
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 12,732

 Description   

Replace every use of System.getProperty by StartupContext to make the server
more embeddable. This is an umbrella issue.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by Tom Mueller [ 04/Jan/13 ]

Assigning to the embedded component for evaluation.





[GLASSFISH-12699] Allow deploy command to accept URI Created: 17/Jul/10  Updated: 21/Jan/13

Status: Open
Project: glassfish
Component/s: deployment
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Sanjeeb Sahoo Assignee: Hong Zhang
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive GLASSFISH-12699_REVISED_SOURCE.zip     Text File pathToUri_patch.txt    
Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-19497 Can't get the proper path when deploy... Sub-task Closed Hong Zhang  
GLASSFISH-19529 The asadmin client should support the... Sub-task Resolved Tom Mueller  
Issuezilla Id: 12,699

 Description   

Currently deploy, redeploy commands accept a file path. It will be nice if they
accept a URI instead. I am attaching a patch which is an attempt to address
this, but I don't think it is complete. Any way, if someone wants to take a stab
at this issue, the patch may come handy.



 Comments   
Comment by Sanjeeb Sahoo [ 17/Jul/10 ]

Created an attachment (id=4587)
Patch generated against svn rev #38356

Comment by Hong Zhang [ 17/Jul/10 ]

add tim to CC, tim is more familiar with this part

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by Jeremy_Lv [ 18/Dec/12 ]

Dear Hong, Sahoo:
I have updated the Sahoo's patch and have this new feature accomplished. But what I have revised is only can be used for deploying the applications in the local space.
i.e:asadmin deploy file:/e:/test_sample1.war(also can be useful about the operation of redeployment)

I have attached the revised source to the JIRA, please review my modification.

BTW: If we need to implement the operation about deploying the application in the Internet(i.e:deploy as http,ftp,https), we can discuss about this scenario first before I have it implemented.
i.e:(asadmin deploy http://http://java.net/jira/secure/attachment/50467/test_sample1.war)

Best Regards
-Jeremy

Comment by Hong Zhang [ 18/Dec/12 ]

Jeremy: thanks for looking into this enhancement and continuing to contribute to GlassFish!

Some comments from my initial look at the changes:

1. When a command line option is File type and annotated with @Param, the admin infrastructure will upload the file from local machine to remote machine. With the changes in DeployCommandParameters, can you make sure the cluster scenario still work as expected, the file will get uploaded as expected? I saw there are changes in MapInjectionResolver which probably take care of this, but want to double check things still work as expected for cluster scenario.

2. Can you try the server restart scenario to make sure things are working as expected there also (deploy application, restart server, and see if application is loaded properly during server start up and can be accessed afterwards)? This is a pretty significant change and I want to make sure there is no regression to the existing scenarios.

3. Run deployment dev tests in PE and EE mode and also run ejb dev tests.

4. Add some new tests in the deployment dev tests to cover the new scenario and enable these tests for both PE and EE mode.

5. The admin related changes (for example, MapInjectionResolver) need to be reviewed by the admin team. We can write to Tom Mueller about this after we make sure the various scenarios are working ok.

And yes we can have further discussions if we decide to expand the feature to support internet protocols.

Comment by Jeremy_Lv [ 09/Jan/13 ]

[Latest investigation]
The changes of mine to support the scenario about 12699 makes the original scenario about deploying the application as File(only deploy the application as relative path) doesn't work...

After I look into the code, I found the value in EntityParamValueFactoryProvider.java(jersey modules) doesn't get the correct value while deploying the application as relative path in File way(e.g: asadmin deploy test.jar)

value = requestContext.readEntity(rawType, parameter.getType(), parameter.getAnnotations());

the value here should be get the absolute path while it just get the name of the deployed application.

However, it can be deployed successfully as absolute path in File way.

Should the original scenario about deploying the application as File way still be support after it is support the URI?

Comment by Sanjeeb Sahoo [ 09/Jan/13 ]

Existing behavior has to be maintained for compatibility reasons. I think it will be reasonable to support the URI syntax for absolute URIs only. An absolute URI always has a scheme component.

Comment by Jeremy_Lv [ 10/Jan/13 ]

Dear Hong, Sahoo, Tom:
I have a question for you. Should the new feature about deploying the application accept the URI instead of File or accept the URI syntax without any changes about File syntax?

Comment by Jeremy_Lv [ 10/Jan/13 ]

After some of my investigation, I found something different between the two definations as follows:
Sample1:

 
    @Param(primary=true) 
    public File path; 
    public File getPath() { 
      return path; 
    } 

Sample2:

 
    private File path; 
     
    @Param(primary=true) 
    public void setPath(File path) { 
        this.path = path; 
    } 
     
    public File getPath() { 
      return path; 
    } 

When the @Param are defined to declare the method as the Sample2 shows, The value of "DEFAULT" is not correct when deployed as a relative File path. the jersey side get the wrong value of "reqeust" when DeployCommandParameters defined as Sample2.

Comment by Hong Zhang [ 10/Jan/13 ]

We have to continue supporting File path for backward compatibility. If that only allows us to support absolute URI, that's fine. We just need to give a good error message for the unsupported case.

I don't know the details of how the payload works (with injected File param), Tom probably knows more about that to explain why. But you will probably need to write an email to him to get his attention on this as I don't think he is monitoring issues outside of the admin area..

Comment by Tom Mueller [ 14/Jan/13 ]

While looking at the subtask GLASSFISH-19529, I decided to comment on this issue instead.

First, what are the expected semantics for the original request? If the deploy command is invoked with a URI, what is the asadmin client expected to do? For example, is the client expected to fetch the content of the URI and then treat that content the same way it treats a file today? Is the URI supposed to be passed to the server, and then the server is supposed to fetch the content of the URI? A key question is, where does the URI client code execute?

Second, since the original syntax must be supported, how is the command parameter actually declared. If it is a URI (as the subtask requests), is the asadmin client expected to convert a path argument to a URI argument automatically? How is the asadmin client supposed to know that the default URI scheme should be "file://"? Is the implementation to be hardcoded this way, or is it necessary to allow the default scheme to be specified by the command.

Or, is the idea hear to allow the operand to be of varying types depending on what is entered by the user? If it looks like a URI, then just the URI is passed, but if it looks like a path, then a File is passed? What would the @Param declaration for a command look like in this case?

Another option might be to have a "deployuri" command (similar to deploydir) which could have a different declaration for the operand.

If just a URI is to be passed to the server (not the content), and the URI references a local file, how would the server access the file if asadmin is remote from the server?

In summary, the following design options seem feasible:

1) Add a deployuri command for which the operand is a String which is passed to the server and the server resolves the URI. Therefore the URI must be resolvable by the server (can't be a file:// URI to a local file that is remote from the server).

2) Modify the CLI framework so that a File parameter (option or operand) can be specified as a URI. In that case, the asadmin client would resolve the URI and download its content to a temporary file which would then be passed as a File parameter like any other File parameter. This option would require no changes to the deploy command at all. With this option, a file:// URI to a file that is local to asadmin would work when the server is remote, but a file:// URI to a file that is local to the server but not asadmin would not work.

Other more complicated options would be to have some way of having a command option that is either a File or a URI but I haven't specified that design here.

Comment by Sanjeeb Sahoo [ 14/Jan/13 ]

I support option #1. It keeps things simple.

Sahoo

Comment by Jeremy_Lv [ 15/Jan/13 ]

First, what are the expected semantics for the original request? If the deploy command is invoked with a URI, what is the asadmin client expected to do? For example, is the client expected to fetch the content of the URI and then treat that content the same way it treats a file today? Is the URI supposed to be passed to the server, and then the server is surpposed to fetch the content of the URI? A key question is, where does the URI client code execute?

What I have supposed to do is that the client expected to fetch the content of the URI and then treat that content the same way it treats a file today.

Second, since the original syntax must be supported, how is the command parameter actually declared. If it is a URI (as the subtask requests), is the asadmin client expected to convert a path argument to a URI argument automatically? How is the asadmin client supposed to know that the default URI scheme should be "file://"? Is the implementation to be hardcoded this way, or is it necessary to allow the default scheme to be specified by the command.
Or, is the idea hear to allow the operand to be of varying types depending on what is entered by the user? If it looks like a URI, then just the URI is passed, but if it looks like a path, then a File is passed? What would the @Param declaration for a command look like in this case?

What I have revised is to define a path as a URI parameter. Then I will try to convert a path argument to a URI argument when it is excuted in the asadmin client.

All in all, What I have revised is based on the option#2, which is defined a URI parameter and change the File to URI when the application is deployed as a File.

BTW: If we decide to take the option#1, I will look into the logical about deploydir first before I code.

Comment by Jeremy_Lv [ 15/Jan/13 ]

Thanks for Tom's suggestion, After being compare these two options I think the option#1 seems better than option#2.
It seems not diffcult to develop and it is no longer to change codes in CLI.

Comment by Jeremy_Lv [ 15/Jan/13 ]

As the JIRA file system can not work, I have sent my modification by email. please check it.

Comment by Jeremy_Lv [ 21/Jan/13 ]

Hi,All:
As Tom has been suggested, I want to make sure what function should I implement.
Here is my option:
1.Support a new command like "deployuri", The "deployuri" will support the following options
1).--name <name>
2).--contextroot <contextroot>
3).--virtualservers <virtualservers>
4).--libraries <libraries>
5).--force[=<force(default:false)>]
6).--precompilejsp[=<precompilejsp(default:false)>]
7).--verify[=<verify(default:false)>]
8).--retrieve <retrieve>
9).--dbvendorname <dbvendorname>
10).--createtables[=<createtables(default:false)>]
11).--dropandcreatetables[=<dropandcreatetables(default:false)>]
12).--uniquetablenames[=<uniquetablenames(default:false)>]
13).--deploymentplan <deploymentplan>
14).--altdd <altdd>
15).--runtimealtdd <runtimealtdd>
16).--enabled[=<enabled(default:false)>]
17).--generatermistubs[=<generatermistubs(default:false)>]
18).--availabilityenabled[=<availabilityenabled(default:false)>]
20).--asyncreplication[=<asyncreplication(default:true)>]
21).--target <target>
22).--keepreposdir[=<keepreposdir(default:false)>
23).--keepfailedstubs[=<keepfailedstubs(default:false)>]
24).--logreportederrors[=<logreportederrors(default:true)>]
25).--description <description>
26).--properties <properties>
27).--property <property>
28).--type <type>
29).--keepstate[=<keepstate(default:false)>]
30).--lbenabled <lbenabled>
31).--deploymentorder <deploymentorder>
32).--upload[=<upload(default:false)>]
33).?|-help[=<help(default:false)>]

BTW:As the application is deployed as URI, Should we give up the function about --upload? (The original option about --upload is support for File types.)

2.Should I support another command which is used for redeploy the application as URI?(As the description shows)

Notice: As the URI is complex type to use, I think I will support the file:// syntax first.

If someone want to present more options about this improvement, please comments.

Best regards
-Jeremy





[GLASSFISH-12628] Disable buttons on screen during long operation Created: 12/Jul/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: HTML File sample.html    
Issuezilla Id: 12,628

 Description   

When there is a long operation, eg, starting a cluster with many instance,
deploy/upload a large files, we should try to disable other buttons on screen
instead of just disable the one user just pressed.

Ken and Jason briefly looked into this and provide the attached html file as a
way that can be done.
Will still need to style it, provide localized message etc.
This will be a nice enhancement.



 Comments   
Comment by Anissa Lam [ 12/Jul/10 ]

Created an attachment (id=4565)
sample.html

Comment by Anissa Lam [ 12/Jul/10 ]

target ms6.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12598] provide apis that will allow restful access to Created: 08/Jul/10  Updated: 15/Jan/13

Status: Open
Project: glassfish
Component/s: jax-rs
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Critical
Reporter: vince kraemer Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: JPEG File gui-webServiceEndpointInfo.jpg     File TestWebJAX-WS20.war    
Issue Links:
Dependency
blocks GLASSFISH-12361 need rest interface to webservice end... Resolved
Issuezilla Id: 12,598

 Description   

webservice endpoint data like the data available in
https://glassfish.dev.java.net/nonav/issues/showattachment.cgi/4546/details-for-ws-management.png

the details will need to be worked out with Jason Lee or Ludovic Champenois



 Comments   
Comment by vince kraemer [ 08/Jul/10 ]

see issue 12361 for additional details

Comment by Anissa Lam [ 12/Jul/10 ]

GUI needs to convert the web service endpoint information screen to use the REST
API. Please see the attached screen.
In v3, this is through a monitoring bean and invoke the appropriate method.

Here is the code:
private static TabularData getEndpointMap (String appName, String moduleName,
String componentName, String type){
ServerMon serverMon =
V3AMX.getInstance().getDomainRoot().getMonitoringRoot().getServerMon().get("server").as(ServerMon.class);
AMXConfigProxy webDeployment =
serverMon.childrenMap("web-service-mon").get("webservices-deployment").as(AMXConfigProxy.class);
String[] params = new String[]

{ appName, moduleName, componentName}

;
String[] sig = new String[]

{"java.lang.String", "java.lang.String", "java.lang.String"}

;
TabularData endpointMap = null;
if (type.equalsIgnoreCase("Servlet"))

{ endpointMap = (TabularData) webDeployment.invokeOp("getServlet109Endpoint", params, sig); }

else

{ endpointMap = (TabularData) webDeployment.invokeOp("getEjb109Endpoint", params, sig); }

return endpointMap;
}

I need to be able to do the same through some REST API.
I have shown this to Jitu and requested him to look into this. There maybe CLI
currently able to do that. He will get back to me.

Change to P2 and assign to Jitu.

Comment by Anissa Lam [ 12/Jul/10 ]

Created an attachment (id=4564)
GUI Web Service Endpoint Info screen

Comment by vince kraemer [ 12/Jul/10 ]

Anissa: thanks for filling in the details on this.

Comment by vince kraemer [ 23/Aug/10 ]

Is there an update on this issue?

I plan on having the view for this data implemented shortly in the glassfish
integration for netbeans, since I can put together 'mock' data easy enough. But
I really need to have access to the live data to validate the interface and
resolve any issues that might get exposed.

Comment by jitu [ 25/Aug/10 ]

I did receive some code for adding asadmin commands from Ludo. However, I will
take a look at this issue after a week or so.

Comment by vince kraemer [ 25/Aug/10 ]

thanks for the update. I should have a client ready for this next week, too.

Comment by vince kraemer [ 02/Sep/10 ]

The client for this is 'ready'. Have you gotten a chance to implement the 'server' for this data?

Comment by jitu [ 09/Sep/10 ]

Added a hidden asadmin command to list web services

Usage: asadmin [asadmin-utility-options] __list-webservices
[--applicationname <applicationname>] [--modulename <modulename>]
[--endpointname <endpointname>] [?|-help[=<help(default:false)>]]

But actually it is(don't know if there is way to show it as follows):
asadmin [asadmin-utility-options] __list-webservices
[-applicationname <applicationname> [modulename <modulename> [-
endpointname <endpointname>]]]

For example:
$ ./asadmin __list-webservices --applicationname echo
application:echo
module:echo
endpoint:Echo
appName:echo
tester:/echo/echoService?Tester
wsdl:/echo/echoService?wsdl
address:/echo/echoService
implType:SERVLET
deploymentType:109
endpointName:Echo
portName:EchoPort
implClass:fromjava.nosei.server.EchoImpl
serviceName:echoService
namespace:http://echo.org/

one can drill down using --applicationname --modulename --endpointname

Also, for REST interface, the whole tree is set as extra properties.

Eventhough it shows --servletlink, --ejblink in the usage, I plan to delete
them. Let me know if this works for you.

Comment by jitu [ 27/Sep/10 ]

Reassigning to Anissa.

Comment by Anissa Lam [ 27/Sep/10 ]

I think the output needs to be modified. Using extraProperties is ok, but there
is no way for me to know what is what.

Here is what i am seeing if i deploy the attached web service:

{"command":"__list-webservices
AdminCommand","exit_code":"SUCCESS","extraProperties":{"TestWebJAX-WS20":{"TestWebJAX-WS20":{"NewService":{"appName":"TestWebJAX-WS20","tester":"\/TestWebJAX-WS20\/NewServiceService?Tester","wsdl":"\/TestWebJAX-WS20\/NewServiceService?wsdl","address":"\/TestWebJAX-WS20\/NewServiceService","implType":"SERVLET","deploymentType":"109","endpointName":"NewService","portName":"NewServicePort","implClass":"service.NewService","serviceName":"NewServiceService","namespace":"http:\/\/service\/"}}}},"children":[{"message":"application:TestWebJAX-WS20","properties":{},"children":[{"message":"
module:TestWebJAX-WS20","properties":{},"children":[{"message":"
endpoint:NewService","properties":{},"children":[{"message":"
appName:TestWebJAX-WS20","properties":{},"children":[{"message":"
tester:\/TestWebJAX-WS20\/NewServiceService?Tester","properties":{},"children":[{"message":"

wsdl:\/TestWebJAX-WS20\/NewServiceService?wsdl","properties":{},"children":[{"message":"

address:\/TestWebJAX-WS20\/NewServiceService","properties":{},"children":[{"message":"
implType:SERVLET","properties":{},"children":[{"message":"
deploymentType:109","properties":{},"children":[{"message":"
endpointName:NewService","properties":{},"children":[{"message":"
portName:NewServicePort","properties":{},"children":[{"message":"
implClass:service.NewService","properties":{},"children":[{"message":"
serviceName:NewServiceService","properties":{},"children":[{"message":"
namespace:http:\/\/service\/","properties":{}}]}]}]}]}]}]}]}]}]}]}]}]}]}]}

the CLI output looks fine:

v3admin __list-webservices --applicationname TestWebJAX-WS20
application:TestWebJAX-WS20
module:TestWebJAX-WS20
endpoint:NewService
appName:TestWebJAX-WS20
tester:/TestWebJAX-WS20/NewServiceService?Tester
wsdl:/TestWebJAX-WS20/NewServiceService?wsdl
address:/TestWebJAX-WS20/NewServiceService
implType:SERVLET
deploymentType:109
endpointName:NewService
portName:NewServicePort
implClass:service.NewService
serviceName:NewServiceService
namespace:http://service/

Command __list-webservices executed successfully.

Are you saying that the
key of first map is 'application', followed by 'module' and then followed by
'endpoint' ?

I am really confused here.

but there is no 'key' for 'module' and 'endpoint'.

Comment by Anissa Lam [ 27/Sep/10 ]

After deploying the attached webservice, you can go to

http://localhost:4848/management/domain/list-webservices.json?applicationname=TestWebJAX-WS20

to see the output.

Comment by Anissa Lam [ 27/Sep/10 ]

Created an attachment (id=4974)
sample webservice

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12597] Web Service Tester not available for secure endpoints Created: 08/Jul/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: web_services
Affects Version/s: v3.0.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: catchwa Assignee: Bhakti Mehta
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive SecWSTester.zip    
Issuezilla Id: 12,597

 Description   

Steps to reproduce in NetBeans 6.9 (roughly based on
http://java.sun.com/webservices/reference/tutorials/wsit/doc/WSIT_Security9.html
#wp162511)

1. Create a new Web Application
2. Create a new Web Service
3. Add an operation to your web service
4. In the Edit Web Service Attributes dialog, tick Secure Service and select
Mutual Certificates Security. Leave the other security settings at their
Development Defaults.
5. Export the sample client key that is bundled with GlassFish into a PKCS12
certificate:

C:\glassfishv3\glassfish\domains\domain1\config>keytool -importkeystore -
srckeystore keystore.jks srcstoretype JKS -srcstorepass changeit -srcalias xws
security-client -destalias xws-security-client -deststoretype PKCS12 -
destkeystore client.p12

6. Import client.p12 into your web browser.
7. Deploy Web Service to GlassFish

Note that the following URLs work as expected
https://localhost:8181/SecWSTester/
https://localhost:8181/SecWSTester/NewWebServiceService
https://localhost:8181/SecWSTester/NewWebServiceService?wsdl

Note, however, that the Web Service Tester that is found at:
https://localhost:8181/SecWSTester/NewWebServiceService?Tester

just displays a blank page.

1.) As the Tester isn't currently available for secure endpoints GlassFish
should display a message to reflect this, rather than not giving any feedback
to the user/developer.

2.) As an enhancement, GlassFish should allow for Web Service Testing
functionality on secure endpoints.



 Comments   
Comment by catchwa [ 08/Jul/10 ]

Created an attachment (id=4555)
Sample NetBeans project (minus contents of the /lib directory to save space)

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12541] config->JVM Settings ->General TAB Created: 06/Jul/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: not determined

Type: New Feature Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
depends on GLASSFISH-12418 convert all property table related ha... Resolved
Issuezilla Id: 12,541

 Description   

Need to finishing up property table conversion



 Comments   
Comment by Anissa Lam [ 06/Jul/10 ]

MS3

Comment by Anissa Lam [ 24/Jul/10 ]

MS4

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12503] deployment differences in comparison to v2 Created: 06/Jul/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: deployment
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: Bhavanishankar Assignee: Hong Zhang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: Linux


Attachments: File ejbwar.war     Text File server.log    
Issuezilla Id: 12,503

 Description   

If a web application of 2.4 version has a @Stateless EJB, the deployment goes
through fine in v2 by ignoring the EJB.

But with v3.1, the deployment fails with

remote failure: Exception while preparing the app : java.lang.RuntimeException:
Unable to load EJB module. DeploymentContext does not contain any EJB Check
archive to ensure correct packaging for
/space/bhavani/ws/glassfish/image/glassfishv3/glassfish/domains/domain1/applications/ejbwar

I have attached both the .war and server.log files.



 Comments   
Comment by Bhavanishankar [ 06/Jul/10 ]

Created an attachment (id=4543)
ejbwar.war

Comment by Bhavanishankar [ 06/Jul/10 ]

Created an attachment (id=4544)
server.log

Comment by Hong Zhang [ 06/Jul/10 ]

As v3 supports ejb lite (ejb in war case), there would definitely be some
behavior change if there is EJB packaged inside the war (previously ignored,
now loaded as part of the war).

The problem in this case, I think is the annotation processing was not
triggered for DOL (as the web.xml referenced an old version of the dtd),but
the EJB annotation was processed during sniffer scanning. We will try to see if
we can improve the error message somewhat to make it more useful for the users.

Comment by Bhavanishankar [ 06/Jul/10 ]

Hi Hong,

Yes, that will do. Probably deploy with a warning or abort deployment with a
error message.
With current error message, I had trouble figuring out what is wrong with the
war, until Sahoo told me.

--Bhavani.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.





[GLASSFISH-12501] support command line options in glassfish specific deployment descriptors Created: 06/Jul/10  Updated: 15/May/13

Status: Open
Project: glassfish
Component/s: deployment
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: Hong Zhang Assignee: Hong Zhang
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 12,501

 Description   

It's useful to allow user to specify command line options through glassfish
specific deployment descriptors, especially for autodeploy and JSR88.

Ludo suggested we could support them generically through a deployment-params
element:
<deployment-params> --foo=bar --keeptable =true etc etc
</deployment-params>

And later Bill suggested rather than creating another place that has to parse a
command line, it probably be more appropriate to have a general way to specify
option names and values as XML:

<deployment-params>
<param><name>foo</name><value>bar</value></param>
<param><name>keepstate</name><value>true</value></param>
</deployment-params>

I don't think we will have time to address this in 3.1 release, but file a RFE
to track this and we will revisit in next release.



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by Jeremy_Lv [ 15/May/13 ]

I agree with you, it will be more useful if we implement this..





[GLASSFISH-12423] Load Balancer Issue with Glassfish Created: 29/Jun/10  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: web_container
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: vinodmutyala Assignee: Amy Roh
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows 2000
Platform: Other


Issuezilla Id: 12,423

 Description   

I am running into issue configuring the ServerIron 450 load balncer in front of
the Glassfish APP server. we are running Apache web application which is calling
Glassfish application URL. when i specify the APP server URL the applcation
server and it works fine we have planned to put a physical load balancer in
front of 2 APP server which is running on Glassfish V3. all the rules are in
place for Load Balancer to forward the requrest to one of the APP servers. but
the request is failing when the Load balancer IP is in place of actual APP
servers. Both the app servers are running and they are able to telnet on port
8080 from the load balancer, but when the application is configured to use the
Load balancer URL it does not work. i really need this to work.

Does the Glassfish V3 has any limitation for suing physical load balance or do i
need to change some configuration in glassfish to serve the request when they
are from load balancer.

Your help is very much appropriated.

Thank you.



 Comments   
Comment by kumara [ 29/Jun/10 ]

Please provide a test case or HTTP traffic between client and load balancer and load balancer to
glassfish instances.

While I do not remember anyone using ServerIron 450 as a load balancer in front of GlassFish, other
hardware load balancers have been used with GlassFish. The configuration as you can imagine will
depend on application as well as hardware load balancer.

As for software load balancer, review the following blog for using Apache/mod_jk –
http://weblogs.java.net/blog/amyroh/archive/2009/06/running_glassfi.html

-> web_container because that is the team likely to suggest the best glassfish configuration once we
see the http traffic trace

Comment by vinodmutyala [ 30/Jun/10 ]

Hi Kumara Thank you for your response. Please find the case study / HTTP traffic
reports attached.

Here is the Env setup we have.

3 web servers running Apache 2.2 and they have the web application loaded on
them, these servers are also using Drupal as Content Management these are
serving the site .

These Web servers are configured to use load balancer

Web server 1 ---- 192.168.49.20
Web Server 2 ----- 192.168.49.21
Web server 3 ----- 192.168.49.22

Above server are configured for Hardware Load Ba lancer ServerIron 450 -
192.168.152.44

These Web server are configured to use the GlassFish V3 as Application server
which WSDL calls made from web servers ( Load Balacer ) to the APP servers.

App Server 1 ---- 192.168.50.90
App Server 2 ---- 192.168.50.91

Above APP servers are configured to use Hard Ware Load Balancer ServerIron 450
– 192.168.152.43

When the Web servers are configured to use the APP URLs (
http://192.168.50.90:8080/Service-broker ) this is direct call not using the
Load Balancer Application responds.

But when we use the Load Balcer IP / DNS name (
http://192.168.152.43:8080/service-broker ) the Application does not respond.
The request dies at the Glassfish Application layer.

I have looked at the Mod_JK configuration and we alredy are using it to direct
the traffic on port 80 instead of 8080. This plug in works fine and the web
server forwards the request to Glassfish server , so we can access the URL by
http://109.168.50.90/Service-broker or with the load balancer
http://192.168.152.43/service-broker.

But the when the URL is changes from APP servers to the Load Balancer IP site
wont respond. Hope this gives you the clear idea of environment and the issue we
are having.

I am also attaching the Port Scan we did using Wireshark from the Client which
is accessing the URL and also from the Glassfish APP server. According to our
network team Glassfish response when the request is coming for direct APP server
URL but it does not when the request is for the load balancer IP.

Hope this will help you understand the issue and would enable you to give us the
GlassFish configuration so it can work with Hardware Load Balancer.

Thank you for your time and looking forward for your response.

Comment by kumara [ 30/Jun/10 ]

> According to our network team Glassfish response when the request is coming for direct APP server
> URL but it does not when the request is for the load balancer IP.

Is there any indication that the load balancer sends http requests to GlassFish server? If yes, can you
check to see what the error condition is – GlassFish server did not respond (timed out), server
responded with an error code, connection was interrupted. Please include the network traffic trace that
shows the request from load balancer and response from GlassFish server. If no, then you should look
at the load balancer configuration and determine why the request does not make it to GlassFish server.

Most load balancers have a way to check the status of server that they are load balancing to (typically
called health check). Is the load balancer able to see GlassFish server as "Alive"? It is possible that the
health check that works for web servers does not work for GlassFish server. If the load balancer is
reporting GlassFish as "not alive" when you know it is "alive", tell us more about the health check
mechanism.

Minor nit – this may be a non-issue but you seem to have a mix of upper case and lower case letters
in the path "/Service-broker" vs. "/service-broker". If the configuration is correct, this will work but I
just wanted to make sure that there is no simple oversight here.

Comment by Shing Wai Chan [ 30/Jun/10 ]

reassigned

Comment by vinodmutyala [ 01/Jul/10 ]

Please find the HTTP trace from Load balancer to APP server.

The source is 192.168.50.4 ( Load Balancer ) to 192.168.50 .90 ( APP server )

I was not able to save filtered data, sorry for the lenghty tarce.

No. Time Source Destination Protocol Info
2393 86.051748 192.168.50.4 192.168.50.90 TCP 11039
> http [SYN] Seq=0 Win=5840 Len=0 MSS=1380 TSV=723675161 TSER=0 WS=7

Frame 2393 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 0, Len: 0

No. Time Source Destination Protocol Info
2397 86.052734 192.168.50.4 192.168.50.90 TCP 11039
> http [ACK] Seq=1 Ack=1 Win=5888 Len=0 TSV=723675162 TSER=13595095

Frame 2397 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
2398 86.052875 192.168.50.4 192.168.50.90 TCP [TCP
segment of a reassembled PDU]

Frame 2398 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
2399 86.254566 192.168.50.4 192.168.50.90 TCP [TCP
Retransmission] [TCP segment of a reassembled PDU]

Frame 2399 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
2401 86.254921 192.168.50.4 192.168.50.90 TCP [TCP
Dup ACK 2399#1] 11039 > http [ACK] Seq=54 Ack=1 Win=5888 Len=0 TSV=723675365
TSER=13595095

Frame 2401 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 54, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
2407 86.656550 192.168.50.4 192.168.50.90 TCP [TCP
Retransmission] [TCP segment of a reassembled PDU]

Frame 2407 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
2409 86.656914 192.168.50.4 192.168.50.90 TCP [TCP
Dup ACK 2407#1] 11039 > http [ACK] Seq=54 Ack=1 Win=5888 Len=0 TSV=723675767
TSER=13595095

Frame 2409 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 54, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
2437 87.460474 192.168.50.4 192.168.50.90 TCP [TCP
Retransmission] [TCP segment of a reassembled PDU]

Frame 2437 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
2439 87.460841 192.168.50.4 192.168.50.90 TCP [TCP
Dup ACK 2437#1] 11039 > http [ACK] Seq=54 Ack=1 Win=5888 Len=0 TSV=723676571
TSER=13595095

Frame 2439 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 54, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
2469 89.068306 192.168.50.4 192.168.50.90 TCP [TCP
Retransmission] [TCP segment of a reassembled PDU]

Frame 2469 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
2471 89.068688 192.168.50.4 192.168.50.90 TCP [TCP
Dup ACK 2469#1] 11039 > http [ACK] Seq=54 Ack=1 Win=5888 Len=0 TSV=723678179
TSER=13595095

Frame 2471 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 54, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
2560 92.283941 192.168.50.4 192.168.50.90 TCP [TCP
Retransmission] [TCP segment of a reassembled PDU]

Frame 2560 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
2562 92.284291 192.168.50.4 192.168.50.90 TCP [TCP
Dup ACK 2560#1] 11039 > http [ACK] Seq=54 Ack=1 Win=5888 Len=0 TSV=723681395
TSER=13595095

Frame 2562 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 54, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
2715 98.715345 192.168.50.4 192.168.50.90 TCP [TCP
Retransmission] [TCP segment of a reassembled PDU]

Frame 2715 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
2717 98.715730 192.168.50.4 192.168.50.90 TCP [TCP
Dup ACK 2715#1] 11039 > http [ACK] Seq=54 Ack=1 Win=5888 Len=0 TSV=723687827
TSER=13595095

Frame 2717 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 54, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
3064 111.578064 192.168.50.4 192.168.50.90 TCP [TCP
Retransmission] [TCP segment of a reassembled PDU]

Frame 3064 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
3066 111.578454 192.168.50.4 192.168.50.90 TCP [TCP
Dup ACK 3064#1] 11039 > http [ACK] Seq=54 Ack=1 Win=5888 Len=0 TSV=723700691
TSER=13595095

Frame 3066 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 54, Ack: 1, Len: 0

No. Time Source Destination Protocol Info
3955 137.303395 192.168.50.4 192.168.50.90 TCP [TCP
Retransmission] [TCP segment of a reassembled PDU]

Frame 3955 (119 bytes on wire, 119 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53

No. Time Source Destination Protocol Info
3957 137.303750 192.168.50.4 192.168.50.90 TCP [TCP
Dup ACK 3955#1] 11039 > http [ACK] Seq=54 Ack=1 Win=5888 Len=0 TSV=723726418
TSER=13595095

Frame 3957 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 54, Ack: 1, Len: 0

Comment by vinodmutyala [ 01/Jul/10 ]

Here is the Difference of trace when we use Load Balancer and when do not use
Load Balancer. This would give you complete trace when the APP response to the
IP which is web server

Source is web server 192.168.49.20 and the destinatio is APP server
192.168.50.90 , this is working fine.

No. Time Source Destination Protocol Info
235 9.789226 192.168.49.21 192.168.50.90 TCP [TCP
segment of a reassembled PDU]

Frame 235 (119 bytes on wire, 119 bytes captured)
Arrival Time: Jun 25, 2010 16:47:08.009935000
[Time delta from previous captured frame: 0.000068000 seconds]
[Time delta from previous displayed frame: 9.789226000 seconds]
[Time since reference or first frame: 9.789226000 seconds]
Frame Number: 235
Frame Length: 119 bytes
Capture Length: 119 bytes
[Frame is marked: False]
[Protocols in frame: eth:ip:tcp:http]
[Coloring Rule Name: HTTP]
[Coloring Rule String: http || tcp.port == 80]
Ethernet II, Src: Cisco_37:6e:00 (00:24:c4:37:6e:00), Dst: HewlettP_4f:22:48
(18:a9:05:4f:22:48)
Destination: HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Address: HewlettP_4f:22:48 (18:a9:05:4f:22:48)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
.... ..0. .... .... .... .... = LG bit: Globally unique address
(factory default)
Source: Cisco_37:6e:00 (00:24:c4:37:6e:00)
Address: Cisco_37:6e:00 (00:24:c4:37:6e:00)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
.... ..0. .... .... .... .... = LG bit: Globally unique address
(factory default)
Type: IP (0x0800)
Internet Protocol, Src: 192.168.49.21 (192.168.49.21), Dst: 192.168.50.90
(192.168.50.90)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 105
Identification: 0xea1a (59930)
Flags: 0x02 (Don't Fragment)
0.. = Reserved bit: Not Set
.1. = Don't fragment: Set
..0 = More fragments: Not Set
Fragment offset: 0
Time to live: 63
Protocol: TCP (0x06)
Header checksum: 0x6cb4 [correct]
[Good: True]
[Bad : False]
Source: 192.168.49.21 (192.168.49.21)
Destination: 192.168.50.90 (192.168.50.90)
Transmission Control Protocol, Src Port: 41876 (41876), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53
Source port: 41876 (41876)
Destination port: http (80)
[Stream index: 26]
Sequence number: 1 (relative sequence number)
[Next sequence number: 54 (relative sequence number)]
Acknowledgement number: 1 (relative ack number)
Header length: 32 bytes
Flags: 0x18 (PSH, ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgement: Set
.... 1... = Push: Set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 5888 (scaled)
Checksum: 0xb529 [validation disabled]
[Good Checksum: False]
[Bad Checksum: False]
Options: (12 bytes)
NOP
NOP
Timestamps: TSval 723428295, TSecr 13571531
[SEQ/ACK analysis]
[Number of bytes in flight: 53]
TCP segment data (53 bytes)

0000 18 a9 05 4f 22 48 00 24 c4 37 6e 00 08 00 45 00 ...O"H.$.7n...E.
0010 00 69 ea 1a 40 00 3f 06 6c b4 c0 a8 31 15 c0 a8 .i..@.?.l...1...
0020 32 5a a3 94 00 50 4c 1f a9 68 12 44 06 3f 80 18 2Z...PL..h.D.?..
0030 00 2e b5 29 00 00 01 01 08 0a 2b 1e a3 c7 00 cf ...)......+.....
0040 15 cb 47 45 54 20 2f 73 65 72 76 69 63 65 2d 62 ..GET /service-b
0050 72 6f 6b 65 72 2f 6d 65 6d 62 65 72 73 68 69 70 roker/membership
0060 53 65 72 76 69 63 65 3f 77 73 64 6c 20 48 54 54 Service?wsdl HTT
0070 50 2f 31 2e 30 0d 0a P/1.0..

But when we repalce the Source IP addredd with Load Balancer IP we dont get a
reply back from Glassfish APP server. , see the below trace.

Source is Load balancer 192.168.50.4 and the destinatio is APP server
192.168.50.90 , this is NOT working

No. Time Source Destination Protocol Info
2398 86.052875 192.168.50.4 192.168.50.90 TCP [TCP
segment of a reassembled PDU]

Frame 2398 (119 bytes on wire, 119 bytes captured)
Arrival Time: Jun 25, 2010 16:51:03.669963000
[Time delta from previous captured frame: 0.000141000 seconds]
[Time delta from previous displayed frame: 86.052875000 seconds]
[Time since reference or first frame: 86.052875000 seconds]
Frame Number: 2398
Frame Length: 119 bytes
Capture Length: 119 bytes
[Frame is marked: False]
[Protocols in frame: eth:ip:tcp:http]
[Coloring Rule Name: HTTP]
[Coloring Rule String: http || tcp.port == 80]
Ethernet II, Src: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02), Dst:
HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Destination: HewlettP_4f:22:48 (18:a9:05:4f:22:48)
Address: HewlettP_4f:22:48 (18:a9:05:4f:22:48)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
.... ..0. .... .... .... .... = LG bit: Globally unique address
(factory default)
Source: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02)
Address: MS-NLB-PhysServer-18_f2:16:2a:02 (02:12:f2:16:2a:02)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
.... ..1. .... .... .... .... = LG bit: Locally administered address
(this is NOT the factory default)
Type: IP (0x0800)
Internet Protocol, Src: 192.168.50.4 (192.168.50.4), Dst: 192.168.50.90
(192.168.50.90)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 105
Identification: 0x551d (21789)
Flags: 0x02 (Don't Fragment)
0.. = Reserved bit: Not Set
.1. = Don't fragment: Set
..0 = More fragments: Not Set
Fragment offset: 0
Time to live: 63
Protocol: TCP (0x06)
Header checksum: 0x00c3 [correct]
[Good: True]
[Bad : False]
Source: 192.168.50.4 (192.168.50.4)
Destination: 192.168.50.90 (192.168.50.90)
Transmission Control Protocol, Src Port: 11039 (11039), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 53
Source port: 11039 (11039)
Destination port: http (80)
[Stream index: 260]
Sequence number: 1 (relative sequence number)
[Next sequence number: 54 (relative sequence number)]
Acknowledgement number: 1 (relative ack number)
Header length: 32 bytes
Flags: 0x18 (PSH, ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgement: Set
.... 1... = Push: Set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 5888 (scaled)
Checksum: 0x0254 [validation disabled]
[Good Checksum: False]
[Bad Checksum: False]
Options: (12 bytes)
NOP
NOP
Timestamps: TSval 723675163, TSecr 13595095
[SEQ/ACK analysis]
[Number of bytes in flight: 53]
TCP segment data (53 bytes)

0000 18 a9 05 4f 22 48 02 12 f2 16 2a 02 08 00 45 00 ...O"H....*...E.
0010 00 69 55 1d 40 00 3f 06 00 c3 c0 a8 32 04 c0 a8 .iU.@.?.....2...
0020 32 5a 2b 1f 00 50 fc 09 b3 d7 63 21 05 00 80 18 2Z+..P....c!....
0030 00 2e 02 54 00 00 01 01 08 0a 2b 22 68 1b 00 cf ...T......+"h...
0040 71 d7 47 45 54 20 2f 73 65 72 76 69 63 65 2d 62 q.GET /service-b
0050 72 6f 6b 65 72 2f 6d 65 6d 62 65 72 73 68 69 70 roker/membership
0060 53 65 72 76 69 63 65 3f 77 73 64 6c 20 48 54 54 Service?wsdl HTT
0070 50 2f 31 2e 30 0d 0a P/1.0..

Comment by kumara [ 02/Jul/10 ]

Thank you for including the trace. The trace does show that two different IP addresses are making the
same request to a server (53 bytes). However, there is nothing to show the difference in response from
the server.

As an example, here is a sample HTTP request/response that I just tried. Would it be possible to include
the request and response so we can make further progress.

$ telnet localhost 8080
Connected to localhost.
Escape character is '^]'.
GET /hello-jaxws2.2/HelloService?wsdl HTTP/1.1
Host: localhost:8080
Connection: Close

HTTP/1.1 200 OK
X-Powered-By: Servlet/3.0
Server: GlassFish v3
Content-Type: text/xml;charset=utf-8
Date: Fri, 02 Jul 2010 07:28:09 GMT
Connection: close

<?xml version='1.0' encoding='UTF-8'?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net.
RI's version is JAX-WS RI 2.2-hudson-752-. -><!- Generated by JAX-WS RI at http://jax-
ws.dev.java.net. RI's version is JAX-WS RI 2.2-hudson-752-. -->

      • Remaining WSDL Deleted for better readability ***
        Connection closed by foreign host.
Comment by vinodmutyala [ 06/Jul/10 ]

Here is the HTTP response from the APP server using telnet. not sure if this
helps. but the WSDL file URL does not print any info on the telnet session.

telnet> open 192.168.50.90 8080
Trying 192.168.50.90...
Connected to n01apw878.dev.goaaa.pri (192.168.50.90).
Escape character is '^]'.
GET /service-broker/membershipService?wsdl HTTP/1.1
Connection closed by foreign host.
[xezzmuty@n01apl025 ~]$

192.168.50.90 is the Glassfish APP server and
/service-broker/membershipService?wsdl is the Context root/ URL for the service
call to the APP servers.

Please let me know if more information is needed.

Thank you.

Comment by vinodmutyala [ 06/Jul/10 ]

Here is the HTTP response from the APP server using telnet. not sure if this
helps

telnet> open 192.168.50.90 8080
Trying 192.168.50.90...
Connected to n01apw878.dev.goaaa.pri (192.168.50.90).
Escape character is '^]'.
GET /service-broker/membershipService?wsdl HTTP/1.1

HTTP/1.1 400 Bad Request
Content-Type: text/html
Content-Length: 721
Date: Tue, 06 Jul 2010 22:02:47 GMT
Connection: close

<html><head><title>Grizzly/1.9.18-k</title><style><!--H1

{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}

H2

{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}

H3

{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}

BODY

{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;}

B

{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}

P

{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}

A

{color : black;}

HR

{color : #525D76;}

--></style> </head><body><h1>BAD
REQUEST</h1><HR size="1"
noshade><h3>Grizzly/1.9.18-k</h3></body></html>Connection closed by foreign host.

192.168.50.90 is the Glassfish APP server and
/service-broker/membershipService?wsdl is the Context root/ URL for the service
call to the APP servers.

Please let me know if more information is needed.

Comment by vinodmutyala [ 09/Jul/10 ]

were you able to look at the below response HTTP from the APP servers. please
let me know if you need more information.

Comment by kumara [ 09/Jul/10 ]

We still need to see the http request and response for the cases that work and the cases that do not
work. I gave an example using telnet, but you can use any tool you like to capture both the request and
the response for us to make further progress.

In my example, following lines were typed by me –

$ telnet localhost 8080
GET /hello-jaxws2.2/HelloService?wsdl HTTP/1.1
Host: localhost:8080
Connection: Close

The last three lines above form the HTTP request.

The remaining lines in the example were returned by the server (except my editorial comment of
deleting the WSDL). Those lines are the HTTP response.

Hope this helps you understand what we are looking for.

Comment by vinodmutyala [ 09/Jul/10 ]

Here is the HTTP response from the APP server using telnet. I have sent this
before not sure if u were able to take a look at this. below is the info.

telnet> open 192.168.50.90 8080
Trying 192.168.50.90...
Connected to n01apw878.dev.goaaa.pri (192.168.50.90).
Escape character is '^]'.
GET /service-broker/membershipService?wsdl HTTP/1.1

HTTP/1.1 400 Bad Request
Content-Type: text/html
Content-Length: 721
Date: Tue, 06 Jul 2010 22:02:47 GMT
Connection: close

<html><head><title>Grizzly/1.9.18-k</title><style><!--H1

{font-family:Tahoma,Arial,sans-serif;color:white;background-colo